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

Redirect a restore to a different Greenplum configuration

When you redirect to a different client, you can restore the Greenplum databases to a NetBackup for Greenplum client other than the one that was originally backed up. The administrator can direct restores to any client (regardless of which client performed the backup).

Review the following requirements:

  • The version of Greenplum must be the same on both clients.

  • The contents of the following directory must be the same on each client:

    /usr/local/greenplum-<version>/bin

  • The target Greenplum system must have the same $GPHOME directory structure as the source system.

  • The user ID of the Greenplum database user must match that of the original host's user ID.

  • The MASTER_DATA_DIRECTORY must be the same on both the source and the destination clients.

  • The VMware Tanzu Greenplum Backup and Restore package utility and all other required utilities must be present in the following directory. This requirement applies to the coordinator and the segment hosts on the target client.

    /usr/local/greenplum-<version>/bin

To redirect a restore to a different Greenplum configuration

  1. Ensure that the NetBackup server is configured to allow for redirected restores.

    If the No.Restrictions file is not used then configure a peername file in the altnames directory for each host that participates in the restore. Every destination segment host must have access to the images from the source segment hosts. This requirement applies to the coordinator and any mirrored coordinator and mirrored segment hosts. For more information, see the NetBackup Web UI Administrator's Guide.

  2. Create a yaml file from the example yaml file.

    In this file use the coordinator_hosts and segment_hosts options to list all the source hosts that are part of the backed up Greenplum configuration.

    coordinator_hosts: "source_cooridnator_hostname,source_mirrored_coordiantor_hostname"
segment_hosts: "source_segment_host1,source_segment_host2,source_segment_host3,…"
  3. On the coordinator, determine which timestamp that you want to restore to. Use the bplist command: 
    /usr/openv/netbackup/bin/bplist -l -t 24 -C client -S server
 -unix_files -R 999 /

    The timestamp is the directory name before the file. For example:

    /data/coordinator/gpseg-1/backups/20241107/20241107135750/
gpbackup_20241107135750_report

    In the previous line, the timestamp is 20241107135750.

  4. On the coordinator, run the gprestore command.
    gprestore --plugin-config path_to_yaml_file --timestamp 
timestamp --redirect-db restoredb --create-db

    The value for timestamp should match the timestamp that you found in step 3. For example, 20241107135750.