MicrosoftDocs
diff --git a/‎articles/site-recovery/azure-stack-site-recovery.md
Lines changed: 26 additions & 31 deletions b/‎articles/site-recovery/azure-stack-site-recovery.md
Lines changed: 26 additions & 31 deletions
@@ -1,17 +1,12 @@
 ---
 title: Replicate Azure Stack VMs to Azure using Azure Site Recovery | Microsoft Docs
 description: Learn how to set up disaster recovery to Azure for Azure Stack VMs with the Azure Site Recovery service.
-services: site-recovery
-author: rayne-wiselman
-manager: carmonm
 ms.topic: conceptual
-ms.service: site-recovery
 ms.date: 08/05/2019
-ms.author: raynew
 ---
 # Replicate Azure Stack VMs to Azure
 
-This article shows you how to set up disaster recovery Azure Stack VMs to Azure, using the [Azure Site Recovery service](https://docs.microsoft.com/azure/site-recovery/site-recovery-overview).
+This article shows you how to set up disaster recovery Azure Stack VMs to Azure, using the [Azure Site Recovery service](site-recovery-overview.md).
 
 Site Recovery contributes to your business continuity and disaster recovery (BCDR) strategy. The service ensures that your VM workloads remain available when expected and unexpected outages occur.
 
@@ -39,9 +34,9 @@ With these steps complete, you can then run a full failover to Azure as and when
 
 **Location** | **Component** |**Details**
 --- | --- | ---
-**Configuration server** | Runs on a single Azure Stack VM. | In each subscription you set up a configuration server VM. This VM runs the following Site Recovery components:<br/><br/> - Configuration server: Coordinates communications between on-premises and Azure, and manages data replication. - Process server: Acts as a replication gateway. It receives replication data, optimizes with caching, compression, and encryption; and sends it to Azure storage.<br/><br/> If VMs you want to replicate exceed the limits stated below, you can set up a separate standalone process server. [Learn more](https://docs.microsoft.com/azure/site-recovery/vmware-azure-set-up-process-server-scale).
-**Mobility service** | Installed on each VM you want to replicate. | In the steps in this article, we prepare an account so that the Mobility service is installed automatically on a VM when replication is enabled. If you don't want to install the service automatically, there are a number of other methods you can use. [Learn more](https://docs.microsoft.com/azure/site-recovery/vmware-azure-install-mobility-service).
-**Azure** | In Azure you need a Recovery Services vault, a storage account, and a virtual network. |  Replicated data is stored in the storage account. Azure VMs are added to the Azure network when failover occurs. 
+**Configuration server** | Runs on a single Azure Stack VM. | In each subscription you set up a configuration server VM. This VM runs the following Site Recovery components:<br/><br/> - Configuration server: Coordinates communications between on-premises and Azure, and manages data replication. - Process server: Acts as a replication gateway. It receives replication data, optimizes with caching, compression, and encryption; and sends it to Azure storage.<br/><br/> If VMs you want to replicate exceed the limits stated below, you can set up a separate standalone process server. [Learn more](vmware-azure-set-up-process-server-scale.md).
+**Mobility service** | Installed on each VM you want to replicate. | In the steps in this article, we prepare an account so that the Mobility service is installed automatically on a VM when replication is enabled. If you don't want to install the service automatically, there are a number of other methods you can use. [Learn more](vmware-azure-install-mobility-service.md).
+**Azure** | In Azure you need a Recovery Services vault, a storage account, and a virtual network. |  Replicated data is stored in the storage account. Azure VMs are added to the Azure network when failover occurs.
 
 
 Replication works as follows:
@@ -62,16 +57,16 @@ Here's what you need to set up this scenario.
 **Requirement** | **Details**
 --- | ---
 **Azure subscription account** | If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/pricing/free-trial/).
-**Azure account permissions** | The Azure account you use needs permissions to:<br/><br/> - Create a Recovery Service vault<br/><br/> - Create a virtual machine in the resource group and virtual network you use for the scenario<br/><br/> - Write to the storage account you specify<br/><br/> Note that:<br/><br/> -If you create an account, you're the administrator of your subscription and can perform all actions.<br/><br/> - If you use an existing subscription and you're not the administrator, you need to work with the admin to assign you Owner or Contributor permissions.<br/><br/> - If you need more granular permissions, review [this article](https://docs.microsoft.com/azure/site-recovery/site-recovery-role-based-linked-access-control). 
-**Azure Stack VM** | You need an Azure Stack VM in the tenant subscription, that will be deployed as the Site Recovery configuration server. 
+**Azure account permissions** | The Azure account you use needs permissions to:<br/><br/> - Create a Recovery Service vault<br/><br/> - Create a virtual machine in the resource group and virtual network you use for the scenario<br/><br/> - Write to the storage account you specify<br/><br/> Note that:<br/><br/> -If you create an account, you're the administrator of your subscription and can perform all actions.<br/><br/> - If you use an existing subscription and you're not the administrator, you need to work with the admin to assign you Owner or Contributor permissions.<br/><br/> - If you need more granular permissions, review [this article](site-recovery-role-based-linked-access-control.md).
+**Azure Stack VM** | You need an Azure Stack VM in the tenant subscription, that will be deployed as the Site Recovery configuration server.
 
 
 ### Prerequisites for the configuration server
 
 [!INCLUDE [site-recovery-config-server-reqs-physical](../../includes/site-recovery-config-server-reqs-physical.md)]
 
 
- 
+
 ## Step 1: Prepare Azure Stack VMs
 
 ### Verify the operating system
@@ -83,7 +78,7 @@ Make sure that the VMs are running one of the operating systems summarized in th
 --- | ---
 **64-bit Windows** | Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2 (from SP1)
 **CentOS** | 5.2 to 5.11, 6.1 to 6.9, 7.0 to 7.3
-**Ubuntu** | 14.04 LTS server, 16.04 LTS server. Review [supported kernels](https://docs.microsoft.com/azure/site-recovery/vmware-physical-azure-support-matrix#ubuntu-kernel-versions)
+**Ubuntu** | 14.04 LTS server, 16.04 LTS server. Review [supported kernels](vmware-physical-azure-support-matrix.md#ubuntu-kernel-versions)
 
 ### Prepare for Mobility service installation
 
@@ -103,10 +98,10 @@ Every VM you want to replicate must have the Mobility service installed. In orde
     - To do this, run **wf.msc** to open the Windows Firewall console. Right click **Inbound Rules** > **New Rule**. Select **Predefined**, and choose **File and Printer sharing** from the list. Complete the wizard, select to allow the connection > **Finish**.
     - For domain computers, you can use a GPO to do this.
 
-    
+
 #### Linux machines
 
-- Ensure that there’s network connectivity between the Linux computer and the process server.
+- Ensure that there's network connectivity between the Linux computer and the process server.
 - On the machine for which you enable replication, you need an account that's a root user on the source Linux server:
     - You specify this account when you set up Site Recovery. Then the process server uses this account to install the Mobility service when replication is enabled.
     - This account will only be used by Site Recovery for the push installation, and to update the Mobility service.
@@ -137,7 +132,7 @@ For each machine you want to replicate, find the IP address:
 ## Step 2: Create a vault and select a replication goal
 
 1. In the Azure portal, select **Create a resource** > **Management Tools** > **Backup and Site Recovery**.
-2. In **Name**, enter a friendly name to identify the vault. 
+2. In **Name**, enter a friendly name to identify the vault.
 3. In **Resource group**, create or select a resource group. We're using **contosoRG**.
 4. In **Location**, enter the Azure region. We're using **West Europe**.
 5. To quickly access the vault from the dashboard, select **Pin to dashboard** > **Create**.
@@ -169,22 +164,22 @@ Set up the configuration server machine, register it in the vault, and discover
 5. Download the Site Recovery Unified Setup installation file.
 6. Download the vault registration key. You need the registration key when you run Unified Setup. The key is valid for five days after you generate it.
 
-	![Set up source](./media/azure-stack-site-recovery/set-source2.png)
+    ![Set up source](./media/azure-stack-site-recovery/set-source2.png)
 
 
 ### Run Azure Site Recovery Unified Setup
 
 To install and register the configuration server, do an RDP connection to the VM you want to use for the configuration server, and run Unified Setup.
 
-Before you start, make sure that the clock is [synchronized with a time server](https://technet.microsoft.com/windows-server-docs/identity/ad-ds/get-started/windows-time-service/windows-time-service) on the VM before you start. Installation fails if the time is more than five minutes off local time.
+Before you start, make sure that the clock is [synchronized with a time server](/windows-server/networking/windows-time-service/windows-time-service-top) on the VM before you start. Installation fails if the time is more than five minutes off local time.
 
 Now install the configuration server:
 
 [!INCLUDE [site-recovery-add-configuration-server](../../includes/site-recovery-add-configuration-server.md)]
 
 > [!NOTE]
 > The configuration server can also be installed from the command line. [Learn more](physical-manage-configuration-server.md#install-from-the-command-line).
-> 
+>
 > It can take 15 minutes or more for the account name to appear in the portal. To update immediately, select **Configuration Servers** > ***server name*** > **Refresh Server**.
 
 ## Step 4: Set up the target environment
@@ -243,9 +238,9 @@ Make sure you've completed all the tasks in [Step 1: Prepare machine](#step-1-pr
 
 > [!NOTE]
 > Site Recovery installs Mobility Service when replication is enabled for a VM.
-> 
+>
 > It can take 15 minutes or longer for changes to take effect and appear in the portal.
-> 
+>
 > To monitor VMs you add, check the last discovered time for VMs in **Configuration Servers** > **Last Contact At**. To add VMs without waiting for the scheduled discovery, highlight the configuration server (don't select it) and select **Refresh**.
 
 
@@ -255,16 +250,16 @@ You run a test failover to Azure to make sure that everything's working as expec
 
 ### Verify machine properties
 
-Before you run a test failover, verify the machine properties, and make sure that they comply with [Azure requirements](https://docs.microsoft.com/azure/site-recovery/vmware-physical-azure-support-matrix#azure-vm-requirements). You can view and modify properties as follows:
+Before you run a test failover, verify the machine properties, and make sure that they comply with [Azure requirements](vmware-physical-azure-support-matrix.md#azure-vm-requirements). You can view and modify properties as follows:
 
 1. In **Protected Items**, click **Replicated Items** > VM.
 2. In the **Replicated item** pane, there's a summary of VM information, health status, and the latest available recovery points. Click **Properties** to view more details.
 3. In **Compute and Network**, modify settings as needed.
 
-    - You can modify the Azure VM name, resource group, target size, [availability set](../virtual-machines/windows/tutorial-availability-sets.md), and managed disk settings.
+    - You can modify the Azure VM name, resource group, target size, [availability set](/azure/virtual-machines/windows/tutorial-availability-sets), and managed disk settings.
     - You can also view and modify network settings. These include the network/subnet to which the Azure VM is joined after failover, and the IP address that will be assigned to the VM.
 1. In **Disks**, view information about the operating system and data disks on the VM.
-   
+
 
 ### Run a test failover
 
@@ -283,27 +278,27 @@ When you run a test failover, the following happens:
 Run a test failover for a VM as follows:
 
 1. In **Settings** > **Replicated Items**, click the VM > **+Test Failover**.
-2. For this walkthrough, we'll select to use the **Latest processed** recovery point. 
+2. For this walkthrough, we'll select to use the **Latest processed** recovery point.
 3. In **Test Failover**, select the target Azure network.
 4. Click **OK** to begin the failover.
 5. Track progress by clicking on the VM to open its properties. Or, click the **Test Failover** job in *vault name* > **Settings** > **Jobs** >**Site Recovery jobs**.
 6. After the failover finishes, the replica Azure VM appears in the Azure portal > **Virtual Machines**. Check that the VM is the appropriate size, connected to the right network, and running.
-7. You should now be able to connect to the replicated VM in Azure. [Learn more](https://docs.microsoft.com/azure/site-recovery/site-recovery-test-failover-to-azure#prepare-to-connect-to-azure-vms-after-failover).
+7. You should now be able to connect to the replicated VM in Azure. [Learn more](site-recovery-test-failover-to-azure.md#prepare-to-connect-to-azure-vms-after-failover).
 8. To delete Azure VMs created during the test failover, click **Cleanup test failover** on the VM. In **Notes**, save any observations associated with the test failover.
 
 ## Fail over and fail back
 
 After you've set up replication, and run a drill to make sure everything's working, you can fail machines over to Azure as required.
 
-Before you run a failover, if you want to connect to the machine in Azure after the failover, then [prepare to connect](https://docs.microsoft.com/azure/site-recovery/site-recovery-test-failover-to-azure#prepare-to-connect-to-azure-vms-after-failover) before you start.
+Before you run a failover, if you want to connect to the machine in Azure after the failover, then [prepare to connect](site-recovery-test-failover-to-azure.md#prepare-to-connect-to-azure-vms-after-failover) before you start.
 
 Then run a failover as follows:
 
 
 1. In **Settings** > **Replicated Items**, click the machine > **Failover**.
 2. Select the recovery point that you want to use.
 3. In **Test Failover**, select the target Azure network.
-4. Select **Shut down machine before beginning failover**. With this setting, Site Recovery tries to shut down the source machine before starting the failover. However failover continues even if shutdown fails. 
+4. Select **Shut down machine before beginning failover**. With this setting, Site Recovery tries to shut down the source machine before starting the failover. However failover continues even if shutdown fails.
 5. Click **OK** to begin the failover. You can follow the failover progress on the **Jobs** page.
 6. After the failover finishes, the replica Azure VM appears in the Azure portal > **Virtual Machines**. If you prepared to connect after failover, check that the VM is the appropriate size, connected to the right network, and running.
 7. After verifying the VM, click **Commit** to finish the failover. This deletes all available recovery points.
@@ -316,18 +311,18 @@ Then run a failover as follows:
 
 When your primary site is up and running again, you can fail back from Azure to Azure Stack. To do this, you need to download the Azure VM VHD, and upload it to Azure Stack.
 
-1. Shut down the Azure VM, so that the VHD can be downloaded. 
+1. Shut down the Azure VM, so that the VHD can be downloaded.
 2. To start downloading the VHD, install [Azure Storage Explorer](https://azure.microsoft.com/features/storage-explorer/).
 3. Navigate to the VM in the Azure Portal (using the VM name).
 4. In **Disks**, click on the disk name, and gather settings.
 
-    - As an example, the VHD URI used in our test: https://502055westcentralus.blob.core.windows.net/wahv9b8d2ceb284fb59287/copied-3676553984.vhd can be broken down to get the following input parameters that are used to download the VHD.
+    - As an example, the VHD URI used in our test: `https://502055westcentralus.blob.core.windows.net/wahv9b8d2ceb284fb59287/copied-3676553984.vhd` can be broken down to get the following input parameters that are used to download the VHD.
         - Storage Account: 502055westcentralus
         - Container: wahv9b8d2ceb284fb59287
         - VHD Name: copied-3676553984.vhd
 
 5. Now, use Azure Storage Explorer to download the VHD.
-6. Upload the VHD to Azure Stack with [these steps](https://docs.microsoft.com/azure/azure-stack/user/azure-stack-manage-vm-disks#use-powershell-to-add-multiple-disks-to-a-vm).
+6. Upload the VHD to Azure Stack with [these steps](/azure-stack/user/azure-stack-manage-vm-disks#use-powershell-to-add-multiple-disks-to-a-vm).
 7. In the existing VM or new VM, attach the uploaded VHDs.
 8. Check that the OS Disk is correct, and start the VM.