Merge pull request #228914 from ankitaduttaMSFT/NIC-Disk

NIC disk renaming

Author: denrea

articles/site-recovery/azure-to-azure-customize-networking.md

@@ -6,8 +6,9 @@ author: ankitaduttaMSFT
 manager: gaggupta
 ms.service: site-recovery
 ms.topic: article
-ms.date: 10/01/2021
+ms.date: 03/27/2023
 ms.author: ankitadutta
+ms.custom: engagement-fy23
 
 ---
 # Customize networking configurations of the target Azure VM
@@ -36,14 +37,14 @@ You can provide the following key resource configurations for the failover VM wh
 
 1. Go to **Replicated Items**. 
 2. Select the desired Azure VM.
-3. Select **Network** and select **Edit**. Notice that the NIC configuration settings include the corresponding resources at the source. 
+3. Select **Network** and select **Edit**. Notice that the NIC configuration settings include the corresponding resources at the source.
 
-    :::image type="content" source="./media/azure-to-azure-customize-networking/edit-networking-properties.png" alt-text="Customize the failover networking configurations" lightbox="./media/azure-to-azure-customize-networking/edit-networking-properties-expanded.png":::
+    :::image type="content" source="./media/azure-to-azure-customize-networking/edit-networking-properties.png" alt-text="Screenshot of how to Customize the failover networking configurations." lightbox="./media/azure-to-azure-customize-networking/edit-networking-properties.png":::
 
 4. Select a test failover virtual network.
 5. Select the NIC tab you want to configure. Now, select the corresponding pre-created resources in the test failover and failover location.
 
-    :::image type="content" source="./media/azure-to-azure-customize-networking/nic-drilldown.png" alt-text="Edit the NIC configuration" lightbox="./media/azure-to-azure-customize-networking/nic-drilldown-expanded.png":::
+    :::image type="content" source="./media/azure-to-azure-customize-networking/nic-drilldown-expanded.png" alt-text="Screenshot of Edit the NIC configuration." lightbox="./media/azure-to-azure-customize-networking/nic-drilldown-expanded.png":::
 
 6. Select **OK**.
 
@@ -78,4 +79,9 @@ Network security group:
 
 
 > [!WARNING]
-> If the target VM is associated with an availability set, then you need to associate the public IP and internal load balancer of the same SKU with that of the other VM's public IP and internal load balancer in the availability set. If you don't, failover might not succeed.
+> If the target VM is associated with an availability set, then you need to associate the public IP and internal load balancer of the same SKU with that of the other VM's public IP and internal load balancer in the availability set. If you don't, failover might not succeed.
+
+## Next steps
+
+- Review [networking guidance](./azure-to-azure-about-networking.md) for Azure VM disaster recovery.
+- [Learn more](site-recovery-retain-ip-azure-vm-failover.md) about retaining IP addresses after failover.

articles/site-recovery/azure-to-azure-network-mapping.md

@@ -5,7 +5,7 @@ author: ankitaduttaMSFT
 manager: rochakm
 ms.service: site-recovery
 ms.topic: conceptual
-ms.date: 7/25/2021
+ms.date: 03/27/2023
 ms.author: ankitadutta
 ms.custom: engagement-fy23
 
@@ -27,14 +27,14 @@ Map networks as follows:
 
 1. In **Site Recovery Infrastructure**, click **+Network Mapping**.
 
-    ![ Create a network mapping](./media/site-recovery-network-mapping-azure-to-azure/network-mapping1.png)
+    :::image type="content" source="./media/site-recovery-network-mapping-azure-to-azure/network-mapping1.png" alt-text="Screenshot of Create a network mapping." lightbox="./media/site-recovery-network-mapping-azure-to-azure/network-mapping1.png":::
 
 3. In **Add network mapping**, select the source and target locations. In our example, the source VM is running in the East Asia region, and replicates to the Southeast Asia region.
 
-    ![Select source and target](./media/site-recovery-network-mapping-azure-to-azure/network-mapping2.png)
+    :::image type="content" source="./media/site-recovery-network-mapping-azure-to-azure/network-mapping2.png" alt-text="Screenshot of Select source and target." lightbox="./media/site-recovery-network-mapping-azure-to-azure/network-mapping2.png":::
 3. Now create a network mapping in the opposite direction. In our example, the source will now be Southeast Asia, and the target will be East Asia.
 
-    ![Add network mapping pane - Select source and target locations for the target network](./media/site-recovery-network-mapping-azure-to-azure/network-mapping3.png)
+    :::image type="content" source="./media/site-recovery-network-mapping-azure-to-azure/network-mapping3.png" alt-text="Screenshot of Add network mapping pane - Select source and target locations for the target network." lightbox="./media/site-recovery-network-mapping-azure-to-azure/network-mapping3.png":::
 
 
 ## Map networks when you enable replication
@@ -59,8 +59,7 @@ The subnet of the target VM is selected based on the name of the subnet of the s
 - If a subnet with the same name doesn't exist in the target network, the first subnet in the alphabetical order is set as the target subnet.
 - You can modify the target subnet in the **Network** settings for the VM.
 
-    ![Network compute properties window](./media/site-recovery-network-mapping-azure-to-azure/modify-subnet.png)
-
+    :::image type="content" source="./media/site-recovery-network-mapping-azure-to-azure/modify-subnet.png" alt-text="Screenshot of Network compute properties window." lightbox="./media/site-recovery-network-mapping-azure-to-azure/modify-subnet.png":::
 
 ## Set up IP addressing for target VMs
 
@@ -88,7 +87,7 @@ Different address space | The next available IP address in the target subnet is
 **Target network** | **Details**
 --- | ---
 Target network is the failover VNet | - Target IP address will be static with the same IP address. <br/><br/>  - If the same IP address is already assigned, then the IP address is the next one available at the end of the subnet range. For example: If the source IP address is 10.0.0.19 and failover network uses range 10.0.0.0/24, then the next IP address assigned to the target VM is 10.0.0.254.
-Target network isn't the failover VNet | - Target IP address will be static with the same IP address, only if it is available in the target virtual network. <br/><br/>  - If the same IP address is already assigned, then the IP address is the next one available at the end of the subnet range.<br/><br/> For example: If the source static IP address is 10.0.0.19 and failover is on an network that isn't the failover network, with the range 10.0.0.0/24, then the target static IP address will be 10.0.0.19 if available, and otherwise it will be 10.0.0.254.
+Target network isn't the failover VNet | - Target IP address will be static with the same IP address, only if it is available in the target virtual network. <br/><br/>  - If the same IP address is already assigned, then the IP address is the next one available at the end of the subnet range.<br/><br/> For example: If the source static IP address is 10.0.0.19 and failover is on a network that isn't the failover network, with the range 10.0.0.0/24, then the target static IP address will be 10.0.0.19 if available, and otherwise it will be 10.0.0.254.
 
 - The failover VNet is the target network that you select when you set up disaster recovery.
 - We recommend that you always use a non-production network for test failover.

articles/site-recovery/azure-to-azure-support-matrix.md

@@ -275,6 +275,7 @@ This table summarized support for the Azure VM OS disk, data disk, and temporary
 
 **Component** | **Support** | **Details**
 --- | --- | ---
+Disk renaming | Supported | You can rename NICs in the target region based on your organization's naming conventions.
 OS disk maximum size | 4096 GB | [Learn more](../virtual-machines/managed-disks-overview.md) about VM disks.
 Temporary disk | Not supported | The temporary disk is always excluded from replication.<br/><br/> Don't store any persistent data on the temporary disk. [Learn more](../virtual-machines/managed-disks-overview.md).
 Data disk maximum size | 32 TB for managed disks<br></br>4     TB for unmanaged disks|
@@ -354,7 +355,7 @@ Premium P20 or P30 or P40 or P50 disk | 16 KB or greater |20 MB/s | 1684 GB per
 
 **Setting** | **Support** | **Details**
 --- | --- | ---
-NIC | Maximum number supported for a specific Azure VM size | NICs are created when the VM is created during failover.<br/><br/> The number of NICs on the failover VM depends on the number of NICs on the source VM when replication was enabled. If you add or remove a NIC after enabling replication, it doesn't impact the number of NICs on the replicated VM after failover. <br/><br/> The order of NICs after failover isn't guaranteed to be the same as the original order. <br/><br/> You can rename NICs in the target region based on your organization's naming conventions. NIC renaming is supported using PowerShell.
+NIC | Maximum number supported for a specific Azure VM size | NICs are created when the VM is created during failover.<br/><br/> The number of NICs on the failover VM depends on the number of NICs on the source VM when replication was enabled. If you add or remove a NIC after enabling replication, it doesn't impact the number of NICs on the replicated VM after failover. <br/><br/> The order of NICs after failover isn't guaranteed to be the same as the original order. <br><br> You can rename NICs in the target region based on your organization's naming conventions.
 Internet Load Balancer | Not supported | You can set up public/internet load balancers in the primary region. However, public/internet load balancers aren't supported by Azure Site Recovery in the DR region.
 Internal Load balancer | Supported | Associate the preconfigured load balancer using an Azure Automation script in a recovery plan.
 Public IP address | Supported | Associate an existing public IP address with the NIC. Or, create a public IP address and associate it with the NIC using an Azure Automation script in a recovery plan.

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

@@ -7,15 +7,16 @@ author: ankitaduttaMSFT
 manager: gaggupta
 ms.service: site-recovery
 ms.topic: conceptual
-ms.date: 04/08/2019
+ms.date: 03/27/2023
 ms.author: ankitadutta
+ms.custom: engagement-fy23
 
 ---
 # Accelerated Networking with Azure virtual machine disaster recovery
 
 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:
 
