wdonovan - Monday, June 26, 2017 1:38 PM
You need to look at the details for the job history - it would have more than just failure. Expand the history by clicking on the plus sign. You will also want to check the SQL Server Agent log file for errors with the job. Did you setup the job itself to create a log file? Where did you set up the logging to the text file and did you verify that permissions for the folder? If you set it up in the job and no log is created from the job, it's typically a permissions issue.
For Maintenance plan history, Did you try querying msdb.dbo.sysmaintplan_log table? If you right click on a Maintenance plan and select view history, it's basically selecting from that table as well as sysmaintplan_plans and sysmaintplan_subplans. You will want to do a count to check the number of records first. Too many records in that table was one of the reasons for the out of memory error. That can be cleaned up by using sp_maintplan_delete_log if needed.
If you open the Maintenance plan to modify, go to the Backup Database task and click on Edit, you can double check the properties for the plan (server name, backup target, etc) but you can also click the View T-SQL which will allow you to view the code that is being executed. If you have more than one task, make sure you have setup precedence constraints so that the tasks flow from one to another in the appropriate order.
Sue