February 4, 2009 at 11:27 am
I have been running a maintence plan (sql 2005) for a while now, with two jobs, a daily job that does the full backup and repreating job that does the logs.
Until last night.
I am not getting log backups today. I opened the job in the visual editor, and none of the 'specific databases' was checked any more. I checked the appropriate dbs and saved the plan. That was odd.
Still did not work. Opened the job and once again, no dbs checked. I checked them, closed the step, then opened it... no jobs checked.
No matter what I do, the 'checked' dbs do not stay checked any more (they are working just fine in the full backup job).
What could possibly be causing this???
...
-- FORTRAN manual for Xerox Computers --
February 4, 2009 at 11:47 am
Have the DBs perhaps been changed to simple recovery?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 4, 2009 at 11:50 am
GilaMonster (2/4/2009)
Have the DBs perhaps been changed to simple recovery?
No, I did check that.
...
-- FORTRAN manual for Xerox Computers --
February 4, 2009 at 4:54 pm
Anything in the logs or event viewer?
February 5, 2009 at 8:03 am
Jason Williams (2/4/2009)
Anything in the logs or event viewer?
Nothing different from the usual backup reporting. No error at the time the logs should be backed up.
I tried recreating a new backup job with the wizard and I still have the same trouble. I can add dbs to the log backup job, but they don't save and immediately become deselected.
Some of these dbs are now mirrored (they weren't previously) and I wondered if that was an issue (I can't see how it should be). However to test that I tried selecting only a non-mirrored db to test and the same problem occurred, the selection did not save.
The full backup part of the job continues to work correctly (and selections do save)
...
-- FORTRAN manual for Xerox Computers --
February 19, 2009 at 9:52 am
More info:
Thinking that perhaps I was doing something wrong, I created a new backup plan through the wizard. Everything seemed fine during the construction, I checked off all databases that need backup at each step.
Once it was saved I went back into it and looked at the tasks. All the tasks were fine (and all contained appropriate db info) EXCEPT the backup log task. None of the dbs to backup showed in that task. If I click 'view T-SQL' the panel that comes up is empty of code and I get an error message:
"object reference not set to an instance of an object"
This is becoming more of an issue and I don't know where to look next.
...
-- FORTRAN manual for Xerox Computers --
February 19, 2009 at 10:22 am
It could be a permission issue, is the owner of the log job the same as the full backup job?
I have had Maintanence plans corrupt themselves before without any logical reason, I kept on getting critical .Net errors when modifying them. And the only fix was to delete and re-create them.
February 19, 2009 at 10:34 am
jay holovacs (2/19/2009)
"object reference not set to an instance of an object"
What version's the server and what version's your client tools?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 19, 2009 at 11:13 am
GilaMonster (2/19/2009)
jay holovacs (2/19/2009)
"object reference not set to an instance of an object"What version's the server and what version's your client tools?
@@version = 9.00.3042.00
management studio = 9.00.3042.00
...
-- FORTRAN manual for Xerox Computers --
February 23, 2009 at 7:50 am
I had a similar problem, there is a bug in SQL 2005 whereby if you specify databases to backup and then click on the backup type the selected databases to backup become deselected.
Its a long shot but worth a try.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply