Re: Moving a 4 node cluster in two pairs?

"John Stoffel" <[email protected]>
Newsgroups gmane.comp.hardware.netapp
Message-ID <[email protected]>
>>>>> "tmac" == tmac  <[email protected]> writes:

tmac> Another idea would be to use SVM-DR

I don't think that will work for us...

tmac> Setup a cluster peer. Then create the destination SVM and create
tmac> a vserver peer between the source and destination.  If you do
tmac> not wish to mirror all volumes, I believe there is a per-volume
tmac> option you can modify to prevent an unwanted snapmirror
tmac> relationship in the SVM-DR.  If the networking is the same
tmac> between both locations, you can even allow the SVM-DR to copy
tmac> the identity (LIFs, Addresses, etc)

So I'd first have to move all the volumes onto one pair, split off the
other pair, set it up as a standalone... the do the SVM-DR
setup... swing things over.  Hmm... tempting.

Except a bunch of networking needs to change, and we can't run current
networks in two seperate DCs.  Blech.  

tmac> You could then "cut over" to the new location and use it.

tmac> Make sense?

tmac> --tmac

tmac> Tim McCarthy, Principal Consultant

tmac> Proud Member of the #NetAppATeam

tmac> I Blog at TMACsRack

tmac> On Wed, Mar 3, 2021 at 2:22 AM Sebastian P. Goetze <[email protected]> wrote:

tmac>     just to add to Heino: I had a student in one of my courses just lately, that moved his
tmac>     datacenter some 4-5 km with exactly this setup (4 cluster switches and good redundant
tmac>     connectivity) and some swing gear, if I remember correctly, because he didn't have enough
tmac>     capacity to completely evacuate a pair before the move. Completely non-disruptive, nobody
tmac>     noticed anything...
   
tmac>     Sebastian

tmac>     sent from my mobile, spellchecker might have messed up...
   
tmac>     On Tue, 2 Mar 2021, 19:36 Heino Walther <[email protected]> wrote:

tmac>         Hi John
       
tmac>          
       
tmac>         I’m not sure if this helps…
       
tmac>         I am also sure you can get the cluster running with half the nodes.
       
tmac>         I am actually migrating between two HA-pairs as we speak.
       
tmac>         We choose to setup a link between the nodes with two cluster switches, so the two HA-pairs
tmac>         is about 500M apart… (I’m not sure when latency becomes an issue)
       
tmac>         But what we did was to add the two new nodes (temporary nodes) to the existing cluster,
tmac>         and we are then able to use the “vol move” operation to move volumes from one HA-pair to
tmac>         another, and of cause also the LIFs.
       
tmac>         Works a charm so far.  Huge NFS datastores have been moved with a hitch.
       
tmac>         We did a “vol move start” with the “-cutover-action wait” option, which does the mirroring
tmac>         but waits until we tell it to do the cut-over… (in a service window)
       
tmac>         There is however some “dedupe processes” which makes the cut-over very slow on larger
tmac>         volumes… it keeps telling us that it is waiting for a dedupe process to complete… (both
tmac>         systems are AFFs)…. But after 10-30 minutes it completes OK.
       
tmac>          
       
tmac>         Once we have emptied the source HA-nodes, we will move them to the new DC, and do it all
tmac>         over again back to the original system again…
       
tmac>          
       
tmac>         So far no down time at all, which is nice 😊
       
tmac>          
       
tmac>         I realize that you may not be a lucky as to where you have to move the systems 😉
       
tmac>         So drive safely, and if you are running spinning disks, be prepared to replace a few as
tmac>         you startup the system 😉
       
tmac>          
       
tmac>         /Heino
       
tmac>          
       
tmac>         Fra: Toasters <[email protected]> på vegne af John Stoffel <[email protected]>
tmac>         Dato: tirsdag, 2. marts 2021 kl. 19.24
tmac>         Til: [email protected] <[email protected]>
tmac>         Emne: Moving a 4 node cluster in two pairs?

tmac>         Guys,
tmac>         We're getting ready to move our 4 node FAS8060 cluster to a new data
tmac>         center.  As part of our due diligence, we're thinking that we would
tmac>         snapmirror the most critical business volumes between the two pairs.
       
tmac>         The idea would be that if the truck holding pair A+B doesn't make it
tmac>         for some reason, we can still bring up the cluster with nodes C+D and
tmac>         still have those snapmirrored volumes available to continue working.
       
tmac>         So my questions are:
       
tmac>         1. Can I boot a cluster with half the nodes missing?  I'm sure I
tmac>            can...
       
tmac>         2. Has anyone else had to do this half assed method of shipping DR?
       
tmac>         Cheers,
tmac>         John
tmac>         _______________________________________________
tmac>         Toasters mailing list
tmac>         [email protected]
tmac>         https://www.teaparty.net/mailman/listinfo/toasters
       
tmac>         _______________________________________________
tmac>         Toasters mailing list
tmac>         [email protected]
tmac>         https://www.teaparty.net/mailman/listinfo/toasters
   
tmac>     _______________________________________________
tmac>     Toasters mailing list
tmac>     [email protected]
tmac>     https://www.teaparty.net/mailman/listinfo/toasters

tmac> _______________________________________________
tmac> Toasters mailing list
tmac> [email protected]
tmac> https://www.teaparty.net/mailman/listinfo/toasters

_______________________________________________
Toasters mailing list
[email protected]
https://www.teaparty.net/mailman/listinfo/toasters
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.