Simple Deployment Question

[svenv]

Ahoy Veeam Team,

first time Veeam user & first time poster here.

Glancing over the Veeam Technical Documentation and forum posts I am still a bit lost with a relatively simple Veeam Deployment. Maybe someone can help me out. I'm asked to migrate a backup solution to Veeam and I am still stuck in the planning phase because I don't know what components I should use.

I have a on-site (Windows) Backup Server (serving as Backup server, proxy and repository) just like the Simple Deployment Scenario in the helpcenter documentation for scheduled full, differential and incremental backups.
A second off-site (Windows again) Backup Repository Server (this should be the destination for Backup Copy jobs, and hold some (TBD) copies of the last full backups) reachable via site-to-site VPN.
And last, directly connected to the off-site repository, a tape loader to archive the copied backups from the off-site repo in regular intervals.

It seems I can use the New Backup Repository wizard to setup my off-site repository and all required components (Data Mover and/or? Backup Proxy) will be installed automatically. So far so good. One Veeam Backup & Replication installation plus some automatically installed components.
But do I need any additional components to archive the off-site copies to tape? And can the off-site backups copied directly to the attached tape storage (without the data flowing to the Backup & Replication server and then back again to the off-site location)?

Any hints are welcome.

thx Sven

[PetrM]

Hello and Welcome to Veeam R&D Forums!

Did you have a chance to take a look at this page about Tape Devices deployment? You may just enable the tape server role on the server with the directly attached tape storage.

Thanks!

[svenv]

Thanks Petr!

That definitely helped. But I'm still not sure about the data flow. From the page you sent I gather the backups are copied from the "Veeam backup server", which is the on-site server in my setup. This is what I'd like to avoid. The data is copied off-site already at this point, and should be copied from the off-site repository server to the tape server (which would be the same server in this setup) instead.

Maybe I can define source explicitly for the archiving part? Even if is possible to set the source (off-site repo) and destination (tape server / tape loader) is the Data Mover smart enough not to copy the data around twice via the VPN connection between the on- and off-site locations.

Best regards,
Sven

[svenv]

It's a little hard for me to put my problem into writing, language barrier an all that.

What I am trying to achieve is something like this (diagrams.net link).

Instead of this.

[PetrM]

Hello,

I'm not certain how you arrived at this conclusion, your first diagram is exactly what you will get as long as the tape server runs on the same machine with the repository, there is no data traffic back to Veeam server. As mentioned on this page:

When a backup to tape job runs, it does not process source machines: it locates already existing backups and copies them from backup repository to tape.

Thanks!

[svenv]

I don't know how I missed that.

Thanks again.