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

An Unexpected Error Has Occurred When Cleaning Up Snapshot Volumes

Please remember to mark the replies as answers if they help and un-mark them if they provide no help. My previous home was wired with Cat5E in almost every room. I love photography (Astro and Wild Life) and to go on long drives whenever I feel low. Privacy statement  © 2016 Microsoft. Source

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.

The question: What should IT do? Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! These matches the entries on another (working) Server 2012 R2. over here

Server3: Windows Server 2012 R2, latest patchlevel, virtual machine, database server with some SQL Instances, no errors on this server. We're not using AOFO for exchange backups. 0 Serrano OP Jaydeep (Symantec) Oct 25, 2012 at 1:00 UTC Brand Representative for Symantec This looks like a very typical 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. Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : V-79-57344-34108 - An unexpected error occurred wh...

Hoping to assist with any Backup Exec issues that you might face with Backup Exec for a very looong time. Create/Manage Case QUESTIONS? Thank you all for your suggestions. Reply Subscribe   1 2 Next ► 44 Replies Habanero OP b0b Oct 22, 2012 at 1:57 UTC Nice intro Jay.

Sorry, we couldn't post your feedback right now, please try again later. Help Desk » Inventory » Monitor » Community » Regards, Paul Luciano, MCSE 0 Serrano OP Jaydeep (Symantec) Oct 23, 2012 at 2:44 UTC Brand Representative for Symantec Thank you Paul. Are there any way to retrieve BE backup status from spice works.

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 Only look for Antivirus on the Exchange Server and turn off the On-Access scan feature. Note: You may need a reboot before testing. 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

Creating your account only takes a few minutes. 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 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"? Hresult: 0xc8000713. 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

But for some reason the errors provided by BE did not point into that direction at all... this contact form To resolve this issue we have been simply timing the Veeam jobs to run prior or after the Backup Exec jobs. BackupV-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes. I am also an active contributor on various MMORPG forums.

There error is generated on this server. If this does not help perform basic diagostics as mentioned in  http://www.symantec.com/docs/TECH130540

0 Serrano OP garyleung Oct 23, 2012 at 2:30 UTC Hey JayDeep, I looked at the B2D The only error I get in the log file is "V-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes. have a peek here VSS List shadows says : RPC call failed VSS List writers says: WMI Writer, NTDS, FRS, System writer all "timed out" Steps I have performed already: -Checkdisk on the D: volume(found

By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. Besides work (Symantec and Backup Exec), I am a married and so if time permits ;-) an avid gamer. 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...

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

I will open an issue with Symantec and see if they can resolve this issue. Thanks, Umesh.S.K Thursday, March 12, 2015 1:00 PM Reply | Quote 0 Sign in to vote Hi Umesh, no unfortunately this issue is still not resolved. Is there any disk encryption involved 0 Serrano OP garyleung Oct 23, 2012 at 3:15 UTC Hey JayDeep, No AV present. Other SQL servers are backing up with any problems.

Yes… I do realize that is somewhat redundant. Have you resolved the issue? Also , when i tried to do the disk check , it said the volume was in use by another process, and i turned out that there was an ESX snapshot Check This Out My new house...

This file cannot verify. This file cannot verify. 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 Simplify and automate the control of unstructured data.

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 Sorry for the confusion. Your voice, your community. 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.

As you finish projects in Quip, the work remains, easily accessible to all team members, new and old. - Increase transparency - Onboard new hires faster - Access from mobile/offline Try Also, try taking a snapshot from the VM. also has error: MYDOMAIN-DAG01.mydomain.com\Microsoft Information Store\MydomainDB\Database is a corrupt file. If there is an error, you would need to correct this from the VM before proceeding with another backup. 0 Kudos Reply Hi, pkh, could you please Mooninite Level 3 ‎04-18-2014

V-79-57344-65245 - A failure occurred accessing the object list.