You are here: Configuration Considerations > Protecting PostgreSQL Best Practices

Protecting PostgreSQL Best Practices

In an Active/Standby configuration, the backup server is not actively running the PostgreSQL, but stands by in case the primary server experiences a failure. In an Active/Active configuration, each server is actively running a PostgreSQL instance, while acting as a backup for the other server in case of failure. The following list provides requirements that should be adhered to when protecting a PostgreSQL resource instance in an active/standby or active/active configuration.

  1. The PostgreSQL DataDir and Write-Ahead-LogPath (PGDATA/pg_xlog) must be installed on one or more shared file systems. The paths DataDir and WAL-Path must be shared between all servers that will protect the resource instance.

  1. The StartupLogPath, SocketPath and the ExecutablePath can be installed to optional shared file systems on the primary server or each local node file system.

  1. It is recommended that each instance use a unique port and socket path when running multiple instances in either an Active/Standby or Active/Active scenario. 

© 2012 SIOS Technology Corp., the industry's leading provider of business continuity solutions, data replication for continuous data protection.