Some presumptions:
1. the destfiler:/vol/volN/qtreeY in /etc/snapmirror.conf *must* be the "hostname" of the filer. 2. the srcfiler-backup:/vol/volM/qtreeX in /etc/snapmirror.conf can be *any* hostname associated with the source filer. (i.e. if src-filer-e11 is the hostname for that interface use that) 3. destfiler and srcfiler-backup *must* be on different networks
In your example:
srcfiler:/vol/volM/qtreeX destfiler:/vol/volN/qtreeY
should change to:
srcfiler-backup:/vol/volM/qtreeX destfiler:/vol/volN/qtreeY
What happens is destfile tries to talk to srcfiler-backup and looks for a common interface. If it finds one then it will use srcfiler-backup interface and should talk to the destfiler-backup
On Wed, Apr 2, 2008 at 10:25 AM, Todd C. Merrill tmerrill@mathworks.com wrote:
I have lots of existing q-tree snapmirrrors of the form:
srcfiler:/vol/volM/qtreeX destfiler:/vol/volN/qtreeY
"srcfiler" (DNS name) is the e11 interface on srcfiler "destfiler" (DNS name) is the e9a interface on destfiler
We just built a "dedicated snapmirror/backup" network and added the following:
"srcfiler-backup" (DNS name) is the e0 inteface on srcfiler "destfiler-backup" (DNS name) is the e11a interface on destfiler
Subsequent 'snapmirror update -S ...' commands (we don't use snapmirror.conf) still use the non "-backup" network links. I'm not seeing the counters on the "-backup" links increment via the `ifstat` command.
The $64,000 question:
How do I "move" these snapmirrors to the "-backup" network links...without, of course, re-initializing them?
I'm expecting, in the end, to see `snapmirror status` give back to me:
srcfiler-backup:/vol/volM/qtreeX destfiler-backup:/vol/volN/qtreeY
and see the counters on e0 on srcfiler and e11a on destfiler increment.
Until next time...The MathWorks, Inc. 508-647-7000 x7792 3 Apple Hill Drive, Natick, MA 01760-2098 508-647-7001 FAX tmerrill@mathworks.com http://www.mathworks.com