Configuring Cohesity DataProtect for PostgreSQLSuggest edits
Implementing Cohesity DataProtect for PostgreSQL with EDB Postgres Advanced Server requires the following components:
- EDB Postgres Advanced Server
- Cohesity Backup Appliance
- Cohesity Linux Agent
- Cohesity PostgreSQL Agent
- A running EDB Postgres Advanced Server instance
- Cohesity Backup Appliance installed and running on VMware
- Cohesity Linux and PostgreSQL agents installed on the same machine as your EDB Postgres Advanced Server database
- The user account of the PostgreSQL instance must have database admin privileges
- Login information for the Cohesity Web interface
- Credentials that are used to access the EDB Postgres Advanced Server database
- Java 1.8 or higher version is installed on the PostgreSQL nodes
- Cohesity PostgreSQL Agent scripts path,
/opt/cohesity/postgres/scripts, obtained during Cohesity PostgreSQL Agent installation
Configure Cohesity DataProtect for PostgreSQL for EDB Postgres Advanced Server
Register and Manage the EDB Postgres Advanced Server Source:
Log on to the Cohesity console at the IP address that was used to create your VMware Cohesity Backup Appliance with the format:
https://ipaddress/login, and when the Cohesity Dashboard appears login with your Cohesity credentials.
You will then be presented with the Cohesity Dashboard.
From the main Dashboard screen select
Data Protectionand then select
Sourceson the left-hand side.
On the Sources page, click on the
Registerbutton on the top right side and click on the
Universal Data Adapteroption.
- Step through the Universal Data Adapter screens by clicking
Nextuntil you get to the Register Universal Data Adapter screen.
- Once on the Register Universal Data Adapter screen, input the specific source information in order for the source to be protected.
- Source Type: For EDB Postgres Advanced Server, Source Type will be PostgreSQL.
- Hostnames/IP Addresses: Hostname or IP Address of the specific database to register.
- Script Directory Path: This path is defined during the installation of the Cohesity Postgres Agent. It will be displayed at the bottom of the installation scripts when the download is complete, and it is the location of where the scripts are located:
- In the App Authentication section, enter the admin username and password for the user who has admin privileges on your database to perform a backup.
Instead of password-based authentication, if you want to use kerberos authentication, then leave the username and password fields blank.
Custom Options, a new form will appear called
Global Source Registration Argumentswhere some more information will be needed to properly register an EDB Postgres Advanced Server database.
In the Global Source Registration Arguments field enter the following information with the same syntax:
--source-name=cohesitypostgres --postgres-user=enterprisedb --host=172.24.113.13 --port=5444 --pg-bin=/usr/edb/as14/bin
- -- source-name: A unique name to identify the EDB Postgres Advanced Server cluster.
- -- postgres-user: Specifies the user account to start the database.
- -- host: The IP address of the EDB Postgres Advanced Server instance.
- -- port: The port the EDB Postgres Advanced Server is listening on. If it is not specified the default port 5432 is used.
- -- pg-bin: The directory path to the EDB Postgres Advanced Server binaries, for example
Registerand your source will be created and ready to backup.
Configuring EDB Postgres Advanced Server
Set up WAL archiving on the EDB Postgres Advanced Server server by using the steps below. WAL archiving prepares Postgresql/EDB Postgres Advanced Server database servers for backup/recovery operations and is a precondition for any backup/recovery tool to work with the database server.
Create a writeable
<archivedir>directory at your desired location.
Set the required parameters in the
postgresql.conffile to turn on WAL archiving:
<archivedir> in the
archive_command parameter with the location of the directory created in Step 1.
- Restart the PostgreSQL server.
When you run your first backup on the database, Cohesity will set archive_mode=on in postgresql.conf and restart the database if you have not already set archive_mode=on.
Could this page be better? Report a problem or suggest an addition!