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. Depending on the amount of data on the machine, this process takes more time 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.
For example, if /dev/sda2 is the root volume, then type mount /dev/sda2 /mnt and then press Enter.
For example, if /dev/sda1 is the boot volume, then type mount /dev/sda1 /mnt/boot and then press Enter.
3. |
Obtain the Universally Unique Identifier (UUID) of the new volumes by using the blkid command. Type the following and then press Enter: |
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: |
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: |
9. |
As of Rapid Recovery release 6.1.1, you can also relocate recovery points from your primary DVM repository to a tiering repository on a Quest DR backup and deduplication appliance. This frees up storage in your primary repository.
To tier recovery points to secondary storage using this method, you must first add the DR appliance as a repository on your Rapid Recovery Core. For more information on creating a new secondary tiering repository on a DR, see Creating a tiering repository. Then, at the protected machine level, specify in the retention policy the age at which you want recovery points to relocate from your primary to your secondary repository. For more information, see Customizing retention policy settings for a protected machine (especially steps 7 and 10).
For more information about archives, see Archiving.
The Core comes preset with a default retention policy. The default policy retains:
For any machine, you can also create a custom retention policy. Setting the policy at the machine level lets you specify a different retention policy than the default Core policy. For more information about configuring retention policies, see Configuring Core default retention policy settings and Customizing retention policy settings for a protected machine.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center