.png)
Step 1: Plan for Storage in Scale-Out File Server
Published: May 31, 2012
Updated: July 27, 2012
Applies To: Windows Server 2012
Planning the storage that will support your Scale-Out File Server can leverage the existing storage in your organization. Before you deploy Scale-Out File Server, you should review the storage requirements for the server applications that will use Scale-Out File Server. After you have completed this step, see Step 2: Plan for Networking in Scale-Out File Server.
Use the following table to help you through the process of identifying the requirements for the server applications in your organization and identify any existing storage that you can leverage.
| Task | Description |
|---|---|
|
Scale-Out File Server uses the features and functionality included with Failover Clustering. You should review the requirements for Failover Clustering when planning for a Scale-Out File Server. |
|
|
Microsoft SQL Server and Hyper-V are server applications that are supported with Scale-Out File Server. If you plan to store your database files, database transaction logs, or virtual hard disks on scale-out file shares, the same storage recommendations for their respective server applications apply. |
|
|
You can use the storage that has already been deployed within your organization. |
Scale-Out File Server is built on top of Failover Clustering so any requirements for Failover Clustering apply to Scale-Out File Server. You should have an understanding of Failover Clustering before deploying Scale-Out File Server. Use the following links for more information on Failover Clustering in Windows Server 2012:
-
How to add storage to Clustered Shared Volumes in Windows Server 2012
-
Installing the Failover Cluster Feature and Tools in Windows Server 2012
-
Creating a Windows Server 2012 Failover Cluster
-
How to Troubleshoot Create Cluster failures in Windows Server 2012
Some important considerations for Failover Clustering and Scale-Out File Server are as follows:
-
The storage configuration must be supported by Failover Clustering before you deploy Scale-Out File Server. You must successfully run the Cluster Validation Wizard before you add Scale-Out File Server.
-
Scale-Out File Server requires the use of Clustered Shared Volumes (CSVs). Since CSVs are not supported with Resilient File System, Scale-Out File Server cannot use Resilient File System.
-
Accessing a continuously available file share as a loopback share is not supported. For example, Microsoft SQL Server or Hyper-V storing their data files on SMB file shares must run on computers that are not a member of the file server cluster for the SMB file shares.
Microsoft SQL Server and Hyper-V are the two server applications supported by Scale-Out File Server in Windows Server 2012. If you choose to use Microsoft SQL Server or Hyper-V with Scale-Out File Server, the storage recommendations for the server application on direct attached storage still apply. Use the following links for more information on their storage requirements:
It is not necessary to deploy new storage in your organization to support Scale-Out File Server. You can use existing storage that may already be deployed within your organization. Some supported storage configurations are as follows:
-
Fibre Channel Storage Area Network You can use an existing fibre channel Storage Area Network as the storage subsystem for Scale-Out File Server.
-
iSCSI Storage Area Network You can use an existing iSCSI Storage Area Network as the storage subsystem for Scale-Out File Server. For more information about iSCSI in Windows Server 2012, see iSCSI Target Block Storage Overview.
-
Storage Spaces Storage Spaces is new in Windows Server 2012 and can also be used as the storage subsystem for Scale-Out File Server. For more information about Storage Spaces, see Storage Spaces Overview.
-
Clustered RAID controller A clustered RAID controller is new in Windows Server 2012 and can be used as the storage subsystem for Scale-Out File Server.
