-
- Veeam Legend
- Posts: 198
- Liked: 55 times
- Joined: Mar 22, 2017 11:10 am
- Full Name: Mark Boothman
- Location: Darlington, United Kingdom
- Contact:
Restore Failed
My Client is having issues restoring hyper-vm after having to restore the vm config file.
The vm's are registered fine in hyper-v and failover cluster manager.
When try a restore prior to the config file restore they are getting
Failed to find virtual machine owner host: Failed to get cluster resource group.
Failed to get VM owner by ID.
Is there a quick fix for this? I know in vmware we can just rescan the host but that doesn't seem to work here
Any thoughts / guidance appreciated
Thanks
Mark
The vm's are registered fine in hyper-v and failover cluster manager.
When try a restore prior to the config file restore they are getting
Failed to find virtual machine owner host: Failed to get cluster resource group.
Failed to get VM owner by ID.
Is there a quick fix for this? I know in vmware we can just rescan the host but that doesn't seem to work here
Any thoughts / guidance appreciated
Thanks
Mark
-
- VP, Product Management
- Posts: 7076
- Liked: 1510 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: Restore Failed
Do I get it correctly, that you restore the VM and Veeam registers it. Then you end up with the error at boot. You then restore the config file as file and it works?
-
- Veeam Legend
- Posts: 198
- Liked: 55 times
- Joined: Mar 22, 2017 11:10 am
- Full Name: Mark Boothman
- Location: Darlington, United Kingdom
- Contact:
Re: Restore Failed
The client backed up the VM's normally and then the config files were corrupted. We restored the config files and re-imported the VM.
When I went to restore the guest files after rescanning the host it told me it couldn't find the vm object ID.
When I went to restore the guest files after rescanning the host it told me it couldn't find the vm object ID.
-
- VP, Product Management
- Posts: 7076
- Liked: 1510 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: Restore Failed
OK... now it is clear what happened. Thank you.
If you register the VM again, it will get a new ID and file restore to original will not work from older backups, as they can not find the VM anymore. You can restore files with "Copy to" if needed.
The question is why the config file went corrupt?
How did you restore the files? With Veeam?
I am just guessing here, if you have damaged your configuration files and restore them with Veeam (VM File Restore https://helpcenter.veeam.com/docs/backu ... tml?ver=95) no VM registration is needed and you can start the VM again?
If you register the VM again, it will get a new ID and file restore to original will not work from older backups, as they can not find the VM anymore. You can restore files with "Copy to" if needed.
The question is why the config file went corrupt?
How did you restore the files? With Veeam?
I am just guessing here, if you have damaged your configuration files and restore them with Veeam (VM File Restore https://helpcenter.veeam.com/docs/backu ... tml?ver=95) no VM registration is needed and you can start the VM again?
-
- Veeam Legend
- Posts: 198
- Liked: 55 times
- Joined: Mar 22, 2017 11:10 am
- Full Name: Mark Boothman
- Location: Darlington, United Kingdom
- Contact:
Re: Restore Failed
Ahh that makes sense. The config file was hit by ransomware so Hyper-v couldn't read the config files. We restored the config files only from backup.I never thought of copy too.
Thanks for the pointers.
Everything is back up and running now thankfully
Thanks for the pointers.
Everything is back up and running now thankfully
Who is online
Users browsing this forum: No registered users and 32 guests