{"id":1365,"date":"2019-05-01T00:00:00","date_gmt":"2019-05-01T00:00:00","guid":{"rendered":"https:\/\/azure.microsoft.com\/blog\/monitoring-enhancements-vmware-physical-azure"},"modified":"2025-06-22T19:12:26","modified_gmt":"2025-06-23T02:12:26","slug":"monitoring-enhancements-vmware-physical-azure","status":"publish","type":"post","link":"https:\/\/azure.microsoft.com\/en-us\/blog\/monitoring-enhancements-vmware-physical-azure\/","title":{"rendered":"Monitoring enhancements for VMware and physical workloads protected with Azure Site Recovery"},"content":{"rendered":"\n

Azure Site Recovery has enhanced the health monitoring of your workloads by introducing various health signals on the replication component, Process Server. The Process Server (PS) in a hybrid DR scenario is a vital component of data replication. It handles replication caching, data compression, and data transfer. Once the workloads are protected issues can be triggered due to multiple factors including high data change rate (churn) at source, network connectivity, available bandwidth, under provisioning the Process Server, or protecting large number of workloads with a single Process Server. These may lead to bad state of the PS and have a cascading effect on replication of VMs.<\/p>\n\n\n\n

Troubleshooting these issues is now made easier with additional health signals from the Process Server<\/a>. It is quick to identify which Process Server is being used by a virtual machine, and easy to relate the health between the two. Notifications are raised on multiple parameters of PS \u2013 free space utilization, memory usage, CPU utilization, and achieved throughput. Both warning and critical alerts are released so that action can be taken at the right time. This helps users avoid running into large scale issue which may impact multiple machines connected to a PS.<\/p>\n\n\n\n

\"Process<\/figure>\n\n\n\n

View of the PS blade<\/em><\/p>\n\n\n\n

Warning and critical events are raised as per the below thresholds set by Azure Site Recovery. Supplemental alerts include issues related to PS services and PS heartbeat. On the portal all these health events are collated on PS blade for deep dive monitoring with up to 72 hours of data points in the events table. Note that throughput is measured in terms of achievable RPO.<\/p>\n\n\n\n

Parameter<\/strong><\/td>Warning Threshold<\/strong><\/td>Critical Threshold<\/strong><\/td><\/tr>
CPU utilization<\/td>80%<\/td>95%<\/td><\/tr>
Memory usage<\/td>80%<\/td>95%<\/td><\/tr>
Free Space<\/td>30%<\/td>25%<\/td><\/tr>
Achievable RPO<\/td>>30 mins<\/td>>45 mins<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

A clear relation between the PS and its replicated items is established on the replicated item blade. This helps in faster issue identification and resolution for ongoing replication.<\/p>\n\n\n\n

\"Replicated<\/figure>\n\n\n\n

A view of the replicated item blade.<\/em><\/p>\n\n\n\n

All these health signals roll up to consolidated Process Server health. This visible parameter helps in choosing a PS when new machines need to be protected, or when load balancing between existing PSes is required. At the time of Process Server selection<\/a> the warning health status deters the user\u2019s choice by raising warning, while critical health completely blocks the PS selection. The signals are powerful as the scale of the workloads grows. This guidance ensures that the apt number of virtual machines are connected to a Process Server, and that related issues can be avoided.<\/p>\n\n\n\n

\n
\"Healthy<\/figure>\n\n\n\n
\"Critical<\/figure>\n<\/blockquote>\n\n\n\n

Enable Replication Workflow with Healthy Process Server (Left) and with Critical Process Server (Right)<\/em><\/p>\n\n\n\n

Process Server health signals for CPU utilization, memory usage and free space are available from 9.24 version onwards. Throughput related alerts will be available in the subsequent releases.<\/p>\n\n\n\n