May 6, 2009 at 2:26 pm
I am receiving the "Database '' is not valid to be included in the maintenance plan." when backing up the transaction logs of selected databases. The weird thing is the databases that are getting the error are not on that server or included in the maintenance plan. I do not have any snap shots either. And I have verified that all databases are compatibility level >80.
Thanks,
Steve
May 6, 2009 at 3:11 pm
Lets pretend I didn't read the part about affected databases not being part of that server.
Is the offending Maintenance Plan set up to backup "All Databases"?
if this is the case try selecting User database individually.
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.May 7, 2009 at 6:45 am
No the maintenance plan is set to backup the transaction logs of only selected databases, not all databases. And the databases affected were removed from the server a while ago.
May 7, 2009 at 2:13 pm
When those databases were removed, was the maintenance plan modified to remove the old databases?
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
May 7, 2009 at 2:26 pm
Not sure, since I didn't remove them. However I would have figured that if a database was removed then it would cascade to the maintenance plans. However I guess not. I am going to try to remove the maintenance plan and recreate it to see if that fixes the errors.
May 7, 2009 at 2:29 pm
Steve Park (5/7/2009)
Not sure, since I didn't remove them. However I would have figured that if a database was removed then it would cascade to the maintenance plans. However I guess not. I am going to try to remove the maintenance plan and recreate it to see if that fixes the errors.
No - don't remove the maintenance plan. Just modify each task and re-save it to update the list of databases. When you create a maintenance plan, and select a set of databases - that set is saved in the plan. Removing a database does not 'cascade' - so the original maintenance plan is trying to backup a database that no longer exists.
Like I said - just open the task and resave the plan. That should remove the old databases.
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
September 17, 2014 at 5:59 am
Hi Jeffrey,
I have a similar scenario: One of my full backup Jobs is failing because a database was deleted by one of the share point administrators who notified me (the DBA) after he had already deleted the database, which is still displaying in the 'backup database task' for the maintenance plan but it no longer displays in the 'Specific Databases' list for me to deselect. Which msdb table holds the specific list of databases to be backed up for the 'backup database task'? I must be able to execute a script to delete this this particular database. Help!
Thanks,
M Morales
September 17, 2014 at 6:19 am
monrroym (9/17/2014)
Which msdb table holds the specific list of databases to be backed up for the 'backup database task'?
None. Maint plans are SSIS packages. Follow the advice above about re-saving the plan. You should be able to toggle the list to 'all databases', save, then back to specific ones, select the ones you want and save again.
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
September 17, 2014 at 7:09 am
Yes, re-saving the maintenance plan with the new list of specific databases did the trick.
Thank you so much 🙂
M Morales
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply