Windows Server 2012 R2 Scale-Out File Server Clusters thoughts.   6 comments

In the Windows server 2012 R2 you can build a Scale-out file server. And Microsoft does only support up to 8 nodes per file server cluster !

Keep this in mind.  Below Is a small brain dump of my SOFS and not completely out off the box ( demo usage only ) There are already somany blog post about how to setup a SOFS so I skip this here and give you only the reminders on what to think about if you do Next ,Next, Close. 

Scale-Out File Servers can host continuously available and scalable storage by using the SMB 3.0 protocol. Failover clusters in Windows Server 2012 provide the following foundational features that support this type of file server:

  • A Distributed Network Name (DNN), which provides an access point for client connections to the Scale-Out File Servers.
  • A Scale-out File Server resource type that supports Scale-out File Services.
  • Cluster Shared Volumes (CSVs) for storage.
  • Integration with File Services features to configure the clustered role for the Scale-Out File Server.

image

You should have at least as many CSVs as you have file server cluster nodes. For instance, for a 3-node Scale-Out File Server, you should have at least 3 CSVs. Having 6 CSVs is also a valid configuration, which will help with rebalancing when one of the nodes is down for maintenance

But what if Someone forget this 8 node rule and just build a 64 node cluster and put a SOFS on top of this. Lets see under the hood of the SOFS

My cluster is in a healthy state. A 64 node cluster with Several shares .

 

In the Windows server 2012 R2 you can build a Scale-out file server. And Microsoft does only support up to 8 nodes per file server clusterIn the Windows server 2012 R2 you can build a Scale-out file server. And Microsoft does only support up to 8 nodes per file server cluster In the Windows server 2012 R2 you can build a Scale-out file server. And Microsoft does only support up to 8 nodes per file server clusterIn the Windows server 2012 R2 you can build a Scale-out file server. And Microsoft does only support up to 8 nodes per file server cluster

All seems fine to me and no problems I can connect to the share so no problems here .

But you can check how many sessions there are get-smbsession

 

imageimage 

But as you can see there is no Specific IP address Given to the Scale-out File server So How does it connect ?

Eh on the name \\DemoSOFS01\demoshare1 that is right but what IP is given to the DemoSOFS01 ? yes the node address from every node.

take a look in the DNS list. so now there are 64 nodes that can handle the share

As in the pictures below you can see the Distributed Network Name (DNN)

image  image

DNN updates DNS when :

  • DNN resource comes online and every 24 hours
  • A node is added or removed to/from cluster
  • A cluster network is added or removed as a client network
  • IP address changes

Some testing with SQLIO on the SMB share.

image

So keep in mind that when you setup a Cluster and create a scale-out file server with more than 8 nodes you will see a lot of connections and my flood your network/storage.  Every node is connecting !

 

Posted January 15, 2014 by Robert Smit [MVP] in Windows Server 2012 R2

Tagged with

6 responses to “Windows Server 2012 R2 Scale-Out File Server Clusters thoughts.

Subscribe to comments with RSS.

  1. We are getting ready to implement a SoFS cluster. I hadn’t seen any documentation until today about having the same number of CSV as nodes. Where did you find this?

    • That is a great Question. There is little guidance on a how to / best practice. but basically it is all about getting the max performance of the SOFS but creating a 8 node SOFS with 8 CSV and only using one VM on a CSV is overkill.

  2. Pingback: Microsoft Most Valuable Professional (MVP) – Best Posts of the Week around Windows Server, Exchange, SystemCenter and more – #64 - Dell TechCenter - TechCenter - Dell Community

  3. Pingback: Microsoft Most Valuable Professional (MVP) – Best Posts of the Week around Windows Server, Exchange, SystemCenter and more – #64 - Windows Management - TechCenter - Dell Community

  4. I’ve also never heard this before about having mutliple CSVs. We have one CSV (storage space) for a 2-node cluster. What are we losing by not having a second CSV?

    • Well If you have storage that can divided then you can create two CSV and if you have to take the CSV down then not all items are down or you can migrate the VM’s from CSV1 to CSV2 But it all depends on your config. basically you get more flexibility

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

  • Twitter

  • %d bloggers like this: