In this post we will configure the Classic VM replication scenario and initiate the synchronization between our sites.
In the previous parts for this series:
- Classic VM to ARM Using Azure Site Recovery (ASR) V2 – Part 1: Vault Deployment
- Classic VM to ARM Using Azure Site Recovery (ASR) V2 – Part 2: Process Server
- Classic VM to ARM Using Azure Site Recovery (ASR) V2 – Part 3: Mobility Service
- Classic VM to ARM Using Azure Site Recovery (ASR) V2 – Part 4: Target Infrastructure
First, let’s create the replication policy and the replication scenario. As you remember, we are “tricking” ASR to think we are working with physical boxes while actually the Mobility Service is installed on the Classic VM. I will leave the default settings for now.
Make sure the Process server is connected and select the replication policy we’ve just created.
Review the compute configuration and hit OK.
Great! We are now ready to enable the replication for the Classic VM.
This is where the real magic gets configured. Make sure you choose “Resource Manager” as the post-failover deployment model. This will allow for an ARM VM creation when we will perform the unplanned failover.
Enter the details for the Classic VM and wait for the discovering process to finish.
Go back to step 1 in the wizard and then back to step 2. Select the VM.
The “Local Admin” is the account we configured in the last part of the Process server deployment.
Select the retention policy.
Awesome! Now the VM will start its replication to the other side.
In the next part for this series we will hit the “big red button” and initiate the unplanned failover process.