Five Workload-to-Cloud Migration Methods
0 likes385 views
This document discusses five methods for migrating workloads to the cloud: 1) Manual data migration, 2) Offline media transfer, 3) Internet transfer of virtual disk images, 4) Software agent-based data replication, and 5) Full server failover using software agents. It provides advantages and considerations for each method, and explains how to implement the fourth and fifth methods which use software agents to replicate data over time without impacting production systems.
Five Workload-to-Cloud Migration Methods
- 2. INTRODUCTION Once you know that cloud computing is for you, then you must decide how to migrate workloads to the cloud or between service providers. This eBook explores options for workload migration to the cloud, hopefully making your research easier and guiding you to a more informed choice about which workload migration methodology best suits you. (For more detailed descriptions, see my blog at _________________.) In this eBook, we devote a chapter to each of five migration methods: 1 2 3 Manual data migration to new OS and application environments Offline media transfer involving the shipment of portable media Internet transfer of virtual disk images 4 5 pg. 2 Software agent-based data replication to new OS and application environments Full server failover into the cloud using software agents
- 3. CHAPTER 2 MANUAL DATA MIGRATION FROM OLD TO NEW Advantages: • • • • Distance is not an issue. Very cost effective. Tools are usually free (e.g. mysqldump and Robocopy). Ability to dry-run transfer with no production impact. Considerations: • • • • • pg. 3 In-flight data; always encrypt. Best for simple applications. Maintenance window varies with data size. Internet connections can be a bottleneck. Not good for short Recovery Point Objectives (RPO). HOW 1 How: Get access to the new environment from your CSP. Copy over your data and configurations via the Internet. Make sure everything migrates to the new environment, no unknown dependencies surface, and the application isn’t attempting to communicate with something that’s not there.
- 4. CHAPTER 3 OFFLINE MEDIA TRANSFER BY SHIPPING PORTABLE MEDIA items associated with the move. HOW 2 The approach is straightforward. Perform the conversion and copy to drive. Ship via a reliable carrier. Import the virtual images and test. Take care of DNS, VPN, certifications, and other patch Advantages: • Good for transferring native format systems (VMware source to VMware provider) or converting systems to CSP’s format (Hyper-V source to VMware provider). • Tools are typically free. • Media and courier service costs. • Handles moderate-size workloads. Considerations: • Data is handled by a third-party; always encrypt. • Lack of USB 3 increases time. • Production system data is lost throughout the copy/conversion process. • Service is unavailable as long as maintenance window remains open. • Long maintenance window. pg. 4
- 5. CHAPTER 4 INTERNET TRANSFER OF VIRTUAL DISK IMAGES HOW 3 Upload workloads in native format or CSP’s format to a SFTP server or similar system. Provider imports the virtual images to its cloud via the Internet. Advantages: • Transferring in native format saves from having to rebuild application environment. • Good over long distances. • Negligible latency with distance and network. • Conversion tools are typically free. Considerations: • Internet bandwidth size and cost at source and at target. • May need software but at minimal cost. • Protect in-flight data over unsecured networks. • Full data copy must be complete before services can be started on the new environment. • Good for smaller data sizes and VMs. • Long maintenance window. pg. 5
- 6. CHAPTER 5 INTERNET TRANSFER OF VIRTUAL DISK IMAGES the new destination server. When the new server 4 HOW Install replication software on the old server and catches up with the old server, stop replication and test the new servers. Restart synchronization until the new server catches up again with the old server. When replication and testing are complete, failover. Advantages: • Good over long distances. • Allows migration heterogeneous environments (e.g. Xen to VMware or Amazon to Peak 10). • Replicate over time without impacting production systems. • Good for large data sets. • Short maintenance window; quick failover. Considerations: • Cost of Internet bandwidth both at source and at target, replication software, more experienced labor. • Complex when many servers are involved. • Unexpectedly large changes to source-system data effectively restarts the process. pg. 6
- 7. CHAPTER 6 INTERNET TRANSFER OF VIRTUAL DISK IMAGES Advantages: • Good over long distances. • Allows migration heterogeneous environments (e.g. Xen to VMware or Amazon to Peak 10). • Replicate over time without impacting production systems. • Good for large data sets. • Short maintenance window; quick failover. Considerations: • Cost of Internet bandwidth both at source and at target, replication software, more experienced labor. • Complex when many servers are involved. • Unexpectedly large changes to source-system data effectively restarts the process. pg. 7 HOW 5 Install the software on the old server and replicate the entire source system to a shell VM, agent to agent or to an aggregated target such as a VM appliance. When the new server catches up with the old server, stop replication and test the new servers. Restart synchronization until the new server catches up again with the old server. When replication and testing are complete, failover.