eBooks/eGuides

This is where, after you've landed on your migration goals and gathered all requirements and constraints, you can choose the method of migration that works for you. It's through the migration effort that you'll determine the approach that meets your requirements. Best addressed on a per-application basis. You're essentially physically moving your workloads and applications (including their data) to the cloud and planning to retire the on-premises versions. Every organization will have a different approach and mixture of rehosting, refactoring, rearchitecting, and rebuilding for their applications. The lift-and-shift method most often employed for server or VM migration is real-time replication, due to its flexibility and capability in staged migration. Real-time replication Real-time replication involves setting up a copy of the workload in the cloud and allowing asynchronous replication to keep the copy and the original in sync (Figure 4). This means that while you're building and executing your migration plans, any data or server updates are synced between the copies. Migrate Chapter 04 13 Many tools also support application- aware replication automatically. Microsoft applications (like SharePoint, Dynamics, and Active Directory) and apps from other companies (including Oracle, SAP, IBM, and Red Hat) can be migrated with application- aware replication. ExpressRoute and Databox can assist with this. As you plan your migration timeline, also remember that migration tools can perform the final launch in your cloud and turn off the on-premises application. Figure 4: Using real-time replication to keep workloads in sync. VM VM VM VM vSphere or Hyper-V Host Firewall On-premises datacenter Replication Cloud provider VM VM VM VM Migrate 04

• Cover