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

An Unexpected Error Occurred When Cleaning Up Snapshot Volumes Symantec

By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. 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 We always schedule our BE jobs to tape after Veeam jobs to disk. Text Quote Post |Replace Attachment Add link Text to display: Where should this link go? check over here

Storage Software VMware Virtualization Storage Configuring Storage Pools in Backup Exec 2012 Video by: Rodney To efficiently enable the rotation of USB drives for backups, storage pools need to be created. Hi all, @maurijo : by "worse" I meant it didn't backup at all. That one completed eventually. Here’s a short overview: Server1: Windows Server 2012 R2, latest patchlevel, physical machine, Domain Controller and Fileserver. https://www.veritas.com/support/en_US/article.TECH38338

I have experienced that this might be really helpful when it comes to the real thing - 'Restore'. Best wishes & good luck. 0 Kudos Reply Contact Privacy Policy Terms & Conditions TechCenter   Sign in United States (English) Brasil (Português)Česká republika (Čeština)Deutschland (Deutsch)España (Español)France (Français)Indonesia (Bahasa)Italia (Italiano)România (Română)Türkiye (Türkçe)Россия Privacy Policy Site Map Support Terms of Use Home Technical questions about Backup Exec - Ask me ! 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

Thanks - that was a life saver. The job just hangs. 0 Kudos Reply « Previous 1 2 Next » Contact Privacy Policy Terms & Conditions Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup Confirm that all snapped volumes are correctly resynchronized with the original volumes" Mooninite Level 3 ‎04-17-2014 06:24 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email when you run "vssadmin list writers" check if it's listed.

Regards, Paul Luciano, MCSE 0 Serrano OP Jaydeep (Symantec) Oct 23, 2012 at 2:44 UTC Brand Representative for Symantec Thank you Paul. 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. Multiple USB devices need t… Storage Software Windows Server 2008 Disaster Recovery Boot From ISO Image in VMWare Video by: Peter This video shows you how easy it is to boot https://vox.veritas.com/t5/Backup-Exec/Backup-often-fails-with-error-quot-V-79-57344-34108-An/td-p/672719 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

Used for remote desktop services, no errors on this server. by Jaydeep (Symantec) on Oct 22, 2012 at 1:51 UTC | Data Backup Brand Representative for Symantec 0Spice Down Next: Backing up a 2TB Drive using Netbackup See more RELATED PROJECTS Note: You may need a reboot before testing. Are there any way to retrieve BE backup status from spice works.

Will try ProcMon and report back. 0 Serrano OP Jaydeep (Symantec) Oct 23, 2012 at 3:21 UTC Brand Representative for Symantec Perfect. 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 and that the service terminated unexpected... On this site I have three servers; the error is only generated for one of them. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.Would you like to participate?

Backup Exec is installed on this machine, backup is written directly to SAS tape loader. http://svbuckeye.com/an-unexpected/an-unexpected-error-has-occurred.php Routinedetails Error calling Query(). [0x80042302] [hr = 0x80042302, unexpected component error of the Volume Shadow Copy Service. The statistics shown is as follows: Clipboard01.jpg ‏53 KB 0 Kudos Reply There could be orphaned pkh Moderator Trusted Advisor Certified ‎04-17-2014 10:30 PM Options Mark as New Bookmark Subscribe Subscribe discussion comment 02 Nov 2014 ComdaIT commented on: V-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes.

My exchange database backup failed. by flfb » Tue Feb 16, 2010 4:08 pm people like this post Anton, Thank you for the reply. 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 - this content Best wishes & good luck.

Announcing Chrome push notifications for the Spiceworks Community Beta Today we are proud to announce we are adding a new way for you to receive the Community updates that you care This file cannot verify. @VJware : the backup is always succesful when I choose manual backup: "Ran next backup now" @pkh: my backup server includes the mentioned license. Simple template.

This file cannot verify.

for more info: http://www.symantec.com/connect/forums/backupexec-2010-bevss-provider-installs-inself 0 Write Comment First Name Please enter a first name Last Name Please enter a last name Email We will never share this with anyone. Turn of the feature as a Troubleshootng step. 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... Hi, in my case the problem vac Level 3 ‎04-15-2015 04:18 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content

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 Thank You! Monday, February 16, 2015 8:49 AM Reply | Quote Moderator 0 Sign in to vote Hi, Yes,I have run this on our windows 2012 R2 and found no issues. have a peek at these guys I've change the AOFO from automaticaly to Microsoft ...

Please remember to mark the replies as answers if they help and un-mark them if they provide no help. Re-registering of VSS writers should not have impact on functionality of DFS-R. There error is generated on this server. Do you think you can write a how to to do that.

Also it's not a Symantec related problem because the cause it is the missing writer which comes from the Microsoft OS. Needless to say that the directory ofcourse was available and backup ran fine like forever until then... Solved Backup Exec/VSS issue on 2008r2 Posted on 2011-07-27 MS Legacy OS VMware Windows Server 2008 1 Verified Solution 1 Comment 3,764 Views Last Modified: 2012-08-13 Hi, I'm facing an irritating Do you need any assistance, please let us know.

when you run "vssadmin list writers" check if it's listed. Template images by fpm. WARNING: "CCSRV\CCSSQL\CCSWEB.ReportServices" is a corrupt file. Availability for the Always-On Enterprise Post a reply 5 posts • Page 1 of 1 Backup Exec Snapshot cleanup issue...

JJ December 7, 2012 at 10:14 AM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Labels 3CX (3) ActiveSync (1) Android (2) Backup (1) BES (4) As I said, error is reported only on server1, no matter if it is a full or an incremental backup. As I said, error is reported only on server1, no matter if it is a full or an incremental backup. If you have feedback for TechNet Support, contact [email protected]

Confirm that all snapped volumes are correctly resynchronized with the original volumes. *********** is a corrupt file. Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Backup often fails with error "V-79-57344-34108 - An Please re-register the VSS writers and see if it helps. It’s not a Backup Exec problem itself, also backups using “Windows Server Backup” failing with the same error.

Where can I find info about type of files failing? the sub-job with only system state and drive C failed.