Chatta subito con l'assistenza
Chat con il supporto

Rapid Recovery 6.8 - 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

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

Using the command line to make a restored Linux machine bootable

Once you complete a clean file system check on the restored volume, you must create bootable partitions.

GNU Grand Unified Bootloader (GRUB) is a boot loader that allows administrators to configure which operating system or specific kernel configuration is used to start the system. After a BMR, the configuration file for GRUB must be modified so that the machine uses the appropriate universally unique identifier (UUID) for the root volume. Before this step you must mount the root and boot volumes, and check the UUIDs for each. This ensures that you can boot from the partition.

NOTE: This procedure applies to Linux machines that use GRUB1 or GRUB2. When using this procedure, ensure that the boot partition is healthy and protected.

GRUB or GRUB2 is typically installed with Linux operating systems. You can perform this procedure using the version that comes with your Linux distribution. If a version of GRUB is not installed, you will have to re-install the default version appropriate for your Linux distribution.

Caution: When you boot a restored Linux machine for the first time after a BMR, Rapid Recovery takes a base image of the restored machine. This process typically takes longer than taking an incremental snapshot. For more information about base images and incremental snapshots, see Understanding protection schedules.

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 create bootable partitions using the command line.

  1. You must mount the root volume first and then the boot volume. Mount each restored volume by using the following commands:
    1. To mount the root volume, type the following command and then press Enter:
          mount /<restored volume[root]> /mnt

      For example, if /dev/sda2 is the root volume, then type mount /dev/sda2 /mnt and then press Enter.

    2. To mount the boot volume, type the following command and then press Enter:
          mount /<restored volume[boot]> /mnt/boot

      For example, if /dev/sda1 is the boot volume, then type mount /dev/sda1 /mnt/boot and then press Enter.

      NOTE: Some system configurations may include the boot directory as part of the root volume.

  2. If the volume size is increasing — that is, if the destination volume on the new Linux machine is larger than the volume was in the recovery point — then you must delete any existing bitmap data files.
  3. Obtain the Universally Unique Identifier (UUID) of the new volumes by using the blkid command. Type the following and then press Enter:
        blkid [volume]

    NOTE: You can also use the ls -l /dev/disk/by-uuid command.

  4. If performing a BMR on a brand new disk on the destination machine, comment out the swap partition in fstab in your root volume.
  5. Modifying fstab and mtab paths should occur on the restored volume, not the Live DVD. There is no need to modify paths on the Live DVD. Prepare for the installation of Grand Unified Bootloader (GRUB) by typing the following commands. Following each command, press Enter:
         mount --bind /dev /mnt/dev
         mount --bind /proc /mnt/proc
         mount --bind /sys /mnt/sys
  6. Change root directory by typing the following command and then press Enter:
         chroot /mnt /bin/bash
  7. Obtain the old UUID of the partition or partitions from the mounted recovery points /etc/fstab file and compare it to the UUIDs for the root (for Ubuntu and CentOS), boot (for CentOS and RHEL), or data partitions by typing the following command and then press Enter:
         less /mnt/etc/fstab
  8. Obtain the old UUID of the partition or partitions from the mounted recovery points /etc/mtab file and compare it to the UUIDs for the root (for Ubuntu and CentOS), boot (for CentOS and RHEL), and data partitions by typing the following command and then press Enter:
         less /mnt/etc/mtab
  9. If using SLES 11, install GRUB by typing the following commands, pressing Enter after each:
         grub-install --recheck /dev/sda
         grub-install /dev/sda
  10. If using Ubuntu, CentOS 6.x, RHEL 6.x, or Oracle Linux 6.x, install GRUB by typing the following command, and then press Enter:
         grub-install /dev/sda
  11. If using SLES 12, CentOS 7, RHEL 7, or Oracle 7, install GRUB2 by typing the following command, and then press Enter:
           grub2-install /dev/sda
  12. After you complete installation, run one of the following updates:
    For SLES:
         grub-install.unsupported --recheck /dev/sda 
         grub-install.unsupported /dev/sda
         update-grub

    NOTE: If the update-grub command does not exist on your Linux distribution, omit this option.

    For other distributions:
         grub-install /dev/sda 
         update-grub

    NOTE: If the update-grub command does not exist on your Linux distribution, omit this option.

  13. Remove the Live DVD disk from the CD-ROM or DVD drive and restart the Linux machine.

Managing aging data

This section describes how to manage aging snapshot data saved to your repository. It includes information about retaining recovery points in your repository, retention policies, and the resulting process of rolling up recovery points to conserve space.

This section also describes how to manage retention policies that control rollup, and how to force rollup on demand.

Topics include:

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione