Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Article Number: 000215502

NetWorker: Virtual Machine Restore Does Not Complete and VM Disk is Removed or Restored as an Empty Drive

Summary: Virtual machine restore fails, and VM disk file is removed or zeroed out during VM restore operations when the vProxy VM experiences vMotion during restore operations.

This article may have been automatically translated. If you have any feedback regarding its quality, please let us know using the form at the bottom of this page.

Article Content

Symptoms

A VM restore performed using the NetWorker VMware Protection (NVP) vProxy appliance fails and the VM shows a missing or zeroed out disk:
VM Shows a Missing or Zeroed Out Disk
Figure 1: VM Shows a Missing or Zeroed Out Disk

 

VM Restore fails with the following error seen in the VM recover session log:

YYYY-MM-DDTHH:MM:SSZ DEBUG:  [105] Data Mover: Hard disk 3: Reporting disk status error: Failed to initialize Block Writer.  Failed to open source VMDK '[DATASTORE] VM_NAME/VM_NAME_2.vmdk': VDDK Error: 13: You do not have access rights to this file.

 

The vProxy's /opt/emc/vproxy/runtime/logs/vrecoverd/vrecoverd-vddk.log may show a "Not found" alert.

YYYY-MM-DDTHH:MM:SSZ NOTICE: VDDK INFO YYYY-MM-DDTHH:MM:SSZ3Z error -[13331] [Originator@6876 sub=transport] Unmounting 42126e5f-f18a-8243-01ea-6a29456f8ecb using transport hotadd failed : Got bad HTTP response during feteching file (Not Found).

 

The vProxy VMs vmware.log shows a vMotion was initiated during the restore.

YYYY-MM-DDTHH:MM:SSZ In(05) vmx - SVMotion: Enter Phase 1
....
YYYY-MM-DDTHH:MM:SSZ In(05) worker-2107995 - SVMotionCleanupThread: Cleanup complete.

 

NOTE: vmware.log files are stored in the same location as the VM configuration files. In the vSphere web client, go to the VM's datastore and open the VM folder, the vmware.log files can be downloaded from here.

 

Cause

VMware Distributed Resource Scheduler (DRS) is enabled. The vProxy VM is vMotioned in the VMware environment during the restore operation. When a VM is vMotioned, it claims any disks attached to it. During a VM restore, the VMs disks are attached to the vProxy; meaning, if a vMotion occurs on the vProxy mid restore the VMs disks are renamed to belong to the vProxy.

 

Depending on how many disks the VM has and when the vMotion occurs on the vProxy, it is possible that some disks may restore correctly. When the vMotion has started, any pending disks fail because the VM disk was renamed and the recover process can no longer find the VMDK using the VM name.

 

This is expected functionality based on vMotion design. See VMware article 1029513. This hyperlink is taking you to a website outside of Dell Technologies.

 

Resolution

Automatic vMotion operations should be avoided for vProxy VMs. If a vProxy VM is vMotioned mid backup or restore, it may cause unexpected issues. Disable DRS on the vProxy VM.

 

Consult with your VMware administrator or support team for making these changes.

 

Article Properties

Affected Product

NetWorker

Product

NetWorker Family, NetWorker Series

Last Published Date

06 Feb 2024

Version

6

Article Type

Solution

Back to Top