Task Statuses - ACRONIS BACKUP AND RECOVERY 10 SERVER FOR WINDOWS - UPDATE 3 User Manual

Hide thumbs Also See for BACKUP AND RECOVERY 10 SERVER FOR WINDOWS - UPDATE 3:
Table of Contents

Advertisement

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
The user can stop a running task or a task that needs interaction. The task changes to the
Stopping state and then to the Idle state. A waiting task can also be stopped. In this case, since
the task is not running, "stop" means removing it from the queue .
Task state diagram

Task statuses

A task can have one of the following statuses: Error; Warning; OK.
A task status is derived from the result of the last run of the task.
Status
1
Error
106
How it is determined
Last result is "Failed"
How to handle
Identify the failed task -> Check the task log to find out the
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 failed task to prevent its future failure
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
Copyright © Acronis, Inc., 2000-2010

Advertisement

Table of Contents
loading

This manual is also suitable for:

Backup & recovery 10 server for windows

Table of Contents