-![Comparison](./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 non-accelerated 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.
 
@@ -69,14 +70,17 @@ When you [enable replication](azure-to-azure-tutorial-enable-replication.md) for
 
 The status of Accelerated Networking can be verified under the respective NIC's Tab in the **Network** settings for the replicated virtual machine.
 
-![Accelerated Networking setting](./media/azure-vm-disaster-recovery-with-accelerated-networking/compute-network-accelerated-networking.png)
+:::image type="content" source="./media/azure-vm-disaster-recovery-with-accelerated-networking/compute-network-accelerated-networking.png" alt-text="Screenshot of Accelerated Networking setting." lightbox="./media/azure-vm-disaster-recovery-with-accelerated-networking/compute-network-accelerated-networking.png":::
+
+
 
 If you have enabled Accelerated Networking on the source virtual machine after enabling replication, you can enable Accelerated Networking for the replicated virtual machine's network interfaces by the following process:
 1. Open **Network** settings for the replicated virtual machine
 2. Click on the name of the network interface under the **Network interfaces** section
 3. Select **Enabled** from the dropdown for Accelerated Networking under the **Target** column
 
-![Enable Accelerated Networking](./media/azure-vm-disaster-recovery-with-accelerated-networking/network-interface-accelerated-networking-enabled.png)
+:::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.
 

articles/site-recovery/concepts-multiple-ip-address-failover.md

@@ -6,8 +6,9 @@ author: ankitaduttaMSFT
 manager: gaggupta
 ms.service: site-recovery
 ms.topic: conceptual
-ms.date: 11/01/2021
+ms.date: 03/27/2023
 ms.author: ankitadutta
+ms.custom: engagement-fy23
 
 ---
 # Configure failover of multiple IP addresses with Azure Site Recovery
@@ -20,32 +21,34 @@ Today, Site Recovery automatically configures the failover of the Primary IP Con
 
 Site Recovery automatically configures the failover of your Primary IP Configuration when you Enable Replication for the VM. Secondary IP Configurations need to be manually configured after the Enable Replication completes. For this you need a protected VM that has one or more Secondary IP Configurations.
 
-Follow the steps as outlined:
+**Follow these steps:**
+
 1. Navigate to the **Network** blade on the Replicated Items page.
 
-    :::image type="content" source="./media/concepts-multiple-ip-address-failover/network-tab.png" alt-text="Replicated Items Blade":::
+    :::image type="content" source="./media/concepts-multiple-ip-address-failover/network-tab.png" alt-text="Screenshot of Replicated Items Blade.":::
 
 
 2. You will see the following highlighted text.  Click on **Edit** to modify it.
 
-    :::image type="content" source="./media/concepts-multiple-ip-address-failover/network-edit.png" alt-text="Network Tab Edit Mode" lightbox="./media/concepts-multiple-ip-address-failover/network-edit-expanded.png":::    
+    :::image type="content" source="./media/concepts-multiple-ip-address-failover/network-edit.png" alt-text="Screenshot of Network Tab Edit Mode." lightbox="./media/concepts-multiple-ip-address-failover/network-edit-expanded.png":::    
 
 3. Click on "+ IP Configurations". You will see two options, Either add all IP Configurations, or selectively add IP Configurations.
 
-    :::image type="content" source="./media/concepts-multiple-ip-address-failover/add-ip-configurations.png" alt-text="Add IP Configurations":::
+    :::image type="content" source="./media/concepts-multiple-ip-address-failover/add-ip-configurations.png" alt-text="Screenshot of Add IP Configurations.":::
 
 4. On clicking **Add all secondary IP Configurations**, all of them will appear in the grid below, and then you can configure them as you like.
 
-    :::image type="content" source="./media/concepts-multiple-ip-address-failover/add-all-ip-configurations.png" alt-text="Add All IP Configurations" lightbox="./media/concepts-multiple-ip-address-failover/add-all-ip-configurations-expanded.png":::    
+    :::image type="content" source="./media/concepts-multiple-ip-address-failover/add-all-ip-configurations.png" alt-text="Screenshot of All IP Configurations." lightbox="./media/concepts-multiple-ip-address-failover/add-all-ip-configurations-expanded.png":::    
 
 5. Alternatively, on clicking **Select and add secondary IP Configurations**, a blade will open where you can pick and add IP Configurations you'd like to configure for failover.
 
-    :::image type="content" source="./media/concepts-multiple-ip-address-failover/select-and-add-ip-configurations.png" alt-text="Select and Add IP Configurations":::
+    :::image type="content" source="./media/concepts-multiple-ip-address-failover/select-and-add-ip-configurations.png" alt-text="Screenshot of Select and Add IP Configurations." lightbox="./media/concepts-multiple-ip-address-failover/select-and-add-ip-configurations.png":::
 
 Now, for each IP Configuration that you've added, you can configure the values for Private IP, Public IP, and Backend Pool for Failover and Test Failover separately. After you've done it all, don't forget to Save changes.
 
 
 ## Next steps
+
 - Learn more about [Traffic Manager with Azure Site Recovery](../site-recovery/concepts-traffic-manager-with-site-recovery.md)
 - Learn more about Traffic Manager [routing methods](../traffic-manager/traffic-manager-routing-methods.md).
 - Learn more about [recovery plans](site-recovery-create-recovery-plans.md) to automate application failover.