After the system had come back up and online, the first backup took place, and while the backup went successfully, for some reason, a few of the jobs (3 out of 4 total jobs) decided to overwrite the VBM data and the VBM file was blanked and a full backup was done. This introduced some pain points obviously and we attempted to contact Veeam and get the data back into the VBMs (case 00849617). Unfortunately they were unable to assist and for now, if I want to do a restore of any historical data from the time before the server rebuild, I have to import the related .BAK file from the date/timeframe I want to restore. Not a huge deal, just an inconvenience as most of our backups are quite large and take 5-15 minutes to import.
Fast forward to today, I have to perform a restore. We backup a remote office's primary file store to the remote office's local Data Domain device. The backup job itself is controlled from the central Veeam server in the data center. The backup job directs the information to be backed up to the remote office's local repository (the Data Domain) from the remote site's Veeam proxy. Typically when the remote office requests a restore, we simply import the .VBM file to the local Veeam proxy and initiate the restore from there. This prevents us from having to pull the data over the WAN for restores. I went to initiate the restore per usual yesterday and the import went fine, but when initiating the restore file from guest wizard, on the choose virtual machine screen, I received the following error:
I have a current open case with Veeam (00875663) to try and deal with this, but I was wondering if anyone on the forums has seen this before. I searched the forums and there was a similar error message, but it seemed to have to do with backups and not restores.Failed to enumerate backup OIBs. Backup: "veeambackupname_imported". Object '<actualguidwithheld>' was not found"