![]() However, Veeam recommends physical hardware whenever possible. Veeam backup repositories can reside on physical or virtual hardware. These limitations are not necessary if the repository is running on appropriately sized hardware, but users may need to throttle undersized repositories to prevent overruns and timeouts from occurring. ![]() The backup repository setup process enables users to limit the maximum concurrent tasks and data transfer rates. According to Veeam, no repository should have less than 2 cores and 8 GB of RAM. ![]() The 11 cores from the previous example, multiplied by 4 GB, would be 44 GB. Veeam recommends that users multiply the number of repository cores by 4 GB to reach the required amount of RAM. For example, an organization with 32 proxy cores would result in 11 cores, rounded up. ![]() Veeam recommends dividing the number of proxy cores by three and then rounding up. Repositories need to be sized to match the proxies that are in use. A backup proxy reads the source data that an organization backs up and transfers that data to the backup repository. Several best practices for Veeam backup repositories are tied directly to the use of Veeam backup proxies.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |