Instant recovery and "Quick" migration

[FireExit]

Hi,
I did an Instant Recovery from an object storage repository, and the server booted into VMware with the write cache redirected to a VMware datastore.

Then Quick Migration, a 4 hour task of "Copying VM files", I think it was pulling all the disk data down from the cloud, but I don't know where it was going. To a VMware datastore, I guess.
Then the Quick Migration process powered off the VM and started "Copying snapshot files".
"Unable to hot add source disk disk0-000001.vmdk, failing over to network mode..."
After 54 minutes it was 1% done.

What was it doing - what needed copying, from where, to where?
If it was committing (deleting) a multi TB snapshot, why did the VM have to be powered off?
Why was it quicker to download from Wasabi than to move locally?

Looks similar to this report: https://old.reddit.com/r/Veeam/comments ... shot_file/

[Mildur]

Hi FireExit,

With Quick Migration, the VM is first restored from the backup repository to the production host. In the next step, all changes from the instant-recovered VM are transferred and consolidated with the recovered VM. More details are available in our Help Center.
The duration of this step depends on the amount of changed data and the available proxy mode. It seems hotadd was not possible, so the network proxy mode was used as a fallback.

A detailed explanation of each Quick Migration step can be found in this Help Center article. Based on your description, it appears a Cold Migration was performed since the VM was powered off during the process.

I recommend opening a support case to review your logs and configuration.

Best,
Fabian