https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyMDA1IiwiaGFzaCI6ImNkNGIxY2M0LTg0OTItNDJlNC05ZDQ2LWM4MzJlNzk2ZmM3NiJ9
1-800-691-1991 | 9am - 8pm ET
EN

Direct SAN Restore for thick disk VDDK error: One of the parameters supplied is invalid

Challenge

When performing an Entire VM Restore,  VM Hard Disk Restore, or initial run of a replication job using Direct-SAN transport mode the task fails with the error:
 
Unable to execute write operation using advanced transport, failing over to network mode...
ERR |VDDK error: 16000 (One of the parameters supplied is invalid)

(The error code may vary, but the informational message will be the same)

Cause

This error occurs when the LUNs presented to the Backup Proxy for DirectSAN access are read-only.

Solution

To confirm that these LUNs are presented in Read-only access, please refer to your SAN configuration interface.
If the disk is presented as Read-only, you must either connect the volume with write access or use a different transport mode.

More information

Direct SAN restores are for Thick Disks only and can be used with the following restore types:

Entire VM restore
VM hard disk restore
Initial Replication of a Replica

 
KB ID:
2005
Product:
Veeam Backup & Replication
Version:
8.x
Published:
2015-02-10
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

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

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later