Search <book_title>...

Important Update: Cohesity Products Documentation

All Cohesity product documentation are now managed via the Cohesity Docs Portal: https://docs.cohesity.com/HomePage/Content/home.htm. Some documentation available here may not reflect the latest information or may no longer be accessible.

NetBackup™ for Greenplum Administrator's Guide

Last Published: 2025-03-18

Product(s): NetBackup (11.0)

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

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.
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,…"
```
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.
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.