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

An Unexpected Error Has Occurred When Cleaning Up Snapshot Volumes

Monday, February 16, 2015 8:49 AM Reply | Quote Moderator 0 Sign in to vote Hi, Yes,I have run this on our windows 2012 R2 and found no issues. Join Now Hey Spiceheads, Taking on from Matt’s last post "Who can I talk to with technical questions about Backup Exec?" I am Jaydeep Sathe from the Symantec Backup Exec Support 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 Windows The short: My company just acquired another company of 5 individuals, 20 VMs on Hyper-V, and a sizable infrastructure. have a peek here

Upon investigating, it turned out that we had 2 VSS providers under services: Backup Exec vss provider BEVSSprovider BEVSSProvider is used to snapshot VMs , and is removed from services after Now it's the exchange one that's giving me issues. About Advertising Privacy Terms Help Sitemap × Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up I think one important point is, that I'm unable to list / delete (maybe) existing shadow copies. click site

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 But all to no avail. Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved!

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 348 We'll be sure to bother you with any questions we may have in the future :) 0 Thai Pepper OP Ccraddock Oct 22, 2012 at 2:17 UTC Brand Confirm that all snapped volumes are correctly resynchronized with the original volumes. If you have feedback for TechNet Support, contact [email protected]

File E:\databaselogs\mydomaindblogs\E02*.log is not present on the snapshot. Oh yes, I love to PVP on various game arenas and sometimes slay all those monster the MMORPGs have to offer. Join Now For immediate help use Live now! http://www.veritas.com/community/fr/forums/backup-often-fails-error-v-79-57344-34108-unexpected-error-occurred-when-cleaning-snapshot-vo and another : V-79-57344-65033 - Directory not found.

Friday, February 13, 2015 2:18 PM Reply | Quote 0 Sign in to vote Hi, IMO, vss writers are meant for backing up the data. http://www.symantec.com/connect/downloads/re-register-vss-windows-server-2008 Thanks, Umesh.S.K Friday, February 13, 2015 12:27 PM Reply | Quote 0 Sign in to vote Hi, will do that but I have read somewhere that this could have an Hi all, @maurijo : by "worse" ComdaIT Level 3 ‎11-13-2014 01:56 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content That is what I supported, when I started working here at Symantec.

Your voice, your community. 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 As for the write caching disabled..where do I check that? That is a good idea. Also, please reboot the server once and run the command.

I'm looking for a new home Wi-Fi router — any advice? navigate here But, I have not found anything from your knowledge base. Ignore all my previous comments 0 Kudos Reply See whether the solution in pkh Moderator Trusted Advisor Certified ‎04-18-2014 01:23 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Labels: 2012 Agents Backing Up Backup and Recovery Backup Exec Windows Server (2003-2008) 2 Kudos Reply 1 Solution Accepted Solutions Accepted Solution!

The cache file is created in a hidden folder named Backup Exec AOFO Store in the root of the selected volume. Best regards, Christoph Friday, February 13, 2015 12:22 PM Reply | Quote 0 Sign in to vote I think you need to re-register VSS writers. Run vssadmin list shadows.If it shows any shadowcopies, then delete them and try to running backup again. http://dukesoftwaresolutions.com/an-unexpected/unexpected-io-error-occurred.html Creating your account only takes a few minutes.

Go to Solution 1 Comment LVL 14 Overall: Level 14 Windows Server 2008 7 MS Legacy OS 3 VMware 1 Message Accepted Solution by:setasoujiro2011-07-27 We seem to have isolated and The only error I get in the log file is "V-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes. Right now the job is just hanging, no bytes counting, so I'll have no other choise as to cancel the backup.

Last week I had another interesting issue with backup exec.

Confirm that all snapped volumes are correctly resynchronized with the original volumes". Backup of files on disk D: just fails saying: V-79-57344-65033 - Directory not found. Yes… I do realize that is somewhat redundant. MenuExperts Exchange Browse BackBrowse Topics Open Questions Open Projects Solutions Members Articles Videos Contribute Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Ask a Question Ask for

also has error: MYDOMAIN-DAG01.mydomain.com\Microsoft Information Store\MydomainDB\Database is a corrupt file. Server3: Windows Server 2012 R2, latest patchlevel, virtual machine, database server with some SQL Instances, no errors on this server. Please remember to mark the replies as answers if they help and un-mark them if they provide no help. this contact form Did any one encounter such a mystery?

Backing up the .mdf and .ldf files would not work. 0 Kudos Reply @VJware : the backup is ComdaIT Level 3 ‎11-02-2014 11:57 PM Options Mark as New Bookmark Subscribe Subscribe The job fails because it cannot verify a couple of files, but Ihave to backup them, they seem to be important. 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. Matt_Cain Posted on Aug 24, 2016 8 0 Veritas Vision 2016 Keynote Session Recordings TylerWelch Posted on Sep 9, 2016 6 0 VOX: The Next Step in Veritas Customer Engagement svranyes

Join Now exchange 2013 running on 2008r2 enterprise. We just acquired a new company — what should IT do? https://kb.acronis.com/content/45472 Thanks, Umesh.S.K Friday, February 13, 2015 10:42 AM Reply | Quote 0 Sign in to vote Hi, similar error COM error "L"vssObject->Query" - HResult: 8004230f - Error message: VSS_E_UNEXPCteD_PROVIDER_ERROR best 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.

If VSS is configured to take scheduled system snapshots of a volume as well as using Backup Exec to backup this same volume... Comment Submit Your Comment By clicking you are agreeing to Experts Exchange's Terms of Use. Symantic support did not even pick this up on my server :) great tip! The schedualed backup of the server usually fails with the response code:V-79-57344-34108,An unexpected error occurred when cleaning up snapshot volumes.

Although I believe the issue is that Symantec simply does not support scenarios when another product is running (because of locked files or something). Without VMware Tools installed in your guest operating syst… VMware Backup Exec 2014 – Overview and Differences from 2012 Video by: Rodney This tutorial will give a short introduction and overview