This was always an unsupported call and I'm not sure of the new one, however, can I ask why you need to create a new VBM file? I believe that v8 allows you to map to backups that don't have a VBM file so there's not a lot of reasons that a VBM would be required.
You mean two backup jobs that you want to merged? If so, why not to create a backup copy job selecting both backup jobs as a source for it and letting it run initial cycle. Once that operation is done, you will be able to create a new backup job and map to the resulting backup (created by the backup copy job). Thanks.
Recreating a VBM is something I've done on a number of occasions, especially when a VBM file has become corrupt. I've encountered a number of instances where this is the case using Windows deduplication in Server 2012. The actual backup files are 100% consistent, simply the VBM is corrupt. There must be a way to resolve this?
Running an active full is not an option due to
a). Backup repository space
b). Backup window
tsightler wrote:Yeah, I realized after I typed that last post that it didn't make any sense. I guess that's what I get for trying to answer a post at 1AM.
So you don't have the original VBM? Unfortunately I don't know what the new backend call would be to force creation of a new VBM file from scratch.
Tom, who do we need to speak to for us to figure this out?
I got this problem when moving my repository to a different location. I have moved repository data serveral times without any problem, but this time i got an error during import. I figure that the vmb file has been corrupted since my individual vbk files can be imported.
However I need to remap the repository to the job but cannot do this if I just import the vbm files at it seems. I probably need the vbm to solve this.
Had I been running a previous version the script might have worked, but in v8 it isn't working anymore.
So Veeam, can we find a way to do this as it was possible to do with previous versions?