 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / Other Technologies / Clustering / September 2006Upgrading the cluster Hardware
Hi I've a challenge of upgrading the curent cluster hardware. my current config: node1 and node2 with a vs1\sql1 and vs2\sql2 respectively attached to SAN It's important to keep the same IP address and preferred the instance name because of my ERP database that is on node1 vs1\sql1 option 1: keep same OS which is Windows 2000 advanced server sp4 and sql 2000 sp3 option 2: upgrade to windows 2003 sp1 with sql 2000 sp4 that is my ERP's limitation can't go to sql 2005 my thoughts: 1-Take old cluster OFF Line 2-Create a windows 2003 Cluster 3-Install windows 2003 enterprise sp1 4-Install sql 2000 sp4 instances with same name and different IP address as the old cluster 5-install the basic security patches antivirus ...etc 6-Take offline 7-How Testing would be 8-After ERP is upgraded to supported level 9-Take old cluster offline 10-Change IP address of new cluster to the old cluster IP address 12-System databases ?, can we move locations from old install location , db logs which location to be installed to 13-Can Other databases be detached and reattached to new location, including 14-SAN attached drives how? regards Layth why don't you install your new hardware add this as a 3rd node to your cluster remove 1 old node add another new node to your cluster remove the remaining old node that way, you do not have to take anything off-line > Hi > I've a challenge of upgrading the curent cluster hardware. [quoted text clipped - 25 lines] > regards > Layth let be more precise: - ensure you have a good backup (tested) that should be the first step in every major upgrade / change exercise - add a node 3 on new hardware running Windows 2000 - move your SQL group from node 1 to node 3 - add another node on new hardware running Windows 2000 - move your SQL group from your old node 2 to this node at this point you have a 2 node cluster on new hardware but still running Windows 2000 and your SQL groups are running on the new nodes (to proof that all is configured OK) - move your SQL from (new) node 4 to old node-2 - move your SQL from (new) node 3 to old node-1 you can now do a rolling upgrade to 2003 on node 3 and 4 : see http://technet2.microsoft.com/WindowsServer/en/library/b7d66f43-8d31-4e57-a470-b 7c0f8c5035c1033.mspx?mfr=true - move your groups back to new node 3/4 - evict old node 1/2 rgds, Edwin. > why don't you install your new hardware > add this as a 3rd node to your cluster [quoted text clipped - 36 lines] > > regards > > Layth Of course backup and backup and backup I didn't mention it thinking testing and backup is for granted. But "eyes wide open" can i do a temporary 4 node cluster on windows 2000 advanced server sp4 ? Because if it is that solves lots of problems but I've been told I can't do more two nodes on w2k adv. srv? thanks L. > let be more precise: > [quoted text clipped - 67 lines] > > > regards > > > Layth Sorry Edwin it's a bit late here in New zealand, and it's been a long day I get it now transition but when i put node 3 in shouldn't i remove node 2 first,specially when i need to retin the IP address and node name? regards and thanks L. > Of course backup and backup and backup > I didn't mention it thinking testing and backup is for granted. [quoted text clipped - 77 lines] > > > > regards > > > > Layth my mistake, use the rolling upgrade to go to W2K3 first, then add in nodes > Sorry Edwin > it's a bit late here in New zealand, and it's been a long day [quoted text clipped - 35 lines] > > > you can now do a rolling upgrade to 2003 on node 3 and 4 : > > > see http://technet2.microsoft.com/WindowsServer/en/library/b7d66f43-8d31-4e57-a470-b 7c0f8c5035c1033.mspx?mfr=true > > > - move your groups back to new node 3/4 > > > - evict old node 1/2 [quoted text clipped - 44 lines] > > > > > regards > > > > > Layth why do you need to retain the node name or the IP address of the node, you are retaining the Network name and Network IP address as configured in your cluster, that should be enough for your application r > Sorry Edwin > it's a bit late here in New zealand, and it's been a long day [quoted text clipped - 35 lines] > > > you can now do a rolling upgrade to 2003 on node 3 and 4 : > > > see http://technet2.microsoft.com/WindowsServer/en/library/b7d66f43-8d31-4e57-a470-b 7c0f8c5035c1033.mspx?mfr=true > > > - move your groups back to new node 3/4 > > > - evict old node 1/2 [quoted text clipped - 44 lines] > > > > > regards > > > > > Layth oops my mistake, sorry revers that, first do a rolling upgrade to W2k3-ent (given that your hardware can support) on your existing nodes after that add 2x new node as W2K3 will support 4 nodes then when all is tested and running OK on your new nodes, evict the old ones > Of course backup and backup and backup > I didn't mention it thinking testing and backup is for granted. [quoted text clipped - 27 lines] > > you can now do a rolling upgrade to 2003 on node 3 and 4 : > > see http://technet2.microsoft.com/WindowsServer/en/library/b7d66f43-8d31-4e57-a470-b 7c0f8c5035c1033.mspx?mfr=true > > - move your groups back to new node 3/4 > > - evict old node 1/2 [quoted text clipped - 44 lines] > > > > regards > > > > Layth I kind of like the option where you evect one node and put in another w2k3 nodes2 with node1 still on w2k and then when all is ok repeat for node 1. that way i can roll back easier to the old node2 if it fails? " not sure". and then do node1. that way i have a clean install w2k3 with i want installed on it. I am relying on the link that you provided and trying to establsih a solid plan. actually my ERP relys on the SQL servers ip address and not the cluster name or ip address, it can be done but it's just a major exercise to change another 6 servers direction to the database that is on node1. regards Layth > oops my mistake, sorry > [quoted text clipped - 97 lines] > > > > > regards > > > > > Layth Hi Layth, You want to be sure that MS Clustering can cope with running a W2K node as well as a W2K3 node. What I would recommend is: 1 - Build your two new servers with a fresh OS (same level as what you are running now), patched and firmware all up to date. 2 - Once all your hardware is ready, fail everything to the node2 3 - Evict node 1 from the cluster 4 - Add the new hardware, and add it is a new node 5 - Once testing has proven everything is ok on the new node, fail everything back to the new node, and repeat the process for node 2. Then once this is done, you can look at how you attack the OS, SQL, and ERP upgrade. I don't recommend you try and tackle everything at one time, it's a huge risk, adds immense complexity, and also if something goes wrong you're not going to know what went wrong, and you're also going to have a HUGE roll back. Hope that helps? Reece Mitchell. > I kind of like the option where you evect one node and put in another w2k3 > nodes2 with node1 still on w2k and then when all is ok repeat for node 1. [quoted text clipped - 111 lines] > > > > > > regards > > > > > > Layth >I kind of like the option where you evect one node and put in another w2k3 > nodes2 with node1 still on w2k and then when all is ok repeat for node 1. [quoted text clipped - 7 lines] > or ip address, it can be done but it's just a major exercise to change > another 6 servers direction to the database that is on node1. The whole idea of a "virtual" server is that you can have the IP Address resource easily remain the current IP and not have to change anything on your ERP side. Yes, the best solution is most likely evicting one node, adding in a Win2K3 node, moving all resources to it, then evicting the other Win2K node and adding a Win2K3 node.  SignatureRuss Kaufmann MVP - Windows Server - Clustering ClusterHelp.com, a Microsoft Certified Gold Partner Web http://www.clusterhelp.com Blog http://msmvps.com/clusterhelp The next ClusterHelp classes are: Denver starting Nov 14th NYC starting Dec 4th. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.