Storagemigrationmadesimple Wp Gtw01274 Usen 01 121307

7/31/2019 Storagemigrationmadesimple Wp Gtw01274 Usen 01 121307

1/28

IBM Global Technology Services

December 2007

Storage migrations made simple.

Overcoming the challenges of technology refresh


2/28

Contents

2 Executive summary

4 Introduction

6 Data migration software

10 Technology refresh examples

28 Summary

Executive summary

Minimizing the impact of data migrations on business operations is a critical

part of the data center managers job. Studies have shown that technology

refreshdened as replacing an older server or storage array with a new

one is the primary driver of data migration. Storage hardware and server

replacement, as well as the expiration of storage equipment leases, means that

storage managers have to move data on a regular basis. Moving data for tech-

nology refresh can be problematic, however, due to application availabilityrequirements, incompatibilities between source and target systems, and time

and budget constraints. While technology refresh projects are typically sched-

uled to be performed during off-hours, todays 24x7 environment means that

applications need to stay online, even during off-hours.

New software allows nondisruptive migration, meaning that applications

remain online during migration, without signicant performance delays. And

reliable methodologies that help plan, migrate and validate data migrations

can enable customization, speed the process and ensure data integritysimplify-

ing the technology refresh process.


Page 2


3/28

The following table presents ve key factors that show how data migration

software can simplify technology refresh and how Softek Transparent Data

Migration Facility (TDMF) technology can meet these needs.

Key factors Description Softek TDMF capability

Performance Performance measurements

must take into consideration

how quickly data is copied

from the source to target,and balanced against

network bandwidth and

system overhead.

TDMF software includes a throttling

or pacing capability that can speed

up or slow down data movement

depending on system demands inorder to easily balance migration.

Roll-back capability If something goes wrong, the

migration can be terminated

and restarted or application

processing can continue on

the source data/device.

Roll back can easily be accom-

plished with TDMF software,

although it can be problematic

with some other technologies,

such as volume managers.

Increase in

volume size

In a recent survey, 40 per-

cent of migrations involved

an increase in volume size

from the source to the target.

TDMF software can accommo-

date an increase in volume size.

Heterogeneoussource and

target hardware

While host-based prod-ucts support unlike storage

devices, most array-based

products require that the

source and target come

from the same vendor.

TDMF software is hardwareindependent.

Application downtime Applications have different

levels of business criticality

and therefore have varying

degrees of acceptable

downtime.

TDMF software allows for

nondisruptive data migration so

applications can stay online

and continue to process data

throughout the migration process.


Page 3

Technology refresh is the primary

driver of data migration.

Highlights


4/28


Page 4

Introduction

What drives data migration? In a recent Softek survey, technology refresh was

cited as the major reason for moving data. Technology refresh is dened as

replacing an array with a new one and most commonly occurs when:

Theleaseonapieceofstorageequipmentends

Dataisbeingmovedfromoldtonewstorage

Thestoragesystemisbeingupgraded Theorganizationhasdecidedtostandardizeonaparticulartechnology.

Typically, most data centers lease their storage hardware under three-year agree-

ments. Once the agreement ends, the hardware needs to be replaced and the data

stored on it moved to new equipment. Data migration must be completed befor

the lease expires to avoid additional monthly lease costs. In cases in which storag

hardware is purchased rather than leased, older arrays that are fully depreciate

can be expensive to maintain. Once again, purchase and implementation of new

equipment requires migrating data from the older arrays.

IT organizations justify purchase or lease of new equipment by the fact thatit is less expensive to maintain, performs better and supports advanced fea-

tures. New arrays can support larger capacities to accommodate the growth

of applications; have faster processing chips to deliver better performance; or

have new features such as snapshot copies. Finally, newer arrays are justied

to minimize the risk of hardware malfunction, as older arrays are perceived

as being less reliable.

Highlights

IT organizations justify new equip-

ment because it can accommodate

growth, process more quickly to

deliver better performance and

minimize the risk of hardware

malfunction.


5/28


Page 5

Figure 1

Example annual migration requirements

Highlights

For most industries, estimates of

data growth can typically range

from 25 to 50 percent annually.

In many cases, technology refresh not only means replacing storage arrays,

but also upgrading associated servers to better meet service level agreements

or because the servers, like the arrays, have reached the end of their lease. In

addition, storage and server capacity are acquired annually or more often to

accommodate data and application growth. Estimates of data growth vary, bu

they typically range from 25 to 50 percent annually for most industries.

So, every year, a typical organization acquires storage technology to replacearrays on which lease or maintenance agreements are expiring, as well as addi-

tional capacity to accommodate anticipated growth. Thus, the IT organization

must move data between servers and storage for technology refresh on a very

regular basis. The storage mantra is: You have data, therefore you will move it.

Total on Floor (TB)

New (TB)

Replaced (TB)

Purchased (TB)

2005

300

70

115

45

2006

390

90

150

60

2007

507

117

194

77

2008

659

152

267

115

2002

136

31

45

14

2003

177

41

60

19

2004

230

53

77

24


6/28


Page 6

IT organizations face many challenges associated with technology refresh

particularly deciding how to deal with data growth and determining how,

when and where to move data. Some of the key issues associated with technol-

ogy refresh include:

Leaseoverlapcostsorduplicatemaintenancecosts,whenoldandnew

equipmentareonthedatacenterooratthesametime

Migrationofdatabetweenarraysfromdifferentvendors,astheremaybesignicantincompatibilities

Riskofdatalossorcorruptionthatmayoccurifthemigrationisnot

doneproperly

Prolongedapplicationdowntime,orevenaninabilitytorestartapplications.

This paper focuses on how organizations can meet these challenges by leveraging

data migration software.

Data migration software

Depending on the criticality of applications, the quantity of data to be moved

and allowable downtime, there are a variety of tools that organizations can useto migrate data, each with its own considerations and limitations.

Ofine migration methods

Ofine migration methods require that applications be taken ofine during

data movement, and therefore are suitable only when signicant downtime can

be tolerated. While the amount of downtime required typically depends on the

quantity of data being transferred, this ofine migration mechanism is not rec-

ommended for heavily used applications or those that must be accessible outside

of normal business hours. Ofine migration typically requires manual manipu-

lation of data or les, which can increase the risk of human error and may notscale to distributed or remote scenarios.

Highlights

Organizations can meet these chal-

lenges by leveraging various types

of data migration software.

It is an ongoing challenge to decide

how to deal with data growth and to

determine how, when and where to

move data.


7/28

Restore from backup tapes

This method involves making a backup copy of data, then taking the associated

arrays and/or servers ofine to ensure that no new data is added. Then, the dat

is restored from the backup tapes to the new arrays and/or servers. Once th

restore process is complete, the systems are brought online. While this is a low

cost solution, especially as nearly all organizations already use backup software

it requires signicant administrative attention and application downtime.

FTP transfer

This method involves manually copying les from the source systems to the targe

systems via File Transfer Protocol (FTP). As it requires le-by-le movement, th

method is not recommended when the data contains large numbers of individua

les. FTP transfer does not provide control over the network bandwidth used for

migration, which can affect other applications and users in the network environ

ment, nor does it enable verication of the complete transfer of data.

Online migration methods

Online migration methods generally allow data movement while applications

are up and running. Depending on the method chosen, however, these methods

can be l imited to a single vendor environment. Other methods may consume

signicant central processing unity (CPU) overhead, potentially resulting in

application slowdown or other disruptions.

Array-based replication

While this method allows for high service level guarantees, it requires moving

between similar storage devices, increasing costs and limiting the data center

to a single vendor.


Page 7

Highlights

Offline migration methods include

restore from backup tapes and

FTP transfer.

Online migration methods include

array-based replication, volume

management or replication, and

host-based mirroring.


8/28

Volume management or replication

Volume management is used primarily to control disk resources by mappin

the logical view of storage space with the actual physical disks. While it can

be used to move small amounts of data , it can be slow. This solution require

a heterogeneous storage environment over an IP network and may require th

costly instal lation of additional software.

Host-based mirroringHost-based mirroring or replication solutions generally focus on le-by-le

data movement to create a secondary data copy for disaster recovery purpose

When used for data migration, this approach may put an additional burden o

application servers and may require high-cost management, especially in het-

erogeneous environments.

Online nondisruptive migration Sotek data migration products

There are a few products available in the marketplace today that were designed

to provide nondisruptive data migrationmeaning that data movement occurs

without causing application outages or slowdowns. Softeks data migration soft-

ware is the proven standard for online, heterogeneous data movement, meeting

the challenges of application availability and technical compatibility between

source and target storage. Softeks TDMF software moves data while maintain-

ing application availability, making it easy to upgrade to new storage, improve

application performance and manage information availability through the

information lifecycle. So, whether the organization needs to upgrade to new

storage hardware (from any vendor to any vendor) or needs a more effective

way to migrate data based on cost/performance, TDMF software can provide


Page 8

Highlights

Softeks TDMF software makes it

easier to upgrade to new storage,

improve application performance

and manage information availability

through the information lifecycle.


9/28

the solution. Together with Softek Logical Data Migration Facility (LDMF)

software for moving mainframe data at the dataset level, Softek TDMF tech-

nology provides the solution to meet a wide range of technology refresh and

other data migration needs.

An examination of real-world scenarios can demonstrate how Softek s data

migration products are used to simplify technology refresh:

Amanufacturingcompanyrunningamission-criticalOraclecustomer

orderandtrackingsystemonSolarisconductinglocalUNIXarray-to-

arraymigration.

Alargebankrunningacreditanddebittransactionapplicationon

IBMz/OSconductinglocalmainframearray-to-arraymigration.

AmajorsavingsandloaninstitutionrunninganIBMDB2,IBMCICSand

VirtualStorageAccessMethod(VSAM)applicationwithhigh-availability

requirementsconductingmainframemigrationwithvolumeconsolidation.

AFortune500nancialservicesrmrunningamission-criticalDB2

datawarehouseconductingmultiserverUNIXarray-to-arraymigration

withconsolidation.

AFortune1000bankrunningaSybasenancialapplicationconducting

aglobalmigrationtonewstorageoverdistance.

Aninsurancecompanywithamission-criticalclaimsprocessingapplication

onOracleconductingaglobalmigrationtonewserversandnewstorage.

AFortune500bankrunningakeyenterprisecompliancemanagement

applicationconductingalocalMicrosoftWindowsarray-to-arraymigration.

The detailed descr iptions of these scenarios that follow show how Softek

capabilities can meet technology refresh needs and streamline technology

refresh projects.


Page 9

Softeks software capabilities

can meet technology refresh

needs and streamline technologyrefresh projects.

Highlights

A discussion of real-world imple-

mentations can illustrate how

Softek technology simplifies tech-nology refresh.


10/28

Technology refresh examples

Local UNIX array-to-array migration

In this example, a manufacturing company running a mission-critical Oracle

customer order and tracking system on Solaris needed to move 3TB of legacy

data from an old storage array to a new storage array.

The challenges that the company faced were as follows:

LimiteddowntimeDowntimewaslimitedtofourhoursontheweekend.

LargevolumeofdataApplicationstoragespannedten300GBvolumes.

IncreaseinvolumesizeTheplannedcapacitygrowthrequiredanincrease

involumesizeduringmigration.

The company considered the pros and cons of several different migration

options, including:

Restorefrombackuptapes Thisoptionwouldhaverequiredmorethan

fourhourstocopythedata,exceedingapplicationdowntimerestrictions.

SunSolsticeVolumeManagerThiswouldnotsupporttheincreaseinvolumesize.

Array-basedreplicationThisoptionwouldhavebeenexpensivetoinstall,

andthecompanydidnotplantouseitfollowingthemigration.Inaddition,

rmwareupgradesrequiredonthelegacyarraystosupportthecurrent

array-basedreplicationversionwouldhaveaddeddowntimeandcomplex-

itytotheproject.

VERITASVolumeReplicator(VVR)Thisoptionwouldhaverequired

installingtheprerequisiteVERITASVolumeManager.


Page 10

Highlights

In the first example, Softek software

helped a manufacturing company

move 3TB of legacy data from an

old storage array to a new one,

without significant downtime.


11/28

Softek TDMF technology was chosen because the asynchronous, host-based

migration was cost-effective, able to work with disparate platforms, did not requi

changes to the source environment and could accommodate the increased volum

size in the target environment. The benets of the TDMF solution were that the

Oracle applications storage volumes were augmented, enabling continued expan-

sion of capacity. In addition, the migration was completed without signican

downtime to this mission-critical application. Most important, the storage techno

ogy upgrade was transparent to the applications end users.

Softek solution: Local UNIX array-to-array migration with Softek

TDMF solution

1.SoftekTDMFtechnologywasinstalledonthehostpriortotheweeklysched-

uleddowntimeandconguredtomapthesourceandtargetdevices.Ascript

waswrittentounmountandremountthesourcedevicesduringtheweekend

outage.Thescriptwasrunjustaftertheweeklybackupsandtooklessthan

30secondstorun,sothescheduleddowntimewasnotaffected.

2.TheTDMFsolutionstartedthecopyoperationonceapplicationsareback

online.Copyranslowlyinbackgroundsoasnottosignicantlyaffectthe

operationoftheapplication.

3.Allvolumesweresynchronizedwithin48hours.

4.Switchoverwasperformedwithoutserviceoutage.Oldvolumeswereleftin

placewhileperformanceofnewvolumeswasvalidated.


Page 11

Highlights

Most important, the storage tech-

nology upgrade was transparent

to users.


12/28

Figure 2

Local UNIX array-to-array migration


Page 12

Highlights

A financial institution cannot afford

downtime when moving from legacy

storage to newer storage arrays.

5.Oldvolumeswereremovedfromconguration.

6.TDMFsoftwarewasleftonthesystemandusedtomovetwovolumesnon-

disruptivelywithinthenewstoragearraytoresolveperformanceproblems

causedbypathingissuesinthenewhardware.

Solaris Server runningOracle application

New Arrays installedOlder arrays installed48 hours

15 minutesdowntime

4

2

1

15 minutesdowntime

Legacy

1

5

3

6

TDMF

Local mainrame array-to-array migration

In this scenario, a large Canadian bank running a credit and debit transaction

application on the IBM z/OS platform was moving from legacy storage to

newer storage arrays.

The challenges the bank faced included the following:

NoapplicationdowntimeallowedTheapplicationwasakeyrevenuedriverequiring24x7access.Theprojected18hoursofdowntimetoinstallandcon-

gurenewarraysandcompletemigrationwouldviolatecorporateITpolicy

andcostthousandsofdollarsinlostrevenue.


13/28

LargenumberofvolumesFourhundredvolumeshadtobemovedfromthe

oldtonewstoragearray.

BudgetconstraintsThemigrationbudgetdidnotincludetheanticipated

needforoutsideconsultingresourceswithmigrationexpertise.

In this case, Softek TDMF technology was the only option considered, because

no other solution could accomplish the migration without requiring downtime.

Using Softeks solution, the bank s migration project was completed on schedul

and required no outside resources so the budget was not affected. And becau

no application performance impact or outages were experienced, the bank coul

continue to generate revenue during the migration.

Softek solution: local mainframe array-to-array migration

1.SoftekTDMFsoftwarewasinstallednondisruptivelyonthehost.

2.Storageadministrators,withoutformaltraining,usedexamplesinSofteks

manualtoperformTDMFinitialization,activationandcopytasks.

3.Intherstweek,administratorsmigrated50percentofvolumestotargetstoragearrayswithnoperformancedegradation.Migrationtookplace

duringpeakperiodsofactivitybecauseTDMFsoftwarehasadynamic

throttlingcapabilitythatspeedsuporslowsdownmigrationasapplica-

tionrequirementschange.

4.Refresheswereperformedperiodicallysothatupdatesmadetosource

volumeduringthecopyphaseweremadetotargetvolume,ensuring

synchronizationbetweensourceandtarget.


Page 13

Highlights

In the case of a large bank migrat-

ing to new storage arrays, Softek

TDMF was the only option consid-ered because no other solution

could perform the migration with-

out requiring downtime.


14/28

5.Administratorsmigratedthenal50percentofvolumesoverthesecond

week,withstillnoapplicationimpact.

6.Whennalsynchronizationhadtakenplace,TDMFsoftwarecompletedthe

swapoperationtoredirectthemainframeI/Ototargetvolumes,whichbecam

primaryvolumes.Switchoverwasperformedwithoutserviceoutage.

7.Backoutoptionwasavailableincaseafailureoccursduringanyphase.If

needed,originalsourcevolumecontainedallthewriteoperationsperformed

duringthemigration.8.Oldvolumeswereremovedfromconguration.

JANUARY

F

1

8

15

22

29

S

2

9

16

23

30

W

6

13

20

27

T

5

12

19

26

M

4

11

18

25

S

3

10

17

24

T

7

14

21

28

JANUARY

F

1

8

15

22

29

S

2

9

16

23

30

W

6

13

20

27

T

5

12

19

26

M

4

11

18

25

S

3

10

17

24

T

7

14

21

28

Credit and debittransaction application

IBM mainframe

New storage arrayOld storage array

1

2

3

7

48

6

5

TDMF

Figure 3Local mainframe array-to-array migration


Page 14

Highlights

This chart depicts the banks local

mainframe array-to-array migration.


15/28


Page 15

Local mainrame migration with volume consolidation

A major savings and loan inst itution had an older local ly attached storage

array under strain that it was replacing with a new locally attached storage

array. The institution was running DB2 and CICS VSAM applications with

very high availability requirements.

The key migration challenges were as follows:

ConvertingdatabetweenvolumesizesTheprojectrequiredmovingMOD3

arraysontoMOD3s,andMOD3arraysontoMOD9satbothvolumeand

datasetlevels

LimiteddowntimeTheonlypermittedsystemdowntimewasSundaymorning

PersonnelconstraintsTherewerelimitedpersonnelavailabletoperform

themigration.

ComplexprojectDuetothecomplexityofthemigrationandthepersonnel

constraints,theestimateddurationoftheprojectwasatleasttwoweeks.

The savings and loan company evaluated several migration options:

Manualmethods Thisoptionwasconsideredtoolaborintensive,especially

withtheoverworkedandunderstaffedcustomerresourcebase.Avoiding

bandwidthimpactsalsowouldbedifcult.

Array-basedreplicationThisoptioncouldnotbeusedastheproject

involvedmigratingMOD3stoMOD9s.

Highlights

A savings and loan company faced

migration challenges such as

personnel constraints and strict

availability requirements.


16/28

A combination of Softeks TDMF and LDMF software was chosen because of the

products ability to migrate data nondisruptively, handle the resizing of MODs,

and move specic data at the dataset level. With the LDMF/TDMF combination,

the project was completed ahead of schedule (60 hours estimated, 55 hours

actual), with data migration constituting 38 hours of the total time. This was

considerably shorter than anticipated, and the migration was performed while

the mainframe was in production, with no impact to end users.

Softek solution: Local mainframe migration with volume consolidation

1.TDMFandLDMFsoftwarewasnondisruptivelyinstalledonIBMZ800

mainframeandveriedbytheimplementationteam.

2.TheteammappedsourceandtargetvolumemigrationforTDMFmigration.

Aspartoftheprocess,TDMFsoftwarewasusedtomigrateasinglesource

MOD3toaMOD9,therebyestablishingthetargetMOD9intotheexist ing

storagemanagementsubsystem(SMS)environmentandeliminatingany

SMSsetuprequirementsforthenewMOD9volumes.

3.TheteammappedtheremainingMOD3toMOD9migration,whichwas

accomplishedusingLDMFsoftware.Themappingdocumentedthetarget-

volumeSMSstoragegroupsandstorageclass.Thisalsoidentiedany

volumesthatwerenotunderSMScontrol.

4.TDMFmigrationwasinitiated.Overthecourseoftenhours(including

verication),theimplementationteammigrated200MOD3to200MOD3

and240MOD3to240MOD9.Thisentiremigrationwascompletedtrans-

parentlyduringproductionhours.

5.TheimplementationteamsetupLDMFmigrationbybuildingsourceand

targetdatasetmigrationgroups(460sourcevolumesgoingto240target

volumesatthedatasetlevel).


Page 16

After evaluating several migra-

tion methods, a savings and loan

company chose Softeks TDMF and

LDMF software due to their ability

to migrate data nondisruptively,resize MODs and move specific

data at the dataset level.

Highlights


17/28

6.LDMFmigrationwasexecutedovera28-hourperiod(submissionofgroup

migrations,monitoringprogressandvericationresults)andnoapplication

impactwasreportedduringthisperiod.

7.Scheduledoff-hoursbounceofalldatabaseapplicationstookplaceafter

migration,andthetotaldurationoftheoutageforallapplicationswas

lessthanonehour.

Figure 4

Local array-to-array migration with consolidation

TDMF

LDMF

New arrays

2

2

1

7

55

4

4

6

Older arrays

240 MOD3 to 240 MOD9

240 MOD3 to 240 MOD9

460 source volumes to 240target volumes at dataset level

DB2 and CICS VSAMapplications

IBM Z800

3

2


Page 17

Highlights

This chart depicts the array-to-array

migration with consolidation enabled

by the Softek software.


18/28

Multiserver UNIX array-to-array migration with consolidation

A Fortune 500 nancial services rm had a mission-critical DB2 data ware-

house (24TB DB2, 10TB supporting les) on seven IBM AIX 5.1 server

platforms with the storage allocated to nine different storage arrays, some

more than ve years old.

The rm faced these key migration challenges:

Storagegrowth Storagecapacitygrewfrom4TBto30TBinthreeyears,

withstorageaddedinademand-driven,ratherthanaplanned,fashion.

LocatingstorageStorageadministratorswereunabletopreciselylocate

storage.

ComplexenvironmentThesystemcouldbeupgradedorchangedonlywith

difculty,resultinginnumerousendusercomplaintsaboutsystemperformance

RelocatingdataAnewstoragearraywaspurchasedtoimproveperformanc

bymigratingandreconguringvolumes.

Source/targetincompatibilitiesThermwasunabletoperformmigration

duetothecomplexityoftheenvironment;thiscreatedincompatibilities

betweenthesourceandtargetstoragearrays,sothenewarraysatunused

fortwomonthsonthedatacenteroor.

The rm evaluated several different migration options:

Ofinebackupandrestorefromtape Thisoptionwasrejecteddueto

timeconstraints.

Operatingsystem(OS)synchronizationtools Thisoptionwasrejected

duetotheinabilitytocontrolmigrationstart/endtimes.

Array-basedreplicationThiswasnotanoptionbecauseoftheincompat

ibilitiesbetweensourceandtargetstorage. AIXserver-nativeLogicalVolumeManagermirroring Thiswasrejecteda

VolumeManagerwastooslowandwasnotconguredformirroring.


Page 18

Highlights

A financial services firm struggled

with excessive storage growth andother related challenges.


19/28

Softeks TDMF UNIX (IP) software was chosen based on its ability to migrate

between disparate platforms and its exibility in working with various logical

denitions. The benet of the TDMF solution is that the data migration could

be performed in a challenging environment well within scheduled windows.

The rm was nally able to take advantage of its new hardware, which enabled

it to run queries four t imes more quickly with the new array, improve data

layout, and greatly simplify administration. Most important, end user complaints

about performance were eliminated almost entirely. In addition, the rm wasno longer paying lease charges for unused or outdated hardware. Softek s

implementation methodology ensured that there were no manual errors and the

onsite resources were used efciently.

Softek solution: multiserver UNIX array-to-array migration with

consolidation

1.Inthepremigrationstage,Softekworkedwiththestoragevendortoperform

comprehensivetestingandproofofconcepttoprovetheviabilityofthemigra

tionstrategy.Thermelectedtoperformmigrationoverscheduledweekend

downtime,withanestimated24hoursfortotalmigration.

2.Inthemigrationstage,themigrationteamwasgiventhesystemat8p.m

onSaturdaynight;itinstalledTDMFsoftwareonsevenAIXhostsinless

than15minutes.

3.Themigrationprocesswasinitiatedwithmigrationcongurationinloop-

back.Theactualmigrationstartedat12a.m.andendedat4a.m.,moving

22TBofdatainfourhours.

4.Aspartofthemigrationprocess,theimplementationteamresizedphysical

partitionsonvolumegroups,improvedthelayoutofthevolumesonthenew

array,andresizedtheIBMJournaledFileSystem(JFS)logs.

5.Thesystemwashandedbackat3p.m.onSunday,wellaheadofschedule,forpreliminarytesting.TheDB2datawarehousestartedcorrectlyandthe

vericationscriptlaunched.


Page 19

Highlights

Softeks implementation meth-

odology ensured that there were

no manual errors and the onsite

resources were used efficiently.

A Fortune 500 financial services

firm chose TDMF UNIX (IP) software

for its migration based on its ability

to migrate between disparate plat-

forms and its flexibility in workingwith various logical definitions.


20/28


Page 20

6.Thermperformedextensivetesting,andattheendofthescheduled

applicationstoppage,thesystemwentintofullproduction.

7.Atthenextscheduleddowntime,theoldsourcearraysweretakenoutof

serviceandsentbacktotheleaseholder.

TDMF

TDMF

TDMF

TDMF

TDMF

TDMF

TDMF

New array

Old arrays

2

7

DB2 data warehouse

AIX 5.1 servers

4 hours22 TB

5

6

3 4

DS1

DS2

DS3

DS4

DS5

DS6

DS7

DS8

DS9

DS10

DS11

DS12

1

Global migration to new storage over distance

A Fortune 1000 bank running a Sybase nancial applicat ion was relocating

four servers from a New Jersey operations center to a New York City opera-

tions center, changing out the legacy storage arrays to newer arrays.

The banks key migration challenges were as follows:

IncreasedstoragedemandsandinternalconsolidationThesefactors

drovethetechnologyrefresh.

Figure 5

Multiserver migration with consolidation

Highlights

A bank needed help relocating

four servers to another state.


21/28

ExpirationofstorageleaseTheNewJerseystorageneededtobereturned

totheleaseholder.

HardwaremovePhysicalservershadtobemovedviacourier.

DatamoveoverdistanceDatahadtobemovedfromtheNewJersey

storageareanetwork(SAN)totheNewYorkCitySAN.

LimiteddowntimeTheonlyallowableoutagewasfromFridaynight

toSaturdaymorning.

The bank reviewed several migration options:

OfinemigrationRestorefromtapeafterphysicallymovingtheservers

waspossiblebutwouldhaverequiredcompleteshutdownofapplication

serversovera48-hourperiod.Availabilityrequirementsmadethisoption

impossible.

FTPtransfer Thelackofbandwidthcontrol,inabilitytoverifythe

completetransferofdataandtherequirementforle-by-lemovement

promptedtherejectionofthisoption.

VERITASVolumeReplicator Thisoptionrequiredtheinstallationof

VERITASVolumeManageronthesourceandtargetmachines.

Hardware-basedmirroring Thisoptionwasnotpossiblebecausethe

sourceandtargetarraysweredissimilar.

Softeks TDMF UNIX (IP) software was chosen for its ability to work

with multiple operating systems and perform fast, controllable transfers.

The migration allowed the bank to realize economies of scale and increase

administrative control. In addition, the increased storage capacity allowed the

bank to more fully utilize the Sybase application in support of key operations.

Softek solution: global migration to new storage over distance

1.Inthetargetenvironment,allnewstoragewasdened,withthebankopting

touseswingservertoperformthemigration.DatafortheNewJerseyservers

wasallocatedtotheswingserver,whichservedasaproxyduringthemigratio


Page 21

Highlights

A Fortune 1000 bank chose Softeks

TDMF UNIX (IP) software for its

migration based on its ability to

work with multiple operating sys-

tems and perform fast transfers.


22/28


Page 22

Figure 6

Global migration to new storage over distance

Highlights

The Softek solution enabled a rapid,

security-rich migration from the

source to the target.

2.At5p.m.onFriday,theapplicationsweretakenofineandTDMFwas

installedontheNewJerseyservers.

3.Migrationwassetupfromthefourserverstoonetargetandwasinitiated.

Thecomplete,fullrefreshtooktwohoursandinvolvedmoving2.2TBover

thebankswideareanetwork(WAN).Uponcompletion,theTDMFsolution

maintainedsynchronizationbetweensourceandtargetenvironment.

4.Themigrationwascompletedandvericationtestingwasperformedondata

5.TheNewJerseyserverswereshutdown,physicallymovedtoNewYorkCityandinstalledatthebankssite.

6.Inthetargetenvironment,thestoragewasrezonedfromtheswingserverto

therelocatedservers.

7.Theserverswerebroughtupandtested,andapplicationswerebroughtup

andtested.At6a.m.Saturday,theapplicationwasputbackintoproduction

8.Atthenextscheduledoutage,theNewJerseystoragearraywastaken

ofineandremovedforreturntoleaseholder.

2

1

Sybase applications

Target environment

SwingServer

3

5

6

4

New arrayOlder array

New YorkNew Jersey

8

72

WAN

1

TDMF


23/28

Global migration to new servers and new storage

An insurance company was running a mission-critical claims processing appli-

cation on Oracle. It was upgrading from legacy servers running Solaris 8 and

VERITAS Filesystem/Solstice Disksuite to new servers running Solaris 9 and

VERITAS Volume Manager. Six TB (allocated 2TB per server) on an older disk

array were being replaced by a new array.

The insurance company faced these key migration challenges:

LimiteddowntimeOnlyfourhoursdowntimeperweekwerepermitted

foranyapplication.

HardwaremoveconstraintsOnlyoneservercouldbemovedatatime

toavoidrisktotheapplicationinfrastructure.

CompatibilityofnewstoragewithlegacyserversTherewereinsufcient

connectionsavailabletodirectlyattachnewstoragetolegacyservers,

anditwasriskytoinstallnewdevicedriversonlegacyservers.

The migration options that were considered included the following:

OfinemigrationThiswouldhaveresultedinmultipledowntime

instances,eachexceeding12hours.

Array-basedreplicationThisoptioncouldnotbeusedduetodissimilar

legacyandtargetstorage,andbecausedisksubsystemswereincompatible.

VERITASVolumeReplicatorThisoptionwouldhaverequiredtheinstallatio

ofVERITASVolumeManageronsourceservers.

Fabric-basedappliancereplication Thiswasrejectedbecauseoftheriskof

reconguringtheSAN.

KashyaThiswasrejectedduetotherequirementthatmirrorsbesetup

andcreatedonthehostsystem.Suchanarrangementwasunacceptablegiventhechangesinvolvedandtheassociateddisruption.


Page 23

Highlights

An insurance company needed

help to maintain availability while

migrating a mission-critical claims

processing application.


24/28

Softeks TDMF UNIX (IP) software was chosen as the least risky option because

no system reboots were required. The migration was performed without requir

ing a reboot of any critical service, continuous application availability was

maintained during data migration, and the migration was performed without

end users experiencing any loss or signicant degradation in service.

Softek solution: global migration to new servers and new storage

1.Intheinitialphase,congurationswerepre-createdanduser-customizable

scriptswerewrittentounmount,replacethevfstable,andremountlesystems.

2.TDMFsoftwarewasinstalledjustpriortoweeklyshutdownwithnodis-

ruption.Eachserverisconguredinturn,withatotalelapsedtimeof15

minutesforTDMFinstallationandconguration.

3.AfullrefreshfromsourceserverAtotargetserverAwasconductedover

thecourseofaweek.Bigasynchronousbuffer(BAB)absorbedpeaksin

writeactivityonlegacyserverstominimizeCPUusageandpreventhigh

I/Oload.

4.NewversionsofOracleandothersoftwarepreinstalledontargetserverA

weretested.Testinginvolvedreceivingmultipleapplication-consistentver-

sionsofproductiondisksonadailybasis.Toavoidhavingtorefreshfrom

theproductiondiskseverytime,checkpointandachainingconguration

wereused.

5.Atthecompletionofthetesting,journalwrotetotargetvolumestoensure

minimaldatatransferonresynchronization.

6.Duringthenextweekendsoutage,applicationsontargetserverAwere

broughtupandpointedtothenewstoragevolumes.SourceserverAwas

takenoutofservice.


Page 24

Highlights

Not only did the migration not

require a reboot of any critical

service, but it also provided con-

tinuous application availability

and no loss or degradation of ser-

vice for end users.

An insurance company chose

Softeks TDMF UNIX (IP) software

because it was the least risky

option, requiring no reboots.


25/28


Page 25

Figure 7

Global migration to new servers and storage

7.TheprocesswasrepeatedforsourceserversBandCoverthenexttwoweeks.

8.Duringthenextscheduledoutage,theolderstoragearraywastaken

outofservice.

Oracle applications

Targetenvironment

Sourceenvironment

SourceServer C

SourceServer B

Checkpoint

Source

Server A

TargetServer A

3

4

New arraysOld array

TDMF

TDMF

TDMF

2

2

1

1

A

B

C

6

6

4

34

77

7

7

Journal

checkpoint

area

5

8

BAB

Highlights

This chart shows how the insur-

ance companys global migrationwas executed.

Local Windows array-to-array migration

A Fortune 500 bank had 5.8TB of data on two servers for a key enterprisecompliance management application based on Microsoft SQL. The bank

wanted to move from an older locally attached storage array to a new locally

attached storage array.


26/28

The key migration challenges were as follows:

AddingnewstorageThegoalwastofreeupexistingstorageandimplemen

newfaster,cheaperstorage.

LimiteddowntimeTheapplicationhadalimiteddowntimewindowfrom

12a.m.to6a.m.Saturdaymorningandfrom12a.m.to2a.m.Tuesday

morningbutitwasestimatedthatthefullmigrationwouldtakeaweek.

RecongurationofalargenumberofvolumesTherewere30volumestobemoved,creatingpotentialcongurationissues.

The bank considered these options:

RestorefromtapebackupsThiswasnotpossibleduetoapplicationavail-

abilityrequirements.

EMCOpenMigratorThiswasinitiallyselectedbutfailedduringanearly

migrationtest.

File-levelmigration/replication Thiswasconsideredbutfoundtobetoo

expensiveanddifculttocongureforuserslackingexpert-levelimplemen

tationexperience.

Softeks TDMF Windows (IP) software was chosen because of its ease of

use, price and ability to maintain continuous application availability durin

data migration.

Softek solution: local Windows array-to-array migration

1.DuringscheduledSaturdaydowntime,SoftekTDMFsoftwarewasinstalled

ontheproductionserver.Targetvolumeswereconnectedtothevolume/disk

managerandthesystemwasrebootedtoallocatetheBABbuffer(RAM)

andregistertargetvolumeatvolume/diskmanager.Installationtooktenminutesperserver.Applicationwasrestartedattheendofscheduleddowntim


Page 26

Highlights

A Fortune 500 bank chose Softeks

TDMF Windows (IP) software for

its ease of use, price and ability to

maintain continuous application

availability during data migration.


27/28

2.Migrationgroupswereconguredonsourceandtargetbytheimplementatio

team.Theteam,withoffsiteSofteksupport,createdmountpointstoresolve

issuesrelatedtoinsufcientdriveletterscausedbythenumberofvolumes

tobemigrated.

3.TDMFfullrefreshwasinitiatedinloopbackconguration.Fullrefresh

tookapproximately24hoursandwasperformedonlinewithoutanyappli-

cationimpact.

4.WithTDMFoperationinnormalmode,theteamvalidatedthedatamigratedtothenewstoragearraybyusingTDMFsoftwarescheckpointfunction.

5.DuringTuesdaydowntime,theapplicationwasstoppedandsourcevolumes

wereremoved.Thetargetvolumeswererenamed,andtheapplicationwas

placedbackintoproductionusingnewarrays.

6.Oldarraysweredecommissioned.


Page 27

Figure 8

Local Windows array-to-array migration

New arraysOld arrays

Production server

1

8

TDMF

55

BAB

33

4

Checkpoint

24 hours24 hours

2

2 2

Highlights

The local Windows array-to-array

migration was a success.


28/28

Summary

For the IT manager, technology refresh is regular, continuous and problematic,

unless data migration software is used to simplify and streamline the process.

The scenarios presented in this paper demonstrate how Softeks data migrationsoftware can be leveraged to streamline technology refresh projects. Above and

beyond what most other products offer, Softeks data migration software provides

nondisruptive, exible and purpose-built solutions to the complex challenges of

technology refresh.

With Softek solutions, applications remain online and continue to process data

throughout the migration process. Softeks TDMF software is completely hard-

ware independent, accommodates increases in volume size, adjusts to system

demands and has roll-back capability.

For more information

For more information about Softek solutions for technology refresh, visit:

ibm.com/services/storage

Copyright IBM Corporation 2007

IBM Global Services

Route 100

Somers, NY 10589

U.S.A.

Produced in the United States of America

12-07

All Rights Reserved

IBM, the IBM logo, AIX, CICS, DB2, LDMF, Softek,

TDMF and z/OS are trademarks or registered

trademarks of International Business Machines

Corporation and other companies in the United

States, other countries, or both.

Microsoft and Windows are trademarks of

Microsoft Corporation in the United States, other

countries, or both.

UNIX is a registered trademark of The Open

Group in the United States and other countries.

Other company, product and service names

may be trademarks or service marks of others.

References in this publication to IBM products

or services do not imply that IBM intends to

make them available in all countries in which

IBM operates.

Storagemigrationmadesimple Wp Gtw01274 Usen 01 121307

Documents

Transcript of Storagemigrationmadesimple Wp Gtw01274 Usen 01 121307