Administrator Guide

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.
: 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.
: 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.
: 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.
反向复制
DR Series 系统上不支持反向复制的概念。这是因为 DR Series 系统上的副本容器始终处于 R-O只读
这就使得写入操作成为不受支持的操作。
在极其特殊的条件下副本容器有可能支持某种类型的写入操作此写入操作的唯一功能就是从归档目标还原
数据。例如可以将数据复制回远程站点此站点上连接了数据管理应用程序 (DMA)也称为备份软件),
而可直接还原此数据。
这种特殊情形仅适用于以下配置从远程位置向本地容器备份数据然后通过 WAN 将数据复制到备份至磁带
的副本容器。数据需要从磁带备份还原至原始位置首先还原回 DR Series 系统副本容器然后还原回 WAN
链路另一端的原始数据源位置。
: 如果您选择使用此备选解决方法则必须在 DMA 中设置新的数据存储单元并导入映像然后才能还
原到原始位置。
要跨 WAN 利用此类重复数据消除请完成以下操作
1. 确保复制操作源与目标之间已经完成。
2. 删除当前的复制关系然后重新创建复制关系颠倒源角色与目标角色
3. 将数据还原到原始的源容器现在的目标
4.
确保复制操作已经完成。
5. 删除复制关系然后重新创建复制关系还原原始源与目标目的地
18