I'm not at the latest patch within 6. You may also refer to the English Version of this knowledge base article for up-to-date information. If you require immediate assistance, please call us and we would be happy to assist. Reason: An error occurred while saving the snapshot: Failed to quiesce the virtual machine. Reason: An error occurred while saving the snapshot: Failed to quiesce the virtual machine. Error Message Virtual machine quiescing fails, causing the snapshot job to fail with error status code 156.
You will lose the ability to restore files and folders from previous volume shadow copy snapshots. Now try scheduling the problematic backup job and check whether the reported issue is fixed and update us. Do you have any more ideas? Backup should work without a reboot, too — but it is recommended… We use Veritas NetBackup, upto and including version 7. I guess that since VeeamZip is new, Gostev statment migt not be valid for VeeamZip, and that in fact VeaamZip relays on vmtools vss? The disks consolidate just fine, and go back to green status, and work fine, until I next try to back them up. And there is no doubt that he has it in for Veeam. Non-Windows guests are not affected and are backed up whether running or not. However, I checked with Veritas if they considered this to be a safe workaround… and they do not.
Either way now using application aware which didn't make a difference either. The error message was: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Please and we'll pull it back in. I am working on the second one presently, and here is what I've found. The option for application aware processing is on the Guest Processing area. Additionally, I migrated the virtual machine to another host, removed it from the inventory and added it back. This morning during troubleshooting, I went ahead and deleted all the Windows Volume Shadow Copies which are internal and inside of the Virtual Machine itself.
Stay tuned to your comments. Hi dhg, we have also the same issue with vmware esx 5. The system restored from such snapshot will boot up and act like it was forcibly powered off. This causes the snapshot job to fail. So getting an error on my new File server 2012R2 when attempting to back it up.
Additional info: -------------------- Error code: 13 Module: 149 LineInfo: d1ab7fa1e56eca4e Fields: Message: Failed to perform the requested operation. There were 3 servers that were having troubles. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc. No problem, it backed up fine. Microsoft Software Shadow Copy Provider 2. Hehe, yea that has been a hot potato for a while! Caution: Symantec does not recommend that you disable quiesce. The servers that I'm having trouble with are all Windows 2012 R2 servers.
Found four related articles - none resolved the issue. When I pressed the right mouse button on My Computer or any other directory, the Symantec Antivirus installer starts with a repair job. I will validate the error directly on the machine to validate I will validate the backup of the execution right now and the results to know. Category VirtualServer Type Integer Windows Packages Default,Virtual Server Agent Min Value 0 Max Value 1 Default Value 0 Supported Version 10. Workaround There is a workaround for this, where you do not quiesce the virtual machine when you try to back it up, and therefore end up with a crash consistent backup, which could be good for you to at least get a backup! Virtual machines created in vSphere 4. All I know is when we did the things above, we stopped having the issues.
Backup should work without a reboot, too — but it is recommended… We use Veritas NetBackup, upto and including version 7. Its not an importatant backup at all, so i might just forget about this whole issue. A vssadmin list writers command returned no errors. In this case, you must perform your own checks for data consistency in the backup data. We had a session with our Commvault parnter today but they need further investigation and created extra logging. If you want to minimize the impact of snapshot commit operation, then integration with storage snapshots will definitely help here. Just to make it clear, the backup of the veeam production server works fine.
Some customers are not able or do not wish to perform this in depth troubleshooting. If you make a post and then can't find it, it might have been snatched away. So, could you please help me on this issue? Veritas does not guarantee the accuracy regarding the completeness of the translation. Reason: An error occurred while saving the snapshot: Failed to quiesce the virtual machine. Edge Out The Competition for your dream job with proven skills and certifications. Please advise how to fix this issue as we need a valid backup data by end on this weekend. Since we disabled Quiesce this has not occurred once.