Several databases are included in a LiteSpeed Maintenance Plan, all are being backed up but one database is not being backed up by maintenance plan. The plan shows success and no errors are displayed or logged.
Excluded database is part of a Log Shipping plan
Turn on the Maintenance Plan Reporting & Logging (setup steps below):
Search the resulting log file for text similar to : "[Pubs] Excluded Log Shippng databases" This indicates that LiteSpeed deemed this database to be *excluded* from the Maintenance Plan backup job because it is part of a Log Shipping plan.
How to turn on the Maintenance Plan Reporting & Logging:
From the LiteSpeed GUI for Maintenance Plan, the top tool bar has a button for "Reporting & Logging", select "Write a Text File", choose a location, choose to delete after # of days, choose "Log Extended Information", choose Debug Logging "Verbose".
Debug Logging—Logs LiteSpeed maintenance plan utility activity: When a subplan is executed, the Maintenance Plan engine saves the archived <plan_name>_<subplan_name>[<GUID>].zip file in the default output directory if under Reporting & Logging, the Debug Logging is set to Verbose.
The location of the log is determined by the path in the HKEY_LOCAL_MACHINE\SOFTWARE\Imceda\SQLLiteSpeed\Engine\ErrorLogPath (The default is: C:\Documents and Settings\All Users\Application Data\Quest Software\LiteSpeed)