Chat now with support
Chat with Support

Quest has tools and processes in place to identify, protect, detect, and remediate vulnerabilities and incidents when they occur, including external security partners. As part of our standard security operations, Quest does not use CrowdStrike in any of our operations. We are reviewing our third parties, and so far, there is minimal affect. It is Quest's policy not to provide further technical details unless they directly impact customer data.

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

Configuring cleaner schedules

Performing scheduled disk space reclamation operations are recommended as a method for recovering disk space from the system. The recommended method is to schedule a time when you can run the Cleaner on your DR Series system with no other planned processes running.

NOTE: Even if no Cleaner schedule is set, but the system detects that there is disk space that can be reclaimed, the Cleaner process runs. However, the Cleaner will not start until the following conditions are met: it detects that there are no active data ingests, that two minutes of system idle time have elapsed since the last data file ingest was completed, and that the Replication process is not running (the Cleaner process runs as a lower system priority operation than the Replication process).

NOTE: Running the Cleaner while ingesting data reduces system performance. Ensure that you schedule the Cleaner to run when backup or replication is not in progress. For more information about best practices for using the system cleaner, refer to the DR Series System Cleaner Best Practices white paper for your specific DR Series system at support.quest.com/DR-Series.

To schedule cleaner operations on your system, complete the following steps.

  1. On the left navigation menu, click System Configuration > Schedules.

    The Schedules page is displayed, showing a weekly/daily calendar representation of currently scheduled operations.

  2. To add a cleaner schedule, on the Action menu in the upper right corner of the page, select Add Cleaner Event.
    1. In the Cleaner pane, select a day from the Set Event At Day drop-down list.
    2. In the From and To drop-down lists, select the time (hour) of the day for the cleaner to run.
    3. Click Save.

      NOTE: Even if no Cleaner schedule is set, but the system detects that there is disk space that can be reclaimed, the Cleaner process runs. However, the Cleaner will not start until the following conditions are met: it detects that there are no active data ingests, that two minutes of system idle time have elapsed since the last data file ingest was completed, and that the Replication process is not running (the Cleaner process runs as a lower system priority operation than the Replication process).

      NOTE: You can also use the DR Series system command line interface (CLI) to create, view, and delete the cleaner schedule. The available commands are:

       			 schedule --add --day <Day of the Week> --start_time <HH:MM> --stop_time <HH:MM> --cleaner   
      			 schedule --show --cleaner
      			 schedule --delete --day <Day of the Week> --cleaner

      For full details on running the cleaner schedule commands, help is available by entering:

      			 schedule --help
  3. To run the cleaner now, on the Action menu in the right corner of the page, select Run Cleaner Now.

Viewing cleaner status

The current Cleaner Status is shown at the top of the Schedules page as one of the three following states:
  • Pending—displays any scheduled window for the Cleaner operation.
  • Running—displays when the Cleaner operation is running.
  • Idle—displayed only if there is no Cleaner operation running.

On the Dashboard page, you can also view a graph of cleaner statistics.

  • In the Action menu in the upper right corner, click Detailed Graphs, and then click the Cleaner tab.

Viewing cleaner statistics

To view additional detailed cleaner statistics, you can use the DR Series system CLI stats --cleaner command to show the following categories of statistics:

  • Last Run Files Processed (number of files processed by Cleaner)
  • Last Run Bytes Processed (number of bytes processed by Cleaner)
  • Last Run Bytes Reclaimed (number of bytes reclaimed by the Cleaner)
  • Last Run Start Time (indicates date and time last Cleaner process started)
  • Last Run End Time (indicates date and time last Cleaner process ended)
  • Last Run Time To Completion(s) (indicates the number of times that Cleaner process has successfully completed)
  • Current Run Start Time (indicates date and time current Cleaner process started)
  • Current Run Files Processed (number of files processed by current Cleaner process)
  • Current Run Bytes Processed (number of bytes processed by current Cleaner process)
  • Current Run Bytes Reclaimed (number of bytes reclaimed by the current Cleaner processed)
  • Current Run Phase 1 Start Time (indicates date and time for start of current Cleaner process phase 1)
  • Current Run Phase 1 Records Processed (lists the number of data records processed in current Cleaner process phase 1)
  • Current Run Phase 1 End Time (indicates date and time for end of current Cleaner process phase 1)
  • Current Run Phase 2 Start Time (indicates date and time for start of current Cleaner process phase 2)
  • Current Run Phase 2 Records Processed (lists the number of data records processed in current Cleaner process phase 2)
  • Current Run Phase 2 End Time (indicates date and time for end of current Cleaner process phase 2)
  • Current Run Phase 3 Start Time (indicates date and time for start of current Cleaner process phase 3)
  • Current Run Phase 3 Records Processed (lists the number of data records processed in current Cleaner process phase 3)
  • Current Run Phase 3 End Time (indicates date and time for end of current Cleaner process phase 3)
  • Current Run Phase 4 Start Time (indicates date and time for start of current Cleaner process phase 4)
  • Current Run Phase 4 Records Processed (lists the number of data records processed in current Cleaner process phase 4)
  • Current Run Phase 4 End Time (indicates date and time for end of current Cleaner process phase 4)

For more information about DR Series system CLI commands, see the DR Series System Command Line Reference Guide.

Configuring replication schedules

You can configure replication schedules on a weekly basis for individual replication-enabled source containers.

NOTE: If there is no Replication schedule set, but there is pending data that can be replicated, replication will run when it detects three (3) minutes of idle time for any newly written files in the replicated container.

NOTE: It is recommended that you do not schedule the running of any Replication operations during the same time period when Cleaner or data ingest operations will be running. If you do not follow this recommendation, the time required to complete the system operations or system performance might be affected.

To configure replication schedules, complete the following steps.

  1. On the left navigation menu, click System Configuration > Schedules.

    The Schedules page is displayed, showing a weekly/daily calendar representation of currently scheduled operations.

  2. To view the Replication Schedule, in the Replication Schedule drop-down list, you can select one of the following types of replication schedules to view:

    • None
    • All Containers
    • Source:
      • All
      • <A specific backup container>
    • Target:
      • All
      • <A specific backup container>

  3. To add a replication schedule, on the Action menu in the upper right corner of the page, click Add Replication Event.
    1. In the Replication pane, select the replication container for which you want to schedule replication in the Set Event to Container drop-down list.
    2. In the Day drop-down list, select the day for the schedule to run.
    3. In the From and To drop-down lists, select the time (hour) of the day for the replication to run.
    4. Click Save.

You can view replication details and status on the Replications page in the DR Series system GUI by selecting a replication and clicking to expand and view details. The current replication status is also shown on the GlobalView page by expanding the detailed view of a selected DR Series system.

Configuring an SSL certificate for your DR Series system

For additional security, you can replace the self-signed, factory-installed certificate with another SSL certificate, for example, with one that is signed by a third-party CA. Once you have obtained your signed certificate, you can install it by using the DR Series system GUI. Only one certificate can be installed on a DR Series system at any given point in time.

  • To view the SSL Certificate page, on the left navigation menu, click System Configuration > SSL Certificate.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating