ACRONIS Backup & Recovery 10 Advanced Server User's Guide Page 181

  • Download
  • Add to my manuals
  • Print
  • Page
    / 381
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 180
Copyright © Acronis, Inc., 2000-2010 181
Otherwise, see 2
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.
2 Warning At least one task has
succeeded with
warnings.
Otherwise, see 3.
View the log to read the warnings -> [optionally] Perform
actions to prevent the future warnings or failure.
3 OK All the tasks are
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.
Task states
A task can be in one of the following states: Idle; Waiting; Running; Stopping; Need interaction. The
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.
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.
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.
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. 112) for details.
Need interaction
Any running task can put itself into the Need interaction state when it needs human interaction
such as changing media or ignoring a read error. The next state may be Stopping (if the user
chooses to stop the task) or Running (on selecting Ignore/Retry or another action, such as
Reboot, that can put the task to the Running state.)
Stopping
Page view 180
1 2 ... 176 177 178 179 180 181 182 183 184 185 186 ... 380 381

Comments to this Manuals

No comments