April 8, 2009 at 9:19 am
The transaction log backup job is enabled, but the schedule was not enabled. I wasn't sure why it wasn't running and a response to this forum advised that the job schedule also had to be enabled. This was correct, so I enabled the schedule under the Schedules tab and it ran my transaction backups without error for the entire day. The next morning I came in and the job schedule wasn't enabled again. I again enabled it and applied the update. Now, for the third morning it wasn't enabled again. Again, I have enabled the schedule, applied the update and it's running again. What should I be setting to hold this schedule? It's set to be a recurring job. Job occurs Weekly, every 1 week on Mon, Tue, Wed, Thur, Fri and Sat every one hour with no end date. Has anyone had this problem and can someone point me in the right direction again?
April 8, 2009 at 9:26 am
I've had a few problems with schedules that were changed after they were created, not working as planned. My solution was to create a new schedule, with the desired settings, and use that instead. It's a band-aid, not a cure, but it did handle that for me.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
April 14, 2009 at 12:09 pm
Well, yesterday I did create a brand new schedule for my transaction log backup. Of course, it does use the same stored procedure and the schedule is the same. Today I reviewed it and the ENABLED box for the schedule is UNCHECKED AGAIN!!!!! The frustration continues. :w00t: Other suggestions welcomed!!!!
April 14, 2009 at 1:46 pm
Find the job or job step (probably in the full backup) that disables the transaction log backups. On SQL Server 2000 - you can't run both a transaction log backup and a full backup at the same time, one will block the other.
So, I am guessing that someone implemented a workaround to prevent the transaction log backups from failing or prevent them from blocking the full backup from running. The workaround would be to disable the job, then enable the job after the full backup is completed.
Again, I am guessing but instead of disabling the job the process is disabling the schedule and the step to enable the schedule is either failing, was removed, or is disabled itself.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
April 17, 2009 at 10:52 am
Well, I've looked in the Full backup job - no steps or code that exists in there that would turn off the transactional job backups. I also look at the stored procedure code itself for the full backup and it's pretty simple - just backs up the db and the logs - don't see anything in there that leads me to believe that something is turning off/unchecking the enable button for the schedule of the transactional job backup. So - in going along with the thought that it could be a conflict, the full backup runs Sunday, Tuesday evening and Thursday evening at 7PM. The transactional backups run Mon-Sat from until 7PM. I changed the transactional job to do it's last run at 6. Still, each day the schedule's enabled button is unchecked when I come in. I wouldn't think I'd have a conflict now since I stop the transactional job before the full backup job runs... Maybe I'll try renaming both the transactional job stored procedure AND creating a new job for that - I'm just not sure what to try next but it's concerning to me that I'm not getting transactional backups until I start the job myself each day.... Any other idea's?
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply