*incoherent scream*

[polarbee.livejournal.com]

I have been beating my head against a wall trying to get the Backup Exec CPS agent on this one server running. It simply will not start up. I have uninstalled and reinstalled multiple times. I finally found an article on Symantec's site that listed an uninstall process as well as some registry key entries to remove before reinstall that should correct my problem.

Except I got distracted right as I started the uninstall and instead of uninstalling the Backup Exec CPS agent, I just uninstalled Backup Exec 11.

FUCK!!!!!!!!!!!!!

ETA: The computer gods have smiled upon me and the reinstall went smoothly over terminal services after hours. The client won't even know backup exec was ever down.

ETA2: Except of course if they actually log on to the server, open up Backup Exec, and see that there is very little history of backup jobs.
Not very likely. Anyone have some good BS reasons for a disappearing job history list? XD

Comments

[jill-idle.livejournal.com]

rm -Rf /*

[polarbee.livejournal.com]

Well, I could claim that the entire hard drive wiped itself, but somehow I don't think they'd buy it.

[phrogg.livejournal.com]

This is the point where we say "um...whoops?"

And then turn around and tell everyone else, "We're having some technical issues getting the server back up and online. We are currently addressing these issues, and will have it back up and running just as soon as we can. Thank you for your patience."

[coren.livejournal.com]

Backup exec sucks for restoring to bare metal. Tried to dwap in new drives for the Exchange server and Backup Exec went thud. We'll be trying Acronis Trueimage next.

[polarbee.livejournal.com]

Last time we had a server crash at this location, backup exec proved itself crap as well. We managed to get an image from the CPS, but it was incomplete and had to be patched from a random NT Backup that had been made. I hate Backup Exec so much.

[ghostdandp.livejournal.com]

Acronis rocks. Last company I worked at we used it and I loved it.

This company uses Backup exec. I'm trying to convert them over. THe feature the allows you to run a image like a virtual machine while restoring it might be enough to make them switch. Although I'm guessing for that to work it'll have to backup to a real drive instead of a tape drive. I wouldn't imagine booting off a tape drive would be a enjoyable experience.

[fuzzyr.livejournal.com]

Or, you could just be honest and say that you uninstalled and reinstalled the backup software.

[polarbee.livejournal.com]

I intend to actually. Besides the fact that doing so fixed the problem, I wouldn't want to risk our relationship with the client.

[fuzzyr.livejournal.com]

I figured that you would.

[merlin-t-wizard.livejournal.com]

Anyone have some good BS reasons for a disappearing job history list?
Here's one that's true and in corpspeak to boot: "As part of the troubleshooting of the Backup Exec CPS agent, we uninstalled and reinstalled Backup Exec. Both Backup Exec and the Backup Exec CPS agent are now operating correctly, and no data was at risk during this process."

Damn, I've been in corporate America WAY too long...

[siliconshaman.livejournal.com]

Dude... when the corporate Bs speak starts to make sense, it's time to get the hell out!

[merlin-t-wizard.livejournal.com]

Don't I know it. Unfortunately, I've been at this too long to be saved. 21 years to be exact. Not at a hell desk, but in it's own way, just as bad. For continued employment reasons (mine), I can't name the Co. but you'd recognize it.

[polarbee.livejournal.com]

The saddest part is that is absolutely true. The removal of all Backup Exec products and reinstallation has fixed the problem we were having with the CPS agent. Which leads me to suspect it was the shared Backup Exec Remote Agent that was the problem.