Home > An Unexpected > An Unexpected Error Occurred When Cleaning Up Snapshot Volumes. Confirm

An Unexpected Error Occurred When Cleaning Up Snapshot Volumes. Confirm

Contents

Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES Services Overview Veritas does not guarantee the accuracy regarding the completeness of the translation. But first a little scenario of the problem: -ESX 4 Host -Windows 2008 R2 SP1 with shares on drive "D:" -Backup of C: has no problem what so ever -VSS errors But all to no avail. http://crearesiteweb.net/an-unexpected/an-unexpected-error-occurred-when-cleaning-up-snapshot-volumes.html

Make sure that no other application has a lock on the... Simple template. Thank You! CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical

V-79-57344-34108

Thank You! You may also refer to the English Version of this knowledge base article for up-to-date information. Create/Manage Case QUESTIONS? May 10, 2012 at 1:00 PM Anonymous said...

Veritas does not guarantee the accuracy regarding the completeness of the translation. Confirm that all snapped volumes are correctly resynchronized with the original volumes.   EVENT VIEWER: Log Name:       Application Source:            Application Error Event ID:          1000 Task Category: Application Crashing Events Level:               Sorry, we couldn't post your feedback right now, please try again later. Thanks - that was a life saver.

No Yes 29 July 2011 V-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes. V-79-57344-33967 If Dell OpenManage Server Administrator is installed on the remote server, it may interfere with the creation of the DR file. No Yes Did this article save you the trouble of contacting technical support? https://www.veritas.com/support/en_US/article.000083478 But because the snapshot hung, the service didn't get removed and somehow backupexec messed up!

No Yes Did this article save you the trouble of contacting technical support? Confirm that all snapped volumes are correctly resynchronized with the original volumes." causing advanced open file option to fail initializing which could potentially lead to job to failing with messages such The cache file extension is .vsp.   If the problem persists, and along with the error in cleaning up the snapshots volumes, remote agent is also terminating with an NDMP error, Create/Manage Case QUESTIONS?

V-79-57344-33967

more info here: http://www.symantec.com/connect/forums/backupexec-2010-bevss-provider-installs-inself Posted by $3t4*$0uj1r0 at 10:13 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: ESX, Server 2008, vmware 4 comments: Anonymous said... https://social.technet.microsoft.com/Forums/office/en-US/8ba1b5b0-1ad4-4737-aa29-bda9be141494/vss-error-an-unexpected-error-occurred-when-cleaning-up-snapshot-volumes-confirm-that-all-snapped?forum=winserver8gen Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? V-79-57344-34108 Email Address (Optional) Your feedback has been submitted successfully! December 9, 2011 at 1:23 AM Anonymous said...

It is possible that updates have been made to the original version after this document was translated and published. have a peek at these guys No Yes Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z You may also refer to the English Version of this knowledge base article for up-to-date information. This can happen when some other application i.e.

Sorry, we couldn't post your feedback right now, please try again later. The cache file is created in a hidden folder named Backup Exec AOFO Store in the root of the selected volume. Solution Delete all "servername - date - time" files/folders in the C:\Program Files\Symantec\Backup Exec\Data directory.     Terms of use for this information are found in Legal Notices.

Related Articles check over here Cannot backup directory D:\HOMEDIRS\BLA\Desktop and its subdirectories.

System snapshots of the volumes may need to be disabled to permanently resolve this issue. THANK YOU VERY MUCH !You saved me a more time, now its running :-)))) - Thanks . Template images by fpm.

It is possible that updates have been made to the original version after this document was translated and published.

Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Then my collegue spotted something I didn't see, for some reason we had 2 VSS providers: -Backup Exec VSS Provider -BEVSS Provider As it turns out, when making backups of whole Confirm that all snapped volumes are correctly resynchronized with the original volumes." and beremote crashes Article:000083478 Publish: Article URL:http://www.veritas.com/docs/000083478 Support / Article Sign In Remember me Forgot Password? Don't have a No Yes How can we make this article more helpful?

Email Address (Optional) Your feedback has been submitted successfully! As you can see from the title the job ended with a : V-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem When performing a backup, the following error is reported, "An unexpected error this content If VSS is configured to take scheduled system snapshots of a volume as well as using Backup Exec to backup this same volume...

Symantic support did not even pick this up on my server :) great tip! August 17, 2012 at 9:51 AM Anonymous said... But then when I went clueless, and just for the fun of it connected directly to the ESX Host instead of Vcenter, I saw a Snapshot task of the said VM Confirm that all snapped volumes are correctly resynchronized with the original volumes.An unexpected error occurred when cleaning up VERITAS Snapshot Provider (VSP) snapshots.

Check for network errors.   V-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes. CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical Therefore, to resolve the error, uninstall Dell OpenManage Server Administrator 5.2 and then perform the backup.       Terms of use for this information are found in Legal Notices.

Use the virus scanner's exclusion list to exclude the VSP cache file and its folder (see the Related Documents section of this TechNote for more information).

No Yes How can we make this article more helpful? JJ December 7, 2012 at 10:14 AM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Labels 3CX (3) ActiveSync (1) Android (2) Backup (1) BES (4) and another : V-79-57344-65033 - Directory not found. a virus scanner does not relinquish control of these volumes or files.  Solution For more information about backups using either the Microsoft Volume Shadow Copy Service (VSS) or VERITAS Storage Foundation

Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem   GRT and non-GRT enabled backup of local drive fails with the warning below. The You made my day!Thank you very much for this simple, but very helpful thread!I´ve lost almoust 4 days to work on this problem, now it´s is solved!:)Not even the Symantec Support This can be done: (WS 2003) Right-clicking on any local volume, 'Properties' , 'Shadow Copies' Tab and disabling all system snapshots (WS 2008) Right-clicking on any local volume and then 'configure Shadow Copies...' and Last week I had another interesting issue with backup exec.

Cause For backups using the Advanced Open File option, the error occurs because AOFO cannot delete the virtual volume and/or the cache file during cleanup. Now to solve this: There is a script that get's called after a VM Backup Job ( Post-Thawte-script.bat) located in "c:\windows" Run this script manually and reboot, this should fix the Confirm that all snapped volumes are correctly resynchronized with the original volumes. When checking out the VCenter , nothing unusual!