1-800-691-1991 | 9am - 8pm ET
EN

Replication job to VMware Virtual Volumes (VVols) fails with VDDK error: 7 (A file access error occurred on the host or guest operating system)

KB ID: 2022
Product: Veeam Backup & Replication
Version: 8.x, 9.x
Published: 2017-01-12
Last Modified: 2020-08-13

Challenge

Replication job to a VVOL target will fail with the error below:

User-added image

Task.<VM name>.vm-<vm-ref> will contain following error:
[TIMESTAMP] <21> Info             [AP] (5e06) disconnecting
[TIMESTAMP] <55> Error                  [AP] (5e06) error: VDDK error: 7 (A file access error occurred on the host or guest operating system). Value: 0x0000000000000007
[TIMESTAMP] <55> Error          Failed to write to a virtual disk

 

Cause

Due to a change in VMware vSphere 6.0 Update 1, replication to VVol datastores is no longer possible with Veeam. This article will be updated in case more recent VMware vSphere updates fix this newly introduced issue.

Here is an official statement from VMware VDDK release notes:
Avoid creating snapshots for restore on VVol datastores. Due to Virtual Volume (VVol) implementation in the vSphere 6.0 release, VMware recommends against creating a snapshot (then reverting and deleting it) when restoring files on a VVol datastore. This is because writing to a non-leaf disk (such as a snapshot backing file) is considered a layering violation and throws an error on many VVol storage devices. Writing to the leaf disk of the snapshot is not a layering violation. The restore snapshot remains mandatory for SAN transport, which is not supported on VVol datastores anyway.

Solution

Replication job to VMware Virtual Volumes (VVols) is no longer supported.
KB ID: 2022
Product: Veeam Backup & Replication
Version: 8.x, 9.x
Published: 2017-01-12
Last Modified: 2020-08-13

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Your report was sent to the responsible team. Our representative will contact you by email you provided.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
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

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please try again later.