"Heino" == Heino Walther hw@beardmann.dk writes:
Heino> We are in the process of migrating from an AFF8060 to an AFF220.
Heino> We have attached two CN1610 switches and we have started to Heino> migrate several volumes over… (NFS and CIFS)
Heino> Because we want to do the cut-over in a service window we have Heino> done it with the command:
Heino> volume move start -vserver vserver -volume volme -cutover-action wait
Heino> We currently have 10 volumes waiting.
Why are you waiting? Are they *that* active that users will notice the cutover interruption?
Heino> Users has started to complain about poor performance…
Heino> I think this is due to the fact that the volume move while in Heino> “wait” status does a snapshot every minute, and updates the Heino> mirror.
Ugh, this is a new feature I don't see in my 9.3 cluster...
Heino> (I can verify this with a “snapshot show”..
Heino> Is there a way to modify this, so that it does not update so often?
Heino> Of cause when we get closer to our service window we would like Heino> to set it back to 1 minute again…
Heino> There is a “volume move pause” but I would rather modify the Heino> frequency of the snapmirror updates if possible?
Again, why wait? I've always found that the cutover impact is mostly from the cloning onto the new destination, not the cutover.
But are you adding the AFF220 into the existing cluster, or just doing snapmirrors? It implies it's all one big cluster now... so why wait for the window?
John