Start-ClusterNode

Start-ClusterNode

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

Sintaxis

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

Descripción detallada

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: Este cmdlet no se puede ejecutar de forma remota sin la autenticación del proveedor de servicio de seguridad de credenciales (CredSSP) en el equipo servidor.

Parámetros

-Cluster<String>

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.

-ForceQuorum

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

-IgnorePersistentState

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

-InputObject<PSObject>

Specifies the cluster node to start.

-Name<StringCollection>

Specifies the name of the cluster node to start.

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

-Wait<Int32>

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.

<CommonParameters>

Este cmdlet admite los siguientes parámetros comunes: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer y -OutVariable. Para obtener más información, consulte about_CommonParameters (https://go.microsoft.com/fwlink/p/?LinkID=113216).

Entradas

El tipo de entrada es el tipo de los objetos que se pueden canalizar al cmdlet.

• Microsoft.FailoverClusters.PowerShell.ClusterNode

Salidas

El tipo de resultado es el tipo de objetos que emite el cmdlet.

• Microsoft.FailoverClusters.PowerShell.ClusterNode

Ejemplos

EXAMPLE 1

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

PS C:\> Start-ClusterNode –Name node3

EXAMPLE 2

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

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

EXAMPLE 3

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.

PS C:\> Start-ClusterNode -FixQuorum

Temas relacionados

Add-ClusterNode

Get-ClusterNode

Remove-ClusterNode

Resume-ClusterNode

Stop-ClusterNode

Suspend-ClusterNode