To set a SnapMirror relationship between source filer and destination filer you have to allow the destination to pull from source. In other words the source filer has to allow the destination filer to replicate the data from the entire volume/qtree. There are basically two ways to do it:
snapmirror.access is an option that let us provide the list of the filers that have a permission to pull the data from the source filer. To print the current setting just go with:
snapmirror.access host=filerB,filerC AND if=vif-10,vif-11
What does it mean? It means that filerB, and filerC has an access (as SnapMirror Destination) to pull data from SnapMirror Source volume/qtrees. The data can be accessed only by the network interfaces vif-10, and vif-11 (again – it is just an example).
If you would like to set it up by yourself, you can just go with:
filerA>options snapmirror.access host=filerC,10.12.12.13
snapmirror.allow is a file. The location of the file is /etc/snapmirror.allow and it can be edited with your favorite wrfile command :). The syntax of the file is pretty simple:
But there is one trick. If you would like to use snapmirror.allow you have to set the snapmirror.access option, because this is the first thing that is checked.
filerA>options snapmirror.access legacy
If the snapmirror.access is not set to legacy option, the filer will not check the snapmirror.allow file at all.
Troubleshoot the access
The first thing would be to check if a proper license is installed on both source and destination, but I’m sure you already checked that.
If you use the host-name instead of IP – make sure that the filer can resolve the name and the host is reachable, the easiest way is to ping it:
filerC is alive
If you can ping the host by IP but not by the host-name, make sure the filer can resolve the name (check /etc/nsswitch.conf and optionally /etc/hosts).