Configuring the CTERA Portal Database for Backup

CTERA Portal uses PostgreSQL to store metadata. This database must be backed up to ensure continued use of CTERA Portal in order to ensure data and metadata persistence and consistency on the CTERA platform, and to keep Recovery Time Objective (RTO) and Recovery Point Objective (RPO) values to a minimum.

Calculating the Minimum Space Required for the Database Backup

The archive pool must be at least double the data pool.

For example, if the primary database uses 1TB storage and a secondary, replication, database uses another 1TB, then each of these databases require 2TB for backup. The total storage must be at least 6TB: 1TB for the primary database, 1TB for the secondary database and 4TB for the primary and secondary backups (2TB for each backup).

See the following procedures:
Using PostgreSQL Continuous Archiving – CTERA Portal uses PostgreSQL's built-in continuous archiving mechanism to enable you to roll back to an older version of the portal database.
Using PostgreSQL Streaming Replication – Streaming replication enables the continuous streaming and replication from a primary database server to a secondary database server.