Solved

Error 1205 in event viewer when adding a 3rd node to Windows 2012 cluster

Posted on 2013-12-05
5
685 Views
Last Modified: 2013-12-21
We have a pair of local nodes (within same VLAN/site) that are
in a cluster.  On one of the two nodes, we used Failover Cluster
Manager's  "Add Node" to add a 3rd node from a remote datacentre
(after permitting firewall rules as recommended by MS) into the
cluster & the 3rd node came online in the cluster but somehow the
2 local nodes' D:, F:, G: H: drives became 'reserved' & if we issue
'dir drive:', it says could not find drive path.

Windows Explorer also can't open those drives & our SQL services
hosted on the cluster became unavailable: four disks resources
appear under Failover Cluster Manager's  -> Resources -> Disks
as Offline/Failed.

To recover back the MS SQL services/Db, we have to 'evict' this  3rd
node & 'Remove' those four disk resources using Failover Cluster
Manager, then use Disk Management to 'Online' back those D, F,
G, H drives.

Now we need to know the root cause of this phenomenon as we
would still like to add the 3rd node again.

One colleague casually remarked that we need to 'unconfigure'
those D, F, G, H drives : anyone has any idea on what's the root
cause & any links that tell us to unconfigure the local nodes' drives?
0
Comment
Question by:sunhux
  • 3
  • 2
5 Comments
 

Author Comment

by:sunhux
ID: 39698089
I guess the C: drive was still accessible as the local nodes'
Win2012 OS is locking it
0
 
LVL 28

Assisted Solution

by:Ryan McCauley
Ryan McCauley earned 500 total points
ID: 39701320
Are the D/F/G/H drives part of the cluster resources? If you've got a clustered instance of SQL Server installed to those drives, then they're part of the cluster and their ownership is controlled by the cluster. However, just adding a third node to the cluster shouldn't do anything with ownership - you'd have to mark that those drives are able to be owned by the new cluster node before you could move ownership.

Does the new node already have drives on those letters, or just a C drive? Did you do anything else when you added the node that may have caused your SQL instance to go offline, or did you just add the node to your cluster and that's it?
0
 

Author Comment

by:sunhux
ID: 39703192
> Are the D/F/G/H drives part of the cluster resources?
No, they are not.

> just adding a third node to the cluster shouldn't do anything with ownership
That's what I thought too because we ever did the same thing at another
site too (with the same types of VM db servers running Win2012) & did not
 encounter such issue.

> Does the new node already have drives on those letters, or just a C drive?
Yes, the 3rd (ie the new) node have drives on those letters too as the 3rd
node is also an MS AAG (Always-On Availability Group) that hosts the same
set of databases, thus we assign all 3 nodes the same drives letters ie
D:Apps binaries  F: Master  G: Data etc


> Did you do anything else when you added the node that may have caused
> your SQL instance to go offline, or did you just add the node to your cluster
> and that's it?
As far as I'm aware, I just add the 3rd node to the cluster & that's it.
Hmm, I'm beginning to wonder if this problem had pre-existing before
I added the 3rd node but that's unlikely as the DB is being used daily
by the application developers.

What if the 3rd node has a Vote that is rather high & sort of upset the
cluster quorum?  Is this scenario likely?
0
 
LVL 28

Accepted Solution

by:
Ryan McCauley earned 500 total points
ID: 39717298
The three nodes will negotiate among themselves to determine ownership, but just adding a third node won't cause an outage or quorum problem of any kind - if anything, it will make things more stable as it makes a node majority easier to achieve (since you have an odd number of nodes).

Does failover between your two existing nodes happen without issue currently? What version of SQL Server are you using? If you're using SQL 2008 or newer, just adding the node to the cluster isn't enough - you also have to install and configure it on the new node before it can take ownership. If you're using SQL 2005, though, it deploys to all nodes at once when you install or patch it, so I'm not sure how this version of SQL deals with a new node being added to a cluster. There a number of people asking online about adding an addition node to a SQL 2005 cluster, and the consensus is that it proceeds without an issue, so I'm not sure what could cause this.
0
 

Author Comment

by:sunhux
ID: 39727103
I can't even do failover.  I'm on SQL 2012
0

Featured Post

Highfive Gives IT Their Time Back

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

This article explains how to reset the password of the sa account on a Microsoft SQL Server.  The steps in this article work in SQL 2005, 2008, 2008 R2, 2012, 2014 and 2016.
Ever needed a SQL 2008 Database replicated/mirrored/log shipped on another server but you can't take the downtime inflicted by initial snapshot or disconnect while T-logs are restored or mirror applied? You can use SQL Server Initialize from Backup…
Via a live example, show how to shrink a transaction log file down to a reasonable size.
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

747 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

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now