Good day, could you please advise the optimal way to accomplish the following task?
There are two geographically separate sites: Site A and Site B. Each site has its own Backup & Replication (BR) server, and all backups are stored in their respective hardened repositories. Additionally, Server A sends Backup Copy jobs to an additional hardened repository.
Sites A and B are connected via a dedicated L2 channel with limited bandwidth.
The task is:
To copy primary backups from Site B to Server A.
Then, have Server A forward these backups to its additional hardened repository.
What is the best way to implement this?
-
- Novice
- Posts: 3
- Liked: 1 time
- Joined: Jun 04, 2025 12:43 pm
- Full Name: Andrew Akimov
- Contact:
-
- Product Manager
- Posts: 10612
- Liked: 2855 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Copy backup Betwenn Server B and Server A
Hi Andrew,
Short answer:
The recommended and supported approach is to use a single backup server to manage jobs and repositories across both sites. Two backup servers cannot achieve what you are looking for. May I ask why you are using two backup servers?
Longer explanation:
To copy backups from one repository to another, both repositories must be connected to the same backup server. Sharing a Hardened Repository (VHR) between multiple backup servers might technically work, but it is not supported.
If you connect VHR from Site A to Server B and have Server B copy its backups to VHR A. To work with this backups, Server A also need access to the folder path with the backups from Server B on VHR A — another unsupported scenario. The same folder path should never be added to more than one backup server.
Server A rescans and imports the copied backups from Server B now, but those imported backups (not attached to a backup job) cannot be copied by a backup copy job to a third repository. Backup Copy Jobs only copy backups attached to a backup job. Imported backups cannot be copied.
Best,
Fabian
Short answer:
The recommended and supported approach is to use a single backup server to manage jobs and repositories across both sites. Two backup servers cannot achieve what you are looking for. May I ask why you are using two backup servers?
Longer explanation:
To copy backups from one repository to another, both repositories must be connected to the same backup server. Sharing a Hardened Repository (VHR) between multiple backup servers might technically work, but it is not supported.
If you connect VHR from Site A to Server B and have Server B copy its backups to VHR A. To work with this backups, Server A also need access to the folder path with the backups from Server B on VHR A — another unsupported scenario. The same folder path should never be added to more than one backup server.
Server A rescans and imports the copied backups from Server B now, but those imported backups (not attached to a backup job) cannot be copied by a backup copy job to a third repository. Backup Copy Jobs only copy backups attached to a backup job. Imported backups cannot be copied.
Best,
Fabian
Product Management Analyst @ Veeam Software
-
- Novice
- Posts: 3
- Liked: 1 time
- Joined: Jun 04, 2025 12:43 pm
- Full Name: Andrew Akimov
- Contact:
Re: Copy backup Between Server B and Server A
"The initial deployment of a local BR server at Site B was aimed at minimizing downtime of the critical service. I wanted to clarify if there’s a way to expand its functionality, but as I see, the most optimal approach remains having Server A perform backups and then upload copies to an additional hardened repository. By the way, is there any limit on the number of additional copies for Backup Copy jobs?"
Who is online
Users browsing this forum: No registered users and 12 guests