Virtual Machine goes to Resync-required state after live migration

Article ID: 2893206 - View products that this article applies to.
Expand all | Collapse all

Symptoms

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.

Cause

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.
 

Resolution

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:

http://technet.microsoft.com/en-us/library/hh848547.aspx

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:

Set-VMReplication -VMName "<ToBeResyncedVMName>" -AutoResynchronizeEnabled 1

In Windows Server 2012 R2, run the following PowerShell Cmdlet to know the replication frequency for all virtual machines:

Get-VMReplication  | select Name,ReplicationFrequencySec

For single VM: Get-VMReplication  -name <VMName>| select ReplicationFrequencySec

Note: The above Cmdlets for replication frequency are applicable in Windows Server 2012 R2 only. In Windows Server 2012, the replication frequency is not configurable and it is set to 5 minutes.

More information


For more information on Set-VMReplication Cmdlet, visit the following Web page:
http://technet.microsoft.com/en-us/library/hh848543.aspx


Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 2893206 - Last Review: September 26, 2013 - Revision: 1.0
Applies to
  • Windows Server 2012 Standard
  • Windows Server 2012 Datacenter
  • Windows Server 2012 R2 Standard
  • Windows Server 2012 R2 Datacenter
Keywords: 
kbhyperv KB2893206

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com