August 5, 2008 at 7:55 am
Hi all
I have setup a simple maintenance plan to backup two user databases at 1:00AM daily.
Few days ago i changed the time to 1:05AM
Now i get two files for each database
db1_backup_200808050100.bak
db1_backup_200808050105.bak
db2_backup_200808050100.bak
db2_backup_200808050105.bak
I did recreate the Maintenance plan and restarted SQL Agent to no avail and i still get two files every night.
When i run it manually i get one file.
Has anyone seen something like this before?
August 5, 2008 at 8:17 am
I haven't seen this exact problem, but many just like it. That's why I don't use maint plans.
Watch my free SQL Server Tutorials at:
http://MidnightDBA.com
Blog Author of:
DBA Rant – http://www.MidnightDBA.com/DBARant
August 5, 2008 at 8:41 am
Are you running SP2? I found maintenance plans almost unworkable until then.
I have mostly given up on the maintenance plans as they do not seems as stable as a collection of jobs based on TSQL. Additionally having then all written in TSQL means I have pretested script for any issues I may encounter during the week.
August 5, 2008 at 8:58 am
Alan (8/5/2008)
Are you running SP2? I found maintenance plans almost unworkable until then.I have mostly given up on the maintenance plans as they do not seems as stable as a collection of jobs based on TSQL. Additionally having then all written in TSQL means I have pretested script for any issues I may encounter during the week.
Yes SP2.
August 5, 2008 at 9:10 am
Two possibilities I can think of:
1. You created a new subtask in the database maintenance which is managing to jobs in the agent
2. (This happened to me) You renamed the sub task and the old maintenance job was orphaned in the agent and will need to be deleted manually.
The real upshot of this is how many jobs exist in the agent?
Hope this helps,
Alan
August 5, 2008 at 9:12 am
crever (8/5/2008)
I haven't seen this exact problem, but many just like it. That's why I don't use maint plans.
Crever Thanks for the links
i will recreate backups with T-SQL.
August 5, 2008 at 9:14 am
Check the schedules. Make sure there aren't two schedules assigned to the maintenance jobs.
😎
August 5, 2008 at 9:25 am
August 5, 2008 at 9:26 am
Alan (8/5/2008)
Two possibilities I can think of:1. You created a new subtask in the database maintenance which is managing to jobs in the agent
2. (This happened to me) You renamed the sub task and the old maintenance job was orphaned in the agent and will need to be deleted manually.
The real upshot of this is how many jobs exist in the agent?
Hope this helps,
Alan
Lynn Pettis (8/5/2008)
Check the schedules. Make sure there aren't two schedules assigned to the maintenance jobs.😎
1 schedule
1 step
1 job.
only changed the schedule from 1AM to 1:05AM.
August 11, 2008 at 9:16 pm
Alan (8/5/2008)
Are you running SP2? I found maintenance plans almost unworkable until then.I have mostly given up on the maintenance plans as they do not seems as stable as a collection of jobs based on TSQL. Additionally having then all written in TSQL means I have pretested script for any issues I may encounter during the week.
Amen to that. I am the same - had so many issues with SSIS doing the maintenance plans (SP1, SP2, post SP2 updates) that I gave up and used a T-SQL roll-your-own solution. You don't need that much crap to do such a basic task.
MARCUS. Why dost thou laugh? It fits not with this hour.
TITUS. Why, I have not another tear to shed;
--Titus Andronicus, William Shakespeare
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply