Finish Prepare Infrastructure
1. Click on the created Azure Recovery Vault and click Prepare Infrastructure. If the previous steps are done successfully, the Source settings should be filled in automatically.
2. In Target Settings, select the Azure subscription and the deployment model for the post-failover environment.
3. Create and associate a replication policy. The policy can be modified as required after creation.
Enable replication
1. Go back to the create vault and select Enable replication from Site Recovery tab.
2. Select the source configuration.
3. In Target environment, select the subscription and resource group and network (VNet and subnet) in which the replicated data will failover to.
4. Select the Virtual machine(s) from the discovered list. If VM(s) can not be selected (grayed out), the reason would appear when you hover on the exclamation mark. The most common reasons are: 1. VMware tools are not installed, 2. Vm is not powered up, 3. No IP address associated to the VM.
If VM(s) are not available in the list, see the troubleshooting steps in Troubleshoot source machines that aren't available for replication.
5. In Replication settings, there are four sections to be filled:
a. User account credentials. This can be added from the configuration server and it is sued to push the installation of the mobility service agent. However, in our scenario, the mobility service has been manually installed in order to particularly include the Boot volume and exclude the rest.
b. Managed disk type. Three options to choose from Standard HDD, Standard SSD, and Premium SSD.
c. Cache storage account. Select the storage account created in Preparing Azure section.
d. Target name. This is the VM name after failover.
6. Assign the replication policy created before and review and Enable replication. To check the replication job navigate to Replication Items.
Perform failover
1. Once the initial replica is completed. The replication Item is cleared to be tested or failed over. it is recommended to test the replication before cutting it over and complete the migration.
2. The Azure VM size can be changed from Compute and Network tab, and then click Edit.
3. In case of failover action to be performed. a list of recent recovery points (crush consistent and application-consistent) to choose from. Also, there is an option to shutdown the source machine.
Note: the frequency of the recovery points can be always configured/changed by associating a new replication policy or modifying an existed one.
4. To verify the failover, navigate to Virtual Machine and select the VM name, scroll down and select Boot diagnostics tab, click refresh to get a live screenshot from the OS.
5. If the failover is successful and VM is healthy. Commit can be initiated to persist the failover and stop the protection/replication. Alternatively, a Complete Migration can be done. However, the VM can not be failed back to the VMware environment at that point.