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.
REMARQUE : 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.
REMARQUE : 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.
REMARQUE : 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.
Réplication inverse
La réplication inverse n'est pas prise en charge sur les systèmes DR Series. Ceci s'explique par le fait que les
conteneurs de réplique sont toujours accessibles en lecture seule (R-O, (read-only) sur ces systèmes, et les opérations
d'écriture ne sont donc pas prises en charge.
Dans des cas très spécifiques, des conteneurs de réplique peuvent prendre en charge un type d'écriture dont la seule
fonction est de restaurer des données depuis une cible archivée. Par exemple, les données peuvent être répliquées vers
le site distant où une application DMA (Data Management Application) ou un logiciel de sauvegarde sont connectés
pour permettre à ces données d'être restaurées directement.
Ce cas particulier s'applique uniquement aux configurations dans lesquelles les données sont sauvegardées depuis un
emplacement distant dans un conteneur local, puis répliquées sur un réseau WAN dans un conteneur de réplique
sauvegardé sur bande. Les données doivent être restaurées depuis la sauvegarde sur bande dans l'emplacement
d'origine, d'abord dans un conteneur de réplique du système DR Series, puis dans l'emplacement d'origine source des
données à l'autre extrémité de la liaison WAN.
20