Update-ClusterFunctionalLevel

Update-ClusterFunctionalLevel

Updates the functional level of a mixed-version cluster.

Syntaxe

Parameter Set: InputObject
Update-ClusterFunctionalLevel [-Cluster <String> ] [-Force] [-InputObject <PSObject> ] [ <CommonParameters>]

Description détaillée

The Update-ClusterFunctionalLevel cmdlet updates the functional level of a mixed-version cluster. You can update the cluster after all nodes have been updated.

Starting with Windows Server 2016, you can add a node that runs a more recent version of the Windows operating system into a cluster of nodes that run a previous version of the Windows operating system. To add a cluster node, use the Add-ClusterNode cmdlet.

After you add a node that runs a different version of the Windows operating system, the cluster becomes a mixed-version cluster. You can implement a mixed-version cluster to continue to run while you upgrade the operating system on each node in the cluster.

We recommend that you upgrade all nodes in the cluster within a month. We do not recommend using a mixed-version cluster permanently.

You can use this cmdlet to support a rolling operating system upgrade for a cluster. If you use cluster that runs Hyper-V in which all the nodes run Windows Server 2012 R2, you can upgrade the nodes of that cluster without downtime for your virtual machines.

First, drain one cluster node by specifying the Drain parameter of the Suspend-ClusterNode cmdlet. This cmdlet causes all virtual machines to live-migrate to one of the other hosts.

Next, remove the host from the cluster by using the Remove-ClusterNode cmdlet.

Next, install a new version of the operating system. Do not perform an upgrade or in-place installation.

Next, add the Hyper-V role and the Failover Clustering feature by using the Install-WindowsFeature cmdlet. For more information, type Get-Help Install-WindowsFeature.

Finally, add the node into the cluster by using the Add-ClusterNode cmdlet.

Repeat these steps for each node of the cluster.

Paramètres

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

-Force

Runs the cmdlet without prompting for confirmation. By default the cmdlet will ask for confirmation from the user before proceeding.

-InputObject<PSObject>

Specifies the input to this cmdlet. You can use this parameter, or you can pipe the input to this cmdlet.

<CommonParameters>

Cette applet de commande prend en charge les paramètres courants : -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer et -OutVariable. Pour plus d'informations, consultez  . about_CommonParameters (https://go.microsoft.com/fwlink/p/?LinkID=113216).

Entrées

Le type d'entrée correspond au type des objets que vous pouvez adresser à l'applet de commande.

• Microsoft.FailoverClusters.PowerShell.Cluster

  This cmdlet accepts a Cluster. This cmdlet updates the functional level of this cluster.

Sorties

Le type de sortie correspond au type des objets que l'applet de commande émet.

• Microsoft.FailoverClusters.PowerShell.Cluster

  This cmdlet returns a Cluster. This cmdlet updates the functional level of this cluster.

Remarques

• This cmdlet performs a one-time, one-way transformation of the cluster functional level. You cannot lower this level.

Exemples

Example 1: Test a possible update

This command tests whether an update would finish successfully. Because the command includes the WhatIf common parameter, the command does not perform the update.

PS C:\> Update-ClusterFunctionalLevel -WhatIf

Example 2: Update a cluster functional level

This command updates the cluster functional level of the cluster named cluster_17. All of the nodes of this cluster must already be updated before you run this command.

PS C:\> Update-ClusterFunctionalLevel –Cluster "cluster_17"

Rubriques connexes

Add-ClusterNode

Suspend-ClusterNode

Remove-ClusterNode