Skip to content

K8SPS-678 Documented the support of page tracking for incremental backups - #241

Open
nastena1606 wants to merge 1 commit into
mainfrom
K8SPS-678-Doc-page-tracking-support-for-incremental-backups
Open

K8SPS-678 Documented the support of page tracking for incremental backups#241
nastena1606 wants to merge 1 commit into
mainfrom
K8SPS-678-Doc-page-tracking-support-for-incremental-backups

Conversation

@nastena1606

Copy link
Copy Markdown
Collaborator

No description provided.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The updated doc introduces broken internal links (missing ReleaseNotes file and incorrect PITR anchor) that should be fixed before merging.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Updates the incremental backups documentation to clarify backup chains/restore behavior and to document page tracking support for faster incremental backups.

Changes:

  • Reworked the “Backup chain”, “How an incremental backup runs”, and “Restore” sections for clearer guidance and updated wording.
  • Documented .incr path layout used to discover and apply incremental chains during restore.
  • Added a new “Speed up incremental backups with page tracking” section, including configuration examples.
File summaries
File Description
docs/backups-incremental.md Refines incremental backup/restore documentation and adds page tracking configuration guidance.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 2
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread docs/backups-incremental.md Outdated
## Speed up incremental backups with page tracking

Incremental destinations use an `.incr` segment in the path so the Operator can tell full and incremental artifacts apart. A typical pattern resembles `prefix/<cluster>-<timestamp>-full.incr/<cluster>-<timestamp>-incr`; exact layout follows your `prefix` and storage settings.
!!! admonition "Version added: [1.3.0](ReleaseNotes/Kubernetes-Operator-for-PS-RN1.3.0.md)"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants