Conversation
The gpbackup timestamp (YYYYMMDDHHMMSS) is the unique backup ID and has one-second granularity. It also names the backup directory and lock file, so a second gpbackup started within the same second fails with "A backup with timestamp ... is already in progress. Wait 1 second and try the backup again." This often happens when scripts back up schemas one by one. Document this limitation in the gpbackup reference and add a tip to the full backup guide. Suggest adding a delay between runs, or backing up multiple schemas or tables in a single gpbackup command. Both docs/ and versioned_docs/version-2.x/ are updated. See: apache/cloudberry#1714 Assisted-by: Claude Code
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Document that
gpbackupcannot start more than one backup within the same second.sys-utilities/gpbackup.md: add a paragraph in the Description section explaining the one-second timestamp granularity, the resulting error message, and how to avoid it.sys-admin/backup-and-restore/perform-full-backup-and-restore.md: add a tip under "Filter by schema" for scripts that back up schemas one by one.Both
docs/andversioned_docs/version-2.x/are updated.Why
The backup timestamp (
YYYYMMDDHHMMSS) is the unique backup ID and also names the backup directory and lock file. When a script runsgpbackuprepeatedly and two runs start in the same second, the later one fails with:This is an architectural limitation rather than a bug, as discussed in apache/cloudberry#1714.
See: apache/cloudberry#1714