Dell NetWorker 19.9 Administration Guide

Identifying clients that missed the workflow schedule

When a client misses the workflow schedule, it logs a message in the workflow logs. Therefore, job records are created so that DPA can easily identify them and inform the end user about this. Clients can miss workflow schedule due to the following reasons:

• Disabled clients included in workflow- Clients that are disabled from NetWorker, still remains part of a workflow. When a client is disabled, it is removed from that workflow run. To identify this, disabled clients attribute is added to the workflow job record that has the list of clients that were disabled.
• Workflow does not start at the scheduled time because the previous run still remains active- If a previous workflow is still running at the time of the next scheduled run, the scheduled run does not start. This long running workflow can be due to a slow client, large data change rate, and L0 backups for large hosts. When the workflow does not run, there is no indication in NetWorker and DPA fails to report it. To identify this, a new utility type job record is created which corresponds to the missed workflow. The new completion status displays missed the schedule and the completion report displays previous instance is still running.
• Workflow is not started since the server is down at the scheduled time- Workflow is scheduled to run at a specific time and does not cover the need for a server maintenance. If the server is down during that time, there is no indication once it restarts that the workflow was not started on time. To identify this, a new utility type job record is created which corresponds to the missed workflow. The new completion status displays missed the schedule and the completion report displays server was down.