Backup Exec Device & Media Service not starting - Help.

[Alshrim]

Greetings everyone. I have a stumper for me, because I've never had this problem before, so i'm hoping you faithful readers can help!

I just started in this new position, and one of the things they have had me look at is their backup server that hasn't backed anything up in about a month.

The issues that i've found is that the BkupExec D&M service fails to start because it claims that the database it connects to does not exist.

I spy down to the Sql services - everything is started. I start them manually through command prompt to get a good print out of what is starting. The files and instances that it claims it starts are all present and accounted for.

BkupExec Agent Browser ... Started.
Exec Job Engine ... Fails (dependencies to D&M service)
Exec D&M service .. fails
Exec Naming Service .... Started
Exec Remote Agent for Win Servers.... Started
Exec server ... Fails (Dependencies)

I've tried a reboot.
I've tried different service accounts .. (just to try something -- not that i had any hopes it'd work - but i wanted to rule it out).

Alshrim
System Administrator
MCSE, MCP+Internet

 

[Alshrim]

ok, things i've done:

I've updated the MDAC and installed the JetDrivers - as the latest version of MDAC may remove components needed by Veritas.

I've run the backup exec utility - and checked for consistancy in the database. everything was fine. Reindexed - worked fine., compressed - it was fine...

The tool could connect to the database - but the service can't...

Please, someone tell me why .. LOL

Alshrim
System Administrator
MCSE, MCP+Internet

 

[Alshrim]

I have resolved my issue - tho', to be honest with you all, i don't know how!

These were the steps i took before the services mysteriously started.

As it happened, there was a backup of the BE database. The files were where they should be: [path]\Veritas\Backup Exec\Data .. there were 4 database files:

bedb.bak
bed_dat.log.bak
bedb_dat.mdf
bedb_dat.log

Of course we all know which ones were old backups..
The backups were from Sept. last year...

I stopped all the services - including the Sql services, renamed the active files to .old - and renamed the backups to live files (.mdf, .log). I restarted the services - still the the D&M service failed, siting that the database did not exist.
And as it happens, the sql service for the database instance fail, because the name of the file was incorrect... BEDB.mdf - did not match the last known DB file in the registry... SO.. i stopped all the services again, renamed the file to bedb_dat.mdf - and sql was happy again.

I ran BEUtililty - ran a consistancy checker - reindexed the database. Still, the D&M service wouldn't start.

So - without shutting down any services, but the SQL instance, i renamed the database file back to the way they were .. restarted the SQL service - then tried the D&M service again - and voila it started!

Ran consistancy checkers, indexed the DB - all checked out - and i was, once again, able to log into the BE Manager.

Very very odd - but there you have it.. if someone can explain to me what happened, man i'd appreciate it.

I'd like to add, however, that i DID install all service pack updates, updated the MDAC and the Jet drivers for ODBC - and rebooted several times.

Now my problem is that i can seem to create new jobs with out a Client Access Denied error popping up.

Perhaps you all could help me with that next LOL..

So - that's what happened..


AlRo
System Administrator
Ottawa, Canada.