Reese Knowledgebase

snapmirror : could not read from socket

View Kristian Reese's profile on LinkedIn


If you like this article, please +1 or Recommend via FB with the provided buttons above:

Article ID: 87
by: Reese K.
Posted: 24 Jan, 2013
Last updated: 24 Jan, 2013
Views: 7780

SnapMirror: could not read from socket

[destination: replication.dst.err:error]: SnapMirror: destination transfer from source:/vol/srcvol to /vol/dstvol : could not read from socket.

/etc/log/snapmirror on the destination filer logs this:

dst Thu Jan 24 11:55:01 EST source:/vol/srcvol destination:/vol/dstvol Abort (could not read from socket)

/etc/log/snapmirror on the source filer logs this:

src Thu Jan 24 11:55:01 EST - - Abort (Access denied for SnapMirror/SnapVault destination)

Solution:

Check the snapmirror.access options.  Ensure it is set to 'legacy' or has the destination/source filer as an allowed host.  In this example, the destination filer was not allowed access to the source filer.

source> options snapmirror.access
snapmirror.access            host=10.30.126.0/23,filer1    
<- where is the destination filer?

Once added, the snapmirror transfer ran successfully:

source> options snapmirror.access host=10.30.126.0/23,filer1,destination
source> options snapmirror.access
snapmirror.access            host=10.30.126.0/23,filer1,destination

This article was:   Helpful | Not Helpful
Prev   Next
How To Setup / Configure NetApps for snapmirror     Create a multistore vfiler and enabling NFSv4

RSS