Tchater maintenant avec le support
Tchattez avec un ingénieur du support

DR Series Software 4.0.3.1 - 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

Restoring data from a DR Series system with Backup Exec

This topic describes how to use Backup Exec to restore data from a DR Series system.

To restore data from a DR Series system using Backup Exec, complete the following steps:

1.
Launch the Backup Exec Administrator console, and select the Job Setup tab.
2.
In the left navigation pane, select Restore Tasks, and click New job.
The Restore Job Properties page is displayed.
3.
Click the View by Resource tab in the Selections pane, and select the dataset to be restored.
4.
Click Run Now to start the restore job.
5.
Click the Job Monitor tab to view the progress of the restore job operation you created.

Understanding the OST CLI commands

The --mode command in the DR Series system command line interface (CLI) command supports three values, which represent optimized writes done via:

deduplication (--mode dedupe) — The client will process hashing on the data, so that deduplication processing occurs on the server side (client-side deduplication).
passthrough (--mode passthrough) — The client will pass all data to the DR Series system for deduplication processing (appliance-side deduplication).
auto (--mode auto)

— The DR Series system will set the deduplication to Dedupe or Passthrough, based on the client’s number of cores and whether it is 32– or 64–bit.

These OST commands are used in the following format: ost --update_client --name --mode.

NOTE: If a RDA with OST client has four or more CPU cores, it is considered to be “dedupe-capable.” However, the client operating mode depends upon how it is configured in the DR Series system (Dedupe is the default RDA with OST client mode). If the administrator did not configure a client to operate in a specific mode and it is dedupe-capable, it will run in the Dedupe mode. If a client is not dedupe-capable (meaning the client has less than four CPU cores), and the administrator sets it to run in the Dedupe mode, it will only run in the Passthrough mode. If a client is set to run in Auto mode, the client will run in the mode setting determined by the media server. The following table shows the relationship between the configured client mode types and the supported client mode based on client architecture type and corresponding number of CPU cores.

Table 1. Supported RDA with OST Client Modes and Settings

Client Mode Settings

32–Bit Client (4 or more CPU cores)

64–Bit Client (4 or more CPU cores)

32–Bit Client (Less than 4 CPU cores)

64–Bit Client (Less than 4 CPU cores)

Auto

Passthrough

Dedupe

Passthrough

Passthrough

Dedupe

Not Supported

Supported

Not Supported

Not Supported

Passthrough

Supported

Supported

Supported

Supported

Supported DR Series System CLI Commands for RDA with OST

NOTE: The --files in the ost --show --file_history command represents replicated files that were processed via the DMA optimized duplication operation. This command displays only up to the last 10 such files. The --name in the ost --show --name command represents the OST container name.
NOTE: For more information about OST-related DR Series system CLI commands, see the DR Series System Command Line Reference Guide.

Understanding RDA with OST Plug-In Diagnostic Logs

You can collect diagnostic logs for supported DMAs with the RDA with OST plug-in.

NOTE: The directory location, C:\ProgramData, is considered to be a hidden directory on Windows-based systems. However, you can copy and paste C:\ProgramData\Quest\DR\log\ into your Internet Explorer Address bar or you can enter this into the Windows command prompt window (Start→ All Programs→ Accessories→ Command Prompt).

For more information about RDA with OST plug-ins and logs, see the topics that follow.

Rotating RDA with OST Plug-In Logs for Windows

By default, the Windows log rotation size is set at 10 megabytes (MB). Once a log file has been reached this size, the RDA with OST plug-in automatically renames the existing log file, libstspioca.log to libstspioca.log.old, and creates a new log.

Modifying Log Rotation Size

Documents connexes