VSS timeout issues, restart not suitable solution
Hello I have had continual issues with vss writers time outs on one of our machines we are backing up. Running Windows Server 2008R2 SP1, using BE2010 R3 SP1 The vss writers continue to cause the backup to fail due to timeout. They restart fixes the error status on the writers, but they will time out almost each and every time i run the job. The tech's say i have the job setup correctly, with aofo selected, ms volume shadow copy service(windows 2003 and later) selected and System-use microsoft software shadow copy provider selected. And backup files following junction points. I have selected "Process logical volumes for backup one at a time" too see if this helps. Any suggestions on fixes, besides contanct MS? We don't have support with MS, and as we are suggested to use their system writers by symantec, i would hope that Symantec would provide better aid in fixing VSS issues. Thanks for the help vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001-2005 Microsoft Corp. Writer name: 'Task Scheduler Writer' Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124} Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b} State: [1] Stable Last error: No error Writer name: 'VSS Metadata Store Writer' Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06} Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93} State: [1] Stable Last error: No error Writer name: 'Performance Counters Writer' Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2} Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381} State: [1] Stable Last error: No error Writer name: 'System Writer' Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Instance Id: {bcedc94e-0c21-4212-8bbf-b65083123138} State: [9] Failed Last error: Timed out Writer name: 'ASR Writer' Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4} Writer Instance Id: {fe09e27a-4aef-4e90-bbd3-2308b5d8c6ae} State: [1] Stable Last error: No error Writer name: 'Shadow Copy Optimization Writer' Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f} Writer Instance Id: {e6368e5a-147a-4561-bf1e-d46989773b71} State: [1] Stable Last error: No error Writer name: 'Registry Writer' Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485} Writer Instance Id: {47a3c30f-0074-4427-9937-749e88f3e5b0} State: [1] Stable Last error: No error Writer name: 'COM+ REGDB Writer' Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f} Writer Instance Id: {f054ffeb-46ea-4d21-b9b3-b4c040a31214} State: [1] Stable Last error: No error Writer name: 'BITS Writer' Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0} Writer Instance Id: {3e2f6dc9-6533-4fad-9658-ece31839d8bf} State: [1] Stable Last error: No error Writer name: 'IIS Config Writer' Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6} Writer Instance Id: {f28b57b4-4222-497d-b54f-e75269db970e} State: [9] Failed Last error: Timed out Writer name: 'WMI Writer' Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} Writer Instance Id: {d50d5687-717b-4535-b70f-bee3ecb3f177} State: [9] Failed Last error: Timed outSolved30KViews2likes9Comments
BackupExec Agent for Mac OS X Server not working
I cannot seem to get the BackupExec agent for OS X Server working. I have an XServe running 10.6.4 and RALUS/RAMS 2896.9 (2010r2). I have gone through the installrams script and verified everything is correct. All ports between my server and the backup server are open while troubleshooting this problem. The admin for the backup server has verified everything is correct on his end. Whenever he goes to connect to my server, it is killing the remote agent on my server. I have restarted with the logfile option and can attach if needed. The only thing that stands out to me is that some of the dylib's are not being loaded even though I have added that directory (/opt/VRTSralus/bin) to my DYLD_LIBRARY_PATH variable. Everything else looks normal, at least to me, but the agent is killed when the backup admin tries to connect to it from the BackupExec Console.26KViews0likes6Comments
Cancel pending - hangs forever.
Hi, I have a job that was running but there was no data coming in so I thought I would cancel it and restart the backup exec agent on the server being backed up. But when the job is caceled it goes into cancel pending mode and does nothing. Just hangs in cancel pending. This happens a lot of the time and is wildly annoying so I thought maybe someone knows how to stop the job. Restarting the backup exec services on the media server is not an acceptable solution since there is another job running there that takes 12 hours and is already 4 hour into its run. Best regards, Agust.Solved17KViews1like9Comments
Disk is Full - How to Delete Old Backup Jobs
Hi All, We have 12TB of Disk space using BE2010, disk is now 92%. I set the option the option to delete overwritable backups few weeks ago. Disk space looks like paus there and not expanding any further. Could some one please advise - what is the best way to erase old backups, I have attached one picture from one of the backups but I don't understand what to erase, advise would be highly appreciated. Thanks NysohSolved17KViews1like4Comments
"Driver has detected a controller error" - help and info pls
Hi We are running B/Up Exec 2010R3 on a IBM X3650 (Win 2003 R2 standard SP2) and the backup keeps failing. It is using an IBM ULT3580-HH5 (LTO5) tape drive with an IBM SAS controller card (actually an LSI 9212-4i4e). I am now getting hardware errors (for about 1 week) but I have the latest drivers installed for the hardware and I have updated BE with the latest hotfixes. The error i get in BE is The following event was reported on 5/1/2012 8:33:30 PM: The driver detected a controller error on \Device\RaidPort1. -------------------- This error signifies controller errors. These errors are generally caused by hardware that is not functioning correctly. To resolve these errors, try the following actions: - Slow the SCSI bus. - Verify that the latest SCSI drivers and firmware are loaded. If these errors continue to occur, contact the hardware manufacturer. In Windows Event Viewer I get The description for Event ID ( 129 ) in Source ( Lsi_sas2 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: \Device\RaidPort1. Followed by Event ID:11 The driver detected a controller error on \Device\RaidPort1. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. I can't update the drivers (as they are the latest)..... I am stuck! The SAS cable has been changed, does this point to a fault with the controller card or tape drive???? If I do a test run it completes successfully, however when I run the backup it does 380gb successfully and then asks for another tape (the overwrite/append times are fine and have been doubled checked!). This happens every day..... Any help or pointers would be extremely useful ThanksSolved17KViews1like7CommentsExchange VSS writer remains in state 5: waiting for completion after a backup
If anyone has any experience with this issue I would greatly appreciate it. Exchange VSS writer remains in state 5: waiting for completion and completion never occurs. The only way I have been able to reset the status is by rebooting exchange. The only time I have this issue is when I use BE to backup exchange. When I use windows server backup I don't have this issue. I can't keep rebooting the server all the time. My environment is simple: Single Exchange Server 2007 SP3 (no rollups), using local storage.My OS is Windows Server 2008 SP2. My Backup software is BackupExec 2010R2. I have the same issue reguardless of device I backup to. I do not have any errors (Event Log) during the snapshot processes. No ESE errors, No Storage Group Consistancy Errors, The Exchange IS preps all snapshots, freezes SGs, thaws SG's, and processes the post snapshots successfully.Solved16KViews1like3Comments
all devices stuck at "discovering devices
I have an issue with my media servers where all devices get stuck at "discovering devices" and service restart or reboot of the server. We are running BE2010R3 on windows server 2008r2 platform. I know back in the day there was a regedit for diodrivers as a temp fix, but need to get this resolved permanently ASAP.Solved16KViews1like5CommentsHow to update Backup Exec Remote Agent For Windows System_
Hi all! I'm excperiencing connecting problems during night becakup to random clients - V-79-57344-65072 "the connection to target system has been lost". I've checked Backup Exec RAWS version at media server as well as on all remote systems - it's 13.0.5204.109. The Backup Exec RAWS version on the media serverin newer than enywhere else - it's 13.0.5204.114. In order to try to resolve this issue I want to update agents first. Is it possible to do it automaticly? The uninstallation process and push install doesn't help - the older version is installed.14KViews1like18CommentsSolution for VSS exceptions with VMware guests / VM tools
Hi everyone, We have been experiencing VSS issues with VMware guests in regards to the installed Backup Exec Agent and a previously installed VMware Tools VSS option. Uninstalling the VMware Tools VSS option in various ways including restarts did not fix our issues. If you search the internet for solutions, you find many attempts but no real solution or explanation. One of our admins spend several hours with the Veritas support without a solution, he was about to escalate the issue with them, when we found the root cause and could actually fix our issues. First the steps to solve this: Uninstall the VMware Tools VSS option (no restart will be requiered) Make sure VMware VSS service was deleted If this is not the case, you might need to do so manually and remove additional DLL's etc. as well as restart the system, but this is independent from this solution You might have already done steps 1 and 2 but you still get VSS exceptions from the backup that says you have more than one VSS agent installed: V-79-8192-38331 - The backup has detected that both the VMware VSS Provider and the Symantec VSS Provider have been installed on the virtual machine 'hostname'. However, only one VSS Provider can be used on a virutal machine. You must uninstall the VMware VSS Provider. Now you wonder what causes this and you get stuck You could uninstall the Veritas/Symantec Backup Exec Agent and only back the system up per VMDK You would lose the GRT / granular backup / restore capabilities Check your registry for the following reg key HKLM\System\CurrentControlSet\Services\BeVssProviderConflict If this key exists, but your VMware VSS provider is uninstalled, you need to follow up with step 5 Open a notepad as administrator Open this file in the notepad C:\ProgramData\VMware\VMware Tools\manifest.txt Search for the following two entries: Vcbprovider_2003.installed vcbprovider.installed Make sure both of them are set to FALSE, most likely one of them is TRUE Run a test backup This test backup now should not show the exception anymore The registry key should vanish (refresh/press F5) without you taking action So what happened? You uninstalled the VMware Tools VSS provider, but this manifest file did not get updated. We actually could see that it sometimes does get updated and sometimes does not. This seems to be some kind of issue with the VMware Tools uninstalled/installer. But why this manifest.txt file? As we found out, there scripts that get executed by Symantec/Veritas Backup Exec before the backup. You might find them in two locations, and it seems to depend a bit on the Windows version which script is executed (at which location). You could edit them both and just undo the checks in the scripts, but this wouldn't be correct. It is more correct to update the manifest.txt file. If you want to, you can check the date/time of the manifest.txt file before you change it - you might see it was not updated while you uninstalled the VMware Tools VSS provider (assuming you did only do this and not do additional installs/uninstalls within the VMware Tools / please note as well that this only is true when you still experienced those issues). Now, back to those scripts, you find them here: C:\Windows C:\Program Files\Symantec\Backup Exec\RAWS\VSS Provider The name of the script that matters: pre-freeze-script.bat This script checks several DLLs, registry entries, paths and on Windows 2008 and newer the ProgramData-Path for this specific manifest.txt file and the two entries mentioned. Once you uninstall the VMware VSS provider, and the file did not get updated, you might see this issue and wonder how to solve it. The solution is to simply update it to mirror the uninstallation of the VMware VSS provider (vcbprovider). We double checked this with several installations and could see if the file actually gets updated, those two values are set to FALSE, if it doesn't, at least one of the values remains true, what causes the pre-freeze-script.bat to write the registry key mentioned earlier and therefor causing the issue in the backup - exceptions. If you still have the same issues after updating the manifest.txt, simply check all the DLL's that are mentioned in the script and make sure they don't exist. You might also consider to manually delete the registry-key (it seems to be just a dumy-key) to make sure there is no issue that prevents the script from deleting it. Make sure it does not re-appear after a backup! Otherwise you might still have some DLLs left on your system that cause the script to re-create the registry key. Hope this helps a few of you out there. This was an ongoing issue for a while and I came accross those issues many times ever since Windows 2008. This applies to Windows 2008 R2, Windows 2012, Windows 2012 R2 and pretty sure to Windows 2016 as well. It helped us getting rid of those issues completely and actually not even needing a single restart of the guest VM to solve the issues (removing the VMware VSS provide did not need a restart). Regards Florian RossmarkSolved14KViews2likes10CommentsBackup job Fails: Error e0008488 Access Is Denied
Hi Guys I am struggling with the following error on my Backup Exec 2010 Media Server: The backupfailedwith error code: e0008488 - Access Is Denied Agent Used: No AOFO Used: Yes I am trying to backup a NAS Device I need to urgently backup the NAS Device and therefore had allocated 4 Tapes to the Scratch Media Set for this Job as i intend to do it manually until i have a succesfull backup set. This is theonlybackup job scheduled at the moment. Weird thing is it does'nt state 'what' was it that the access was denied to ? It does'nt give me any file names under Set Detail Information - Backup. It only gives me a set of filenames which were either 'skipped' or detected as 'corrupt'. Under the Devices Tab i See that 2 Tapes have been written to completely. The 3rd tape is almost 90% full but did not complete (probably due to the error) and the 4th tape is still in the Scratch Media Set. I looked into the following article:http://www.symantec.com/business/support/index?page=content&id=TECH71644&profileURL=https%3A%2F%2Fsymaccount-profile.symantec.com%2FSSO%2Findex.jsp%3FssoID%3D1375605283542jGBWRVRpNH2H4odkBn89L2AXb8CcbYNUCxc2D Out of the 4causes listed in the above article for the error, i could not find any one of the 4 to be of any relevance in this scenario. Any help is appreciated. Thanks a Lot !Solved13KViews1like11Comments
BackupExec Agent for Mac OS X Server not working
I cannot seem to get the BackupExec agent for OS X Server working. I have an XServe running 10.6.4 and RALUS/RAMS 2896.9 (2010r2). I have gone through the installrams script and verified everything is correct. All ports between my server and the backup server are open while troubleshooting this problem. The admin for the backup server has verified everything is correct on his end. Whenever he goes to connect to my server, it is killing the remote agent on my server. I have restarted with the logfile option and can attach if needed. The only thing that stands out to me is that some of the dylib's are not being loaded even though I have added that directory (/opt/VRTSralus/bin) to my DYLD_LIBRARY_PATH variable. Everything else looks normal, at least to me, but the agent is killed when the backup admin tries to connect to it from the BackupExec Console.How to update Backup Exec Remote Agent For Windows System_
Hi all! I'm excperiencing connecting problems during night becakup to random clients - V-79-57344-65072 "the connection to target system has been lost". I've checked Backup Exec RAWS version at media server as well as on all remote systems - it's 13.0.5204.109. The Backup Exec RAWS version on the media serverin newer than enywhere else - it's 13.0.5204.114. In order to try to resolve this issue I want to update agents first. Is it possible to do it automaticly? The uninstallation process and push install doesn't help - the older version is installed.