Issue with Backup Exec 2010 R1 (2896)
Hi,
We are running an LTO5 tape library with Backup Exec 2010 rev 2896. We recently have had an issue with our inventory jobs. Some fail and other work fine, even though they are the same jobs. All our media is LTO5
We get the following 2 error codes
e000e005 - The job has reported multiple errors. See the job log for details.
e000821e - Library error - incompatible storage media detected in robotic library.
We also have 4 remote agents running as well. My first instinct is to upgrade Backup Exec 2010 to R3 and update the device drivers. Doing this requires me to update the 4 remote agents as well.
To do the update for the device drivers I need to install hotfix 348284 and then I can apply the latest device drivers which is hotfix 348315
My main issue is whether after installing the 2 hotfixes and updating the remote agents will I need to reboot the servers that the remote agent is running on? If not, then all is good and I can take the next step by updating Backup Exec to R3
Any help would be greatly appreciated
Regards
Arran
Comments
A reboot is required only If
A reboot is required only If the remote agents were initially installed with AOFO option.
Regards
Amol
__________________________________________________________________________________________
If this response answers your query, please mark it as a solution
You should upgrade to R3
You should upgrade to R3 because there would be no new fixes for your version of BE 2010 and there are a lot of fixes between your version and R3.
After you upgrade to R3, make sure that you run LU until it says that there is no more update. This is so that you will have SP1 and the current 7 other hotfixes.
Expect to re-boot your server, but occasionally after some hotfixes, there is no re-boot required.
Regarding your incompatible media problem, make sure that you only use LTO4 and LTO5 tapes in your library. LTO5 drives cannot write to LTO3 and below.
...you can short-cut a reboot
...you can short-cut a reboot if necessary by browsing to your registry and the following key on the server in question:
HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec
Look for a key called PatchReboot and delete this. It doesn't mean you don't need a reboot, but you can then do so at a more appropriate time. It "fools" BE into thinking that the server was rebooted, and allows the RAWS service to start up without erroring out.
If you do this, don't forget to restart at an appropriate time.
If you find this is a solution, please mark it as such.
Would you like to reply?
Login or Register to post your comment.