サポートと今すぐチャット
サポートとのチャット

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

Upgrading the DR Series system software

You can obtain the latest DR Series system software binary package from the Quest website. You would then upload this file in the DR Series system GUI for the system software upgrade.

NOTE: The DR Series system only supports the copying of upgrade images and diagnostics files to and from the system using WinSCP. The DR Series system does not support the copying or deleting of any other file types using WinSCP. To use WinSCP to copy DR Series software upgrade and diagnostics log files, ensure that the File Protocol mode is set to SCP (Secure Copy) mode.

NOTE: You can use other SCP tools with the DR Series system, but you cannot use these other SCP tools to copy other types of files to or from the DR Series system.

To upgrade the DR Series system software, complete the following steps.

  1. Using your browser, go to support.quest.com/dr-series, select your specific DR model and then navigate to Software Downloads.
  2. Under Upgrade File, locate the version you want to download, and click the Download button. If you are not logged in, you may be prompted to log in with your registered Quest account.
  3. Save the latest system software upgrade file to a network location accessible by the DR Series system that is running the browser session started by the DR Series administrator.
  4. In the DR Series system GUI, in the left navigation menu, click Support > Software Upgrade.
  5. Click the button, Select DR Binary Package.
  6. Browse to the location of the of the file you downloaded from quest.com, select the file, and click Open. The system verifies that the file is the proper format.
  7. Once the file has been uploaded, on the Software Upgrade page, click Start Upgrade.

    The administrator who initiated the software upgrade sees a System Information pane that displays an alert and upgrade status, as well as the Current Version and Upgrade History versions of the DR Series system software listed.

    The first time you log on after a software upgrade, you will see an Upgrade notification dialog box, which instructs you to review and verify user roles and logon information for your DR Series system and associated DMAs.

    There are only three possible outcomes for a DR Series system software upgrade operation:

    • Upgrade has completed successfully—no reboot is required.
    • Upgrade has completed successfully—but a reboot is required (click Reboot in the Software Upgrade page).
    • Upgrade has failed.

    NOTE: If the DR Series system software upgrade operation fails, you can reboot the system and attempt another software upgrade operation using the DR Series system GUI. If this is unsuccessful, you can use the DR Series system CLI system --show command to view the current System State status. DR Series system software upgrades can also be performed using the DR Series system CLI. For details, see the DR Series System Command Line Reference Guide. If both the DR Series system GUI and CLI attempts are unsuccessful, contact Technical Support for assistance.

Restore Manager (RM)

The Restore Manager (RM) utility can be used to restore the DR Series system software. RM can be used when a non-recoverable hardware or software failure prevents the DR Series system from functioning correctly.

RM can also be used to reset the system back to its initial factory settings when moving it from a test environment to a production environment. RM supports the following two modes:

  • Recover Appliance—in Recover Appliance mode, RM reinstalls the operating system and attempts to recover the prior system configuration and the data residing in the containers.

    NOTE: To use the Recover Appliance mode, you must use an RM build that is compatible with the DR Series system software version that was running before the OS reset was attempted.

  • Factory Reset—in a Factory Reset mode, RM reinstalls the operating system and resets the system configuration back to the original factory state. It is important to note that when doing a factory reset, all of the containers and the data in the containers gets deleted.

Caution: Using the Factory Reset mode deletes all of the DR Series system data. The Factory Reset mode must only be used when the container data is no longer needed.

Downloading the Restore Manager

The Restore Manager (RM) utility runs from a USB boot key that contains the RM image, which must first be downloaded from the Quest Support site.

  1. Using your browser, go to support.quest.com/dr-series, select your specific DR model and then navigate to Software Downloads.
  2. Under Restore Manager, locate the version you want to download, and click the Download button. If you are not logged in, you may be prompted to log in with your registered Quest account.

Creating the Restore Manager USB key

To create a Restore Manager (RM) USB key, you must first download the RM image (.img) file from the Quest Support site, and then transfer it to a USB key. The USB key must be a minimum of 4 GB (Gigabytes) in size or larger. Windows USB image tools can be used to transfer the RM image when they meet the following conditions:
  • Support using the .img file format
  • Support using a direct block-to-block device copy to ensure that the USB key is bootable

To transfer the RM image to the USB key on a Linux or Unix system, perform the following:

  1. Copy the downloaded RM image file to a Linux or Unix system.
  2. Insert the USB key into an available USB port on the Linux or Unix system.

    Make note of the device name that is reported by the operating system (for example, /dev/sdc4).

  3. Do not locally mount the USB device to a file system at this time.
  4. Copy the RM image to the USB key using the dd command:
    dd if=<path to .img
file> of=<usb device> bs=4096k
    For example:
    dd if=/root/DR-RM-1.05.03.313-2.1.0851.2.img
 of=/dev/sdc4 bs=4096
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択