[
https://issues.apache.org/jira/browse/HDDS-16147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wei-Chiu Chuang reassigned HDDS-16147:
--------------------------------------
Assignee: Wei-Chiu Chuang
> [Docs] OM metadata backup and cold restore procedure
> ----------------------------------------------------
>
> Key: HDDS-16147
> URL: https://issues.apache.org/jira/browse/HDDS-16147
> Project: Apache Ozone
> Issue Type: Task
> Components: documentation
> Reporter: Wei-Chiu Chuang
> Assignee: Wei-Chiu Chuang
> Priority: Major
> Labels: documentation, pull-request-available, website
>
> Document operator procedures for backing up Ozone Manager (OM) metadata,
> including bucket snapshot RocksDB state, and restoring from offline
> checkpoint tarballs.
> h3. Scope
> * Add Administrator Guide → Operations → Backup and recovery section
> * OM metadata backup runbook using leader OM {{/v2/dbCheckpoint}} with
> {{includeSnapshotData=true}} (Ozone 2.2+, inode-based transfer)
> * Multi-batch backup helper script (same client logic as OM HA bootstrap)
> * Prescriptive cold-restore steps from an offline tarball when no live OM
> leader is available
> * Clarify legacy v1 {{/dbCheckpoint}} transfers AOS metadata only (no bucket
> snapshots)
> * Cross-link from OM disk replacement standalone recovery path
> h3. Motivation
> Operators need a published procedure for consistent OM metadata backups that
> include bucket snapshot state, and guidance for disaster recovery when
> bootstrap from a live leader is not possible.
> h3. Acceptance criteria
> * New docs page under
> {{docs/05-administrator-guide/03-operations/16-backup-and-recovery/}}
> * {{pnpm run build}} passes
> * PR to apache/ozone-site
> h3. Related
> * OM bootstrapping with snapshots (HDDS-12090)
> * Draft PR: https://github.com/apache/ozone-site/pull/526
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]