Forum Discussion

DMXDirect's avatar
DMXDirect
Level 3
11 years ago

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

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:

VeritasServer.jpg

 

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:

VeritasServices.jpg

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.

14 Replies

  • 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.

  • 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!

  • Here is the Admin Guide.

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