Safe and Secure Data Migration It s Not That Tough

Transcription

1 Safe and Secure Data Migration It s Not That Tough David Clark Director of Product Marketing QLogic, Storage Solutions Group

2 Agenda Drivers for Data Migration Why Data Migration is complex Seven Gremlins to a Safe DM Methods / Tools used for Data Migration A Better Data Migration tool

3 Data Migration It s Not That Tough

4 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.

5 Leading Drivers End of Life/lease on storage systems Technology transitions Speed changes on FC 2Gb 4Gb 8 Gb iscsi, FCoE Operating Systems and Application Migration M&A activities Regulatory Compliance VMware / Virtualization driven server consolidation Storage Consolidation Tiered Storage Strategies Information Life Cycle Management

6 Why Data Migration is complex Data Migration cuts across: 1. Multiple OS and applications 2. Multiple SAN islands & Storage protocols 3. Multi-Vendor Storage O/S A O/S B O/S C O/S D Servers FC SAN FC SAN iscsi SAN Vendor A FC Storage Vendor B iscsi Storage

7 IT Organizations within Data Centers Application team Manages applications Network team Manages Networks Storage team Manages storage Applications Storage Network Data Migration involves interactions amongst many IT teams

8 Different Types of Data Migration ONLINE / OFFLINE Depends on how much down time application can tolerate Local Within Data Center Remote Migration of Data Centers Across Storage Protocols FC, iscsi, FCoE Many-to-one Consolidation of volume grown over multiple LUNs to a single large volume

9 Customer Concerns re: DM Extend Downtime 58% Compatibility Issues 48% Data Corruption 37% Applications Performance 36% Lost Data 32% No Problems 25% Other 6% Data Source - ESG Survey 0% 10% 20% 30% 40% 50% 60% 70%

10 Gremlins of Data Migration 1. Downtime 2. Human error 3. Data corruption 4. Infrastructure incompatibilities 5. Departmental conflict 6. Costs and resources 7. Poor planning (too many details)

11 Data Migration Methods Manual Methods Software based Network based appliance Array based New paradigm

12 Manual Methods VTL Server Backup & Restore Simple to use Protects Meta Data Requires Backup device Extended down time Expensive Requires scheduling with backup windows Manual copies Source Array If small amount of file-based data set, most inexpensive method For repetitive work, develop scripts Tedious & prone to human error Must ensure the copy of application metadata Extended down time Server SAN FC SAN Target Array Source Array Target Array

13 Software only Migration tools Typically installed on the server Manages Migrations at Volume level Supports Migration From DAS to SAN SAN to SAN Independent of Storage and SAN 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 A O/S B O/S C Servers FC SAN Migration is OS vendor dependent Source Array Target Array

14 Software Migration Steps 1. Schedule application down time 2. Storage Manager kills Application Manager (or whatever is needed to load DM agents/apps) 3. Ensure that Agent/App supports proper OS release(s) 4. Create volume-to-lun map 5. Take application offline 6. Run migration for selected volumes/luns 7. Rezone new storage to application 8. Reboot server/application

15 Network Based DM Tools Deployed in the Network Independent of Operating System & Storage Array Block based migration tool ONLine / OFFline Migration Today s DM tools work only in a vendor specific Network May require a specific Fabric infrastructure already installed Cumbersome to setup Downtime during install Expensive May require new multi-path SW O/S A O/S B O/S C Servers FC SAN Fabric Vendor Dependent Source Array Target Array

16 Network DM Steps 1. Determine fabric-based or direct-attach 2. Network Manager kills Storage Manager a) Attach and zone new device b) Disconnect storage and rezone O/S A O/S B O/S C Servers FC SAN Fabric Vendor Dependent Source Array Target Array

17 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 Fabric Vendor Dependent Source Array Target Array

18 Storage Array based Deployment Software License on an array New class of array Independent of Operating System and Fabric vendors Cost effective if used in very narrow use case Incompatible across heterogeneous storage SW often not compatible within different family of arrays even from same vendor Software License tied to a specific array, allows migration in and out of that specific array New class of storage requires a fork lift upgrade

19 Array-based Steps 1. Check array family compatibility 2. Acquire and load license for EACH array 3. Determine Volume-to-LUN map 4. Take application(s) offline 5. Perform block-level transfers 6. Rezone and reboot O/S A O/S B O/S C Servers FC SAN Source Array Target Array

20 It can t be that tough? A Better Data Migration Solution

21 Need for DM tools Block based offline migration Service Must be Independent of: OS, Fabric, Storage Vendors Low cost: Small Capital investment Pay as you go model Simple to transport OFFLINE Server C w/ LUN 3 OFFLINE Server B w/ LUN 2 OFFLINE Server A w/ LUN 1 Old Storage FC SAN Minimize downtime Fast install and configuration Simple to use Associate Server volumes to physical LUNs Use only allocated array bandwidth DATA PATH Data Mover New Storage LUN 3 LUN 2 LUN 1 Migrated LUNs LUN 3 LUN 2 LUN 1

22 DM Tool requirement for Enterprise 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

23 DM Tool requirement for Enterprise 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

24 DM Tool requirement for Enterprise Provide Protection against Human errors Accidently migrating Destination LUN to Source LUN Selection of one of the other Data LUN as Destination LUN 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

25 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 Server B w/ LUN 2 FC SAN Data Mover Server A w/ LUN 1 Old Storage DATA PATH New Storage LUN 3 LUN 2 LUN 1 Migrated LUNs LUN 3 LUN 2 LUN 1

26 Online DM Scenario Standard zoning before DM Dual SAN, split path SAN A SAN B Old Storage New Storage

27 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 SAN B Old Storage New Storage

28 Online DM Scenario Simplified topology for illustration SAN Old Storage New Storage Source LUN Destination LUN Sector 0 Sector N Sector 0 Sector N

29 Online DM Scenario Simplified topology for illustration SAN Sync Log SRC sector 3 New write Old Storage New Storage Source LUN Destination LUN Sector 0 Sector N Sector 0 Sector N

30 Online DM Scenario Simplified topology for illustration SAN Sync Log SRC sector 3 Old Storage New Storage Source LUN Destination LUN Sector 0 Sector N Sector 0 Sector N

31 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 Safe and Secure Data Migration is now possible, it s not that tough!

32 Questions? THANK YOU

33