IBM DATA MIGRATION SERVICES - User manual

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

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 manager’s job. Studies have shown that technology
refresh—dened 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 availability
requirements, 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, today’s 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 signicant performance delays. And
reliable methodologies that help plan, migrate and validate data migrations
can enable customization, speed the process and ensure data integrity—simplify-
ing the technology refresh process.
Storage migrations made simple.
Page 2

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 in
order 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.
Heterogeneous
source 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 hardware
independent.
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.
Storage migrations made simple.
Page 3
Technology refresh is the primary
driver of data migration.
Highlights

Storage migrations made simple.
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 dened as
replacing an array with a new one and most commonly occurs when:
• Theleaseonapieceofstorageequipmentends
• Dataisbeingmovedfromoldtonewstorage
• Thestoragesystemisbeingupgraded
• Theorganizationhasdecidedtostandardizeonaparticulartechnology.
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 before
the lease expires to avoid additional 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 implementation of new
equipment requires migrating data from the older arrays.
IT organizations justify purchase or lease of new equipment by the fact that
it 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 justied
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.

Storage migrations made simple.
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, but
they typically range from 25 to 50 percent annually for most industries.
So, every year, a typical organization acquires storage technology to replace
arrays 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

Storage migrations made simple.
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:
• Leaseoverlapcostsorduplicatemaintenancecosts,whenoldandnew
equipmentareonthedatacenterooratthesametime
• Migrationofdatabetweenarraysfromdifferentvendors,astheremay
besignicantincompatibilities
• Riskofdatalossorcorruptionthatmayoccurifthemigrationisnot
doneproperly
• Prolongedapplicationdowntime,orevenaninabilitytorestartapplications.
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 use
to migrate data, each with its own considerations and limitations.
Offline migration methods
Ofine migration methods require that applications be taken ofine during
data movement, and therefore are suitable only when signicant downtime can
be tolerated. While the amount of downtime required typically depends on the
quantity of data being transferred, this ofine migration mechanism is not rec-
ommended for heavily used applications or those that must be accessible outside
of normal business hours. Ofine migration typically requires manual manipu-
lation of data or les, which can increase the risk of human error and may not
scale 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.

Restore from backup tapes
This method involves making a backup copy of data, then taking the associated
arrays and/or servers ofine to ensure that no new data is added. Then, the data
is restored from the backup tapes to the new arrays and/or servers. Once the
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 signicant administrative attention and application downtime.
FTP transfer
This method involves manually copying les from the source systems to the target
systems via File Transfer Protocol (FTP). As it requires le-by-le movement, the
method is not recommended when the data contains large numbers of individual
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 verication 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 limited to a single vendor environment. Other methods may consume
signicant 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.
Storage migrations made simple.
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.

Volume management or replication
Volume management is used primarily to control disk resources by mapping
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 requires
a heterogeneous storage environment over an IP network and may require the
costly installation of additional software.
Host-based mirroring
Host-based mirroring or replication solutions generally focus on le-by-le
data movement to create a secondary data copy for disaster recovery purposes.
When used for data migration, this approach may put an additional burden on
application servers and may require high-cost management, especially in het-
erogeneous environments.
Online nondisruptive migration — Softek data migration products
There are a few products available 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 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. Softek’s 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
Storage migrations made simple.
Page 8
Highlights
Softek’s TDMF software makes it
easier to upgrade to new storage,
improve application performance
and manage information availability
through the information lifecycle.

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:
• Amanufacturingcompanyrunningamission-criticalOraclecustomer
orderandtrackingsystemonSolarisconductinglocalUNIX®array-to-
arraymigration.
• Alargebankrunningacreditanddebittransactionapplicationon
IBMz/OS®conductinglocalmainframearray-to-arraymigration.
• AmajorsavingsandloaninstitutionrunninganIBMDB2®,IBMCICS®and
VirtualStorageAccessMethod(VSAM)applicationwithhigh-availability
requirementsconductingmainframemigrationwithvolumeconsolidation.
• AFortune500nancialservicesrmrunningamission-criticalDB2
datawarehouseconductingmultiserverUNIXarray-to-arraymigration
withconsolidation.
• AFortune1000bankrunningaSybasenancialapplicationconducting
aglobalmigrationtonewstorageoverdistance.
• Aninsurancecompanywithamission-criticalclaimsprocessingapplication
onOracleconductingaglobalmigrationtonewserversandnewstorage.
• AFortune500bankrunningakeyenterprisecompliancemanagement
applicationconductingalocalMicrosoft®Windows®array-to-arraymigration.
The detailed descriptions of these scenarios that follow show how Softek
capabilities can meet technology refresh needs and streamline technology
refresh projects.
Storage migrations made simple.
Page 9
Softek’s software capabilities
can meet technology refresh
needs and streamline technology
refresh projects.
Highlights
A discussion of real-world imple-
mentations can illustrate how
Softek technology simplifies tech-
nology refresh.

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:
• Limiteddowntime — Downtimewaslimitedtofourhoursontheweekend.
• Largevolumeofdata—Applicationstoragespannedten300GBvolumes.
• Increaseinvolumesize—Theplannedcapacitygrowthrequiredanincrease
involumesizeduringmigration.
The company considered the pros and cons of several different migration
options, including:
• 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increasein
volumesize.
• Array-basedreplication—Thisoptionwouldhavebeenexpensivetoinstall,
andthecompanydidnotplantouseitfollowingthemigration.Inaddition,
rmwareupgradesrequiredonthelegacyarraystosupportthecurrent
array-basedreplicationversionwouldhaveaddeddowntimeandcomplex-
itytotheproject.
• VERITASVolumeReplicator(VVR) —Thisoptionwouldhaverequired
installingtheprerequisiteVERITASVolumeManager.
Storage migrations made simple.
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.

Softek TDMF technology was chosen because the asynchronous, host-based
migration was cost-effective, able to work with disparate platforms, did not require
changes to the source environment and could accommodate the increased volume
size in the target environment. The benets of the TDMF solution were that the
Oracle application’s storage volumes were augmented, enabling continued expan-
sion of capacity. In addition, the migration was completed without signicant
downtime to this mission-critical application. Most important, the storage technol-
ogy upgrade was transparent to the application’s end users.
Softek solution: Local UNIX array-to-array migration with Softek
TDMF solution
1.SoftekTDMFtechnologywasinstalledonthehostpriortotheweeklysched-
uleddowntimeandconguredtomapthesourceandtargetdevices.Ascript
waswrittentounmountandremountthesourcedevicesduringtheweekend
outage.Thescriptwasrunjustaftertheweeklybackupsandtooklessthan
30secondstorun,sothescheduleddowntimewasnotaffected.
2.TheTDMFsolutionstartedthecopyoperationonceapplicationsareback
online.Copyranslowlyinbackgroundsoasnottosignicantlyaffectthe
operationoftheapplication.
3.Allvolumesweresynchronizedwithin48hours.
4.Switchoverwasperformedwithoutserviceoutage.Oldvolumeswereleftin
placewhileperformanceofnewvolumeswasvalidated.
Storage migrations made simple.
Page 11
Highlights
Most important, the storage tech-
nology upgrade was transparent
to users.

Figure 2
Local UNIX array-to-array migration
Storage migrations made simple.
Page 12
Highlights
A financial institution cannot afford
downtime when moving from legacy
storage to newer storage arrays.
5.Oldvolumeswereremovedfromconguration.
6.TDMFsoftwarewasleftonthesystemandusedtomovetwovolumesnon-
disruptivelywithinthenewstoragearraytoresolveperformanceproblems
causedbypathingissuesinthenewhardware.
Solaris Server running
Oracle application
New Arrays installedOlder 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 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:
• Noapplicationdowntimeallowed—Theapplicationwasakeyrevenuedriver,
requiring24x7access.Theprojected18hoursofdowntimetoinstallandcon-
gurenewarraysandcompletemigrationwouldviolatecorporateITpolicy
andcostthousandsofdollarsinlostrevenue.

