Skip to content

Commit 67e4b69

Browse files
authored
Fix callouts (#1436)
1 parent 10e9b09 commit 67e4b69

File tree

4 files changed

+16
-2
lines changed

4 files changed

+16
-2
lines changed

modules/deploy/pages/redpanda/manual/disaster-recovery/shadowing/failover-runbook.adoc

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,10 @@
44
:env-linux: true
55
:page-categories: Management, High Availability, Disaster Recovery, Emergency Response
66

7+
[NOTE]
8+
====
79
include::shared:partial$enterprise-license.adoc[]
10+
====
811

912
This guide provides step-by-step procedures for emergency failover when your primary Redpanda cluster becomes unavailable. Follow these procedures only during active disasters when immediate failover is required.
1013

modules/deploy/pages/redpanda/manual/disaster-recovery/shadowing/failover.adoc

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,12 +2,15 @@
22
:description: Learn how failover can transform shadow topics into fully writable resources during disasters.
33
:page-categories: Management, High Availability, Disaster Recovery
44

5+
[NOTE]
6+
====
57
include::shared:partial$enterprise-license.adoc[]
6-
7-
include::shared:partial$emergency-shadowing-callout.adoc[]
8+
====
89

910
Failover is the process of modifying shadow topics or an entire shadow cluster from read-only replicas to fully writable resources, and ceasing replication from the source cluster. You can fail over individual topics for selective workload migration or fail over the entire cluster for comprehensive disaster recovery. This critical operation transforms your shadow resources into operational production assets, allowing you to redirect application traffic when the source cluster becomes unavailable.
1011

12+
include::shared:partial$emergency-shadowing-callout.adoc[]
13+
1114
== Failover behavior
1215

1316
When you initiate failover, Redpanda performs the following operations:

modules/deploy/pages/redpanda/manual/disaster-recovery/shadowing/monitor.adoc

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,15 @@
22
:description: Monitor Shadowing health with status commands, metrics, and best practices for tracking replication performance.
33
:page-categories: Management, Monitoring, Disaster Recovery
44

5+
[NOTE]
6+
====
57
include::shared:partial$enterprise-license.adoc[]
8+
====
69

710
Monitor your shadow links to ensure proper replication performance and understand your disaster recovery readiness. Use `rpk` commands, metrics, and status information to track shadow link health and troubleshoot issues.
811

12+
include::shared:partial$emergency-shadowing-callout.adoc[]
13+
914
== Status commands
1015

1116
List existing shadow links:

modules/deploy/pages/redpanda/manual/disaster-recovery/shadowing/overview.adoc

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,10 @@
33
:env-linux: true
44
:page-categories: Management, High Availability, Disaster Recovery
55

6+
[NOTE]
7+
====
68
include::shared:partial$enterprise-license.adoc[]
9+
====
710

811
Shadowing is Redpanda's enterprise-grade disaster recovery solution that establishes asynchronous, offset-preserving replication between two distinct Redpanda clusters. A cluster is able to create a dedicated client that continuously replicates source cluster data, including offsets, timestamps, and cluster metadata. This creates a read-only shadow cluster that you can quickly failover to handle production traffic during a disaster.
912

0 commit comments

Comments
 (0)