Merge pull request #100897 from rayne-wiselman/raynejanuary12

updating author

Author: PMEds28

articles/site-recovery/azure-to-azure-common-questions.md

@@ -1,12 +1,10 @@
 ---
 title: Common questions about Azure VM disaster recovery with Azure Site Recovery
-description: This article answers common questions about disaster recovery of Azure VMs to another Azure region using Azure Site Recovery
-author: carmonmills
+description: This article answers common questions about Azure VM disaster recovery using Azure Site Recovery.
+author: sideeksh
 manager: rochakm
-ms.service: site-recovery
 ms.date: 04/29/2019
 ms.topic: conceptual
-ms.author: carmonm
 
 ---
 # Common questions: Azure-to-Azure disaster recovery
@@ -40,7 +38,7 @@ The Site Recovery team works with the Azure capacity management team to plan suf
 Yes, Site Recovery supports disaster recovery of VMs with Azure disk encryption (ADE) enabled. When you enable replication, all the required disk encryption keys and secrets are copied from the source region to the target region in the user context. If you don't have appropriate permission, a ready-to-use script can be handed to the security administrator, to copy the keys and secrets.
 
 - Site Recovery supports ADE for Azure VMs running Windows.
-- Site recovery supports ADE version 0.1, with a schema using Azure Active Directory (AAD), and version 1.1, without AAD. [Learn more](../virtual-machines/extensions/azure-disk-enc-windows.md#extension-schemata).
+- Site Recovery supports ADE version 0.1, with a schema using Azure Active Directory (AAD), and version 1.1, without AAD. [Learn more](../virtual-machines/extensions/azure-disk-enc-windows.md#extension-schemata).
 - ADE version 1.1, the Windows VMs must be used managed disks.
 - [Learn more](azure-to-azure-how-to-enable-replication-ade-vms.md) about enabling replication for encrypted VMs.
 

articles/site-recovery/azure-to-azure-enable-replication-added-disk.md

@@ -1,14 +1,10 @@
 ---
 title: Enable replication for an added Azure VM disk in Azure Site Recovery 
 description: This article describes how to enable replication for a disk added to an Azure VM that's enabled for disaster recovery with Azure Site Recovery
-services: site-recovery
-author: carmonmills
+author: sideeksh
 manager: rochakm
-ms.service: site-recovery
-ms.topic: conceptual
+ms.topic: how-to
 ms.date: 04/29/2019
-ms.author: carmonm
-
 ---
 
 

articles/site-recovery/azure-to-azure-exclude-disks.md

@@ -1,13 +1,12 @@
 ---
 title: Exclude Azure VM disks from replication with Azure Site Recovery and Azure PowerShell
 description: Learn how to exclude disks of Azure virtual machines during Azure Site Recovery by using Azure PowerShell.
-author: carmonmills
+author: sideeksh
 manager: rochakm
-ms.service: site-recovery
-ms.topic: conceptual
+ms.topic: how-to
 ms.date: 02/18/2019
-ms.author: carmonm
 ---
+
 # Exclude disks from PowerShell replication of Azure VMs
 
 This article describes how to exclude disks when you replicate Azure VMs. You might exclude disks to optimize the consumed replication bandwidth or the target-side resources that those disks use. Currently, this capability is available only through Azure PowerShell.

articles/site-recovery/azure-to-azure-how-to-enable-replication-s2d-vms.md

@@ -1,13 +1,10 @@
 ---
-title: Replicate Azure VMs running Storage Spaces Direct using Azure Site Recovery 
-description: This article describes how to replicate Azure VMs running Storage Spaces Direct using Azure Site Recovery.
-services: site-recovery
-author: carmonmills
+title: Replicate Azure VMs running Storage Spaces Direct with Azure Site Recovery 
+description: Learn how to replicate Azure VMs running Storage Spaces Direct using Azure Site Recovery.
+author: sideeksh
 manager: rochakm
-ms.service: site-recovery
-ms.topic: article
+ms.topic: how-to
 ms.date: 01/29/2019
-ms.author: carmonm
 
 ---
 
@@ -19,13 +16,13 @@ This article describes how to enable disaster recovery of Azure VMs running stor
 >Only crash consistent recovery points are supported for storage spaces direct clusters.
 >
 
-## Introduction 
-[Storage spaces direct (S2D)](https://docs.microsoft.com/windows-server/storage/storage-spaces/deploy-storage-spaces-direct) is a software-defined storage, which provides a way to create [guest clusters](https://blogs.msdn.microsoft.com/clustering/2017/02/14/deploying-an-iaas-vm-guest-clusters-in-microsoft-azure) on Azure.  A guest cluster in Microsoft Azure is a Failover Cluster comprised of IaaS VMs. It allows hosted VM workloads to fail over across the guest clusters achieving higher availability SLA for applications than a single Azure VM can provide. It is useful in scenarios where VM hosting a critical application like SQL or Scale out file server etc.
+[Storage spaces direct (S2D)](https://docs.microsoft.com/windows-server/storage/storage-spaces/deploy-storage-spaces-direct) is software-defined storage, which provides a way to create [guest clusters](https://blogs.msdn.microsoft.com/clustering/2017/02/14/deploying-an-iaas-vm-guest-clusters-in-microsoft-azure) on Azure.  A guest cluster in Microsoft Azure is a failover cluster comprised of IaaS VMs. It allows hosted VM workloads to fail over across guest clusters, achieving higher availability SLA for applications, than a single Azure VM can provide. It is useful in scenarios where a VM hosts a critical application like SQL or scale-out file server.
+
+## Disaster recovery with storage spaces direct
 
-## Disaster Recovery of Azure Virtual Machines using Storage spaces direct
 In a typical scenario, you may have virtual machines guest cluster on Azure for higher resiliency of your application like Scale out file server. While this can provide your application higher availability, you would like to protect these applications using Site Recovery for any region level failure. Site Recovery replicates the data from one region to another Azure region and brings up the cluster in disaster recovery region in an event of failover.
 
-Below diagram shows the pictorial representation of two Azure VMs failover cluster using storage spaces direct.
+Below diagram shows a two-node Azure VM failover cluster using storage spaces direct.
 
 ![storagespacesdirect](./media/azure-to-azure-how-to-enable-replication-s2d-vms/storagespacedirect.png)
 
@@ -38,7 +35,7 @@ Below diagram shows the pictorial representation of two Azure VMs failover clust
 **Disaster Recovery Considerations**
 
 1. When you are setting up [cloud witness](https://docs.microsoft.com/windows-server/failover-clustering/deploy-cloud-witness#CloudWitnessSetUp) for the cluster, keep witness in the Disaster Recovery region.
-2. If you are going to fail over the virtual machines to the subnet on the DR region which is different from the source region then cluster IP address needs to be change after failover.  To change IP of the cluster you need to use ASR [recovery plan script.](https://docs.microsoft.com/azure/site-recovery/site-recovery-runbook-automation)</br>
+2. If you are going to fail over the virtual machines to the subnet on the DR region which is different from the source region then cluster IP address needs to be change after failover.  To change IP of the cluster you need to use the Site Recovery [recovery plan script.](https://docs.microsoft.com/azure/site-recovery/site-recovery-runbook-automation)</br>
 [Sample script](https://github.com/krnese/azure-quickstart-templates/blob/master/asr-automation-recovery/scripts/ASR-Wordpress-ChangeMysqlConfig.ps1) to execute command inside VM using custom script extension 
 
 ### Enabling Site Recovery for S2D cluster:
@@ -65,11 +62,11 @@ A recovery plan supports the sequencing of various tiers in a multi-tier applica
 
 
 ### Add scripts to the recovery plan
-For your applications to function correctly, you might need to do some operations on the Azure virtual machines after the failover or during a test failover. You can automate some post-failover operations. For example, here we are attaching loadbalancer and changing cluster IP.
+For your applications to function correctly, you might need to do some operations on the Azure virtual machines after the failover or during a test failover. You can automate some post-failover operations. For example, here we are attaching load balancer and changing cluster IP.
 
 
 ### Failover of the virtual machines 
-Both the nodes of the virtual machines needs to be fail over using the [ASR Recovery plan](https://docs.microsoft.com/azure/site-recovery/site-recovery-create-recovery-plans) 
+Both the nodes of the VMs need to be fail over using the Site Recovery [recovery plan](https://docs.microsoft.com/azure/site-recovery/site-recovery-create-recovery-plans) 
 
 ![storagespacesdirect protection](./media/azure-to-azure-how-to-enable-replication-s2d-vms/recoveryplan.PNG)
 

articles/site-recovery/azure-to-azure-how-to-enable-replication.md

@@ -1,13 +1,10 @@
 ---
-title: Configure replication for Azure VMs in Azure Site Recovery | Microsoft Docs
-description: This article describes how to configure replication for Azure VMs, from one Azure region to another using Site Recovery.
-services: site-recovery
-author: carmonmills
+title: Configure replication for Azure VMs in Azure Site Recovery
+description: Learn how to configure replication to another region for Azure VMs, using Site Recovery.
+author: sideeksh
 manager: rochakm
-ms.service: site-recovery
-ms.topic: conceptual
+ms.topic: how-to
 ms.date: 04/29/2018
-ms.author: carmonm
 
 ---
 

articles/site-recovery/azure-to-azure-troubleshoot-network-connectivity.md

@@ -1,15 +1,12 @@
 ---
 title: Troubleshoot connectivity for Azure to Azure disaster recovery with Azure Site Recovery 
-description: Troubleshoot errors and issues when you replicate Azure virtual machines for disaster recovery
-services: site-recovery
-author: carmonmills
+description: Troubleshoot connectivity issues in Azure VM disaster recovery
+author: sideeksh
 manager: rochakm
-ms.service: site-recovery
-ms.topic: article
+ms.topic: how-to
 ms.date: 08/05/2019
-ms.author: carmonm
-
 ---
+
 # Troubleshoot Azure-to-Azure VM network connectivity issues
 
 This article describes the common issues related to network connectivity when you replicate and recover Azure virtual machines from one region to another region. For more information about networking requirements, see the [connectivity requirements for replicating Azure VMs](azure-to-azure-about-networking.md).

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

@@ -1,16 +1,13 @@
 ---
-title: Troubleshoot ongoing replication of Azrue VMs with Azure Site Recovery 
-description: Troubleshooting errors and problems when replicating Azure virtual machines for disaster recovery
-services: site-recovery
-author: carmonmills
+title: Troubleshoot replication of Azure VMs with Azure Site Recovery 
+description: Troubleshoot replication in Azure VM disaster recovery with Azure Site Recovery
+author: sideeksh
 manager: rochakm
-ms.service: site-recovery
 ms.topic: troubleshooting
 ms.date: 8/2/2019
-ms.author: carmonm
 
 ---
-# Troubleshoot ongoing problems in Azure-to-Azure VM replication
+# Troubleshoot replication in Azure VM disaster recovery
 
 This article describes common problems in Azure Site Recovery when you're replicating and recovering Azure virtual machines from one region to another region. It also explains how to troubleshoot them. For more information about supported configurations, see the [support matrix for replicating Azure VMs](site-recovery-support-matrix-azure-to-azure.md).
 
@@ -62,7 +59,7 @@ If a spike is from an occasional data burst and the data change rate is greater
     - Navigate to the Disks blade of the impacted replicated machine and copy the replica disk name
     - Navigate to this replica managed disk
     - You may see a banner on the Overview blade saying that a SAS URL has been generated. Click on this banner and cancel the export. Ignore this step if you do not see the banner.
-    - As soon as the SAS URL is revoked, go to Configuration blade of the Managed Disk and increase the size so that ASR supports the observed churn rate on source disk
+    - As soon as the SAS URL is revoked, go to Configuration blade of the Managed Disk and increase the size so that Site Recovery supports the observed churn rate on source disk
 
 ## <a name="Network-connectivity-problem"></a>Network connectivity problems
 
@@ -108,12 +105,12 @@ In the above example **2147754994** is the error code that tells you about the f
 
 #### VSS writer is not installed - Error 2147221164 
 
-*How to fix*: To generate 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 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>
 Refer [article for VSS writer installation troubleshooting](https://docs.microsoft.com/azure/site-recovery/vmware-azure-troubleshoot-push-install#vss-installation-failures) 
 
 #### VSS writer is disabled - Error 2147943458
 
-**How to fix**: To generate 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 disabled, the application consistency snapshot creation fails with the error id "The specified service is disabled and cannot be started(0x80070422)". </br>
+**How to fix**: To generate 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 disabled, the application consistency snapshot creation fails with the error ID "The specified service is disabled and cannot be started(0x80070422)". </br>
 
 - If VSS is disabled,
     - Verify that the startup type of the VSS Provider service is set to **Automatic**.

articles/site-recovery/site-recovery-dynamicsax.md

@@ -1,12 +1,10 @@
 ---
-title: Disaster recovery for a multi-tier Dynamics AX deployment with Azure Site Recovery | Microsoft Docs
-description: This article describes how to set up disaster recovery for Dynamics AX with Azure Site Recovery
-author: carmonmills
+title: Disaster recovery of Dynamics AX with Azure Site Recovery 
+description: Learn how to set up disaster recovery for Dynamics AX with Azure Site Recovery
+author: sideeksh
 manager: rochakm
-ms.service: site-recovery
-ms.topic: article
+ms.topic: how-to
 ms.date: 11/27/2018
-ms.author: carmonm
 
 ---
 # Set up disaster recovery for a multitier Dynamics AX application   
@@ -34,7 +32,7 @@ Implementing disaster recovery for Dynamics AX application by using Site Recover
 
 ## Site Recovery support
 
-For the purpose of creating this article, we used VMware virtual machines with Dynamics AX 2012 R3 on Windows Server 2012 R2 Enterprise. Because site recovery replication is application agnostic, we expect the recommendations provided here to hold for the following scenarios.
+For the purpose of creating this article, we used VMware virtual machines with Dynamics AX 2012 R3 on Windows Server 2012 R2 Enterprise. Because Site Recovery replication is application agnostic, we expect the recommendations provided here to hold for the following scenarios.
 
 ### Source and target
 

articles/site-recovery/site-recovery-extension-troubleshoot.md

@@ -1,15 +1,14 @@
 ---
-title: Troubleshoot issues with Azure Site Recovery agents | Microsoft Docs'
-description: Provides information about symptoms, causes, and resolutions of Azure Site Recovery agent failures.
-author: carmonmills
+title: Troubleshoot the Azure VM extension for disaster recovery with Azure Site Recovery
+description: Troubleshoot issues with the Azure VM extension for disaster recovery with Azure Site Recovery.
+author: sideeksh
 manager: rochakm
-ms.service: site-recovery
 ms.topic: troubleshooting
 ms.date: 11/27/2018
-ms.author: carmonm
+
 ---
 
-# Troubleshoot issues with the Azure Site Recovery agent
+# Troubleshoot Azure VM extension issues
 
 This article provides troubleshooting steps that can help you resolve Azure Site Recovery  errors related to VM agent and extension.
 
@@ -25,7 +24,7 @@ Error code: "151076"
 **Cause 2: [The agent installed in the VM is out of date (for Linux VMs)](#the-agent-installed-in-the-vm-is-out-of-date-for-linux-vms)**  
 **Cause 3: [The Site Recovery extension fails to update or load](#the-site-recovery-extension-fails-to-update-or-load)**  
 
-Error message: "Previous site recovery extension operation is taking more time than expected."<br>
+Error message: "Previous Site Recovery extension operation is taking more time than expected."<br>
 Error code: "150066"<br>
 
 **Cause 1: [The agent is installed in the VM, but it's unresponsive (for Windows VMs)](#the-agent-installed-in-the-vm-but-unresponsive-for-windows-vms)**