Required file proxies resources are 24 cores and 48GB of RAM. Files to process per hour: 10M / 8 hours = 1.25M/h (processing 5 millions files per hour).Incremental throughput requirements: (3PB x 2%) / 8 hours = 7.68TB/h (at 100MB/s).When using virtual proxies, keep in mind that the number of cores per proxy should not exceed 8 to avoid co-stop.ģPB source data, 10M files, 40 shares, 2% change rate, eight hours backup window.If you have more shares than proxy cores, then consider adding cores to your existing proxies before adding more proxies. If you have less shares than number of proxy cores, then consider spreading these cores across multiple proxies.An exception might be the processing of a single, exceptionally large share. Generally speaking, the “normal” setting will be optimal.Note: these numbers are given assuming the infrastructure itself won’t present any limitation. Depending on the backup IO control seting, these numbers may slightly vary if the number of threads per core is modified. Expected performanceĮach proxy task (core) is expected to process 100MB/s or 5 million files per hour. The backup IO control is a static setting, it is not based on latency monitoring, because NAS filers don’t provide such values via SMB/NFS protocol. It controls the number of proxies allowed to back up a given share and the number of concurrent threads per task following rules below : When configuring the file share in the Veeam Backup & Replication inventory, the backup IO control parameter will affect the way proxy resources will be used. Backup IO control and proxy resource usage One CPU-core per proxy task is recommended. When sizing a proxy, do not forget to dedicate necessary resource to the operating system (usually two core and 4GB RAM).Ī proxy task (core) processes one file share at a time and CPU/RAM resources are used for inline compression and/or encryption. It is best practice to plan for one physical core or one vCPU and 2 GBof RAM for each of these tasks. Proxies do have multiple task slots to process source data. In this section, we will outline the recommendations to follow for appropriate sizing. Getting the right amount of processing power is essential to achieving the RTO/RPO defined by the business.

We recommend the latest supported version of Windows Server OS for all proxies. Optimized data (normally ~50% of the source data size) will be transferred here. The traffic from the source to the proxy is not yet optimized, meaning that 100% of the backup data will be transferred over this link.Īlso, consider a good connection between proxy and repository.

This site uses Just the Docs, a documentation theme for Jekyll.Īs a general rule, the proxy should be as close to the source data as possible with a high bandwidth connection.

Restoring VMs to an HPE 3PAR with thin disks.

Backup Repository HA using Windows Storage Replica.

Veeam file server backup best practices