docs(influxdb3 backup-restore): add object versioning guidance#7162
Open
jstirnaman wants to merge 4 commits into
Open
docs(influxdb3 backup-restore): add object versioning guidance#7162jstirnaman wants to merge 4 commits into
jstirnaman wants to merge 4 commits into
Conversation
Add a new "Object storage features and backup planning" section to the shared Core/Enterprise backup-restore page covering: - Short-term object versioning as protection against errant writes and accidental deletions (1-2 day retention). - Limitations: Parquet files are mostly immutable, so versioning helps most with single-file recovery rather than mass restores. - Cost trade-offs: versioning costs scale with object update frequency, amplified by compaction-driven object writes. - Provider-side features (versioning, soft delete, PITR) are not a substitute for periodic backups to a separate object store. - Provider-agnostic backup-to-different-bucket pattern with low-load timing guidance. - Enterprise-only cross-reference: cross-bucket restores affect license binding (gated with show-in). Restructure the section: drop the "Important considerations" umbrella and promote its subsections to top-level subject-oriented headings (`Recovery expectations`, `Licensing and disaster recovery`, `Containerized deployments`, `Excluded files`, `Backup timing`). No inbound external links use the renamed anchors. Closes influxdata/DAR#665
Contributor
Vale Style Check Results
Warnings (2)
✅ Check passed |
github-actions
Bot
added
product:shared
Contributor
|
Contributor
📦 PR Preview — Preview Bot
Pages included in this preview
Preview auto-deploys on push. Will be cleaned up when PR closes. |
jstirnaman
commented
Apr 28, 2026
reidkaufmann
approved these changes
May 1, 2026
Contributor
reidkaufmann
left a comment
reidkaufmann
left a comment
There was a problem hiding this comment.
Looks fine. Could mention cost concerns with versioning and provider-side features, but this is sufficient.
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
2 participants
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
Adds a new "Object storage features and backup planning" section to the shared Core/Enterprise backup-restore page covering:
show-in).Sources: the original recommendation comes from the existing Clustered backup-restore page; additional generalized guidance comes from internal SME comments on EAR#6827
Adjacent restructuring
The shared file's
## Important considerationsumbrella was a heterogeneous catch-all. Promoted its###subsections to##and renamed a few for subject orientation:### Recovery expectations## Recovery expectations### License files(Enterprise)## Licensing and disaster recovery(Enterprise)### Docker considerations## Containerized deployments### Table snapshot files## Excluded files### Timing recommendations## Backup timingVerified no inbound links use the previous anchors.
Closes influxdata/DAR#665
Test plan