Migrating your on-premises workloads to Azure involves various phases. You’ve completed the planning and assessment, and prepared the environment and VMs for migration.
The next phase is to track and monitor the replication process, before running a full migration to Azure. You’ll run a test migration in a non-production environment to ensure that your VMs can successfully migrate to Azure before finally cutting over to a full migration.
In this unit, you’ll review the replication process and components involved. You’ll also learn how to track and monitor each phase of the migration process.
Replication process
The replication process consists of several steps, beginning with a Start Replication job.
- On successful completion of the Start Replication job, the VMs start their initial replication to Azure.
- During initial replication, a Hyper-V VM snapshot it taken. The Azure Site Recovery provider and Azure Recovery Service agent work together to replicate data from Hyper-V VMs to Azure. The replicated data is uploaded to a storage account in the Azure subscription.
- Disk data from the snapshot is replicated to Hyper-V Replica managed disks in Azure. The replica disks are used to create the Azure VMs when you migrate.
- Hyper-V Replica tracks disk changes during initial replication, and changes are stored in log files.
- On completion of initial replication, the VM snapshot is deleted, and delta replication starts.
- The Recovery Services agent periodically uploads replication logs to a log storage account.
Leave a Reply