The vSphere Replication appliance contains an embedded vPostgreSQL database that you can use immediately after you deploy the appliance, without any additional database configuration. If necessary, you can reconfigure vSphere Replication to use an external database.
About this task
Each vSphere Replication appliance requires its own database. If the database at either site is corrupted, vSphere Replication does not function. vSphere Replication cannot use the vCenter Server database because it has different database schema requirements. However, if you do not use the embedded vSphere Replication database you can use the vCenter database server to create and support an external vSphere Replication database.
You might need to use an external database to improve performance or load balancing, for easier backup, or to meet your company's database standards.
vSphere Replication server inside the vSphere Replication appliance uses its own embedded database and config files. Configuring VRMS to use external database does not provide protection of losing the vSphere Replication appliance or any Additional vSphere Replication Server appliance.
If you reinitialize the database after you deploy vSphere Replication, you must go to the vSphere Replication virtual appliance management interface (VAMI) to reconfigure vSphere Replication to use the new database connection.
Prerequisites
Verify that the vSphere Replication appliance is powered on.
You must have administrator privileges to configure the vSphere Replication appliance.
You must create and configure the external database before you connect it to vSphere Replication. See Databases that vSphere Replication Supports for the configuration requirements for each supported type of database.
Procedure
Results
You configured vSphere Replication to use an external database instead of the database that is embedded in the vSphere Replication appliance.