NetBackup™ for PostgreSQL Administrator's Guide

Last Published:
Product(s): NetBackup (11.0)
  1. Overview
    1.  
      Overview of configuring and protecting PostgreSQL assets in the NetBackup web UI
  2. Managing PostgreSQL instances and databases
    1.  
      Quick configuration checklist to protect PostgreSQL instances and databases
    2.  
      Configure PostgreSQL instance
    3.  
      Add a PostgreSQL instance
    4.  
      Manage credentials for an instance
    5.  
      Discover PostgreSQL databases
    6.  
      Remove PostgreSQL instances
    7.  
      Change the autodiscovery frequency of PostgreSQL assets
  3. Managing PostgreSQL environment credentials
    1.  
      Add new PostgreSQL credentials
    2.  
      Default PostgreSQL Administrator
    3.  
      Validate credentials of PostgreSQL instance
    4.  
      View the credential name that is applied to an asset
    5.  
      Edit or delete a named credential
  4. Protecting PostgreSQL instances and databases
    1.  
      Things to know before you protect PostgreSQL instances and databases
    2.  
      Protect PostgreSQL instances and databases
    3.  
      Customize protection settings for the PostgreSQL assets
    4.  
      Remove protection from PostgreSQL instances
    5.  
      View the protection status of PostgreSQL instance
  5. Restoring PostgreSQL Instances and Databases
    1.  
      Things to know before you restore the PostgreSQL instances and databases
    2.  
      About the pre-restore check
    3.  
      Restore PostgreSQL instance and database
    4.  
      Restore target options
    5.  
      Pre-restore checks for PostgreSQL
    6.  
      Steps to perform recovery after restore operation
    7.  
      Steps to perform after Restore and Recovery for PostgreSQL cluster deployment
    8.  
      Limitations
  6. Troubleshooting PostgreSQL operations
    1.  
      Troubleshooting tips for NetBackup for PostgreSQL
    2.  
      Error during PostgreSQL credential addition
    3.  
      Error during the PostgreSQL instances and databases discovery phase
    4.  
      Error during the PostgreSQL Protection Plan Creation
    5.  
      Error while subscribing protection plan to PostgreSQL asset
    6.  
      Error while removing PostgreSQL asset
    7.  
      Error while backup of PostgreSQL asset
    8.  
      Error while restoring PostgreSQL asset image
  7. API for PostgreSQL instances and databases
    1.  
      Using APIs to manage, protect or restore PostgreSQL
  8.  
    Index

Protect PostgreSQL instances and databases

Use the following procedure for subscribing a protection plan to PostgreSQL instance and database. When you subscribe an asset to a protection plan, you assign predefined backup settings to the asset.

Note:

The RBAC role assigned to a user must have access to the assets that you want to manage and also to the protection plans you want to use.

To protect a PostgreSQL instance or database:

  1. On the left pane, click PostgreSQL.
  2. On the Instances tab or Databases tab, click the box for the instance or the database and click Add protection.
  3. Select a protection plan and click Next.
  4. You can edit one or more of the following settings:

    • Schedules and retention

      Change when backups occur and the backup start window.

      Schedules:

      • Full: Complete instance backup using snapshot/pg_basebackup/pg_dumpall and completes database-backup using pg_dump utility.

      • Differential Incremental: Based on the previous backup timestamp, NetBackup identify the changed set of transaction logs (WAL files) and perform its backup.

    • Backup options

      Adjust the Database options like Job limit and Backup method.

      • Snapshot: This option is used to take the snapshot of an instance. For Windows - VSS snapshot method is used. For Linux - LVM snapshot method is used.

      • pg_basebackup: This utility of PostgreSQL performs the backup of an instance. It is recommended in the case of non-LVM deployment.

      • pg_dumpall: This utility of PostgreSQL performs logical backup of instance. It is recommended in the case of non-LVM deployment.

      • pg_dump: This utility of PostgreSQL performs logical backup of an individual database.

      Note:

      In the case of snapshot-based backups, it is recommended to keep the archive directory and the data directory in separate locations.

      Note:

      If a PostgreSQL instance has tablespaces configured, then use pg_dumpall backup method. In the case of pg_dumpall and pg_dump backup method, incremental backups are not supported.

  5. Click Protect.

    Note:

    If the PostgreSQL instance is deployed on the root LVM, then Snapshot backup method is not recommended.

    In case of cluster deployment of PostgreSQL, instances can be protected of primary or standby node.