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.
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.
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.
df
umount <mount point>
fsck -f <volume>
If the fsck returns clean, the file system is verified.
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
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.
mount /<restored volume[root]> /mnt
For example, if /dev/sda2 is the root volume, then type mount /dev/sda2 /mnt 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. |
blkid
command. Type the following and then press Enter:
blkid [volume]
|
NOTE: You can also use the |
mount --bind /dev /mnt/dev
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
chroot /mnt /bin/bash
/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
/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
grub-install --recheck /dev/sda
grub-install /dev/sda
grub-install /dev/sda
grub2-install /dev/sda
grub-install.unsupported --recheck /dev/sda grub-install.unsupported /dev/sda update-grub
NOTE: If the |
grub-install /dev/sda update-grub
NOTE: If the |
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:
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 利用規約 プライバシー Cookie Preference Center