Merge pull request #292197 from ankitaduttaMSFT/eee

1912 EEE tasks

Author: v-ccolin

articles/site-recovery/exclude-disks-replication.md

@@ -2,7 +2,7 @@
 title: Exclude disks from replication with Azure Site Recovery
 description: How to exclude disks from replication to Azure with Azure Site Recovery.
 ms.topic: how-to
-ms.date: 09/18/2024
+ms.date: 12/20/2024
 ms.service: azure-site-recovery
 ms.author: ankitadutta
 author: ankitaduttaMSFT
@@ -31,9 +31,9 @@ Yes | Yes | Yes | Yes (only in classic architecture)
 --- | --- | ---
 **Disk types** | You can exclude basic disks from replication.<br/><br/> You can't exclude operating system disks or dynamic disks. Temp disks are excluded by default. | You can exclude basic disks from replication.<br/><br/> You can't exclude operating system disks or dynamic disks. | You can exclude basic disks from replication.<br/><br/> You can't exclude operating system disks. We recommend that you don't exclude dynamic disks. Site Recovery can't identify which VHS is basic or dynamic in the guest VM. If all dependent dynamic volume disks aren't excluded, the protected dynamic disk becomes a failed disk on a failover VM, and the data on that disk isn't accessible.
 **Replicating disk** | You can't exclude a disk that's replicating.<br/><br/> Disable and reenable replication for the VM. |  You can't exclude a disk that's replicating. |  You can't exclude a disk that's replicating.
-**Mobility service (VMware)** | Not relevant | You can exclude disks only on VMs that have the Mobility service installed.<br/><br/> This means that you have to manually install the Mobility service on the VMs for which you want to exclude disks.You can't use the push installation mechanism because it installs the Mobility service only after replication is enabled. | Not relevant.
+**Mobility service (VMware)** | Not relevant | You can exclude disks only on VMs that have the Mobility service installed.<br/><br/> This means that you have to manually install the Mobility service on the VMs for which you want to exclude disks. You can't use the push installation mechanism because it installs the Mobility service only after replication is enabled. | Not relevant.
 **Add/Remove** | You can add managed disks on replication-enabled Azure VMs with managed disks. You cannot remove disks on replication-enabled Azure VMs. | You can't add or remove disks after replication is enabled. Disable and then reenable replication to add a disk. | You can't add or remove disks after replication is enabled. Disable and then reenable replication.
-**Failover** | If an app needs a disk that you excluded, after failover you need to create the disk manually so that the replicated app can run.<br/><br/> Alternatively, you can create the disk during VM failover, by integrating Azure automation into a recovery plan. | If you exclude a disk that an app needs, create it manually in Azure after failover. | If you exclude a disk that an app needs, create it manually in Azure after failover.
+**Failover** | If an app needs a disk that you excluded, after failover you need to create the disk manually so that the replicated app can run.<br/><br/> Alternatively, you can create the disk during VM failover, by integrating Azure Automation into a recovery plan. | If you exclude a disk that an app needs, create it manually in Azure after failover. | If you exclude a disk that an app needs, create it manually in Azure after failover.
 **On-premises failback-disks created manually** | Not relevant | **Windows VMs**: Disks created manually in Azure aren't failed back. For example, if you fail over three disks and create two disks directly on an Azure VM, only the three disks that were failed over are then failed back.<br/><br/> **Linux VMs**: Disks created manually in Azure are failed back. For example, if you fail over three disks and create two disks on an Azure VM, all five will be failed back. You can't exclude disks that were created manually from failback. | Disks created manually in Azure aren't failed back. For example, if you fail over three disks and create two disks directly on an Azure VM, only three disks that were failed over will be failed back.
 **On-premises failback-Excluded disks** | Not relevant | If you fail back to the original machine, the failback VM disk configuration doesn't include the excluded disks. Disks that were excluded from VMware to Azure replication aren't available on the failback VM. | When failback is to the original Hyper-V location, the failback VM disk configuration remains the same as that of original source VM disk. Disks that were excluded from Hyper-V site to Azure replication are available on the failback VM.
 
@@ -265,4 +265,4 @@ Our paging file settings on the Azure VM are as follows:
 - Learn more about guidelines for the temporary storage disk:
     - [Learn about](https://cloudblogs.microsoft.com/sqlserver/2014/09/25/using-ssds-in-azure-vms-to-store-sql-server-tempdb-and-buffer-pool-extensions/) using SSDs in Azure VMs to store SQL Server TempDB and Buffer Pool Extensions
     - [Review ](/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-checklist) performance best practices for SQL Server in Azure VMs.
-- After your deployment is set up and running, [learn more](failover-failback-overview.md) about different types of failover.
+- After your deployment is set up and running, [learn more](failover-failback-overview-modernized.md) about different types of failover.

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

@@ -2,7 +2,7 @@
 title: About failover and failback in Azure Site Recovery - Modernized
 description: Learn about failover and failback in Azure Site Recovery - Modernized.
 ms.topic: overview
-ms.date: 02/13/2024
+ms.date: 12/19/2024
 ms.author: ankitadutta
 ms.service: azure-site-recovery
 author: ankitaduttaMSFT
@@ -11,7 +11,7 @@ author: ankitaduttaMSFT
 
 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) - Modernized.
 
-For information about failover and failback in Azure Site Recovery Classic releases, [see this article](failover-failback-overview.md).
+For information about failover and failback in Azure Site Recovery Classic releases, [see this article](vmware-azure-architecture.md#failover-and-failback-process).
 
 ## Recovery stages
 
@@ -160,16 +160,9 @@ Once you have initiated the planned failover and it completes successfully, your
 
 ## Next steps
 
-> [!div class="nextstepaction"]
-> [Failover VMware VMs to Azure (modernized)](vmware-azure-tutorial-failover-failback-modernized.md#run-a-failover-to-azure)
-
-> [!div class="nextstepaction"]
-> [Planned failover (modernized)](vmware-azure-tutorial-failover-failback-modernized.md#planned-failover-from-azure-to-on-premises)
-
-> [!div class="nextstepaction"]
-> [Reprotect (modernized)](vmware-azure-tutorial-failover-failback-modernized.md#re-protect-the-on-premises-machine-to-azure-after-successful-planned-failover)
-
-> [!div class="nextstepaction"]
-> [Cancel failover (modernized)](vmware-azure-tutorial-failover-failback-modernized.md#cancel-planned-failover)
+- [Failover VMware VMs to Azure (modernized)](vmware-azure-tutorial-failover-failback-modernized.md)
+- [Planned failover (modernized)](vmware-azure-tutorial-failover-failback-modernized.md#planned-failover-from-azure-to-on-premises)
+- [Reprotect (modernized)](vmware-azure-tutorial-failover-failback-modernized.md#re-protect-the-on-premises-machine-to-azure-after-successful-planned-failover)
+- [Cancel failover (modernized)](vmware-azure-tutorial-failover-failback-modernized.md#cancel-planned-failover)
 
 

articles/site-recovery/hybrid-how-to-enable-replication-private-endpoints.md

@@ -5,7 +5,7 @@ author: ankitaduttaMSFT
 ms.author: ankitadutta
 ms.service: azure-site-recovery
 ms.topic: how-to
-ms.date: 04/08/2024
+ms.date: 12/19/2024
 ms.custom: subject-rbac-steps, engagement-fy23
 ---
 # Replicate on-premises machines by using private endpoints

articles/site-recovery/hyper-v-azure-failback.md

@@ -1,12 +1,10 @@
 ---
 title: Fail back Hyper-V VMs from Azure with Azure Site Recovery 
 description: How to fail back Hyper-V VMs to an on-premises site from Azure with Azure Site Recovery.
-services: site-recovery
 author: ankitaduttaMSFT
-manager: gaggupta
 ms.service: azure-site-recovery
 ms.topic: tutorial
-ms.date: 12/14/2023
+ms.date: 12/19/2024
 ms.author: ankitadutta
 ms.custom: engagement-fy23
 
@@ -22,7 +20,7 @@ This article describes how to fail back Azure VMs that were created after failov
 
 ## Before you start
 
-1. [Review the types of failback](failover-failback-overview.md#hyper-v-reprotectionfailback) you can use - original location recovery and alternate location recovery.
+1. [Review the types of failback](concepts-types-of-failback.md) you can use - original location recovery and alternate location recovery.
 2. Ensure that the Azure VMs are using managed disks. Failback of Hyper-V virtual machines, that failed over to Azure machines using managed disks, is supported. It is not recommended to use storage accounts, as they will be [fully retired on September 30, 2025](/azure/virtual-machines/unmanaged-disks-deprecation).
 3. Check that the on-premises Hyper-V host (or System Center VMM server if you're using with Site Recovery) is running and connected to Azure. 
 4. Make sure that failover and commit are complete for the VMs. You don't need to set up any specific Site Recovery components for failback of Hyper-V VMs from Azure.
@@ -35,7 +33,7 @@ This article describes how to fail back Azure VMs that were created after failov
 
 To fail back Hyper-V VMs in Azure to the original on-premises VM, run a planned failover from Azure to the on-premises site as follows:
 
-1. In the vault > **Replicated items**, select the VM. Right-click the VM > **Planned Failover**. If you're failing back a recovery plan, select the plan name and click **Failover** > **Planned Failover**.
+1. In the vault > **Replicated items**, select the VM. Right-click the VM > **Planned Failover**. If you're failing back a recovery plan, select the plan name and select **Failover** > **Planned Failover**.
 2. In **Confirm Planned Failover**, choose the source and target locations. Note the failover direction. If the failover from primary worked as expected and all virtual machines are in the secondary location this is for information only.
 3. In **Data Synchronization**, select an option:
 	- **Synchronize data before failover (synchronize delta changes only)**—This option minimizes downtime for VMs as it synchronizes without shutting them down.
@@ -47,13 +45,13 @@ To fail back Hyper-V VMs in Azure to the original on-premises VM, run a planned
 
 4. For VMM only, if data encryption is enabled for the cloud, in **Encryption Key**, select the certificate that was issued when you enabled data encryption during Provider installation on the VMM server.
 5. Initiate the failover. You can follow the failover progress on the **Jobs** tab.
-6. If you selected the option to synchronize the data before the failover, after the initial data synchronization is complete and you're ready to shut down the virtual machines in Azure, click **Jobs** > job name > **Complete Failover**. This does the following:
+6. If you selected the option to synchronize the data before the failover, after the initial data synchronization is complete and you're ready to shut down the virtual machines in Azure, select **Jobs** > job name > **Complete Failover**. This does the following:
     - Shuts down the Azure machine.
 	- Transfers the latest changes to the on-premises VM.
 	- Starts the on-premises VM.
 7. You can now sign into the on-premises VM machine to check that it's available as expected.
-8. The virtual machine is in a commit pending state. Click **Commit** to commit the failover.
-9. To complete the failback, click **Reverse Replicate** to start replicating the on-premises VM to Azure again.
+8. The virtual machine is in a commit pending state. Select **Commit** to commit the failover.
+9. To complete the failback, select **Reverse Replicate** to start replicating the on-premises VM to Azure again. You can [failback to original location](hyper-v-azure-failback.md#fail-back-to-the-original-location).
 
 
 
@@ -70,11 +68,11 @@ Fail back to an alternate location as follows:
 	- **Phase 1**: Takes snapshot of the Azure VM and copies it to the on-premises Hyper-V host. The machine continues running in Azure.
 	- **Phase 2**: Shuts down the Azure VM so that no new changes occur there. The final set of changes is transferred to the on-premises server and the on-premises virtual machine is started up.
 
-7. Click the checkmark to begin the failover (failback).
-8. After the initial synchronization finishes and you're ready to shut down the Azure VM, click **Jobs** > \<planned failover job> > **Complete Failover**. This shuts down the Azure machine, transfers the latest changes to the on-premises VM, and starts it.
+7. Select the checkmark to begin the failover (failback).
+8. After the initial synchronization finishes and you're ready to shut down the Azure VM, select **Jobs** > \<planned failover job> > **Complete Failover**. This shuts down the Azure machine, transfers the latest changes to the on-premises VM, and starts it.
 9. You can sign into the on-premises VM to verify that everything is working as expected.
-10. Click **Commit** to finish the failover. Commit deletes the Azure VM and its disks, and prepares the on-premises VM to be protected again.
-10. Click **Reverse Replicate** to start replicating the on-premises VM to Azure. Only the delta changes since the VM was turned off in Azure will be replicated.
+10. Select **Commit** to finish the failover. Commit deletes the Azure VM and its disks, and prepares the on-premises VM to be protected again.
+11. Select **Reverse Replicate** to start replicating the on-premises VM to Azure. Only the delta changes since the VM was turned off in Azure will be replicated. You can now [fail back to the alternate location](hyper-v-azure-failback.md#fail-back-to-an-alternate-location).
 
     > [!NOTE]
     > - If you cancel the failback job during data synchronization, the on-premises VM will be in a corrupted state. This is because data synchronization copies the latest data from Azure VM disks to the on-premises data disks, and until the synchronization completes, the disk data may not be in a consistent state. If the on-premises VM starts after data synchronization is canceled, it might not boot. In this case, rerun the failover to complete data synchronization.

articles/site-recovery/hyper-v-azure-support-matrix.md

@@ -3,7 +3,7 @@ title: Support for disaster recovery of Hyper-V VMs to Azure with Azure Site Rec
 description: Summarizes the supported components and requirements for Hyper-V VM disaster recovery to Azure with Azure Site Recovery
 ms.service: azure-site-recovery
 ms.topic: concept-article
-ms.date: 12/20/2024
+ms.date: 12/19/2024
 author: ankitaduttaMSFT
 ms.author: ankitadutta
 ---
@@ -20,7 +20,7 @@ This article summarizes the supported components and settings for disaster recov
 
 **Scenario** | **Details**
 --- | ---
-Hyper-V with Virtual Machine Manager <br> <br>| You can perform disaster recovery to Azure for VMs running on Hyper-V hosts that are managed in the System Center Virtual Machine Manager fabric.<br/><br/> You can deploy this scenario in the Azure portal or by using PowerShell.<br/><br/> When Hyper-V hosts are managed by Virtual Machine Manager, you also can perform disaster recovery to a secondary on-premises site. To learn more about this scenario, read [this tutorial](hyper-v-vmm-disaster-recovery.md).
+Hyper-V with Virtual Machine Manager <br> <br>| You can perform disaster recovery to Azure for VMs running on Hyper-V hosts that are managed in the System Center Virtual Machine Manager fabric.<br/><br/> You can deploy this scenario in the Azure portal or by using PowerShell.<br/><br/> When Hyper-V hosts are managed by Virtual Machine Manager, you also can perform disaster recovery to a secondary on-premises site. To learn more about this scenario, read [this tutorial](hyper-v-vmm-azure-tutorial.md).
 Hyper-V without Virtual Machine Manager | You can perform disaster recovery to Azure for VMs running on Hyper-V hosts that aren't managed by Virtual Machine Manager.<br/><br/> You can deploy this scenario in the Azure portal or by using PowerShell.
 
 > [!NOTE]
@@ -44,7 +44,7 @@ The following table summarizes VM support. Site Recovery supports any workloads
  **Component** | **Details**
 --- | ---
 VM configuration | VMs that replicate to Azure must meet [Azure requirements](#azure-vm-requirements).
-Guest operating system | Any guest OS [supported for Azure](../cloud-services/cloud-services-guestos-update-matrix.md#family-5-releases)..<br/><br/> Windows Server 2016 Nano Server isn't supported.
+Guest operating system | Any guest OS [supported for Azure](https://learn.microsoft.com/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc794868%28v=ws.10%29#supported-guest-operating-systems). <br/><br/> Windows Server 2016 Nano Server isn't supported.
 
 
 ## VM/Disk management
@@ -200,4 +200,5 @@ Azure Site Recovery provider | Coordinates communications between on-premises se
 Microsoft Azure Recovery Services agent | Coordinates replication between Hyper-V VMs and Azure<br/><br/> Installed on on-premises Hyper-V servers (with or without Virtual Machine Manager) | Latest agent available from the portal
 
 ## Next steps
-Learn how to [prepare Azure](tutorial-prepare-azure.md) for disaster recovery of on-premises Hyper-V VMs.
+
+Learn how to [prepare Azure](tutorial-prepare-azure-for-hyperv.md) for disaster recovery of on-premises Hyper-V VMs.