Backup Plan Execution State Not Showing Correct Status
I am having an issue where the execution state of backup jobs does not display properly. For example, in the attached screenshot three jobs are running but only two have progress bars and in the lower it says only two running tasks. The jobs that do not show a status run and complete ok but the "last finished time" does not update when they complete.
If you click on the running job with no status (HFIRBIOSANS in this instance), it does display a status in the lower pane. This has been going on for some time and it is not always the same jobs that have the issue. It appears random. What can be done to fix this?
Thanks.
-Lee
The systray icon is active on the target machine(s) and the backup does run ok. The Management Console even shows the correct status in the lower pane. Notice how HFIRBIOSANS selectd in the upper pane but the upper pane shows the status as "idle" but in the lower pane it shows the correct information. The total number of jobs running in th elower right corner is also incorrect. There are three jobs running, but the only way to see one of them is by selecting the plan and looking in the lower pane. It makes it impossible to tell with a quick glance when systems were last backed up because even when the job completes, the last backup time does not update. I have to go to the Vault and check each system there to see what the most recent backup is. Very frustrating.
That doesn't clarify the root cause and possible solution.
No Sir, it does not. If I knew the root cause and solution I would not be here.
I was attempting to clarify the problem after you said "it looks like some status information from agent was not sent to Management Server or was incorrectly processed there". I was not sure you had looked at the screenshot and were seeing that the information got there and must have been processed correctly because it shows the correct status in the lower pane. I was hoping this behavior had been seen before and there was a quick fix like clearing out a cache somewhere or something. Apparently not. Now I am trying to decide if I really want to spend more time looking for an answer.
Thank you for your time Sir.
Thank you or the provided info, anyway. What I meant to say is that the root cause remains totally unclear for me and you still need to contact support in order to get the proper solution, given that the issue not a one-time glitch and reoccurs for recreated plans.