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

An Unexpected Error Has Occurred When Cleaning Up Snapshot Volumes

by flfb » Tue Feb 16, 2010 3:15 pm people like this post Currently we use Backup Exec for file level backups on our critical servers and also use Veeam to Confirm that all snapped volumes are correctly resynchronized with the original volumes. But I am curious as to why this is happening. Though, I have lined up a few topics of my own, I would request all of you to suggest topics related to any Backup Exec Option that you would like to check over here

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. Run vssadmin list shadows.If it shows any shadowcopies, then delete them and try to running backup again. Just a guess. If Symantec Exec still works improperly after deleting the key (but WSB does), test to remove and reinstall Symantec Exec to see the result. see this here

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 If Dell OpenManage Server Administrator is installed on the remote server, it may interfere with the creation of the DR file. We're often experiencing failed backups, they fail with an error "V-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes. Join Find Answers.

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

No disk encryption either. Symantic support did not even pick this up on my server :) great tip!

But because the snapshot hung, the service didn't get removed and somehow backupexec messed up! If you have feedback for TechNet Support, contact [email protected] The cache file is created in a hidden folder named Backup Exec AOFO Store in the root of the selected volume. http://www.veritas.com/community/fr/forums/backup-often-fails-error-v-79-57344-34108-unexpected-error-occurred-when-cleaning-snapshot-vo By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks.

I am currently supporting v 12.5. During the backup I found the following errors is the event log (translated from a german system): Event ID: 12293 Volume Shadow Copy Service error: Error calling a routine on a 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 When we bought that house, it had an unfinished basement and an unfinished attic room, making the cabling process very simple.

I built it with little cost and I will share other affordable IT solutions that I leverage. This can happen when some other application i.e. 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 But all to no avail.

I am currently supporting v 12.5. 0 Serrano OP Jaydeep (Symantec) Oct 22, 2012 at 6:12 UTC Brand Representative for Symantec @infocon Thank you. check my blog That one completed eventually. best regards Christoph Friday, February 13, 2015 10:27 AM Reply | Quote 0 Sign in to vote Canyou run the below command? any suggestions - besides dumping backup exec.  I still may later, but not right now Reply Subscribe RELATED TOPICS: Reply or forward via OWA gives “An unexpected error occurred and your

Do you need any assistance, please let us know. 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 Confirm that all snapped volumes are correctly resynchronized with the original volumes.”It seems that when the Veeam job completes inside the window that the Backup Exec job is running we receive this content Are there any way to retrieve BE backup status from spice works.

backup exec 2014. The question: What should IT do? Create/Manage Case QUESTIONS?

Veritas.com Support Veritas.com Support Welcome to VOX An open exchange of conversations and connections.

Share Insights. best regards Monday, February 16, 2015 8:08 AM Reply | Quote 0 Sign in to vote Hi, What's the result of running "vssadmin list providers"? Solved! Is there a way to check which process has locked that file? 0 Serrano OP Jaydeep (Symantec) Oct 23, 2012 at 3:08 UTC Brand Representative for Symantec ProcMon

My new house... Re-registering of VSS writers should not have impact on functionality of DFS-R. For the past 2 days the 2 jobs were succesfulwith out my interference. have a peek at these guys eventually as I stated earlier, I did follow the advices here and splitted up the jobs to SQL only and Non-SQL jobs.

It was indeed related to the esx hanging on the snapshot... You may get a better answer to your question by starting a new discussion. 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 and another : V-79-57344-65033 - Directory not found.

Join Now exchange 2013 running on 2008r2 enterprise. Other SQL servers are backing up with any problems. If there is another working Windows 2012 R2 system, compare the content of the key, backup and delete the extra values to see the result. Also the D: disk is correctly configured (security etc) since it has always worked.

Thank you. Confirm that all snapped volumes are correctly resynchronized with the original volumes.