foggy wrote:There's no contradiction, since initially I said that generally you can use your existing files for mapping. However, after getting more details about your scenario, I added that it is not possible to map a single job to several backup chains from different jobs (even with per-VM setting enabled), since there's no combined VBM file for that.
My suggestion was to create a new backup copy job that would have three jobs you want to combine as source and run it locally at remote site (so no need to transfer data to a new location). As a result you will get a new set of VBK files (per-VM) for all VMs in those three jobs and will be able to map your new remote combined job to it.
Zew wrote:but then I'd be back to the old school style. Build BCJ pointing to original source, local repo.
Zew wrote:Stop the BCJ, move the data to a mobile device (generall a USB HDD) manually move it to the Cold site, Copy the contents to my NAS. Adjust permissions. Scan the repo, and then map the job.... basically defeating teh exact purpose of my initial question. use old backup data for "seed" of new BCJ
Users browsing this forum: Bing [Bot], Google [Bot] and 6 guests