acro

Author: Ankita Dutta

articles/site-recovery/azure-vm-disaster-recovery-with-accelerated-networking.md

@@ -18,7 +18,7 @@ ms.custom: engagement-fy23
 
 Accelerated Networking enables single root I/O virtualization (SR-IOV) to a VM, greatly improving its networking performance. This high-performance path bypasses the host from the datapath, reducing latency, jitter, and CPU utilization, for use with the most demanding network workloads on supported VM types. The following picture shows communication between two VMs with and without accelerated networking:
 
-:::image type="content" source="./media/azure-vm-disaster-recovery-with-accelerated-networking/accelerated-networking-benefit.png" alt-text="Screenshot of difference between accelerated and non-accelerated networking." lightbox="./media/azure-vm-disaster-recovery-with-accelerated-networking/accelerated-networking-benefit.png":::
+:::image type="content" source="./media/azure-vm-disaster-recovery-with-accelerated-networking/accelerated-networking-benefit.png" alt-text="Screenshot of difference between accelerated and nonaccelerated networking." lightbox="./media/azure-vm-disaster-recovery-with-accelerated-networking/accelerated-networking-benefit.png":::
 
 Azure Site Recovery enables you to utilize the benefits of Accelerated Networking, for Azure virtual machines that are failed over to a different Azure region. This article describes how you can enable Accelerated Networking for Azure virtual machines replicated with Azure Site Recovery.
 
@@ -31,7 +31,7 @@ Before you begin, ensure that you understand:
 
 ## Accelerated Networking with Windows VMs
 
