Update-Cluster Functional Level

Module:
failoverclusters
Updates the functional level of a mixed-version cluster.

Syntax 

Update-ClusterFunctionalLevel
      [-Force]
      [-WhatIf]
      [-InputObject <PSObject>]
      [-Cluster <String>]
      [<CommonParameters>]

Description

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.

Examples

Example 1: Test a possible update 

PS C:\> Update-ClusterFunctionalLevel -WhatIf
Name
----
cluster_17

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

Example 2: Update a cluster functional level 

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

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.

Optional 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
-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
-InputObject

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

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

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

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

Inputs

Microsoft.FailoverClusters.PowerShell.Cluster

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

Outputs

Microsoft.FailoverClusters.PowerShell.Cluster

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

Notes

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