Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

failover question Expand / Collapse
Author
Message
Posted Monday, July 14, 2014 7:01 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, October 16, 2014 8:01 AM
Points: 54, Visits: 151
I'm pretty weak on networking concepts. I'll say that up front. Hopefully I can ask my question intelligently enough for someone to understand and know the answer.

We have a series of SQL Server boxes. Each server has 2 dedicated boxes:

SEP01 runs on SEP01A and SEP01B
HR01 runs on HR01A and HR01B

There are a bunch more but I'm sure you get the point.

My question involves the drive and directory structures on the nodes. SEP01 has a database named CM and it's mdf/ldf files are defined as being in F:\DATA and F:\LOGS. If I remote to 1 node, the F drive is exactly as I expect to see. If I remote to the other node, an F drive doesn't even exist. Can someone give me the 5 cent explanation of why this works or if it's bad and I should fix it? Should I make the nodes match each other?

Post #1592168
Posted Monday, July 14, 2014 7:13 AM This worked for the OP Answer marked as solution
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Today @ 9:59 AM
Points: 304, Visits: 574
robin.pryor (7/14/2014)
I'm pretty weak on networking concepts. I'll say that up front. Hopefully I can ask my question intelligently enough for someone to understand and know the answer.

We have a series of SQL Server boxes. Each server has 2 dedicated boxes:

SEP01 runs on SEP01A and SEP01B
HR01 runs on HR01A and HR01B

There are a bunch more but I'm sure you get the point.

My question involves the drive and directory structures on the nodes. SEP01 has a database named CM and it's mdf/ldf files are defined as being in F:\DATA and F:\LOGS. If I remote to 1 node, the F drive is exactly as I expect to see. If I remote to the other node, an F drive doesn't even exist. Can someone give me the 5 cent explanation of why this works or if it's bad and I should fix it? Should I make the nodes match each other?



What you seeing is entirely correct. What you have is your SQL server instances hosted on a 2 node failover cluster. At any given time only 1 node of your cluster is running the active SQL services. When the node is active the shared storage drives (F:\ in your case) is logically attached to the active node hence why you can see the drive in windows explorer on the active node but not on the passive node.

In the event of a failover the drives and SQL services will shutdown \ detach from the active node and attach \ start up on what was the passive node.

All storage in a failover cluster are shared storage and generally will be SAN storage rather than physical drives within the host server.


MCITP SQL 2005, MCSA SQL 2012
Post #1592172
Posted Monday, July 14, 2014 7:32 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, October 16, 2014 8:01 AM
Points: 54, Visits: 151
Excellent explanation. Thank you so much!
Post #1592175
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse