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

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: 1 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 2 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	17294 (VLG‑110), 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.	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: 1 Issue the following command to copy the original “bootlist” file to your custom directory: # 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. 2 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	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.	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.	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: Use the View/Change Installation Settings feature in Storix to adjust the partition sizes.
To allow the recovery process to re-create a striped logical volume across multiple disks, manually change the stripe size. 1 From the Main Menu in Storix, select View/Change Installation Settings > Logical Volume Management > Add or Change Logical Volume. 2 Select the applicable volume, and press Enter. 3 Change the Stripe Size from 0 to the size that was originally configured. 4 To return to the Main Menu, press F3 on each selection screen.

System requirements

Before installing NetVault Bare Metal Recovery Plug-in Live Client for Linux 10.5, ensure that your system meets the following minimum hardware and software requirements.

Software requirements

)

Table 3. Requirements

Platform

Linux® x86 (32-bit) Linux® x86-64 (32/64-bit)

Supported Linux® operating systems

 

Table 4. Requirements

Platform	Version	Bit mode
CentOS™	5.1 through 5.10	32/64
CentOS™	6.1 through 6.6	32/64
Debian®	5.0, 6.0	32
Novell® Open Enterprise Server (OES) Linux	2	32/64
Red Hat® Enterprise Linux® (RHEL)	4.x	32/64
RHEL	5.1 through 5.10	32/64
RHEL	6.1 through 6.6	32/64
SUSE® Linux Enterprise Server (SLES®)	10.x	32/64
SUSE® SLES®	11.x	32/64
TurboLinux®	11.x	32
Ubuntu®	10.04, 10.10	32/64
Ubuntu®	11.04	32/64

Supported virtual machine (VM) platforms

 

Table 5. Supported VMs

Platform	Version
VMware® ESX® Server	3.5, 4.0, 4.1
VMware® ESXi™	3.5, 4.0, 4.1, 5.0, 5.1, 5.5

Upgrade and compatibility

For complete supported-platform information, see the Dell NetVault Backup Compatibility Guide.

Pure64 Builds

Starting with NetVault Backup 8.6, a new build type named “LinuxX86Pure64” has been added, while the pure 32-bit Linux® version has been retired. To understand the impact of this change, review the following:

•

Hybrid 32/64-bit Build: The hybrid 32/64-bit build has been retained. However, the platform type has been renamed from “LinuxX8664” to “LinuxX86Hybrid.” This build functions as the standard build for Linux users who do not have a pure 64-bit-only requirement. This build lets you upgrade from pure 32-bit builds and from hybrid builds of NetVault Backup.

The LinuxX86Hybrid build retains binary compatibility with all previous versions of plug-ins, including plug-ins marked as 32-bit and plug-ins designated 64-bit. Also, this build works on 32-bit systems that do not have 64-bit capability.

•

Pure 64-bit Build: A new type of build named “LinuxX86Pure64” has been introduced for pure 64-bit Linux distributions. If you have a specific reason that you cannot use any 32-bit components (for example, you are using a Linux distribution that does not run 32-bit code), use this type. You cannot use this new type to upgrade existing NetVault Backup installations; remove the existing version and install the pure 64-bit version separately. To reduce confusion, warning messages have been added to both the upgrade and installation packages to ensure that you understand that they are not compatible.

 

Table 6. Pure64 builds

OS	Core Build	Plug-in
		32-bit	64-bit	Hybrid	Itanium	Pure64
32-bit	32-bit	X		X
	Hybrid	X		X
64-bit	Itanium				X
	64-bit		X	X
	Hybrid		X	X
	Pure64					X

 

NOTE: X = Compatible Some plug-ins do not support Pure64-bit builds.