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.
Note
The pg_dump parallel job option (pg_dump with -j) is supported for PostgreSQL 9.3 and more recent versions.
For PostgreSQL agents, the Indexing version 2 is enabled by default for newly installed clients in Feature Release 11.30 and more recent versions. For clients that are installed in older Feature Releases, the Indexing version will be 1. If you enable the Use parallel jobs to dump the database option for a client, the Indexing will be upgraded to version 2.
Before You Begin
Verify that no jobs are running for the instance.
Procedure
-
From the navigation pane, go to Protect > Databases.
The database overview page appears.
-
On the Instances tab, click the instance.
The instance properties page appears.
-
In the DumpBasedBackupSet details section, click Edit.
The Edit PostgreSQL Backup set dialog box appears.
-
Move the Use parallel jobs to dump the database toggle key to the right.
-
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. Since pg_dump opens n jobs+1 connections to the database, verify that the max_connections setting is set to a value that is sufficient to accommodate all connections.
-
To set the staging path for backups, in the Staging path box, enter the location on the client to use for staging backups.
-
Click SAVE.
What to Do Next
Whenever you enable or disable parallel jobs, run a full backup on all the database groups under the DumpBasedBackupsets.