-
buk3ta
- Influencer
- Posts: 14
- Liked: 3 times
- Joined: Oct 09, 2019 8:33 am
- Full Name: Jufri Juhan
- Contact:
Exclude VMs from Backup Job
I have excluded two VMs from my backup to disk job. But after the job has completed, the error message still appeared.
Do I need to exclude the disk as well? Or VM exclusion should be sufficient. On the other hand, both VMs are not in use anymore, what would be the best practice? Exclusion or remove it?
Error details: Task failed. Failed to expand object [VM name]. Error: Failed to find virtual machine owner host: Failed to get cluster resource group. Failed to get VM owner by ID.
-
HannesK
- Veeam Software
- Posts: 12494
- Liked: 2400 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Exclude VMs from Backup Job
Post
by HannesK » Oct 15, 2019 5:59 am
Hello,
does your backup job contain the whole cluster, or did you add each VM one by one to the backup job?
both VMs are not in use anymore
does that mean, that they do not exist anymore? because in that case, it should be a warning that the VM does not exist anymore. not an error.
In general: the best way is to remove unused VMs from the job
Best regards,
Hannes
-
buk3ta
- Influencer
- Posts: 14
- Liked: 3 times
- Joined: Oct 09, 2019 8:33 am
- Full Name: Jufri Juhan
- Contact:
Re: Exclude VMs from Backup Job
Post
by buk3ta » Oct 15, 2019 7:44 am
Hi Hannes,
Thank you for your reply. I added the whole cluster into the backup job.
The VMs are still existed, but it is currently offline. So, still best to remove it from the job right?
-
foggy
- Veeam Software
- Posts: 20911
- Liked: 2063 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Exclude VMs from Backup Job
Post
by foggy » Oct 15, 2019 10:28 am
Hi Muhamad, how did you configure exclusion? Did you browse to the VMs under the same cluster to exclude them?
-
buk3ta
- Influencer
- Posts: 14
- Liked: 3 times
- Joined: Oct 09, 2019 8:33 am
- Full Name: Jufri Juhan
- Contact:
Re: Exclude VMs from Backup Job
Post
by buk3ta » Oct 18, 2019 6:40 am
Hi Alexander,
It seems like the exclusion is unable to solve the issue. I took another alternative by removing the VMs completely from the backup job.
My backup is working fine now without warning or error messages.
Thanks!
-
foggy
- Veeam Software
- Posts: 20911
- Liked: 2063 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
-
Contact:
Re: Exclude VMs from Backup Job
Post
by foggy » Oct 18, 2019 10:11 am
1 person likes this post
Actually, exclusions should work as you expect, that’s why I asked how you have configured them. If removing VMs completely is an option, then you’re good anyway.
Who is online
Users browsing this forum: AdsBot [Google] and 22 guests
-
MarkBoothmaa
- Service Provider
- Posts: 74
- Liked: 11 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
-
Andreas Neufert
- VP, Product Management
- Posts: 6256
- Liked: 1301 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: Restore Failed
Post
by Andreas Neufert » Sep 23, 2018 6:06 pm
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?
-
MarkBoothmaa
- Service Provider
- Posts: 74
- Liked: 11 times
- Joined: Mar 22, 2017 11:10 am
- Full Name: Mark Boothman
- Location: Darlington, United Kingdom
- Contact:
Re: Restore Failed
Post
by MarkBoothmaa » Sep 24, 2018 8:21 am
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.
-
Andreas Neufert
- VP, Product Management
- Posts: 6256
- Liked: 1301 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: Restore Failed
Post
by Andreas Neufert » Sep 24, 2018 8:44 am
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?
-
MarkBoothmaa
- Service Provider
- Posts: 74
- Liked: 11 times
- Joined: Mar 22, 2017 11:10 am
- Full Name: Mark Boothman
- Location: Darlington, United Kingdom
- Contact:
Re: Restore Failed
Post
by MarkBoothmaa » Sep 24, 2018 10:52 am
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 
Who is online
Users browsing this forum: No registered users and 5 guests
Hyper-V Backup jobs failing with an error “The system cannot find the file specified” – Veeam Backup & Replication 9.5 Update 4
We have recently upgraded the Veeam Backup & Replication to version 9.5 Update 4 and we got trouble on backing windows 2012 Hyper-V cluster VMs.The error was related “application-aware processing may fail with the error “The system cannot find the file specified”.”
Error
Processing “VMName” Error: The system cannot find the file specified. Failed to open file [\?GLOBALROOTDeviceCSV{e72144ea-ef3e-475b-88b9-733771799784}VMNAMESnapshotsF68A0FFE-F6AC-4605-9B55-B80DB89098B3.xml] in readonly mode. Failed to open file [\?GLOBALROOTDeviceCSV{e72144ea-ef3e-475b-88b9-733771799784}VMNAMESnapshotsF68A0FFE-F6AC-4605-9B55-B80DB89098B3.xml] for reading.
Cause
This issue is caused by the snapshot path in the VM ‘s configuration being different from the actual path on a file system in terms of symbols capitalization. You can confirm this by comparing paths in bold in the Task.<VM NAME>.<VM UUID>.log file:
[22.01.2019 19:39:09] <28> Info [AP] (65e8) output: <snapshots>
[22.01.2019 19:39:09] <28> Info [AP] (65e8) output: <data_root type=”string”>C:Temp<VM name></data_root>
[22.01.2019 19:39:09] <28> Info [AP] (65e8) output: <list>
[22.01.2019 19:39:09] <28> Info [AP] (65e8) output: <size type=”integer”>0</size>
[22.01.2019 19:39:09] <28> Info [AP] (65e8) output: </list>
[22.01.2019 19:39:09] <28> Info [AP] (65e8) output: </snapshots>
[22.01.2019 19:39:09] <11> Info [AP] (65e8) command: ‘file2textn\?GLOBALROOTDeviceHarddiskVolumeShadowCopy16temp<VM NAME>Snapshots<VM UUID>.xmln2097152n’
[22.01.2019 19:39:10] <10> Info [ReconnectableSocket] Stop confirmation was sent on [c1d84e94-b09b-4039-a8dc-4973e12934fc].
[22.01.2019 19:39:10] <23> Error [AP] (65e8) error: The system cannot find the file specified.
[22.01.2019 19:39:10] <23> Error Failed to open file [\?GLOBALROOTDeviceHarddiskVolumeShadowCopy16temp<VM NAME>Snapshots<VM UUID>.xml] in readonly mode.
Solution
There are two methods for correcting this issue depending on your preference:
Change the snapshot path in VM configuration manually
- Connect to the Hyper-V host and go to VM Configuration of VM in question
- Go to Checkpoints tab and choose ‘Browse…’ underneath the snapshot path
- Update the path.
Install a hotfix for Veeam Backup & Replication 9.5 Update 4 (build 9.5.4.2615):
Download
N0te:- Ensure that all jobs are in a stopped state before procceding this step
- Stop all services on the Veeam Backup server that begin with Veeam. (PowerShell: gsv Veeam* | spsv )
- Navigate to the Veeam installation folder on the Veeam Backup Server (by default it is C:Program FilesVeeamBackup and ReplicationBackup)
- Rename the Veeam.Backup.Core.dll file to Veeam.Backup.Core.dll_backup
- Replace the files listed in the previous step with those found in the hotfix package
- Start Veeam services on Veeam Backup server. (PowerShell: gsv Veeam* | sasv )
Reference
Conclusion
We have followed the steps mentioned on the Veeam KB and the issue fixed.