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

Steps to perform after Restore and Recovery for PostgreSQL cluster deployment

The following procedure is applicable for snapshot and pg_basebackup backup methods, and not applicable for the pg_dumpall and pg_dump backup methods.

If the recovery done from backup of PostgreSQL primary node to same or alternate primary node, do the following on the PostgreSQL standby node:

  • Stop PostgreSQL services.

  • Clean the PostgreSQL data directory path.

  • Run the $ pg_basebackup -h primary_node_ip -U db_replication_user --checkpoint=fast -D data_directory_path -R --slot=unique_slot_name -C command with database user.

  • Start the PostgreSQL services.

If the recovery done from backup of PostgreSQL standby node to same or alternate primary node, do the following on the PostgreSQL primary node:

  • Stop the PostgreSQL services.

  • Delete the standby.signal file from the data directory.

  • Fix the archive command in postgresql.conf file from data directory.

    For example: For Linux: archive_command='cp %p /path/to/archive/location/%f' and for Windows: archive_command = 'copy "%p" "path\\to\\archive\\location\\%f"'

  • Start the PostgreSQL services.

PostgreSQL standby node:

  • Stop PostgreSQL services.

  • Clean the PostgreSQL data directory path.

  • Run the below command with database user:$ pg_basebackup -h master_node_ip -U db_replication_user --checkpoint=fast -D data_directory_path -R --slot=unique_slot_name -C

  • Start the PostgreSQL services.

Note:

When the recovery is done from backup of PostgreSQL primary node to PostgreSQL standby node, then the standby node becomes an independent primary node.