The VMware Cloud 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 VMware Cloud Director database.

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

To configure HA for your VMware Cloud 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 VMware Cloud Director appliance. You can horizontally scale your server group by additionally deploying application cells. See the VMware Cloud Director Appliance Database HA Cluster figure.

Figure 1. VMware Cloud Director Appliance Database HA Cluster
One primary and two standby cells

Creating a VMware Cloud Director Appliance Deployment with Database HA

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

    The primary cell is the first member in the VMware Cloud Director server group. The embedded database is configured as the VMware Cloud 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 VMware Cloud Director service health, log in with the system administrator credentials to the VMware Cloud Director Service Provider Admin Portal at https://primary_eth0_ip_address/provider.
    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 VMware Cloud 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 VMware Cloud Director database and therefore the VMware Cloud Director UI are unavailable.
  4. Verify that all cells in the HA cluster are running.

    See View the VMware Cloud Director Appliance Cluster Health and Failover Mode.

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

    The embedded databases are not used. The VMware Cloud Director Application cell connects to the primary database.

One primary cell, two standby cells, and N VMware Cloud Director Application cells
Note: If your cluster is configured for automatic failover, after you deploy one or more additional cells, you must use the Appliance API to reset the cluster failover mode to Automatic. See the VMware Cloud Director Appliance API. The default failover mode for new cells is Manual. If the failover mode is inconsistent across the nodes of the cluster, the cluster failover mode is Indeterminate. The Indeterminate mode can lead to inconsistent cluster states between the nodes and nodes following an old primary cell. To view the cluster failover mode, see View the VMware Cloud Director Appliance Cluster Health and Failover Mode.

Creating a VMware Cloud Director Appliance Deployment Without Database HA

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

    The primary cell is the first member in the VMware Cloud Director server group. The embedded database is configured as the VMware Cloud 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 VMware Cloud Director service health, log in with the system administrator credentials to the VMware Cloud Director Service Provider Admin Portal at https://primary_eth0_ip_address/provider.
    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 VMware Cloud Director appliance as VMware Cloud Director Application cells.

    The embedded database is not used. The VMware Cloud Director Application cell connects to the primary database.

One primary cell and N VMware Cloud Director application cells