An Unexpected Error Has Occurred When Cleaning Up Snapshot Volumes
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet When performing a backup, the following error is reported, "An unexpected error occurred when cleaning up snapshot volumes. Confirm that all snapped volumes are correctly re-synchronized with the original volumes." Article:000029170 Publish: Article URL:http://www.veritas.com/docs/000029170 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem When performing a backup, the following error is reported, "An unexpected error occurred when cleaning up snapshot volumes. Confirm that all snapped volumes are correctly resynchronized with the original volumes." causing advanced open file option to fail initializing which could potentially lead to job to failing with messages such as: 0xe000fe36 - Corrupt data encountered.Unable to open the item \\[Server Name]\[File Path] - skipped.WARNING: [Filename] is a corrupt file.Directory [Path] was not found, or could not be accessed. None of the files or subdirectories contained within will be backed up. Error Message V-79-57344-34108 An unexpected error occ
connections. Your voice, your community. Join Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Veritas.com Support Welcome to VOX An open exchange of conversations and connections. Your voice, your community. Join Communities Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In https://www.veritas.com/support/en_US/article.TECH38338 CommunityResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX Featured on VOX Viva Veritas! 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 http://www.veritas.com/community/fr/forums/backup-often-fails-error-v-79-57344-34108-unexpected-error-occurred-when-cleaning-snapshot-vo Next Step in Veritas Customer Engagement svranyes Posted on Jul 19, 2016 15 1 Explore VOX Topics Information Governance Reduce risk. Reduce cost. Simplify and automate the control of unstructured data. Achieve compliance and limit liability by gaining control of critical business processes including retention, eDiscovery, and risk management. 113555 Posts 12301 Solutions Backup and Recovery Veritas backup and recovery products protect, locate, and recover more information in less time, across any combination of platform, application, storage, and cloud. 627367 Posts 37803 Solutions Business Continuity Keep your information and critical applications up and running in the face of any disaster or outage. 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, updates, and information from Veritas executives and thought leaders can be found here. 4563 Posts 181 Solutions Vision 2016 Learn about Vision 2016, including free certification sessions, hand on labs, and sessions on hybrid cloud, open source including OpenStack & Docker, modern data protection, Office 36
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: VSS Error: 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 "An unexpected error occurred when cleaning up snapshot volumes. Confirm that all snapped volumes are correctly re-synchronized with the original volumes." Windows Server > Windows https://community.spiceworks.com/topic/1482420-backups-failing-unexpected-error-occurred-when-cleaning-up-snapshot-volumes Server 2012 General Question 0 Sign in to vote Hi all, at a customer’s site I’ve a problem with a fresh installation of Backup Exec 2014. an unexpected Every backup (full or incremental) always reports the following error: “An unexpected error occurred when cleaning up snapshot volumes. Confirm that all snapped volumes are correctly re-synchronized with the original volumes.”. It’s not a Backup Exec problem itself, also backups using “Windows Server Backup” failing with the same error. On this an unexpected error site I have three servers; the error is only generated for one of them. Here’s a short overview: Server1: Windows Server 2012 R2, latest patchlevel, physical machine, Domain Controller and Fileserver. Backup Exec is installed on this machine, backup is written directly to SAS tape loader. There error is generated on this server. Server2: Windows Server 2008 R2, latest patchlevel, virtual machine, running on Citrix Xen Server 6.2. Used for remote desktop services, no errors on this server. Server3: Windows Server 2012 R2, latest patchlevel, virtual machine, database server with some SQL Instances, no errors on this server. As I said, error is reported only on server1, no matter if it is a full or an incremental backup. 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 Shadow Copy
- Follow 43 Mentions12 Products Neal (Exclaimer) Sales & Marketing Manager GROUP SPONSORED BY EXCLAIMER IN THIS DISCUSSION Join the Community! Creating your account only takes a few minutes. Join Now exchange 2013 running on 2008r2 enterprise. backup exec 2014. when backup exec backs up the exchange database, although it backs up the database itself, the logs are not being cleared, fails with V-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes. Confirm that all snapped volumes are correctly resynchronized with the original volumes. also has error: MYDOMAIN-DAG01.mydomain.com\Microsoft Information Store\MydomainDB\Database is a corrupt file. This file cannot verify. VSS Snapshot warning. File E:\databaselogs\mydomaindblogs\E02*.log is not present on the snapshot. VSS Snapshot warning. File E:\databaselogs\mydomaindblogs\E02.chk is not present on the snapshot. thing is, both those log files do exit in the database logs folder. shadow copy is turned off on all the drives on exchange server, backup exec support had me enable and then disable shadow copy to see if that makes a difference, but doubt that it will. 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 request exchange 2010 OWA an unexpected error occurred   3 Replies Cayenne OP Captain James T Kirk Mar 7, 2016 at 7:14 UTC also, just saw this on the remote exchange server in the dag, which is the passive copy, exchange2013B: RPC request to the Microsoft Exchange Information Store service for log truncation failed for database MydomainDB\EXCHANGE2013B. Error: Failed to notify source server 'exchange2013p.mydomain.com' about the local truncation point. Hresult: 0xc8000713. Error: Unable to find the file. 0 Serrano OP CasIT Mar 27, 2016 at 4:10 UTC I've had my share of BE headaches (2012 for me), and am moving to either Unitrends or Veeam soon :) That said, have you tried recreating the backup job and running that? As a last resort I've gotten BE working again by dumping the old log and catalog files and forcing it to recreate them. Hope that helps, it's a twitchy, finicky program at times... 1 Habanero OP Katie (Un