In any case the bandwith is always shared across the number of threads.Ĭopyright © 2019-2023 Solutions Architects, Veeam Software. It is interesting to note the VB365 Proxy might not necessarily use the maximum bandwidth configured as this also depends on the Microsoft 365 throttling limiting the connection speed. The best practice is to limit the maximum amount of bandwidth the VB365 Proxy can use. In this case all the available bandwidth to the server running as VB365 Proxy will be used. Represents the network throughput shared across the number of configured threads. Very high CPU and memory load is a indicator for a misconfigured (too high) thread number. The advice is to monitor same sample “test jobs” to verify and adjust the number of threads. Although it is possible to change this number, using a thread number too high might incur in the Throttling Policy that Microsoft 365 activates to control the resources external clients/connection require. Default number of VB365 Proxy connections is 64. The higher the number the faster potentially the backup job will complete. It is the number of active connections started by the VB365 Proxy responsible for backing up data. When sizing the VB365 Proxies there are two important VB365 parameters to know about: Objects can be any combination of Mail, Archive, Site, OneDrive and Teams. Check out the Configuration Maximums to see how many proxies can be used and how many objects each of them can handle. Restoring to another tenant is a default feature of Veeam Backup for Microsoft 365 now. VB365 Proxy sizing depends on the total number of objects to protect. Best practice from the field for Veeam Backup for Microsoft 365.
0 kommentar(er)
