Can I do rolling upgrade of active-active SQL cluster

Hi,
We have an active-active cluster where SQL server instances are created on
node 1 and Analysis services are installed on node 2. We need to upgrade the
H/W for both nodes? Can I do a rolling upgrade i.e. replacing one node at
time in above configuration?
If not then what are my options & if yes then can you give me some links to
documentation on how to do this?
Thanks,
Sushil
Sushil
Yes you can. I have done exactly this type of project. The more you plan
and test, the better your chance of success. I don't have any publicly
available documentation on a rolling upgrade.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Sushil" <Sushil@.discussions.microsoft.com> wrote in message
news:EA4D680F-4548-4536-8BD2-88ECE1004CF8@.microsoft.com...
> Hi,
> We have an active-active cluster where SQL server instances are created on
> node 1 and Analysis services are installed on node 2. We need to upgrade
> the
> H/W for both nodes? Can I do a rolling upgrade i.e. replacing one node at
> time in above configuration?
> If not then what are my options & if yes then can you give me some links
> to
> documentation on how to do this?
> Thanks,
> --
> Sushil
> --
> Sushil
|||Geoff,
Thanks for response. Can you please list if you had any challenges while
doing this?
I have been told that, When we replace node 2 by new node (Just with OS)
and install SQL server on this new node and try to cluster this new node
with OLD node 1 then that clustering will not work.
Can you point me any Microsoft documentation or books where I can get some
clues?
Thanks,
Sushil
Sushil
"Geoff N. Hiten" wrote:

> Yes you can. I have done exactly this type of project. The more you plan
> and test, the better your chance of success. I don't have any publicly
> available documentation on a rolling upgrade.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Sushil" <Sushil@.discussions.microsoft.com> wrote in message
> news:EA4D680F-4548-4536-8BD2-88ECE1004CF8@.microsoft.com...
>
>
|||Here is the quick version.
Starting with SQL 2000 2-node (4-Proc DELL) connected to DELL | EMC CX-600.
Windows 2000 OS. 2 SQL Instances.
Ended with SQL 2000 4-node (8-proc Unisys) still connected to the same SAN
(expanded the storage capacity, though). Windows 2003 OS. 3 SQL Instances.
Started with in-place upgrade of OS (one node at a time). Obtaining the
correct drivers for the HBAs was a challenge. This was Q4 '03, so that
shouldn't be a problem, but it is a critical step.
Added the two new nodes. When stable, removed original two nodes. Finally
added the remaining new nodes.
Note that if you have a SCSI based cluster, you cannot have more than two
nodes even with Windows 2003.
Again, planning and testing was essential. Each step had numerous tests and
bailout plans to avoid downtime.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Sushil" <Sushil@.discussions.microsoft.com> wrote in message
news:97D3A989-1C04-450C-B3C4-20F674299E09@.microsoft.com...[vbcol=seagreen]
> Geoff,
> Thanks for response. Can you please list if you had any challenges while
> doing this?
> I have been told that, When we replace node 2 by new node (Just with OS)
> and install SQL server on this new node and try to cluster this new node
> with OLD node 1 then that clustering will not work.
> Can you point me any Microsoft documentation or books where I can get some
> clues?
> Thanks,
> Sushil
>
> --
> Sushil
>
> "Geoff N. Hiten" wrote:
|||I have a thought rolling around in my brain about limitations of the number
of nodes being different between WIn2K and Win2K3...but I can't remember the
specifics. Geoff, can you recall or am I off-base (anymore than usual?)
Kevin Hill
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.expertsrt.com - not your average tech Q&A site
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OF3pKh0MGHA.4052@.TK2MSFTNGP15.phx.gbl...
> Here is the quick version.
> Starting with SQL 2000 2-node (4-Proc DELL) connected to DELL | EMC
> CX-600. Windows 2000 OS. 2 SQL Instances.
> Ended with SQL 2000 4-node (8-proc Unisys) still connected to the same SAN
> (expanded the storage capacity, though). Windows 2003 OS. 3 SQL
> Instances.
> Started with in-place upgrade of OS (one node at a time). Obtaining the
> correct drivers for the HBAs was a challenge. This was Q4 '03, so that
> shouldn't be a problem, but it is a critical step.
> Added the two new nodes. When stable, removed original two nodes.
> Finally added the remaining new nodes.
> Note that if you have a SCSI based cluster, you cannot have more than two
> nodes even with Windows 2003.
> Again, planning and testing was essential. Each step had numerous tests
> and bailout plans to avoid downtime.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Sushil" <Sushil@.discussions.microsoft.com> wrote in message
> news:97D3A989-1C04-450C-B3C4-20F674299E09@.microsoft.com...
>
|||Windows 2000 Enterprise Edition supports 2 nodes. Windows 2003 supports up
to 8 nodes, but SQL 2000 Enterprise Edition only supports a maximum of 4
nodes so that is the limit. That is why I had to do an in-place OS upgrade
as a beginning step for this process. I normally don't like in-place
upgrades, but this was only for a short time during a transition.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kevin3NF" <Kevin@.DontNeedNoSpam3NF-inc.com> wrote in message
news:eP$dgeWNGHA.1192@.TK2MSFTNGP11.phx.gbl...
>I have a thought rolling around in my brain about limitations of the number
>of nodes being different between WIn2K and Win2K3...but I can't remember
>the specifics. Geoff, can you recall or am I off-base (anymore than
>usual?)
> --
> Kevin Hill
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
> www.expertsrt.com - not your average tech Q&A site
>
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:OF3pKh0MGHA.4052@.TK2MSFTNGP15.phx.gbl...
>