An Unexpected Error Occurred When Cleaning Up Snapshot Volumes. Confirm
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 v-79-57344-34108 About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers v-79-57344-33967 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 occurred when cleaning up snapshot volumes. Confirm that all snapped volumes are correctly resynchronized with the original volumes.An unexpected error occurred when cleaning up VERITAS Snapshot Provider (VSP) snapshots. Make sure that no other application has a lock on the... Cause For backups using the Advanced Open File option, the error occurs because AOFO cannot de
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 Backup of local C:\ fails with warning "An unexpected error occurred when cleaning up snapshot volumes. https://www.veritas.com/support/en_US/article.TECH38338 Confirm that all snapped volumes are correctly resynchronized with the original volumes." and beremote crashes Article:000083478 Publish: Article URL:http://www.veritas.com/docs/000083478 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 https://www.veritas.com/support/en_US/article.000083478 in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem GRT and non-GRT enabled backup of local drive fails with the warning below. The beremote service on the Backup Exec server also crashes. Error Message JOB LOG: V-79-57344-34040 - Final error: 0xe00084f8 - The network connection to the Backup Exec Remote Agent has been lost. Check for network errors. 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. EVENT VIEWER: Log Name: Application Source: Application Error Event ID: 1000 Task Category: Application Crashing Events Level: Error Keywords: Classic User: N/A Computer: COMPNAME Description: Faulting application name: beremote.exe, version: 13.0.4164.109, time stamp: 0x4cffac43 Faulting module name: kernel32.dll, version: 6.0.6002.18005, time stamp: 0x49e041d1 Exception code: 0xe06d7
exec. As you can see from the title the job ended with a : V-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes. Confirm that all snapped volumes are correctly resynchronized with the http://b1tsnbyt3s.blogspot.com/2011/07/v-79-57344-34108-unexpected-error.html original volumes. and another : V-79-57344-65033 - Directory not found. Cannot backup directory D:\HOMEDIRS\BLA\Desktop https://forums.veeam.com/veeam-backup-replication-f2/backup-exec-snapshot-cleanup-issue-t2973.html and its subdirectories. Needless to say that the directory ofcourse was available and backup ran fine like forever until then... But first a little scenario of the problem: -ESX 4 Host -Windows 2008 R2 SP1 with shares on drive "D:" -Backup of C: has no problem what so ever -VSS errors filling up event log an unexpected during backup of D: So to isolate the problem I had checked every goddamn Symantec KB, every MS KB... But all to no avail. When checking out the VCenter , nothing unusual! But then when I went clueless, and just for the fun of it connected directly to the ESX Host instead of Vcenter, I saw a Snapshot task of the said VM running and hung at 95% for an unexpected error like 1 week already!!(from the backup exec VMWare backup) So I cancelled this snapshot, but still not any luck with my D: Disk. Then my collegue spotted something I didn't see, for some reason we had 2 VSS providers: -Backup Exec VSS Provider -BEVSS Provider As it turns out, when making backups of whole VMs, Backup exec generates an extra VSS Provider (BEVSS Provider) in the services console of windows, and when backups are complete removes it again. But because the snapshot hung, the service didn't get removed and somehow backupexec messed up! 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 issue and remove the extra VSS Provider!! more info here: http://www.symantec.com/connect/forums/backupexec-2010-bevss-provider-installs-inself Posted by $3t4*$0uj1r0 at 10:13 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: ESX, Server 2008, vmware 4 comments: Anonymous said... Symantic support did not even pick this up on my server :) great tip! December 9, 2011 at 1:23 AM Anonymous said... Thanks - that was a life saver. May 10, 2012 at 1:00 PM Anonymous said... You made my day!Thank you very much for this simple, b