Getting rid of those jobs would require manually deleting them from the database. There aren't any external documents on how to do that... you'd need to call into support.

Russ

> Getting rid of those jobs would require manually
> deleting them from the database.

Any ideas or suggestions how I can do that?

Joerg

You could try using enterprise manager to connect to the backup exec database and edit the entries.
But I would recommend you take a backup of the database, prior to deleting anything in the database.

I am having the same problem. I have a job that cannot be deleted because it was created with a policy, but the policy is no longer there. What would all have to be deleted in the database to remove this job?

I have same problem and it appears to have been going on for around a year (by logs on these forums!)

This is getting silly now, come on Symantec...FIX IT!

You could try using enterprise manager to connect to the backup exec database and edit the entries.
But I would recommend you take a backup of the database, prior to deleting anything in the database.


Is that Symantec's formal solution...DIY! Well, Ive looked at the DB and I aint about to start deleting stuff from that without knowing the References and Constraints involved...maybe someone from Symantec would like to mess my DB up for me?

NOTE: If I don't receive reply in 1 business day, I will be majorly upset :-)

Hi,

What Russ posted on the 8th of Dec last year is correct.
This is described in http://support.veritas.com/docs/284077
You will need to call support to get this cleared up so you can get rid of the "orphaned" jobs and create new ones from the policy.
When you call in you must refer to the technote above.

Best regards,

I printed out the 284077 document, but I am using 11d, and Enterprise Manager does not work with this version of the database. How can I delete the job manually from the database now? I did rename the bad/old job so I could create a new policy to cover what that job did, but still need to delete it.