Monitor REC_ARVM_REPOSITORY_OVER_WARN_THRESHOLD (415)

Mirrored Volume Repository - Threshold Exceeded

What Caused the Problem?

A mirrored volume's repository capacity has exceeded the warning threshold. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.

Important Notes

• The repository warning threshold is a notification that is triggered when the repository capacity of a mirrored volume within the asynchronous mirror group reaches the defined percentage set by the warning threshold. This parameter is set on each mirror group.

• This problem can occur on the repository of either the primary mirrored volume or secondary mirrored volume within the asynchronous mirror group.

  • If the repository of a primary mirrored volume becomes full, synchronization of the mirror group will not be suspended and the next synchronization interval will begin when a new snapshot image is created.

  • If the repository of a secondary mirrored volume becomes full, synchronization of the mirror group will be suspended in order to preserve the recovery point for the mirrored pair.

• If this problem is occurring frequently, it is recommended to evaluate the repository capacity to determine if it is appropriately sized for the mirroring configuration. The repository warning threshold should also be evaluated to determine if the setting is appropriate for the mirroring configuration. If the threshold is set too low, the mirror group will not be able to handle the amount of data that must be synchronized.

• The Remaining unsynchronized data field in the Details area indicates the amount of data that was unsynchronized at the time the repository capacity reached the warning threshold. This value may help you identify whether the repository capacity should be increased.

  • If the amount of unsynchronized data is high, the repository capacity should be evaluated to ensure that it is adequate for the amount of write activity on the primary mirrored volume.

  • If the amount of unsynchronized is low, this problem may be the result of a one-time, unusually high amount of write activity on the primary mirrored volume. Unless this problem begins to occur on a regular basis, the repository capacity is likely adequate for the typical amount of write activity.

• This is a 'notification' condition such that there are no specific recovery steps to fix the problem. The recovery steps below are provided suggestions for how to diagnose problems that may be triggering this condition. The

  Clear

  button will remove this occurrence of the notification from the Recovery Guru.

Recovery Steps