-
- Expert
- Posts: 107
- Liked: 6 times
- Joined: Sep 21, 2022 6:53 am
- Full Name: Keita Kuroki
- Contact:
Traffic flow of agent backup
Hi,
I would like to know traffic flow of agent backup.
In current situation,
- there are backup target physical servers in site A.
- there is Veeam Backup Server on AWS EC2 (All in one install to one EC2).
- Site A and AWS are connected by Internet VPN.
In the above situation, I would like to backup physical servers to NAS in siteA.
In this situation, how is the backup data traffic ?
I care for backup data will flow "Site A physical server > AWS Veeam Server > Site A NAS"
Best regards
Kei
I would like to know traffic flow of agent backup.
In current situation,
- there are backup target physical servers in site A.
- there is Veeam Backup Server on AWS EC2 (All in one install to one EC2).
- Site A and AWS are connected by Internet VPN.
In the above situation, I would like to backup physical servers to NAS in siteA.
In this situation, how is the backup data traffic ?
I care for backup data will flow "Site A physical server > AWS Veeam Server > Site A NAS"
Best regards
Kei
-
- Product Manager
- Posts: 9848
- Liked: 2607 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Traffic flow of agent backup
Hi Kei
Let's say, you add the NAS as a Veeam Backup Repository with the Veeam Backup server in AWS as the gateway server. Then you create a Veeam Agent Backup Job which writes the data to that NAS backup repository. The traffic flow will be:
- Veeam Agent on Site A> Veeam Backup Server in AWS > NAS on Site A
The Traffic will always go over the configured gateway server. Veeam Agent will not directly write backups to the SMB share if the NAS was added as a Veeam backup repository.
Alternative for better performance and stability: If you have a physical/virtual windows machine in Site A, you can use it as a Gateway server for the NAS SMB share. Then the Traffic flow will stay in Site A.
You can also configure Shared Folder as a destination in the step below. The traffic will then flow directly to the NAS:
- Veeam Agent on Site A > NAS on Site A
Thanks
Fabian
Let's say, you add the NAS as a Veeam Backup Repository with the Veeam Backup server in AWS as the gateway server. Then you create a Veeam Agent Backup Job which writes the data to that NAS backup repository. The traffic flow will be:
- Veeam Agent on Site A> Veeam Backup Server in AWS > NAS on Site A
The Traffic will always go over the configured gateway server. Veeam Agent will not directly write backups to the SMB share if the NAS was added as a Veeam backup repository.
Alternative for better performance and stability: If you have a physical/virtual windows machine in Site A, you can use it as a Gateway server for the NAS SMB share. Then the Traffic flow will stay in Site A.
You can also configure Shared Folder as a destination in the step below. The traffic will then flow directly to the NAS:
- Veeam Agent on Site A > NAS on Site A
Thanks
Fabian
Product Management Analyst @ Veeam Software
-
- Expert
- Posts: 107
- Liked: 6 times
- Joined: Sep 21, 2022 6:53 am
- Full Name: Keita Kuroki
- Contact:
Re: Traffic flow of agent backup
Hi Fabin
Thank you for quick response every time.
I understood the data traffic flow.
I would like to know bellow alternative way.
> You can also configure Shared Folder as a destination in the step below. The traffic will then flow directly to the NAS:
Now, I am trying to make backup job in Veeam console on EC2 Veeam Server, but I cannot find "Destination".
So I can only select the backup repository.
I assume this operation is conducted on target physical server , right ?
Best regards
Thank you for quick response every time.
I understood the data traffic flow.
I would like to know bellow alternative way.
> You can also configure Shared Folder as a destination in the step below. The traffic will then flow directly to the NAS:
Now, I am trying to make backup job in Veeam console on EC2 Veeam Server, but I cannot find "Destination".
So I can only select the backup repository.
I assume this operation is conducted on target physical server , right ?
Best regards
-
- Product Manager
- Posts: 9848
- Liked: 2607 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Traffic flow of agent backup
You‘re welcome.
You can configure it on the backup server.
Shared Folder are only available for „Managed by Agent“ backup policies.
„Managed by Server“ backup jobs require a veeam backup repository.
Thanks
Fabian
You can configure it on the backup server.
Shared Folder are only available for „Managed by Agent“ backup policies.
„Managed by Server“ backup jobs require a veeam backup repository.
Thanks
Fabian
Product Management Analyst @ Veeam Software
-
- Expert
- Posts: 107
- Liked: 6 times
- Joined: Sep 21, 2022 6:53 am
- Full Name: Keita Kuroki
- Contact:
Re: Traffic flow of agent backup
Hi Fabin
Thanks a lot.
I could find how to backup to Shared Folder directly.
Best regards.
Thanks a lot.
I could find how to backup to Shared Folder directly.
Best regards.
-
- Enthusiast
- Posts: 51
- Liked: 10 times
- Joined: May 18, 2021 1:55 pm
- Location: Slovakia
- Contact:
Re: Traffic flow of agent backup
You can also configure a duplicate entry of the backup repository on the target host (give it the backup repository role). Preferably into its own subdirectory or file share. This plus agent mode backup causes all the work to be done on the single target host. The downside is that the host will receive credentials to write to the NAS. If you don't fully trust the host, either configure the repository on a nearby on-premises trusted server, or at least ensure that a compromise of the host's NAS credentials won't compromise other backups on the NAS (hardened / immutable repo, separate credentials and subfolders/shares for each backup target, NFS share restriction to each host's IP only, etc).
Who is online
Users browsing this forum: Google [Bot] and 8 guests