> Software > Databases > PostgreSQL > Configuration

Using Parallel Jobs to Dump the PostgreSQL Database

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.

  • If you schedule a backup on a standby node and the PostgreSQL version is older than 10, do not use parallel jobs.

Before You Begin

  • Verify that no jobs are running for the instance.

  • If you have enabled IntelliSnap or block-level backups for an instance, verify that the backup copy jobs are completed.

  • During pg_dump job, the maximum backup dump size of a database may be up to 120% of the size of the database. Ensure that the staging path has sufficient free space to accommodate subclient content and the number of streams.

Procedure

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

    The database Overview page appears.

  2. Go to Instances tab.

  3. Click an instance.

    The instance page appears.

  4. On the Backup sets tab, click DumpBasedBackupSet.

    The DumpBasedBackupSet overview page appears.

  5. In the General tile, click Edit.

    The Edit PostgreSQL Backup set dialog box appears.

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

  7. 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.

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

  9. Click Save.

Page contents

×

Loading...