Introducing NetVault Bare Metal Recovery Plug-ins
NetVault Bare Metal Recovery Plug-ins: at a glance
Key benefits
Feature summary
Target audience
Recommended additional reading
Deploying NetVault Bare Metal Recovery
NetVault Bare Metal Recovery components
Using the Plug-in Offline Client
Plug-in Offline Client component
Plug-in Live Client for Windows component
Plug-in Live Client for Linux component
Plug-in Server component
VaultOS component
NetVault Bare Metal Recovery deployment scenarios
Plug-in Offline Client only x86/x86-64 clients with Windows-based NetVault Server deployment
Plug-in Offline Client only x86/x86-64 Clients with Linux-based NetVault Server deployment
Plug-in Live Client for Windows withWindows-based NetVault Server deployment
Plug-in Live Client for Windows with Linux-based NetVault Server deployment
Plug-in Live Client for Linux with Linux-based NetVault Server deployment
Plug-in Live Client for Linux with Windows-based NetVault Server deployment
Plug-in Live Client for Windows and for Linux with Linux-based NetVault Server deployment
Plug-in Live Client for Windows and for Linux with Windows-based NetVault Server deployment
Plug-in Server: an overview
Installing and removing Plug-in Server
Using NetVault Bare Metal Recovery Plug-in Live Client
Prerequisites for installing Plug-in Server
Installing or upgrading Plug-in Server
Removing Plug-in Server
Upgrading Plug-in Server
Configuring Plug-in Server for use with Plug-in Offline Client
Creating a Plug-in Offline Client Boot System
Booting a NetVault Bare Metal Recovery Client with Plug-in Offline Client
Creating a Linux-based Boot System
Creating a Windows PE-based Boot System
Creating a rescue device for use with a LiveCD
Adding a NetVault Bare Metal Recovery Client to the Plug-in Server
Booting with Plug-in Offline Client
Backing up data with Plug-in Offline Client
Using a Windows Server 2012-based virtual machine with Plug-in Offline Client for Linux
Gathering NetVault Bare Metal Recovery Client network information
Booting the NetVault Bare Metal Recovery Client with the Linux-based Plug-in Offline Client
Booting the NetVault Bare Metal Recovery Client with the Windows PE-based Plug-in Offline Client
Loading drivers dynamically
Injecting drivers and restarting drdaemon to facilitate storage controller recognition
Injecting drivers into the Plug-in Offline Client image
Booting the NetVault Bare Metal Recovery Client from a LiveCD
Prerequisites for backing up data with Plug-in Offline Client
Restoring data with Plug-in Offline Client
Booting the NetVault Bare Metal Recovery Client with Plug-in Offline Client
Verifying Disk Geometry and Device Size
Backing up data with Plug-in Offline Client
Using Plug-in Offline Client to restore data to a physical machine
Prerequisites for restoring data with Plug-in Offline Client to a physical machine
Restore procedure for using Plug-in Offline Client to restore data to a physical machine
Post-restore for using Plug-in Offline Client to restore data to a physical machine
Using Plug-in Offline Client to restore data as a VMDK Image
Selecting data for a restore using Plug-in Offline Client to restore data as a VMDK Image
Setting restore options for using Plug-in Offline Client to restore data as a VMDK Image
Finalizing and submitting the job for using Plug-in Offline Client to restore data as a VMDK Image
Creating the VM from the restored VMDK Image
Using Plug-in Offline Client to recover data to a standby NetVault Bare Metal Recovery Client
Plug-in Live Client overview
Configuring Plug-in Server for use with Plug-in Live Client
Using NetVault Bare Metal Recovery Plug-in Live Client for Linux
Creating a Plug-in Offline Client Boot System
Installing and removing Plug-in Live Client
Creating a Linux-based Boot System for use with Plug-in Live Client
Creating a Windows PE-based Boot System for use with Plug-in Live Client for Windows
Installing VaultOS on a writable CD for use with Plug-in Live Client
Adding a NetVault Bare Metal Recovery Client to the Plug-in Server for use with Plug-in Live Client
Installing or upgrading Plug-in Server for use with Plug-in Live Client
Adding Plug-in Live Clients for use with Plug-in Live Client
Installing or upgrading Plug-in Live Client
Upgrading Plug-in Live Client
Removing Plug-in Live Client
Backing up data with Plug-in Live Client
Prerequisites for backing up data with Plug-in Live Client for Windows
Performing an online backup of data using Plug-in Live Client for Windows
Booting a NetVault Bare Metal Recovery Client with Plug-in Offline Client
Restoring data with Plug-in Live Client
Restoring to a physical machine with Plug-in Live Client for Windows
Prerequisites for restoring to a physical machine with Plug-in Live Client for Windows
Restore procedure for restoring data with Plug-in Live Client
Restoring data as a VMDK Image with Plug-in Live Client for Windows
Selecting data for a restore as a VMDK Image with Plug-in Live Client for Windows
Setting restore options for a restore as a VMDK Image with Plug-in Live Client for Windows
Finalizing and submitting the job for a restore as a VMDK Image with Plug-in Live Client for Windows
Creating the VM for a restore as a VMDK Image with Plug-in Live Client for Windows
Plug-in Live Client for Linux: an overview
Installing and removing Plug-in Live Client for Linux
NetVault Bare Metal Recovery physical-to-virtual (P2V) recovery
Prerequisites for installing Plug-in Live Client for Linux
Installing or upgrading Plug-in Live Client for Linux on each Linux-based NetVault Bare Metal Recovery Client
Removing Plug-in Live Client for Linux
Generating a DR image for use with Plug-in Live Client for Linux
Selecting data for a backup with Plug-in Live Client for Linux
Finalizing and submitting the job for a backup with Plug-in Live Client for Linux
Creating the required bootable CD for use with Plug-in Live Client for Linux
Creating the CD and saving it for future use with Plug-in Live Client for Linux
Creating the CD at the time of recovery for use with Plug-in Live Client for Linux
Recovering a DR image for use with Plug-in Live Client for Linux
Restoring data using a DR image with Plug-in Live Client for Linux
Selecting data for a restore with a DR image with Plug-in Live Client for Linux
Setting restore options for a DR image with Plug-in Live Client for Linux
Finalizing and submitting the job for a restore with a DR image with Plug-in Live Client for Linux
Booting the target NetVault Bare Metal Recovery Client with the appropriate OS and drivers for use with Plug-in Live Client for Linux
Prerequisites for booting the target NetVault Bare Metal Recovery Client for use with Plug-in Live Client for Linux
Reconfiguring the communication port for the target NetVault Bare Metal Recovery Client for use with Plug-in Live Client for Linux (optional)
Boot procedure for the target NetVault Bare Metal Recovery Client for use with Plug-in Live Client for Linux
Accommodating for Raw disks for use with Plug-in Live Client for Linux
Monitoring job progress and finalizing a recovery with Plug-in Live Client for Linux
Completing post-restore requirements for use with Plug-in Live Client for Linux
Installing SCSI and IDE device drivers on a physical machine
Supported physical to virtual configurations
Troubleshooting
Excluding LUNs from the NetVault Selections pages
Performing a restore in which Disk Numbers are different from the backup
Access denied during MBR recovery
VMware ESX and ESXi Server 4.x and earlier not supported with Windows PE
Attaching a restored VMDK image to a VM fails to power on the machine
VMDK restore job to remote ESXi 6.0 fails with failure to clone error
Using NetVault Bare Metal Recovery Plug-in Live Client for Linux
Using NetVault Bare Metal Recovery Plug-in Live Client for Linux
Plug-in Live Client for Linux: an overview
Plug-in Live Client for Linux: an overview
This topic describes how to install, configure, and use Plug-in Live Client for Linux for backing up and restoring data.
The Plug-in Live Client for Linux supports DR operations for Linux x86 and x86-64-based systems. This plug-in can back up and recover an entire disk including the OS, applications, system settings, partition information, and data. The plug-in enables online backup a full Linux system, thus allowing system administrators to conduct DR backups while eliminating system downtime for users.
After the plug-in is correctly installed and configured, a DR image of a live system can be taken and saved for future recovery if a system failure occurs. During creation of this image, the Plug-in Live Client for Linux can automatically include all information pertaining to the networking hardware in use by the target Linux NetVault Bare Metal Recovery Client machine, that is, driver information files. These files are then compiled into a separate CD creation file, “.iso” file format, that can be saved along with the DR image. At the time of recovery, this file is recovered and used to create a bootable CD, complete with the necessary driver files that were taken from the Linux NetVault Bare Metal Recovery Client. Using this CD, the Linux NetVault Bare Metal Recovery Client can be successfully booted to a state that allows for the recovery of the DR image.
The Plug-in Live Client for Linux does not support the following:
|
• |
For large sparse files, the BB Agent Timeout must be configured to a large value. For details on the BB Agent Timeout option, see Storix installation for Plug-in Live Client for Linux. |
Installing and removing Plug-in Live Client for Linux
Installing and removing Plug-in Live Client for Linux
This topic covers the installation procedures required to install Plug-in Live Client for Linux for use with NetVault.
|
• |
Prerequisites for installing Plug-in Live Client for Linux
Prerequisites for installing Plug-in Live Client for Linux
|
• |
Plug-in Live Client for Linux obtained: Download the plug-in from the Quest website or the Quest NetVault Installation CD. |
|
• |
Separate NetVault Server established: A machine that does not serve as a Linux NetVault Bare Metal Recovery Client must be set up with the Server version of NetVault installed. This machine must have network connectivity to all desired Linux NetVault Bare Metal Recovery Clients. |
|
IMPORTANT: NetVault requires that you install the Plug-in Live Client for Linux on both the NetVault Server and each applicable NetVault Client. Installation of the plug-in is required on the Client machine during backup and on the Server machine during restore. If the NetVault Server is running an OS other than Linux, ensure that the correct version of this plug-in is available for installation on this OS. For example, if the NetVault Server is running Windows, the Windows version of the Plug-in Live Client for Linux is required for installation on the NetVault Server, while the Linux-based version of the plug-in is required for installation on all target NetVault Bare Metal Recovery Clients. If both the NetVault Server and the desired NetVault Bare Metal Recovery Clients are running Linux, only a single version of the plug-in is required. |
|
• |
Uninstall previous version of Plug-in Live Client: If a previous version of the plug-in is installed, it must be removed before proceeding with the installation. For details, see Removing Plug-in Live Client for Linux. |
|
• |
Client machine memory requirement: All machines that are to serve as NetVault Bare Metal Recovery Clients must have at least 128 MB of RAM installed. |
|
• |
Linux NetVault Bare Metal Recovery Client machines configured as NetVault Clients: All machines that serve as Linux NetVault Bare Metal Recovery Clients must have at least the Client version of NetVault installed. Also, each machine must be successfully added to the NetVault Server as NetVault Clients by using the Manage Clients page. |
|
• |
100 MB free space on all target machines for plug-in installation: All machines that the plug-in is to be installed on must have 100 MB of free space to accommodate a third-party DR boot utility application that is used by this plug-in to perform backups and restores. |
|
• |
Extra free hard disk space on target NetVault Bare Metal Recovery Clients: This plug-in uses existing free space on a target NetVault Bare Metal Recovery Client’s hard disk to synchronize the backup of currently online files. If a target NetVault Bare Metal Recovery Client’s hard disk is full, or nearly full, attempts to perform an online backup may fail. |
|
• |
The “genisoimage” or “mkisofs” utility installed and available on all Linux NetVault Bare Metal Recovery Clients: The plug-in requires installation of either of these components to allow for the creation of “.iso” CD creation files from any potential Linux NetVault Bare Metal Recovery Clients. These components may not be automatically available with all installations of Linux. |
If the component does not exist on an intended Linux NetVault Bare Metal Recovery Client, it can be obtained and installed as follows:
|
a |
Access your copy of the Linux installation media, and locate the “genisoimage*.rpm” or “mkisofs*.rpm” file. |
rpm -i <installationFileName>
|
• |
The “SYSLINUX” package installed (SUSE Linux 9.0, ONLY): This version of the Plug-in Live Client for Linux uses a specific boot loader application for the creation of the bootable CD that is required for the restore procedure. Default installations of SUSE Linux 9.0 do not offer support for this boot loader application. Therefore, the SYSLINUX package must be installed on all NetVault Bare Metal Recovery Client systems running SUSE Linux 9.0. At time of this publication, this component could be found for download at: http://syslinux.zytor.com |
|
• |
The “vim-6.3.84-2.i586.rpm” package installed (SUSE Linux 10, ONLY): Backups of SUSE Linux 10 NetVault Bare Metal Recovery Clients fail, unless this package is installed. At time of this publication, this package could be obtained from: http://rpm.pbone.net/index.php3/stat/17/dept/4/idg/Productivity_Editors_Vi |
|
• |
Enable RAM file system and RAM disk (initramfs/initrd) support: Support for ramdisk is enabled by default. If it is not, run make menuconfig or make xconfig from the kernel source directory and set the Initial RAM filesystem and RAM disk (initramfs/initrd) support option under General setup. The .config parameters are BLK_DEV_INITRD and BLK_DEV_RAM. |
During a backup, the Plug-in Live Client for Linux uses Storix to create a bootable image from the currently running Linux installation. While booting, it tries to load its data into a temporary ramdisk (root=/dev/ram0). To complete this process, the booted kernel must have ramdisk support. Because the plug-in uses the same kernel that the previously running system was using, the original kernel must have support for ramdisk enabled.
|
• |
Additional configuration for Xen Dom0 machine: On a Xen Dom0 machine, complete the following steps: |
|
a |
Open “/boot/grub/grub.conf” and find the section from which the machine was booted. |
|
b |
Create a file named “/storix/config/multibootfile” with a line specifying the full path to the hypervisor file as shown in the following example: |
If this process is not completed, backups may fail with the following error: “Cannot find the Xen hypervisor file which the system was booted with. Without this process, you cannot install a system. Create the file /storix/config/multibootfile with a line specifying the full path to the hypervisor file and recreate the boot media.”
|
IMPORTANT: NetVault’s Plug-in for Encryption functionality is not supported for use with this plug-in. Ensure that this functionality is disabled before installing and using NetVault Bare Metal Recovery. For details on uninstalling the Plug-in for Encryption, see the Quest NetVault Plug-in for Encryption User’s Guide. |
|
• |
Multipath support: If you intend to use multipath support, verify that your environment meets the following requirements. For more information, see the Storix System Backup Administrator DM‑Multipath Guide, which is available at http://www.storix.com/download/sbaDM-Multipath.pdf. |
|
• |
Software requirements: At a minimum, you must have: |
|
• |
Device naming: The SBAdmin software must be able to recognize your devices before creating a backup. There are multiple ways your multipath devices can be named. How the devices are named depends on the “user_friendly_names” setting in “/etc/multipath.conf,” aliases set up in “/etc/multipath.conf,” and UDEV rules. Multipath support with SBAdmin requires the setting “user_friendly_names yes” and that you use a UDEV rule that creates a symbolic link from the device node to the device in “/dev/mpath.” |
|
• |
Entries in “/etc/fstab”: Different Linux distributions handle multipath devices differently. One area that can cause problems with the SBAdmin software is the mount entry in the “/etc/fstab” file. Some distributions use an underlying path device, which causes problems when the software queries the device for size and geometry. If your “/etc/fstab” file is using the “/dev/disk/by-uuid/*” — where * is a numerical value — naming convention, change the entries to the dm-multipath device name or to use the “/dev/disk/by-name/*” naming convention. |
|
• |
Systems with non-English characters in filenames or directories: If you use non-English characters in filenames or system names, you must update the “/.stdefaults” file before completing a backup job. In the “/.stdefaults” file, specify the applicable language and set the tar flag to blank. For example, if you are using a system that includes files that use Japanese characters, you must update the file with the following entries: |