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

An Unexpected Error Occurred When Cleaning Up Snapshot Volumes

Contents

On the HP Array config utility? 0 Serrano OP Jaydeep (Symantec) Oct 25, 2012 at 1:42 UTC Brand Representative for Symantec Oh, if it is only an Exchange Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? I have experienced that this might be really helpful when it comes to the real thing - 'Restore'. Log onto the Backup Exec Central Administration Server. weblink

BackupV-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes. Also, please reboot the server once and run the command. There error is generated on this server. But all to no avail. https://www.veritas.com/support/en_US/article.TECH38338

An Unexpected Error Occurred When Cleaning Up Snapshot Volumes Symantec

If not, do so 0 Kudos Reply @pkh AOF was already on. Right now the job is just hanging, no bytes counting, so I'll have no other choise as to cancel the backup. This file cannot verify. THANK YOU VERY MUCH !You saved me a more time, now its running :-)))) - Thanks .

But problem still persists. VOX : Backup and Recovery : Backup Exec : V-79-57344-34108 - An unexpected error occurred wh... The only error I get in the log file is "V-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes. Hoping to get more inputs here on Spiceworks to make Backup Exec work better. 0 Serrano OP garyleung Oct 23, 2012 at 2:53 UTC Okay, event id 33808

Do you think you can write a how to to do that. An Unexpected Error Occurred When Cleaning Up Snapshot Volumes Backup Exec the system snapshot process may not relinquish control or release VSS writers. If Symantec Exec still works improperly after deleting the key (but WSB does), test to remove and reinstall Symantec Exec to see the result. http://www.veritas.com/community/fr/forums/backup-often-fails-error-v-79-57344-34108-unexpected-error-occurred-when-cleaning-snapshot-vo Confirm that all snapped volumes are correctly re-synchronized with the original volumes.”.

Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Creating your account only takes a few minutes. Join & Ask a Question Need Help in Real-Time? Confirm that all snapped volumes are correctly resynchronized with the original volumes.An unexpected error occurred when cleaning up VERITAS Snapshot Provider (VSP) snapshots.

An Unexpected Error Occurred When Cleaning Up Snapshot Volumes Backup Exec

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 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 Join Now exchange 2013 running on 2008r2 enterprise. An Unexpected Error Occurred When Cleaning Up Snapshot Volumes Symantec Simplify and automate the control of unstructured data. An Unexpected Error Has Occured In Quickbooks Privacy Policy Site Map Support Terms of Use Community Forums Veeam products and related data center technologies Skip to content Board index ‹ Products ‹ Veeam Backup & Replication ‹ Backup

Help Desk » Inventory » Monitor » Community » Home backups failing - unexpected error occurred when cleaning up snapshot volumes by Captain James T Kirk on Mar 7, 2016 at have a peek at these guys Covered by US Patent. best regards Christoph Friday, February 13, 2015 10:27 AM Reply | Quote 0 Sign in to vote Canyou run the below command? Also the performance drop looks like a direct result of disabling the write caching on disk, what were the other chages that made from the article in my previous posts. 0 V-79-57344-33967

Join the community Back I agree Powerful tools you need, all for free. Thanks, Nadav. 0 Kudos Reply Have you tried to split this VJware Level 6 Employee Accredited Certified ‎11-03-2014 02:05 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed That is a good idea. check over here Backup Exec is installed on this machine, backup is written directly to SAS tape loader.

Create/Manage Case QUESTIONS? Does anyone know what this is? © Copyright 2006-2016 Spiceworks Inc. flfb Novice Posts: 5 Liked: never Joined: Tue Dec 22, 2009 1:31 pm Full Name: Jeremy Jon Hilsen Private message Top Re: Backup Exec Snapshot cleanup issue...

One job with AOFO on for file data and the other job without AOFO for SQL ? 0 Kudos Reply « Previous 1 2 Next » Contact Privacy Policy Terms &

Thanks, Umesh.S.K Monday, February 16, 2015 9:26 AM Reply | Quote 0 Sign in to vote Hi Shaon, vssadmin list providers gave the following output: vssadmin list providers vssadmin 1.1 - Learn about the Veritas Technology Partner Program. 267 Posts 31 Solutions Trusted Advisors mikebounds Partner Trusted Advisor Accredited 51 Kudos 2297 Posts 672 Solutions Marianne Partner Trusted Advisor Accredited Certified 347 Also the D: disk is correctly configured (security etc) since it has always worked. Thanks, Umesh.S.K Friday, April 03, 2015 5:56 AM Reply | Quote Microsoft is conducting an online survey to understand your opinion of the Technet Web site.

I don't want to exclude the mentioned files because their are a core part of the server, plus as said before when I ran it manualy the backup was succesful. Thanks! 0 Kudos Reply Hi @CraigV, It's a freshly ComdaIT Level 3 ‎10-30-2014 08:02 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend BackupA selection on device \SERVERNAMEl\F: was skipped because of previous errors with the job. http://crearesiteweb.net/an-unexpected/an-unexpected-error-occurred-when-cleaning-up-snapshot-volumes-confirm.html If you are not able to fnd it, then disable the antivirus for now and then try the Exchange backup.

i've already tried all the the KB regarding codeV-79-57344-34108 and non of them seem to apply to my problem. Today I have a third day in a row of failed backup.