May 12 2020 12/05/2020 12/05/2020 by Pablo Villaronga

Create a Failover Cluster

Posted in , ,

Create a failover cluster

  • 06/06/2019
  • 13 minutes to read
  • +3

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

StatusTaskReference
☐Verify the prerequisitesVerify the prerequisites
☐Install the Failover Clustering feature on every server that you want to add as a cluster nodeInstall the Failover Clustering feature
☐Run the Cluster Validation Wizard to validate the configurationValidate the configuration
☐Run the Create Cluster Wizard to create the failover clusterCreate the failover cluster
☐Create clustered roles to host cluster workloadsCreate clustered roles

Verify the prerequisites

Before you begin, verify the following prerequisites:

  • Make sure that all servers that you want to add as cluster nodes are running the same version of Windows Server.
  • Review the hardware requirements to make sure that your configuration is supported. For more information, see Failover Clustering Hardware Requirements and Storage Options. If you’re creating a Storage Spaces Direct cluster, see Storage Spaces Direct hardware requirements.
  • To add clustered storage during cluster creation, make sure that all servers can access the storage. (You can also add clustered storage after you create the cluster.)
  • Make sure that all servers that you want to add as cluster nodes are joined to the same Active Directory domain.
  • (Optional) Create an organizational unit (OU) and move the computer accounts for the servers that you want to add as cluster nodes into the OU. As a best practice, we recommend that you place failover clusters in their own OU in AD DS. This can help you better control which Group Policy settings or security template settings affect the cluster nodes. By isolating clusters in their own OU, it also helps prevent against accidental deletion of cluster computer objects.

Additionally, verify the following account requirements:

  • Make sure that the account you want to use to create the cluster is a domain user who has administrator rights on all servers that you want to add as cluster nodes.
  • Make sure that either of the following is true:
    • The user who creates the cluster has the Create Computer objects permission to the OU or the container where the servers that will form the cluster reside.
    • If the user does not have the Create Computer objects permission, ask a domain administrator to prestage a cluster computer object for the cluster. For more information, see Prestage Cluster Computer Objects in Active Directory Domain Services.

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

  1. Start Server Manager.
  2. On the Manage menu, select Add Roles and Features.
  3. On the Before you begin page, select Next.
  4. On the Select installation type page, select Role-based or feature-based installation, and then select Next.
  5. On the Select destination server page, select the server where you want to install the feature, and then select Next.
  6. On the Select server roles page, select Next.
  7. On the Select features page, select the Failover Clustering check box.
  8. To install the failover cluster management tools, select Add Features, and then select Next.
  9. On the Confirm installation selections page, select Install.
    A server restart is not required for the Failover Clustering feature.
  10. When the installation is completed, select Close.
  11. Repeat this procedure on every server that you want to add as a failover cluster node.

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

  1. On a computer that has the Failover Cluster Management Tools installed from the Remote Server Administration Tools, or on a server where you installed the Failover Clustering feature, start Failover Cluster Manager. To do this on a server, start Server Manager, and then on the Tools menu, select Failover Cluster Manager.
  2. In the Failover Cluster Manager pane, under Management, select Validate Configuration.
  3. On the Before You Begin page, select Next.
  4. On the Select Servers or a Cluster page, in the Enter name box, enter the NetBIOS name or the fully qualified domain name of a server that you plan to add as a failover cluster node, and then select Add. Repeat this step for each server that you want to add. To add multiple servers at the same time, separate the names by a comma or by a semicolon. For example, enter the names in the format server1.contoso.com, server2.contoso.com. When you are finished, select Next.
  5. On the Testing Options page, select Run all tests (recommended), and then select Next.
  6. On the Confirmation page, select Next. The Validating page displays the status of the running tests.
  7. On the Summary page, do either of the following:
    • If the results indicate that the tests completed successfully and the configuration is suited for clustering, and you want to create the cluster immediately, make sure that the Create the cluster now using the validated nodes check box is selected, and then select Finish. Then, continue to step 4 of the Create the failover cluster procedure.
    • If the results indicate that there were warnings or failures, select View Report to view the details and determine which issues must be corrected. Realize that a warning for a particular validation test indicates that this aspect of the failover cluster can be supported, but might not meet the recommended best practices. Note If you receive a warning for the Validate Storage Spaces Persistent Reservation test, see the blog post Windows Failover Cluster validation warning indicates your disks don’t support the persistent reservations for Storage Spaces for more information.

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.

  1. Start Server Manager.
  2. On the Tools menu, select Failover Cluster Manager.
  3. In the Failover Cluster Manager pane, under Management, select Create Cluster. The Create Cluster Wizard opens.
  4. On the Before You Begin page, select Next.
  5. If the Select Servers page appears, in the Enter name box, enter the NetBIOS name or the fully qualified domain name of a server that you plan to add as a failover cluster node, and then select Add. Repeat this step for each server that you want to add. To add multiple servers at the same time, separate the names by a comma or a semicolon. For example, enter the names in the format server1.contoso.com; server2.contoso.com. When you are finished, select Next. Note If you chose to create the cluster immediately after running validation in the configuration validating procedure, you will not see the Select Servers page. The nodes that were validated are automatically added to the Create Cluster Wizard so that you do not have to enter them again.
  6. If you skipped validation earlier, the Validation Warning page appears. We strongly recommend that you run cluster validation. Only clusters that pass all validation tests are supported by Microsoft. To run the validation tests, select Yes, and then select Next. Complete the Validate a Configuration Wizard as described in Validate the configuration.
  7. On the Access Point for Administering the Cluster page, do the following:
    1. In the Cluster Name box, enter the name that you want to use to administer the cluster. Before you do, review the following information:
      • During cluster creation, this name is registered as the cluster computer object (also known as the cluster name object or CNO) in AD DS. If you specify a NetBIOS name for the cluster, the CNO is created in the same location where the computer objects for the cluster nodes reside. This can be either the default Computers container or an OU.
      • To specify a different location for the CNO, you can enter the distinguished name of an OU in the Cluster Name box. For example: CN=ClusterName, OU=Clusters, DC=Contoso, DC=com.
      • If a domain administrator has prestaged the CNO in a different OU than where the cluster nodes reside, specify the distinguished name that the domain administrator provides.
    2. If the server does not have a network adapter that is configured to use DHCP, you must configure one or more static IP addresses for the failover cluster. Select the check box next to each network that you want to use for cluster management. Select the Address field next to a selected network, and then enter the IP address that you want to assign to the cluster. This IP address (or addresses) will be associated with the cluster name in Domain Name System (DNS).
    Note If you’re using Windows Server 2019, you have the option to use a distributed network name for the cluster. A distributed network name uses the IP addresses of the member servers instead of requiring a dedicated IP address for the cluster. By default, Windows uses a distributed network name if it detects that you’re creating the cluster in Azure (so you don’t have to create an internal load balancer for the cluster), or a normal static or IP address if you’re running on-premises. For more info, see Distributed Network Name.
    1. When you are finished, select Next.
  8. On the Confirmation page, review the settings. By default, the Add all eligible storage to the cluster check box is selected. Clear this check box if you want to do either of the following:
    • You want to configure storage later.
    • You plan to create clustered storage spaces through Failover Cluster Manager or through the Failover Clustering Windows PowerShell cmdlets, and have not yet created storage spaces in File and Storage Services. For more information, see Deploy Clustered Storage Spaces.
  9. Select Next to create the failover cluster.
  10. On the Summary page, confirm that the failover cluster was successfully created. If there were any warnings or errors, view the summary output or select View Report to view the full report. Select Finish.
  11. To confirm that the cluster was created, verify that the cluster name is listed under Failover Cluster Manager in the navigation tree. You can expand the cluster name, and then select items under Nodes, Storage or Networks to view the associated resources. Realize that it may take some time for the cluster name to successfully replicate in DNS. After successful DNS registration and replication, if you select All Servers in Server Manager, the cluster name should be listed as a server with a Manageability status of Online.

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:

  1. Use Server Manager or Windows PowerShell to install the role or feature that is required for a clustered role on each failover cluster node. For example, if you want to create a clustered file server, install the File Server role on all cluster nodes. The following table shows the clustered roles that you can configure in the High Availability Wizard and the associated server role or feature that you must install as a prerequisite. Table 2 Clustered Role Role or Feature Prerequisite Namespace Server Namespaces (part of File Server role) DFS Namespace Server DHCP Server role Distributed Transaction Coordinator (DTC) None File Server File Server role Generic Application Not applicable Generic Script Not applicable Generic Service Not applicable Hyper-V Replica Broker Hyper-V role iSCSI Target Server iSCSI Target Server (part of File Server role) iSNS Server iSNS Server Service feature Message Queuing Message Queuing Services feature Other Server None Virtual Machine Hyper-V role WINS Server WINS Server feature
  2. In Failover Cluster Manager, expand the cluster name, right-click Roles, and then select Configure Role.
  3. Follow the steps in the High Availability Wizard to create the clustered role.
  4. To verify that the clustered role was created, in the Roles pane, make sure that the role has a status of Running. The Roles pane also indicates the owner node. To test failover, right-click the role, point to Move, and then select Select Node. In the Move Clustered Role dialog box, select the desired cluster node, and then select OK. In the Owner Node column, verify that the owner node changed.

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. PowerShell

Install-WindowsFeature –Name Failover-Clustering –IncludeManagementTools

The following example runs all cluster validation tests on computers that are named Server1 and Server2. PowerShell

Test-Cluster –Node Server1, Server2

Note

The Test-Cluster cmdlet outputs the results to a log file in the current working directory. For example: C:\Users<username>\AppData\Local\Temp.

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. PowerShell

New-Cluster –Name MyCluster –Node Server1, Server2 –StaticAddress 192.168.1.12

The following example creates the same failover cluster as in the previous example, but it does not add eligible storage to the failover cluster. PowerShell

New-Cluster –Name MyCluster –Node Server1, Server2 –StaticAddress 192.168.1.12 -NoStorage

The following example creates a cluster that is named MyCluster in the Cluster OU of the domain Contoso.com. PowerShell

New-Cluster -Name CN=MyCluster,OU=Cluster,DC=Contoso,DC=com -Node Server1, Server2

For examples of how to add clustered roles, see topics such as Add-ClusterFileServerRole and Add-ClusterGenericApplicationRole.

More information

Command : Test-Cluster

Module:failoverclusters Runs validation tests for failover cluster hardware and settings.

Syntax

PowerShell

Test-Cluster
    [[-Node] <StringCollection>]
    [-Disk <Object[]>]
    [-Pool <Object[]>]
    [-ReportName <String>]
    [-List]
    [-Include <StringCollection>]
    [-Ignore <StringCollection>]
    [-Force]
    [-InputObject <PSObject>]
    [-Cluster <String>]
    [-WhatIf]
    [-Confirm]
    [<CommonParameters>]

Description

The Test-Cluster cmdlet runs validation tests for failover cluster hardware and settings. Tests can be run both before and after a cluster is set up.

Test results are captured in a file with the file name that you specify. By running the validation tests, you can confirm that your hardware and settings are compatible with Failover Clustering. There are multiple types of tests, including Cluster, Inventory, Network, Storage, System, and other types of tests. Storage tests will not test online disks or storage pools that are in use by a clustered role. To test such disks, first run Stop-ClusterGroup to stop the clustered role, and then run Test-Cluster. After the tests are done, start the clustered roles, also known as resource groups, again.

Examples

Example 1: Validate local cluster PowerShell

PS C:\> Test-Cluster
Mode                LastWriteTime     Length Name 
----                -------------     ------ ---- 
-a---        10/10/2008   6:31 PM    1132255 Test-Cluster on 2008.10.10 At 18.22.53.mht

This example runs all applicable cluster validation tests on the local cluster.

Example 2: Validate specified nodes PowerShell

PS C:\> Test-Cluster -Node "node1", "node2"
Mode                LastWriteTime     Length Name 
----                -------------     ------ ---- 
-a---        10/10/2008   6:18 PM     998032 Test-Cluster on 2008.10.10 At 18.08.24.mht

This example runs all cluster validation tests on the nodes named node1 and node2. If either node1 or node2 is already a member of a cluster, then the tests will include all nodes in that cluster.

Example 3: View tests and categories in cluster validation PowerShell

PS C:\> Test-Cluster -List
Category                                DisplayName                             Description 
--------                                -----------                             ----------- 
Cluster Configuration                   List Cluster Core Groups                List information about the available... 
Cluster Configuration                   List Cluster Network Information        List cluster-specific network settin... 
Cluster Configuration                   List Cluster Resources                  List the resources that are configur... 
Cluster Configuration                   List Cluster Volumes                    List information for the volumes in ... 
Cluster Configuration                   List Clustered Roles                    List information about clustered roles. 
Cluster Configuration                   Validate Quorum Configuration           Validate that the current quorum con... 
Cluster Configuration                   Validate Resource Status                Validate that cluster resources are ... 
Cluster Configuration                   Validate Service Principal Name         Validate that a Service Principal Na... 
Cluster Configuration                   Validate Volume Consistency             If any volumes are flagged as incons... 
Hyper-V Configuration                   List Information About Servers Runni... List Hyper-V related information on ... 
Hyper-V Configuration                   Validate Compatibility of Virtual Fi... Validate that all specified nodes sh... 
Hyper-V Configuration                   Validate Hyper-V Memory Resource Poo... Validate that all specified nodes sh... 
Hyper-V Configuration                   Validate Hyper-V Network Resource Po... Validate that all specified nodes sh... 
Hyper-V Configuration                   Validate Hyper-V Processor Resource ... Validate that all specified nodes sh... 
Hyper-V Configuration                   Validate Hyper-V Role Installed         Validate that all the nodes have the... 
Hyper-V Configuration                   Validate Hyper-V Storage Resource Po... Validate that all specified nodes sh... 
Hyper-V Configuration                   Validate Matching Processor Manufact... Validate that all specified nodes sh... 
Hyper-V Configuration                   List Hyper-V Virtual Machine Informa... List Hyper-V virtual machine informa... 
Hyper-V Configuration                   Validate Hyper-V Integration Service... Validate that the Hyper-V integratio... 
Hyper-V Configuration                   Validate Hyper-V Virtual Machine Net... Validate that all virtual machines o... 
Hyper-V Configuration                   Validate Hyper-V Virtual Machine Sto... Validate that all virtual machines o... 
Inventory                               List Fibre Channel Host Bus Adapters    List Fibre Channel host bus adapters... 
Inventory                               List iSCSI Host Bus Adapters            List iSCSI host bus adapters on each... 
Inventory                               List SAS Host Bus Adapters              List Serial Attached SCSI (SAS) host... 
Inventory                               List BIOS Information                   List BIOS information from each node. 
Inventory                               List Environment Variables              List environment variables set on ea... 
Inventory                               List Memory Information                 List memory information for each node. 
Inventory                               List Operating System Information       List information about the operating... 
Inventory                               List Plug and Play Devices              List Plug and Play devices on each n... 
Inventory                               List Running Processes                  List the running processes on each n... 
Inventory                               List Services Information               List information about the services ... 
Inventory                               List Software Updates                   List software updates that have been... 
Inventory                               List System Drivers                     List the system drivers on each node. 
Inventory                               List System Information                 List system information such as comp... 
Inventory                               List Unsigned Drivers                   List the unsigned drivers on each node. 
Network                                 List Network Binding Order              List the order in which networks are... 
Network                                 Validate Cluster Network Configuration  Validate the cluster networks that w... 
Network                                 Validate IP Configuration               Validate that IP addresses are uniqu... 
Network                                 Validate Multiple Subnet Properties     For clusters using multiple subnets,... 
Network                                 Validate Network Communication          Validate that servers can communicat... 
Network                                 Validate Windows Firewall Configuration Validate that the Windows Firewall i... 
Storage                                 List Disks                              List all disks visible to one or mor... 
Storage                                 List Potential Cluster Disks            List disks that will be validated fo... 
Storage                                 Validate CSV Network Bindings           Validate that network bindings requi... 
Storage                                 Validate CSV Settings                   Validate that settings and configura... 
Storage                                 Validate Disk Access Latency            Validate acceptable latency for disk... 
Storage                                 Validate Disk Arbitration               Validate that a node that owns a dis... 
Storage                                 Validate Disk Failover                  Validate that a disk can fail over s... 
Storage                                 Validate File System                    Validate that the file system on dis... 
Storage                                 Validate Microsoft MPIO-based disks     Validate that disks that use Microso... 
Storage                                 Validate Multiple Arbitration           Validate that in a multiple-node arb... 
Storage                                 Validate SCSI device Vital Product D... Validate uniqueness of inquiry data ... 
Storage                                 Validate SCSI-3 Persistent Reservation  Validate that storage supports the S... 
Storage                                 Validate Simultaneous Failover          Validate that disks can fail over si... 
System Configuration                    Validate Active Directory Configuration Validate that all the nodes have the... 
System Configuration                    Validate All Drivers Signed             Validate that tested servers contain... 
System Configuration                    Validate Cluster Service and Driver ... Validate startup settings used by se... 
System Configuration                    Validate Memory Dump Settings           Validate that none of the nodes curr... 
System Configuration                    Validate Operating System Edition       Validate that all tested servers are... 
System Configuration                    Validate Operating System Installati... Validate that the operating systems ... 
System Configuration                    Validate Operating System Version       Validate that the operating systems ... 
System Configuration                    Validate Required Services              Validate that services required for ... 
System Configuration                    Validate Same Processor Architecture    Validate that all servers run as 64-... 
System Configuration                    Validate Service Pack Levels            Validate that all servers with same ... 
System Configuration                    Validate Software Update Levels         Validate that all tested servers hav... 
System Configuration                    Validate System Drive Variable          Validate that all nodes have the sam...

