Merge pull request #85344 from Rajani-Janaki-Ram/master

ktoliver · web-flow · commit 682125a460c0 · 2019-08-19T07:49:06.000-07:00
Update azure-to-azure-tutorial-migrate.md
diff --git a/articles/site-recovery/azure-to-azure-tutorial-migrate.md b/articles/site-recovery/azure-to-azure-tutorial-migrate.md
@@ -37,46 +37,43 @@ In this tutorial, you will:
 - Review the [support limitations and requirements](azure-to-azure-support-matrix.md).
 - Verify account permissions. If you created your free Azure account, you're the administrator of your subscription. If you're not the subscription administrator, work with the administrator to assign the permissions that you need. To enable replication for a VM and essentially copy data by using Azure Site Recovery, you must have:
 
-    * Permissions to create a VM in Azure resources. The Virtual Machine Contributor built-in role has these permissions, which include:
-        - Permission to create a VM in the selected resource group
-        - Permission to create a VM in the selected virtual network
-        - Permission to write to the selected storage account
-
-    * Permissions to manage Azure Site Recovery operations. The Site Recovery Contributor role has all the permissions that are required to manage Site Recovery operations in a Recovery Services vault.
+    - Permissions to create a VM in Azure resources. The Virtual Machine Contributor built-in role has these permissions, which include:
+    - Permission to create a VM in the selected resource group
+    - Permission to create a VM in the selected virtual network
+    - Permission to write to the selected storage account
+    
+    - Permissions to manage Azure Site Recovery operations. The Site Recovery Contributor role has all the permissions that are required to manage Site Recovery operations in a Recovery Services vault.
 
-## Prepare the source VMs
+- Make sure that all the latest root certificates are on the Azure VMs that you want to move. If the latest root certificates aren't on the VM, security constraints will prevent the data copy to the target region.
 
-1. Make sure that all the latest root certificates are on the Azure VMs that you want to move. If the latest root certificates aren't on the VM, security constraints will prevent the data copy to the target region.
+- For Windows VMs, install all the latest Windows updates on the VM, so that all the trusted root certificates are on the machine. In a disconnected environment, follow the standard Windows Update and certificate update processes for your organization.
+    
+- For Linux VMs, follow the guidance provided by your Linux distributor to get the latest trusted root certificates and certificate revocation list on the VM.
+- Make sure that you're not using an authentication proxy to control network connectivity for VMs that you want to move.
 
-    - For Windows VMs, install all the latest Windows updates on the VM, so that all the trusted root certificates are on the machine. In a disconnected environment, follow the standard Windows Update and certificate update processes for your organization.
-    - For Linux VMs, follow the guidance provided by your Linux distributor to get the latest trusted root certificates and certificate revocation list on the VM.
-1. Make sure that you're not using an authentication proxy to control network connectivity for VMs that you want to move.
-1. If the VM that you're trying to move doesn't have access to the internet, or it's using a firewall proxy to control outbound access, [check the requirements](azure-to-azure-tutorial-enable-replication.md#set-up-outbound-network-connectivity-for-vms).
-1. Identify the source networking layout and all the resources that you're currently using. This includes but isn't limited to load balancers, network security groups (NSGs), and public IPs.
+- If the VM that you're trying to move doesn't have access to the internet, or it's using a firewall proxy to control outbound access, [check the requirements](azure-to-azure-tutorial-enable-replication.md#set-up-outbound-network-connectivity-for-vms).
 
-## Prepare the target region
+- Identify the source networking layout and all the resources that you're currently using. This includes but isn't limited to load balancers, network security groups (NSGs), and public IPs.
 
-1. Verify that your Azure subscription allows you to create VMs in the target region that's used for disaster recovery. Contact support to enable the required quota.
+- Verify that your Azure subscription allows you to create VMs in the target region that's used for disaster recovery. Contact support to enable the required quota.
 
-1. Make sure that your subscription has enough resources to support VMs with sizes that match your source VMs. If you're using Site Recovery to copy data to the target, Site Recovery chooses the same size or the closest possible size for the target VM.
+- Make sure that your subscription has enough resources to support VMs with sizes that match your source VMs. If you're using Site Recovery to copy data to the target, Site Recovery chooses the same size or the closest possible size for the target VM.
 
-1. Make sure that you create a target resource for every component that's identified in the source networking layout. This step is important to ensure that your VMs have all the functionality and features in the target region that you had in the source region.
+- Make sure that you create a target resource for every component that's identified in the source networking layout. This step is important to ensure that your VMs have all the functionality and features in the target region that you had in the source region.
 
-    > [!NOTE]
-    > Azure Site Recovery automatically discovers and creates a virtual network when you enable replication for the source VM. You can also pre-create a network and assign it to the VM in the user flow for enable replication. As mentioned later, you need to manually create any other resources in the target region.
+     > [!NOTE] 
+     > Azure Site Recovery automatically discovers and creates a virtual network when you enable replication for the source VM. You can also pre-create a network and assign it to the VM in the user flow for enable replication. As mentioned later, you need to manually create any other resources in the target region.
 
