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

DR Series Software 3.2.6 - Administrator Guide

Introduction to the DR Series System Documentation Understanding the DR Series System Setting Up the DR Series System Hardware Configuring the DR Series System Settings Managing DR Series Storage Operations Monitoring the DR Series System Using Global View Using the DR Series System Support Options Configuring and Using Rapid NFS and Rapid CIFS Configuring and Using Rapid Data Access with Dell NetVault Backup and with Dell 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 Troubleshooting and Maintenance Supported Ports in a DR Series System Getting Help
•
Replication process
•
Cleaner process (space reclamation)

The main goal in planning and scheduling operations is running the Cleaner and Replication operations at times when they do not overlap or interfere with other important system operations. You want to make sure that by properly scheduling and planning, your system can perform each of these key operations independent of the other.

The best practice is to run these two operations during non-standard business hours, so that they do not conflict with any of your other backup or ingest operations. In short, efficient scheduling maximizes the best use of your system resources.

Dell recommends scheduling resource-intensive operations during specific time periods when no other system operations are being performed. This approach is called windowing, which requires scheduling a specific block of time (or “window”), each with a set starting and stopping point so that you can perform data ingests, replication, or space reclamation operations without interfering with the running of any other operation.

Parent topic 

Creating a Cleaner Schedule

Creating a Cleaner Schedule

Performing scheduled disk space reclamation operations are recommended as a method for recovering disk space from system containers in which files were deleted as a result of deduplication. The best method is to schedule a time when you can run the Cleaner on your DR Series system with no other planned processes running. Alternately, another method lets the Cleaner process on the DR Series system run whenever it determines that there are no active data ingests.

 
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.
 
NOTE: The Cleaner Schedule page displays the current DR Series system time zone and current timestamp (using this format: US/Pacific, Fri Nov 2 15:15:10 2012).

To schedule Cleaner operations on your system, complete the following:

1.
Select Schedules > Cleaner Schedule.
The Cleaner Schedule page is displayed.
2.
Click Schedule to create a new schedule (or click Edit Schedule to modify an existing schedule).
The Set Cleaner Schedule page is displayed.
3.
Select (or modify) the Start Time and Stop Time setpoint values using the Hour and Minutes pull-down lists to create a Cleaner schedule.
 
NOTE: You must set a corresponding Stop Time for every Start Time set in each Cleaner schedule you create. The DR Series system will not support any Cleaner schedule that does not contain a Start Time/Stop Time pair of setpoints (daily or weekly).
4.
Click Set Schedule for the system to accept your Cleaner schedule (or click Cancel to display the Cleaner Schedule page).
 
NOTE: To reset all of the values in the current Cleaner schedule, click Reset in the Set Cleaner Schedule dialog. To selectively modify values in the current schedule, make your changes to the corresponding hours and minutes pull-down lists to represent the Start Time and Stop Time you wish to set, and click Set Schedule.

The current Cleaner Status is represented in the Dashboard page in the System Information pane as one of the three following states:

•
Pending—displayed when there is any scheduled window set and the current time is outside the scheduled window for the Cleaner operation.
•
Running—displayed when the Cleaner operation is running during a scheduled window.
•
Idle—displayed only if there is no Cleaner operation running during a scheduled window.

Dell recommends that you do not schedule the running of any Cleaner operations during the same time period when replication or ingest operations will be running. Failure to follow this practice will affect the time required to complete the system operations and/or impact your DR Series system performance.

 
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
NOTE: For full details on running the cleaner schedule commands, help is available by entering:
schedule --help
 
NOTE: For more information about using the system cleaner, refer to the DR Series System Cleaner Best Practices white paper for your specific DR Series system at: dell.com/support/manuals.
 
 
Parent topic 

Displaying Cleaner Statistics

Displaying Cleaner Statistics

To display additional Cleaner statistics, you can use the DR Series system CLI stats --cleaner command to show the following categories of Cleaner 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 Dell DR Series System Command Line Reference Guide.

Parent topic 

Supported Ports in a DR Series System

Supported Ports in a DR Series System

The following table lists the application and service ports found on a normally operating DR Series system. There may be other ports that are not listed here, that an administrator may need to open and enable to support specific operations across the network. Be aware that the ports listed in the following table may not reflect your specific network environment, or any planned deployment. While some of these DR Series system ports may not need to be accessible through the firewall, this information is made available when deploying the DR Series system in your own network because it indicates supported ports that may need to be exposed.

Table 6. Supported DR Series System Ports

Port Type

Number

Port Usage or Description

DR Series System Application Ports

TCP

20

File Transfer Protocol (FTP)—for transferring files.

TCP

23

Telnet—remote terminal access protocol for unencrypted text communications.

TCP

80

Hypertext Transfer Protocol (HTTP)—unencrypted protocol communications.

TCP

443

HTTPS—combination of the HTTP with Secure Socket Layer (SSL)/Transport Layer Security (TLS).

TCP

1311

Hardware Health Monitor (Note: this is not used on the DR2000v)

TCP

9901

Watcher

TCP

9904

Configuration Server (needed for replication operations)

TCP

9911

Filesystem Server (needed for replication operations)

TCP

9915

MetaData Replication (needed for replication operations)

TCP

9916

Data Filesystem Server (needed for replication operations)

TCP

9918

Diagnostics Collector

TCP

9920

Data path used for OST or RDS replications

TCP

10011

Control channel (needed for OST or RDS operations)

TCP

11000

Data channel (needed for OST or RDS operations)

DR Series System Service Ports

TCP

22

Secure Shell (SSH)—used for secure logins, file transfers like SCP (Secure Copy) and SFTP (Secure File Transfer Protocol)

TCP

25

Simple Mail Transfer Protocol (SMTP)—used for routing and sending email

TCP

139

SMB daemon—used for SMB protocol-related processes

TCP

199

SNMP daemon—used by Simple Network Management Protocol (SNMP) requests

TCP

801

NFS status daemon

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation