Microsoft Windows Cluster Scanning
Within a network, it is possible to have multiple independent servers working together to increase the availability and scalability of certain Windows features or applications, like SQL Server databases and Hyper-V virtual machines. This kind of setup is called a cluster and the machines within are called nodes. If one node fails, other nodes within the cluster take over the failed machine's clustered tasks, a process known as failover. The concept of ensuring that a feature runs continuously without disruption is also called high availability (HA). That's why we created the new Windows Cluster scanning feature.
When Lansweeper scans a Windows computer or server, it will automatically detect if it is part of a cluster. By scanning all of your clustered servers, regardless of the type of cluster, you can get a complete overview of your clusters and their nodes.
Alongside cluster and node information, just like with the normal Windows computer event logs, Lansweeper also retrieves log information specifically for clusters. Cluster log information provides an extra level of depth of information and lets you take a look at exactly what happened on your cluster nodes. For failover clusters, this means that if one of the servers or nodes fail, another node takes over the workload without any downtime, which will be represented in the logs.
Since Hyper-V clusters are slightly more unique with the addition of hosts and guests, Hyper-V guest machines will also be scanned from the host and get their own asset page. While the information from Hyper-V guests is limited, you can always scan them directly just like any other asset to get the detailed information you are used to.
Because Hyper-V guests are scanned from the hosts, you will see which Hyper-V guests are on each host and which guests are hosted on which host. Guests and hosts are automatically linked so you can easily navigate from the guest to the host or vice versa.
Just like other Windows clusters, Hyper-V cluster logs are also scanned. To prevent cluttering the log, Hyper-V has a dedicated Hyper-V Log page, so you can see exactly what happened in your Hyper-V environment.