UnprotectedVolume check searches for volumes not protected by SnapMirror.

The new UnprotectedVolume check searches for volumes not protected by a SnapMirror. An alarm is generated if one or more unprotected volumes are found. Specific volumes and vservers can be checked by using the standard check_netapp_pro --include= and --exclude= arguments. A simple example follows using the default arguments and a single host argument: ./check\_netapp\_pro.pl UnprotectedVolume -H filer NETAPP\_PRO UNPROTECTEDVOLUME CRITICAL - 7 volumes checked, 6 critical and 0 warning mycluster-01:vol0: unprotected (CRITICAL) vserv\_a:vol0: unprotected (CRITICAL) vserv\_b:vol0: unprotected (CRITICAL) vserv\_b:vol1: unprotected (CRITICAL) vserv\_b:vol1\_mirror: unprotected (CRITICAL) vserv\_b:vol2: unprotected (CRITICAL) vserv\_a:vol1: protected (vserv\_b:vol1\_mirror, data\_protection) This check is part of the upcoming 5.
Read full post

Warnings for Unprotected Volumes

We are currently thinking of developing a check that sends a warning when volumes appear on a filer that are not protected by a SnapVault or SnapMirror relationship. This way, the following scenario should be identified before any loss of data can occur: Somebody creates a primary volume and forgets to save it with a SnapVault or SnapMirror relationship. Examples (Excerpts from the specification): $ check_netapp_pro.pl UnprotectedVolumes -H filer ‑‑source=prod-svm ‑‑destination=backup-svm This would check any volume on that specific vserver – so the check must be configured per vserver.
Read full post