Converse agora com nosso suporte
Chat com o suporte

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

Quest® NetVault® Bare Metal Recovery Plug-in Live Client for Linux 14.0

Quest® NetVault® Bare Metal Recovery Plug-in Live Client for Linux 14.0
These release notes provide information about the Quest® NetVault® Bare Metal Recovery Plug-in Live Client for Linux release.

About this release

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

Enhancements

The following is an enhancement implemented in NetVault Bare Metal Recovery Plug-in Live Client for Linux 14.0

NOTE: NetVault Bare Metal Recovery Plug-in Live Client for Linux 14.0 does not offer backward compatibility with BMR 13.x version backups. It uses Storix, a third-party DR boot utility, to boot the target NetVault Bare Metal Recovery Client and recover data. For restoring BMR 13.x versions, use 13.x servers only.

Known issues

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

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

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:

1
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.
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

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:

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:

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.

1
From the Main Menu in Storix, select View/Change Installation Settings > Logical Volume Management > Add or Change Logical Volume.
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.

 

Because Storix SBAdmin does not support the Dell EqualLogic driver, the plug-in does not support backup jobs sent to Dell EqualLogic devices.

DNBMR-1079, DNBMR-1097 (31073, 32465)

The virtual machine failed to start after a physical-to-virtual (P2V) restore.

Workaround: Before you take a backup of a physical machine, start and run the command dracut -f -N to ensure the recovery process succeeds.

DNBMR-1271

File and folder has been garbled since restore completed

DNBMR-1294

Ferramentas de autoatendimento
Base de conhecimento
Notificações e alertas
Suporte a produtos
Downloads de software
Documentação técnica
Fóruns de usuário
Tutorial em vídeo
Feed RSS
Fale conosco
Obtenha assistência de licenciamento
Suporte técnico
Visualizar tudo
Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação