The cache repository is always a standard repository. If you have multiple proxy or repository servers, you can distribute the load over all machines. This also makes fast disks not necessary. No disk sizing is required unless using backup to Object Storage: usually the size of the cache files does not exceed 4GB and due to the optimized size of the cache, data will be loaded into memory when needed. At the best, they should be one hop away from each other. The bigger the share, the more the traffic between file proxies and cache repository.

Ideally, the cache repository should sit as close as possible to the File Proxy and source data. Note that there can be only one cache repository per source file share. If there is a match to the cache value, no file has to be processed and the file proxy will be instructed to iterate and repeat this process on deeper levels of the share to find folders with a mismatch. The file proxy sends back the top level structures hashes, the cache repository loads them into memory and initiates a CRC check on the data stored in the cache (generated with the previous job run). Whenever a NAS backup job runs, it is the cache repository that requests the File Proxy to retrieve data from the source share. It is also the controlling unit of a NAS backup job. It is used for NAS backup only and it is crucial to accelerate the incremental backup process, allowing to identify any object that has changed since the last backup. The cache repository was introduced in Veeam Backup & Replication v10 and holds a cache of folders information in the structure of the protected NAS share. This site uses Just the Docs, a documentation theme for Jekyll.

Veeam backup calculator