Warning backing-up - VMware_VDDK: The file is write-protected
On 2 out of 12 vm's I get mulitple warnings like the one below. How can I find out which file is the problem, and what can be done to fix this warning?
18 Warning 11/14/11 5:00:41 AM VMware_VDDK: The file is write-protected
Additional info:
--------------------
Error code: 208
Module: 83
LineInfo: c61573f663f5d769
Fields: code : 11
Message: VMware_VDDK: The file is write-protected
Thanks
James P
Hi, Anton
I also have this type of signaling (8 / 12 all up) but then I saw that in the tests properly restore the VM, but it is annoying to justify it to the customer.
I attach the complete log
VMware_VDDK: Unknown error
Additional Information:
--------------------
Error Code: 208
Form: 83
LineInfo: c61573f663f5d764
Fields: code: 1
Message: VMware_VDDK: Unknown error
thanks
Luca Paolantonio
Also have the very same error for a couple of VM's
i have the same. but i changed the backup location to another cifs share and hardware and it worked.
but still the old cifs share is not working even with deleting all files
Does this problem only occur when the destination is a CIFS share?
I just re-ran a backup that failed last night and it failed again with the similar error.
Task 'Backup ISL Windows Machines' failed: 'Failed to create the backup.
Additional info:
--------------------
Error code: 3
Module: 435
LineInfo: 555b5abba0950053
Fields:
Message: Failed to create the backup.
--------------------
Error code: 32786
Module: 114
LineInfo: 28314c961de7d2fd
Fields:
Message: Failed to prepare for backing up.
--------------------
Error code: 353
Module: 149
LineInfo: a71592046cb2c5c6
Fields:
Message: Failed to back up the group.
--------------------
Error code: 2
Module: 218
LineInfo: 600f7166ce397de5
Fields:
Message: Error occurred while running the backup and recovery engine.
--------------------
Error code: 208
Module: 83
LineInfo: c61573f663f5d769
Fields: code : 11
Message: VMware_VDDK: The file is write-protected
--------------------'.
No, I don't think so. I just reinstalled vmProtect to the same server that contains the backup-folder and I get the same error anyway, now using a local folder.
I get the error in the begining of the backup process. It seems like vmProtect performs some kind of check before it starts backing up VM's and it's during this check the errors apears.
Can someone at Acronis please tell us what this error means and how we resolv it.
Does this problem only occur when the destination is a CIFS share?
No. I configured an iSCSI disk instead of a shared folder on the NAS and the result is the same.
@Administrator
But e-mail notifications do not work?
Hello all,
Thank you for your comments. Let me please assist you with these issues.
James, after studying the logs it appears to be a warning message caused by nonstandard hard drives in your virtual machines. This could occur if the disk hasn't been initialized for example. The problem here is that vmProtect erroneously sends write requests to the disk under these certain circumstances and this causes the VDDK warnings since it’s forbidden to apply any changes to the backed up disks. This warning can be safely ignored and we have corrected this issue already and the fix will be available in the next official update.
Luca, I would recommend to install the virtual appliance to get rid of these warning messages. There also appears to be a network issue, the logs returned this error: VMware_VDDK: [NFC ERROR] NfcFssrvrRecv: failed with code = 9
There were also several certificate errors which can be fixed by applying this solution.
Christian and Jan, could you get back to me with full operation logs so that I can analyzed them. Even though the error messages appear to be similar, we need the exact errors to get to the bottom of these issues.
Please let me know if you have additional questions.
Thank you.
Well, here is some error log that I got today...
Mostly like this one:
VMware_VDDK: The file is write-protected Additional info:
--------------------
Error code: 208
Module: 83
LineInfo: c61573f663f5d769
Fields: code : 11
Message: VMware_VDDK: The file is write-protected
--------------------
And this one:
Task 'Telematics vmProtect daily backup' failed: 'Failed to create the backup.
Additional info:
--------------------
Error code: 3
Module: 435
LineInfo: 555b5abba0950053
Fields:
Message: Failed to create the backup.
--------------------
Error code: 32786
Module: 114
LineInfo: 28314c961de7d2fd
Fields:
Message: Failed to prepare for backing up.
--------------------
Error code: 353
Module: 149
LineInfo: a71592046cb2c5c6
Fields:
Message: Failed to back up the group.
--------------------
Error code: 2
Module: 218
LineInfo: 600f7166ce397de5
Fields:
Message: Error occurred while running the backup and recovery engine.
--------------------
Error code: 1
Module: 7
LineInfo: a5695862aaf8e6b9
Fields:
Message: Failed to perform the operation with archive 'avfs:/smb?//192.168.140.190/vmprotect/Telematics%20vmProtect%20daily_2011_11_16_21_07_26_928D24.TIB'. Error: 'Internal error: number of backed up sectors differs from counted'.
I think it's two different issues here..
Luca, I would recommend to install the virtual appliance to get rid of these warning messages. There also appears to be a network issue, the logs returned this error: VMware_VDDK: [NFC ERROR] NfcFssrvrRecv: failed with code = 9
There were also several certificate errors which can be fixed by applying this solution.
Hello Anton,
perfect, I have installed and reconfigured the backup under "virtual appliances" and now it works without returning any error.
It was also resolved that's what I would have asked for an explanation:
Unable to retrieve the list of directories.
Additional Information:
--------------------
Error code: 4
Form: 424
LineInfo: 10f02767c7826ac8
fields:
Message: Unable to retrieve the list of directories.
--------------------
Error Code: 1
Module: 4
LineInfo: bd01591c540a12f4
Fields: IsReturnCode: 1
Message: Error reading file.
--------------------
Error Code: 32
Module: 4
LineInfo: bd01591c540a111b
Fields: Provider: Microsoft Windows Network, code: 6118
Message: The list of servers for this workgroup is not currently available.
--------------------
Thanks again
Luca
Hello Christian and Luca,
Thank you for the update.
Christian, you are absolutely right, these are indeed two different issues. The problem with the error message - number of backed up sectors differs from counted can be fixed by the following KB article. For the other issue, we will need to take a look at full operation logs.
Luca, this error message appears if the Computer Browser service is not started on your computer. You can enable it like this:
- Go to Start > Run, then type in Services.msc and click ok.
- Locate Computer Browser service, right click and select Properties.
- Change startup type to Automatic and start the service.
Please let me know if you have additional questions.
Thank you.
The "number of backed up sectors..." bug seems to only (at least in my environement) happen with Windows Server 2008R2 VM with standard NTFS filesystem, nolthing special at all. VMware tools are installed. The KB you refered to is not an accepted solution since the workaround is to disable CBT. CBT is the main reason why people choose this product in the first place. The KB says that this is already fixed and will be available in the next public release of vmProtect. I heard from another of your support staff that this will be avaiable in two months. You should therefore consider releasing a hotfix instead ASAP. I don't think I'm alone saying that there is no way I can use this product with CBT disabled, performing daily backups of 70+ VM's according to the space and time consumption.
Also, the VM Version is 8
I also have the same issue while backuping my vCenter Server Appliance:
VMware_VDDK: The file is write-protected
Additional info:
--------------------
Error code: 208
Module: 83
LineInfo: c61573f663f5d769
Fields: code : 11
Message: VMware_VDDK: The file is write-protected
Please fix this bug.
Hi,
We have the same issue when trying to backup Vcenter with Error code: 208 VMware_VDDK: The file is write-protected. We tried it with two environments ; one where VMProtect is installed as a server appliance and the other as a Windows service. Both backup jobs returns the same Warning. Please help how to fix this issue.
Thanks
Same problem here (VMware_VDDK: The file is write-protected).
Sometimes by recreating the backup job the problem goes away, but after a few days it returns. Sometimes rebooting the acronis virtual appliance helps.
We also often have the 'number of backed up sectors differs from counted' problem, that was solved by disabling CBT, however our file systems are completely standard NTFS, and i agree with Christian that this is not a solution because CBT backup is one of the main reason why people buy this product.
We see this behaviour on three different ESXI servers (HP machines with SAS datastores. We are directing our backups to SMB fileshares on QNAP NAS devices.
We also have seen that when the backups start to fail, there are often snapshots that are not cleaned up on the virtual machines. Under the acronis appliance, there are sometimes 15+ virtual harddisks linked to the appliance...
We also have had a few cases where the virtual appliance simply hangs completely and the web interface is not accessible anymore.
Our experiences with VMProtect are up to now not positive. In our setups, it does not work reliably. I wonder when there will be an update for version 6 that addresses these issues. 6 months without hotfixes is a very long time, especially when our customers pay for maintenance....
Piet, I recognize every single problem that you mention. We have a similair environment as you with three ESX servers and Qnap NAS as backup storage (I tried other as well).
There is a unofficial build that addreses the "number of backed up sectors..."-bug but believe me - there is a lot more bugs that makes this product unreliable.You probably have to open a support case to get the fix or just PM me and I'll send it to you.
But as I sad you probaly won't be able to perform a safe backup anyway. At the moment I run vmProtect 7 Beta wich I was told includes the above mention fix and a lot of other fixes but it still suffers from some major bugs. The problem you mention about the webinterface that becomes unaccesible is still in the vmp7. So is randomly interupted backups without any useful error messages. Also, browsing recovery points is not possible during a running backup in vmp7.
The best advice I can give you is to break down the backup jobs so that they at most holds 2-3 VM's each. This is absolutely not a perfect setup and it won't give you a 100% succesful backup history, just some peace during Christmas.
Actually I have no hope left for this product. I've messed around with it for over a month now and I can't get a reliable backup. Acronis won't accept a refund either.
Merry Christmas!
This is the latest error message I got in wmp7 (apperars on the first incremental backup after a full)
--------------------
Error code: 16
Module: 161
LineInfo: ca365a28db17197d
Fields:
Message: Archive with the same name already exists.
--------------------'.
Haha! what a joke...
I wanted to let you know that the latest VMProtect 6.0 build, available since end december 2011 seems to resolve all of our problems. (above problem, and the CBT problems)
cross my fingers...
Piet
Hi All,
Can confirm same issues mentioned by Piet @Sat, 2011-12-24 11:35 still exist even with build 3145, most annoying part is that sometimes job will finish ok and other times same job will fail leaving snapshot behind which may give you problems if this is going unnoticed.