Skip to content

Commit b0385d0

Browse files
committed
new dr
1 parent 8a82474 commit b0385d0

File tree

2 files changed

+16
-0
lines changed

2 files changed

+16
-0
lines changed

_topic_maps/_topic_map.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4079,6 +4079,8 @@ Topics:
40794079
File: virt-backing-up-vms
40804080
- Name: Restoring virtual machines
40814081
File: virt-restoring-vms
4082+
- Name: About disaster recovery
4083+
File: virt-disaster-recovery
40824084
# - Name: Collecting OKD Virtualization data for community report
40834085
# File: virt-collecting-virt-data
40844086
# Distros: openshift-origin
Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
:_mod-docs-content-type: ASSEMBLY
2+
[id="virt-disaster-recovery"]
3+
= About disaster recovery
4+
include::_attributes/common-attributes.adoc[]
5+
:context: virt-about-dr
6+
7+
toc::[]
8+
9+
The disaster recovery documentation provides information for administrators on
10+
how to recover from certain disaster scenarios that might occur with an
11+
{product-title} cluster. As an administrator, you must plan your {VirtProductName} deployment in advance in order to take advantage of disaster recovery.
12+
13+
link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.14/html-single/configuring_openshift_data_foundation_disaster_recovery_for_openshift_workloads/index#metro-dr-solution[Metropolitan Disaster Recovery (Metro-DR)]::
14+
Metro-DR provides two-way synchronous data replication between OpenShift Virtualization clusters installed at two separate sites. Use Metro-DR during a site disaster to fail applications to the additional site. This synchronous solution is only available to metropolitan distance data centers with a 10 millisecond latency or less.

0 commit comments

Comments
 (0)