Dell PowerVault DR6000 - Manual (Page 18)

DR Series system software. The DR Series systems provide a key component that performs backup, recovery, and
data protection operations.
• Deduplication — This technology eliminates redundant copies of data and in the process it decreases disk capacity
requirements and reduces the bandwidth needed for data transfer. Deduplication can be a major asset for
companies that are dealing with increasing data volumes and require a means for optimizing their data protection.
• Compression — This technology reduces the size of data that is stored, protected, and transmitted. Compression
helps companies improve their backup and recovery times while helping reduce infrastructure and network
resource constraints.
In general, DR Series systems are disk-based data protection appliances that offer advanced deduplication and
compression capabilities to reduce the time and cost associated with backing up and restoring data. Based on
deduplication and compression technology, the DR Series systems eliminate the need to maintain multiple copies of the
same data. This lets customers keep more data online longer and reduce the need for tape backup dependency.
Using its deduplication and compression technology, DR Series systems can help achieve an expected data reduction
ratio of 15:1. Achieving this reduction in data means that you need fewer incremental storage operations to run and it
provides you with a smaller backup footprint. By removing redundant data, DR Series systems deliver fast reliable
backup and restore functionality, reduce media usage and power and cooling requirements, and improve your overall
data protection and retention costs.
You can extend the benefits of data deduplication across the enterprise as well–using the DR Series system
deduplication replication function–to provide a complete backup solution for multi-site environments. With 64:1
deduplicated replication (32:1 for DR4X00, 8:1 for DR2000v), up to 64 nodes can be replicated simultaneously to separate,
individual containers on one node. The DR Series systems use compression with replication to shrink the data that is
needed to be moved across the wire to a container.
Replication can be scheduled based on your settings to occur during non-peak periods. The replication schedule you
create can be set and prioritized to ingest data over replication data to ensure the most optimal back up windows based
on your needs.
Unlike NFS and CIFS containers, OST and RDS container replication is handled by the Data Management Applications
(DMAs) media servers.
The DR Series system supports the 64:1 replication of data (32:1 if on the DR4X00 and 8:1 for the DR2000v), whereby up to
64 source DR Series systems can write data to different individual containers on a single, target DR Series system. This
supports, for example, 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.
NOTE: 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.
If the source and target systems reside in different Active Directory (AD) domains, then the data that resides on the
target DR Series system may not be accessible. When AD is used for authentication for DR Series systems, the AD
information is saved with the file. This can serve to restrict user access to the data based on the type of AD permissions
that are in place.
NOTE: 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.
Reverse Replication: The concept of reverse replication is not supported on DR Series systems. This is because replica
containers are always in a R-O (read-only) mode on the DR Series system, thus making write operations a non-
supported operation. Under very specific conditions, it might be possible for replica containers to support a type of
write.
For a complete list of supported management application, refer to the
DR Series System Interoperability Guide .
18