Review comments

Author: v-ksreedevan

articles/migrate/troubleshoot-replication-vmware.md

@@ -13,15 +13,14 @@ ms.custom: mvc, engagement-fy23
 
 This article helps you troubleshoot slow replication or stuck migration issues that you may encounter when you replicate on-premises VMware VMs using the Azure Migrate: Server Migration agentless method.
 
-## Slow or stuck replication 
 
-### Replication is slow or stuck for VM 
+## Replication is slow or stuck for VM 
 
 While performing replications, you might observe that replication for a particular VM isn't progressing at the expected pace. Generally, the underlying reason for this issue is an unavailability or scarcity of some resources required for replication. The resources might be consumed by other VMs that are replicating or some other process running on the appliance in the datacenter. 
 
 Following are some reasons that generally cause this issue and remediations. 
 
-#### NFC buffer size low 
+### NFC buffer size low 
 
 The Azure Migrate appliance operates under the constraint of using 32 MB of NFC buffer to concurrently replicate 8 disks on the ESXi host. An NFC buffer size of less than 32 MB might cause slow replication. 
 You may also get the following exception:  
@@ -72,52 +71,51 @@ You can increase the NFC buffer size beyond 32 MB to increase concurrency. The s
    - net start asrgwy  
 
 
-#### ESXi host available RAM low 
+### ESXi host available RAM low 
 
 When the ESXi host on which the replicating VM is present is too busy, the replication process will slow down due to unavailability of RAM. 
 
 #### Remediation
 
 Use VMotion to move the VM with slow replication to an ESXi host, which isn't too busy. 
 
-#### Network bandwidth  
+### Network bandwidth  
 
 Replications might be slow because of low network bandwidth available to the Azure Migrate appliance. Low bandwidth might be due to other applications using up the bandwidth or presence of bandwidth throttling applications or a proxy setting restricting the bandwidth use of replication appliance.  
 
 #### Remediation
 
 In case of low bandwidth, you can first reduce the number of applications using network bandwidth. Check with your network administrator if any throttling application or proxy setting is present. 
 
-#### Disk I/O 
+### Disk I/O 
 
 Replications can be slow because the server that is being replicated has too much load on it and this is causing high I/O operations on disks attached to it. It's advised to reduce the load on the server to increase the replication speed. You may also encounter the following error: 
 
 The last replication cycle for the virtual machine ‘VM Name’ failed. Encountered timeout event. 
 
 If no action is taken, the replication will proceed and be completed with a delay. 
 
-#### Disk write rates 
+### Disk write rates 
 
 Replications can be slower than expected if the data upload speed is higher than the write speed of the disk that you selected while enabling replication. To get better speeds at same upload speeds, you would need to restart the replication and select **Premium** while selecting the disk type for replication.  
 
 > [!Caution]
 > The disk type recommended during Assessment might not be **Premium** for a particular VM. In this case, switching to Premium disk to improve replication speeds isn't advisable since it might not be required post migration to have a Premium disk attached to this VM. 
 
-## Slow or stuck migration 
 
-### Migration operation on VM is stuck 
+## Migration operation on VM is stuck 
 
-While triggering migration for a particular VM, you might observe that the migration is stuck at some stage (queued or delta sync) longer than expected. Generally, the underlying reason for this issue is an unavailability or scarcity of some resources required for replication. The resources might be consumed by other VMs that are replicating or some other process running on appliance on in the datacenter. Following are some reasons that generally cause this issue and the remedies. 
+While triggering migration for a particular VM, you might observe that the migration is stuck at some stage (queued or delta sync) longer than expected. Generally, the underlying reason for this issue is an unavailability or scarcity of some resources required for migration. The resources might be consumed by other VMs that are replicating or some other process running on appliance on in the datacenter. Following are some reasons that generally cause this issue and the remedies. 
 
-#### NFC buffer size low 
+### NFC buffer size low 
 
 If an IR cycle for a server with large disks is ongoing while migration is triggered for second VM, the second VM’s migration job can get stuck. Even though migration jobs are given high priority, the NFC buffer might not be available for migration. In this case, it's recommended to stop or pause the initial replication of servers with large disks and complete the migration of the second VM. 
 
-#### Ongoing delta sync cycle isn't complete 
+### Ongoing delta sync cycle isn't complete 
 
 If migration is triggered during an ongoing delta replication cycle, it would be queued. The delta replication cycle on the VM will be completed first after which migration will start. The time required to trigger migration depends on the time taken to complete one delta sync cycle. 
 
-#### Shutdown of on-premises VM taking longer than usual
+### Shutdown of on-premises VM taking longer than usual
 
 Try to migrate without shutting down the VM or turn off the VM manually and then migrate it.