?
Solved

SQL 2008 R2 to 2012 Failover Cluster in-place upgrade

Posted on 2013-06-21
3
Medium Priority
?
3,074 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 1050 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 1050 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

Get 15 Days FREE Full-Featured Trial

Benefit from a mission critical IT monitoring with Monitis Premium or get it FREE for your entry level monitoring needs.
-Over 200,000 users
-More than 300,000 websites monitored
-Used in 197 countries
-Recommended by 98% of users

Question has a verified solution.

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

In this article we will learn how to fix  “Cannot install SQL Server 2014 Service Pack 2: Unable to install windows installer msi file” error ?
What if you have to shut down the entire Citrix infrastructure for hardware maintenance, software upgrades or "the unknown"? I developed this plan for "the unknown" and hope that it helps you as well. This article explains how to properly shut down …
This tutorial will walk an individual through the process of configuring basic necessities in order to use the 2010 version of Data Protection Manager. These include storage, agents, and protection jobs. Launch Data Protection Manager from the deskt…
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…

762 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