2014-10-01 01:53 AM - last edited on 2015-01-30 12:32 PM by allison
Running VSC 4.2.1 on Vsphere 5.0, clustered data ontap 8.2.1
I've got several backup jobs that snapshot a volume and then do a snapmirror update. The jobs run fine and the snapmirror is updated correctly however the job issues a warning so I get an email. In the log for the job I have the lines
2014-10-01 09:24:05,049 PROGRESS - SnapMirror update has been invoked between the source '172.19.1.1:/vol/nfs_vserver_01_gold_01a' and the destination 'dr_nfs_vserver_01:nfs_vserver_01_Gold_01a_mirror'.
2014-10-01 09:24:05,081 WARN - SnapMirror is not available on volume "nfs_vserver_01_gold_01a"
2014-10-01 09:24:05,299 PROGRESS - SnapMirror update has been invoked between the source '172.19.2.1:/vol/nfs_vserver_02_gold_01' and the destination 'dr_nfs_vserver_01:nfs_vserver_02_Gold_01_Mirror'.
2014-10-01 09:24:05,346 WARN - SnapMirror is not available on volume "nfs_vserver_02_gold_01"
you can see that the snapmirror is invoked correctly but then a warning is issued. What can I do to get rid of these warnings? It makes spotting potential problems harder.