Skip to content

Commit 5d4dd65

Browse files
authored
shadowing updates (#1472)
1 parent d827ff4 commit 5d4dd65

File tree

4 files changed

+32
-5
lines changed

4 files changed

+32
-5
lines changed

modules/manage/pages/disaster-recovery/shadowing/overview.adoc

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -62,6 +62,11 @@ Choose your implementation approach:
6262
* **xref:./failover.adoc[Planned Failover]** - Controlled disaster recovery testing and migrations
6363
* **xref:./failover-runbook.adoc[Failover Runbook]** - Rapid disaster response procedures
6464

65+
[TIP]
66+
====
67+
include::shared:partial$shadow-link-management-tip.adoc[]
68+
====
69+
6570
== Disaster readiness checklist
6671

6772
Before a disaster occurs, ensure you have:

modules/manage/pages/disaster-recovery/shadowing/setup.adoc

Lines changed: 25 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,24 +4,45 @@
44
:page-categories: Management, High Availability, Disaster Recovery
55
:page-aliases: deploy:redpanda/manual/disaster-recovery/shadowing/setup.adoc
66

7+
include::shared:partial$shadow-link-management-tip.adoc[]
8+
9+
== Prerequisites
10+
711
[NOTE]
812
====
913
include::shared:partial$enterprise-license.adoc[]
1014
====
1115

12-
== Prerequisites
13-
1416
=== License and cluster requirements
1517

16-
- You must have xref:get-started:licensing/overview.adoc[Enterprise Edition] licenses on both clusters.
17-
1818
- Both clusters must be running Redpanda v25.3 or later.
1919

20+
- If you use Redpanda Console, ensure that it is running v3.30 or later.
21+
22+
- You must have xref:get-started:licensing/overview.adoc[Enterprise Edition] licenses on both clusters.
23+
2024
[TIP]
2125
====
2226
Deploy clusters in different geographic regions to protect against regional disasters.
2327
====
2428

29+
=== Cluster properties
30+
31+
Both source and shadow clusters must have the xref:reference:properties/cluster-properties.adoc#enable_shadow_linking[`enable_shadow_linking`] cluster property set to `true`.
32+
33+
To enable this property, run:
34+
[,bash]
35+
----
36+
rpk cluster config set enable_shadow_linking true
37+
----
38+
39+
[NOTE]
40+
====
41+
This cluster property must be configured using `rpk` or the Admin API v1 before you can create shadow links through any interface.
42+
====
43+
44+
To learn more about configuring cluster properties, see xref:manage:cluster-maintenance/cluster-property-configuration.adoc[].
45+
2546
=== Administrative access
2647

2748
Superuser access is required on both clusters through xref:get-started:rpk/index.adoc[`rpk`], the Admin API, or xref:console:index.adoc[Redpanda Console] to create and manage shadow links.

modules/reference/pages/properties/cluster-properties.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1589,7 +1589,7 @@ Enable creating shadow links from this cluster to a remote source cluster for da
15891589

15901590
*Enterprise license required:* `true`
15911591

1592-
*Default:* `true`
1592+
*Default:* `false`
15931593

15941594
*Related topics:*
15951595

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
You can create and manage shadow links using xref:get-started:rpk/index.adoc[`rpk`], xref:console:index.adoc[Redpanda Console], or the link:https://docs.redpanda.com/api/doc/admin/v2/[Admin API v2^], giving you flexibility in how you interact with your disaster recovery infrastructure.

0 commit comments

Comments
 (0)