One of the most critical components of any vSphere environment is the vCenter server. This server provides a single view of the entire virtual environment, and a central point of management. Veeam Backup & Replication communicates with vCenter for many operations, so fast, stable communications between Veeam Backup & Replication and the vCenter server are critical to achieving a stable backup environment.
Below are listed some of the important factors that should be considered.
•Problems with connectivity to vCenter are one of the top reasons for failed Veeam jobs, but having a well performing vCenter server with reliable connectivity will mitigate this issue and provide a strong backbone for a reliable backup infrastructure.
•The vCenter server must be reliable and always available when backup jobs are running. It must be able to answer queries and perform actions in a reasonable amount of time. If the vCenter server performs poorly during normal operations, this should be corrected prior to implementing Veeam Backup & Replication.
•For larger environments, with many concurrent jobs, especially jobs that run at short intervals, such as Near-CDP, the load on the vCenter server can be significant. The vCenter server must be able to handle this increased transactional workload to prevent random job failures due to command timeouts.
•The Veeam backup server must have reliable network connectivity to the vCenter server. It is generally suggested that the Veeam backup server be placed in close logical proximity to the vCenter server, but this is not always the best deployment option. In cases where the Veeam server and vCenter must be deployed across a distance, the only real requirement is that this connection be reliable.
•When maintenance is being performed on the vCenter server, best practice would dictate that all Veeam Backup and Replication jobs should be idle, and Veeam Backup Service should be stopped. This includes applying Windows updates, vCenter patches and upgrades, or any maintenance that would require the vCenter service to be restarted or the system rebooted.