Skip to content

Document Complete Transaction History with Point-in-Time Recovery #77

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tamalsaha wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Document Complete Transaction History with Point-in-Time Recovery #77

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions docs/concepts/capabilities/complete-transaction-history-pitr/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
---
title: Complete Transaction History with Point-in-Time Recovery
description: Complete transaction history database with point-in-time recovery (PITR) to any second.
menu:
docs_{{ .version }}:
identifier: capabilities-complete-transaction-history-pitr
name: Complete Transaction History with Point-in-Time Recovery
parent: capabilities
weight: 60
product_name: kubestash
menu_name: docs_{{ .version }}
section_menu_id: concepts
---

# Complete Transaction History with Point-in-Time Recovery

KubeStash maintains a complete transaction history database for supported engines (PostgreSQL, MySQL, MongoDB, and equivalents) by continuously archiving WAL, binlog, and engine-equivalent transaction logs. Combined with periodic base snapshots, this enables Point-in-Time Recovery (PITR) to any second within the retention window. The transaction log archive itself is the complete, queryable transaction history of record, which satisfies audit and regulatory requirements for transaction-level traceability without standing up a separate CDC pipeline.

## Related concepts

- [BackupConfiguration](../../crds/backupconfiguration/)
- [BackupBlueprint](../../crds/backupblueprint/)
- [RestoreSession](../../crds/restoresession/)
- [RetentionPolicy](../../crds/retentionpolicy/)
- [BackupVerifier](../../crds/backupverifier/)
1 change: 1 addition & 0 deletions docs/concepts/what-is-kubestash/overview/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,3 +37,4 @@ section_menu_id: concepts
| Auto Backup | Share backup configuration across workloads using templates. Enable backup for a target application via annotation. |
| Point-In-Time Recovery (PITR) | Restore a set of files from a time in the past. |
| Role Based Access Control (RBAC) | |
| Complete Transaction History with Point-in-Time Recovery | Complete transaction history via continuous WAL / binlog archiving. Point-in-Time Recovery (PITR) to any second within the retention window. |
Loading