Chat now with support
Chat with Support

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

About the DR Series system maintenance mode

About the DR Series system maintenance mode

In general, the DR Series system enters the Maintenance mode whenever the file system has encountered an issue that prevents it from operating normally.

NOTE: You can use the Reason code information available in the Maintenance mode to contact Technical Support. All maintenance must be conducted using the DR Series systems Command Line Interface.

When in its Maintenance mode, the filesystem is in a read-only state, and the system runs the following maintenance-based operations:

NOTE: Whenever the DR Series systems enters or exits from the Maintenance mode state, all communication via protocols is lost.

If the filesystem check finds issues, you can choose to make repairs (using Confirm Repair Filesystem) or ignore the detected issue (using Skip Repair Filesystem), at which point the system switches back to Operational mode.

The Maintenance mode process displays a number of stages, indicated on the Maintenance Mode progress bar, which include:

NOTE: If the Filesystem Check detects any repairable files, it generates a Repair Report that identifies these reported files. The Maintenance Mode progress bar halts at the Completed Generating Repair stage, and remains in Maintenance mode until you click Confirm Repair Filesystem. The DR Series system does not advance to the Switching to Operation Mode stage until the filesystem repair is completed.

The Maintenance Mode page provides the following information:

Provides a search capability that allows you to click prev or next to display the previous or next page in the Repair Report, or lets you display a specific page number of the Repair Report by entering this number in the Goto page and click go.

After the DR Series system enters Maintenance mode, there can only be two possible outcome states:

Operational mode (Normal State): where the filesystem check was successful, and no system files need to be repaired (Filesystem Check: successful).
Maintenance mode has halted: where the filesystem check detected one or more repairable files (Filesystem Check: unsuccessful).

Filesystem Check — Successful: when the Maintenance mode successfully completes all of its stages, the DR Series system displays its status as having entered Operational mode (Normal State). Only after the Maintenance mode has successfully completed its internal check can it return to an Operational mode.

To return to the Operational mode, click Go to Dashboard on the Maintenance Mode page options bar. Go to Dashboard is only active when all of the internal system checks have completed and the progress bar indicates that all stages have been completed.

NOTE: When in Maintenance mode, image expiration fails because the DR Series system is in a read-only state. If this occurs, the DMA assumes that the backup images have expired. However, the DR Series system administrator may be unaware that the backup data images still reside on the DR Series system.

Filesystem Check — Unsuccessful: when the Maintenance mode halts at the Completed Generating Report stage, this indicates that the filesystem check detected some repairable files, and listed them in the Repair Report pane on the Maintenance Mode page.

To return to the Operational mode, click Confirm Repair Filesystem on the Maintenance Mode page options bar to repair the files listed in the Repair Report. Confirm Repair Filesystem is the only active option you can select when the progress bar indicates that some filesystem files are in need of repair.

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 4. Supported DR Series System Ports

Port Type


Port Usage or Description

DR Series System Application Ports



File Transfer Protocol (FTP)—for transferring files.



Telnet—remote terminal access protocol for unencrypted text communications.



Hypertext Transfer Protocol (HTTP)—unencrypted protocol communications.



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



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






Configuration Server (needed for replication operations)



Filesystem Server (needed for replication operations)



MetaData Replication (needed for replication operations)



Data Filesystem Server (needed for replication operations)



Diagnostics Collector



Data path used for OST or RDS replications



Control channel (needed for OST or RDS operations)



Data channel (needed for OST or RDS operations)

DR Series System Service Ports



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



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



SMB daemon—used for SMB protocol-related processes



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



NFS status daemon

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating