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

An Unexpected Error Has Occurred When Cleaning Up Snapshot Volumes

Do you need any assistance, please let us know. By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. On this site I have three servers; the error is only generated for one of them. V-79-57344-65247 - A failure occurred reading an object. this content

Thanks. 0 Kudos Reply Use the snapshot manager in pkh Moderator Trusted Advisor Certified ‎04-18-2014 01:10 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to One thing for sure: after server restart the next backup always succeeds, but restarting the server is not an option. best regards Friday, February 13, 2015 1:39 PM Reply | Quote 0 Sign in to vote How about rebooting the affected server without re-registering? Go to Solution.

But because the snapshot hung, the service didn't get removed and somehow backupexec messed up! By creating an account, you're agreeing to our Terms of Use and our Privacy Policy Not a member? Confirm that all snapped volumes are correctly resynchronized with the original volumes. *********** is a corrupt file.

BackupA selection on device \SERVERNAMEl\F: was skipped because of previous errors with the job. What can i do to resolve this? 0 Ghost Chili OP ErikN Oct 22, 2012 at 2:35 UTC Just just inspired me to post my questions, which have But for some reason the errors provided by BE did not point into that direction at all... But, I have not found anything from your knowledge base.

It is possible that updates have been made to the original version after this document was translated and published. I'm looking for a new home Wi-Fi router — any advice? 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 http://www.veritas.com/community/fr/forums/backup-often-fails-error-v-79-57344-34108-unexpected-error-occurred-when-cleaning-snapshot-vo 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

But I am curious as to why this is happening. By creating an account, you're agreeing to our Terms of Use and our Privacy Policy Not a member? 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. Where can I find info about type of files failing?

There error is generated on this server. see this It was indeed related to the esx hanging on the snapshot... Reduce cost. VOX : Backup and Recovery : Backup Exec : Backup often fails with error "V-79-57344-34108 - ...

Will try ProcMon and report back. 0 Serrano OP Jaydeep (Symantec) Oct 23, 2012 at 3:21 UTC Brand Representative for Symantec Perfect. news I hope I made the problem clear enough and easy to understand :) Thanks! 0 Question by:setasoujiro Facebook Twitter LinkedIn Google LVL 14 Best Solution bysetasoujiro We seem to have isolated The… Storage Software Disaster Recovery Windows Server 2008 Advertise Here 823 members asked questions and received personalized solutions in the past 7 days. System snapshots of the volumes may need to be disabled to permanently resolve this issue.

Networking I've moved recently. All rights reserved. Yes… I do realize that is somewhat redundant. have a peek at these guys donikatz Expert Posts: 124 Liked: never Joined: Sun Jan 01, 2006 1:01 am Private message Top Display posts from previous: All posts1 day7 days2 weeks1 month3 months6 months1 year Sort

Change font size Print view FAQ MembersRegister Login Backup Exec Snapshot cleanup issue... Confirm that all snapped volumes are correctly resynchronized with the original volumes. Automate recovery across any distance to physical, virtual, or cloud with the predictability you require. 20015 Posts 2362 Solutions Partners Regional Veritas partner communities. 1358 Posts 99 Solutions Inside Veritas News,

by Gostev » Tue Feb 16, 2010 3:53 pm people like this post Jeremy, unfortunately we are unable to troubleshoot 3rd party backup product failures.

Thanks, Nadav. 0 Kudos Reply Did you turn on AOF in your pkh Moderator Trusted Advisor Certified ‎11-02-2014 01:06 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed We have a 2008r2 server sp1 fully patched VM, with 1 vmdk disk (C:) it has a "data" disk that is mapped over RDM in ESX.(D:) Everything was working fine, until The only error I get in the log file is "V-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes. This file cannot verify.

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 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 Confirm that all snapped volumes are correctly resynchronized with the original volumes." Both OSs are Windows Server 2008 R2. check my blog Join Now For immediate help use Live now!

Would be nice if we can start a thread for this as it might help others also. @Fletch33 would be glad if I could assist. @ me again Performance issues can 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, Do you think you can write a how to to do that. I also noticed the job rate drop from 1200-1300 MB/min from previous backups to 80-120 MB/min.

Showing results for  Search instead for  Do you mean  VOX Featured on VOX Viva Veritas! Additionally, make sure that no antivirus is scanning the B2D folder. Is there any disk encryption involved 0 Serrano OP garyleung Oct 23, 2012 at 3:15 UTC Hey JayDeep, No AV present. I'm looking for a new home Wi-Fi router — any advice?

But problem still persists. Confirm that all snapped volumes are correctly resynchronized with the original volumes.