-
- Service Provider
- Posts: 205
- Liked: 22 times
- Joined: Feb 01, 2016 10:09 pm
- Contact:
Restored Virtual machine with same settings but wont backup now
WE had one of our virtual machines get corrupted for whatever reason.
WE restored the VM with veeam with the same settings.....entire vm.
This all went fine.
The backup ran again the following night but failed saying that vm is no longer available. The job fails and states "Virtual Machine <VM NAME> is unavailable and will be skipped from processing.
It is still defined in the job but veeam cant seem to see the newly restored vm is the same as the old vm we restored.
Does the guid or identifier change or something? DO i need to add the newly restored vm back to the job again becuase of this ? If i click the "edit settings" on the job i can see the vm listed under "virtual machines" but it lists as 0 bytes. "Recalculate" doesnt do anything. DO i need to remove and readd it to pick up the restored vm?
This is very odd. IF i do remove and readd it........i assume it will start a whole new backup of that vm and the history will still be there but start a new chain based on the newly restored vm?
WE restored the VM with veeam with the same settings.....entire vm.
This all went fine.
The backup ran again the following night but failed saying that vm is no longer available. The job fails and states "Virtual Machine <VM NAME> is unavailable and will be skipped from processing.
It is still defined in the job but veeam cant seem to see the newly restored vm is the same as the old vm we restored.
Does the guid or identifier change or something? DO i need to add the newly restored vm back to the job again becuase of this ? If i click the "edit settings" on the job i can see the vm listed under "virtual machines" but it lists as 0 bytes. "Recalculate" doesnt do anything. DO i need to remove and readd it to pick up the restored vm?
This is very odd. IF i do remove and readd it........i assume it will start a whole new backup of that vm and the history will still be there but start a new chain based on the newly restored vm?
-
- Veeam Software
- Posts: 752
- Liked: 172 times
- Joined: Jan 22, 2015 2:39 pm
- Full Name: Stefan Renner
- Location: Germany
- Contact:
Re: Restored Virtual machine with same settings but wont backup now
Yes the morefID will be different and with that the VM is new to VMware and veeam.
Just re-add it to the job an it will work again.
Just re-add it to the job an it will work again.
Stefan Renner
Veeam PMA
Veeam PMA
-
- Service Provider
- Posts: 205
- Liked: 22 times
- Joined: Feb 01, 2016 10:09 pm
- Contact:
Re: Restored Virtual machine with same settings but wont backup now
Thanks. I figured that might be the case as the job will remove/delete the existing vm and then "restore". I just wasnt sure if there was some magic under the hood that kept the ID of the vm somehow on restore.
Thank you for the prompt reply / clarification.
Thank you for the prompt reply / clarification.
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Oct 06, 2024 5:47 pm
- Contact:
Re: Restored Virtual machine with same settings but wont backup now
I had this exact same question / scenario, And it does seem that you have to manually edit the backup job to point to the newly restored VM.
However that seems counterintuitive to me (I'm sure post restore, many either don't know about this or forget , and thus have missing VMs from their backups), is there any way to work around this? ie Can you tell veeam to back up based on the VM name or a wild card perhaps (or tags?) ?
thanks
However that seems counterintuitive to me (I'm sure post restore, many either don't know about this or forget , and thus have missing VMs from their backups), is there any way to work around this? ie Can you tell veeam to back up based on the VM name or a wild card perhaps (or tags?) ?
thanks
-
- Product Manager
- Posts: 10702
- Liked: 2901 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Restored Virtual machine with same settings but wont backup now
You can add your VMs through vSphere tags or using containers (such as vCenter, clusters, ESXi hosts, or folders). Adding them by container ensures that all virtual machines within that container are protected by the Job.
Best,
Fabian
Best,
Fabian
Product Management Analyst @ Veeam Software
-
- Veeam Vanguard
- Posts: 649
- Liked: 162 times
- Joined: Aug 13, 2014 6:03 pm
- Full Name: Chris Childerhose
- Location: Toronto, ON
- Contact:
Re: Restored Virtual machine with same settings but wont backup now
Tags are a great way to do backups as you can create different categories and jobs associated to each tag, etc.
-----------------------
Chris Childerhose
Veeam Vanguard / Veeam Legend / Veeam Ceritified Architect / VMCE
vExpert / VCAP-DCA / VCP8 / MCITP
Personal blog: https://just-virtualization.tech
Twitter: @cchilderhose
Chris Childerhose
Veeam Vanguard / Veeam Legend / Veeam Ceritified Architect / VMCE
vExpert / VCAP-DCA / VCP8 / MCITP
Personal blog: https://just-virtualization.tech
Twitter: @cchilderhose
Who is online
Users browsing this forum: No registered users and 6 guests