Windows Server 2016: Testing Workgroup Cluster – Part2


Now when the cluster File Server role is up and running I’d like to see whether there’ll be any issues making non-authoritative and authoritative restore of the cluster. First of all, I’ll take the system state backup of the Node1 to \\Node2\Backup:

Suppose Node1 has suffered some issues and needs to be restored while preserving the cluster configuration – in this case I must restore the system state backup of Node1 (restoring just the image of drive C: is not sufficient!)  and after restarting Node1 will replicate the current cluster configuration from Node2.
Prior to restoring Node1 I’d like to make sure my system state backup contains (among others things) the cluster database:

wbadmin get versions

wbadmin get items -version:04/07/2017-13:27

Now I’ll start the restore process for the system state backup taken on 04/07/2017:

…and the following window will open upon restart:

Let’s start Failover Cluster Manager:


As we see Node1 has been successfully restored.

To test the authoritative  restore I’ll make some changes to the cluster configuration and then restore the same backup – if after restoring of the same backup the cluster configuration reverts to the previous settings it would mean the cluster has been authoritatively restored.

The change I’m going to make is simply a renaming the one of the cluster networks: I’ll change  the network name Clients Network to ClientsNetwork111:

Since I’m testing authoritative restore on Node1 I must stop Cluster service on Node2 because in this case it is Node1 from which other cluster members (Node2) would read the restored cluster configuration.

Once again  wbadmin get versions :

wbadmin get items -version:04/07/2017-13:27

…and to start authoritative restore of the cluster I type this:

wbadmin startrecovery -version:04/07/2017-13:27 -itemtype:App -items:Cluster

To complete the restore I’ll restart Cluster service on Node1 and start it on Node2:

Now let’s go back to the cluster console and open the cluster networks node:

The first cluster network is named again Clients Network instead of Clients Network111 so the restore operation has completed successfully.



You can restore (both authoritatively and non-authoritatively) the workgroup cluster in exactly the same way as you would for a domain-based cluster.

%d bloggers like this: