You could open a case and ask for it to be linked to "Bug" number 315117.
It has only one customer attached to it yet (not TEAC), and as an RFE may not see the light for a while (unless you're willing to pay for it through Sales: a PVR). Also, it's not public yet, but I'll give you the header info here:
id 315117 title RFE for the ability to issue command to see current snapmirror throttle setting state NEW
Current target ONTAP is 8.1, but not confirmed.
HOWEVER...
There is also a global throttle option since 7.2RC1: http://now.netapp.com/NOW/knowledge/docs/ontap/rel727/html/ontap/cmdref /man1/na_options.1.htm ------------------------- replication.throttle.enable
Enables global network throttling of snapmirror and snapvault transfers. The default value for this options is off. -------------------------
This means you can schedule your bandwidth for all SnapMirror/SnapVault transfers in one go.
Cheers, Olaf Leimann Escalations Engineer EMEA Escalations
NetApp 00800-44-638277 EMEA Toll-free 1-877-2638277 USA Toll-free olaf@netapp.com now.netapp.com
-----Original Message----- From: John Stoffel [mailto:john.stoffel@taec.toshiba.com] Sent: donderdag 12 november 2009 16:34 To: Leimann, Olaf Cc: John Stoffel; toasters@mathworks.com Subject: RE: Determining the current 'snapmirror throttle' value?
Leimann> Perhaps a silly question, but if "you" are doing the throttle Leimann> change, then why are you not logging that yourself for future Leimann> reference ? Script the thing (perl, sh, whatever).
Yeah, it is a silly question. Let me push back on you, why can't NetApp *tell* me what the current limit is? What's so hard about:
snapmirror throttle -q [<dest>]
or something like that? My issue is that if sysadmin A makes a change, then script B makes another change, then sysadmin C want's to confirm the settings... it's just not possible. The only current answer is to just re-do your 'snapmirror throttle N <dest>' commands to force things to be what you expect.
Leimann> Another thing to look at: divide amount transferred by Leimann> current transfer time.
Sure, I guess I could pull that out with a perl script to parse the snapmirror status -v output and do the math. But that only gives the number over the lifetime of that transfer. And if the throttle will work on on-going transfers, it doesn't help me because I could have a multi-day transfer that gets throttled during work hours, then un-throttled at night, and throttled again the next time.
So the transfer rate will change and the number you propose I use won't help.
Thanks, John John Stoffel - Senior Staff Systems Administrator - System LSI Group Toshiba America Electronic Components, Inc. - http://www.toshiba.com/taec john.stoffel@taec.toshiba.com - 508-486-1087