After you install the Failover Clustering feature, we recommend that you apply the latest updates from Windows Update. Also, for a Windows Server 2012-based failover cluster, review the Recommended hotfixes and updates for Windows Server 2012-based failover clusters Microsoft Support article and install any updates that apply. Windows Server How-To. How To Create a Windows Server Failover Cluster Without Shared Storage. Follow these step-by-step instructions and you will be up and running in about 15 minutes.
-->
Applies to: Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, and Windows Server 2012
This topic shows how to create a failover cluster by using either the Failover Cluster Manager snap-in or Windows PowerShell. The topic covers a typical deployment, where computer objects for the cluster and its associated clustered roles are created in Active Directory Domain Services (AD DS). If you're deploying a Storage Spaces Direct cluster, instead see Deploy Storage Spaces Direct.
You can also deploy an Active Directory-detached cluster. This deployment method enables you to create a failover cluster without permissions to create computer objects in AD DS or the need to request that computer objects are prestaged in AD DS. This option is only available through Windows PowerShell, and is only recommended for specific scenarios. For more information, see Deploy an Active Directory-Detached Cluster.
Checklist: Create a failover cluster
Verify the prerequisites
Before you begin, verify the following prerequisites:
Additionally, verify the following account requirements:
Note
This requirement does not apply if you want to create an Active Directory-detached cluster in Windows Server 2012 R2. For more information, see Deploy an Active Directory-Detached Cluster.
Install the Failover Clustering feature
You must install the Failover Clustering feature on every server that you want to add as a failover cluster node.
Install the Failover Clustering feature
Note
After you install the Failover Clustering feature, we recommend that you apply the latest updates from Windows Update. Also, for a Windows Server 2012-based failover cluster, review the Recommended hotfixes and updates for Windows Server 2012-based failover clusters Microsoft Support article and install any updates that apply.
Validate the configuration
Before you create the failover cluster, we strongly recommend that you validate the configuration to make sure that the hardware and hardware settings are compatible with failover clustering. Microsoft supports a cluster solution only if the complete configuration passes all validation tests and if all hardware is certified for the version of Windows Server that the cluster nodes are running.
Note
You must have at least two nodes to run all tests. If you have only one node, many of the critical storage tests do not run.
Run cluster validation tests
For more information about hardware validation tests, see Validate Hardware for a Failover Cluster.
Create the failover cluster
To complete this step, make sure that the user account that you log on as meets the requirements that are outlined in the Verify the prerequisites section of this topic.
After the cluster is created, you can do things such as verify cluster quorum configuration, and optionally, create Cluster Shared Volumes (CSV). For more information, see Understanding Quorum in Storage Spaces Direct and Use Cluster Shared Volumes in a failover cluster.
Create clustered roles
After you create the failover cluster, you can create clustered roles to host cluster workloads.
Note
For clustered roles that require a client access point, a virtual computer object (VCO) is created in AD DS. By default, all VCOs for the cluster are created in the same container or OU as the CNO. Realize that after you create a cluster, you can move the CNO to any OU.
Here's how to create a clustered role:
Create a failover cluster by using Windows PowerShell
The following Windows PowerShell cmdlets perform the same functions as the preceding procedures in this topic. Enter each cmdlet on a single line, even though they may appear word-wrapped across several lines because of formatting constraints.
Note
You must use Windows PowerShell to create an Active Directory-detached cluster in Windows Server 2012 R2. For information about the syntax, see Deploy an Active Directory-Detached Cluster.
The following example installs the Failover Clustering feature.
The following example runs all cluster validation tests on computers that are named Server1 and Server2.
Note
The Test-Cluster cmdlet outputs the results to a log file in the current working directory. For example: C:Users<username>AppDataLocalTemp.
The following example creates a failover cluster that is named MyCluster with nodes Server1 and Server2, assigns the static IP address 192.168.1.12, and adds all eligible storage to the failover cluster.
The following example creates the same failover cluster as in the previous example, but it does not add eligible storage to the failover cluster.
The following example creates a cluster that is named MyCluster in the Cluster OU of the domain Contoso.com.
For examples of how to add clustered roles, see topics such as Add-ClusterFileServerRole and Add-ClusterGenericApplicationRole.
More information-->
Applies To: Windows Server 2012 R2, Windows Server 2012
This topic shows how to create a failover cluster by using either the Failover Cluster Manager snap-in or Windows PowerShell. The topic covers a typical deployment, where computer objects for the cluster and its associated clustered roles are created in Active Directory Domain Services (AD DS).
Windows Server Failover Cluster Requiremen…
Note
In Windows Server 2012 R2 you can also deploy an Active Directory-detached cluster. This deployment method enables you to create a failover cluster without permissions to create computer objects in AD DS or the need to request that computer objects are prestaged in AD DS. This option is only available through Windows PowerShell, and is only recommended for specific scenarios. For more information, see Deploy an Active Directory-Detached Cluster.
Checklist: Create a failover cluster
Verify the prerequisites![]()
Before you begin, verify the following prerequisites:
Additionally, verify the following account requirements:
Install the Failover Clustering feature
You must install the Failover Clustering feature on every server that you want to add as a failover cluster node.
To install the Failover Clustering feature
![]()
Note
After you install the Failover Clustering feature, we recommend that you apply the latest updates from Windows Update. Also, for a Windows Server 2012-based failover cluster, review the Microsoft Support article Recommended hotfixes and updates for Windows Server 2012-based Failover Clusters, and install any updates that apply. Sketch crack mac os x.
Validate the configuration
Before you create the failover cluster, we strongly recommend that you validate the configuration to make sure that the hardware and hardware settings are compatible with failover clustering. Microsoft supports a cluster solution only if the complete configuration passes all validation tests and if all hardware is certified for the version of Windows Server that the cluster nodes are running.
Note
You must have at least two nodes to run all tests. If you have only one node, many of the critical storage tests do not run.
To run cluster validation tests
Create the failover cluster
To complete this step, make sure that the user account that you log on as meets the requirements that are outlined in the Verify the prerequisites section of this topic.
To create the failover cluster
After the cluster is created, you can do things such as verify cluster quorum configuration, and optionally, create Cluster Shared Volumes (CSV). For more information, see Configure and Manage the Quorum in a Windows Server 2012 Failover ClusterandUse CSVs in a Failover Cluster.
Create clustered roles
After you create the failover cluster, you can create clustered roles to host cluster workloads.
Note
For clustered roles that require a client access point, a virtual computer object (VCO) is created in AD DS. By default, all VCOs for the cluster are created in the same container or OU as the CNO. Realize that after you create a cluster, you can move the CNO to any OU.
To create a clustered role
Create a failover cluster by using Windows PowerShell
Windows PowerShell equivalent commands
The following Windows PowerShell cmdlets perform the same function as the preceding procedures in this topic. Enter each cmdlet on a single line, even though they may appear word-wrapped across several lines because of formatting constraints.
Note
You must use Windows PowerShell to create an Active Directory-detached cluster in Windows Server 2012 R2. For information about the syntax, see Deploy an Active Directory-Detached Cluster.
The following example installs the Failover Clustering feature.
The following example runs all cluster validation tests on computers that are named Server1 and Server2.
Note
The Test-Cluster cmdlet outputs the results to a log file in the current working directory, for example C:Users<EM>usernameAppDataLocalTemp.
The following example creates a failover cluster that is named MyCluster with nodes Server1 and Server2, assigns the static IP address 192.168.1.12, and adds all eligible storage to the failover cluster.
The following example creates the same failover cluster as in the previous example, but it does not add eligible storage to the failover cluster.
The following example creates a cluster that is named MyCluster in the Cluster OU of the domain Contoso.com.
For examples of how to add clustered roles, see topics such as Add-ClusterFileServerRole and Add-ClusterGenericApplicationRole.
See alsoComments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |