Understanding States And Statuses; Backup Plan Execution States; Backup Plan Statuses - ACRONIS Backup & Recovery 10 Advanced Server Virtual Edition User Manual


Use the Information panel to review detailed information on the selected plan (task). The panel
is collapsed by default. To expand the panel, click the
also duplicated in the Plan details (p. 193) and Task details (p. 191) windows respectively.
6.1.2.1

Understanding states and statuses

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.
State
1 Need interaction
2 Running
3 Waiting
4 Stopping
5 Idle

Backup plan statuses

A backup plan can have one of the following statuses: Error; Warning; OK.
A backup plan status is derived from the results of the last run of the plans' tasks.
State
1 Error
184
How it is determined
At least one task needs
user interaction.
Otherwise, see 2.
At least one task is
running.
Otherwise, see 3.
At least one task is
waiting.
Otherwise, see 4.
At least one task is
stopping.
Otherwise, see 5.
All the tasks are idle.
How it is determined
At least one task has
failed.
chevron. The content of the panel is
How to handle
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).
No action is required.
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.
No action is required.
No action is required.
How to handle
Identify the failed tasks -> Check the tasks log to find out
the reason of the failure, then do one or more of the
Copyright © Acronis, Inc., 2000-2010