Jan-Otto Kröpke
d819362150
Every optional collector of the mixin now has alerts, generated only with that collector enabled in _config.collectors: clock source, disk drive status, page file usage, license status, scheduled task results, pending updates, Hyper-V WMI and replication health, failover cluster nodes, resources, groups and shared volumes, Storage Spaces pool and virtual disk health, DHCP scope exhaustion and DNS zone transfer failures. The alerts of the pagefile, diskdrive and license collectors join the memory, disk and system groups; the other collectors get a group of their own. New knobs: taskSelector, sharedVolumeSelector, pagefileUsageThreshold, dhcpScopeFreeWarningThreshold, dhcpScopeFreeCriticalThreshold and updatePendingDuration. The test configuration enables every optional collector and tests/optional.test.yaml covers the new alerts. Signed-off-by: Jan-Otto Kröpke <mail@jkroepke.de>
2.0 KiB
title
| title |
|---|
| WindowsHyperVReplicationCritical |
Meaning
Hyper-V Replica reports critical health for the virtual machine vm for five
minutes. The alert carries the relationship label, primary for the normal
replication and extended for an extended replica, and needs the hyperv
collector with its replica_vm subcollector. Critical health means that
replication has not succeeded for long enough that the replica misses the
recovery point objective, or that replication is paused because of an error.
Impact
The replica of the virtual machine is stale. A failover to it loses the changes since the last successful replication, and the recovery point objective of the service is not met. If the primary host fails now, data is lost.
Diagnosis
-
Inspect
windows_hyperv_replica_vm_healthandwindows_hyperv_replica_vm_statefor the virtual machine; the state tells whether replication is suspended, resynchronizing or in error, andwindows_hyperv_replica_vm_replication_latency_secondshow long the last cycle took. -
On the primary host, read the replication details:
Measure-VMReplication -VMName '<vm>' | Format-List * Get-VMReplication -VMName '<vm>' | Format-List State, Health, LastReplicationTime, ReplicationMode Get-WinEvent -LogName Microsoft-Windows-Hyper-V-VMMS-Admin -MaxEvents 50 | Where-Object Message -like '*<vm>*' -
Check the replica server: free space on the replica storage, the Hyper-V Replica HTTP or HTTPS listener, the certificate for authentication, and the network path between the hosts. Check whether a snapshot merge or a storage migration on the primary blocks replication.
Mitigation
Fix the cause on the replica server or the network, then resume replication
with Resume-VMReplication -VMName '<vm>'; add -Resynchronize when the
state asks for a resynchronization. Confirm the health returns to normal and
the last replication time advances. If the replica cannot be recovered, remove
and re-enable replication, which sends a full initial copy.