Link to home
Start Free TrialLog in
Avatar of jbklop24
jbklop24

asked on

Tape backups not working. Backup Exec 8.6 does not run or schedule jobs anymore.

We're running Veritas Backup Exec 8.6 on Windows 2000.  A few days ago Backup Exec just stopped running and scheduling jobs.  We backup exchange and file servers.  All the jobs in the queue are all showing a "missed" status, and Backup Exec doesn't re-schedule the job like it used to do.  If I tell a job to "run now" it just schedules it and does nothing.  

The tape loader seems to be working fine.  I can load/unload tapes, perform maintenance, etc through the loader's on-board display.  

We haven't changed, upgraded or reinstalled anything.  The error I found in the event log says "Unable to load file ESEBCLI2.DLL" but we're using Exchange 5.5, and as I understand it, that DLL is only needed for later versions of Exchange.
Another error I found in the log says "A service specific error has occurred.  Backup Exec error: 6 SelfServiceStatus."  I checked online briefly but was unable to find anything on this error.

Anybody have any ideas?
Avatar of bstrauss3
bstrauss3

I think you need to talk to Veritas, but I'm betting their answer will be to upgrade.

Both BE 8.6, W2K and Exchange 5.5 are older versions and they probably aren't testing against them anymore. So they could easily have sent you a broken update...

-----Burton
Hi jbklop24,

are you up to date with all service packs? if you trial a job with ntbackup is it successful

did you see this from veritas?

http://seer.support.veritas.com/docs/246973.htm
ASKER CERTIFIED SOLUTION
Avatar of norgan
norgan
Flag of Australia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of jbklop24

ASKER

Thanks norgan.  I was just about to close my question, but saw that you had the right solution and wanted to give you credit.  Last Friday afternoon, just before leaving work, I looked through device tree in Backup Exec and found that the backup server was in a "paused" status.  I'm surprised nobody checked that earlier.