Hi, I'm evaluating snapmirror for qtree migration from our existing filers running 6.5.4P8 to a newly purchased FAS3040 running 7.2.2
I have configured snapmirror and managed to figure out how to do the initial transfer but I can't seem to get the following ... I would like to be able to stop (and resume at a later time) both the initial and any later updates if I find that they are impacting the production system.
Tried: quiesce, break & resync, break & resume
Please help.
George
Quiesce should do the job, however on a QSM transfer, I've found it can take a while and I'm not 100% sure it will work well on a QSM initialization, but I'll admit, it's been a while since I've tried it in the lab.
-- Adam Fox adamfox@netapp.com
-----Original Message----- From: George Kahler [mailto:george@yorku.ca] Sent: Monday, June 25, 2007 1:26 PM To: toasters@mathworks.com Subject: snapmirror newbie
Hi, I'm evaluating snapmirror for qtree migration from our existing filers running 6.5.4P8 to a newly purchased FAS3040 running 7.2.2
I have configured snapmirror and managed to figure out how to do the initial transfer but I can't seem to get the following ... I would like to be able to stop (and resume at a later time) both the initial and any later updates if I find that they are impacting the production system.
Tried: quiesce, break & resync, break & resume
Please help.
George
You can use 'snapmirror abort' to abort the transfer and then restart from where you left off using initialize or update. You can also use 'snapmirror off' to abort all running transfers at once.
Cheers.
Vinay
-----Original Message----- From: George Kahler [mailto:george@yorku.ca] Sent: Monday, June 25, 2007 10:26 AM To: toasters@mathworks.com Subject: snapmirror newbie
Hi, I'm evaluating snapmirror for qtree migration from our existing filers running 6.5.4P8 to a newly purchased FAS3040 running 7.2.2
I have configured snapmirror and managed to figure out how to do the initial transfer but I can't seem to get the following ... I would like to be able to stop (and resume at a later time) both the initial and any later updates if I find that they are impacting the production system.
Tried: quiesce, break & resync, break & resume
Please help.
George
Starting/Stopping snapmirrors is a very manual process and if your concerned that SnapMirror will be starving your other application data volumes of I/O, CPU, or memory then I would take advantage of a feature called Flexshare, which is new to the 7.2 release. It'll allow you to "prioritize" the workload in several different ways by volume, for example to your questions point, If I had a volume that was serving up Exchange LUN's and the volume containing these LUN's was being snapmirrored to another filer offsite for DR purposes but I never wanted to SnapMirror transfers to take priority over the Exchange clients I would set the "User versus system priority" to give priority to the user workload (exchange clients) over the system workloads (SnapMirror updates).
There is a good article in Tech ONTAP this month that explains this in more detail.
http://www.netapp.com/go/techontap/flexshare.html
I hope this helps
On 6/25/07 1:36 PM, "Gupta, Vinay" Vinay.Gupta@netapp.com wrote:
You can use 'snapmirror abort' to abort the transfer and then restart from where you left off using initialize or update. You can also use 'snapmirror off' to abort all running transfers at once.
Cheers.
Vinay
-----Original Message----- From: George Kahler [mailto:george@yorku.ca] Sent: Monday, June 25, 2007 10:26 AM To: toasters@mathworks.com Subject: snapmirror newbie
Hi, I'm evaluating snapmirror for qtree migration from our existing filers running 6.5.4P8 to a newly purchased FAS3040 running 7.2.2
I have configured snapmirror and managed to figure out how to do the initial transfer but I can't seem to get the following ... I would like to be able to stop (and resume at a later time) both the initial and any later updates if I find that they are impacting the production system.
Tried: quiesce, break & resync, break & resume
Please help.
George
Mike Partyka . Technical Engineer [ p. 612 .669 .8268 f. 952 .471 .0409 e. mpartyka@acmn.com ]
To add, if the concern is over network congestion, you can throttle the bandwidth that Snapmirror uses. (without a throttle setting, SnapMirror will take what's available to it...)
This setting can also be set in the snapmirror.conf file using the 'kbs' argument.
See Appliance> snapmirror throttle usage: snapmirror throttle <n> [<filer>:]<dstpath> in which <n> is the new throttle value in KB/s, <dstpath> is <volname> or </vol/volname/qtreename> - modifies the throttle value for the snapmirror transfer to the specified destination
For system-wide throttling (ie: a more permanent solution), check appliance> options replication replication.throttle.enable off replication.throttle.incoming.max_kbs unlimited replication.throttle.outgoing.max_kbs unlimited
-----Original Message----- From: Mike Partyka [mailto:mpartyka@acmn.com] Sent: Monday, June 25, 2007 3:39 PM To: Gupta, Vinay; George Kahler; toasters@mathworks.com Subject: Re: SnapMirror newbie
Starting/Stopping snapmirrors is a very manual process and if your concerned that SnapMirror will be starving your other application data volumes of I/O, CPU, or memory then I would take advantage of a feature called Flexshare, which is new to the 7.2 release. It'll allow you to "prioritize" the workload in several different ways by volume, for example to your questions point, If I had a volume that was serving up Exchange LUN's and the volume containing these LUN's was being snapmirrored to another filer offsite for DR purposes but I never wanted to SnapMirror transfers to take priority over the Exchange clients I would set the "User versus system priority" to give priority to the user workload (exchange clients) over the system workloads (SnapMirror updates).
There is a good article in Tech ONTAP this month that explains this in more detail.
http://www.netapp.com/go/techontap/flexshare.html
I hope this helps
On 6/25/07 1:36 PM, "Gupta, Vinay" Vinay.Gupta@netapp.com wrote:
You can use 'snapmirror abort' to abort the transfer and then restart from where you left off using initialize or update. You can also use 'snapmirror off' to abort all running transfers at once.
Cheers.
Vinay
-----Original Message----- From: George Kahler [mailto:george@yorku.ca] Sent: Monday, June 25, 2007 10:26 AM To: toasters@mathworks.com Subject: snapmirror newbie
Hi, I'm evaluating snapmirror for qtree migration from our existing filers
running 6.5.4P8 to a newly purchased FAS3040 running 7.2.2
I have configured snapmirror and managed to figure out how to do the initial transfer but I can't seem to get the following ... I would like to be able to stop (and resume at a later time) both the initial and any later updates if I find that they are impacting the production
system.
Tried: quiesce, break & resync, break & resume
Please help.
George
Mike Partyka . Technical Engineer [ p. 612 .669 .8268 f. 952 .471 .0409 e. mpartyka@acmn.com ]
Thanks to Vinay Gupta, Mike Partyka and Kevin Parker for their suggestions.
This past long weekend I was able to transfer about 1,050 GB in 30 hrs from a production F840 using the on-board secondary NIC (100 Mbit) to a FAS3040.
Luckily snapmirror did not put that much extra load on the production filer and I did not have to use the "abort".
I did, however, tested it on another QSM and it worked like a charm. Thanks again.
George
On Mon, 25 Jun 2007 13:26:26 -0400 (EDT), George Kahler george@yorku.ca wrote:
Hi, I'm evaluating snapmirror for qtree migration from our existing filers running 6.5.4P8 to a newly purchased FAS3040 running 7.2.2
I have configured snapmirror and managed to figure out how to do the initial transfer but I can't seem to get the following ... I would like to be able to stop (and resume at a later time) both the initial and any later updates if I find that they are impacting the production system.
Tried: quiesce, break & resync, break & resume
Please help.
George
-
Fox, Adam -
George Kahler -
Gupta, Vinay -
Mike Partyka -
Parker, Kevin