NetBackup™ for Greenplum Administrator's Guide

Last Published:
Product(s): NetBackup & Alta Data Protection (11.0)
  1. Introducing NetBackup for Greenplum
    1.  
      About NetBackup for Greenplum
    2.  
      NetBackup for Greenplum terminology
    3.  
      Features of NetBackup for Greenplum
    4.  
      NetBackup for Greenplum technical overview
    5.  
      Sequence of operation for NetBackup for Greenplum backups
  2. Installing NetBackup for Greenplum
    1.  
      Verifying the operating system and platform compatibility
    2.  
      NetBackup server and client requirements
    3.  
      Greenplum server software requirements
  3. Configuring NetBackup for Greenplum
    1.  
      About NetBackup for Greenplum configuration
    2. About configuring a backup policy for Greenplum
      1.  
        Adding a NetBackup for Greenplum policy
      2.  
        About policy attributes
      3.  
        Schedule properties
      4. NetBackup for Greenplum backup types
        1.  
          Configure an application backup schedule
        2.  
          Example application backup schedule
        3.  
          Configure automatic backup schedules
        4.  
          Example automatic backup schedule
      5.  
        Add clients to a policy
      6.  
        Adding NetBackup for Greenplum scripts to the backup selections list
    3. About the backup script for NetBackup for Greenplum
      1.  
        Modify the backup script for NetBackup for Greenplum
    4.  
      Best practices for Greenplum backups
    5.  
      Configuration options for backup jobs
    6.  
      Use of the --jobs option or backup streams and the effect on NetBackup jobs and throttling options
    7.  
      The nbgpbackup_config.yaml file
    8.  
      About permissions for NetBackup for Greenplum log files
    9.  
      Perform a manual backup
  4. Using NetBackup for Greenplum
    1.  
      About Greenplum database backups
    2.  
      Perform a user-directed backup for Greenplum
    3. About restoring a Greenplum database
      1.  
        Restore a Greenplum database
      2.  
        Redirect a restore to a different Greenplum configuration
  5. Troubleshooting NetBackup for Greenplum
    1. NetBackup debug logs and reports
      1.  
        Enabling the debug logs manually
      2.  
        About the bphdb directory on the database client
      3.  
        Setting the debug level
      4.  
        About NetBackup server reports
    2.  
      Minimizing time-out failures on large database restores
    3.  
      Troubleshooting of Greenplum backups that are canceled mid-backup
  6. Appendix A. Register authorized locations
    1.  
      Registering authorized locations used by a NetBackup database script-based policy

NetBackup for Greenplum technical overview

NetBackup for Greenplum uses the gpbackup and gprestore commands to backup and restore Greenplum databases. These commands are not part of the Tanzu Greenplum database software installation. The Tanzu Greenplum Backup and Restore software package contains the gpbackup and gprestore commands so it must be installed with the database software. The NetBackup for Greenplum agent is a command-line plug-in for gpbackup and gprestore. (The NetBackup for Greenplum plug-in command-line is nbgpbackup.)

Greenplum is a distributed database that runs on multiple hosts. The database uses one coordinator host and multiple segment hosts. Each segment host can contain multiple segments. Each host must have the NetBackup client software installed. The Greenplum agent uses the Datastore policy type.

For more information on the Greenplum Database, see your Greenplum documentation.

The gpbackup command calls nbgpbackup multiple times during a backup. On the segment hosts nbpgbackup is called many times to protect a database. For the best performance, the agent attempts to put multiple files from a segment into an image. To achieve this action the agent uses shared memory to pass the data to a nbgpbackup process that communicates with the NetBackup servers. Each NetBackup stream is a separate process that services its shared memory. After the segment host backups are complete gpbackup also calls nbgpbackup multiple times on the coordinator host. But unlike with the segment hosts, each of those calls results in separate backup images.

Each segment on each segment host is backed up into a separate image. To achieve this action the number_of_streams option in the config file must be at least equal to the number of segments per host. If more than one stream per segment is configured, then there can be multiple images for each segment.