HDDS-16147. Document OM metadata backup including bucket snapshots - #526
Draft
jojochuang wants to merge 3 commits into
Draft
HDDS-16147. Document OM metadata backup including bucket snapshots#526jojochuang wants to merge 3 commits into
jojochuang wants to merge 3 commits into
Conversation
Add Administrator Guide backup-and-recovery section with v2 checkpoint backup steps, multi-batch helper script, and prescriptive cold restore from offline tarballs; cross-link from OM disk replacement. Co-authored-by: Cursor <cursoragent@cursor.com>
sadanand48
reviewed
Aug 11, 2026
|
|
||
| usage() { | ||
| cat <<'EOF' | ||
| Usage: om-metadata-backup.sh [options] --base-url URL |
There was a problem hiding this comment.
I feel we could add a java based tool itself instead of adding bash code. I don't see the hardlink construction logic here and we could re-use the existing code that follower uses to construct the db from the tar
Replace manual live-OM restore steps with the HDDS-16171 repair CLI and add download subcommand reference in the Ozone Repair guide. Co-authored-by: Cursor <cursoragent@cursor.com>
…load. Lead with the repair CLI for live-OM backup and restore, keep HTTP/curl as an alternative, and align command examples with the HDDS-16171 tool behavior. Co-authored-by: Cursor <cursoragent@cursor.com>
sadanand48
reviewed
Aug 25, 2026
|
|
||
| ## Alternative: HTTP checkpoint download | ||
|
|
||
| Use `curl` or `om-metadata-backup.sh` only when the backup host has no Ozone CLI. This runs the same `/v2/dbCheckpoint` transfer, but the saved tarball stays in inode-based form and needs hard link reconstruction before install. |
There was a problem hiding this comment.
problem with direct curl for V2 is that it doesn't construct the paths from hardlink file. We can document this limitation if we are going with the alternative , while the backup is available it needs the unpack logic from follower
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
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.
Summary
HDDS-16147: https://issues.apache.org/jira/browse/HDDS-16147
/v2/dbCheckpointwithincludeSnapshotData=true, Ozone 2.2+).om-metadata-backup.shfor multi-batch checkpoint downloads (same logic as OM HA bootstrap)./dbCheckpointomits bucket snapshot data.What is the link to the Apache Jira?
https://issues.apache.org/jira/browse/HDDS-16147
How was this patch tested?
pnpm run build— passes (no broken links)Test plan