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

Rapid Recovery 6.10 - User Guide

Introduction to Rapid Recovery The Core Console Repositories Core settings Protecting machines
About protecting machines with Rapid Recovery Understanding the Rapid Recovery Agent software installer Deploying Agent to multiple machines simultaneously from the Core Console Using the Deploy Agent Software Wizard to deploy to one or more machines Modifying deploy settings Understanding protection schedules Protecting a machine About protecting multiple machines Enabling application support Settings and functions for protected Exchange servers Settings and functions for protected SQL servers
Managing protected machines Snapshots and recovery points Managing privacy Encryption Authentication Replication Events Reporting VM export Restoring data Bare metal restore
About bare metal restore Differences in bare metal restore for Windows and Linux machines Understanding boot CD creation for Windows machines Managing a Linux boot image Performing a bare metal restore using the Restore Machine Wizard Using the Universal Recovery Console for a BMR Performing a bare metal restore for Linux machines Verifying a bare metal restore
Managing aging data Archiving Cloud accounts Core Console references REST APIs Glossary

Troubleshooting connections to the Universal Recovery Console

The following are troubleshooting steps for connecting to the boot CD image as part of the process for Selecting a recovery point and initiating a BMR.

If an error displays indicating that the Core could not connect to the remote server, then any of several possible causes are likely.

  • Verify that the IP address and Current Password displayed in the URC are identical to the information you entered in the Recovery Console Instance dialog box.
  • To reach the server on which to restore data, the Core must be able to identify the server on the network. To determine if server identification is possible, you can open a command prompt on the Core and ping the IP address of the target BMR server. You can also open a command prompt on the target server and ping the IP address of the Rapid Recovery Core.
  • Verify that the network adapter settings are compatible between Core and target BMR server.

Repairing boot problems

The following tasks are prerequisites for this procedure.

Complete the steps in this procedure to repair startup problems. Keep in mind that if you restored to dissimilar hardware, you must have injected storage controller, RAID, AHCI, chipset and other drivers if they are not already on the boot CD. These drivers make it possible for the operating system to operate all devices on your target server successfully. For more information, see Loading drivers using the Universal Recovery Console. Complete the following procedure to repair startup problems on your target server.

  1. From the Universal Recovery Console, click the Existing Windows driver manager tab.
  2. Click Repair Boot Problems.

    The startup parameters in the target server boot record are automatically repaired.

Verifying the bare metal restore from the command line

Quest recommends performing the following steps to verify a bare metal restore completed from the command line.

This task is a step in Performing a bare metal restore for Linux machines.

Performing a file system check on the restored volume

Once you execute a bare metal restore from the command line, you should perform a file system check on the restored volume to ensure the data restored from the recovery point was not corrupted.

This task is a step in Performing a bare metal restore for Linux machines. It is part of the process for Verifying the bare metal restore from the command line.

Perform the task below to perform a file system check on the restored volume.

  1. From the command line in the Universal Recovery Console of the Linux machine you have restored, to verify whether the appropriate partitions are mounted, type the following command and then press Enter: 
        df
  2. If the restored volume is not mounted, then skip to Step 3. If the restored volume is mounted, unmount it by typing the following command and then pressing Enter: 
         umount <mount point>
  3. Run a file system check on the restored volumes by typing the following command and then press Enter: 
         fsck -f <volume>

    If the fsck returns clean, the file system is verified.

  4. Mount the appropriate volumes once again by typing the following command in format mount <volume> <folder>, and then press Enter.

    For example, if the volume path is prod/sda1 and the folder you want to mount to is mnt, then type the following and then press Enter: 

        mount /dev/sda1 /mnt
Documents connexes
Rapid Recovery - 6.10
Commands and Scripting Reference Guide
Installation and Upgrade Guide
Release Notes
System Requirements Guide
User Guide
Showing 1 to 5 of 5 rows

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation