You can use replication to designate a secondary appliance that contains a copy of the database that is on your primary appliance. After everything is set up, and the initial copy of the database is created on the secondary system, updates made to the database on the primary system ripple through to the replica database on the secondary system.
Note: Even though "database" is referred to in the singular, all databases contained in the Postgres instance on the primary system would be replicated. You can view the list of these databases on the Database Management window.
One of the principal reasons for setting up replication is so that the secondary database can be used as a failover system if the primary database becomes unusable. For this reason, the secondary database is frequently referred to as a standby database, because it is ready and waiting, standing by in case it is needed. It is also possible to set up multiple standby databases for the same primary database.
For more information on setting up failover, see the Set Up Automatic Failover section.
When the replication setup process is complete, the
Postgres Replication Status window on the primary appliance and on the standby appliance display their respective statuses.
Select
Set up Auto Failover on either the primary system or the standby system to go to the window where you can set up automatic changeover to the standby database if the primary database has a failure for any reason. For more information, see
Set Up Automatic Failover.
