Azure Migrate
A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
819 questions
Azure migrate Physical appliance CPU suddenly gone high and process queue become red with 54
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(28.799999999999997, 69%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMS%3C/text%3E%3C/svg%3E)
Mahendra Sahu
0
Reputation points
We are replicating servers using agent , it was working fine but from 2 days CPU going high , we are replicating only 25 servers all servers are in delta sync.
{count} votes
-
SadiqhAhmed-MSFT 46,291 Reputation points Microsoft Employee2024-09-30T07:19:47.4866667+00:00 @Mahendra Sahu Greetings!
It sounds like your Azure Migrate Physical Appliance is experiencing high CPU usage and a long process queue1. This can happen if the appliance is under-resourced for the workload it's handling.
- Monitor CPU and memory usage on the appliance to see if they are consistently high.
- Ensure there aren’t any bottlenecks with disk I/O.
- Check the logs for any errors or warnings that might indicate what processes are consuming resources. Look for any specific tasks or operations that are failing.
- Sometimes, restarting the Azure Migrate appliance services can help clear up any temporary issues. Ensure to do this during a maintenance window if applicable.
- Ensure that the appliance has the recommended resources allocated (CPU, RAM, etc.) based on the scale of your environment.
- Check network connectivity to Azure. High latency or packet loss can cause delays and increase processing time.
- Ensure the Azure Migrate appliance is up-to-date with the latest patches and updates. Sometimes, performance issues are addressed in newer versions.
- If you consistently experience high CPU usage, consider scaling up the resources allocated to the Azure Migrate appliance.
- If the issue persists and you cannot identify the cause, then the best option would be to contact Azure technical support by raising a support request. The ticket enables you to work closely with the support engineers and get a quick resolution to your issue. Here is the link - https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request to create support case.
Hope this helps!
Sign in to comment
Sign in to answer