Administrator Guide

Targets with replication data are read-only, and are updated with new or unique data during scheduled or manual
replications. The DR Series system can be considered to act as a form of a storage replication process in which the
backup and deduplication data is replicated in real-time or via a scheduled window in a network environment. In a
replication relationship between two DR Series systems, this means that a relationship exists between a pair of systems.
One system acts as the source and the other as a target in this replication pair (for example, acme-west and acme-east).
When this type of relationship exists between distinct containers on two distinct DR Series systems, it can be
considered bidirectional in the sense that:
• The West1 container on the acme-west source system can replicate data to a separate East1 container on the
acme-east target system.
• The East2 container on the target acme-east system can also replicate data back to the West2 container on the
source acme-west system.
This form of replication involves separate containers on two distinct DR Series systems. Target containers in replication
must always act as read-only, while sources containers can act as read-write. Unlike NFS and CIFS containers, OST and
RDS container replication is handled by the two supported Data Management Applications (DMAs) on media servers.
For more information on OST, see Understanding OST. For more information on RDS, see Configuring and Using Rapid
Data Storage.
ANMERKUNG: OST and RDS containers are categorized as Rapid Data Access (RDA) containers in DR Series
systems.
The DR Series system supports the 32:1 replication of data, whereby up to 32 source DR Series systems can write data
to different individual containers on a single, target DR Series system. This supports the use case where branch or
regional offices can each write their own data to a separate, distinct container on a main corporate DR Series system.
ANMERKUNG: Be aware that the storage capacity of the target DR Series system is directly affected by the
number of source systems writing to its containers, and by the amount being written by each of the source
systems.
However, if the source and target systems in a replication pair are in different Active Directory (AD) domains, then the
data that resides on the target system may not be accessible. When AD is used to perform authentication for DR Series
systems, the AD information is saved with the file. This can act to restrict user access to the data based on the type of
AD permissions that are in place.
ANMERKUNG: This same authentication information is replicated to the target DR Series system when you have
replication configured. To prevent domain access issues, ensure that both the target and source systems reside in
the same Active Directory domain.
Umgekehrte Replikation
Das Konzept der umgekehrten Replikation wird auf DR Series-Systemen nicht unterstützt. Replikatcontainer befinden
sich auf dem DR Series-System immer im schreibgeschützten Modus, sodass Schreibvorgänge generell nicht
unterstützt werden.
Unter sehr spezifischen Bedingungen können Replikatcontainer eine Form von Schreibvorgang unterstützen, dessen
einzige Funktion darin besteht, Daten aus einem Archivziel wiederherzustellen. Beispiel: Wenn eine
Datenverwaltungsanwendung (DMA), auch als Sicherungssoftware bezeichnet, installiert ist und die direkte
Wiederherstellung dieser Daten zulässt, können die Daten zurück zum Remote-Standort repliziert werden.
Dieser Sonderfall gilt nur für Konfigurationen, bei denen Daten von einem Remote-Speicherort in einen lokalen
Container gesichert und dann über ein WAN zu einem Replikatcontainer repliziert werden, der auf Band gesichert wird.
Die Daten aus der Bandsicherung müssen am ursprünglichen Speicherort wiederhergestellt werden; zuerst in einem
Replikatcontainer des DR Series-Systems dann zurück am ursprünglichen Quellspeicherort auf der anderen Seite der
WAN-Verbindung.
20