-     To create the most commonly used network resources that are relevant for you based on the source VM configuration, see the following documentation:
+    To create the most commonly used network resources that are relevant for you based on the source VM configuration, see the following documentation:
+    - [Network security groups](https://docs.microsoft.com/azure/virtual-network/manage-network-security-group)
+    - [Load balancers](https://docs.microsoft.com/azure/load-balancer/#step-by-step-tutorials)
+    -  [Public IP](../virtual-network/virtual-network-public-ip-address.md)
+    - For any other networking components, see the [networking documentation](https://docs.microsoft.com/azure/#pivot=products&panel=network).
 
-   - [Network security groups](https://docs.microsoft.com/azure/virtual-network/manage-network-security-group)
-   - [Load balancers](https://docs.microsoft.com/azure/load-balancer/#step-by-step-tutorials)
-   - [Public IP](../virtual-network/virtual-network-public-ip-address.md)
-    
-     For any other networking components, see the [networking documentation](https://docs.microsoft.com/azure/#pivot=products&panel=network).
 
-1. Manually [create a non-production network](https://docs.microsoft.com/azure/virtual-network/quick-create-portal) in the target region if you want to test the configuration before you perform the final move to the target region. We recommend this step because it ensures minimal interference with the production network.
 
-## Copy data to the target region
-The following steps show you how to use Azure Site Recovery to copy data to the target region.
+## Prepare
+The following steps shows how to prepare the virtual machine for the move using Azure Site Recovery as a solution. 
 
 ### Create the vault in any region, except the source region
 
@@ -103,44 +100,39 @@ Site Recovery retrieves a list of the VMs that are associated with the subscript
 
     ![Enable replication](media/tutorial-migrate-azure-to-azure/settings.png)
 
-## Test the configuration
+## Move
 
-1. Go to the vault. In **Settings** > **Replicated items**, select the VM that you want to move to the target region, and then select **+Test Failover**.
-1. In **Test Failover**, select a recovery point to use for the failover:
+The following steps shows how to perform the move to the target region.
 
-   - **Latest processed**: Fails the VM over to the latest recovery point that was processed by the
-     Site Recovery service. The time stamp is shown. With this option, no time is spent processing
-     data, so it provides a low Recovery Time Objective (RTO).
-   - **Latest app-consistent**: This option fails over all VMs to the latest app-consistent
-     recovery point. The time stamp is shown.
-   - **Custom**: Select any recovery point.
+1. Go to the vault. In **Settings** > **Replicated items**, select the VM, and then select **Failover**.
+2. In **Failover**, select **Latest**.
+3. Select **Shut down machine before beginning failover**. Site Recovery attempts to shut down the source VM before triggering the failover. Failover continues even if shutdown fails. You can follow the failover progress on the **Jobs** page.
+4. After the job is finished, check that the VM appears in the target Azure region as expected.
 
-1. Select the target Azure virtual network to which you want to move the Azure VMs to test the configuration.
-    > [!IMPORTANT]
-    > We recommend that you use a separate Azure VM network for the test failover. Don't use the production network that was set up when you enabled replication and that you want to move your VMs into eventually.
-1. To start testing the move, click **OK**. To track progress, click the VM to open its properties. Or,
-   you can click the **Test Failover** job in the vault name > **Settings** > **Jobs** > **Site Recovery jobs**.
-1. After the failover finishes, the replica Azure VM appears in the Azure portal > **Virtual Machines**. Make sure that the VM is running, is sized appropriately, and is connected to the appropriate network.
-1. If you want to delete the VM tha was created as part of testing the move, click **Cleanup test failover** on the replicated item. In **Notes**, record and save any observations that are associated with the test.
 
-## Perform the move to the target region and confirm
+## Discard 
 
-1. Go to the vault. In **Settings** > **Replicated items**, select the VM, and then select **Failover**.
-1. In **Failover**, select **Latest**.
-1. Select **Shut down machine before beginning failover**. Site Recovery attempts to shut down the source VM before triggering the failover. Failover continues even if shutdown fails. You can follow the failover progress on the **Jobs** page.
-1. After the job is finished, check that the VM appears in the target Azure region as expected.
-1. In **Replicated items**, right-select the VM > **Commit**. This step finishes the move process to the target region. Wait until the commit job finishes.
+In case you checked the moved VM and need to make changed to point of failover or want to go back to a previous point, in the **Replicated items**, right-select the VM > **Change recovery point**. This step provides you the option to specify a different recovery point and failover to that one. 
+
+
+## Commit 
+
+Once you have checked the moved VM and are ready to commit the change, in the **Replicated items**, right-select the VM > **Commit**. This step finishes the move process to the target region. Wait until the commit job finishes.
+
+## Clean up
+
+The following steps will guide you through how to clean up the source region as well as related resources that were used for the move.
 
-## Delete the resource in the source region
+For all resources that were used for the move:
 
-Go to the VM. Select **Disable Replication**. This step stops the process from copying the data for the VM.
+- Go to the VM. Select **Disable Replication**. This step stops the process from copying the data for the VM.
 
-> [!IMPORTANT]
-> It's important to perform this step to avoid being charged for Azure Site Recovery replication.
+   > [!IMPORTANT]
+   > It's important to perform this step to avoid being charged for Azure Site Recovery replication.
 
-If you have no plans to reuse any of the source resources, follow these steps:
+If you have no plans to reuse any of the source resources, complete these additional steps:
 
-1. Delete all the relevant network resources in the source region that you listed out as part of step 4 in [Prepare the source VMs](#prepare-the-source-vms).
+1. Delete all the relevant network resources in the source region that you identified in [prerequisites](#prerequisites).
 1. Delete the corresponding storage account in the source region.
 
 ## Next steps
