"Linchi Shea" wrote:

> > Here is the current setup:
> >
> > Current Cluster:
> > NODE01
> > VSQL1\sqlsrv01
> > VSQL1\sqlsrv02
> >
> > NODE02
> > VSQL1\sqlsrv03
> > VSQL1\sqlsrv04
>
> That can't be your current setup. Your current setup is probably more like:
>
> NODE01
> VSQL01\sqlsrv01
> VSQL02\sqlsrv02
>
> NODE02
> VSQL03\sqlsrv03
> VSQL04\sqlsrv04
>
> I'd probably just do a switchover with the current cluster. First, get the
> necessary database files to a staging server. Then, remove the cluster from
> the network. But keep it as your rollback plan. Create two new clusters and
> install SQL instances as follows:
>
> New Cluster 1:
> NODE01 - active
> VSQL01\sqlsrv01
> VSQL02\sqlsrv02
>
> NODE02 - inactive
> ------------------------------------------------
> New Cluster 2:
> NODE01 - active
> VSQL03\sqlsrv03
> VSQL04\sqlsrv04
>
> And finally get the database files from the staging server to their
> respective new servers.
>
> Linchi
>
> "randall_dh" wrote:
>
> > We currently have a (2) node active/active cluster with each node ideally
> > hosting (2) virtual servers and their instances. We want to split the
> > cluster into (2) active/passive clusters and move what normally resides on a
> > given node to it's own cluster. Here is the catch. We have cross
> > server/instances queries/procedures and Access database/queries with the
> > Virtual Server and instance name hard coded, and creating new names isn't
> > really an viable option.
> >
> > Here is the current setup:
> >
> > Current Cluster:
> > NODE01
> > VSQL1\sqlsrv01
> > VSQL1\sqlsrv02
> >
> > NODE02
> > VSQL1\sqlsrv03
> > VSQL1\sqlsrv04
> >
> >
> > And here is the proposed setup::
> >
> > New Cluster 1:
> > NODE01 - active
> > VSQL1\sqlsrv01
> > VSQL1\sqlsrv02
> >
> > NODE02 - inactive
> > ------------------------------------------------
> > New Cluster 2:
> > NODE01 - active
> > VSQL1\sqlsrv03
> > VSQL1\sqlsrv04
> >
> > NODE02 - inactive
> >
> > Can we create the servers in a different domain, moving them to our
> > production domain when testing has been completed? And if so, how do we
> > handle the fact that the VSQLx and named instances already exists in Active
> > Directory? Can the old server just be turned off, the new one brought up and
> > added to the domain by resetting the current domain accounts and re-joining?