<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Scheduled Task - SnapMirror Throttling in Microsoft Virtualization Discussions</title>
    <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Scheduled-Task-SnapMirror-Throttling/m-p/43900#M2091</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I ended up using the following command to basically ssh to the filer and use a standard DataONTAP command to throttle the transfer at 128 KBps:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Invoke-NaSsh -Name sourcefiler -Command "snapmirror throttle 128 destinationfiler:/volumepath"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This command doesn't change the setting in the snapmirror.conf file, it just changes the throttling for the active running snapmirror job.&amp;nbsp; That way I can set the max transfer rate to unlimited and just run a scheduled task that will run this powershell script to throttle during business hours for any jobs that spill over into the day.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When the next snapmirror job kicks off, it will default back to whatever is set in the snapmirror.conf file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can run Set-NaCredential prior to running that command to store your ssh credentials so that aren't prompted for them every time you want to run the script.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 26 Mar 2014 14:22:03 GMT</pubDate>
    <dc:creator>JBIDDLE2212</dc:creator>
    <dc:date>2014-03-26T14:22:03Z</dc:date>
    <item>
      <title>Scheduled Task - SnapMirror Throttling</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Scheduled-Task-SnapMirror-Throttling/m-p/43891#M2089</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am trying to figure out using powershell how I can script out a way to on the fly change the throttling of snapmirror relationships on our filers.&amp;nbsp; The issue we are having is that some transfers that normally finish overnight are beginning to run into the daytime and use all the available bandwidth, so if I could just set up a scheduled task to throttle this during certain hours of the day, That would be ideal.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was considering using the Set-NaSnapmirrorSchedule.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am curious if I were to run something like Set-NaSnapmirrorSchedule -MaxTransferRate 256, would this change the throttling on the fly for an active transfer?&amp;nbsp; And if so, would this be the only option that was changed or would it mess up the entire schedule for the active schedule since I didn't specify the -Hours, -DaysOfWeek, etc.?&amp;nbsp; The only thing I want to change is the transfer rate.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 05:40:08 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Scheduled-Task-SnapMirror-Throttling/m-p/43891#M2089</guid>
      <dc:creator>JBIDDLE2212</dc:creator>
      <dc:date>2025-06-05T05:40:08Z</dc:date>
    </item>
    <item>
      <title>Re: Scheduled Task - SnapMirror Throttling</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Scheduled-Task-SnapMirror-Throttling/m-p/43896#M2090</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I find it easier to do at a global level than per snapmirror relationship.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You need to do something like this&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;set-naoption replication.throttle.enable on&lt;/P&gt;&lt;P&gt;and&lt;/P&gt;&lt;P&gt;set-naoption replication.throttle.enable off&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create two scripts and create AT jobs in windows to schedule it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Enjoy!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Mar 2014 16:30:06 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Scheduled-Task-SnapMirror-Throttling/m-p/43896#M2090</guid>
      <dc:creator>JGPSHNTAP</dc:creator>
      <dc:date>2014-03-20T16:30:06Z</dc:date>
    </item>
    <item>
      <title>Re: Scheduled Task - SnapMirror Throttling</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Scheduled-Task-SnapMirror-Throttling/m-p/43900#M2091</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I ended up using the following command to basically ssh to the filer and use a standard DataONTAP command to throttle the transfer at 128 KBps:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Invoke-NaSsh -Name sourcefiler -Command "snapmirror throttle 128 destinationfiler:/volumepath"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This command doesn't change the setting in the snapmirror.conf file, it just changes the throttling for the active running snapmirror job.&amp;nbsp; That way I can set the max transfer rate to unlimited and just run a scheduled task that will run this powershell script to throttle during business hours for any jobs that spill over into the day.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When the next snapmirror job kicks off, it will default back to whatever is set in the snapmirror.conf file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can run Set-NaCredential prior to running that command to store your ssh credentials so that aren't prompted for them every time you want to run the script.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Mar 2014 14:22:03 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Scheduled-Task-SnapMirror-Throttling/m-p/43900#M2091</guid>
      <dc:creator>JBIDDLE2212</dc:creator>
      <dc:date>2014-03-26T14:22:03Z</dc:date>
    </item>
    <item>
      <title>Re: Scheduled Task - SnapMirror Throttling</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Scheduled-Task-SnapMirror-Throttling/m-p/43907#M2092</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I still think it's easier to turnon and turnoff with a scheduled task.&amp;nbsp; Thats just my opinion&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;as for setting credentials, you can store your credentials in cache, or you can write a security object and pass it to the connection&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;C:\PS&amp;gt;$password = ConvertTo-SecureString "&lt;A href="mailto:p@ssword" target="_blank"&gt;p@ssword&lt;/A&gt;" -AsPlainText -Force&lt;/P&gt;&lt;P&gt;$cred = New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList "root",$password&lt;/P&gt;&lt;P&gt;Connect-NaController benson -Credential $cred&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Mar 2014 19:28:55 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Scheduled-Task-SnapMirror-Throttling/m-p/43907#M2092</guid>
      <dc:creator>JGPSHNTAP</dc:creator>
      <dc:date>2014-03-31T19:28:55Z</dc:date>
    </item>
    <item>
      <title>Re: Scheduled Task - SnapMirror Throttling</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Scheduled-Task-SnapMirror-Throttling/m-p/43911#M2093</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There may be some confusion about my previous post, but I did set it up with a scheduled task.(actually 2 scheduled tasks, 1 to turn on throttling, 1 to turn it off)&amp;nbsp; I've set up a scheduled task using a service account to run the one line above at 7:00 AM, and then it runs the same command again at 6:00 PM to turn off throttling (same command except instead of "128", plug in "0" to remove all throttling.)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That's a neat way to store the creds, but using netapps set-nacredential cmdlet was very easy.&amp;nbsp; It saves the creds for that particular filer in an encrypted file so that you never have to enter them again (unless you change the password for that account.)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your help!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Mar 2014 19:38:21 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Scheduled-Task-SnapMirror-Throttling/m-p/43911#M2093</guid>
      <dc:creator>JBIDDLE2212</dc:creator>
      <dc:date>2014-03-31T19:38:21Z</dc:date>
    </item>
  </channel>
</rss>

