Using Parallel Jobs to Dump the Azure Database for PostgreSQL

You can use parallel jobs to dump the databases for DumpBasedBackupset subclients. To back up the database, parallel jobs use the pg_dump -j option.

For PostgreSQL agents, indexing is enabled by default for newly installed clients in Feature Release 11.30 and more recent versions. For clients that are installed in older releases, Indexing Version 1 will be used. If you enable the Use parallel jobs to dump the database option for a client, the indexing will be upgraded to the latest version of indexing.

Before You Begin

• Verify that no jobs are running for the instance.

• During a pg_dump job, the backup dump size of a database can reach up to 120% of the original database size to accommodate data and metadata. Therefore, make sure that the access node staging path has enough free space to accommodate the subclient content as per the configured streams.

• If a subclient is configured with n streams, you should make sure that the free storage space in the staging area is least 120% of the combined size of the n largest databases in the subclient. For example, if a subclient is configured with 2 streams and contains five databases of sizes 40 GB, 30 GB, 15 GB, 5 GB, and 1 GB, the required free space would be 120% of the two largest databases (40 GB and 30 GB), which equals 84 GB.

• If the same access node is used for multiple cloud Postgres instance backups, the space requirements should be planned based on the subclient content and the number of streams.

Procedure

1. From the Command Center navigation pane, go to Protect > Databases.

   The database Overview page appears.

2. Go to the Instances tab.

3. Click the instance.

   The instance Overview page appears.

4. In the DumpBasedBackupSet details section, click Edit.

   The Edit PostgreSQL Backup set dialog box appears.

5. Move the Use parallel jobs to dump the database toggle key to the right.

6. In the Number of parallel jobs box, enter the number of jobs to dump the database.

   Note

   pg_dump -j uses multiple database connections to connect to the database, once using the leader process and one more time for each worker job. As pg_dump opens n jobs+1 connections to the database, verify that the max_connections setting is set to the sufficient value that can accommodate all connections.

7. To set the staging path for backups, in the Staging path box, enter the location on the client to use for staging backups.

8. Select the Back up global objects check box to back up information about global objects (such as roles).

9. Click SAVE.