Comprehensive data protection for all workloads

Dik
Lurker
Posts: 1
Liked: never
Joined: December xvi, 2010 two:43 pm
Total Name: Dik
Contact:

Failed to open VDDK disk - is read-only style - [true]

Hullo,
I testing veeam five.0 and we have run in to some issues.
I have VMware ESX iv.one.0

Information technology is not possible to complete reserve copying.
At that place is an error.

Bankroll up object "[datastore1_800] Win7/Win7.vmdk"
BackupDiskFull failed
Client error: Failed to open VDDK disk [[datastore1_800] Win7/Win7.vmdk] ( is read-only mode - [truthful] )
Failed to open up VMDK.
Logon endeavor with parameters [VC/ESX: [10.1.2.23];Port: 902;Login: [dik];VMX Spec: [moref=448];Snapshot mor: [448-snapshot-25];Transports: [nbd]] failed considering of the post-obit errors:

Server error: End of file

Gostev
SVP, Product Management
Posts: 29736
Liked: 5739 times
Joined: January 01, 2006 ane:01 am
Location: Baar, Switzerland
Contact:

Re: Failed to open VDDK disk - is read-only mode - [truthful]

Post by Gostev » this post

Hi Dik, welcome to our forums. Please review the forum rules on posting support problems provided when you click New Topic. Thank you.

WesleyKnox
Novice
Posts: 3
Liked: never
Joined: Apr thirteen, 2011 12:38 pm
Full Name: Wesley Knox
Contact:

Re: Failed to open up VDDK disk - is read-only way - [truthful]

Post by WesleyKnox » this post

Howdy Guys,

My name is Wesley and I have had the same bug for about a week now. I have managed to resolve my issue by enableing VSS for all backup jobs. A domain or local account needs to be local admin on the VM in gild to employ VSS. Its makes total sense ( read only style) = VM beingness on and app, data or files existence in use. Having this option enabled will freeze the guest and backup the VM's in your job. I really hope this helps out people having the same effect.

Cheers

Wesley Knox :)

spgsit5upport
Expert
Posts: 220
Liked: 16 times
Joined: May 28, 2010 10:25 am
Full Name: Seb
Contact:

Re: Failed to open VDDK disk - is read-but fashion - [true]

Postal service by spgsit5upport » this mail

VB&R 6.1 on Server 2008 R2

24-hour interval 1, full fill-in chore runs fine.
Twenty-four hours 2, incremental fill-in task runs, VM that worked fine yesterday now gives:

Mistake: Client error: Failed to open VDDK disk [[VMFS5-EQL] ZCM/ZCM_1.vmdk] ( is read-just mode - [true] ) Failed to open up VMDK. Logon attempt with parameters....

The KB http://www.veeam.com/KB1100
is of no help as this VM does NOT have IDE disks!

Seb

ZachW
Enthusiast
Posts: 68
Liked: 10 times
Joined: Aug 02, 2011 6:09 pm
Full Proper noun: Zach Weed
Contact:

Re: Failed to open VDDK deejay - is read-only mode - [truthful]

Postal service past ZachW » this mail service

If y'all are running into this fault while running a task then please open up a ticket with support to get squared abroad. This error alone does not provide plenty information as to why the job is declining. The KB that you lot are referring to ( while information technology does comprise the "failed to open vddk disk" string ) is referring to a specific error. Equally seen towards the terminate of the "problem" row it makes reference to checking the logs for a line along the lines of "Cannot utilise hotadd to transport to mount Virtual Machines with non-SCSI disks" which is referring to trying to run a chore using Virtual Appliance transport mode against a VM containing IDE disks. So, this KB is helpful if someone is throwing the "failed to open up vddk disk" fault and they happen to see that line inside their logs, but I presume this is non the case for you lot. This is just a generic mistake beingness thrown stating that we cannot open the disk for some reason. Then, go ahead and open up upwards a ticket with back up and so we can try and observe in the logs what other issue may exist causing this error to be thrown.

spgsit5upport
Expert
Posts: 220
Liked: 16 times
Joined: May 28, 2010 10:25 am
Full Proper name: Seb
Contact:
kte
Skillful
Posts: 179
Liked: 8 times
Joined: Jul 02, 2013 7:48 pm
Total Name: Koen Teugels
Contact:

