Edit

Share via

Start-ClusterNode

  • Reference
Module:
FailoverClusters

Starts the Cluster service on a node in a failover cluster.

Syntax

Start-ClusterNode
     [[-Name] <StringCollection>]
     [-ForceQuorum]
     [-ClearQuarantine]
     [-IgnorePersistentState]
     [-PreventQuorum]
     [-Wait <Int32>]
     [-InputObject <PSObject>]
     [-Cluster <String>]
     [<CommonParameters>]

Description

The Start-ClusterNode cmdlet starts the Cluster service on a node in a failover cluster. If this is the first node started, then it will wait for other nodes to join. The cluster will begin to run when a quorum has formed.

This cmdlet with the FixQuorum parameter can be used to force quorum, that is, force the start of a cluster node even if quorum has not been achieved. When quorum is forced on a given node, the copy of the cluster configuration that is on that node will be treated as the authoritative copy and will be replicated to all other nodes. Therefore, forcing quorum should be considered a last resort, because some cluster configuration changes could be lost. The ability to force quorum can be especially useful in a multi-site cluster if the primary site, with the majority of nodes, becomes unavailable, and the secondary site, with a minority of nodes, need to be brought into service. Similarly, the ability to force quorum makes it possible to start a cluster that uses the Node and File Share Majority quorum option when none of the available cluster nodes contains a current copy of the cluster configuration.

Note: This cmdlet cannot be run remotely without Credential Security Service Provider (CredSSP) authentication on the server computer.

Examples

Example 1

PS C:\> Start-ClusterNode -Name node3
Name                                                                      State 
----                                                                      ----- 
node3                                                                   Joining

This example starts the Cluster service on the node named node3 on the local cluster.

Example 2

PS C:\> Start-ClusterNode -Name node1 -Cluster cluster2
Name                                                                      State 
----                                                                      ----- 
node1                                                                   Joining

This example starts the Cluster service on the node named node1 on the cluster named cluster2.

Example 3

PS C:\> Start-ClusterNode -FixQuorum
Name                                                                      State 
----                                                                      ----- 
node1                                                                   Joining

This example forces the local node and the local cluster to start, even if quorum has not been achieved. If quorum has not been achieved, then the copy of the cluster configuration that is on the local node will be treated as the authoritative copy and will be replicated to all other nodes. This cmdlet should be considered a last resort, because some cluster configuration changes could be lost, such as recovery options for cluster service.

Parameters

-ClearQuarantine

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

-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
Required:False
Accept pipeline input:False
Accept wildcard characters:False

-ForceQuorum

Indicates that the cmdlet forces the start of a cluster node regardless if quorum is not formed.

Type:SwitchParameter
Aliases:fq, FixQuorum
Position:Named
Default value:None
Required:False
Accept pipeline input:False
Accept wildcard characters:False

-IgnorePersistentState

Starts the cluster node without bringing resources online on the node.

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

-InputObject

Specifies the cluster node to start.

Type:PSObject
Position:Named
Default value:None
Required:False
Accept pipeline input:True
Accept wildcard characters:False

-Name

Specifies the name of the cluster node to start.

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

-PreventQuorum

Starts the node, but prevents it from achieving quorum and forming the cluster, to prevent a split situation with two competing instances of the cluster running.

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

-Wait

Specifies the time in seconds to wait for the cmdlet. If the Wait parameter is not specified, then the cmdlet waits for completion. If -Wait 0 is specified, then the call is initiated and the cmdlet returns without waiting.

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

Inputs

Microsoft.FailoverClusters.PowerShell.ClusterNode

Outputs

Microsoft.FailoverClusters.PowerShell.ClusterNode