Add a PostgreSQL instance when you need to manage a database.
Tip
If you have access to more than 10 server groups, use the arrow buttons at the lower-left bottom of the page to page through the server groups.
When you add an instance, the following backup sets are automatically created, each with a default database group:
-
DumpBasedBackupSet
-
FSBasedBackupSet
Before You Begin
-
Obtain the PostgreSQL application path and library directory path.
-
Obtain the credentials that you use to access the PostgreSQL application.
-
Make sure that you have a storage policy to use for log backups.
-
Configure the PostgreSQL archive log directory.
For more information, see Configuring the PostgreSQL Archive Log Directory.
-
Optional: If you want to use a specific account when you perform backup and restore operations, have the user name and the password.
Procedure
-
From the Command Center navigation pane, go to Protect > Databases.
The database Overview opens.
-
From the Add instances list, select Database server.
The Configure Database Instance dialog box appears.
-
Select PostgreSQL.
The Add PostgreSQL instance dialog box appears.
-
From the Server name list, select a server where you want to create the new instance.
-
In the Instance Name box, type the PostgreSQL instance name.
-
From the Plan list, select a backup plan.
-
Under Connection details section, enter the following information:
-
From Credential list, select an existing credential or add a new credential. To add a new credential, do the following:
Steps to add a credential
-
Click +.
The Add Credential dialog box appears.
-
From the Account type list, select a database account type.
-
From the Database credential type, select a database agent.
-
From the Credential Vault list, select a credential vault to store, share, and update account credentials with shared resources in your environment.
-
In the Credential name box, enter a unique name to access the credential.
-
Under the Azure AD/AWS IAM Authentication section, enter the following details:
-
In the Username box, enter the user name to access the Azure Database for PostgreSQL application.
-
In the Password box, enter the password to access the Azure Database for PostgreSQL application.
Note
If you move the Azure AD/AWS IAM Authentication toggle to right, you only need to enter the user name detail.
-
-
Move SSL certificate toggle key to right, and enter the following details:
-
In the SSL CA file field, provide the SSL CA file path on the proxy computer.
-
In the SSL Cert file field, provide the SSL certificate file path on the proxy computer.
-
In the SSL Key file field, provide the SSL key file path on the proxy computer.
-
-
In the Description box, enter a brief description for the credential.
-
Click Save.
-
-
In the Maintenance DB box, type the name of a system database which is used as a maintenance database.
-
In the Port box, type the port to open the communication between PostgreSQL Server and the clients.
-
If you are using the same port number for two or more instances, you can type the port number in the IP:PORT format.
For example: You can type the port number as 10.57.198.4:5432, if the IP for your Network Interface Card (NIC) is 10.57.198.4 and you are using port 5432. To use the same port number on a different NIC, you can type 10.57.198.5:5432.
-
If you are using the custom socket directory, enter the port in the SOCKET_DIR_PATH:PORT format.
For example: If socket directory used is /var/run/postgresql and you are using port 5432, enter the port as /var/run/postgresql:5432.
-
If you are configuring a containerized PostgreSQL instance, enter the port in HOSTNAME:PORT format or IP:PORT format.
-
-
-
Under PostgreSQL paths section, enter the following information:
-
In the Binary directory box, type or browse the path to the PostgreSQL application.
-
In the Lib directory box, type or browse the path to the library directory for the instance.
For example, /opt/PostgreSQL/9.4/lib.
-
In the Archive log directory box, complete one of the following steps:
-
On a UNIX client, type the path to the directory where you want to store the archive log files. For example, /opt/wal. Make sure that this path does not point to pg_log and pg_xlog directories.
-
On a Windows client, type the path to the directory where you want to store the archive log files.
Note
The Archive log directory is required only for running fs-based backups for the instance. It is not required if you plan to run only dump-based backups.
-
-
-
Click Add.
The software creates the instance and a default database group for DumpBasedBackupSet and FSBasedBackupSet.
Note
For Dumpbased backupset, associating a database group to a backup plan will only associate a storage policy, and not a schedule policy. To associate a schedule policy, edit the instance and move the Run dump backups with plan-based schedules toggle key to the right. This will disable schedule policy for FSBased backupset.
What to Do Next
Create database groups for the data that you want to protect.