I have had to do an instant recovery a few times, and each time the restore and migration back to production has been successful. The problem occurs during the first backup of this newly restored VM(s). When a backup copy job attempts to copy the VM to the cloud, the job fails with an error like below, indicating it can't find the VM in the cloud repo.
-During my first cases and a lot of wasted days I had to delete my entire cloud backup set and reseed. And this took nearly a week which means a week without off-site backups. Unacceptable.Warning Cannot find migrated local object with old host ID d0cfbcf9-c710-472b-8f7e-ee0b043518be and old object ID vm-11682
-During my last instant recovery, I opened another case and this time was told that I could work with my cloud provider and copy the VBM file to clean instance, edit the VBM file to remove the reference to vm-11682 (in my case), then copy the VBM file back over to my tenant. This worked well and only resulted in having to reseed this one particular VM within the job rather than the entire set of VMs.
I am desperately requesting a way for Veeam to know when a machine has been recovered and to do whatever it needs to do so that backups can continue without trickery and days of support tickets between Veeam and the provider to get back to normal.
If I'm crazy and there is another way to accomplish this, please let me know.
Happy backups!
