2.7

Table Of Contents
3 Expand the Organization panel and select the vPostgres database group to which you want to add
replication.
4 Right-click the vPostgres master database, and select Create Slave.
5 Complete the following information in the Create Slave wizard.
Wizard page Action
Creation Type
Click Create new database.
General
Specify the database name, type, base database template, and database group
from which to create the database.
Name
Type a name to identify the database within the Data
Director user interface.
Description
(Optional) Type a description of this database.
Database Type
Displays the type of database from which you are
creating a slave database.
Base DB
Template
Displays the name of the base database template
from which the master database was created, and
which will be used to replicate the slave database.
Database Group
The name of the database group that you want the
slave instance to belong to. By default, this is the
database group the master instance belongs to.
Storage
Specify the data, log, and backup disk storage allocation for this database.
Specify storage allocation for each disk type. If multiple datastores are
available, specify the datastore that the slave database uses for its virtual
disks. To ensure redundancy, replicas use different datastores than the
master database.
6 Click Finish.
The slave database is replicated from the master database, and appears in the Databases tab within the
Organization and Database Group to which you assigned it. You can monitor the replication status of slave
databases in the Dashboard tab, and the progress of the replication process in the Tasks panel.
You can verify that all of the data in the master instance has been replicated to the slave instance on the
Replication Status panel in the Dashboard tab. The Replay Delta column displays 0 when all the data has been
replicated.
What to do next
If a master database fails, manually promote one of the slave database instances to take the place of the master
database. See “Failover to a Standby vPostgres Database,” on page 165.
Failover to a Standby vPostgres Database
You can manually failover by promoting a slave (or standby) database to take over from its master (or primary)
database. When you promote a slave database to take over from its master database, all other slave instances
are redirected to use the newly created master instance.
NOTE During failover, all connections to the database are terminated.
Prerequisites
Verify that you have one or more slave instances of a vPostgres database that you can promote to a master
database if the original master database instance fails.
Chapter 13 High Availability and Replication
VMware, Inc. 165