If your disks are on SAN, you can also just create a new and separate
cluster, install SQL Server exactly the same as the old cluster, remove the
shared drives from the old cluster, remove the shared drives from the new
cluster, and present the drives from the old cluster to the new cluster,
making sure the drive letters are assigned the same.
If you can afford the down time during the switch, this gives you an
alternative approach. Another problem of this approach is that you'll end up
with new IP addresses and new network names.
Linchi
[quoted text, click to view] "Ole Thomsen" wrote:
> I will have to move a 2-node SQL2005 MSCS cluster to new servers.
>
> Wonder if I could just
>
> - remove node1 from cluster
> - add node3 to cluster
> - remove node2 from cluster
> - add node4 to cluster
>
> Is this a valid plan?
>
> Ole Thomsen
>
Well, the change had to be transparent to users and network, so I chose the
"rolling swap".
Thanks,
Ole Thomsen
[quoted text, click to view] "Linchi Shea" <LinchiShea@discussions.microsoft.com> wrote in message
news:52FD2AC7-D375-4428-8828-AC4EA58027BB@microsoft.com...
> If your disks are on SAN, you can also just create a new and separate
> cluster, install SQL Server exactly the same as the old cluster, remove
> the
> shared drives from the old cluster, remove the shared drives from the new
> cluster, and present the drives from the old cluster to the new cluster,
> making sure the drive letters are assigned the same.
>
> If you can afford the down time during the switch, this gives you an
> alternative approach. Another problem of this approach is that you'll end
> up
> with new IP addresses and new network names.
>
> Linchi
>
> "Ole Thomsen" wrote:
>
>> I will have to move a 2-node SQL2005 MSCS cluster to new servers.
>>
>> Wonder if I could just
>>
>> - remove node1 from cluster
>> - add node3 to cluster
>> - remove node2 from cluster
>> - add node4 to cluster
>>
>> Is this a valid plan?
>>
>> Ole Thomsen
>>
>>
I discovered the hard way that SQL uninstall in 2005 means uninstall BOTH
nodes (just like install is on both) :-)
Otherwise the swap went fine, just a bit more downtime than expected and a
restore of system databases at the end.
Ole Thomsen
[quoted text, click to view] "Geoff N. Hiten" <SQLCraftsman@gmail.com> wrote in message
news:uI6XC8K3GHA.1588@TK2MSFTNGP02.phx.gbl...
> Yes. But it is a bit more complex.
>
> Uninstall SQL from Node1.
> Evict Node1 from the cluster.
> Add Node3 to the cluster
> Install SQL to node 3
> Test, Test, Test
> Uninstall SQL from Node2.
> Evict Node2 from the cluster.
> Add Node4 to the cluster
> Install SQL to Node 4
> Test, Test, Test again.
>
> I have done this process using SQL 2000 and it works. I haven't tested it
> with SQL 2005, but the basic steps should not have changed.
>
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Ole Thomsen" <ot@networks.dk> wrote in message
> news:OOzYBSK3GHA.1068@TK2MSFTNGP05.phx.gbl...
>>I will have to move a 2-node SQL2005 MSCS cluster to new servers.
>>
>> Wonder if I could just
>>
>> - remove node1 from cluster
>> - add node3 to cluster
>> - remove node2 from cluster
>> - add node4 to cluster
>>
>> Is this a valid plan?
>>
>> Ole Thomsen
>>
>
>
