D-Link DNS-1250-04 Acronis Backup Software User Manual for DNS-1250-04 - Page 64

Task statuses, Task state diagram

Page 64 highlights

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 How it is determined How to handle 1 Error 2 Warning 3 OK Last result is "Failed" 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 Last result is "Succeeded View the log to read the warnings -> [optionally] Perform with warning" actions to prevent the future warnings or failure. Last result is No action is required.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153

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
How it is determined
How to handle
1
Error
Last result is "Failed"
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
2
Warning
Last result is "Succeeded
with warning"
View the log to read the warnings -> [optionally] Perform
actions to prevent the future warnings or failure.
3
OK
Last result is
No action is required.