Migrate-restore failure; failed to decompress

[eric]

Restore/migration failure with an open support ticket, 00496367. This is on an evaluation server so time is of the essence (when isn't it though).
If anyone can help with this it would be appreciated.

The error occurs when attempting to restore/migrate any server from the Backup.
Interestingly Instant Recovery does work, but you cannot copy it to a datastore, it returns the same error.

1/1/2014 8:28:02 PM VM files restore started
1/1/2014 8:31:42 PM File restored: server.vmx
1/1/2014 8:31:47 PM File restored: server.vmxf
1/1/2014 8:31:53 PM File restored: server.nvram
1/1/2014 8:31:58 PM File restored: server.vmdk
1/1/2014 8:39:36 PM Error Failed to restore file: server-flat.vmdk Error: Client error: Failed to decompress LZ4 block: Incorrect decompression result or length (result: '-595015', expected length: '1048576').
Unable to receive file.
An existing connection was forcibly closed by the remote host
Cannot process [restore] command.
1/1/2014 8:39:38 PM VM files restore completed


TYIA,

~eric

[Gostev]

The only possible issue I am aware of around Quick Migration can happen for disks larger than 2TB. Is this the case here?

[eric]

Nope, the disk is about 60GB with only 12GB of data. I have tried with two different machines.

This ticket was opened on the 27th of December. Still not resolved (or really even worked on) as of the 3rd of January.

When can I expect a technician to work with me to resolve this?

~eric

[foggy]

Eric, if you are not satisfied with how your case is treated, you can ask your engineer to escalate the case to a higher tier. Thanks.

[eric]

As an update the restore failure occured on the source host as well as the offsite Backup Copy host.

I deleted the Backup Copy data and job and the original Backup data and job. I then recreated the Backup of this machine and attempted to restore the vm files, vmx and vmdk locally.

Same decompress error. The support ticket has been updated and I have call scheduled with a support technician.

~eric

[foggy]

While you're waiting for the call, it is probably worth trying to back up to some other storage and see whether the issue is reproduced. This will allow to eliminate the effect of the underlying storage itself.