Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
bakerjon
Posting Yak Master
145 Posts |
 Posted - 2005-03-15 : 14:23:54
|
I'm currently working on a project to upgrade a production Win2k/SQL2k cluster to Win2k3. It is the standard for the customer to perform clean installs for OS upgrades (no upgrade in place). I think I know the basic steps (evict, rebuild, rejoin, etc.), but I'm a little fuzzy on some of the details, such as - MSDTC setup/upgrade - I already have MSDTC installed with Win2k (comclust.exe). I know there are different configs for Win2k3 MSDTC in the cluster. What do I need to do to upgrade to Win2k3 when I bring the first 2k3 node into the cluster?
- SPs and Hotfixes - I have SQL replication in place. The current security hotfix (.818) is also installed. When I bring the new node into the cluster, I have to install SP3a and the .818 hotfix to bring the binaries up to date on the new node. However, hotfix .818 fails whenever I run it a second time on a replicated system, throwing PK and FK violations on system tables. Microsoft Support did not provide help with these errors, but gave a great response like, "It's a hotfix, what do you expect."
 To remedy this bad state, I'm restoring master, which, of course means cluster downtime and business outage.  Has anyone done this differently/successfully? - Our storage is HP EVA 3000 SAN. We have had issues with volumes snapping between Win2k and Wink2k3 (both directions, known issue from HP). I'm concerned about a fail-over in a mixed mode cluster (will it work, will it always work, will my data corrupt). Info from HP is trickling in and we can't get a definitive answer.
The good news is that I have a lab environment to test this in. The bad news is that I have to be done this week with my testing. I don't want to flounder in the lab, rather I need to nail down my upgrade process quickly. Any help you can provide is greatly appreciated.Thanks in advance,Jon BakerEvergreen Consulting ofCentral Ohio, Inc.What's with the yak thing? |
|
|
MichaelP
Jedi Yak
2489 Posts |
Posted - 2005-03-15 : 15:45:52
|
| MSDTC That was really ticky with W2k3.With our install, I believe that we had to create a small LUN just for MSDTC. Read the MS KB articles about setting up the MSDTC in a Win2k3 cluster, and they should tell you everything except that you should have a small LUN just for DTC.BTW, I'd highly suggest against an "upgrade." A Clean install would be best, esp. with clustering. I couldn't 100% tell if that was teh direction or not, but I thought I'd chime in about that.I can't help you with the other issues. Sorry.Michael<Yoda>Use the Search page you must. Find the answer you will.</Yoda> |
 |
|
|
bakerjon
Posting Yak Master
145 Posts |
Posted - 2005-03-15 : 16:01:39
|
To confirm, we are planning to rebuild each node. There will be no "upgrade" of Windows, but rather a clean install.quote:
Originally posted by MichaelP
MSDTC That was really ticky with W2k3.With our install, I believe that we had to create a small LUN just for MSDTC. Read the MS KB articles about setting up the MSDTC in a Win2k3 cluster, and they should tell you everything except that you should have a small LUN just for DTC.BTW, I'd highly suggest against an "upgrade." A Clean install would be best, esp. with clustering. I couldn't 100% tell if that was teh direction or not, but I thought I'd chime in about that.I can't help you with the other issues. Sorry.Michael<Yoda>Use the Search page you must. Find the answer you will.</Yoda>
What's with the yak thing? |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2005-03-15 : 21:45:43
|
HP doesn't support win2k3.  we had that problem when we tried the clean install and upgrade, what a mess. finally getting hold someone from HP, some drivers are not supported for win2k3 and was advised to stick to win2k. --------------------keeping it simple... |
|
|
|
MichaelP
Jedi Yak
2489 Posts |
Posted - 2005-03-15 : 23:57:13
|
| We are running an IBM FastT200 SAN with our Win2k3 Cluster. Runs great!I have experience with EMC and IBM low end SAN's. I gotta say I like the IBM's better.Michael<Yoda>Use the Search page you must. Find the answer you will.</Yoda> |
|
|
|
bakerjon
Posting Yak Master
145 Posts |
Posted - 2005-03-16 : 09:05:02
|
Our hardware configuration is supported by HP.quote:
Originally posted by jen
HP doesn't support win2k3. we had that problem when we tried the clean install and upgrade, what a mess. finally getting hold someone from HP, some drivers are not supported for win2k3 and was advised to stick to win2k. --------------------keeping it simple...
What's with the yak thing? |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2005-03-17 : 05:26:32
|
| and have you tried doing the upgrade or clean install?--------------------keeping it simple... |
|
|
|
bakerjon
Posting Yak Master
145 Posts |
Posted - 2005-03-18 : 16:47:57
|
Well, I just dove in with the testing. Node 1 has been evicted and rebuilt as Windows 2003. I joined it back in to the cluster and SQL Server with all SPs and patches without issue. That has me a little flumoxed, but I'll deal with the fact that I got no errors this time Now I'm stuck with MSDTC that doesn't work. It was in the cluster group with Windows 2000 (comclust). I didn't realize it wasn't working until I evicted the 2nd 2000 node.I then realized that I did not Network Enable DTC (duh!). So I flipped that switch, deleted MSDTC, and set it up in it's own group with a disk, IP and Name as recommended for Win2k3. Still no luck.I'm testing MSDTC with SQL Server BEGIN DISTRIBUTED TRANSACTION and running a SELECT through a Linked Server. This works on other non-clustered machines as expected. When I run the command, SQL Server says Server: Msg 7391, Level 16, State 1, Line 2The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction.[OLE/DB provider returned message: New transaction cannot enlist in the specified transaction coordinator. ]OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x8004d00a].Last ditch, I'm giving it the ol' 3 finger salute to see what happens...OK, now I get a different error stating Server: Msg 8501, Level 16, State 3, Line 1MSDTC on server 'NOTLEOPARD' is unavailable.Going back through the config again...Although I enabled Network DTC Access earlier, when I verified it again, it wasn't checked. So I checked it again, rebooted, stopped and started SQL Server. Verified Network DTC Access Again, but still not enabled. I went through the enable proccess again, reboot, restarted SQL Server, NOW IT WORKS!!!!! WOOOOHOOOOOOO!!!!!!BTW...I also checked Enable COM+ Network Access. Not sure if I need this, but I added it since our Apps use COM+. Any info that anyone can provide, I would appreciate it!On with the other node rebuild! Wish me luck!!! This looks like a good blog entry waiting to happen...quote:
Originally posted by jen
and have you tried doing the upgrade or clean install?--------------------keeping it simple...
What's with the yak thing? |
|
|
|
bakerjon
Posting Yak Master
145 Posts |
Posted - 2005-04-06 : 14:13:28
|
| Quick update on this for anyone who cares. When I joined the other node to the cluster MSDTC blew up again. I gave up and called PSS. Come to find out it was a corrupted NetMon driver. Installing RASDIAG.EXE replaced the driver and fixed the problem. This was likely due to the fact that MSDTC was not network enabled before being added to the cluster. Just thought I would provide more detail in case others bump into this like I did...JonNow I know, and knowing is half the battle!http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=48013 |
|
|
|
|
|
|
|
|
Win2k/S2k -> Win2k3 Cluster Upgrade Clean Install