The Node Recovery Point Report is helpful in analyzing and determining which nodes are adequately protected for a recovery, and which ones could be potential problem areas. If you find a problem with the number of recovery points for a specific node, look for patterns to determine why not enough or why too many backup recovery points have been taken. It is important to analyze the results from all fields of this report when attempting to determine problem nodes.
Generally if a specific node contains high-priority data, you would want to ensure that you have enough backup points to enable a quick and complete recovery if necessary.
For example, a node that contains high-priority data should have five recovery points taken to be adequately protected. If from this report, you discover that this specific high-priority node only contains two recovery points, you should investigate the reason, and modify your backup schedule as necessary to ensure proper recovery protection. You can also identify the latest possible time up to which your data can be recovered for each node and whether it is possible to recover each node through the DR option.
Likewise, if a specific node contains low-priority data, you would want to ensure that you do not have too many unnecessary backup points.
For example, a node that contains low-priority data should generally have two recovery points taken to be adequately protected. If from this report, you discover that this specific low-priority node contains five recovery points, you should investigate the reason, and modify your backup schedule to ensure you are not wasting valuable resources and time.
A good practice is to review this report in conjunction with the Media Assurance Report to make sure you not only have adequate recovery points, but also assure the data is guaranteed good to restore.
|
Copyright © 2017
|
|