February 4, 2013 at 7:34 am
Hi everyone,
we had to Upgrade RAM to our Servers running on Windows Server 2008 32 Bit. In Order to use it, we had to reinstall Windows Server OS 2008 R2 in 64Bit. Now we reinstalled the passive node, but I can't access the shared volumes any more. What can I do now to install the passive node so far, that I can swicht it active an reinstall the other Server? Can I readd the newly installed srv to the cluster or do I have to build up a second cluster? Anyone of you did this before?
Greetz and thanks in advance
sql pizza
Greetz
Query Shepherd
February 4, 2013 at 11:58 am
What OS did you upgrade from?
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
February 5, 2013 at 1:04 am
Hi Jeffrey,
thanks for your answer. I thought it's all in the text...
...we had Windows Server 2008 Enterpise 32Bit which we upgraded to 2008 R2 64Bit.
Greetz
sql pizza
Greetz
Query Shepherd
February 5, 2013 at 3:26 am
When you install SQL on the passive node you do not need to access the shared drives. If you are using a command-line install, you should use ACTION=ADDNODE to tell SETUP that you are adding a node to an existing SQL cluster.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
February 5, 2013 at 3:32 am
Ok. But the real question is, if I would need some of the clustered virtual volumes though, which are at the moment bound to the old cluster, how could I access it from the newly built cluster in parallel?
Greetz
Query Shepherd
February 5, 2013 at 3:41 am
You cannot share volumes between different Windows clusters. Each Windows cluster needs its own set of shared volumes.
You can add new nodes to an existing Windows cluster. It may be possible to mix 32-bit and 64-bit nodes on the same cluster, but I have not tried it. However, if this is successful, you should then be able to install SQL 64-bit on your new nodes. If this works, then you can fail over from the 32-bit node to the 64-bit node and evict the 32-bit node from the cluster. Ultimately you will have a cluster using only 64-bit nodes that can access all the memory on those nodes.
If you are running SQL 2012 RTM or below, all the nodes in the cluster must use the same operating system. With SQL 2012 SP1 and above, you can add a Windows 2012 node to a Windows 2008 R2 cluster, and ultimately migrate the cluster to Windows 2012.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
February 6, 2013 at 9:58 am
EdVassie (2/5/2013)
If you are running SQL 2012 RTM or below, all the nodes in the cluster must use the same operating system. With SQL 2012 SP1 and above, you can add a Windows 2012 node to a Windows 2008 R2 cluster, and ultimately migrate the cluster to Windows 2012.
Ed, can you point me to some documentation on this? I found documentation on cross cluster migration of availability groups but that is a very different thing than allowing mixed nodes.
February 6, 2013 at 10:01 am
All of the SQL Server instances must be on SQL 2012 SP1 for this to work. You cannot mix SQL Server versions. However, you should be able to migrate Windows from W2008 R2 to W2012.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
February 6, 2013 at 10:38 am
Thanks for clarifying that Ed. I have to read more carefully and stop getting SQL 2008R2 vs. Windows 2008R2 mixed up in my head.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply