#1 Global Leader in Data Protection & Ransomware Recovery

VDDK error: 13 - Troubleshooting

KB ID: 2008
Product: Veeam Backup & Replication
Version: All
Published: 2015-02-19
Last Modified: 2024-03-21
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

Backup/Replication jobs fail with:

VDDK error: 13.You do not have access rights to this file

Solution

Below is a list of possible solutions to this issue sorted by what transport mode was being used when this error occurred.
Note: There are many causes for VDDK 13; this list is not intended to be all-encompassing.

Using Transport Mode: Network Mode

  • Solution 1:
    Sometimes, you may receive this error when permissions are not correctly set. To confirm, please follow the steps outlined in the following KB article to test ports, permissions, and DNS resolution
    Veeam KB1198: NFC connectivity troubleshooting steps

Using Transport Mode: Hotadd Mode

  • Solution 1:
    Veeam KB1054: Appliance Mode (Hotadd) Requirements and Troubleshooting
    VMware Tools must be installed and up-to-date on the Veeam server and any Veeam proxies
  • Solution 2:
    Veeam KB1775: Removing Stuck VMDK From the Veeam Proxy
    Stuck Hotadded Disks – Review all virtual proxies for disks attached that do not belong to the VM in question, and remove the disks not owned by this VM without deleting them from the datastore. Once deleted, consolidate snapshots on the affected VMs.
  • Solution 3:
    VMware KB1002310: Consolidating/Committing snapshots in VMware ESXi
    Orphaned Snapshots – Consolidate snapshots on affected VMs
  • Solution 4:
    Veeam Backup & Replication - Permissions for VMware vSphere Guide
    Permissions - Please configure the account leveraged to access the vCenter as an Administrator within vCenter
  • Solution 5:
    Automount – In some cases, it may be necessary to perform an automount scrub to clear any existing mount points that are no longer in the system.

    Run the following via CMD Prompt on the proxy server:
    diskpart
    automount disable
    automount scrub
    exit
    
  • Solution 6:
    Veeam Latest Product Updates
    Patching – Please ensure that all VMware and Veeam components are fully up to date.
  • Solution 7:
    In some rare instances, performing a storage vMotion has been known to resolve the issue due to a locked VM file on the datastore where the VM files reside.
  • Solution 8:
    In some rare instances, restarting the vCenter appliance or alternatively restarting the ESXi management agents (VMware KB1003490: Restarting the Management agents in ESXi) may yield positive results if all above testing does not resolve the issue.
  • Solution 9:
    Veeam Proxy has a Veeam replica with the same bios UUID within the vCenter Server. The following can be observed in 

    Job.Job_name.log:
    [time stamp] < threadID> Info VM VeeamProxy _replica(vm-100001) has the same bios uuid as proxy VeeamProxy.local in the DB
    
    Agent.Job_name.VM_name.Hotadd.Attacher.log:
    [time stamp] < threadID> vdl| [vddk] time stamp error -[07132] [Originator@6876 sub=transport] Cannot use mode hotadd to access [datastore_name] VM_name/VM_name.vmdk: Cannot mount using this method. (Mounting VM vm-101 using transport hotadd failed : Cannot access datastore for one of the disks of Virtual Machine VM_name..)
    
    The behavior is observed when a Veeam Proxy is replicated with Veeam B&R. The replication process preserves the original VM bios UUID for restore purposes. To work around the issue, set up a dedicated VM as a Veeam Proxy. Replicating Veeam Proxies is not usually necessary due to ease of deployment.

    More information: Veeam KB2159: Appliance Mode (Hotadd) isn't available if proxy VM and its replica are running under the same vCenter

Using Transport Mode: Direct SAN

More Information

Additional Troubleshooting

  • Deploy an additional standalone proxy to isolate failures to a single specified proxy
  • To isolate a specific transport mode as the point of failure, you may also test the other transport modes to ensure that connectivity is correctly established and backup jobs work as intended via the other transport mode.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.