Skip to content

Document Non-Disruptive Restoration #73

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 Non-Disruptive Restoration #73

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/non-disruptive-restoration/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
---
title: Non-Disruptive Restoration
description: Restore data without impacting application performance or response time.
menu:
docs_{{ .version }}:
identifier: capabilities-non-disruptive-restoration
name: Non-Disruptive Restoration
parent: capabilities
weight: 20
product_name: kubestash
menu_name: docs_{{ .version }}
section_menu_id: concepts
---

# Non-Disruptive Restoration

KubeStash restores data without impacting application performance or response time. A `RestoreSession` does not have to overwrite the source. The default and recommended pattern is to restore into an alternate namespace, PVC, or even a separate cluster, validate integrity, and only then cut traffic over. Because the live production workload is never touched during recovery, response time and throughput remain at steady state. `BackupVerifier` runs scheduled, isolated restore drills against every backup, providing continuous evidence that any snapshot is fully recoverable, again without disturbing production.

## 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) | |
| Non-Disruptive Restoration | RestoreSession targets a different namespace, PVC, or cluster so the live workload is untouched. BackupVerifier proves recoverability in an isolated environment without affecting production latency. |
Loading