gpbackup Error: “A backup with timestamp <ID> is already in progress” When Multiple Backups Triggered Simultaneously
Article ID: 414621
Updated On:
Products
Issue/Introduction
Users may encounter the following error while running gpbackup operations:
[CRITICAL]:-A backup with timestamp <ID> is already in progress. Wait 1 second and try the backup again.
This issue typically occurs when multiple gpbackup processes are triggered at the exact same second, causing duplicate timestamp conflicts. Since gpbackup uses the current timestamp as a unique identifier for each backup session, concurrent executions within the same second can lead to this error.
Cause
- The gpbackup utility assigns a timestamp using the current time, formatted as YYYYMMDDHHMMSS, as a unique backup identifier.
- When two or more backups are initiated within the same second, they generate identical timestamp IDs, leading to a conflict.
- gpbackup detects that another process is already using that timestamp and aborts the duplicate process to prevent corruption or overlapping writes.
Resolution
Workaround:
To avoid triggering concurrent backups within the same second:
- Schedule backups a few seconds or minutes apart.
- If you are automating backups through a script, use a "sleep" between invoking the backups to ensure different timestamps.
Permanent Solution (Planned):
- The R&D team is actively working on improvements to gpbackup to support high-frequency and overlapping backup executions while maintaining data integrity.
- This enhancement will eliminate timestamp conflicts and improve concurrent backup handling.
- Users are encouraged to monitor the official release notes for announcements regarding this enhancement in upcoming gpbackup releases.
Feedback
