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

An Unexpected Error Occurred When Cleaning Up Snapshot Volumes. Confirm

Contents

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:               Veritas does not guarantee the accuracy regarding the completeness of the translation. 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 29 July 2011 V-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes. check over here

May 10, 2012 at 1:00 PM Anonymous said... Veritas does not guarantee the accuracy regarding the completeness of the translation. It is possible that updates have been made to the original version after this document was translated and published. Thank You! https://www.veritas.com/support/en_US/article.TECH38338

V-79-57344-34108

No Yes Did this article save you the trouble of contacting technical support? 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 December 9, 2011 at 1:23 AM Anonymous said... THANK YOU VERY MUCH !You saved me a more time, now its running :-)))) - Thanks .

No Yes Did this article save you the trouble of contacting technical support? 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. This can happen when some other application i.e. Thanks - that was a life saver.

Last week I had another interesting issue with backup exec. But because the snapshot hung, the service didn't get removed and somehow backupexec messed up! 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 my response If VSS is configured to take scheduled system snapshots of a volume as well as using Backup Exec to backup this same volume...

None of the files or subdirectories contained within will be backed up.   Error Message 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 But all to no avail. 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,

V-79-57344-33967

When checking out the VCenter , nothing unusual! System snapshots of the volumes may need to be disabled to permanently resolve this issue. V-79-57344-34108 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 the system snapshot process may not relinquish control or release VSS writers.

If Dell OpenManage Server Administrator is installed on the remote server, it may interfere with the creation of the DR file. check my blog Confirm that all snapped volumes are correctly resynchronized with the original volumes.An unexpected error occurred when cleaning up VERITAS Snapshot Provider (VSP) snapshots. August 17, 2012 at 9:51 AM Anonymous said... The cache file is created in a hidden folder named Backup Exec AOFO Store in the root of the selected volume.

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) 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.

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 this content 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

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 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 Create/Manage Case QUESTIONS?

Create/Manage Case QUESTIONS?

Confirm that all snapped volumes are correctly resynchronized with the original volumes. Simple template. Symantic support did not even pick this up on my server :) great tip! 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).

You may also refer to the English Version of this knowledge base article for up-to-date information. Thank You! 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 have a peek at these guys Needless to say that the directory ofcourse was available and backup ran fine like forever until then...

You may also refer to the English Version of this knowledge base article for up-to-date information. 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... Confirm that all snapped volumes are correctly re-synchronized with the original volumes." Article:000029170 Publish: Article URL:http://www.veritas.com/docs/000029170 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create 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

Sorry, we couldn't post your feedback right now, please try again later. Cannot backup directory D:\HOMEDIRS\BLA\Desktop and its subdirectories. Email Address (Optional) Your feedback has been submitted successfully! No Yes How can we make this article more helpful?

Confirm that all snapped volumes are correctly resynchronized with the original volumes. 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 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 Make sure that no other application has a lock on the...

Template images by fpm.