"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 ThanksSolved17KViews1like7CommentsBackup Exec Server Service Won't Start
My Backup Exec Server service stopped at 10:06 this morning. I try to restart the service using services.msc and I get the following: The Backup Exec Server service on Local Computer Started and the stopped. Some services stop automatically if they are not in use by other services or programs. I get the following in Event Viewer: Event 57802, The Backup Exec Server Service did not start. An internal error (10) occurred in object 13. I looked to see if any updates were installed and I did find SP2 was installed today, 10/23/13. So it seems that this update may have broken something. I did not apply this update nor can it be uninstalled. I have tried changing the service logon to Local System account and the service still would not start. I have also tried repairing the installation with no success starting the service. I appreciate any feedback. P.S. I find it kind of odd that this happened after my support agreement ended a couple of days ago and I renewed the agreement. Coincidence?Solved14KViews1like11CommentsBackup Exec log files 38GB
We've had an issue with our server due to lack of free space. We've examined the contents of the drive and "C:\Program Files\Symantec\Backup Exec\Logs\" is taking up 38GB of space. Can you tell me why it would take up this much space please? More importantly how do i cap it at say 10GB? We are using Backup Exec 2010 R3 on a windows 2007 sbs server. All our backups are backup to disk folders on removable drives and we backup also backup exchange and SQL. Thanks, your help is appreciated ThanksSolved12KViews1like4CommentsError 1068 when attempting to start BackupExec
Hi, I have installed backupExec 2010 on my Windows Server. I keep getting Error 1068: Dependency group failed to start. Some facts: -SQL Server is running (I run Hyper-V and to access VMs, my SQL Server must be running). -I have the domain account set with administrator, domain user and domain admin rights. -I was even able to login before but all of a sudden, not anymore. What could be wrong? Thanks11KViews1like7CommentsBackup Exec Server service stopping automatically.
I am having issues with my Backup Exec and Remote Agent setup. I have an Windows XP machine with Backup Exec 2010, which connects through a local area network to a Server 2003 (R2) machine which holds the physical removable media, and the Backup Exec Remote Agent package. Up until recently, and for reasons I can't explain, the Backup Exec 2010 no longer connects to the Media Server on the Server 2003 machine anymore, claiming that the Backup Exec services have stopped. I check the services.msc on the Server 2003 machine, and indeed the Backup Exec Server service is stopped and the services that have this as a dependency (Backup Exec Agent Browser & Backup Exec Job Engine) are also stopped. When trying to start the Backup Exec Server service, I get the following message: "The Backup Exec Server service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service." Is this by design? I've never noticed this occur before, and it's stopping the Windows XP Backup Exec 2010 client from connecting to the Media Server on the Server 2003 machine as the other services need to run off it. I have tried a machine reboot, I have tried repairing the Remote Agent install on the Server 2003 machine, I have also reinstalled from fresh, but the problem persists. Any help would be greatly appreciated. Thanks.Solved11KViews2likes20CommentsBackup Exec error E000E020
I'm getting a E000E020 error. It is to my understanding, that this error happens when thier is not enough resources for said job to run within the allowed time window, so it returns that error code then. We had a full system backup (2 jobs) set to run over the weekend every week for some reason this time it failed. Now I have checked the useage of the server and no other jobs we running/using the drive at the time. There should have been no reason for a lack of resources to run the jobs. 1 job is set to run a 6pm while the other starts at 6:30. It has worked for the past 6 months just fine, so not sure why out of the blue it failed. Anyways, my question is: Is there a way I can look up in more detail, why this error was given? I've looked under job Monitor and the last thing to run was an inventory job at 3pm same day, which ended at 3:34pm. That means there's almost 2.5 hours now between job tasks, so what could have told BE that it was in use/couldn't run the job? I have noticed how ever that under the alerts tab, there has been a "LiveUpdate Information." Something about 2updates are available. I've looked up how to do this update, but what (if anything) would that change? Also, there is a "LiveUpdate Warning" for a remote agent server update. I don't think either of these has anything to do with this cause both warnings were a day after the job had already failed.Solved8.5KViews0likes4CommentsBackup Exec is ejecting a tape when it shouldn't...
Hi guys, Backup Exec 2012 (patched to date). Windows 2003 SBS SP2 Single HP Ultrium 3 internal SAS tape drive. LastFriday I inserted a brand new tape intothe backuprotation. For this I simply put the new tape in the drive and ran a label job on it. This puts the tape, as you probably already know, into the scratch media pool. Saturday morning I discovered I had received repeated emails, from BENT, asking me to remove the media. I connected to the server and noticed that the Friday night backup job was still running, with 0KB written to the tape, and a remove media alert was visible in BENT. When I checked the properties of the brand new tape in the drive I noticed it had been allocated to one of my backup media pools that are set to overwrite protect the backup data for a set period of time. However, it appears BENT had done this to the tape before it had run the backup; thereby preventing itself from overwriting the blank tape (this mishandling of the media pool allocation is a separate issue I am still dealing with on a Symantec support case)!? So, to get the backup job running again I thought, all I have to do is cancel the backup job, reallocate the tape back to the scratch pool and rerun the job. So, I ignored the media remove request and cancelled the job. Only to find that BENT had ejected the tape anyway!? Surely, this is a fault in the logic of BENT. The tape should not be ejected until after the operator acknowledges the media removal alert. The backup job hasn't been set up to eject the tape on completion and I didn't acknowledge the media removal request, so BENT has abug (faulty logic)whereby the tape is still ejected, in this scenario. In this instance, I had to ask my client to go into their office, on a weekend, so they can push the tape back into the drive. Whereby I moved the tape back into the scratch pool and kicked the job off again, which completed without further errors. What should happen, when a tape that is overwrite protected and a backup job is trying to overwrite the tape is as follows: 1. A media removal alert is generated. 2. The operator is given the opportunity to check the backup job's settings and the state of the media in the drive and take actions to remediate the problem. In my case, this was to cancel the backup job, reallocate the blank tape to the scratch pool and then kick the backup job off again. However, I was precluded from doing this because BENT had already shosen to eject the tape. 3. Ifmy chosen course of actionwas to swap the media then, and only then,Backup Exec shouldeject the tape if I acknowledge the media removal alert. As far as I can see this is a fundamental flaw in the logic of the product that precludes it from being suitable for use at sites that have a single tape backup unit where backups need to be managed unattended. Any help or suggestions would be appreciated. Cheers, David7.8KViews3likes38CommentsNo media recognized in the tape drive
Hi, I have Backup Exec 2012 and a USB HP DAT 72 drive for backup connected to a HP Proliant Server on Windows 2008 Server Standard R2. The backup drive only allows 1 tape. I use 5 tapes: from Monday to Friday. Issue: Although there's physically a tape in the drive,the tape isn't recognized by Backup Exec. In the "Storage" tab, it's written "No media" in brackets besides "Tape drive". When you double click on the tape drive and goes to "Media Properties", it's written "There is no media in the drive". Because there's no media recognized, I can't erase the tape as the option is grayed. I tried to run the backup manually to test, but I get the error:"The media in drive 'Tape drive' is written in an unrecognized format. Erase the media to make it usable." So it becomes an infinite loop as I can't format the tape because Backup Exec doesn't detect any media in the drive and the option to erase is unavailable. I tried with several tapes: Friday, Monday, Tuesday, Wednesday, Thursday, Week 1. The issue remains the same. I tried to stop the Backup Exec services and unplug the DAT drive from the server + turning it off and starting everything again: the issue still remained. Does anyone know how to fix this issue? Are all my tapes or drive broken?Solved7.8KViews2likes9CommentsBackup Exec Server Service won't start after latest LiveUpdate run
Has anyone else experienced after updating to the latest push from LiveUpdate for BackupExec 2014 the BackupExec Server service not starting? I thought at first it was an issue isolated to one of my servers but it seems that the same issue has arisen after another site ran LiveUpdate and is experiencing the same issue. I'm running Backup Exec 2014 on Windows Server 2012 R2. Everything has been running fine prior to the LiveUpdate. Any response or help is appreciated.Solved7KViews1like9CommentsVerifying taking much longer that backup ?
I have BE2010 installed on MS Windows 2008 R2. Backing up on SAS hard disk and appropriate 'agents' are enabled and installed. Backup starts at 22:00 and completes without warning. But verify starts at ~00:45 and proceeds until ~04:50. I cannot understand why verify is taking so long. Any assistance greatly appreciated, MartinSolved5.7KViews1like15Comments