-Azure Site Recovery supports enabling Accelerated Networking for replicated virtual machines only if the source virtual machine has Accelerated Networking enabled. If your source virtual machine does not have Accelerated Networking enabled, you can learn how to enable Accelerated Networking for Windows virtual machines [here](../virtual-network/create-vm-accelerated-networking-powershell.md#enable-accelerated-networking-on-existing-vms).
+Azure Site Recovery supports enabling Accelerated Networking for replicated virtual machines only if the source virtual machine has Accelerated Networking enabled. If your source virtual machine doesn't have Accelerated Networking enabled, you can learn how to enable Accelerated Networking for Windows virtual machines [here](../virtual-network/create-vm-accelerated-networking-powershell.md#enable-accelerated-networking-on-existing-vms).
 
 ### Supported operating systems
 The following distributions are supported out of the box from the Azure Gallery:
@@ -47,7 +47,7 @@ For more information on VM instances, see [Windows VM sizes](../virtual-machines
 
 ## Accelerated Networking with Linux VMs
 
-Azure Site Recovery supports enabling Accelerated Networking for replicated virtual machines only if the source virtual machine has Accelerated Networking enabled. If your source virtual machine does not have Accelerated Networking enabled, you can learn how to enable Accelerated Networking for Linux virtual machines [here](../virtual-network/create-vm-accelerated-networking-cli.md#enable-accelerated-networking-on-existing-vms).
+Azure Site Recovery supports enabling Accelerated Networking for replicated virtual machines only if the source virtual machine has Accelerated Networking enabled. If your source virtual machine doesn't have Accelerated Networking enabled, you can learn how to enable Accelerated Networking for Linux virtual machines [here](../virtual-network/create-vm-accelerated-networking-cli.md#enable-accelerated-networking-on-existing-vms).
 
 ### Supported operating systems
 The following distributions are supported out of the box from the Azure Gallery:
@@ -84,7 +84,7 @@ If you have enabled Accelerated Networking on the source virtual machine after e
 :::image type="content" source="./media/azure-vm-disaster-recovery-with-accelerated-networking/network-interface-accelerated-networking-enabled.png" alt-text="Screenshot of Enable Accelerated Networking." lightbox="./media/azure-vm-disaster-recovery-with-accelerated-networking/network-interface-accelerated-networking-enabled.png":::
 
 
-The above process should also be followed for existing replicated virtual machines, that did not previously have Accelerated Networking enabled automatically by Site Recovery.
+The above process should also be followed for existing replicated virtual machines that didn't previously have Accelerated Networking enabled automatically by Site Recovery.
 
 ## Next steps
 - Learn more about [benefits of Accelerated Networking](../virtual-network/accelerated-networking-overview.md#benefits).

articles/site-recovery/vmware-azure-disaster-recovery-powershell.md

@@ -1,5 +1,5 @@
 ---
-title: Set up VMware disaster recovery using PowerShell in Azure Site Revoery
+title: Set up VMware disaster recovery using PowerShell in Azure Site Recovery
 description: Learn how to set up replication and failover to Azure for disaster recovery of VMware VMs using PowerShell in Azure Site Recovery.
 author: ankitaduttaMSFT
 manager: gaggupta
@@ -16,7 +16,7 @@ ms.custom: devx-track-azurepowershell
 > [!CAUTION]
 > This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
 
-In this article, you see how to replicate and failover VMware virtual machines to Azure using Azure PowerShell.
+In this article, you see how to replicate and fail over VMware virtual machines to Azure using Azure PowerShell.
 
 You learn how to:
 
@@ -39,7 +39,7 @@ Before you start:
 - Review the [support requirements](./vmware-physical-azure-support-matrix.md) for all components.
 - You have the Azure PowerShell `Az`  module. If you need to install or upgrade Azure PowerShell, follow this [Guide to install and configure Azure PowerShell](/powershell/azure/install-azure-powershell).
 
-## Log into Azure
+## Log in to Azure
 
 Log into your Azure subscription using the Connect-AzAccount cmdlet:
 
@@ -53,7 +53,7 @@ Select-AzSubscription -SubscriptionName "ASR Test Subscription"
 ```
 ## Set up a Recovery Services vault
 
-1. Create a resource group in which to create the Recovery Services vault. In the example below, the resource group is named VMwareDRtoAzurePS and is created in the East Asia region.
+1. Create a resource group in which to create the Recovery Services vault. In the following example, the resource group is named VMwareDRtoAzurePS and is created in the East Asia region.
 
    ```azurepowershell
    New-AzResourceGroup -Name "VMwareDRtoAzurePS" -Location "East Asia"
@@ -66,7 +66,7 @@ Select-AzSubscription -SubscriptionName "ASR Test Subscription"
    ResourceId        : /subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/VMwareDRtoAzurePS
    ```
 
-2. Create a Recovery services vault. In the example below, the Recovery services vault is named VMwareDRToAzurePs, and is created in the East Asia region and in the resource group created in the previous step.
+2. Create a Recovery services vault. In the following example, the Recovery services vault is named VMwareDRToAzurePs, and is created in the East Asia region and in the resource group created in the previous step.
 
    ```azurepowershell
    New-AzRecoveryServicesVault -Name "VMwareDRToAzurePs" -Location "East Asia" -ResourceGroupName "VMwareDRToAzurePs"
@@ -96,7 +96,7 @@ Select-AzSubscription -SubscriptionName "ASR Test Subscription"
    C:\Work\VMwareDRToAzurePs_2017-11-23T19-52-34.VaultCredentials
    ```
 
-4. Use the downloaded vault registration key and follow the steps in the articles given below to complete installation and registration of the Configuration Server.
+4. Use the downloaded vault registration key and follow the following steps in the articles to complete installation and registration of the Configuration Server.
    - [Choose your protection goals](vmware-azure-set-up-source.md#choose-your-protection-goals)
    - [Set up the source environment](vmware-azure-set-up-source.md#set-up-the-configuration-server)
 
@@ -107,7 +107,7 @@ Set the vault context using the Set-ASRVaultContext cmdlet. Once set, subsequent
 > [!TIP]
 > The Azure Site Recovery PowerShell module (Az.RecoveryServices module) comes with easy to use aliases for most cmdlets. The cmdlets in the module take the form *\<Operation>-**AzRecoveryServicesAsr**\<Object>* and have equivalent aliases that take the form *\<Operation>-**ASR**\<Object>*. You can replace the cmdlet aliases for ease of use.
 
-In the example below, the vault details from the $vault variable is used to specify the vault context for the PowerShell session.
+In the following example, the vault details from the $vault variable is used to specify the vault context for the PowerShell session.
 
    ```azurepowershell
    Set-ASRVaultContext -Vault $vault
@@ -128,10 +128,10 @@ Subsequent sections of this article assume that the vault context for Azure Site
 
 ## Validate vault registration
 
-For this example, we have the following:
+For this example, we have the following requirements:
 
 - A configuration server (**ConfigurationServer**) has been registered to this vault.
-- An additional process server (**ScaleOut-ProcessServer**) has been registered to *ConfigurationServer*
+- An extra process server (**ScaleOut-ProcessServer**) has been registered to *ConfigurationServer*
 - Accounts (**vCenter_account**, **WindowsAccount**, **LinuxAccount**) have been set up on the Configuration server. These accounts are used to add the vCenter server, to discover virtual machines, and to push-install the mobility service software on Windows and Linux servers that are to be replicated.
 
 1. Registered configuration servers are represented by a fabric object in Site Recovery. Get the list of fabric objects in the vault and identify the configuration server.
@@ -316,7 +316,7 @@ Errors           : {}
 
 ## Create storage accounts for replication
 
-**To write to managed disk, use [PowerShell Az.RecoveryServices module 2.0.0](https://www.powershellgallery.com/packages/Az.RecoveryServices/2.0.0-preview) onwards.** It only requires creation of a log storage account. It is recommended to use a standard account type and LRS redundancy since it is used to store only temporary logs. Ensure that the storage account is created in the same Azure region as the vault.
+**To write to managed disk, use [PowerShell Az.RecoveryServices module 2.0.0](https://www.powershellgallery.com/packages/Az.RecoveryServices/2.0.0-preview) onwards.** It only requires creation of a log storage account. It's recommended to use a standard account type and LRS redundancy since it's used to store only temporary logs. Ensure that the storage account is created in the same Azure region as the vault.
 
 If you are using a version of Az.RecoveryServices module older than 2.0.0, use the following steps to create storage accounts. These storage accounts are used later to replicate virtual machines. Ensure that the storage accounts are created in the same Azure region as the vault. You can skip this step if you plan to use an existing storage account for replication.
 
@@ -348,13 +348,13 @@ You will need the following details to protect a discovered virtual machine:
 * The resource group in which virtual machines must be created on failover.
 * Optionally, the Azure virtual network and subnet to which the failed over virtual machine should be connected.
 
-Now replicate the following virtual machines using the settings specified in this table
+Now replicate the following virtual machines using the settings specified in this table:
 
 
 |Virtual machine  |Process Server        |Storage Account              |Log Storage account  |Policy           |Account for Mobility service installation|Target resource group  | Target virtual network  |Target subnet  |
 |-----------------|----------------------|-----------------------------|---------------------|-----------------|-----------------------------------------|-----------------------|-------------------------|---------------|
 |CentOSVM1       |ConfigurationServer   |N/A| logstorageaccount1                 |ReplicationPolicy|LinuxAccount                             |VMwareDRToAzurePs      |ASR-vnet                 |Subnet-1       |
-|Win2K12VM1       |ScaleOut-ProcessServer|premiumstorageaccount1       |logstorageaccount1   |ReplicationPolicy|WindowsAccount                           |VMwareDRToAzurePs      |ASR-vnet                 |Subnet-1       |   
+|Win 2K12VM1       |ScaleOut-ProcessServer|premiumstorageaccount1       |logstorageaccount1   |ReplicationPolicy|WindowsAccount                           |VMwareDRToAzurePs      |ASR-vnet                 |Subnet-1       |   
 |CentOSVM2       |ConfigurationServer   |replicationstdstorageaccount1| N/A                 |ReplicationPolicy|LinuxAccount                             |VMwareDRToAzurePs      |ASR-vnet                 |Subnet-1       |   
 
 
@@ -448,7 +448,7 @@ Errors           : {}
 
 ## Run a test failover
 
-1. Run a DR drill (test failover) as follows:
+1. Run a disaster recovery drill (test failover) as follows:
 
    ```azurepowershell
    #Test failover of Win2K12VM1 to the test virtual network "V2TestNetwork"
@@ -459,7 +459,7 @@ Errors           : {}
    #Start the test failover operation
    $TFOJob = Start-AzRecoveryServicesAsrTestFailoverJob -ReplicationProtectedItem $ReplicatedVM1 -AzureVMNetworkId $TestFailovervnet.Id -Direction PrimaryToRecovery
    ```
-2. Once the test failover job completes successfully, you will notice that a virtual machine suffixed with *"-Test"* (Win2K12VM1-Test in this case) to its name is created in Azure.
+2. Once the test failover job completes successfully, you'll notice that a virtual machine suffixed with *"-Test"* (Win2K12VM1-Test in this case) to its name is created in Azure.
 3. You can now connect to the test failed over virtual machine, and validate the test failover.
 4. Clean up the test failover using the Start-ASRTestFailoverCleanupJob cmdlet. This operation deletes the virtual machine created as part of the test failover operation.
 

articles/site-recovery/vmware-azure-install-linux-master-target.md

@@ -102,7 +102,7 @@ Keep an Ubuntu 16.04.2 minimal 64-bit ISO in the DVD drive and start the system.
 
 1.  In the next selection for encrypting your home directory, select **No** (the default option), and then select **Enter**.
 
-1. If the time zone that's displayed is correct, select **Yes** (the default option), and then select **Enter**. To reconfigure your time zone, select **No**.
+1. If the time zone displayed is correct, select **Yes** (the default option), and then select **Enter**. To reconfigure your time zone, select **No**.
 
 1. From the partitioning method options, select **Guided - use entire disk**, and then select **Enter**.
 
@@ -125,7 +125,7 @@ Keep an Ubuntu 16.04.2 minimal 64-bit ISO in the DVD drive and start the system.
      ![Select how to manage upgrades](./media/vmware-azure-install-linux-master-target/image18-ubuntu.png)
 
     > [!WARNING]
-    > Because the Azure Site Recovery master target server requires a very specific version of the Ubuntu, you need to ensure that the kernel upgrades are disabled for the virtual machine. If they are enabled, then any regular upgrades cause the master target server to malfunction. Make sure you select the **No automatic updates** option.
+    > Because the Azure Site Recovery master target server requires a very specific version of the Ubuntu, you must ensure that the kernel upgrades are disabled for the virtual machine. If they are enabled, then any regular upgrades cause the master target server to malfunction. Make sure you select the **No automatic updates** option.
 
 1.  Select default options. If you want openSSH for SSH connect, select the **OpenSSH server** option, and then select **Continue**.
 
@@ -181,12 +181,12 @@ To get the ID for each SCSI hard disk in a Linux virtual machine, the **disk.Ena
 
 #### Disable kernel upgrades
 
-Azure Site Recovery master target server requires a specific version of the Ubuntu, ensure that the kernel upgrades are disabled for the virtual machine. If kernel upgrades are enabled,it can cause the master target server to malfunction.
+Azure Site Recovery master target server requires a specific version of the Ubuntu. Ensure that the kernel upgrades are disabled for the virtual machine. If kernel upgrades are enabled, it can cause the master target server to malfunction.
 
-#### Download and install additional packages
+#### Download and install extra packages
 
 > [!NOTE]
-> Make sure that you have Internet connectivity to download and install additional packages. If you don't have Internet connectivity, you need to manually find these Deb packages and install them.
+> Make sure that you have Internet connectivity to download and install extra packages. If you don't have Internet connectivity, you need to manually find these Deb packages and install them.
 
  ```bash
     sudo apt-get install -y multipath-tools lsscsi python-pyasn1 lvm2 kpartx
@@ -354,11 +354,11 @@ After the installation has finished, register the configuration server by using
 
 ### Install VMware tools / open-vm-tools on the master target server
 
-You need to install VMware tools or open-vm-tools on the master target so that it can discover the data stores. If the tools are not installed, the reprotect screen isn't listed in the data stores. After installation of the VMware tools, you need to restart.
+You need to install VMware tools or open-vm-tools on the master target so that it can discover the data stores. If the tools are not installed, the reprotected screen isn't listed in the data stores. After installation of the VMware tools, you need to restart.
 
 ### Upgrade the master target server
 
-Running the installer will automatically detect that the agent is installed on the master target. To complete the upgrade, complete the following steps:
+Running the installer automatically detects that the agent is installed on the master target. To complete the upgrade, complete the following steps:
 1. Copy tar.gz from configuration server to linux master target
 2. Run this command to validate the version you are running: cat /usr/local/.vx_version
 3. Extract tar: tar -xvf latestlinuxmobsvc.tar.gz
@@ -373,7 +373,7 @@ After the setup has been completed, check the version of the master target insta
    sudo cat /usr/local/.vx_version
 ```
 
-You will see that the **Version** field gives the version number of the master target.
+You'll see that the **Version** field gives the version number of the master target.
 
 ## Upgrade OS of master target server from Ubuntu 16.04 to Ubuntu 20.04