Monitoring callback events for AFM and AFM DR
You can use events to monitor AFM and AFM DR fileset.
All events are at the fileset level. To add the events, run the mmaddcallback command.
An example of the command is
#mmdelcallback callback3
mmaddcallback callback3 --command /tmp/recovery_events.sh --event
afmRecoveryStart --parms "%eventName %homeServer %fsName %filesetName
%reason"
Events | Applicable to.. | Description |
---|---|---|
afmprepopend | All AFM filesets | Completion of the prefetch task. |
afmRecoveryStart | SW, IW, DR filesets | Beginning of the recovery process. |
afmRecoveryEnd | SW, IW, DR filesets | End of the recovery process. |
afmRPOMiss | primary | Indicates that RPO is missed due to a network delay or a failure to create snapshot on secondary side. Failed RPOs are queued and tried again on the secondary. |
afmHomeDisconnected | All AFM filesets, DR filesets | For NFS target: The AFM home/DR secondary is not reachable. |
afmHomeConnected | All AFM filesets, DR filesets | For NFS target: The AFM home/DR secondary is reachable. |
afmFilesetExpired | RO fileset | For RO fileset: Fileset has expired |
afmFilesetUnexpired | RO fileset | For RO fileset: Fileset is back to Active after expiration. |
afmManualResyncComplete | SW, IW, DR filesets | The SW resync or failover process is complete after -
|
afmQueueDropped | All AFM filesets, DR filesets | The queue is dropped. |
afmfilesetunmounted | All AFM filesets, DR filesets | The fileset is in the Unmounted state. |
afmFilesetCreate | All AFM filesets | The fileset is created successfully. |
afmFilesetLink | All AFM filesets | The fileset is linked successfully. |
afmFilesetChange | All AFM filesets | The fileset is changed successfully. If the fileset was renamed, then the new name is mentioned in %reason. |
afmFilesetUnlink | All AFM filesets | The fileset is unlinked successfully. |
afmFilesetDelete | All AFM filesets | The fileset is deleted successfully. |