The virtual machine goes into error state or Resync required state after Live Migration, with 30 seconds replication enabled in Windows Server 2012 R2, this case may occur more dominantly than in Windows Server 2012. Additionally, you may receive the following error message:
The incoming delta has a parent transfer ID (CD5ED5C2-9ECB-4676-BFD9-B242BFE0B59A) which is different from the last transfer ID (E0C365C3-E0CF-41BD-9C36-3665EF9C62B4).: unknown error (0x800480c5)
Note: The migration operations triggered through Failover Clustering or ‘Move-VM’ PowerShell Cmdlet implement migration process atomically. As a result, you may not notice this issue.
Since the migration process using Move Wizard or SCVMM is a multi-step process, there is a possible chance of dated VM replication metadata in VM config being present at the migrated location. This happens because changed VM replication metadata is not refreshed at the end of the multi-step migration process. This causes the VM configuration to go out of sync with regard to the replication partner (primary or replica) leading to error or Resync-required state.
In theory, even Windows Server 2012 with 5 minutes replication can run into this problem but the chances are very low unlike 30 seconds replication in Windows Server 2012 R2.
Use ‘Move-VM’ PowerShell Cmdlet for migration of VMs when replication relationship is set.
For more information on Move-VM Cmdlet, visit the following Web page:
If you are using other methods to migrate, and if the VM goes into Resync-required state after migration, VM will resynchronize automatically if AutoResynchronizeEnabled option is set to 1 in Set-VMReplication command.
To set a VM to resynchronize automatically, use the following PowerShell Commandlet: