Use VBR backup copy job to copy specific GFS recovery points from a VBAZ appliance

[ckalkmer]

Use backup copy job to copy only specific recovery points from a VBAZ appliance

We have VMs in Azure we protect with a Veeam Backup for Azure (VBAz) appliance. Each job has 3 schedules configured, creating (GFS) recovery points with Daily, Weekly and Monthly retention storing each in their own repository. We have a need to copy only the Monthly recovery points outside of Azure. To do this we have:
Deployed a VBR server
Added the VBAz appliance and credentials of the associated repos to the VBR server
Added a backup copy job to the VBR server
Attempted to target only the monthly recovery points in the Backup Copy job
This last point has proved very frustrating. Currently Azure backups can only be added to backup copy jobs using the “from backups” workflow in the add objects screen. The “from backups” window only shows the name of the job that created the backups. If you have your various GFS schedules placing backups in different repos as most people do, you simply see the job name repeated for each tier of backup – with no hint as to what repo they actually reside in. The current workaround is to remove the credentials for repos of a given job where daily and weekly points live, then go back to the add objects screen and now you will only see the job mentioned once – these are your monthly recovery points.

This process to say the least is sub-optimal. Does anyone know of a better way to do this OR is it on the roadmap to expose more information about the backups you are selecting in that screen? Ideally to show specifically - what repository the backups you are selecting reside in?

[lyudmila.ezerskaya]

Hi Chris,

Let me check this and I’ll get back to you.

[lyudmila.ezerskaya]

You are right—the Backup Copy Job wizard currently displays the same name for all policy jobs without details on the schedule or repository. We are glad you found a workaround that works for your infrastructure.

Thank you for bringing this to our attention; we’ll consider enhancing this behavior in future releases.