Home > Unexpected Error > V-79-57344-33967

V-79-57344-33967

Contents

Last week I had another interesting issue with backup exec. Go to Solution. when you run "vssadmin list writers" check if it's listed. Just thinking out loud, the database could be polled for successful eventlog messages and confirm that server with BE installed show that message. (thinking about how I write my own scripts

Best regards, Friday, February 13, 2015 9:55 AM Reply | Quote All replies 0 Sign in to vote Do you see any previous shadowcopies on the drive? May 10, 2012 at 1:00 PM Anonymous said... V-79-57344-34036 - An unknown error has occurred. View solution in original post 0 Kudos Reply 18 Replies ...have you tried to recreate CraigV Moderator Partner Trusted Advisor Accredited ‎10-30-2014 07:25 AM Options Mark as New Bookmark Subscribe Subscribe

V-79-57344-33967

Server3: Windows Server 2012 R2, latest patchlevel, virtual machine, database server with some SQL Instances, no errors on this server. Besides work (Symantec and Backup Exec), I am a married and so if time permits ;-) an avid gamer. Server2: Windows Server 2008 R2, latest patchlevel, virtual machine, running on Citrix Xen Server 6.2.

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 Please test both Backup exec and Windows Server Backup. Labels: 2012 Agents Backing Up Backup and Recovery Backup Exec Windows Server (2003-2008) 2 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! by Gostev » Tue Feb 16, 2010 4:22 pm people like this post Thank you.

Also, please reboot the server once and run the command. V-79-57344-65033 I don't want to exclude the mentioned files because their are a core part of the server, plus as said before when I ran it manualy the backup was succesful. I am working with Symantec for about 5 years now and am a member of the Advanced support team. https://vox.veritas.com/t5/Backup-Exec/VSS-An-unexpected-error-occurred-when-cleaning-up-snapshot/td-p/703765 As stated above.

Needless to say that system state also fails... Confirm that all snapped volumes are correctly resynchronized with the original volumes. 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... Every backup (full or incremental) always reports the following error: “An unexpected error occurred when cleaning up snapshot volumes.

  1. 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
  2. Any ideas?And thank you for any suggestions on the matter!
  3. If Backup Exec can trigger an application Event Message, you could generate a report or a plugin that checked for those.
  4. I will check out the symantec article..thanks. 0 Datil OP Paul Luciano Oct 23, 2012 at 2:30 UTC Glad to see that Symantec is working with us by
  5. by flfb » Tue Feb 16, 2010 4:08 pm people like this post Anton, Thank you for the reply.
  6. Used for remote desktop services, no errors on this server.

V-79-57344-65033

But,whenever I choose to manually backup it, by clicking on 'Run next backup now', the job is always succesful. Needless to say that the directory ofcourse was available and backup ran fine like forever until then... V-79-57344-33967 If you have feedback for TechNet Support, contact [email protected] Also the performance drop looks like a direct result of disabling the write caching on disk, what were the other chages that made from the article in my previous posts. 0

Email Address (Optional) Your feedback has been submitted successfully! Confirm that all snapped volumes are correctly re-synchronized with the original volumes.”. That is what I supported, when I started working here at Symantec. Is there a way to check which process has locked that file? 0 Serrano OP Jaydeep (Symantec) Oct 23, 2012 at 3:08 UTC Brand Representative for Symantec ProcMon

Do you think you can write a how to to do that. 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 Thank you all for your suggestions. by donikatz » Wed Feb 17, 2010 3:13 pm people like this post If you are using VSS for both Veeam and Backup Exec (or similar VSS-addressing app) at the same

If you don't understand the best way to use the tools available, you may end up being stumped as to why your drive says it's not full when you have no There are no limits set for vss on the volume. Do you Still remember, one of the most stable BE out there, 'BE 9.1 for Netware'.

Thanks. 0 Kudos Reply Use the snapshot manager in pkh Moderator Trusted Advisor Certified ‎04-18-2014 01:10 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to

What I already have tried: Disabled Antivirus during the whole backup Installed Service Pack 2 for Backup Exec Rebooted the server vssadmin list writers do not show any errors consult eventid.net 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 It was indeed related to the esx hanging on the snapshot... There error is generated on this server.

Also, do you have any archives to go back to, just in case? 0 Text Quote Post |Replace Attachment Add link Text to display: Where should this link go? Solved! I'll try disabling SEP on exchange box and retry backup. 0 1 2 Next ► This discussion has been inactive for over a year. Will try ProcMon and report back. 0 Serrano OP Jaydeep (Symantec) Oct 23, 2012 at 3:21 UTC Brand Representative for Symantec Perfect.

VSS Snapshot warning. Also change the value of value for Maximum size for B2D files to 4 GB default (or max 10 GB) and if "Allocate the maximum size for Backup-To-Disk files" is used Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : VSS: An unexpected error occurred when cleaning up... To get the best performance from Backup Exec, you should review several factors - Data transfer path, Backup Exec agent performance, network performance, Backup Exec server performance, Storage device performanceI would

Best wishes & good luck. 0 Kudos Reply Contact Privacy Policy Terms & Conditions Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business Continuity Partners Error reported: The process cannot access the file because it is being used by another process. If he agree I will give re-registering the vss a try, if this failed we still can reinstall the machine. Do you think you can write a how to to do that.

But, I have not found anything from your knowledge base. Edited by MedicalSMicrosoft contingent staff, Moderator Monday, February 23, 2015 2:54 AM Monday, February 23, 2015 2:52 AM Reply | Quote Moderator 0 Sign in to vote Hi, there are only Also it's not a Symantec related problem because the cause it is the missing writer which comes from the Microsoft OS.