SOLVED: Veeam Fails on Server 2016 Cluster

If you Veeam backups are failing when connected to a new or upgraded Server 2016 cluster, you likely need to set a disk parameter to fix it.  Veeam has a KBase article on this but it skips some simple steps and does not tell you where to perform the changes… so we do, right here: Note that this will only work if you have upgraded the functional level of your cluster to Server 2016 which…

SOLVED: How To Migrate A Server 2012 R2 Cluster To New Server 2016 Servers In 11 Easy Steps

If you want to simply upgrade your existing cluster from Server 2012 R2 to Server 2016, you just need to buy Server 2016 licenses and perform a “Server 2016 Rolling Upgrade”.  What this does is to take one of your cluster nodes offline, then upgrade it to 2016, then bring that node online, move the VM’s to it and then it takes down the next node, updates it and now your cluster is happy. However,…

SOLVED: Cluster Aware Updating Readiness Analyzer Warning – The machine proxy on each failover cluster node should be set to a local proxy server

You may find ANALYZE CLUSTER UPDATING READINESS (in CLUSTER AWARE UPDATING in your Windows Server Cluster) comes back with a warning: Rule ID: 10 Title: The machine proxy on each failover cluster node should be set to a local proxy server Result: Warning Problem: One or more failover cluster nodes have an incorrect machine proxy server configuration. Impact: Cluster-Aware Updating cannot update this failover cluster in a deployment scenario where the failover cluster must directly access…

SOLVED: The machine proxy on each failover cluster node should be set to a local proxy server on Server 2012 Cluster

If you are new to clustering, like me, then the hundreds of checks the Microsoft wizards handle for you are invaluable tools to ensuring a functional cluster configuration.  There are, however, some alerts that seem to indicate something is required when it is not.  This is one of those alerts in Cluster Aware Updating (CAU) .  You may also see: The Microsoft WindowsUpdatePlugin plug-in reported a failure while attempting to install updates on node “XXXXX”. Additional information reported by…