Include all backups in repository-level copy jobs

[DanielJ]

Are there any plans to include all types of backups when creating a copy job for a whole repository? That would be both convenient and logical.

[Gostev]

@Dima P. which are we missing today?

[Dima P.]

Hello folks,

1. Enterprise application backups: it's a dedicated backup copy job with it's own application backup specifics and logic.
2. NAS/OS backup: it's built-in to the NAS/OS backup jobs.
3. Backup copy for Amazon EC2, Microsoft Azure and Google Cloud backups: there is a limitation that requires specific backup to be selected on a first place. This one is already in our books as we plan to address it in the upcoming versions.

Daniel, any workload you are specifically interested in?

[DanielJ]

A common scenario is that we place a hardened repository at a customer, backup all the customer's workloads to it, and then copy everything to our central storage. This has so far included vm backups, agent backups and NAS backups. So in my case it's the NAS backups that must have an extra copy job (and building this copy job into the backup job is a design choice which is inconsistent and difficult to understand).

[Dima P.]

Understood, thank you! It's a valid use case and we will discuss with the team how to improve the current experience.