Greenplum Disaster Recovery(GPDR) archive command failed with exit code 103 and unable to find a valid repository

Products

• VMware Tanzu Data Intelligence
• VMware Tanzu Greenplum
• VMware Tanzu Greenplum / Gemfire

Issue/Introduction

The archive_command for a Greenplum Disaster Recovery (GPDR) failed with the following message in the segment log:

2026-02-07 08:37:28.541138 +03,,,p16013,th-504941824,,,,0,,,seg12,,,,,"LOG","00000","3rd party error log:
ERROR: [103]: unable to find a valid repository:
       repo1: [FileMissingError] unable to load info file '/<path_to_repo>/gpseg12/archive/gpdb-seg12/archive.info' or '/<path_to_repo>/gpseg12/archive/gpdb-seg12/archive.info.copy':
       FileMissingError: unable to open missing file '/<path_to_repo>/gpseg12/archive/gpdb-seg12/archive.info' for read
       FileMissingError: unable to open missing file '/<path_to_repo>/gpseg12/archive/gpdb-seg12/archive.info.copy' for read
       HINT: archive.info cannot be opened but is required to push/get WAL segments.
       HINT: is archive_command configured correctly in postgresql.conf?
       HINT: has a stanza-create been performed?
       HINT: use --no-archive-check to disable archive checks during backup if you have an alternate archiving scheme.
",,,,,,,,"SysLoggerMain","syslogger.c",719,
2026-02-07 08:37:28.543489 +03,,,p16035,th-504941824,,,,0,,,seg12,,,,,"LOG","00000","archive command failed with exit code 103","The failed archive command was: pgbackrest --stanza=gpdb-seg12 --config=/usr/local/gpdr/configs/pgbackrest-seg12.conf archive-push pg_wal/000000090000096E00000004 --pg1-path $(pwd)",,,,,,0,,"pgarch.c",661,

A build up of WAL files on the primary cluster is also seen.

Cause

Files in the repository filesystem were deleted for one or more segments. This caused the file archive.info to be missing.

 

Resolution

The recommended solution is to reconfigure GPDR from the beginning.The reconfiguration will clean up any WAL backlog/accumulation.

1. Remove the existing GPDR configuration files on the primary cluster hosts. These configuration files are located under '/usr/local/gpdr/configs' and are named 'pgbackrest-seg*.conf'
2. Delete the existing backup repository.
3. Run 'gpdr configure backup -config-file <config_file>'. Note: This will restart the cluster.
4. Perform a full backup using 'gpdr backup -type full'.
5. Restore the backup on the recovery cluster.

Refer to "Data Synchronization Tasks" for details on the steps.