Acronis Backup & Recovery 10 Adv WS TIDLBPDES User Manual
Product codes
TIDLBPDES
A backup plan status is derived from the results of the last run of the plans' tasks.
State
How it is determined
How to handle
1
Error
At least one task has
failed.
failed.
Otherwise, see 2
Identify the failed tasks -> Check the tasks log to find out the
reason of the failure, then do one or more of the following:
reason of the failure, then do one or more of the following:
•
Remove the reason of the failure -> [optionally] Start the
failed task manually
•
Edit the local plan to prevent its future failure in case a
local plan has failed
•
Edit the backup policy on the management server in case
a centralized plan has failed
When creating a backup plan or policy the administrator can
turn on the option to stop executing the backup plan as soon
as the backup plan gets the Error status. The backup plan's
execution can be resumed using the Restart button.
turn on the option to stop executing the backup plan as soon
as the backup plan gets the Error status. The backup plan's
execution can be resumed using the Restart button.
2
Warning
At least one task has
succeeded with
warnings.
succeeded with
warnings.
Otherwise, see 3.
View the log to read the warnings -> [optionally] Perform
actions to prevent the future warnings or failure.
actions to prevent the future warnings or failure.
3
OK
All the tasks are
completed successfully.
completed successfully.
No action is required. Note that a backup plan can be OK in
case none of the tasks has been started yet or some of the
tasks are stopped or being stopped. These situations are
considered as normal.
case none of the tasks has been started yet or some of the
tasks are stopped or being stopped. These situations are
considered as normal.
Task states
A task can be in one of the following states: Idle; Waiting; Running; Stopping; Need interaction. The
initial task state is Idle.
initial task state is Idle.
Once the task is started manually or the event specified by the schedule occurs, the task enters either
the Running state or the Waiting state.
the Running state or the Waiting state.
Running
A task changes to the Running state when the event specified by the schedule occurs AND all the
conditions set in the backup plan are met AND no other task that locks the necessary resources is
running. In this case, nothing prevents the task from running.
conditions set in the backup plan are met AND no other task that locks the necessary resources is
running. In this case, nothing prevents the task from running.
Waiting
A task changes to the Waiting state when the task is about to start, but another task using the
same resources is already running. In particular, more than one backup or recovery task cannot
run simultaneously on a machine. A backup task and a recovery task also cannot run
simultaneously. Once the other task unlocks the resource, the waiting task enters the Running
state.
same resources is already running. In particular, more than one backup or recovery task cannot
run simultaneously on a machine. A backup task and a recovery task also cannot run
simultaneously. Once the other task unlocks the resource, the waiting task enters the Running
state.
A task may also change to the Waiting state when the event specified by the schedule occurs but
the condition set in the backup plan is not met. See Task start conditions (p. 107) for details.
the condition set in the backup plan is not met. See Task start conditions (p. 107) for details.
Need interaction
Copyright © Acronis, Inc., 2000-2009
181