Gateway server for NAS repo

[waelNa]

I have 2 sites each with Synology NAS repository. VBR runs on site A to local Synology repository, however backup speed is a little slow
i want to create backup copy job to send the same data to Synology on site B.
1-how I install the gateway server on site B? I understand that I need to have a Windows machine on site B that running as gateway server. I need clarification for this part, if this machine would need to have a full installation of VBR, or I just need to add that machine to VBR on site A as a managed server
2- permissions: which credentials I'll add to VBR (the gateway server cred or Synology NAS cred on site B)
3- do I need to have WAN acceleration enabled on any of the sites?
4- I understand that CDP option is applicable to VMware server only. what is the closest option to apply CDP for Hyper-V server?
5- if I can run the backup task every 2 hours, would that affect performance on production or backup ?

Case # 07420350
thanks

[Andreas Neufert]

1 and 2
Go to the Veeam Server
Go to Backup Infrastructure and add a Windows/Linux System on site 2 as managed server. You need to give Administrator rights (On linux root or user with elevated rights needed). Software deployment happens automatically.
Add a new SMB/NFS repository and give there credentials that gives you full access to the files and file attributes and select the above created managed server.
3
No this is not required, but if you use Windows it can help to save bandwidth. If you have Enterprise Plus or Veeam Unversal Licensing you can use it. Think about it like this. It takes time to process things and IO, but if the WAN link is the bottleneck in your processing, then it can help to speed up things.
4
In Hyper-V you can replicate as well the VMs to the other sides Hyper-V system, and failover as needed. Replication can be started every x minute if you like.
Replicas are usually done in addition of the backups as you can not keep that long backup chains there and granular restore methods are limited. It is more for fast disaster recovery.
5
Running backups or replicas high frequent are usually not that bad. That said you need to know that additional data is processed more frequently (additional overhead for your primary storage) and as well if you enable consistency (Veeam Guest processing), then the consistency mode for applications and the filesystem can slow down the environment further, because they write the RAM to disk and prepare consistency on disk.

[waelNa]

thank you Andreas for your reply,
can you please explain the best practice to implement the replication task between the 2 sides for best performance. and if I still can manage using a single VBR server or would need another server on the DR site?

if I need to minimize traffic do I need to manually copy the backup files to the DR site. or just use the default without seeding
do I need to configure one or two proxy servers?

[Andreas Neufert]

You likely would use On-Host Proxies to interact with the data.
So you need one Veeam Backup Server somewhere (preferred on the replication target side so that you can failover without issues when site 1 is down).
The OnHost Proxy read from Hyper-V side one and sends data to side 2 OnHost Proxy on their Hyper-V servers.
The documentation is really good on all details:
https://helpcenter.veeam.com/docs/backu ... ml?ver=120

You can optionally use our Software WAN accelerators (separate VMs/Servers) to reduce WAN usage further but it is a bit more complicated in the planning.

You can use seeding as well for the initial replication through external media shipping.
https://helpcenter.veeam.com/docs/backu ... ng&ver=120

I suggest that you create a small empty VM to test the seeding process (copy backups over WAN as they are very small) just so that you can test everything before you transport the big amount of data.