Tchater maintenant avec le support
Tchattez avec un ingénieur du support

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

Introducing NetVault Bare Metal Recovery Plug-ins Deploying NetVault Bare Metal Recovery Using the Plug-in Offline Client
Plug-in Server: an overview Installing and removing Plug-in Server Configuring Plug-in Server for use with Plug-in Offline Client Booting a NetVault Bare Metal Recovery Client with Plug-in Offline Client Backing up data with Plug-in Offline Client Restoring data with Plug-in Offline Client
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
Using NetVault Bare Metal Recovery Plug-in Live Client for Linux
Plug-in Live Client for Linux: an overview Installing and removing Plug-in Live Client for Linux Generating a DR image for use with Plug-in Live Client for Linux Creating the required bootable CD for use with Plug-in Live Client for Linux Recovering a DR image for use with Plug-in Live Client for Linux
NetVault Bare Metal Recovery physical-to-virtual (P2V) recovery  Troubleshooting

Performing a restore in which Disk Numbers are different from the backup

In some instances, the Disk Number assigned to a drive during backup might be different for the restore. To work around this issue, note the Disk ID and disk order displayed on the Create Selection Set page, use the Plug-in Offline Client to boot the machine that is targeted for the restore, and then note whether the disk order is different. If the order is different, use the Rename option during the restore process to prevent data loss.

To determine whether the disk order is different
1
In the Navigation pane of the NetVault WebUI on the NetVault Server, click Create Restore Job.
2
On the Create Restore Job — Choose Saveset page, select Plug-in Server from the Plugin Type list.
3
In the saveset table, double-click the applicable saveset to open it.
4
When the backed-up client machine is displayed, double-click it to open it and list the disks that were backed up.
5
Note the information displayed within the parentheses for each disk.
6
Use the Plug-in Offline Client to boot the NetVault Bare Metal Recovery Client that is targeted by the restore, access the NetVault Server, and open the NetVault Selections page.
7
Drill down to the disk-level of the client, and note the current disk order.
If the order is different, use the Rename option during the restore.

Access denied during MBR recovery

During recovery of a Master Boot Record (MBR), if you receive an error message that indicates access was denied because a filesystem is still mounted, you must manually unmount the filesystem and complete the recovery process again.

VMware ESX and ESXi Server 4.x and earlier not supported with Windows PE

Because the Plug-in Offline Client for Windows PE is based on Windows 8, you might encounter the following error if you boot a VM that resides on VMware ESX or ESXi Server 4.x or earlier:

Your PC ran into a problem and needs to restart. We're just collecting some error info, and then we'll restart for you. (0% complete)
If you would like to know more, you can search online later for this error: HAL_INITIALIZATION_FAILED

For more information, see http://support.microsoft.com/kb/2814803.

Attaching a restored VMDK image to a VM fails to power on the machine

Restoring a Plug-in Live Client Windows backup to a local directory VMDK image and then attaching it to a virtual machine (VM) created from VMware can fail to power on the VM with the following error: Failed - Unsupported or invalid disk type 2 for ‘scsi0:0’. Ensure that the disk has been imported.

This error happens ESXi version 6.5 fails to address the VMDK descriptor.

To resolve the issue, after you restore the VMDK image, complete one of the following two methods:

•
Method 1: While attaching the VMDK to the VM, change the storage controller from SCSI to IDE.
•
Method 2: Use vmkfstools to convert the flat disk vmdk to a vmdk descriptor file. For more information, see https://kb.vmware.com/s/article/1028943.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation