Link Search Menu Expand Document

NAS Backup Proxy

NAS proxy deployment works similar like VMware proxy deployment. To estimate the resource requirements, the following calculation can be used: 100MByte per second or 5 million files per hour per proxy CPU core. Take the higher value.

Virtual Proxy

The recommendations for virtual proxies are:

  • Scale-out proxies in sets of 4-cores & 16GB RAM
  • A minimum of two proxies for redundancy
  • Break out to a physical proxy or proxies once the practical limits of virtual proxies are met.

Physical Proxy

With Physical proxies it allows for higher bandwidth than could be expected with virtual proxies.

For example a 20-core processor can process at approximately 2GBps or 16Gbps which is reasonable for a single server. However, as this increases the bandwidth may become an issue both for the ports on the server and the network at large.

This graph shows cores to bandwidth required between 1-48 cores with 50% reduction on the egress.

file_proxy_cores

At 48 cores the ingress bandwidth is ~40Gbps, Egress ~20Gbps for a total of ~60Gbps of packages the server has to process. Based on a 5% change rate over 8-hours that would equate the incremental for a 2.57PB backup.

The recommendations for physical proxies are:

  • A minimum of two proxies for redundancy
  • Be mindful of the amount of bandwidth going through each server both ingress and egress
  • Check the network between NAS, physical proxies and the repository to ensure bandwidth requirements can be met
  • Ensure that the Backup IO control is set appropriately for the quantity of Proxies

Backup I/O Control

Based on this setting the following maximum number of proxies are used for NAS backups:

IO control Max Proxies per share
Lower impact 1
Below normal 1
Normal 2
Above normal 4
Faster backup unlimited

Help center Backup IO Control


Back to top

Copyright © 2019-2021 Solutions Architects, Veeam Software.