> Commvault SaaS > Databases > PostgreSQL

Backing Up a PostgreSQL Database

You can perform a full backup operation or an incremental backup operation of a PostgreSQL database.

Before You Begin

  • For FSBasedBackupSet, verify that the archive directory is properly configured, and that archiving is working. For more information, see Configuring the PostgreSQL Archive Log Directory.

  • If serverless log backups are enabled in the plan, the archive_command parameter is automatically configured by the Commvault Cloud software to write logs directly to the Backup Gateway.

Procedure

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

    The database overview page appears.

  2. Go to the Instances page.

  3. Click an instance.

    The instance Overview page appears.

  4. On the Backup sets section, click a backup set.

    The backup set Overview page appears.

  5. On the Database groups tab, if you click the Action button action_button in the row for the database instance to restore, and then click Backup.

    Alternatively, you can click a database group and select the Backup option from the database group overview page.

    The Backup options dialog box opens.

  6. Under Backup level, select the type of backup that you want to perform, either Full or Incremental.

  7. Click Submit.

Note

  • If a database that belongs to a database group (other than the default group) is renamed or removed, you must manually update the backup content for that database group. The old database entry is not removed automatically.

  • By default, backup operations using the DumpBased backup set do not include location information for roles and tablespaces. This is because the pg_dump utility, which performs DumpBased backups, does not back up roles or tablespaces.

To capture this information using the pg_dumpall utility, see
Enable backups for global objects in PostgreSQL databases.

  • By default, pg_dump is performed on Windows clients using the tar format (-Ft). This process does not require staging on the Commvault side. However, PostgreSQL uses the system’s temporary directory (typically C:\temp) as a staging location for temporary files while generating the tar-based dump.

Ensure that the Windows temporary directory has sufficient free space to accommodate the dump files.

  • The available free space must be sufficient to generate dump files based on the subclient content and the number of configured streams.

If a subclient is configured with n streams, ensure that the free space in the staging area is at least 120% of the combined size of the n largest databases in the subclient.

Example:
If a subclient is configured with two streams and includes five databases sized 40 GB, 30 GB, 15 GB, 5 GB, and 1 GB, the required free space is 84 GB (120% of 40 GB + 30 GB).

In most cases, dump files are smaller than the actual database size. However, in rare situations, dump files may exceed the database size depending on the data characteristics.

Page contents

×

Loading...