I have two sites (as in physical offices).
- Site A has an ESXi server.
- Site A also has a separate physical Windows server that acts as Veeam backup server and Veeam Backup Proxy. It backups the VM's from the ESXi server.
- Site A has another physical server with a Veeam Linux repository where the backups are stored.
- Site B has an ESXi server which will retire soon. It's not needed anymore.
- Site B currently also has a Veeam backup and Veeam proxy server but this server will retire soon. It's not needed anymore.
- Site B has a NAS SMB repository which stores offsite backups from site A and backups from the site B ESXi server. These last backups (from the site B ESXi server) are soon not performed anymore since the ESXi server will retire.
Since Veeam backup server and ESXi server on site B will retire soon, I'm looking for the best approach to still keeping storing site A's offsite backups on the site B NAS SMB repository. I'm thinking that site B only needs a Veeam backup proxy. Would that assumption be correct? Can I just install a Veeam Linux backup proxy on site B, add it to the site A offsite jobs and have the most optimal configuration? Or is the backup proxy on site B not needed?
(P.s. I know a NAS SMB isn't the most ideal repository but we need to keep that)
Thanks in advance for the help
-
- Enthusiast
- Posts: 35
- Liked: 1 time
- Joined: Feb 10, 2017 10:07 am
- Contact:
-
- Veeam Software
- Posts: 2838
- Liked: 650 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Infrastructure advise
Hi xmzmc,
Backup copies are the way to go with this task indeed.
As far as infrastructure goes, will make a small semantic correction, but you need a Gateway Server on Site B, not a proxy.
Network shares cannot host our datamover binaries, so we need a gateway server to access them, in this case a Windows based one. This also helps with the cross-site traffic as the connection will be more resilient to interruptions as opposed to connecting to the SMB share cross-site (the veeam datamovers can gracefully handle temporary interruptions, a direct SMB connection cross-site would be closed on error). Be sure to size the gateway like a normal backup repository.
Backup copies are the way to go with this task indeed.
As far as infrastructure goes, will make a small semantic correction, but you need a Gateway Server on Site B, not a proxy.
Network shares cannot host our datamover binaries, so we need a gateway server to access them, in this case a Windows based one. This also helps with the cross-site traffic as the connection will be more resilient to interruptions as opposed to connecting to the SMB share cross-site (the veeam datamovers can gracefully handle temporary interruptions, a direct SMB connection cross-site would be closed on error). Be sure to size the gateway like a normal backup repository.
David Domask | Product Management: Principal Analyst
-
- Enthusiast
- Posts: 35
- Liked: 1 time
- Joined: Feb 10, 2017 10:07 am
- Contact:
Re: Infrastructure advise
Thank you David. I will go ahead and install a gateway server on site B instead. Have a nice day 

Who is online
Users browsing this forum: No registered users and 2 guests