Skip to content

Document Active-Active Data Replication between Primary and DR Sites #75

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
+26 −0
Open

Document Active-Active Data Replication between Primary and DR Sites #75

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/active-active-data-replication/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
---
title: Active-Active Data Replication between Primary and DR Sites
description: Real-time, secure data replication between primary DC and DR sites in active-active mode.
menu:
docs_{{ .version }}:
identifier: capabilities-active-active-data-replication
name: Active-Active Data Replication between Primary and DR Sites
parent: capabilities
weight: 40
product_name: kubestash
menu_name: docs_{{ .version }}
section_menu_id: concepts
---

# Active-Active Data Replication between Primary and DR Sites

KubeStash supports real-time and secure data replication between the primary data center (DC) and the disaster recovery (DR) site operating in active-active mode. Backup snapshots are replicated across multiple `BackupStorage` targets simultaneously, so the same logical snapshot is materialized in DC, DR, and any Near-DR site. For the live data path, KubeStash works together with KubeDB, which provides engine-native synchronous multi-master replication (MySQL Group Replication, Galera, MongoDB cross-region replica sets, PostgreSQL Patroni stretched clusters). Both sites remain authoritative and writable, with RPO near zero. Data in transit is encrypted end to end.

## 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) | |
| Active-Active Data Replication between Primary and DR Sites | Real-time replication across primary DC and DR sites in active-active mode. Multi-target BackupStorage for snapshot replication; KubeDB for engine-native synchronous multi-master replication of the live data layer. |
Loading