Solved

SQL 2008 R2 to 2012 Failover Cluster in-place upgrade

Posted on 2013-06-21
3
2,980 Views
Last Modified: 2013-06-24
Hi!

I'm planning to do an in-place upgrade of our SQL 2008 R2 Failover Cluster to 2012. If any of you have done this already, would you care to share?

Steps I've in mind:
1. Pause or evict (?) the passive node from the cluster
2. Upgrade Windows 2008 R2 to Windows 2012 - reboot the server?
3. Upgrade SQL 2008 R2 to SQL server 2012
4. Restart the node
5. Make sure Failover Cluster settings are intact.
6. Failover cluster to this passive node (passive will then become active node)
7. Repeat #1 - 5 until the other node is upgraded
8. Test failover and failbacks few times.
9. Check database connectivity
10. Finish!

There may be some steps in between the above steps to carry out that I have no knowledge about. Please let me know what they are!

Thanks, Sharad
0
Comment
Question by:sharad_rai
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 8

Assisted Solution

by:didnthaveaname
didnthaveaname earned 350 total points
ID: 39266368
I would take a look at this article first and foremost: http://technet.microsoft.com/en-us/library/ms191295.aspx - looks like you can do rolling upgrades relatively painlessly.
1
 

Author Comment

by:sharad_rai
ID: 39266419
Thanks, the link is pretty useful.
What is the suggested method of backing up the nodes before going into the upgrade cycle?

- Sharad
0
 
LVL 8

Accepted Solution

by:
didnthaveaname earned 350 total points
ID: 39266976
I would imagine you just back up all of the databases on the passive nodes before you upgrade them (since the upgrade will upgrade the databases).  Technically speaking, you'll never be upgrading an active node, since you'll failover to an upgraded node before you upgrade the active node.

Where the link I posted gets me to thinking is where it mentions that upgraded nodes don't participate in the cluster until the cluster resource group ownership is moved to an upgraded  node, which, by default, automatically occurs during the upgrade of the next node after half of the nodes have been upgraded.  If this is a 2-node cluster, I would imagine there is going to be some manual intervention required.  I am, unfortunately, not going to be of a whole lot of use on the specifics as I avoid clusters like the plague (definitely intrigued by the 2012 availability groups, however).
0

Featured Post

Salesforce Made Easy to Use

On-screen guidance at the moment of need enables you & your employees to focus on the core, you can now boost your adoption rates swiftly and simply with one easy tool.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The following article is comprised of the pearls we have garnered deploying virtualization solutions since Virtual Server 2005 and subsequent 2008 RTM+ Hyper-V in standalone and clustered environments.
I have a large data set and a SSIS package. How can I load this file in multi threading?
Viewers will learn how to use the INSERT statement to insert data into their tables. It will also introduce the NULL statement, to show them what happens when no value is giving for any given column.
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…

729 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question