Can I delete orphaned jobs without a complete reinstall? 1

[meastaugh1]

Hi,

BackupExec 10.1D
I had a job hang with cancel pending. I tried restarting the services. Then I tried deleting all the jobs that were created from my policy/selection list. It seems to have deleted some, but left others. It seems to have removed the link between the jobs and the policies, because if I select to delete jobs created by policy/selection list, there is nothing for selection. However, the remaining jobs cannot be deleted individually because they were created by policy.

I've tried restarting the server, there are no active jobs. I've run a consistency check, and that checks out fine. Is there anything I can do?

If I do have to do a complete reinstall, can I leave the remote agents installed, then just run the install over the top to reestablish the link between the remote agents and the media server?

Many thanks
Mike

 

[steveot]

Have you contacted support to have them remove the jobs manually out of the database?

 

[meastaugh1]

Hi,

Thanks for your prompt reply.

I don't hold a support contract. Do you think having Symantec do it would be the only way to sort this?

 

[meastaugh1]

....
I only purchased the Backup Exec licenses within the last month. Do you know if the license usually comes with any sort of support? Or does it all have to be purchased? I can't even seem to post on Symantec/Veritas support forum for this product.

 

[steveot]

You may be able to get some sort of support. But you can use the beutility to reload from base. This will basically load in a new database which you will lose you job setting/selection list/etc. Restore selection will not be affected.

If you a SQL person you could look into the database with Enterprise manager and remove the stuck jobs.

 

[meastaugh1]

Hi,

No, I'm not an SQL person.

I did take a look at beutility, but couldn't see the option to start afresh. Do you know what the option is called? Thanks

 

[meastaugh1]

... got it. Recover database and reload from base.

Thanks for your advice.

 

[rabowsm1]

I'm having the same issue with 4 out of 44 jobs. Reload from base is not an option for us since we use a CASO setup. So there's a central server which sets of the jobs for about 60 Managed Media Servers. I am not going to recreate the policies and jobs for 60 servers (it is scripted though).

I am about to call Symantec support on this one but maybe someone has a bright idea?