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.
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.
The startup parameters in the target server boot record are automatically repaired.
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.
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