[MERGED] Error: Client error: Failed to open VDDK deejay [[vmf

Mail service by kte » this mail

ix/15/2013 11:55:16 PM :: Processing 'xxx1' Fault: Client error: Failed to open up VDDK disk [[VMFS_LUN04] xxx/xxx_17.vmdk] ( is read-simply mode - [truthful] )
Failed to open VMDK.
Logon try with parameters [VC/ESX: [vcenter];Port: 443;Login: [****];VMX Spec: [moref=vm-748];Snapshot mor: [snapshot-1115];Transports: [san];Read Only: [truthful]] failed because of the following errors:
Failed to open VMDK.
Logon attempt with parameters [VC/ESX: [vcenter];Port: 443;Login: [****];VMX Spec: [mor

case 00446547

kte
Good
Posts: 179
Liked: 8 times
Joined: Jul 02, 2013 7:48 pm
Full Name: Koen Teugels
Contact:

Re: Failed to open up VDDK deejay - is read-merely way - [true]

Post by kte » 1 person likes this post

It seems to working now I added addition ram and CPU on my vCenter and some esx host could communicate anymore with the vcenter so I restarted there management agents

DaFresh
Enthusiast
Posts: 64
Liked: 1 time
Joined: Aug 30, 2011 9:31 pm
Full Name: Cedric Lemarchand
Contact:

Re: Failed to open up VDDK deejay - is read-only style - [truthful]

Postal service by DaFresh » 1 person likes this mail

How-do-you-do all,

I have had this issue lot of times ... specifically on large VM with vhd larger than 1To.
It took me i month to find that turning up colossal frame on the storage side resolve the issue, at least for me. I think that my hardware was pushed to the limit because of the IO at the iSCSI layer, resulting in some strange behaviours ...
And so it seems that sometimes this issue could be caused by a misconfiguration of the storage.

Hope this could help.

EBoucq
Service Provider
Posts: 258
Liked: 16 times
Joined: Jan 21, 2011 10:10 am
Full Name: Eric Boucq
Contact:

[MERGED] Replication to NFS datastore (NAS)

Mail service by EBoucq » this post

Hi,

I have to run replications of a VM (on a SAN) to a NFS datastore on a NAS.
I use Veeam V7.
After a few successful replication, I started to go errors similar mentionnig "failed to open up vddk deejay" and "read-only mode"

Could it be linked to the proxy transport style configuration that'south been set up to "Virtual Appliance" ? What would be the best selection for that kind of storage (NAS) ?

Thanks !

Shestakov
Expert
Posts: 7328
Liked: 776 times
Joined: May 21, 2014 11:03 am
Full Name: Nikita Shestakov
Location: Prague
Contact:

Re: Failed to open up VDDK deejay - is read-but mode - [true]

Mail service by Shestakov » this post

Hello Eric,
What is the build number of VBRv7 version you are using?
You are correct, 1 of possible reasons is that Hot Add proxy didn't unmount disks failed server. Another gauge is that in that location is a VM with unsupported disks blazon like IDE virtual disks.
Please review the topic and this article.
Thanks.

EBoucq
Service Provider
Posts: 258
Liked: 16 times
Joined: Jan 21, 2011 10:10 am
Full Name: Eric Boucq
Contact:

Re: Failed to open VDDK disk - is read-only mode - [true]

Postal service by EBoucq » this mail

Hi Nikita,

I'grand using VBR v 7.0.0.871.
If the VM source is on a SAN and the replica on a NAS (NFS), what transport fashion would you recommend
Cheers !

Shestakov
Expert
Posts: 7328
Liked: 776 times
Joined: May 21, 2014 11:03 am
Full Name: Nikita Shestakov
Location: Prague
Contact:

Re: Failed to open VDDK disk - is read-only mode - [true]

Mail by Shestakov » this post

EBoucq wrote:I'1000 using VBR v seven.0.0.871.

Bully, that`s the last release version of v7 (patch 4). Is there a reason why yous are not updating to v8?

EBoucq wrote:If the VM source is on a SAN and the replica on a NAS (NFS), what transport way would you lot recommend

To streamline the replication procedure, you tin can deploy a fill-in proxy on a VM. The virtual backup proxy must be registered on an ESX(i) host that has a direct connection to the target datastore. In this case, the fill-in proxy will be able to use the Virtual Appliance ship way for writing replica information to target.
What ship way for replication VBR is using at present? Do you see the [hotadd] or [nbd] tag side by side to the target proxy server name in the VM processing log?

This topic contains more relevant info. Delight accept a look.
Thanks.

EBoucq
Service Provider
Posts: 258
Liked: 16 times
Joined: Jan 21, 2011 10:10 am
Total Proper noun: Eric Boucq
Contact:

Re: Failed to open VDDK deejay - is read-only mode - [true]

Mail service past EBoucq » this post

Hi Nikita,

This is how the replication is set up:
Source proxy: send mode --> Virtual appliance --> [hotadd] appears in the log
target proxy: transport style --> Virtual appliance --> [hotadd] appears in the log
Shouldn't I choose an other option than Virtual appliance if I don't desire hotadd

Source VM is a Windows Vista 64-bit with LSI Logic SAS controller.

Shestakov
Skilful
Posts: 7328
Liked: 776 times
Joined: May 21, 2014 xi:03 am
Total Name: Nikita Shestakov
Location: Prague
Contact:

Re: Failed to open up VDDK disk - is read-only mode - [true]

Postal service past Shestakov » this post

Thanks for the answer.
If you don`t want to employ hot-add together, you can switch to the Network mode.
You can instruct VBR to switch to the Network transport mode and transfer VM information over the LAN if the primary send mode — Direct SAN Access or Virtual Apparatus — becomes inaccessible. This option is enabled by default to ensure that jobs and tasks can exist completed successfully in any situation.
Thank you.

adrianoses
Lurker
Posts: 1
Liked: never
Joined: Oct 08, 2019 iii:twenty pm
Full Name: Adrián Oses
Contact:

Re: Failed to open VDDK disk - is read-only manner - [true]

Post by adrianoses » this post

Hi Guys,

My proper name is Adrian, and I accept this error trying to do a Quick Migration with Veeam BackUp and Replication Update four:

8/10/2019 xi:25:27 :: Copying VM files Fault: Failed to open VDDK disk [[datastore1] VM HADES/hades_1-s001.vmdk] ( is read-simply mode - [truthful] )
Logon attempt with parameters [VC/ESX: [192.168.1.3];Port: 902;Login: [root];VMX Spec: [moref=xxx];Snapshot mor: [30-snapshot-one];Transports: [nbd];Read Simply: [true]] failed considering of the following errors:
Failed to replicate content of the deejay [vddk://<vddkConnSpec><viConn name="192.168.1.three" authdPort="902" vicPort="443" /><vmxPath vmRef="thirty" datacenterRef="ha-datacenter" datacenterIn

The source is ESXI 5.5 and the destination is ESXI 6.vii

Thanks!!!

wishr
Veeam Software
Posts: 2958
Liked: 422 times
Joined: Aug 07, 2018 3:11 pm
Total Proper name: Fedor Maslov
Contact:

Re: Failed to open up VDDK disk - is read-only way - [true]

Mail by wishr » this mail

How-do-you-do Adrian,

Welcome to Veeam Community Forums!

If none of the aforementioned solutions aid, please attain out to our technical back up squad directly and post your back up instance ID hither once y'all have it. This procedure is in identify to make certain you lot get a solution ASAP and customs members benefit from such posts.

Thanks

Matej.Sur
Novice
Posts: 6
Liked: never
Joined: January 13, 2016 12:33 pm
Full Proper noun: Matej Sur
Contact:

Re: Failed to open up VDDK disk - is read-but way - [truthful]

Post past Matej.Sur » this post

Hi everybody! I accept similar problem. Backups often fail with error:

Failed to open up VDDK deejay [xxx.vmdk] ( is read-only style - [true] )
Logon attempt with parameters [VC/ESX: [xxx];Port: 443;Login: [veeam@vsphere.local];VMX Spec: [moref=vm-23766];Snapshot mor: [snapshot-26772];Transports: [nbd];Read Only: [true]] failed because of the following errors:
Failed to open deejay for read.
Failed to upload disk.
Agent failed to process method {DataTransfer.SyncDisk}.

and in log is this additional info: VDDK error: 30028 (Network operation timed out). Value: 0x000000000000754c

I have tried to use different transport modes, and proxies but no divergence. Originally I suspected network connexion simply there is no errors or any problems. Backup jobs sometime works fine, quondam some jobs are successful at retry and sometime jobs fail. Any advice or idea? Thank you a lot in advance!

Who is online

Users browsing this forum: Baidu [Spider], Google [Bot] and 44 guests