지금 지원 담당자와 채팅
지원 담당자와 채팅

NetVault Bare Metal Recovery 13.1.2 - 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
NetVault Bare Metal Recovery physical-to-virtual (P2V) recovery  Troubleshooting

Excluding LUNs from the NetVault Selections pages

In some instances of using the Windows PE-based Plug-in Offline Client, the logical unit numbers (LUNs) of a Fibre Channel card are identified as drives by the Windows Disk Manager. As a result, NetVault might also interpret the LUNs as drives, display them on the NetVault Selections page, and attempt to include them in a backup job if they are selected. The VSS Backup job then fails because of this issue. To work around this issue, you can edit the “nvdrw.cfg” file to prevent the LUNs from appear on the NetVault Selections page.

To update the file
1
Locate and open the “nvdrw.cfg” file in a text editor.
For the Plug-in Offline Client, this file is located in \\Windows\System32\. For the Plug-in Live Client, this file is located in \\NetVault\config\. If the file does not exist, you can create it.
2
Update the file to include a section similar to the following; replace the applicable segments with the information for your card:
[Disk Vendor:Product]
IgnoreDisk=LSI, Universal Xport
3
Save and close the file.
4
For the Plug-in Offline Client, complete the following steps to restart the drdaemon:
a
On the NetVault Bare Metal Recovery Client, start the Windows Task Manager by typing the following at a command prompt, and pressing Enter:
taskmgr
b
In the Windows Task Manager screen, select the Processes tab, right-click drdaemon, select End Process, and close the Task Manager.
c
To restart the drdaemon, type the following at a command prompt; if necessary, click Launch CMD again; and press Enter:
drdaemon
5
For the Plug-in Live Client, access the Windows Task Manager on the NetVault Bare Metal Recovery Client, select the Processes tab, right-click nvdrw, select End Process, and close the Task Manager.
6
Access the NetVault Selections page of the NetVault Backup window, and verify that the changes are reflected.

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.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택