Thinking through this logically (in my mind anyway)

place new heads on old 8000-based cluster.

If acquired, new storage as well.

setup cluster peering and then vserver peering and establish mirrors.

Mirror old storage to peer

Schedule time and cut over.

In 8.3, there may be a better way. You could setup SVM replication and do a permanent failover of the SVM.

Bottom line, I believe it is possible.

Is there a well documented procedure? I would guess (at least) not (yet).

--tmac

Tim McCarthy

Principal Consultant

On Tue, Jul 21, 2015 at 6:41 AM, Borzenkov, Andrei <andrei.borzenkov@ts.fujitsu.com> wrote:

No procedure is known today. The only possibility is to evacuate data and reinitialize node(s) in new cluster. As long as you have enough space in cluster2 you could do SVM migration to preserve configuration.

From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Milazzo Giacomo
Sent: Tuesday, July 21, 2015 1:30 PM
To: Toasters
Subject: Cluster evolution

Hi everybody,

suppose that for technical (i.e. a 3240HA controller pair that does not fit with a 8060HA one in the same cluster) reason I’ve to start with two different 2 nodes cluster, each of the two managing its respective aggregates and node.

So I can have now:

CLUSTER1-01 and CLUSTER1-02 (3240HA) and CLUSTER2-01 and CLUSTER2-02 (8060HA)

In the future customer could have budget to do a tech refresh on the first cluster changing the heads to an 8000 pairs.
Well, what’s about the merge of the CLUSTER1 nodes to the CLUSTER2 preserving all data in CLUSTER1 aggregates? So I mean that I would have in the end a 4 nodes cluster and not two separate 2 nodes ones.

Is there some procedure?

Regards.

_______________________________________________
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters