> [!CAUTION]
> **Caution:** Support for backing up and restoring workloads managed using the legacy appliance management console is deprecated. For more information, see [Feature deprecations](https://docs.cloud.google.com/backup-disaster-recovery/docs/deprecations.md.txt) in the Backup and DR documentation.

Backup and DR uses [VMware vSphere storage APIs](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.storage.doc/GUID-3FD5AB1E-47B3-49B5-845E-5224BE062A59.html) data protection to
create backups of VMware VMs, placing backups either in the snapshot pool
of the backup/recovery appliance or in OnVault pools.

To make API calls, the backup/recovery appliance needs to connect to the
vCenter or ESX server host with a username and password that has authority to
perform the required actions. This page explains how to add a vCenter or ESX
server host in the appliance management console.

## Before you begin

- Be sure to review [Configure Google Cloud VMware Engine for Backup and DR protection](https://docs.cloud.google.com/backup-disaster-recovery/management-console/configuration/prepare-vmware.md.txt).

- Make sure that the vCenter server is accessible from the appliance
  as described in [Third-party service certificate](https://docs.cloud.google.com/backup-disaster-recovery/management-console/configuration/certificate.md.txt).

- Backup and DR establishes a secure connection with the vCenter. If a
  secure connection is not established, backup and restore jobs fail.
  The connection to vCenter fails in either of the following scenarios:

  - If there is a mismatch between the name of the vCenter and the name in the vCenter certificate.
  - If the vCenter certificate is not trusted by OS trust anchors or if vCenter has self-signed certificates.

## Add a new vCenter or ESX Server host

Use these instructions to add a new vCenter or ESX server host to the
appliance management console:

1. Click **Manage** \> **Hosts**.

2. Select **+ Add Host**.

3. In the **Name** field, enter the *fully qualified domain name* of the vCenter host.
   Ensure that the name in the host's **Name** field is the same as in the vCenter certificate.
   The connection fails if there is a mismatch.

4. Optional: In the **Friendly Name** field, enter a user-friendly name for the host.
   The name of a host must start with a letter, and can contain letters
   and digits (0-9). Don't use underscore (*_* ) characters in hostnames.
   You can also add a friendly name for the vCenter host in the **Friendly Name**
   field.

   > [!NOTE]
   > **Note:** For existing vCenter hosts, if the hostname does not match the fully qualified domain name (FQDN) of the server, then the backup/recovery appliance automatically updates the hostname during the appliance upgrade. The existing hostname is moved to the **Name** column if the **Friendly Path** column is empty.

5. Enter the IP address of the host in **IP Address** . Click **+** to add
   multiple IP addresses.

6. In the **Appliances** section, select one or more appliances that serve this host.
   If the list is long, you can use the search field to find a specific appliance
   or group of appliances.

7. In **Host Type** , select either **vCenter** or **ESX Server**.

   > [!NOTE]
   > **Note:** You normally don't need to add ESX servers as they are auto-discovered when you add the vCenter host that manages them.

8. Select the data transport mode, either **NFS** or **SAN** . NFS is the
   recommended and default setting. Enter the username and password to
   connect to the host and then use the **Test** button to validate them.
   You only need to enter a port if a non-standard port is being used.

   | To protect | Select host type | Connection type |
   |---|---|---|
   | vCenter with ESXi VMs | vCenter | The default vCenter management port is 443. If you use a different port, then enter it here. Enter the **vCenter User Name** and **vCenter Password** and then select **Test**. |
   | ESXi standalone | ESX Server | The default ESX Server management port is 902. If you use a different port, then enter it here. Enter the **ESX User Name** and **ESX Password** and then select **Test**. |
   [Host settings]

   <br />

9. Click **Add**.

## Edit or rotate vCenter credentials

To edit or update credentials for an existing host, see
[Edit host properties](https://docs.cloud.google.com/backup-disaster-recovery/docs/configuration/manage-hosts-and-their-applications#edit-host).

When you update credentials for an existing vCenter host in the
appliance management console, the management server broadcasts the updated
credentials to all registered backup/recovery appliances that serve the host.

### Rotate credentials in multi-appliance fleets

To minimize database lock contention and avoid update errors in multi-appliance
fleets, rotate credentials during periods of low activity.

During a credential update, the management server acquires per-appliance
database advisory locks to synchronize changes across appliances. If active
backup jobs, restore jobs, or background replication and synchronization tasks
hold database locks simultaneously, lock contention can cause error code
`10053` (`Appliance is busy`).

Don't pause all fleet backups. Pausing backups disrupts scheduled jobs and
doesn't prevent lock contention from background system tasks.

If error code `10053` occurs during a credential update, do the following:

1. Wait a few minutes for background tasks to release locks, and then retry the update.
2. If the error persists, see [Event IDs and resolutions](https://docs.cloud.google.com/backup-disaster-recovery/management-console/monitor-reports/event-codes.md.txt) or [contact Cloud Customer Care](https://docs.cloud.google.com/backup-disaster-recovery/docs/support.md.txt) for assistance with specific appliances.

## What's next

- To discover and protect VM, see [Discover and protect VMware VMs](https://docs.cloud.google.com/backup-disaster-recovery/docs/configuration/discover-and-protect-vms)

## The VMware administrator's guide

- [Backup and DR for VMware VMs](https://docs.cloud.google.com/backup-disaster-recovery/docs/concepts/vmware-intro)
- [Configure Google Cloud VMware Engine for Backup and DR protection](https://docs.cloud.google.com/backup-disaster-recovery/management-console/configuration/prepare-vmware.md.txt)

- [Add vCenter and ESX server hosts to the appliance management console](https://docs.cloud.google.com/backup-disaster-recovery/management-console/configuration/add-vcenter-host.md.txt)

- [Discover and protect VMware VMs](https://docs.cloud.google.com/backup-disaster-recovery/docs/configuration/discover-and-protect-vms)

- [Apply a backup template to protect a VM](https://docs.cloud.google.com/backup-disaster-recovery/docs/create-plan/apply-backup-template-to-manage-a-VM)

- [Configure application settings for VMware VMs](https://docs.cloud.google.com/backup-disaster-recovery/docs/backup/configure-application-settings-for-vmware-vm)

- [Restore a VMware VM](https://docs.cloud.google.com/backup-disaster-recovery/management-console/restore-data/restore-vm.md.txt)

- [Mount a VMware image](https://docs.cloud.google.com/backup-disaster-recovery/management-console/access-data/mount-vmware-image.md.txt)

- [Clone an image of a VMware VM](https://docs.cloud.google.com/backup-disaster-recovery/docs/access-data/clone-image-of-a-vm)

- [Create LiveClone workflows](https://docs.cloud.google.com/backup-disaster-recovery/docs/access-data/create-liveclone-workflows)

- [Move VM management between two backup/recovery appliances](https://docs.cloud.google.com/backup-disaster-recovery/docs/configuration/supported-vmware)