NetVault Bare Metal Recovery 13.1.2 - User Guide for Plug-ins

Creating the VM from the restored VMDK Image

After the restore job has completed, you can create a VM from the restored VMDK file using the VMware Server console.

Confirm that the VMDK file is located in the datastore path that was specified under ESX Server Options.

On the VMware ESX or VMware ESXi Server, browse the datastore and navigate to the specified path.

The path should contain a file with the extension “.vmdk”.

In the upper-left corner of the VMware Server console, click the Create Virtual Machines icon.

When the Configuration dialog box is displayed, select Custom, and click Next.

In the Name field on the Name and Location dialog box, enter a descriptive name for your VM, and click Next.

When the Datastore dialog box is displayed, select a datastore in which to store the VM, and click Next.

When the Virtual Machine Version dialog box is displayed, select the version, and click Next.

When the Guest Operating System dialog box is displayed, select the guest OS, and click Next.

When the CPUs dialog box is displayed, select the number of virtual processors on the VM, and click Next.

When the Memory dialog box is displayed, configure the VM’s memory size, and click Next.

When the Network dialog box is displayed, configure the VM’s network connections, and click Next.

When the SCSI Controller dialog box is displayed, select the SCSI Controller type, and click Next.


	NOTE: NetVault Bare Metal Recovery only supports LSI Logic Parallel SCSI controllers for ESX 4.0 and LSI Logic SCSI for ESX 3.5.

When the Select a Disk dialog box is displayed, select Use an existing virtual disk, and click Next.

When the Browse Datastores dialog box is displayed, navigate to the datastore to locate the VMDK file, select it, and click OK.

When the Advanced Options dialog box is displayed, select any applicable options, and click Next.

When the Ready to Complete dialog box is displayed, review the summary of the VM you created, and then click Finish.

When the new VM is displayed in the left pane of the VMware console, right-click it, and select Open Console from the menu.

Turn on the VM from the console.

The Windows logo is displayed following a successful boot.

NOTE: Additional notes for creating the VM from the restored VMDK Image:

•

Quest recommends installing VMware Tools before using the VM. For instructions, see the VMware documentation for instructions.

•

The “@” character cannot be used in the datastore path.

•

When restoring to an ESX or ESXi Server, verify that there is sufficient free disk space available on the ESX or ESXi VM. For details on calculating the required disk space, see http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1003755

•

The block size determines the minimum amount of disk space that any file takes up on Virtual Machine File System (VMFS) datastores. Choose the block size carefully when creating VMFS datastores. The following block sizes are available:

•

1 MB block size = 256 GB maximum file size

•

2 MB block size = 512 GB maximum file size

•

4 MB block size = 1024 GB (1 TB) maximum file size

•

8 MB block size = 2048 GB (2 TB) maximum file size

Using Plug-in Offline Client to recover data to a standby NetVault Bare Metal Recovery Client

If a hardware failure occurs in a specific client machine, you can restore a previous NetVault Bare Metal Recovery backup to a different, preconfigured NetVault Bare Metal Recovery Client, or “standby.” To accomplish this restore, use the information provided in the following topics.

Before performing the recovery procedure, consider the following important points:

•

This procedure only works when restoring backups performed with the standard Plug-in Server.

•

The target NetVault Bare Metal Recovery Client, the “standby,” for this operation must be preconfigured using the procedure described in Adding a NetVault Bare Metal Recovery Client to the Plug-in Server.

•

When attempting this operation, there must be sufficient disk space on the standby machine; otherwise, the operation fails. For more information, see Verifying Disk Geometry and Device Size.

•

With this process, the new target machine must have a similar hardware configuration to that of the originally backed-up machine, regarding the NIC and SCSI cards used. If the hardware in use differs too much from the original, driver software conflicts may occur, resulting in a failed restore.

•

Values entered in the Restore Name field are case-sensitive. Ensure that the exact NetVault name of the machine to be relocated to is entered in this field; otherwise, the restore fails.

•

Relocations of this type must be restored to the same partition they were backed up from. For example, if a NetVault Bare Metal Recovery backup was taken of a system’s “C:\” partition on a Windows-based system, the restore must be performed to the relocation target’s “C:\” partition as well. You cannot restore to a different partition.

•

If you are restoring a 64-bit Linux Client that uses the Unified Extensible Firmware Interface (UEFI) with Plug-in Offline Client for Linux, add the applicable entry in the UEFI/EFI boot manager the first time that you boot the standby client after the restore. To do so, during the boot routine, press Esc, select Boot Maintenance Manager > Configure boot options > Add boot, add HD(1, GPT, <partitionGUID>, <partitionOffset>,<partitionSize>)/EFI/<LinuxDistribution>/grub(64).efi, and commit the changes.

To recover to a standby NetVault Bare Metal Recovery Client, perform the following steps.

In the Navigation pane of the NetVault WebUI, click Create Restore Job.

On the Create Restore Job — Choose Saveset page, select Plug-in Server from the Plugin Type list.

To filter the items displayed in the saveset table further, use the Client, Date, and Job ID lists.

The table displays the saveset name (job title and saveset ID), creation date and time, and size. By default, the list is sorted by creation date.

In the saveset table, locate the applicable client, and select the applicable item.

Click Next.

On the Create Selection Set page, select and open the disk to be relocated.

Click a disk item, and select Rename from the context menu.

In the Rename/Relocate dialog box, enter the Disk Number of the disk to be restored, and click Ok.

For example, enter 0 for system disk 1, 1 for system disk 2, and so on. Evaluation of the SCSI disks is completed before the IDE disks. So a system with two SCSI disks and two IDE disks would have the numbering 0 — SCSI 1, 1 — SCSI 2, 2 — IDE 1, 3 — IDE 2.

Repeat Step 7 and Step 8 for each disk you want to relocate.

On the Create Selection Set page, click

, and ensure that Physical Machine is the selected Restore Type.

In the Restore Name box, enter the name of the preconfigured NetVault Bare Metal Recovery Client that is to serve as the standby machine.

Continue with the restore, as explained previously in Using Plug-in Offline Client to restore data to a physical machine, and submit the job.

Using NetVault Bare Metal Recovery Plug-in Live Client

•

Plug-in Live Client overview

•

Configuring Plug-in Server for use with Plug-in Live Client

•

Installing and removing Plug-in Live Client

•

Backing up data with Plug-in Live Client

•

Booting a NetVault Bare Metal Recovery Client with Plug-in Offline Client

•

Restoring data with Plug-in Live Client

Plug-in Live Client overview

This topic describes how to install, configure, and use Plug-in Live Client for backing up and restoring data.

Plug-in Live Client, referred to as the Plug-in Live Client, is a DR solution that lets you back up and restore a hard disk on a target client, including the OS, applications, system settings, partition information, and data.

•

Backup: Backup lets you target a Windows-based system, and perform a full and complete backup of its contents while the system remains online and available to users.

•

Recovery: Recovery requires that you use the included Plug-in Offline Client boot utility to take the protected Windows-based system offline, which allows for complete access to its hard disk for restore operations.

In addition, the Plug-in Live Client also provides the following features:

•

VSS-based snapshots (Windows): For VSS-enabled applications such as SQL Server, Exchange, and SharePoint, the software uses VSS to quiesce these applications before taking the snapshot. Using VSS to quiesce the applications reduces the amount of application crash recovery that must be performed after recovery of the image file. This method is supported on Windows Server 2012 and later.

•

Block-based snapshots (Linux): The Linux version of the plug-in uses a block-based snapshot kernel module to recover data at the block level, similar to the process for Windows.

•

Eliminate backup ‘whitespace’: This feature lets you back up only the used blocks on the partition. For example, if a machine has a “C:” drive of size 10 GB and only 6 GB is used, the plug-in only backs up 6 GB, the used space. This feature saves a considerable amount of time and space.

•

Restore as VMDK Image: This feature restores the backup of a physical machine to a VMDK Image that can be used to create a VM.


	IMPORTANT: This plug-in works with the Plug-in Server. Before backing up with the Plug-in Live Client, install the Plug-in Server and verify connectivity between target NetVault Bare Metal Recovery Clients and the NetVault Server where Plug-in Server is installed. In addition, the Plug-in Server is required to perform all restores of Plug-in Live Client backups.

Selecione seu produto:

Para podermos atendê-lo melhor, informe o Propósito de seu chat:

Soluções recomendadas para seu problema

NetVault Bare Metal Recovery 13.1.2 - User Guide for Plug-ins

Creating the VM from the restored VMDK Image

Using Plug-in Offline Client to recover data to a standby NetVault Bare Metal Recovery Client

Using NetVault Bare Metal Recovery Plug-in Live Client

Plug-in Live Client overview