Just updated to 9.5u4a - REALLY miss the repository copy job!

[vmff]

We used to run backup copy jobs based on restore points in an entire B&R Repository. It made it really easy to have a backup copy job that didn't need to be updated anytime another job was created, and we'd still have our restore points on the backup copy repository.

Why was this option removed in 9.5? What is the intended workaround? You want us to make sure and not miss updating any jobs that are targeted at that repository?

[Vitaliy S.]

Hi,

Can you please clarify what option you're referring to? Backup copy job never allowed copying the entire repository, but it always had an option to select backup data from either VI, backups or from jobs.

Thanks!

[tsightler]

As far as I know, only Backup to Tape jobs had (and still have) the ability to select the entire repository.

[vmff]

You're right, I was thinking about the selection of all objects in a repository to a tape job; as we also changed from a tape device during this transition at the same time. Would really like to be able to do the same thing as a regular copy job... guess I don't follow the logic why offer it for tapes but not disk?

[foggy]

Backup copy job doesn't copy files, it copies a particular VM state, so you have to select VMs to process, not their backup files.

[Vitaliy S.]

The main idea was to allow granular selection of VMs you want to have a secondary copy for without grabbing all the files from the repository.