• Largenumberofvolumes—Fourhundredvolumeshadtobemovedfromthe
oldtonewstoragearray.
• Budgetconstraints— Themigrationbudgetdidnotincludetheanticipated
needforoutsideconsultingresourceswithmigrationexpertise.
In this case, Softek TDMF technology was the only option considered, because
no other solution could accomplish the migration without requiring downtime.
Using Softek’s solution, the bank’s migration project was completed on schedule
and required no outside resources so the budget was not affected. And because
no application performance impact or outages were experienced, the bank could
continue to generate revenue during the migration.
Softek solution: local mainframe array-to-array migration
1.Softek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.
3.Intherstweek,administratorsmigrated50percentofvolumestotarget
storagearrayswithnoperformancedegradation.Migrationtookplace
duringpeakperiodsofactivitybecauseTDMFsoftwarehasadynamic
throttlingcapabilitythatspeedsuporslowsdownmigrationasapplica-
tionrequirementschange.
4.Refresheswereperformedperiodicallysothatupdatesmadetosource
volumeduringthecopyphaseweremadetotargetvolume,ensuring
synchronizationbetweensourceandtarget.
Storage migrations made simple.
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.

5.Administratorsmigratedthenal50percentofvolumesoverthesecond
week,withstillnoapplicationimpact.
6.Whennalsynchronizationhadtakenplace,TDMFsoftwarecompletedthe
swapoperationtoredirectthemainframeI/Ototargetvolumes,whichbecame
primaryvolumes.Switchoverwasperformedwithoutserviceoutage.
7.Backoutoptionwasavailableincaseafailureoccursduringanyphase.If
needed,originalsourcevolumecontainedallthewriteoperationsperformed
duringthemigration.
8.Oldvolumeswereremovedfromconguration.
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 debit
transaction application
IBM mainframe
New storage arrayOld storage array
1
2
3
7
4
8
6
5
TDMF
Figure 3
Local mainframe array-to-array migration
Storage migrations made simple.
Page 14
Highlights
This chart depicts the bank’s local
mainframe array-to-array migration.

Storage migrations made simple.
Page 15
Local mainframe migration with volume consolidation
A major savings and loan institution had an older locally 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:
• Convertingdatabetweenvolumesizes—TheprojectrequiredmovingMOD3
arraysontoMOD3s,andMOD3arraysontoMOD9satbothvolumeand
datasetlevels
• Limiteddowntime—The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personnel
constraints,theestimateddurationoftheprojectwasatleasttwoweeks.
The savings and loan company evaluated several migration options:
• Manualmethods—Thisoptionwasconsideredtoolaborintensive,especially
withthe“overworkedandunderstaffed”customerresourcebase.Avoiding
bandwidthimpactsalsowouldbedifcult.
• Array-basedreplication—Thisoptioncouldnotbeusedastheproject
involvedmigratingMOD3stoMOD9s.
Highlights
A savings and loan company faced
migration challenges such as
personnel constraints and strict
availability requirements.

A combination of Softek’s TDMF and LDMF software was chosen because of the
products’ ability to migrate data nondisruptively, handle the resizing of MODs,
and move specic 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.TDMFandLDMFsoftwarewasnondisruptivelyinstalledonIBMZ800
mainframeandveriedbytheimplementationteam.
2.TheteammappedsourceandtargetvolumemigrationforTDMFmigration.
Aspartoftheprocess,TDMFsoftwarewasusedtomigrateasinglesource
MOD3toaMOD9,therebyestablishing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migration,whichwas
accomplishedusingLDMFsoftware.Themappingdocumentedthetarget-
volumeSMSstoragegroupsandstorageclass.Thisalsoidentiedany
volumesthatwerenotunderSMScontrol.
4.TDMFmigrationwasinitiated.Overthecourseoftenhours(including
verication),theimplementationteammigrated200MOD3to200MOD3
and240MOD3to240MOD9.Thisentiremigrationwascompletedtrans-
parentlyduringproductionhours.
5.TheimplementationteamsetupLDMFmigrationbybuildingsourceand
targetdatasetmigrationgroups(460sourcevolumesgoingto240target
volumesatthedatasetlevel).
Storage migrations made simple.
Page 16
After evaluating several migra-
tion methods, a savings and loan
company chose Softek’s TDMF and
LDMF software due to their ability
to migrate data nondisruptively,
resize MODs and move specific
data at the dataset level.
Highlights

6.LDMFmigrationwasexecutedovera28-hourperiod(submissionofgroup
migrations,monitoringprogressandvericationresults)andnoapplication
impactwasreportedduringthisperiod.
7.Scheduledoff-hoursbounceofalldatabaseapplicationstookplaceafter
migration,andthe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 240 MOD9
240 MOD3 to 240 MOD9
460 source volumes to 240
target volumes at dataset level
DB2 and CICS VSAM
applications
IBM Z800
3
2
Storage migrations made simple.
Page 17
Highlights
This chart depicts the array-to-array
migration with consolidation enabled
by the Softek software.

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:
• 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
difculty,resultinginnumerousendusercomplaintsaboutsystemperformance.
• Relocatingdata—Anewstoragearraywaspurchasedtoimproveperformance
bymigratingandreconguringvolumes.
• Source/targetincompatibilities—Therm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oor.
The rm evaluated several different migration options:
• Ofine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conguredformirroring.
Storage migrations made simple.
Page 18
Highlights
A financial services firm struggled
with excessive storage growth and
other related challenges.

Softek’s TDMF UNIX (IP) software was chosen based on its ability to migrate
between disparate platforms and its exibility in working with various logical
denitions. The benet 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 times 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 was
no 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 efciently.
Softek solution: multiserver UNIX array-to-array migration with
consolidation
1.Inthepremigrationstage,Softekworkedwiththestoragevendortoperform
comprehensivetestingandproofofconcepttoprovetheviabilityofthemigra-
tionstrategy.Therm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p.m.
onSaturdaynight;itinstalledTDMFsoftwareonsevenAIXhostsinless
than15minutes.
3.Themigrationprocesswasinitiatedwithmigrationcongurationinloop-
back.Theactualmigrationstartedat12a.m.andendedat4a.m.,moving
22TBofdatainfourhours.
4.Aspartofthemigrationprocess,theimplementationteamresizedphysical
partitionsonvolumegroups,improvedthelayoutofthevolumesonthenew
array,andresizedtheIBMJournaledFileSystem(JFS)logs.
5.Thesystemwashandedbackat3p.m.onSunday,wellaheadofschedule,
forpreliminarytesting.TheDB2datawarehousestartedcorrectlyandthe
vericationscriptlaunched.
Storage migrations made simple.
Page 19
Highlights
Softek’s 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 working
with various logical definitions.

Storage migrations made simple.
Page 20
6.Thermperformedextensivetesting,andattheendofthescheduled
applicationstoppage,thesystemwentintofullproduction.
7.Atthenextscheduleddowntime,theoldsourcearraysweretakenoutof
serviceandsentbacktotheleaseholder.
TDMF TDMF TDMF
TDMF TDMF TDMF TDMF
New array
Old arrays
2
7
DB2 data warehouse
AIX 5.1 servers
4 hours
22 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 application 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 bank’s key migration challenges were as follows:
• Increasedstoragedemandsandinternalconsolidation—Thesefactors
drovethetechnologyrefresh.
Figure 5
Multiserver migration with consolidation
Highlights
A bank needed help relocating
four servers to another state.