Problem description
Phoenix VMware Restore fails with Error VMWARE_VDDK1. Phoenix logs shows the VDDK error[13] You do not have access rights to this file.
Cause
DNS Name Resolution
Traceback
Phoenix Log location: PhoenixLogs-Job<jobid>\<backupset>\PhoenixJob<jobid>\Phoenix.<timestamp>
[2023-02-07 13:20:51,280] [ERROR] VDDK error[13] You do not have access rights to this file. [2023-02-07 13:20:51,281] [ERROR] Error <class 'inSyncLib.inSyncError.SyncError'>:You do not have access rights to one or more vmdk files of the VM. (#100050001 : 13) (Error Code : VMWARE_VDDK1). Traceback -Traceback (most recent call last): File "agents/vmware/vixDiskLibOCManager.py", line 117, in handle_oc_work File "agents/vmware/vixDiskLibHelper/vddk_lib.py", line 141, in open_disk File "agents/vmware/vixDiskLibHelper/vddk_lib.py", line 243, in __raise_vddk_error SyncError: You do not have access rights to one or more vmdk files of the VM. (#100050001 : 13) (Error Code : VMWARE_VDDK1)
VDDK Log location: PhoenixLogs-Job<jobid>\<backupset>\PhoenixJob<jobid>\VDDK.ZIP
2023-02-07T13:20:51.236-05:00| vthread-7| I125: 2023-02-07T13:20:51.236-05:00 warning -[7FD1F289F700] [Originator@6876 sub=Libs] [NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error: Host address lookup for server Test1.Druva.com failed: Name or service not known 2023-02-07T13:20:51.238-05:00| vthread-7| I125: 2023-02-07T13:20:51.238-05:00 error -[7FD1F289F700] [Originator@6876 sub=transport] Mounting VM vm-374 using transport hotadd failed : Could not connect to ESX host Test1.Druva.com: Host address lookup for server Test1.Druva.com failed: Name or service not known. [Originator@6876 sub=transport] Cannot use mode hotadd to access [DR_VM_DataStore_DP0] DruvaTestVMRestore/DruvaTestVMRestore_1.vmdk: Cannot mount using this method. (Mounting VM vm-374 using transport hotadd failed : Could not connect to ESX host Test1.Druva.com: Host address lookup for server Test1.Druva.com failed: Name or service not known.) 2023-02-07T13:20:51.258-05:00| vthread-7| I125: NBD_ClientOpen: attempting to create connection to vpxa-nfcssl://[DR_VM_DataStore_DP0] DruvaTestVMRestore/DruvaTestVMRestore_1.vmdk@Test1.Druva.com:902 2023-02-07T13:20:51.258-05:00| vthread-7| I125: CnxAuthdConnect: Returning false because CnxAuthdConnectTCP failed 2023-02-07T13:20:51.258-05:00| vthread-7| I125: CnxConnectAuthd: Returning false because CnxAuthdConnect failed 2023-02-07T13:20:51.258-05:00| vthread-7| I125: Cnx_Connect: Returning false because CnxConnectAuthd failed 2023-02-07T13:20:51.258-05:00| vthread-7| I125: Cnx_Connect: Error message: Host address lookup for server Test1.Druva.com failed: Name or service not known 2023-02-07T13:20:51.258-05:00| vthread-7| W115: [NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error: Host address lookup for server Test1.Druva.com failed: Name or service not known
Resolution
If you are experiencing DNS resolution issues in Druva Phoenix, follow these steps to troubleshoot and resolve the problem:
Ping ESX Host Server:
Verify if you can successfully ping the ESX Host server from the backup proxy. This step helps ensure proper connectivity between the two.
Forward/Reverse Lookup Name Resolution:
Check if the forward and reverse lookup name resolution is functioning correctly from the VMware Backup Proxy to the ESX host. This ensures that the DNS is correctly resolving the hostnames and IP addresses.
Port 902 Verification:
Confirm whether port 902 is open between the VMware Backup Proxy and the ESX host. This port is essential for communication between the backup proxy and the ESX host. Ensure that it is not blocked by any firewalls or network configurations.
Check resolv.conf and ensure DNS entry is correct:
Locate the resolv.conf file. The path for this file is typically /etc/resolv.conf on Linux
Open the file using a text editor.
Verify that the DNS entry in the resolv.conf file is correct, pointing to a valid DNS server.
If necessary, modify the resolv.conf file and update the DNS entry to the correct server.
Create host file entries of ESX Server on VMware Backup Proxy:
Locate the host file on the VMware Backup Proxy machine. The path for the host file is typically /etc/hosts on Linux
Open the file using a text editor.
Add an entry for the ESX Server in the host file, specifying the IP address and hostname of the ESX Server.
Save the changes to the host file.
Network Configuration:
If the above steps do not resolve the DNS resolution issue, consider changing the network configuration. Review the network settings on the backup proxy and ESX host to ensure they are correctly configured and aligned with the requirements of Druva Phoenix.
Verification
Create ESX host entry in VMware Backup Proxy host file.
Path:
/etc/hosts