NetVault Bare Metal Recovery 12.4 - Release Notes for Linux Live Client Plug-in

NetVault Bare Metal Recovery Plug-in Live Client for Linux 12.4 is a minor release, with enhanced features and functionality. For complete product documentation, visit https://support.quest.com/technical-documents.

Resolved issues

The following is a list of issues resolved in this hotfix.

Table 1. Resolved issues
Resolved issue	Issue ID
Corrected an installation issue in which the value of the TARFLAGS variable was not populated correctly.	DNBMR-1196

Known issues

The following is a list of issues, including issues attributed to third-party products, known to exist at the time of release.

Table 2. General known issues

Known issue

Issue ID

Backing up a Red Hat Enterprise Linux (RHEL) 5.1 Client might fail with the following error:

Cannot find the Xen hypervisor file which the system was booted with. Without this, it is not possible to perform a system installation. You should create the file /storix/config/multibootfile with a line specifying the full path to the hypervisor file and recreate the boot media.

Workaround:

Open “/boot/grub/grub.conf”, and find the section from which the machine was booted.

It is similar to the following: kernel /xen.gz-2.6.18-53.el5

Create a file named “/storix/config/multibootfile” with a line specifying the full path to the hypervisor file as shown in the following example: /boot/xen.gz-2.6.18-53.el5

DNBMR-16 (17294, VLG‑110), DNBMR-64 (17342, VLG‑156)

After a successful restore, the size of mounted partitions might change and the temporary file systems might be unmounted. Manually mount the temporary filesystem (tmpfs) or edit “/etc/fstab” to mount it when the system starts.

DNBMR-24 (17302, VLG‑118)

If the SCSI or network devices are not available upon booting from the Storix boot media, it might indicate that your device modules are not included on the boot media or not listed in the master modules file.

Workaround:

To add the missing SCSI and network device modules, perform the following steps on the client on which the boot media is created:

To copy the original “bootlist” file to your custom directory, issue the following command: # cp /opt/storix/config/bootlist_scsi /storix/config/bootlist_scsi

NOTE: Use “bootlist_network” files when adding an entry for network driver and “bootlist_scsi” files when adding an entry for SCSI driver.

Open the “bootlist” file in the custom directory, and add your SCSI device modules following #$ SCSI adapters and network device modules following "#$ Ethernet Network Adapters.

Use the following format to add the modules: #MOD:S:module name:description

Example: #MOD:S:dc395x_trm:DC-395U SCSI adapter support

DNBMR-39 (17317, VLG‑131)

On an Ubuntu client, the Storix maintenance shell does not return the maint> prompt after a restore. This issue occurs because /bin/sh is linked to /bin/dash in Ubuntu. When the restore completes, Storix does a chroot to the newly restored root and invokes /bin/sh. This shell does not display any prompt.

DNBMR-68 (17346, VLG‑161)

The plug-in does not support encrypted partitions. If an encrypted partition is enabled, a backup fails with the following errors:

Warning: Volume Group VolGroup00 will be ignored because it contains physical volume mapper/luks-bfb0ef38-6066-4d0e-9e15-8c5fbe53ee4f, which is not a supported device type.

Error: The / filesystem exists on the system but is not included on the backup because it is in a logical volume you did not select to include. You must include volume group VolGroup00 on a system backup.

DNBMR-83 (17361, VLG‑175)

If you are using Storix, restoring to the same client or a different client of the same disk size — either of which is configured as part of a logical group and volume — causes the following message to appear:

The following non-fatal errors must be corrected before continuing: Disk sdb: This disk is not large enough for the partitions as they are currently defined. You must reduce the space requirements on this disk by at least 7MB by removing the partitions or reducing their sizes.

Workaround: To adjust the partition sizes, use the View/Change Installation Settings feature in Storix.

To allow the recovery process to re-create a striped logical volume across multiple disks, manually change the stripe size.

From the Main Menu in Storix, select View/Change Installation Settings > Logical Volume Management > Add or Change Logical Volume.

Select the applicable volume, and press Enter.

Change the Stripe Size from 0 to the size that was originally configured.