Maintenance Plan Stops Working

10 pts.
Tags:
Desktops
Management
Microsoft Windows
OS
Security
Servers
SQL Server
Has anyone else had this problem? We have 2 SQL servers in my office and both have Maintenance Plans set up. On a random check this morning, we found that the plan had not backed up the DB in over a month. The services were running and once restarted, everything started working again. Is there a service pack or patch that we might need? We are running SQL 2000. Thanks!

Answer Wiki

Thanks. We'll let you know when a new response is added.

There are a couple of things to look at:
1. Make sure that the jobs are set correctly, You can run each individual job from the jobs section. If they fail then look at the error it generates in the logs.
2. Make sure you have enough space in the drive that you are backing up to. If you run out of space calculate how many backups you can have at one time and in the maintenance job you can specify to delete backups older then xx days or xx weeks.

Discuss This Question: 3  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • 398669
    You can go crazy tryng to debug a maint plan that stops working. I have found the quick fix is to make a new main plan exactly like the one that stopped working and then disable the old one. I have also found that rebooting the server sometimes fixes it.
    0 pointsBadges:
    report
  • PDMeat
    Make sure the SQL agent is running otherwise no job activity. If that is all ok, try recreating the plan which will recreate (or create new) the jobs in the agent view in SEM.
    0 pointsBadges:
    report
  • Mortree
    Yes there is a problem with SQL Agent maintenance plans being easily corrupted but displaying correctly. Just like Outlook profiles. You really never want to edit maintenance plans unless you are going to watch them closely afterward to makes sure they carry out all operations as expected. And as mentioned if some other Agent task kills SQL Agent it won't run other tasks - especially time sensitive ones. The auto-restart for the SQL Agent helps that perspective but doesn't always work. Plus you don't always want SQL Agent retrying bad tasks without proper error handling!
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following