Home > An Unexpected > V-79-57344-34108

V-79-57344-34108

Contents

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 Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? 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. Veritas does not guarantee the accuracy regarding the completeness of the translation.

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 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 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 https://www.veritas.com/support/en_US/article.TECH38338

V-79-57344-34108

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.

Create/Manage Case QUESTIONS? Make sure that no other application has a lock on the...

Sorry, we couldn't post your feedback right now, please try again later. May 10, 2012 at 1:00 PM Anonymous said... When checking out the VCenter , nothing unusual! It is possible that updates have been made to the original version after this document was translated and published.

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). V-79-57344-33967 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 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 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

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 Needless to say that the directory ofcourse was available and backup ran fine like forever until then... 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. No Yes 29 July 2011 V-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes.

V-79-57344-33967

Cannot backup directory D:\HOMEDIRS\BLA\Desktop and its subdirectories. Confirm that all snapped volumes are correctly resynchronized with the original volumes. V-79-57344-34108 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 You may also refer to the English Version of this knowledge base article for up-to-date information.

Thanks - that was a life saver. It is possible that updates have been made to the original version after this document was translated and published. No Yes How can we make this article more helpful? You may also refer to the English Version of this knowledge base article for up-to-date information.

Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? 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, 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... Powered by Blogger.

If VSS is configured to take scheduled system snapshots of a volume as well as using Backup Exec to backup this same volume... This can happen when some other application i.e. Create/Manage Case QUESTIONS?

THANK YOU VERY MUCH !You saved me a more time, now its running :-)))) - Thanks .

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

Last week I had another interesting issue with backup exec. 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 Sorry, we couldn't post your feedback right now, please try again later. 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)

Thank You! 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 Confirm that all snapped volumes are correctly resynchronized with the original volumes. 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

Email Address (Optional) Your feedback has been submitted successfully! But all to no avail. Thank You! Template images by fpm.

the system snapshot process may not relinquish control or release VSS writers. Confirm that all snapped volumes are correctly resynchronized with the original volumes.An unexpected error occurred when cleaning up VERITAS Snapshot Provider (VSP) snapshots. 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. and another : V-79-57344-65033 - Directory not found.

Symantic support did not even pick this up on my server :) great tip! If Dell OpenManage Server Administrator is installed on the remote server, it may interfere with the creation of the DR file. 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 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