サポートと今すぐチャット
サポートとのチャット

DR Series Software 4.0.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 (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 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

Replication seeding

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.

 
NOTE: The following scenarios are not supported for seeding:
•
Import AND export from one share/device cannot occur at the same time.
•
Import from one share/device cannot be completed from multiple locations at the same time.
•
Export to a mount point can be completed only from one seed job. Multiple seed export jobs cannot send data to a single mount point.

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 Dell DR Series System Command Line Reference Guide for more information about replication seeding support.

Parent topic 

Reverse replication

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.

Alternate ways to retrieve data

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.

 
NOTE: If you choose to use this alternate workaround method, you must set up a new data storage unit in your DMA, and import the images before a restore to the original location can occur.

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

1.
Make sure that the replication operation has completed (between source and target).
2.
Delete the current replication relationship, and re-create a replication relationship (reversing the source and target roles).
3.
Restore data to the original source container (now the target).
4.
Make sure that the replication operation has completed.
5.
Delete the replication relationship and re-create a replication relationship (restoring original source and target destinations).

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:

•
If step 1 is not followed correctly, any changes not fully replicated are lost.
•
During steps 2 and 3, any data that is written to the original DR Series system source container may be lost.
•
During step 4, if the data is not fully replicated back before the switch is made, it may be lost.
Alternatively, you could still support this type of effort by completing the following:
1.
Create a new container on the target DR Series system.
2.
Set up replication from this container back to the source DR Series system container.
3.
Set up a new disk storage unit in the DMA and make sure that the DMA is aware of any new images.
4.
Import the old images back into the DMA from the target DR Series system (the original source location).
5.
Use a new disk storage unit in the DMA, and then restore the data back to the original client.
Parent topic 

Reverse replication: alternate method

Reverse replication: alternate method

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

1.
Create a new container on the target DR Series system.
2.
Set up replication from this container back to the source DR Series system container.
3.
Set up a new disk storage unit in your Data Management Application (DMA) and make sure that the DMA is aware of any new images.
4.
Import the old images back into the DMA from the target DR Series system (the original source location).
5.
Use a new disk storage unit in the DMA, and then restore the data back to the original client.
Parent topic 

Secure erase

Secure erase

Secure Erase is a process for securely deleting data that follows standards developed by the Defense Security Service (DSS). These standards were developed to solve the problem of secure and permanent removal of data, and this capability is now used by many commercial enterprises. These standards require multiple passes to erase data. In the process of erasing, the system overwrites data with zeros, a random pattern of data, or ones (1s) to make the original contents unreadable.

In the DR Series system, two modes of secure erase have been adopted: 3-pass and 7-pass standards.

•
3 passes (US DoD 5220.22-M (C))
◦
Pass 1: Writing zeros.
◦
Pass 2: Writing pseudo random pattern.
◦
Pass 3: Writing ones.
•
7 passes (US DoD 5220.22-M (ECE))
◦
Pass 1-3: Writing pattern according to the 3-pass mode.
◦
Pass 4: Writing a pseudo random pattern.
◦
Pass 5-7: Writing pattern according to the 3-pass mode.

The Secure Erase process can be completed at the system level by using the DR Series system CLI. This feature securely erases all data with a 3-pass or 7-pass mode and runs during the system initialization. This method erases all of the stored data while keeping the system in tact. See the DR Series System Command Line Reference Guide for more information.

 
NOTE: This capability is not supported on the DR2000v.
Parent topic 
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択