Chat now with support
Chat with Support

DR Series Software 4.0.3 - Administration Guide

Introducing the DR Series system documentation Introducing the DR Series system Setting up the DR Series system Configuring the DR Series system settings Managing containers Managing replications Monitoring the DR Series system Using GlobalView Configuring and using Rapid NFS and Rapid CIFS Configuring and using Rapid Data Access with NetVault Backup and with vRanger Configuring and using RDA with OST
Understanding RDA with OST Guidelines Terminology Supported RDA with OST software and components Best Practices: RDA with OST and the DR Series System Setting client-side optimization Configuring an LSU Installing the RDA with OST plug-in Configuring DR Series system information using NetBackup Backing up data from a DR Series system with NetBackup Using Backup Exec with a DR Series system (Windows) Understanding the OST CLI commands Understanding RDA with OST Plug-In Diagnostic Logs Collecting diagnostics by using a Linux utility Guidelines for gathering media server information
Configuring and using VTL Configuring and Using Encryption at Rest Support, maintenance, and troubleshooting Supported Ports in a DR Series system About us

Replication seeding

The DR Series system supports replication seeding, which provides the ability to create a local seed and place it in a remote system. The seed backup is a process on the source DR Series system, which collects all of the unique data chunks from the containers and stores them on the target device. This is helpful if you have a new replication target DR to set up, the amount of data to be replicated is very large, and the network bandwidth is low. You can seed the target replica with the source data saved on a third party device, for example, a CIFS—mounted share, attach it to the target DR and then get the data into the target DR. Once the seeding is complete, replication is enabled between source and target and replication re-synchronization is done to complete any pending data transfers. Thereby, continuous replication can be done, which reduces network traffic significantly, and data can be replicated and synced with the target in a short amount of time.

You can initiate seeding using the DR Series system command line interface (CLI), and the data to be seeded is gathered in an organized manner and stored in the target devices. Refer to the DR Series System Command Line Reference Guide for more information about replication seeding support.

Reverse replication

The concept of reverse replication is not a supported operation on the DR Series system. 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 could be possible for replica containers to support a type of write operation whose sole function is to restore data from an archival target. For example, data could be replicated back to the remote site where a data management application (DMA), or backup software, is connected to allow this data to be restored directly.

This specific type of case applies only to configurations where data is backed up from a remote location to a local container, and then replicated over a WAN to a replica container that is backed up to tape. The data needs to be restored from the tape backup to the original location; first back to a DR Series system replica container, and then back to the original source location of the data on the other side of the WAN link.

To leverage this type of deduplication across the WAN, complete the following:

Under this scenario, a fraction of the data to be recovered is sent across the WAN link. This could speed up a remote restore significantly. However, there are some downsides to this type of scenario:

Reverse replication: alternate method

For an alternate method of reverse replication, complete the following steps:

Rapid Air Gap

Rapid Air Gap is a replication feature in which a secondary target DR Series system in a three-way replication scenario exists in an isolated private network. The Secondary target is available for replication for only a specific period of time (when the Air gap closes). Only during this period of time will replication between the Primary and Secondary target DR systems occur. Only a subset of services are available on the secondary target so that it is secured from the external environment. The primary target DR Series system acts as the target as well as the source for the Secondary target. The primary target will be in two different networks to cater both Primary DR and Secondary target networks. The Secondary target also has a (user-editable) retention period that retains the data on it even after the respective data is deleted on the Secondary source. Commands for using this feature are available in the DR Series system command line interface (CLI). For information about setting up and using this feature, see the DR Rapid Air Gap Setup Guide and the DR Series System Command Line Reference Guide.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating