From 17fa691bac015fe714aa050bcf5ec656af99c343 Mon Sep 17 00:00:00 2001 From: Tamal Saha Date: Tue, 2 Jun 2026 21:42:45 +0600 Subject: [PATCH] Document Non-Disruptive Restoration Adds a feature card and an in-depth page describing how KubeStash supports this capability. --- .../features/non-disruptive-restoration.md | 21 +++++++++++++++++++ data/products/kubestash.json | 13 ++++++++++++ 2 files changed, 34 insertions(+) create mode 100644 content/features/non-disruptive-restoration.md diff --git a/content/features/non-disruptive-restoration.md b/content/features/non-disruptive-restoration.md new file mode 100644 index 00000000..2c489cfd --- /dev/null +++ b/content/features/non-disruptive-restoration.md @@ -0,0 +1,21 @@ +--- +title: Non-Disruptive Restoration +description: Restore data without impacting application performance or response time. +menu: + main: + parent: features + name: Non-Disruptive Restoration + weight: 20 +--- + +# 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](/docs/latest/concepts/crds/backupconfiguration/) +- [BackupBlueprint](/docs/latest/concepts/crds/backupblueprint/) +- [RestoreSession](/docs/latest/concepts/crds/restoresession/) +- [RetentionPolicy](/docs/latest/concepts/crds/retentionpolicy/) +- [BackupVerifier](/docs/latest/concepts/crds/backupverifier/) diff --git a/data/products/kubestash.json b/data/products/kubestash.json index 804465f9..82bf0801 100644 --- a/data/products/kubestash.json +++ b/data/products/kubestash.json @@ -168,6 +168,19 @@ }, "summary": "", "description": "Stash comes with native support for monitoring via Prometheus. You can use builtin Prometheus scrapper or CoreOS Prometheus Operator to monitor your database in Kubernetes. You can use the Grafana to view key operational metrics, including compute/memory/storage capacity utilization, I/O activity, and instance connections." + }, + { + "title": "Non-Disruptive Restoration", + "image": { + "src": "/assets/images/addons/illustrations/declarative-api.png", + "alt": "http" + }, + "icon": { + "src": "/assets/images/products/stash/features/declarative-api.svg", + "alt": "http" + }, + "summary": "Restore data without impacting application performance or response time.", + "description": "KubeStash restores data without impacting the performance or response time of the live workload. A RestoreSession writes into an alternate namespace, PVC, or cluster while production keeps serving traffic. BackupVerifier runs scheduled restore drills out of band to prove recoverability continuously." } ], "versions": [