Fixing Backup Exec 2010
As I began to research what was going on, I found that several of the BackupExec services were not started, most notably the one called "Backup Exec Server." When I attempted to start the service, it would bring up the normal dialog box indicating that the service was starting, and upon completion, the service appeared to be started. A simple press of F5 to refresh the window showed otherwise...the service was not started. Another strange thing was also happening...the event viewer would not start. It crashed every. single. time.
So I began the arduous task of opening a support ticket with Symantec. After wrestling with their support system for around 40 minutes, I'd managed to open a support ticket. It was already after hours, and I knew they wouldn't be calling back that night.
My Wednesday started off with looking at what changed on this server. Windows Update had applied some patches over the weekend, so I began to dig through those seeing what each one touched. While I was doing this, a very helpful tech from Symantec called and walked me through a number of things, none of which got the Backup Exec service to start. While rebooting the server, the tech said she had some other callbacks to make and would call me back.
After the system rebooted, I began digging through those hotfixes, and found an interesting side effect caused by one of them. It seems that for kb2449742, if you're running certain versions of a SQL server, the event viewer would fail to start. Aha! Backup Exec uses a SQL server to save job logs and other stuff.
I uninstalled the update for kb2449742, and rebooted the server and checked the services. Lo and behold, Backup Exec had started just fine. Also, I could now run the Event Viewer.
So, the take away from this is MS' fixes sometimes break other things. And sometimes that ripple can be pretty large.
0 comments:
Post a Comment