The vCloud Director appliance includes an embedded PostgreSQL database. The embedded PostgreSQL database includes the Replication Manager (repmgr) tool suite, which provides a high availability (HA) function to a cluster of PostgreSQL servers. You can create an appliance deployment with a database HA cluster that provides failover capabilities to your vCloud Director database.

You can deploy the vCloud Director appliance as a primary cell, standby cell, or vCD application cell. See Deploy the vCloud Director Appliance By Using the vSphere Web Client or the vSphere Client, Deploying the vCloud Director Appliance by Using VMware OVF Tool, or Deploy the vCloud Director Appliance with Signed Wildcard Certificates for HTTPS and Console Proxy Communication.

To configure HA for your vCloud Director database, when you create your server group, you can configure a database HA cluster by deploying one primary and two standby instances of the vCloud Director appliance.

Figure 1. A vCloud Director Appliance Database HA Cluster
One primary and two standby cells

Creating a vCloud Director Appliance Deployment with Database HA

To create a vCloud Director server group with a database HA configuration, follow this workflow:
  1. Deploy the vCloud Director appliance as a primary cell.

    The primary cell is the first member in the vCloud Director server group. The embedded database is configured as the vCloud Director database. The database name is vcloud, and the database user is vcloud.

  2. Verify that the primary cell is up and running.
    1. To verify the vCloud Director service health, log in with the system administrator credentials to the vCloud Director Web Console at https://primary_eth0_ip_address/cloud.
    2. To verify the PostgreSQL database health, log in as root to the appliance management user interface at https://primary_eth1_ip_address:5480.

      The primary node must be in a running status.

  3. Deploy two instances of the vCloud Director appliance as standby cells.

    The embedded databases are configured in a replication mode with the primary database.

    Note: After the initial standby appliance deployment, the replication manager begins synchronizing its database with the primary appliance database. During this time, the vCloud Director database and therefore the vCloud Director UI are unavailable.
  4. Verify that all cells in the HA cluster are running.

    See View the Status of the Cells in a Database High Availability Cluster.

  5. (Optional) Deploy one or more instances of the vCloud Director appliance as vCD Application cells.

    The embedded databases are not used. The vCD Application cell connects to the primary database.

One primary cell, two standby cells, and N vCD Application cells

Creating a vCloud Director Appliance Deployment Without Database HA

To create a vCloud Director server without a database HA configuration, follow this workflow:
  1. Deploy the vCloud Director appliance as a primary cell.

    The primary cell is the first member in the vCloud Director server group. The embedded database is configured as the vCloud Director database. The database name is vcloud, and the database user is vcloud.

  2. Verify that the primary cell is up and running.
    1. To verify the vCloud Director service health, log in with the system administrator credentials to the vCloud Director Web Console at https://primary_eth0_ip_address/cloud.
    2. To verify the PostgreSQL database health, log in as root to the appliance management user interface at https://primary_eth1_ip_address:5480.

      The primary node must be in a running status.

  3. (Optional) Deploy one or more instances of the vCloud Director appliance as vCD Application cells.

    The embedded database is not used. The vCD Application cell connects to the primary database.

One primary cell and N vCD application cells