Hello
I am starting to look into a possible rollover of our 7-mode IBM N-Series systems to new NetApp CDOT systems.
I run backups with snapmirror and snapvault that are controlled by a AIX ksh script. The ksh script runs the following cmds to perform the data transfers:
snapmirror update -S ${filerpri}:${vol} -w ${filerdr}:${vol} snapvault snap create -w $vol $vol
Note the '-w' parm. I run these cmds in forground, so all backups are single threaded and return a response back to the script.
I'm looking at CDOT cmds manual for an equivalent '-w' parm. I find the following for the "snapmirror update" cmd:
[-foreground | -w [true]] - Foreground Process This specifies whether the operation runs as a foreground process. If this parameter is specified, the default setting is true (the operation runs in the foreground). When set to true, the command will not return until the process completes. This parameter is only applicable to relationships with "Relationship Capability" of "Pre 8.2".
Q) What does "applicable to relationships with "Relationship Capability" of "Pre 8.2" mean?
Does this mean that a CDOT>8.2 system doesn't support this parm?
Thanks!
Rick
----------------------------------------- The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Well, for starters, SnapVault is very different in cDOT than 7-mode. In 7-mode, it is qtree (or all-but qtree) based.
In cDOT, it is all volume based. It is run with SnapMirror Labels for Housekeeping of the Vaults. It is also considered an SnapMirror XDP (eXtended Data Protection) mirror (think logical replication...sort of)
SnapMirrors can be TDP (Transition Data Protection) when transitioning from 7-mode to cDOT, DP (Data Protection) for Regular version dependant SnapMirror operations and then XDP for SnapVault and/or Version-independant (think 9.0 snapmirrors TO 8.3!) SnapMirror.
You should be able to follow the 9.X transition guide to use SnapMirror to transition your Mirrors. Unfortunately, SnapVaults are not transitionable. New SnapVault baselines will be required.
Next, you should also look at possibly updating your scripts with the NetApp SDK. Use the ONTAPI commands instead. SHould even provide better error handling.
--tmac
*Tim McCarthy, **Principal Consultant*
*Proud Member of the #NetAppATeam https://twitter.com/NetAppATeam*
On Mon, Nov 28, 2016 at 9:04 AM, Rhodes, Richard L. < rrhodes@firstenergycorp.com> wrote:
Hello
I am starting to look into a possible rollover of our 7-mode IBM N-Series
systems to new NetApp CDOT systems.
I run backups with snapmirror and snapvault that are controlled
by a AIX ksh script. The ksh script runs the following cmds to
perform the data transfers:
snapmirror update -S ${filerpri}:${vol} *-w* ${filerdr}:${vol}
snapvault snap create *-w* $vol $vol
*Note the '-w' parm. *
I run these cmds in forground, so all backups are single threaded and
return a response back to the script.
I'm looking at CDOT cmds manual for an equivalent '-w' parm.
I find the following for the "*snapmirror update*" cmd:
[*-foreground *| *-w *[true]] - Foreground Process
This specifies whether the operation runs as a foreground process.
If this parameter is specified, the default setting is true
(the operation runs in the foreground). When set to true, the command
will not return until the process completes. This parameter is only
applicable to *relationships with "Relationship Capability" of "Pre 8.2".*
Q) What does "applicable to relationships with "Relationship Capability" of "Pre 8.2" mean?
Does this mean that a CDOT>8.2 system doesn't support this parm?
Thanks!
Rick
- The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message. *
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters