Hello,
I am hoping someone can shed some light on an issue I'm having. We are using Veeam B&R 11 Enterprise Plus Edition. We have 4 ESXi servers (not using VCenter) and we had to restore one of the servers using a backup OS that was cloned. Because of that, we had some VMs that needed to be registered again from the datastore. After registering those VMs, it seems Veeam got its morefIDs mixed up (again) and I had to manually go through each backup job and choose the correct VM to be backed up. In some cases, the VM was still the right one with a 0B size, so it had to be removed and added back. In other cases, the VM was not correct, so it had to be removed and the right VM had to be added. In this case, is there a way to avoid this? Is there a fix in a later version?
Any answers/theories would be greatly appreciated..
Thank you.
I am hoping someone can shed some light on an issue I'm having. We are using Veeam B&R 11 Enterprise Plus Edition. We have 4 ESXi servers (not using VCenter) and we had to restore one of the servers using a backup OS that was cloned. Because of that, we had some VMs that needed to be registered again from the datastore. After registering those VMs, it seems Veeam got its morefIDs mixed up (again) and I had to manually go through each backup job and choose the correct VM to be backed up. In some cases, the VM was still the right one with a 0B size, so it had to be removed and added back. In other cases, the VM was not correct, so it had to be removed and the right VM had to be added. In this case, is there a way to avoid this? Is there a fix in a later version?
Any answers/theories would be greatly appreciated..
Thank you.
Statistics: Posted by aobrien — Oct 04, 2024 2:33 pm