Does anyone know what this is? © Copyright 2006-2016 Spiceworks Inc. May 10, 2012 at 1:00 PM Anonymous said... http://www.symantec.com/docs/TECH691070 Serrano OP garyleung Oct 24, 2012 at 5:36 UTC Okay, I reran the backup the other day and it completed...However a new issue has popped up. December 9, 2011 at 1:23 AM Anonymous said... http://lanprolab.net/an-unexpected/an-unexpected-error-has-occurred-when-cleaning-up-snapshot-volumes.php
FreeNAS ZFS to the rescue! It’s not a Backup Exec problem itself, also backups using “Windows Server Backup” failing with the same error. the sub-job with only system state and drive C failed. As I said, error is reported only on server1, no matter if it is a full or an incremental backup.
and that the service terminated unexpected... If you have feedback for TechNet Support, contact [email protected] Please remember to mark the replies as answers if they help and un-mark them if they provide no help. and another : V-79-57344-65033 - Directory not found.
Routinedetails Error calling Query(). [0x80042302] [hr = 0x80042302, unexpected component error of the Volume Shadow Copy Service. Used for remote desktop services, no errors on this server. Privacy statement © 2016 Microsoft. Will try ProcMon and report back. 0 Serrano OP Jaydeep (Symantec) Oct 23, 2012 at 3:21 UTC Brand Representative for Symantec Perfect.
discussion comment 02 Nov 2014 ComdaIT commented on: V-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes. Their is plenty of space on the server. Also the D: disk is correctly configured (security etc) since it has always worked. Veritas does not guarantee the accuracy regarding the completeness of the translation.
V-79-57344-34036 - An unknown error has occurred. news V-79-57344-65245 - A failure occurred accessing the object list. Ignore all my previous comments 0 Kudos Reply See whether the solution in pkh Moderator Trusted Advisor Certified 04-18-2014 01:23 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed 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?
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 My exchange database backup failed. I assume there will be 2 providers in this case and that could be the cause of the issue that 2 providers cause conflict. have a peek at these guys If there are 2 providers, you should also found them in this key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers Backup the key and delete Symantec one, reboot and see if at least Windows Server Backup will
Subscribe to our monthly newsletter for tech news and trends Membership How it Works Gigs Live Careers Plans and Pricing For Business Become an Expert Resource Center About Us Who We Labels: Backing Up Backup and Recovery Backup Exec Troubleshooting Windows Server (2003-2008) 2 Kudos Reply 11 Replies Hello Mooninite, Could you lmosla Level 6 04-17-2014 08:07 AM Options Mark as New In my case they all does not help and I eneded up, reinstalling the whole machine.
We always schedule our BE jobs to tape after Veeam jobs to disk. Server3: Windows Server 2012 R2, latest patchlevel, virtual machine, database server with some SQL Instances, no errors on this server. Email Address (Optional) Your feedback has been submitted successfully! Template images by fpm.
You may get a better answer to your question by starting a new discussion. 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 Best regards, Christoph Friday, February 13, 2015 12:22 PM Reply | Quote 0 Sign in to vote I think you need to re-register VSS writers. check my blog Hoping to assist with any Backup Exec issues that you might face with Backup Exec for a very looong time.
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 The goal: provide consistent, reliable data protection with redundancy wherever possible. 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 Confirm that all snapped volumes are correctly resynchronized with the original volumes. *********** is a corrupt file.
Confirm that all snapped volumes are correctly re-synchronized with the original volumes. Also it's not a Symantec related problem because the cause it is the missing writer which comes from the Microsoft OS. But Idid as you suggested and i'm waiting for the scheduale to kick in, i'll keep you ... Every backup (full or incremental) always reports the following error: “An unexpected error occurred when cleaning up snapshot volumes.
I think one important point is, that I'm unable to list / delete (maybe) existing shadow copies. These failures don't have any particular pattern, one can fail, the next it's backed up or two can fail and then the job is successful. I was thinking about SNMP. vssadmin list writers output says the writers state is stable with no errors.
the system snapshot process may not relinquish control or release VSS writers. Can someone advise on this? I am currently supporting v 12.5. 0 Serrano OP Jaydeep (Symantec) Oct 22, 2012 at 6:12 UTC Brand Representative for Symantec @infocon Thank you. Server2: Windows Server 2008 R2, latest patchlevel, virtual machine, running on Citrix Xen Server 6.2.
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 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? It not only failed but the rate dropped dramatically from the previous successful backups of the database. Also if there is an antivirus present, try to stop its services for troubleshooting purpose.
This can happen when some other application i.e. it even made things worse. To resolve this issue we have been simply timing the Veeam jobs to run prior or after the Backup Exec jobs.