-
- Veteran
- Posts: 528
- Liked: 104 times
- Joined: Sep 17, 2017 3:20 am
- Full Name: Franc
- Contact:
Feature request: Restored VMs removed from jobs -> autocorrect MoRef id
Hi,
we have some jobs that have specific VMs added or excluded from them. In these job we don't use tags. Now, when we have restored such a vm from backup, the jobs still lists them, but they aren't valid anymore. This is because the moREF id has changed. You have to manually remove the old VMs from the job and add the restored VM to it. It would be nice if Veeam would detect this situation on a full restore operation and corrects the jobs automatically. It already know that it restores an existing VM with a backup so it can also update the moREF id's of that VM in the jobs it's included.
p.s. As a workaround I now use the option to only restore the vmdks instead of the whole VM. This also works, since the moREF id isn't changed by that action.
Franc.
we have some jobs that have specific VMs added or excluded from them. In these job we don't use tags. Now, when we have restored such a vm from backup, the jobs still lists them, but they aren't valid anymore. This is because the moREF id has changed. You have to manually remove the old VMs from the job and add the restored VM to it. It would be nice if Veeam would detect this situation on a full restore operation and corrects the jobs automatically. It already know that it restores an existing VM with a backup so it can also update the moREF id's of that VM in the jobs it's included.
p.s. As a workaround I now use the option to only restore the vmdks instead of the whole VM. This also works, since the moREF id isn't changed by that action.
Franc.
-
- Product Manager
- Posts: 20413
- Liked: 2302 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Feature request: Restored VMs removed from jobs -> autocorrect MoRef id
Can you specify what kind of restore was used? Full VM Restore to Original Location, Full VM Restore to Different Location, Instant VM Recovery, etc.? Thanks!
-
- Veteran
- Posts: 528
- Liked: 104 times
- Joined: Sep 17, 2017 3:20 am
- Full Name: Franc
- Contact:
Re: Feature request: Restored VMs removed from jobs -> autocorrect MoRef id
Hi,
full vm restore to original locatin.
Franc.
full vm restore to original locatin.
Franc.
-
- Product Manager
- Posts: 20413
- Liked: 2302 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Feature request: Restored VMs removed from jobs -> autocorrect MoRef id
Hmm, if my memory serves me well, we added morefID preservation logic for in-place restores a few years ago. So, do you mind opening a ticket? In the meantime I will confirm few things internally. Thanks!
-
- Veteran
- Posts: 528
- Liked: 104 times
- Joined: Sep 17, 2017 3:20 am
- Full Name: Franc
- Contact:
Re: Feature request: Restored VMs removed from jobs -> autocorrect MoRef id
Ok, will do some more testing also.
-
- Veteran
- Posts: 528
- Liked: 104 times
- Joined: Sep 17, 2017 3:20 am
- Full Name: Franc
- Contact:
Re: Feature request: Restored VMs removed from jobs -> autocorrect MoRef id
In this case it was an accidental delete of a vm and then a full restore to original location, can that be a difference?
-
- Product Manager
- Posts: 20413
- Liked: 2302 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Feature request: Restored VMs removed from jobs -> autocorrect MoRef id
Correct, this explains the morefId change. Thanks!
-
- Veteran
- Posts: 528
- Liked: 104 times
- Joined: Sep 17, 2017 3:20 am
- Full Name: Franc
- Contact:
Re: Feature request: Restored VMs removed from jobs -> autocorrect MoRef id
Ok, but wouldn’t it be possible to restore the morefid in this case also? Now it behaves differently (I haven’t it tested yet by overwriting the existing vm to confirm).
-
- Chief Product Officer
- Posts: 31814
- Liked: 7302 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Feature request: Restored VMs removed from jobs -> autocorrect MoRef id
It's not possible. Even if we store moRef ID as a part of the backup and could have easily assign it to the newly created VM, vSphere does not provide any API to do this, because VMware does not want 3rd party software to manage those IDs.
Restore to the original location by overwriting the existing VM preserves the ID because we purposely don't delete the actual VM object in this case to avoid the loss of ID, and instead restore virtual disks only.
Restore to the original location by overwriting the existing VM preserves the ID because we purposely don't delete the actual VM object in this case to avoid the loss of ID, and instead restore virtual disks only.
-
- Veteran
- Posts: 528
- Liked: 104 times
- Joined: Sep 17, 2017 3:20 am
- Full Name: Franc
- Contact:
Who is online
Users browsing this forum: Google [Bot] and 40 guests