For BMR 7.5.x.x, after BMR restoration of a RHEL6 client, during the first restart, the system may go into maintenance mode.

Article:TECH179048  |  Created: 2012-01-16  |  Updated: 2013-03-04  |  Article URL http://www.symantec.com/docs/TECH179048
Article Type
Technical Solution

Product(s)

Issue



In case of RHEL6 platform, after BMR restore, system goes into Maintenance mode during BMR firstboot.

This is due to UDEV daemon which dynamically detects devices and populates the /dev/sdX names thereby resulting in dissimilar ordering of the disk name across reboots. This can result in system going into Maintenance mode during BMR first boot due to system files like “/etc/fstab” having the wrong entries for the disk names.

During system restore the internal and/or SAN disks can change disk names from /dev/sda, /dev/sdb, /dev/sdc to different disk names like /dev/sdb, /dev/sdd, /dev/sdc, while the /etc/fstab entries of the system still expect the old disk name entries for their respective partitions.

For example:  Suppose in /etc/fstab, if /dev/sdf2 is the /boot partition, then this will fail BMR first boot if this changes to some other disk name say /dev/sdb2.


Error



Sample error messages:

"No such file or directory /dev/sdaXN"

or

"/dev/sdXN already mounted”

 


Environment



Associated platforms: RHEL6 and later
BMR version: 7.5.x.x and beyond


Solution



Carry out any of the following procedures:

Procedure A

  • Reboot the system.

Procedure B

Redo the system restore as follows:

  1. Carry out the Prepare To Restore (PTR) task.
  2. Pull the client-ip_hex-address.conf file from the BMR database by running the following commands:

a. /usr/openv/netbackup/bin/bmrs -o query -r database -table restoreconfigfile

This command provides a list of configuration files along with their configuration IDs.

b. /usr/open/netbackup/bin/bmrc -o pull -r info -client clientname -source
client-ip_hex-address.conf -destination client-hex-address.conf

  1. Append the following 2 lines to the client-hex-address.conf file:

use_UUID_set=YES
export use_UUID_set

  1. Save the file.
  2. Push the file again into the BMR database using the following command:

/usr/open/netbackup/bin/bmrc -o push -r info -client client-name -source
client-ip_hex-address.conf -destination client-hex-address.conf

Note: Do not initiate the Prepare To restore (PTR) process again, at this stage.

  1. Boot the client for restoration.

 




Article URL http://www.symantec.com/docs/TECH179048


Terms of use for this information are found in Legal Notices