Converse agora com nosso suporte
Chat com o suporte

DR Series DR4300 - DR Series System Administrator's 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

Configuring and using Rapid Data Access with NetVault Backup and with vRanger

Configuring and using Rapid Data Access with NetVault Backup and with vRanger

Overview
Guidelines for using RDA with NetVault Backup and with vRanger
Best Practices: RDA with NetVault Backup and vRanger and the DR Series System
Setting client-side optimization
Adding RDS Devices in NetVault Backup
Removing RDS Devices From NetVault Backup
Backing Up Data on the RDS Container Using NetVault Backup
Replicating Data to a RDS Container using NetVault Backup
Restoring Data From a DR Series System using NetVault Backup
Supported DR Series system CLI commands for RDS
 
 

Overview

Overview

Rapid Data Access (RDA) with NetVault Backup and with vRanger provides the logical disk interface that can be used with network storage devices. The DR Series system requires a DR Rapid plug-in to integrate its data storage operations with NetVault Backup and vRanger. The plug-in is installed by default on the NetVault Backup and vRanger servers and the DR Series system when the latest software updates are installed. Using the DR Rapid plug-in, the DMAs can take full advantage of key DR Series system features like replication and data deduplication.

When DR Rapid is used with the DR Series system, it offers the following benefits:

•
RDA with NetVault Backup and RDA with vRanger protocols provide faster and improved data transfers:
◦
Focus is on backups with minimal overhead
◦
Accommodates larger data transfer sizes
◦
Provides throughput that is better than CIFS or NFS
•
DR Rapid and data management application (DMA) integration:
◦
DMA-to-media server software communication
◦
DR Series system storage capabilities can be used without extensive changes to DMAs
◦
Backup and replication operations are simplified by using built-in DMA policies
•
DR Series system and DR Rapid ports and write operations:
◦
Control channel uses TCP port 10011
◦
Data channel uses TCP port 11000
◦
Optimized write operations enable client-side deduplication
•
Replication operations between DR Series systems:
◦
No configuration is required on the source or target DR Series system
◦
Replication is file-based, not container-based
◦
Replication is triggered by DMA optimized duplication operation
◦
DR Series system transfers the data file (not the media server)
◦
After duplication completes, DR Series system notifies DMA to update its catalog (acknowledging the second backup). This makes the DMA aware of the replication location. Restores from either the source or replication target can be used directly from the DMA.
◦
Supports different retention policies between source and replica
◦
Replication is set up in the DMA itself, not the DR Series system
Parent topic 

Guidelines for using RDA with NetVault Backup and with vRanger

Guidelines for using RDA with NetVault Backup and with vRanger

For best results, observe the following guidelines for optimal performance with your supported RDA with NetVault Backup and RDA with vRanger operations with the DR Series system:

•
Backup, restore, and optimized duplication operations are performed using the RDA with NetVault Backup or RDA with vRanger plug-in.
 
NOTE: The plug-in is installed on client systems to support client-side deduplication.
•
Deduplication. The DR Series system supports two deduplication modes:
◦
Passthrough: When this mode is selected, deduplication processing occurs on the DR Series system. Passthrough writes occur when data is sent from a media server to the DR Series system without applying any optimization to the data.
 
NOTE: Passthrough mode requires at least 200MB of free RAM on the backup client.
◦
Dedupe: When this mode is selected, dedupe writes occur when data is sent from a media server to the DR Series system after optimization is applied to the data; deduplication processing would occur on a NetVault Backup client, for example.
 
NOTE: Dedupe mode requires at least 4GB of free RAM on the DR Series system.
Parent topic 

Best Practices: RDA with NetVault Backup and vRanger and the DR Series System

Best Practices: RDA with NetVault Backup and vRanger and the DR Series System

This topic introduces some recommended best practices for using DR Rapid operations with the DR Series system.

RDS and non-RDS type containers can exist on the same DR Series system
The DR Series system supports having both RDS and non-RDS containers on the same appliance. However, this can cause incorrect capacity reporting as both container types share the same underlying storage.
RDS replication and non-RDS replication on the same DR Series system
Non-RDS replication must be configured, and it is replicated on a per-container basis. However, this type of replication will not replicate RDS containers. RDS replication is file-based and is triggered by the DMA.
Do not change the container connection type from NFS/CIFS to RDS
A non-RDS container must be deleted before this container can then be created as an RDS container using the same name.
Parent topic 
Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação