Troubleshooting
Problem
The Operations Center considers recent activity for a client and determines whether the client is at risk of being unprotected.
Diagnosing The Problem
The "at risk" designation primarily indicates that an administrator should investigate a client issue to determine whether or not it creates a significant risk (based on the business goals, data protection strategy, and such).
The "at risk" interval can be set at two different levels:
- at node level, by selecting a Custom node interval for each Client Node
- default, that is valid for all Client Nodes
In a situation where both are defined, it is important to understand which one applies.
In IBM Spectrum Protect Operation center evaluate at-risk in following cases.
1. In IBM Spectrum Protect Operation center version 7.1.4 and before:
- Operation center will not evaluate at-risk on the node if the node has never done anything backup
- Operation center will not evaluate at-risk on the TDP type node if the node has never done anything archive
2. Starting from version 7.1.6 Operation Center will evaluate the node no matter node has a schedule associated with node or not and show at risk in below cases:
- the node has not backup any data at all.
- The node has not backup any data within scheduled time when the node has schedule.
- The "TDP" (TDP = "Tivoli Data Protection" node) type node has not archive any data at all.
- The "TDP" (TDP = "Tivoli Data Protection" node) type node has not archive any data within scheduled time when the node has schedule.
Resolving The Problem
The custom "at-risk" interval for a node can be found using the command
"QUERY NODE <nodename> F=D".
If the "At-risk type" field is reported as "default", then the values in "QUERY MONITORSETTINGS" apply.
If the "At-risk type" field is shown as "custom", then the custom interval applies.
More information on how to set the "At-risk" interval can be found here:
http://www-01.ibm.com/support/knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.srv.ref.doc/r_cmd_nodeatriskinterval_set.html
It is also possible to specify an "at-risk" type equal to BYPASSED.
In this case, the Client Node is not evaluated for at-risk status by the status monitor.
Related Information
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21883409