This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

export validation failed of standby VM

I have a primary core that also exports two standby VM's to a hypervisor.  I am now setting up a replication core and want to export the same to machines to another Hypervisor. On the replication core I am unable to export my second standby VM with an error message of-

Failed to enqueue continuous export of <server name> to localhost. Reason export validation failed. An additional 82.49 GB free space is required

The space on the replication server partition for VM storage is short but it should fit. My other copy of this same server uses about 1.8Tb and the replication server has 2.04 Tb free.

Ideas?

  • Let's get some back ground information:

    1. What build is your core?
    2. What are you exporting too, HV or ESXi?
    3. What is the build of OS are exporting too?

    Agent you are exporting:

    1. What is total size of volumes being exported?
    2. What is current used space on the volumes being exported?
  • 6.2.1.100/2012r2/HyperV

    It should be about 1.87 Tb going to 2.04 Tb

    I added two drives and expanded the array. It should be over a Tb free now. We'll see how it goes. I suspect it just wants more wiggle room for some reason. saying I need 82.49GB is oddly specific and does not work with any amount of math so it must be some weird percentage calculation the algorithm decided on

  • Yes, we do need wiggle room. Besides the overhead needed by HV or ESXi, every volume exported has an associated snapshot vhdx or vmdk. The snapshot is used to add changes needed for the machine to run on the host being exported too. For continuous exports, it is also used to update changes from new recovery points every time it is updated.

  • That was it. The extra space stopped the error and allowed the export of the second standby VM.

    Thanks!