blockers removed

Author: Ankita Dutta

.openpublishing.redirection.json

@@ -1107,7 +1107,7 @@
         },
         {
             "source_path": "articles/site-recovery/vmware-azure-about-disaster-recovery.md",
-            "redirect_url": "/azure/site-recovery/ite-recovery-overview",
+            "redirect_url": "/azure/site-recovery/site-recovery-overview",
             "redirect_document_id": false
         },
         {

articles/site-recovery/toc.yml

@@ -6,12 +6,10 @@
     href: site-recovery-overview.md
   - name: What's new in Site Recovery
     href: site-recovery-whats-new.md
-  - name: Archieve for What's new
+  - name: Archive for What's new
     href: site-recovery-whats-new-archive.md
   - name: Site Recovery - FAQ
     href: site-recovery-faq.yml
-  - name: Disaster recovery for VMware
-    href: vmware-azure-about-disaster-recovery.md
 - name: Quickstarts
   expanded: true
   items:
@@ -179,7 +177,7 @@
       href: deploy-vmware-azure-replication-appliance-modernized.md
     - name: Failover and failback - Modernized
       href: failover-failback-overview-modernized.md
-    - name: Vmware to Azure architecture - Modernized
+    - name: VMware to Azure architecture - Modernized
       href: vmware-azure-architecture-modernized.md      
   - name: About Hyper-V VM disaster recovery
     items:

articles/site-recovery/vmware-azure-troubleshoot-replication.md

@@ -38,8 +38,8 @@ When you try to select the source machine to enable replication by using Site Re
 * **vCenter insufficient privileges**: If the permissions provided to access vCenter don't have the required permissions, failure to discover virtual machines might occur. Ensure that the permissions described in [Prepare an account for automatic discovery](vmware-azure-tutorial-prepare-on-premises.md#prepare-an-account-for-automatic-discovery) are added to the vCenter user account.
 * **Azure Site Recovery management servers**: If the virtual machine is used as a management server under one or more of the following roles - Configuration server /scale-out process server / Master target server, then you won't be able to choose the virtual machine from the portal. Management servers cannot be replicated.
 * **Already protected/failed over through Azure Site Recovery services**: If the virtual machine is already protected or failed over through Site Recovery, the virtual machine isn't available to select for protection in the portal. Ensure that the virtual machine you're looking for in the portal isn't already protected by any other user or under a different subscription.
-* **vCenter not connected**: Check if vCenter is in a connected state. To verify, go to Recovery Services vault > Site Recovery Infrastructure > Configuration Servers > Click on respective configuration server > a blade opens on your right with details of associated servers. Check if vCenter is connected. If it's in a "Not Connected" state, resolve the issue, and then [refresh the configuration server](vmware-azure-manage-configuration-server.md#refresh-configuration-server) on the portal. After this, virtual machine is not listed on the portal.
-* **ESXi powered off**: If the ESXi host under which the virtual machine resides is in a powered-off state, then the virtual machine is not listed or is not selectable on the Azure portal. Power on the ESXi host, and [refresh the configuration server](vmware-azure-manage-configuration-server.md#refresh-configuration-server) on the portal. After this, virtual machine is listed on the portal.
+* **vCenter not connected**: Check if vCenter is in a connected state. To verify, go to Recovery Services vault > Site Recovery Infrastructure > Configuration Servers > Click on respective configuration server > a blade opens on your right with details of associated servers. Check if vCenter is connected. If it's in a "Not Connected" state, resolve the issue, and then [refresh the configuration server](vmware-azure-manage-configuration-server.md#refresh-configuration-server) on the portal. After this, virtual machine isn't listed on the portal.
+* **ESXi powered off**: If the ESXi host under which the virtual machine resides is in a powered-off state, then the virtual machine isn't listed or isn't selectable on the Azure portal. Power on the ESXi host, and [refresh the configuration server](vmware-azure-manage-configuration-server.md#refresh-configuration-server) on the portal. After this, virtual machine is listed on the portal.
 * **Pending reboot**: If there is a pending reboot on the virtual machine, then you won't be able to select the machine on the Azure portal. Ensure to complete the pending reboot activities and [refresh the configuration server](vmware-azure-manage-configuration-server.md#refresh-configuration-server). After this, virtual machine is listed on the portal.
 * **IP not found or Machine does not have an IP address**: If the virtual machine doesn't have a valid IP address associated with it, then you are not able to select the machine on the Azure portal. Ensure to assign a valid IP address to the virtual machine, and [refresh the configuration server](vmware-azure-manage-configuration-server.md#refresh-configuration-server). It could also be caused if the machine does not have a valid IP address associated with one of its NICs. Either assign a valid IP address to all NICs or remove the NIC that's missing the IP. After this, the virtual machine is listed on the portal.
 
@@ -48,7 +48,7 @@ When you try to select the source machine to enable replication by using Site Re
 Virtual machines that are replicated under Site Recovery aren't available in the Azure portal if there are duplicate entries in the system. [Learn more](https://social.technet.microsoft.com/wiki/contents/articles/32026.asr-vmware-to-azure-how-to-cleanup-duplicatestale-entries.aspx) about deleting stale entries and resolving the issue.
 
 
-Another reason could be that the machine was cloned. When machines move between a hypervisor and if BIOS ID changes, then the mobility agent blocks the replication. Replication of cloned machines is not supported by Site Recovery.
+Another reason could be that the machine was cloned. When machines move between a hypervisor and if BIOS ID changes, then the mobility agent blocks the replication. Replication of cloned machines isn't supported by Site Recovery.
 
 ## No crash-consistent recovery point available for the VM in the last 'XXX' minutes
 
@@ -97,10 +97,10 @@ To resolve the issue, use the following steps to verify the network connectivity
 
 ### Process server with no heartbeat [error 806]
 
-In case there's no heartbeat from the Process Server (PS), check that:
+In case there's no heartbeat from the Process Server, check that:
 
-1. PS VM is up and running
-2. Check the following logs on the PS for error details:
+1. Process Server VM is up and running
+2. Check the following logs on the Process Server for error details:
 
     *C:\ProgramData\ASR\home\svsystems\eventmanager\*.log*\
     and\
@@ -142,7 +142,7 @@ To resolve the issue, you can associate the policy with the configuration server
 
 Enhancements have been made in mobility agent [9.23](vmware-physical-mobility-service-overview.md#mobility-service-agent-version-923-and-higher) & [9.27](site-recovery-whats-new-archive.md#update-rollup-39) versions to handle VSS installation failure behaviors. Ensure that you're on the latest versions for best guidance on troubleshooting VSS failures.
 
-Some of the most common issues are listed below
+Some of the most common issues are listed:
 
 #### Cause 1: Known issue in SQL server 2008/2008 R2
 **How to fix**: There is a known issue with SQL server 2008/2008 R2. Please refer this KB article [Azure Site Recovery Agent or other non-component VSS backup fails for a server hosting SQL Server 2008 R2](https://support.microsoft.com/help/4504103/non-component-vss-backup-fails-for-server-hosting-sql-server-2008-r2)
@@ -171,12 +171,12 @@ Search for the string "vacpError"  by opening the vacp.log file in an editor
 
 `Ex: `**`vacpError`**`:220#Following disks are in FilteringStopped state [\\.\PHYSICALDRIVE1=5, ]#220|^|224#FAILED: CheckWriterStatus().#2147754994|^|226#FAILED to revoke tags.FAILED: CheckWriterStatus().#2147754994|^|`
 
-In the above example **2147754994** is the error code that tells you about the failure as shown below
+In the preceeding  example **2147754994** is the error code that tells you about the failure as shown:
 
 #### VSS writer is not installed - Error 2147221164
 
 
-*How to fix*: To generate an application consistency tag, Azure Site Recovery uses Microsoft Volume Shadow copy Service (VSS). It installs a VSS Provider for its operation to take app consistency snapshots. This VSS Provider is installed as a service. In case the VSS Provider service is not installed, the application consistency snapshot creation fails with the error ID 0x80040154  "Class not registered". </br>
+*How to fix*: To generate an application consistency tag, Azure Site Recovery uses Microsoft Volume Shadow copy Service (VSS). It installs a VSS Provider for its operation to take app consistency snapshots. This VSS Provider is installed as a service. In case the VSS Provider service isn't installed, the application consistency snapshot creation fails with the error ID 0x80040154  "Class not registered". </br>
 
 Refer [article for VSS writer installation troubleshooting](./vmware-azure-troubleshoot-push-install.md#vss-installation-failures)
 
@@ -227,7 +227,7 @@ This error occurs when trying to enable replication and the application folders
     - *C:\thirdparty\rrdtool-1.2.15-win32-perl58\rrdtool\Release\**
 
 ## Troubleshoot and handle time changes on replicated servers
-This error occurs when the source machine's time moves forward and then moves back in a short time, to correct the change. You may not notice the change as the time is corrected very quickly.
+This error occurs when the source machine's time moves forward and then moves back in a short time, to correct the change. You may not notice the change as the time is corrected quickly.
 
 **How to fix**: 
 To resolve this issue, wait until the system time crosses the skewed future time. Another option is to disable and enable replication once again, which is only feasible for forward replication (data replicated from on-premises to Azure) and isn't applicable for reverse replication (data replicated from Azure to on-premises).