The target is the repository, whether local or in the cloud. The network bottleneck for a backup copy job to a cloud provider would be your internet connection and both speed and stability of the connection impact performance. If running these on the same server, you should not see a network bottleneck, but a NAS or other network storage device could become a choke point. The network component looks at the path from the proxy to the repository. The proxy is the data mover and where deduplication and compression occur, and these processes are CPU intensive. You may split, separate, and add to these as necessary for your environment. Proxyīy default, Veeam installs the Backup & Replication console, proxy, and repository on the same server. Slow or over-subscribed disks will hamper this process and cause issues with production virtual machines and backup jobs. Backups happen while production VMs are running by taking snapshots and reading data.
The source is the location of the production data, such as a VMware datastore or a Hyper-V Cluster Shared Volume. We’ll focus on four areas: source, proxy, network, and target. If you apply throttling to a job or network traffic that becomes the primary slow point, you will see ‘throttling’ as the bottleneck. It displays the component with the most work time during a job.Īn unmentioned performance bottleneck is throttling. Important note: VBR will always indicate one of these components as a bottleneck, even if no performance issues exist. Target - target disk writer – backup storage or replica datastore Target WAN Accelerator - WAN accelerator deployed on the target side Network - network queue writer, responsible for sending processed VM data from the backup proxy over the network to a backup repository or another backup proxy
Source WAN accelerator - WAN accelerator deployed on the source side
Proxy - backup proxy, responsible for processing VM data Source - source disk reader – indicates the source storage, such as a VMware datastore Veeam uses a built-in indicator that analyzes all components during the backup or replication process, which are: Whether backing up VMware vSphere, Microsoft Hyper-V, or physical servers, performance usually dictates how quickly backups run and determines recovery point objectives. Understanding these bottlenecks allows you to troubleshoot latency quickly. Veeam Backup & Replication (VBR) detects performance issues during job processing, which are not always evident. As a platinum Veeam® Cloud & Services Provider, we frequently receive questions about backup performance, especially backup copy jobs.
0 kommentar(er)