This example lists the names of all tests and categories in cluster validation. Specify these test names with Ignore or Include parameters to run specific tests.

Example 4: Validate specified nodes for storage PowerShell

PS C:\> Test-Cluster -Node "node1", "node2" -Include "Storage"
Mode                LastWriteTime     Length Name 
----                -------------     ------ ---- 
-a---        10/10/2008   6:20 PM      37818 Test-Cluster on 2008.10.10 At 18.20.52.mht

This example runs the storage validation tests on the nodes named node1 and node2. If either node1 or node2 is already a member of a cluster, then the tests will include all nodes in that cluster.

Example 5: Validate specified nodes for everything except inventory PowerShell

PS C:\> Test-Cluster -Node "node1", "node2" -Ignore Inventory
Mode                LastWriteTime     Length Name 
----                -------------     ------ ---- 
-a---        10/10/2008   6:20 PM     732889 Test-Cluster on 2008.10.10 At 18.19.47.mht

This example runs all validation tests except the Inventory tests on the nodes named node1 and node2. If either node1 or node2 is already a member of a cluster, then the tests will include all nodes in that cluster.

Example 6: Run a specific test PowerShell

PS C:\> Test-Cluster -Include "List Potential Cluster Disks"
Mode                LastWriteTime     Length Name 
----                -------------     ------ ---- 
-a---        10/15/2008   2:58 PM      36119 Test-Cluster on 2008.10.15 At 14.58.44.mht

