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.
1 |
Locate and open the “nvdrw.cfg” file in a text editor. |
4 |
For the Plug-in Offline Client, complete the following steps to restart the drdaemon: |
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: |
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. |
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.
1 |
In the Navigation pane of the NetVault WebUI on the NetVault Server, click Create Restore Job. |
2 |
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. |
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:
For more information, see http://support.microsoft.com/kb/2814803.
© ALL RIGHTS RESERVED. Termini di utilizzo Privacy Cookie Preference Center