GPDR full backup is not completing

Products

• VMware Tanzu Data Intelligence

Issue/Introduction

When running the following command:

 gpdr backup --type full --compress-type gz --compress-level 4

 

The following message appears as the backup fails:

gpdr:gpadmin:<server_name>-[INFO]:-Detected that another restore point is getting created. Current restore point creation will wait until the other one has completed.

 

DEBUG logs show:

20260110:14:37:30 gpdr:gpadmin:<server_name>-[DEBUG]:-Still waiting for the other restore point to get created which might mean one of two things: either the other create-restore-point command is indeed still running or there is an orphaned lock file left over from a previous create-restore-point command. If the lock file /usr/local/gpdr/state/gpdr_create_restore_point.lock is indeed orphaned, you might want to either contact Support or remove the lock file manually. Note that the wait will continue until the timeout has exceeded, or the new lock file can be created, or there is a user interrupt.

Resolution

This is a known issue that makes GPDR vulerable to issues caused by exiting from receiving SIGHUP like leaking incomplete backups or leaking create_restore_point lock files.

The workaround is to manually delete the lock file.

This issue is fixed in GPDR version 1.4, please see Release Notes.