This example runs the test called List Potential Cluster Disks on the local cluster.

Example 7: Run multiple tests PowerShell

PS C:\> Test-Cluster -Include "List System Drivers","List Unsigned Drivers"
Mode                LastWriteTime     Length Name 
----                -------------     ------ ---- 
-a---        10/15/2008   3:00 PM     266571 Test-Cluster on 2008.10.15 At 15.00.08.mht

This example runs the tests called List System Drivers and List Unsigned Drivers on the local cluster.

Parameters

-Cluster

Specifies the name of the cluster on which to run this cmdlet. If the input for this parameter is . or it is omitted, then the cmdlet runs on the local cluster.

Type:String
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

-Confirm

Prompts you for confirmation before running the cmdlet.

Type:SwitchParameter
Aliases:cf
Position:Named
Default value:False
Accept pipeline input:False
Accept wildcard characters:False

-Disk

Specifies the disk number or disks for which to run the cmdlet. If the specified disk is online and is assigned to a clustered role or Cluster Shared Volume, you must also specify the Force parameter to take the disk offline for the duration of the storage tests. Otherwise, the specified disk must be offline before the cmdlet is run. If the Disk parameter is not specified, storage tests run on all disks that are available for use in the cluster or that are in the cluster resource offline or failed state. The acceptable values for this parameter are:

  • Int32, Int64, Uint32, Uint64. A number that represents a master boot record (MBR) signature of the disk.
  • System.String. A string that represents a master boot record (MBR) signature of the disk, hexadecimal format is supported.
  • System.String. A string that represents the GUID of a GPT disk.
  • ClusterResource. A cluster resource object that represents a clustered disk.
  • CimInstance#MSFT_Disk. An object returned from Get-Disk, from the Windows PowerShell® storage module.
Type:Object[]
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

-Force

Forces the command to run without asking for user confirmation.

Type:SwitchParameter
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

-Ignore

Specifies which tests or category of tests to ignore during the validation test run. All others tests or category of tests will run.

Type:StringCollection
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

-Include

Specifies which tests or category of tests to include during the validation test run. Only the tests or category of tests specified here will run.

Type:StringCollection
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

-InputObject

Specifies the cluster on which to run the validation tests.

Type:PSObject
Position:Named
Default value:None
Accept pipeline input:True (ByValue)
Accept wildcard characters:False

-List

Causes the cmdlet to list the tests and test categories. No tests will run on the servers or cluster nodes.

Type:SwitchParameter
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

-Node

Specifies a comma-separated list of server names on which to run the cluster validation tests.

Type:StringCollection
Position:0
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

-Pool

Specifies the clustered storage pool or pools for which to run the cmdlet. When the specified storage pool is online and a virtual disk in the storage pool is assigned to a clustered role or Cluster Shared Volume, you must also specify the Force parameter to take the storage pool offline for the duration of the storage tests. Otherwise, the specified storage pool must be taken offline before the storage tests. If the Pool parameter is not specified, storage tests run on all storage pools that are available for use in the cluster or that are in the cluster resource offline or failed state. The acceptable values for this parameter are:

  • System.String: A string that represents the name of the clustered storage pool or pools.
  • ClusterResource: A cluster resource object that represents a clustered storage pool.
  • CimInstance#MSFT_StoragePool: An object returned from Get-StoragePool, from the Windows PowerShell storage module.
Type:Object[]
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

-ReportName

Specifies the name of the test report to generate.

Type:String
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

-WhatIf

Shows what would happen if the cmdlet runs. The cmdlet is not run.

Type:SwitchParameter
Aliases:wi
Position:Named
Default value:False
Accept pipeline input:False
Accept wildcard characters:False

Inputs

Microsoft.FailoverClusters.PowerShell.Cluster

Outputs

System.IO.FileInfo

Microsoft.FailoverClusters.PowerShell.ClusterTestInfo