

In this scenario, a failover can be performed from the Veeam console without a working vCenter Server itself (for example to failover the vCenter Server virtual machine). It can be best practice to add the ESXi hosts from the replica target side (only) directly to Veeam Backup & Replication as managed servers and to perform replication without vCenter Server on the target side. In most cases, Veeam does not need a vCenter Server for replica target processing.
#Veeam backup vcenter password
If you use a password manager such as KeePass, it’s also a good idea to include it in the scenario. vCenter Server (and vCD) infrastructure should as well be considered for the failover scenario. DNS and possibly authentication services (Active Directory, for example, or DHCP server if some replicated VMs do not use static addresses) should be implemented across both sides. These mechanisms reduce the amount of replication traffic while network mapping and re-IP streamline replica configuration. When planning off-site replication, consider advanced possibilities: It is recommended to place a Veeam backup server on the replica target side so that it can perform a failover when the source side is down.
#Veeam backup vcenter windows

Built-in WAN Acceleration (for replicas).Built-in WAN Acceleration (for backups).Built-in WAN Acceleration (for Veeam Cloud Connect).Scale-out Backup Repository™ (limited to three extents).Replication (1-Click Failover Orchestration).Enhanced encryption (lost password protection).Advanced recovery for Microsoft Active Directory, Exchange, SharePoint and SQL Server.On-Demand Sandbox (for low-risk application deployment from backups and replicas).SureBackup and SureReplica (recovery verification).Centralized deployment and management of Veeam Agent for Linux and Veeam Agent for Microsoft Windows.

