Virtual Standby to Hyper-V Job Fails with Failed to Add Device ‘Microsoft Virtual Hard Disk’ Error (4036057)

An attempt to export to Hyper-V and returns the following error in the Core UI.
System.AggregateException: One or more errors occurred. —> Replay.Common.Contracts.Virtualization.HyperVException: Operation with VHD virtual disk failed

(Full error details in attached file 'Virtual Standby to Hyper-V ID119440.txt')

Though typically present on Windows Server 2008 R2 and Windows 7 machines, it is possible that the System Reserve Partition (SRP) may not exist in some configurations.

When performing a virtual standby export (ad-hoc or continuous) for a server with physical disks in excess of 2 TB, it is not possible to complete the export of the disks which exceed 2 TB in size; however, in certain scenarios it is possible to export just the C: and SRP (if applicable) partitions and then perform a rollback or live rollback of the remaining volumes. The following criteria must be met to accomplish this procedure:

• The physical disk on which the C: and SRP (if applicable) reside must be smaller than 2 TB.
• The Hyper-V server receiving the export must be support virtual disks larger than 2 TB.  Currently, only Windows Server 2012 and Windows 8 (using VHDX) have this capability.

To execute this workaround, perform the following.

1. Verify that the C: and SRP (if applicable) reside on a disk that is less the 2 TB. This can be done using MSINFO32 or disk manager for the original agent server, if still available.
   1. If using MSINFO32, navigate to System Summary\Storage\Disks. Typically, the system disk will be the partition labeled “Disk #0, Partition #0″. If this disk is larger than 2 TB the export will not complete.
   2. If using Disk Manager on the original agent server, simply observe the size of Disk0.
2. Configure an ad-hoc or continuous virtual standby export, selecting only the C: and SRP (if applicable) volumes.
3. Once the initial export is complete, manually create one or more virtual disks using the VHDX format. Be sure to size them appropriately.
4. Attache any VHDX virtual disk to the virtual machine configuration.
5. The new virtual machine can now be booted. Once booted, the 2+ TB disks should be visible in Disk Manager.
   1. Please note that some applications may not function properly yet, as not all volumes will be present in the operating system (OS).
6. Perform a rollback or live rollback for the remaining volumes using typical procedures as if it were a physical server.

For more information, please refer to the following links:

• AppAssure Virtual Standby
• How to Perform a Rollback on a Server in AppAssure 5
• How to Perform a Rollback – Live Recovery of a Data Volume
• How to Create or Attach a VHD or VHDX File in Windows 8
• Configure Disks and Storage