Merge pull request #262897 from ankitaduttaMSFT/qlt-st

added note

Author: prmerger-automator[bot]

articles/site-recovery/failover-failback-overview.md

@@ -9,9 +9,12 @@ ms.service: site-recovery
 ---
 # About on-premises disaster recovery failover/failback - Classic
 
-This article provides an overview of failover and failback during disaster recovery of on-premises machines to Azure with [Azure Site Recovery](site-recovery-overview.md) - Classic.
+[Azure Site Recovery](site-recovery-overview.md) contributes to your business continuity and disaster recovery (BCDR) strategy by keeping your business apps up and running during planned and unplanned outages. Site Recovery manages and orchestrates disaster recovery of on-premises machines and Azure virtual machines (VMs). Disaster recovery includes replication, failover, and recovery of various workloads.
 
-For information about failover and failback in Azure Site Recovery Modernized release, [see this article](failover-failback-overview-modernized.md).
+> [!IMPORTANT]
+> This article provides an overview of failover and failback during disaster recovery of on-premises machines to Azure with [Azure Site Recovery](site-recovery-overview.md) - Classic.
+><br>
+> For information about failover and failback in Azure Site Recovery Modernized release, [see this article](failover-failback-overview-modernized.md).
 
 ## Recovery stages
 

articles/site-recovery/hyper-v-vmm-network-mapping.md

@@ -3,7 +3,7 @@ title: About Hyper-V (with VMM) network mapping with Site Recovery
 description: Describes how to set up network mapping for disaster recovery of Hyper-V VMs (managed in VMM clouds) to Azure, with Azure Site Recovery.
 ms.service: site-recovery
 ms.topic: conceptual
-ms.date: 11/14/2019
+ms.date: 01/10/2024
 ms.author: ankitadutta
 author: ankitaduttaMSFT
 ---
@@ -29,21 +29,6 @@ Network mapping works as follows:
 - If the target network has multiple subnets, and one of those subnets has the same name as subnet on which the source virtual machine is located, then the replica virtual machine connects to that target subnet after failover.
 - If there’s no target subnet with a matching name, the virtual machine connects to the first subnet in the network.
 
-## Prepare network mapping for replication to a secondary site
-
-When you're replicating to a secondary site, network mapping maps between VM networks on a source VMM server, and VM networks on a target VMM server. Mapping does the following:
-
-- **Network connection**—Connects VMs to appropriate networks after failover. The replica VM will be connected to the target network that's mapped to the source network.
-- **Optimal VM placement**—Optimally places the replica VMs on Hyper-V host servers. Replica VMs are placed on hosts that can access the mapped VM networks.
-- **No network mapping**—If you don’t configure network mapping, replica VMs won’t be connected to any VM networks after failover.
-
-Network mapping works as follows:
-
-- Network mapping can be configured between VM networks on two VMM servers, or on a single VMM server if two sites are managed by the same server.
-- When mapping is configured correctly and replication is enabled, a VM at the primary location will be connected to a network, and its replica at the target location will be connected to its mapped network.
-- When you select a target VM network during network mapping in Site Recovery, the VMM source clouds that use the source VM network will be displayed, along with the available target VM networks on the target clouds that are used for protection.
-- If the target network has multiple subnets and one of those subnets has the same name as the subnet on which the source virtual machine is located, then the replica VM will be connected to that target subnet after failover. If there’s no target subnet with a matching name, the VM will be connected to the first subnet in the network.
-
 ## Example
 
 Here’s an example to illustrate this mechanism. Let’s take an organization with two locations in New York and Chicago.

articles/site-recovery/site-recovery-backup-interoperability.md

@@ -5,12 +5,15 @@ author: ankitaduttaMSFT
 manager: rochakm
 ms.service: site-recovery
 ms.topic: conceptual
-ms.date: 12/15/2023
+ms.date: 01/10/2024
 ms.author: ankitadutta
 
 ---
 # Support for using Site Recovery with Azure Backup
 
+> [!NOTE]
+> Running MARS agent of both ASR and Backup on the same Hyper-V host is not be supported.
+
 This article summarizes support for using the [Site Recovery service](site-recovery-overview.md) together with the [Azure Backup service](../backup/backup-overview.md).
 
 **Action** | **Site Recovery support** | **Details**
@@ -20,4 +23,5 @@ This article summarizes support for using the [Site Recovery service](site-recov
 **Disk restore** | No current support | If you restore a backed up disk, you need to disable and re-enable replication for the VM again.
 **VM restore** | No current support | If you restore a VM or group of VMs, you need to disable and re-enable replication for the VM.  
 
-Please note that the above table is applicable across all supported Azure Site Recovery scenarios.
+> [!IMPORTANT]
+> The above table is applicable across all supported Azure Site Recovery scenarios.

articles/site-recovery/site-recovery-workload.md

@@ -3,7 +3,7 @@ title: About disaster recovery for on-premises apps with Azure Site Recovery
 description: Describes the workloads that can be protected using disaster recovery with the Azure Site Recovery service.
 ms.topic: conceptual
 ms.service: site-recovery
-ms.date: 03/18/2020
+ms.date: 01/10/2024
 ms.author: ankitadutta
 author: ankitaduttaMSFT
 ---