Feature Request: Allow Map Backup Agent Backup Copy Job

[jchr]

I was surprised to find out there is no way to map an existing backup repository for physical servers like there is for virtual machine backups. After using Veeam for over a year for our production virtual environment, we purchased more licensing to protect out main office the same way. The addition of physical server support we could use one piece of software that we trust to backup our entire company. We still mantain a couple physical file servers and an exchange server. With out an option to map backup for the backup copy job we can not create a seed for offsite storage. This is a problem because of there size and the amount of bandwidth/time it takes to do the inital backup copy. Replacing the offsite backup storage device will be another problem with the agent backup copy job, as we will have to start over with a new backup copy job without a mapping option.

[Dima P.]

Hello jchr,

Unfortunately, it's true that backup copy does not support mapping for backup files produced by agents. We plan to add this functionality in one of the upcoming releases. Thanks.

[jchr]

Is there any timeline for adding this feature for physical server backups? Replacing the backup hardware is on my list of projects for next year. I would like to be able to move the existing backup copy archives and keep the GFS continuing without having to start over for sure since seeding physical server backups is not possible either. Thanks.

[veremin]

It's definitely on our road map, but we cannot comment on ETA. Based on the results of testing, this feature might be implemented either in upcoming update or later. Thanks.