Backup plan execution states

A backup plan can be in one of the following execution states: Idle; Waiting; Running; Stopping; Need Interaction.

Plan states names are the same as task state names because a plan state is a cumulative state of the plan’s tasks.



How it is determined

How to handle


Need interaction

At least one task needs user interaction.

Otherwise, see 2.

Identify the tasks that need interaction (the program will display what action is needed) -> Stop the tasks or enable the tasks to run (change media; provide additional space on the vault; ignore the read error; create the missing Acronis Secure Zone).



At least one task is running.

Otherwise, see 3.

No action is required.



At least one task is waiting.

Otherwise, see 4.

Waiting for condition. This situation is quite normal, but delaying a backup for too long is risky. The solution may be to set the maximum delay or force the condition (tell the user to log off, enable the required network connection.)

Waiting while another task locks the necessary resources. A one-time waiting case may occur when a task start is delayed or a task run lasts much longer than usual for some particular reason and this way prevents another task from starting. This situation is resolved automatically when the obstructing task comes to an end. Consider stopping a task if it hangs for too long to enable the next task to start.

Persistent task overlapping may result from an incorrectly scheduled plan or plans. It makes sense to edit the plan in this case.



At least one task is stopping.

Otherwise, see 5.

No action is required.



All the tasks are idle.

No action is required.

See also:

Backup plan statuses

Task states

Task statuses

Backup plan execution states