December 9, 2008 at 12:22 pm
With the "Backup Database Task", when I use the "Backup type" of "Transaction Log", then specify the databases and save the Maintenace Plan - if I re-open the Maintenance Plan, it doesn't retain the specific databases - the "Database(s)" option has returned to " ", and none of them are checked.
However, the same "Backup Database Task" retains the database settings if, instead of the "Transaction Log" option, I select "Full".
Also, even with this situation, the Maintenace Plan performs the plan without error, saving a transaction log backup (.trn) file. I have used such backups to restore to another SQL Server, also, so they seem valid.
Is is just a "visual" thing, then, this apparent loss of which-databases setting? Is there a fix?
Thanks,
Randy
December 10, 2008 at 2:58 pm
What is the sql server version and edition?
Mj
December 10, 2008 at 3:12 pm
I have also noticed similar behavior when using maintenance plans. It was the eventual reason(besides a number of bugs in maintenance plans) I have switched to individual jobs to track my sql backups. It creates a number of jobs but each one is independent and works just fine. It also allows me to precisely schedule when any backup is occurring so as not to overload any time period.
Conan
December 10, 2008 at 3:13 pm
SQL Server 2005, SP2, no additional service packs or cumulative updates after SP2.
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply