background image

Multiserver UNIX array-to-array migration with consolidation

A Fortune 500 financial services firm had a mission-critical DB2 data ware-
house (24TB DB2, 10TB supporting files) on seven IBM AIX

®

 5.1 server 

platforms with the storage allocated to nine different storage arrays, some 
more than five years old.

The firm faced these key migration challenges:

•  Storage growth — Storage capacity grew from 4TB to 30TB in three years, 

with storage added in a demand-driven, rather than a planned, fashion.

•  Locating storage — Storage administrators were unable to precisely locate 

storage.

•  Complex environment — The system could be upgraded or changed only with 

difficulty, resulting in numerous end user complaints about system performance.

•  Relocating data—A new storage array was purchased to improve performance 

by migrating and reconfiguring volumes.

•  Source/target incompatibilities—The firm was unable to perform migration 

due to the complexity of the environment; this created incompatibilities 
between the source and target storage arrays, so the new array sat unused 
for two months on the data center floor.

The firm evaluated several different migration options:

•  Offline backup and restore from tape — This option was rejected due to  

time constraints.

•  Operating system (OS) synchronization tools — This option was rejected  

due to the inability to control migration start/end times.

•  Array-based replication — This was not an option because of the incompat-

ibilities between source and target storage.

•  AIX server-native Logical Volume Manager mirroring — This was rejected as 

Volume Manager was too slow and was not configured for mirroring.

Storage migrations made simple.

Page 18

Highlights

A financial services firm struggled 
with excessive storage growth and 
other related challenges.

Summary of Contents for DATA MIGRATION SERVICES -

Page 1: ...IBM Global Technology Services December 2007 Storage migrations made simple Overcoming the challenges of technology refresh...

Page 2: ...basis Moving data for tech nology refresh can be problematic however due to application availability requirements incompatibilities between source and target systems and time and budget constraints Wh...

Page 3: ...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 m...

Page 4: ...ditional monthly lease costs In cases in which storage hardware is purchased rather than leased older arrays that are fully depreciated can be expensive to maintain Once again purchase and implementat...

Page 5: ...odate data and application growth Estimates of data growth vary but they typically range from 25 to 50 percent annually for most industries So every year a typical organization acquires storage techno...

Page 6: ...f applications the quantity of data to be moved and allowable downtime there are a variety of tools that organizations can use to migrate data each with its own considerations and limitations Offline...

Page 7: ...l over the network bandwidth used for migration which can affect other applications and users in the network environ ment nor does it enable verification of the complete transfer of data Online migrat...

Page 8: ...ailable in the marketplace today that were designed to provide nondisruptive data migration meaning that data movement occurs without causing application outages or slowdowns Softek s data migration s...

Page 9: ...e migration with volume consolidation A Fortune 500 financial services firm running a mission critical DB2 data warehouse conducting multiserver UNIX array to array migration with consolidation A Fort...

Page 10: ...Restore from backup tapes This option would have required more than four hours to copy the data exceeding application downtime restrictions Sun Solstice Volume Manager This would not support the incre...

Page 11: ...Softek TDMF solution 1 Softek TDMF technology was installed on the host prior to the weekly sched uled downtime and configured to map the source and target devices A script was written to unmount and...

Page 12: ...application New Arrays installed Older arrays installed 48 hours 15 minutes downtime 4 2 1 15 minutes downtime Legacy 1 5 3 6 TDMF Local mainframe array to array migration In this scenario a large Can...

Page 13: ...oftek TDMF software was installed nondisruptively on the host 2 Storage administrators without formal training used examples in Softek s manual to perform TDMF initialization activation and copy tasks...

Page 14: ...source volume contained all the write operations performed during the migration 8 Old volumes were removed from configuration 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...

Page 15: ...only permitted system downtime was Sunday mornings Personnel constraints There were limited personnel available to perform the migration Complex project Due to the complexity of the migration and the...

Page 16: ...ing the target MOD 9 into the existing storage management subsystem SMS environment and eliminating any SMS setup requirements for the new MOD 9 volumes 3 The team mapped the remaining MOD 3 to MOD 9...

Page 17: ...e total duration of the outage for all applications was less than one hour Figure 4 Local array to array migration with consolidation TDMF LDMF New arrays 2 2 1 7 5 5 4 4 6 Older arrays 240 MOD3 to 24...

Page 18: ...performance by migrating and reconfiguring volumes Source target incompatibilities The firm was unable to perform migration due to the complexity of the environment this created incompatibilities bet...

Page 19: ...tion strategy The firm elected to perform migration over scheduled weekend downtime with an estimated 24 hours for total migration 2 In the migration stage the migration team was given the system at 8...

Page 20: ...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 financial application was relocating four servers from a...

Page 21: ...allation of VERITAS Volume Manager on the source and target machines Hardware based mirroring This option was not possible because the source and target arrays were dissimilar Softek s TDMF UNIX IP so...

Page 22: ...d synchronization between source and target environment 4 The migration was completed and verification testing was performed on data 5 The New Jersey servers were shut down physically moved to New Yor...

Page 23: ...o legacy servers and it was risky to install new device drivers on legacy servers The migration options that were considered included the following Offline migration This would have resulted in multip...

Page 24: ...a week Big asynchronous buffer BAB absorbed peaks in write activity on legacy servers to minimize CPU usage and prevent high I O load 4 New versions of Oracle and other software preinstalled on targe...

Page 25: ...Source Server B Checkpoint Source Server A Target Server A 3 4 New arrays Old array TDMF TDMF TDMF 2 2 1 1 A B C 6 6 4 3 4 7 7 7 7 Journal checkpoint area 5 8 BAB Highlights This chart shows how the i...

Page 26: ...was considered but found to be too expensive and difficult to configure for users lacking expert level implemen tation experience Softek s TDMF Windows IP software was chosen because of its ease of us...

Page 27: ...TDMF operation in normal mode the team validated the data migrated to the new storage array by using TDMF software s checkpoint function 5 During Tuesday downtime the application was stopped and sourc...

Page 28: ...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 Som...

Reviews: