Recreate vbm file

[Erhard]

I hit a situation where a NAS became defective and we had to start a new backup change on a temporary device.
We were able to repair and upgrade the original NAS and we could salvage the old backups.
So we changed things back to the original NAS by first copying new existing backups from the temporary device to the original one.
We couldn't use the "Move Backup" feature as the amount of data to move would have taken half a week preventing actual backups to occur so we used Robocopy from a Windows server.
Then I copied the old and salvaged backups from an USB hdd to the original NAS into the same location where the actual backups reside.
Since two vbm files cannot exist in the same location there was no way to copy the old vbm.
Unfortunately I was wrong in so far that I thought Veeam BR would be able to import the old backup files, simply update the existing vbm file (or create a new one) and properly continue maintaining restore points including GFS.

While I think that Veeam BR is a very reliable backup and recovery solution I fail to understand that such a self evident function is not available.

Beyond this I think that there is some room for improvement in other areas as well:

- Veeam should maintain the number of restore points on removable media PER MEDIUM instead of unevenly distributing the files across them
- Veeam should name the removable medium used for backup in the report so that one can see which medium caused a problem if any occurred
- Veeam should mark those VMs that are already included with a job in the list when adding one and there should be a column showing the host server the VMs reside on
- Veeam's Move Backup feature should merely replicate the backups to the destination instead of being unable to run actual backup jobs while a move is in progress

Cheers

[david.domask]

Hi Erhard,

Thank you for the detailed description of the situation, and I'm sorry to hear about the defective NAS situation.

I have an immediate question on the situation though, does original VBM file still exist? It may still be possible to import the old chain via VBM if the VBM is not corrupted; I need to clarify that even if the VBM is usable and suitable, we cannot "merge" the two chains together, but there would be a few more options on how to proceed.

As for your requests, I will note them for review.

> - Veeam should mark those VMs that are already included with a job in the list when adding one and there should be a column showing the host server the VMs reside on

For this one on the first part about VMs already in the job, can you describe the situation you're trying to avoid a bit more? I do see that right now it just quietly will let you select and "add" the same VM, but it won't have any effect on the job; did I maybe misunderstand and you mean when a VM is added to multiple jobs?