eee tasks

Author: Ankita Dutta

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
@@ -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

@@ -161,7 +161,7 @@ Once you have initiated the planned failover and it completes successfully, your
 ## Next steps
 
 - [Failover VMware VMs to Azure (modernized)](vmware-azure-tutorial-failover-failback-modernized.md)
-- [Planned failover (modernized)](vmware-azure-tutorial-failover-failback-modernized#planned-failover-from-azure-to-on-premises.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/hyper-v-azure-troubleshoot.md

@@ -1,11 +1,10 @@
 ---
 title: Troubleshoot Hyper-V disaster recovery with Azure Site Recovery 
-description: Describes how to troubleshoot disaster recovery issues with Hyper-V to Azure replication using Azure Site Recovery
-services: site-recovery
+description: Describes how to troubleshoot disaster recovery issues with Hyper-V to Azure replication using Azure Site Recovery.
 author: ankitaduttaMSFT
 ms.service: azure-site-recovery
 ms.topic: troubleshooting
-ms.date: 03/02/2023
+ms.date: 12/20/2024
 ms.author: ankitadutta
 ms.custom: engagement-fy23
 
@@ -14,7 +13,7 @@ ms.custom: engagement-fy23
 
 This article describes common issues that you might come across when replicating on-premises Hyper-V VMs to Azure, using [Azure Site Recovery](site-recovery-overview.md).
 
-## Enable protection issues
+## Enable protection issues 
 
 If you experience issues when you enable protection for Hyper-V VMs, check the following recommendations:
 
@@ -23,7 +22,7 @@ If you experience issues when you enable protection for Hyper-V VMs, check the f
 3. Check that the Hyper-V Virtual Machine Management service is running on Hyper-V hosts.
 4. Check for issues that appear in the Hyper-V-VMMS\Admin sign in to the VM. This log is located in **Applications and Services Logs** > **Microsoft** > **Windows**.
 5. On the guest VM, verify that WMI is enabled and accessible.
-   - [Learn about](https://techcommunity.microsoft.com/t5/ask-the-performance-team/bg-p/AskPerf) basic WMI testing.
+   - [Learn about](https://techcommunity.microsoft.com/blog/askperf/basic-wmi-testing/372423) basic WMI testing.
    - [Troubleshoot](/windows/win32/wmisdk/wmi-troubleshooting) WMI.
    - [Troubleshoot](/previous-versions/tn-archive/ff406382(v=msdn.10)#H22) problems with WMI scripts and services.
 6. On the guest VM, ensure that the latest version of Integration Services is running.
@@ -48,7 +47,7 @@ When trying to enable replication, you may face an error informing that enable r
 
 Troubleshoot issues with initial and ongoing replication as follows:
 
-1. Make sure you're running the [latest version](https://social.technet.microsoft.com/wiki/contents/articles/38544.azure-site-recovery-service-updates.aspx) of Site Recovery services.
+1. Make sure you're running the [latest version](./site-recovery-whats-new.md) of Site Recovery services.
 2. Verify whether replication is paused:
    - Check the VM health status in the Hyper-V Manager console.
    - If it's critical, right-click the VM > **Replication** > **View Replication Health**.
@@ -75,7 +74,7 @@ Network bandwidth limitations can affect replication. Troubleshoot issues as fol
 3. After running the profiler, follow the [bandwidth](hyper-v-deployment-planner-analyze-report.md#recommendations-with-available-bandwidth-as-input) and [storage](hyper-v-deployment-planner-analyze-report.md#vm-storage-placement-recommendation) recommendations.
 4. Check [data churn limitations](hyper-v-deployment-planner-analyze-report.md#azure-site-recovery-limits). If you see high data churn on a VM, do the following:
    - Check if your VM is marked for resynchronization.
-   - Follow [these steps](https://techcommunity.microsoft.com/t5/virtualization/bg-p/Virtualization) to investigate the source of the churn.
+   - Follow [these steps](./monitoring-high-churn.md) to investigate the source of the churn.
    - Churn can occur when the HRL log files exceed 50% of the available disk space. If this is the issue, provision more storage space for all VMs on which the issue occurs.
    - Check that replication isn't paused. If it is, it continues writing the changes to the hrl file, which can contribute to its increased size.
 
@@ -178,4 +177,4 @@ All Hyper-V replication events are logged in the Hyper-V-VMMS\Admin log, located
 This tool can help with advanced troubleshooting:
 
 -	For VMM, perform Site Recovery log collection using the [Support Diagnostics Platform (SDP) tool](https://social.technet.microsoft.com/wiki/contents/articles/28198.asr-data-collection-and-analysis-using-the-vmm-support-diagnostics-platform-sdp-tool.aspx).
--	For Hyper-V without VMM, [download this tool](https://answers.microsoft.com/en-us/windows/forum/all/unable-to-open-diagcab-files/e7f8e4e5-b442-4e53-af7a-90e74985a73f), and run it on the Hyper-V host to collect the logs.
+- [Enable logging](https://learn.microsoft.com/troubleshoot/azure/site-recovery/backup/asr-enable-debug-logging) for the Azure Site Recovery in Hyper-V Site Protection. 

articles/site-recovery/toc.yml

@@ -185,8 +185,6 @@
     items:
     - name: Hyper-V to Azure architecture
       href: hyper-v-azure-architecture.md
-    - name: About excluding disks from replication
-      href: exclude-disks-replication.md
   - name: About Backup center
     items:
     - name: Backup center overview
@@ -233,6 +231,8 @@
     href: site-recovery-role-based-linked-access-control.md
 - name: How-to Guides
   items:
+  - name: Exclude disks from replication
+    href: exclude-disks-replication.md
   - name: Azure to Azure disaster recovery
     items:
     - name: Set up networking