Sync is volume-only and follows the VSM rules.
-- Adam Fox
------------------------
Typed with my thumbs on a very small keyboard.
From: MRWILLIS@UP.COM <MRWILLIS@UP.COM>
To: Fox, Adam
Cc: klises@caminomedical.org <klises@caminomedical.org>; owner-toasters@mathworks.com <owner-toasters@mathworks.com>; toasters@mathworks.com <toasters@mathworks.com>
Sent: Thu Jun 03 12:06:23 2010
Subject: Re: snapmirror question
You might also want to read up on SYNC and ASYNC requirements
;)
"Fox, Adam" <Adam.Fox@netapp.com>
Sent by: owner-toasters@mathworks.com06/03/2010 10:44 AM | To | <klises@caminomedical.org>, <toasters@mathworks.com> | cc | | Subject | Re: snapmirror question |
|
This will work fine and is supported.
For Volume SnapMirrors it's best to keep both sides on the same single-dot
release. If they must be different, then the destination side needs
to be higher.
For Qtree SnapMirror, you can mix releases versions more liberally.
But in your case you are within the same single-dot release (7.3) so you're
fine.
-- Adam Fox
------------------------
Typed with my thumbs on a very small keyboard.
----- Original Message -----
From: steve klise <klises@caminomedical.org>
To: toasters@mathworks.com <toasters@mathworks.com>
Sent: Thu Jun 03 10:29:56 2010
Subject: snapmirror question
We are doing a head upgrade tonight, and will upgrade ontap from 7.24 and
go
to 7.3.3 GD. We have a bunch of filers that snapmirror to a 3070
that is
7.3.2.p3.
Our VAR said this should still be supported, snapmirroring from 7.3.3 to
7.3.2. Has anyone done this or confirmed if it will work? Any
gotchas?
thanks always in advance.
--
View this message in context: http://old.nabble.com/snapmirror-question-tp28768308p28768308.html
Sent from the Network Appliance - Toasters mailing list archive at Nabble.com.
**
This message and any attachments contain information from Union Pacific which may be confidential and/or privileged. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited by law. If you receive this message in error, please contact the sender immediately and delete the message and any attachments.
**