Professional Documents
Culture Documents
Data Migration
Its Not That Tough
David Clark
Director of Product Marketing
QLogic, Storage Solutions Group
Agenda
Data Migration
Data Migration
Data Migration is one of those tasks that never
seems to be done. The data center ebbs and
flows through periods of storage and server
expansion & consolidation.
The need to
migrate data never goes away, it just takes a
break.
Leading Drivers
End of Life/lease on storage systems
Technology transitions
Speed changes on FC 2Gb 4Gb 8 Gb
iSCSI, FCoE
O/S B
O/S C
FC SAN
FC
SAN
O/S D
Servers
iSCSI
SAN
Vendor A
FC Storage
Vendor B
iSCSI Storage
Network team
Storage
Applications
Network
Manages Networks
Storage team
Manages storage
Local
Within Data Center
Remote
Migration of Data Centers
Many-to-one
Consolidation of volume grown over multiple LUNs to a
single large volume
58%
Compatibility Issues
48%
Data Corruption
37%
Applications Performance
36%
Lost Data
32%
No Problems
25%
Other
6%
0%
10%
20%
30%
40%
50%
60%
70%
Manual Methods
Software based
Network based appliance
Array based
New paradigm
Manual Methods
Server
VTL
SAN
Simple to use
Protects Meta Data
Requires Backup device
Source Array
Extended down time
Expensive
Requires scheduling with backup windows
Target Array
Manual copies
Source Array
Target Array
O/S B
OS Specific
Need a different tool or
version of SW per OS type
Compatibility with many
different versions of OS and
software is required
Server Reboot Required after
install
O/S C
Servers
FC
SAN
Source Array
Migration is OS
vendor
dependent
Target Array
O/S A
O/S B
Servers
FC
SAN
Source Array
Fabric Vendor
Dependent
Target Array
Network DM Steps
1.
2.
O/S A
O/S B
O/S C
Servers
FC SAN
Source Array
Fabric Vendor
Dependent
Target Array
Network DM Steps
3. Ensure fabric compatibility
4. Determine which Apps/LUNs to be migrated
5. Schedule downtime for some Apps (SANattached) or all Apps (direct-attached)
6. Reboot server/Apps to new storage
O/S A
O/S B
O/S C
Servers
FC SAN
Source Array
Fabric Vendor
Dependent
Target Array
Array-based Steps
1.
2.
3.
4.
5.
6.
O/S B
O/S C
Servers
FC SAN
Source Array
Target Array
Low cost:
Small Capital investment
Pay as you go model
Simple to transport
OFFLINE
Server C w/ LUN 3
OFFLINE
FC
SAN
Server B w/ LUN 2
Data Mover
OFFLINE
Server A w/ LUN 1
DATA
PATH
Old Storage
LUN 3
LUN 2
LUN 1
Migrated LUNs
New Storage
LUN 3
LUN 2
LUN 1
Independent of :
Operating System
SAN Vendor
Storage protocols (FC, iSCSI, FCoE)
Storage Array
Need to support :
Online / Offline
Local / Remote
Many to One
Volume consolidation from many small LUNs to a single LUN
Least intrusive
Should not require any changes to Host Software or any other infrastructure
already in place
Should be able to insert ONLINE
Management
Manage Remotely
Simple to install, configure and deploy
Should provide detailed intelligent migration reports that are simple to
understand
Flexible scheduling of migration Jobs
Should facilitate communication amongst multiple groups with Data Center
Association of Application Volume to Physical Luns
Accountability
Security
Provide the access to Job configuration only for authorized
users
Alerts on unauthorized attempt
Address cost
Low capital cost
Should not require fork lift upgrades
Pay as you go model
Enterprise Online DM
1. Install appliance and new storage (nondisruptive)
2. Create Volume/LUN map
3. Migrate and verify
4. Rezone and reboot
Server C w/ LUN 3
FC
SAN
Server B w/ LUN 2
Server A w/ LUN 1
Data Mover
DATA
PATH
Old Storage
LUN 3
LUN 2
LUN 1
Migrated LUNs
New Storage
LUN 3
LUN 2
LUN 1
Online DM Scenario
Standard zoning before DM
Dual SAN, split path
SAN A
Old Storage
SAN B
New Storage
Online DM Scenario
Rezone dual-path with DM appliance as target for server
Rezone dual-path with DM appliance as initiator for storage
Maintain one server path while configuring the other path
SAN A
Old Storage
SAN B
New Storage
Online DM Scenario
Simplified topology for illustration
SAN
Old Storage
New Storage
Source LUN
Sector 0
Destination LUN
Sector N
Sector 0
Sector N
Online DM Scenario
Simplified topology for illustration
Sync Log
SRC sector 3
SAN
New
write
Old Storage
New Storage
Source LUN
Sector 0
Destination LUN
Sector N
Sector 0
Sector N
Online DM Scenario
Simplified topology for illustration
Sync Log
SRC sector 3
SAN
Old Storage
New Storage
Source LUN
Sector 0
Destination LUN
Sector N
Sector 0
Sector N
Summary
Data Migration should be:
1. Managed by one group
2. Independent of OS, Fabric and Storage
environments
3. Minimally intrusive
4. Highly automated less prone to error
5. Cost-effective
Questions?
THANK YOU