VM Instant Recovery-changes during migration

[collinp]

If you are performing a VM instant recovery, lets say of a file server, that takes a long period of time for the storage to migrate and customers are making changes to the file system, is there a way to recover those changed files in the case that the Instant recovery fails?

[foggy]

Hi Collin, what kind of IR failure do you mean? Basically, Quick Migration uses the VM backup as a source to restore the VM contents and then synchronizes the latest changes to the running VM. If the IR session is not available at the moment of synchronization, there's nothing to synchronize and the QM will likely fail (need to check that).

[collinp]

Yes, I'm talking about a Quick migration. Let's say the process failed unexpectedly. Let's say a quick migration is happening and the veeam server/repository servrers reboot accidentally during the quick migration while the quick migration was at 50%. The file server user was working on a word doc on the vm file server being instantly migrated and saved it prior to the disaster. Where can they find that word doc?

[Mildur]

The Instant VM Recovery process can survive an unexpected vbr reboot:
veeam-backup-replication-f2/instant-rec ... 73465.html

I would say, it´s the same like for every VM Storage vMotion procedure.
If the vMotion has an issue, the vm will be running without any problem like before the vmotion procedure was started. Of course, after the vbr server was rebooted again. An failed vmotion process does not delete an entire vm.