Backup Jobs won't start - "Ready; No media servers are available"

[DMXDirect]

I'm running Backup Exec 10.0 on a very old server (Windows 2000). Our backups have been working fine on this machine for years with only the occasional failed job. Last week, out of the blue, I can't get any jobs to run. The job seems to start, then the status changes to, "Ready; No media servers are available". This is extremely frustrating as you can imagine. My guess is that someone changed the credentials for one of the Backup Exec services, but not knowing what they were set to before it's hard to check that.

When I first start up Veritas, the server says its Offline even though the details indicate the opposite:

Perhaps this is just the server loading up because if I hit F5 to refresh a couple seconds later, it reports as Online. All the services seem to be running fine as well:

I'm sure there's just a wrong setting somewhere but I can't make heads or tails of it. At this point I haven't backed up successfully in a week, so I need a solution pretty quick.

[Donald_Eady]

Please take a look at the following documentation 

http://www.symantec.com/docs/TECH55748

[Rahul_Kumar1]

Hi,

     Apart from what steps Donald has suggested, plase check if there is a tape stuck in the tape drive. If yes remove the tape and try running the backups again.

Thanks

[CraigV]

...that's already mentioned in the TN that Donald posted...

Thanks!

[DMXDirect]

I couldn't even finish step 1. I changed the job to run Backup to Disk, which is step 1, and it still reports the same error - no media servers are available. That eliminates it being the tape drive, correct?

There is a tape in the drive but it's not a tape library, it's a stand-alone drive, so if there weren't a tape I wouldn't be getting very far :).

So. What now?

[Rahul_Kumar1]

. Reboot the Media server and the tape drive. Then try again.

Thanks

[DMXDirect]

"Remboot the Media server"... Does that mean to bounce the Backup Exec services, or to completely power off the physical server? If so, it's a production server, so it'll have to wait for tonight.

[pkh]

Try restarting the BE services

[DMXDirect]

I shut down the services and rebooted the tape drive. Next I turned the services back on. Several gave logon failures:

Processing services
 
Start services on server: DMX-STAN
Starting Backup Exec Remote Agent for Windows Servers on DMX-STAN.
The service Backup Exec Remote Agent for Windows Servers has been started on DMX-STAN.
Starting Backup Exec Device & Media Service on DMX-STAN.
Error starting the service Backup Exec Device & Media Service on DMX-STAN.
The service did not start due to a logon failure.

Starting Backup Exec Server on DMX-STAN.
Error starting the service Backup Exec Server on DMX-STAN.
The dependency service or group failed to start.

Starting Backup Exec Job Engine on DMX-STAN.
Error starting the service Backup Exec Job Engine on DMX-STAN.
The dependency service or group failed to start.

Starting Backup Exec Agent Browser on DMX-STAN.
Error starting the service Backup Exec Agent Browser on DMX-STAN.
The service did not start due to a logon failure.

Starting ExecView Communications Module(ECM) on DMX-STAN.
Error starting the service ExecView Communications Module(ECM) on DMX-STAN.
The service did not start due to a logon failure.

Start services on server DMX-STAN completed.
 
Processing services completed!

So, I can change these logon credentials, which I suspect was the source of the initial problem to begin with. Which need to log into the local server? Which need to log in to the domain Admin account? I have a feeling if I can get these set correctly I'll be good.

[HAMZAOUI_Omar]

Hi, 

I think your databse is corrupted.

Backu It (directory data and catalogs)

Create a new database with beutility, test the services, and a new backup job.

Restore the database and if the problem become, it's your database...

Thanks

[Donald_Eady]

If you would please open windows services and verify that each service is running as it should be it local system or domain\administrator

Backup Exec Agent Browser  -------------------- Domain\Administrator

Backup Exec Device & Media Service  -------- Domain\Administrator

Backup Exec Error Recording Service----------LocalSystem

Backup Exec Job Engine  ---- --------------------Domain\Administrator

Backup Exec Management Service.  ---------- Domain\Administrator

Backup Exec Remote Agent for Windows ----LocalSystem

Backup Exec Server   ----------------------------- Domain\Administrator

SQL Server (BKUPEXEC) ------------------------LocalSystem

 Also under each service that runs as Domain\Admin right click and view properties.. under theh logon as tab please reenter the credentials.. once this is done please restart B.E. services

[DMXDirect]

Any database tasks in BEUtility are greyed out, and none of the current media servers are showing there. How do I do what you suggest? I'll need documentation.

[DMXDirect]

I will. A couple questions/anomalies before I do so:

1. For the Local System accounts, should I check the "Allow service to interact with desktop" checkbox
2. I don't have the following services listed at all: "Backup Exec Error Recording Service", "Backup Exec Management Service"
3. I have a service that Veritas says is related called "ExecView Communication Module (ECM). Does it log in as DOMAIN\ADMIN or LocalSystem?
4. I don't have "SQL Server (BKUPEXEC)" as a service but I do have one called "MSSQL$BKUPEXEC" and one called "SQLAgent$BKUPEXEC" Which of these is the correct one to modify? Both, either, neither?

Thank you for your help!

[pkh · Accepted solution]

Here is the Admin Guide.

[pkh]

MSSQL$BKUPEXEC should be it.  I am not sure what the other one is for.  It has been years since I use BE 10.