Backup policy statuses
A backup policy status is the cumulative status of the policy statuses on all machines the policy is applied to. For example, if the policy is applied to three machines and has the “OK” status on the 1st machine, the “Warning” status on the 2nd machine and the “Error” status on the 3rd machine, the status of the policy will be “Error.”
A backup policy status on a group of machines is the cumulative status of the policy statuses on the machines included in the group.
The following table shows a summary of possible backup policy statuses.
|
|
Status
|
How it is determined
|
How to handle
|
|
1
|
Error |
The policy status on at least one machine is “Error”.
Otherwise, see 2.
|
View the log or identify the failed tasks 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 backup policy to prevent future failure
|
|
2
|
Warning |
The policy status on at least one machine is “Warning”.
Otherwise, see 3.
|
View the log to read the warnings -> [optionally] Perform actions to prevent future warnings or failure.
|
|
3
|
OK |
The policy status on all machines is “OK”.
|
No action is required. Note that if a backup policy is not applied to any machine, its state is also “OK”.
|
What to do if a policy has the Error status
- To find out the reason of the failure, do one or more of the following:
- Click the Error hyperlink to see the log entry of the latest occurred error.
- Select the policy and click View tasks. Check the tasks that have Failed as their last result: select a task and then click View log. Select a log entry and then click View details. This approach comes in handy if the policy state is Deployed, that is, the policies’ tasks already exist on the managed machines.
- Select the policy and click View log. Check the “error” log entries to find out the reason of the failure: select a log entry and then click View details. This approach comes in handy if the policy has errors while being deployed, revoked or updated.
In the Tasks view, apply the Last result -> Failed filter if there are too many tasks. You can also sort the failed tasks by backup plans or by machines.
In the Log view, apply the Error  filter if there are too many log entries. You can also sort the “error” entries by backup plans, managed entities or machines.
- Once the reason of the failure is clear, do one or more of the following:
- Remove the reason of the failure. After that, you may want to start the failed task manually to maintain the backup scheme consistency, for example, if the policy uses the GFS or Tower of Hanoi backup scheme.
- Edit the backup policy to prevent future failure.
Use the Activities section of the Dashboard to quickly access the “error” log entries.
What to do if a policy has the Warning status
- To find out the reason of the warning, do one or more of the following:
- Click the Warning hyperlink to see the log entry of the latest warning.
- Select the policy and click View tasks. Check the tasks that have Succeeded with warnings as their last result: select a task and then click View log. This approach comes in handy if the policy state is Deployed, that is, the policies’ tasks already exist on the managed machines.
- Select the policy and click View log. Check the “warning” log entries to find out the reason for the warnings : select a log entry and then click View details. This approach comes in handy if the policy has warnings while being deployed, revoked or updated.
In the Tasks view, apply the Last result -> Succeeded with warnings filter if there are too many tasks. You can also sort the tasks succeeded with warnings by backup plans or by machines.
In the Log view, apply the Warning  filter if there are too many log entries. You can also sort the “warning” entries by backup plans, managed entities or machines.
- Once the reason of the warning is clear you might want to perform actions to prevent future warnings or failure.
Use the Activities section of the Dashboard to quickly access the “warning” log entries.
What to do if a policy status is OK
No action is required.
|