"Peter Lindberg" <peter.lindberg@unigrid.se> wrote in message
news:406873b9.247543388@msnews.microsoft.com...
> Thank's for your advice Geoff.
>
> The questions comes after a test install I have done and there was a
> few odd things that happend.
>
> We use Veritas Volume Manager to allow dynamic disc. I'm not involved
> in that part, but the storage techi say's that the veritas code for
> w2k can't handle an upgrade of windows to w2k3 and veritas w2k code
> can't be upgraded to w2k3 version and still running on w2k. That's why
> I want to install w2k3 on new hw with the new codepack from Verirtas.
>
> In our test we run into the following situation:
> On node one where we installed the veritas code we connected to disk
> and then set up the cluster and then the first sql virtual server. At
> that time the other node didn't have the veritas code yet, it only had
> w2k3 and was not part of the ckuster. That means all disk was
> available to node one. That node was installed with a named instance
> where I by the way had to use instruction from KB815431 and sp3a. That
> was after the install of sql2k failed once.
>
> After this we set up the veritas code on the other machine with
> clustersupport and added it to the cluster. We made an error labeling
> one disk with the same name as the other node(cut and paste). When
> changing that we had to uninstall the veritas code and break the
> cluster. On with veritas code again without clustersupport so we get a
> possiblity to chage that label. Then get the node in the cluster
> again.
>
> Here I installed a new virtuel server with a new named instance and
> sp3a on the second node. This setup was without problem and the only
> odd thing was that the dtc service still was automatic.
>
> Next step was to se that the instances could move between the nodes.
> The second node could move to the first, but the first could not move
> to the second. We found out that the first node have the service for
> both instances but the second only the service for the last installed
> instance.
>
> I can't se why this happend.
>
> This is why I'm conserned about adding 2 more nodes after a week. Will
> the initial two be able to move to new once? If the problem I
> described is created by some of my mistake I will still will do this
> upgrade in 2 steps, but if there is this problem we have to reinstall
> the old nodes to w2k3 at the same time.
>
> I will try to recreate it in vmware workstation, but if someone know
> anything about this I will be happy to hear it.
>
> /Peter
>
>
> On Fri, 26 Mar 2004 10:26:22 -0500, "Geoff N. Hiten"
> <SRDBA@Careerbuilder.com> wrotc:
>
> >I actually did a 2 to 4 node cluster upgrade. During the transition, I
> >replaced the original nodes with new hardware, so I went from 2 nodes
with 4
> >procs each to 4 nodes with 8 procs each. I also went from 2 instances to
3
> >instances of SQL server. Here is how I did it.
> >
> >Upgrade the existing nodes (1 at a time) to W2K3. Add the new nodes.
> >Install SQL and Service packs to the new nodes. Fail the cluster over to
> >the new nodes. Remove the old nodes and replace with new hardware. At
this
> >point, I would drop those nodes and rebuild them from scratch. Upgrad
for
> >2003 is good, but I prefer a clean build. Add the new nodes to SQL and
> >apply the service packs. Install the third SQL instance and service
pack.
> >
> >As for your two questions, whenever you add or remove a node, you will
need
> >to use the SQL install CD to add or remove the node from the SQL
> >installation. This is in addition to evicting or adding the node from
the
> >cluster tool. Choose Advanced Options and Maintain Failover Clustering.
> >Read BOL on failover clustering for more details.
> >
> >--
> >Geoff N. Hiten
> >Microsoft SQL Server MVP
> >Senior Database Administrator
> >Careerbuilder.com
> >
> >I support the Professional Association for SQL Server
> >www.sqlpass.org
> >
> >"Peter Lindberg" <peter.lindbergTAKE@AWAYmartinsson.se> wrote in message
> >news:40641e4b.73299028@msnews.microsoft.com...
> >> Hi!
> >>
> >> I have a customer with a 2-node active/active sql2k cluster hosted on
> >> w2k.
> >>
> >> We now want to run this on w2k3 and we also want to build up the
> >> cluster to have a 4-node active/active/active/active sql2k cluster.
> >>
> >> Our plan is to do it in two steps as follow. We take the current 2
> >> nodes offline and unplug them from the network and then install the 2
> >> new nodes with w2k3 using the original ipaddresses and netbiosname and
> >> then restoring the sql2k (one virtuel server and one named instance).
> >> This should give us the same cluster as before but with sql2k running
> >> on w2k3.
> >>
> >> This is because the customer will be able to unplug the new nodes and
> >> replug the old ones if there is any trouble with the new nodes.
> >>
> >> Then after a few days it's time to reinstall the old nodes with w2k3
> >> and new netbiosnames and connect them to the cluster so we get our
> >> 4-node. Then install 2 new named sql instances.
> >>
> >> We want all 4 sql instances to be able to run in all 4 nodes.
> >>
> >> Now some questions!
> >>
> >> When I install a new named instance (on node 3) it will be available
> >> in the other 2 nodes, but will the original sql2k on these 2 nodes be
> >> available in node 3? The same question with node 4.
> >>
> >> Is there some problems with sql2k and w2k3 because it is no way to
> >> uninstall sql2k under MSCS? In w2k I'm able to remove it under the
> >> control panel.
> >>
> >> /Peter
> >>
> >
>

>You can determine which nodes can host which instances. Using the Install
>CD and the Advanced Options tab, you can add or remove individual nodes to a
>particular instance. I added each instance to each new node individually.
>I then added the service pack to the new node/instance. Of course, I
>rebooted each new node after each step, so there are a lot of reboots.
>
>There is a new feature in W2k3 where you can expand basic cluster disks
>without converting them to dynamic disks. That may eliminate the need for
>Veritas Volume Manager.