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

About restoring a Greenplum database

NetBackup for Greenplum supports incremental restores from the incremental timestamps.

Limitations

The following limitations apply to Greenplum database restores:

  • The NetBackup for Greenplum plug-in does not support the restore_subset option. It should stay set to off in the nbgpbackup_config.yaml file.

  • The plug-in does not support the gprestore command with the --incremental option.

  • When you use the optimize_restore option, then NetBackup for Greenplum uses a cache directory. The agent makes every attempt to clean up the cache directory. However, if errors occur during a restore then you may need to manually clean up the cache directory on all segment hosts.

Restore options

For the best restore performance set incremental_optimize_restore: on in the nbgpbackup_config.yaml file. This setting starts a job for each image that is needed for the restore. By default, this setting is turned off and each restore_data request is a separate job. For a large number of tables, in the media server host properties update the Client read timeout to a higher value. For example, 14400.

Table: Effect of restore options on number of jobs

Non-optimized

optimize_restore

incremental_optimize_restore

Job for each time that nbgpbackup is called. This number can be thousands of jobs.

A job for each image that is used during the database restore.

A job for each image that is used during the database restore.

Table: Restore options and use of the disk cache on segment hosts

Non-optimized

optimize_restore

incremental_optimize_restore

No

Yes. Each image that is requested is restored to the cache directory even if a file in the image is not needed. Files are deleted after they are restored to the Greenplum database.

No

Table: Effect of restore options on speed

Non-optimized

optimize_restore

incremental_optimize_restore

Slowest

Fastest for any restores from a full backup.

Fastest for any restores from incremental backups.

Table: Restore options and use of shared memory

Non-optimized

optimize_restore

incremental_optimize_restore

No

No

Yes