gpdr backup reports error "latest backup directory is not consistent across segments"

Products

• VMware Tanzu Greenplum
• VMware Tanzu Greenplum / Gemfire
• VMware Tanzu Data Suite
• VMware Tanzu Data Suite

Issue/Introduction

gpdr backup error

Resolution

Use pgbackrest commands to expire backups on individual segments to make the segments consistent.

For example, if the repository is an NFS mounted directory (The example uses environment variables to indicate what needs to be changed to appropriate values):

To list the backups for a segment:

ssh sdw1 # ssh to the correct segment host for the segment
source /usr/local/greenplum-db/greenplum_path.sh
source /usr/local/gpdr/gpdr_path.sh

# Set SEG to the segment ID, this example is for gpseg0
SEG=0
# Set LABEL to the backup-label
LABEL=20260217-092851F_20260217-134206I
# Set REPO to the location of the backups
REPO=/data/gpdr

# List all backups for the segment:
pgbackrest info --config=/usr/local/gpdr/configs/pgbackrest-seg${SEG}.conf --log-level-console=info --repo1-path=${REPO}/gpseg${SEG}

# List a particular backup:
pgbackrest info --config=/usr/local/gpdr/configs/pgbackrest-seg${SEG}.conf --log-level-console=info --repo1-path=${REPO}/gpseg${SEG} --set=${LABEL} --stanza=gpdb-seg${SEG}

# To expire a particular backup:
pgbackrest expire --config=/usr/local/gpdr/configs/pgbackrest-seg${SEG}.conf --log-level-console=info --repo1-path=${REPO}/gpseg${SEG} --repo1-type=posix --set=${LABEL} --stanza=gpdb-seg${SEG}

If the repository is an S3 location, then the parameters need to be changed to specify the location.

Examples of the parameters for the cluster can be found in the log files in /usr/local/gpdr/logs/