3 Replies Latest reply: Mar 9, 2018 7:20 AM by CLEB RSS

vProxy backup failed for VMs

mossman200

Hi

 

We have Networker 9.1.0.4 and have just deployed a new environment with only virtual servers, so all vProxy based backups. Two of the servers seem to be continually failing with the error 'Unable to backup virtual disk "Hard disk 1"' . From one of the servers, the logs show the following:

 

ERROR: [82] VDDK Error: 13: You do not have access rights to this file.

ERROR: [82] Failed to open source VMDK "[VNX02] xxxxxCCM001/xxxxxCCM001.vmdk".

ERROR: [82] "Hard disk 1": BackupVmdk: "Hard disk 1": Unable to open virtual disk "[VNX02] xxxxxCCM001/xxxxxCCM001.vmdk" in hottadd:nbd" mode.

ERROR: [82] "Hard disk 1": BackupVmdk: "Hard disk 1": Unable to open virtual disk "[VNX02] xxxxxCCM001/xxxxxCCM001.vmdk" in hotadd:nbd" mode.

ERROR: [82] "Hard disk 1": BackupVmdk: Failed backup.

ERROR: [82] Unable to backup virtual disk "Hard disk 1".

.....

 

I have checked DNS entries for all components - all present and correct. I have had firewalls checked for drops - there don't appear to be any issues. There are no mentions of port 902 (I believe a similar post found port 902 to be left out between vProxy and ESX host). I have tried both hotadd only and

 

They are the only VMs on a particular host and both fail thus I thought it might be host related but without migrating them to another host (change control required), I have not been able to validate this.

 

There seem to be very few posts here on the EMC Networker forum, or responses on Google, to this type of failure (unless I am not using the correct keywords), so I hope someone can help identify the problem please..

 

Thanks.

  • 1. Re: vProxy backup failed for VMs
    CLEB

    I was having similar issues with a few VMs. What OS are they? My issue was with XP, had to switch them to a vProxy set to NBD only.

     

    Also, do all your hosts have access to the datastores where these failing VMs reside?

  • 2. Re: vProxy backup failed for VMs
    mossman200

    So, it turns out that there is an issue with the ESX server the VMs are hosted on. We migrated the VMs on to another host and the VMs backed up perfectly.

     

    Unfortunately, the hosts have some affinity/anti-affinity rules that stop the VMs staying on another host (or ensure that they only run on the original host) and no sooner had the back ups started, ESX immediately started vMotion back to the original host. Subsequent backup attempts on the original host failed. Unfortunately, our VMware guys haven't been able to look at the reason why it would stop the backups on that host only as yet. I will update this post when it has been investigated further.

  • 3. Re: vProxy backup failed for VMs
    CLEB

    Sounds like the Datastores aren't accessible to all hosts/vProxy.