Re: [EXTERNAL] Moving a 4 node cluster in two pairs?
"John Stoffel" <[email protected]>
| Newsgroups | gmane.comp.hardware.netapp |
|---|---|
| Message-ID | <[email protected]> |
>>>>> "Scott" == Scott Miller <[email protected]> writes: Scott> why not vol move everything to one pair, then remove the other Scott> pair from the cluster. make a new 2-node cluster, snap mirror Scott> everything, then ship. then re-make the 4 node cluster once Scott> you safely arrive at the destination. That might be an option, if we have enough space on the cluster. But we might only snapmirror the critical stuff and pray on the rest. Scott> or, ship the temp 2-node pair first, *then* snapmirror Scott> everything to it (requires a decent WAN) so the data is known Scott> safe at the destination before you move the origin cluster. It's certainly an idea. Scott> On Tue, Mar 2, 2021 at 10:25 AM John Stoffel <[email protected]> wrote: Scott> Guys, Scott> We're getting ready to move our 4 node FAS8060 cluster to a new data Scott> center. As part of our due diligence, we're thinking that we would Scott> snapmirror the most critical business volumes between the two pairs. Scott> The idea would be that if the truck holding pair A+B doesn't make it Scott> for some reason, we can still bring up the cluster with nodes C+D and Scott> still have those snapmirrored volumes available to continue working. Scott> So my questions are: Scott> 1. Can I boot a cluster with half the nodes missing? I'm sure I Scott> can... Scott> 2. Has anyone else had to do this half assed method of shipping DR? Scott> Cheers, Scott> John Scott> _______________________________________________ Scott> Toasters mailing list Scott> [email protected] Scott> https://www.teaparty.net/mailman/listinfo/toasters