ARP alerts on suspicious writes but do not revert to a Snapshot. Why is this behavior observed?

ARP alerts on suspicious writes but do not revert to a Snapshot. Why is this behavior observed?

• A. ARP never reverts automatically
• B. The volume is offline
• C. FlexGroup volumes prevent revert
• D. SnapMirror blocks Snapshot use

Answer: (C)

ARP aims to automatically roll back to a known-good state when it detects suspicious writes, but that automatic revert only works when there’s a single, coherent volume to revert. A FlexGroup is made up of many member volumes distributed across the cluster, each with its own snapshots. There isn’t one global snapshot that covers the entire FlexGroup, so an automatic revert across all data isn’t supported. As a result, ARP will raise alerts for suspicious activity but won’t perform an automatic revert on a FlexGroup; you’d have to revert each member volume separately to its own pre-suspect snapshot or recover by other means.

ARP aims to automatically roll back to a known-good state when it detects suspicious writes, but that automatic revert only works when there’s a single, coherent volume to revert. A FlexGroup is made up of many member volumes distributed across the cluster, each with its own snapshots. There isn’t one global snapshot that covers the entire FlexGroup, so an automatic revert across all data isn’t supported. As a result, ARP will raise alerts for suspicious activity but won’t perform an automatic revert on a FlexGroup; you’d have to revert each member volume separately to its own pre-suspect snapshot or recover by other means.