Classic to mod

Author: Ankita Dutta

articles/site-recovery/classic-to-modernized-common-questions.md

@@ -44,17 +44,17 @@ The modernized Recovery Services vault should be located in the same region and
 
 ### Will my replication continue while the migration is happening?
 
-No, the replication will break for some time while the migration is in progress. During this time, the last created recovery point, in the classic Recovery Services vault, will be available for you to failover to. Once the migration is complete, a new recovery point is generated in the modernized Recovery Services vault.  
+No, the replication breaks for some time while the migration is in progress. During this time, the last created recovery point, in the classic Recovery Services vault, is available for you to failover to. Once the migration is complete, a new recovery point is generated in the modernized Recovery Services vault.  
 
 ### When will my migration operation be marked as complete?
 
-Migration operation will only be marked complete once the first recovery point has been successfully created in the modernized Recovery Services vault.  
+Migration operation is only be marked complete once the first recovery point has been successfully created in the modernized Recovery Services vault.  
 
 ### What operations can be performed from my classic Recovery Services vault, after migration is done?  
 
-You can perform failover from your classic vault after the migration. The failover operation will continue to be available in the classic vault until the recovery points expire.
+You can perform failover from your classic vault after the migration. The failover operation continues to be available in the classic vault until the recovery points expire.
 
-For example, if the retention period for a replicated item is 72 hours (three days), the latest recovery point on the classic vault will continue to be available for 72 hours (three days), after a successful migration. After the stipulated time, Azure Site Recovery will automatically trigger a purge replication operation on the replicated item and perform the cleanup of all associated storage and billing-causing items.   
+For example, if the retention period for a replicated item is 72 hours (three days), the latest recovery point on the classic vault continues to be available for 72 hours (three days), after a successful migration. After the stipulated time, Azure Site Recovery automatically triggers a purge replication operation on the replicated item and perform the cleanup of all associated storage and billing-causing items.   
 
 ### What if a disaster strikes my machine while the migration operation is in progress?
 
@@ -73,9 +73,9 @@ No, the same resources, which were being used previously will be defaulted to in
 
 ### How will my replication policies be moved to the modernized vault?
 
-As a prerequisite, Site Recovery will create replication policies in the modernized vault with the same configuration as in the classic vault. So, before a replicated item is moved, the associated policy is created in the modernized vault. We recommend that you avoid making changes to the configuration of replication policies in the classic vault after the migration has been triggered, as these changes won't be reflected in the modernized vault. It's best to make these changes before starting the migration process.
+As a prerequisite, Site Recovery creates replication policies in the modernized vault with the same configuration as in the classic vault. So, before a replicated item is moved, the associated policy is created in the modernized vault. We recommend that you avoid making changes to the configuration of replication policies in the classic vault after the migration has been triggered, as these changes won't be reflected in the modernized vault. It's best to make these changes before starting the migration process.
 
-The replication policy created in the modernized vault will have its name changed in the modernized vault. It is prefixed with resource group name and vault name of the modernized Recovery Services vault. So, if the policy name was “default replication policy” in the classic vault, then in the modernized vault, this policy’s name is `default replication policy contoso-modern-vault_contoso-rg`, given the vault’s name is contoso-modern-vault and the vault’s resource group is contoso-rg.  
+The replication policy created in the modernized vault has its name changed in the modernized vault. It is prefixed with resource group name and vault name of the modernized Recovery Services vault. So, if the policy name was `default replication policy` in the classic vault, then in the modernized vault, this policy’s name is `default replication policy contoso-modern-vault_contoso-rg`, given the vault’s name is contoso-modern-vault and the vault’s resource group is contoso-rg.  
 
 ### Can I edit my replication policy during migration or post migration in the classic vault?
 
@@ -90,7 +90,7 @@ All replicated items that are part of a replication group are migrated together.
 ### Can I migrate my classic setup with public endpoint to modernized setup with private endpoint?
 
 No, you can only move classic disaster recovery setup with public endpoint to modernized public endpoint setup. 
-Note that, non-private endpoint to private endpoint migration is not supported, but private endpoint to private endpoint migration is supported.
+Note that, nonprivate endpoint to private endpoint migration is not supported, but private endpoint to private endpoint migration is supported.
 
 
 ## Next steps

articles/site-recovery/shared-disks-common-questions.md

@@ -0,0 +1,46 @@
+---
+title: Common questions about Shared disks in Azure Site Recovery (preview)
+description: This article answers common questions about Azure to Azure Shared disks in Azure Site Recovery.
+ms.author: ankitadutta
+author: ankitaduttaMSFT
+ms.topic: faq
+ms.date: 03/26/2025
+ms.service: azure-site-recovery
+
+---
+# Common questions: Shared Disks
+
+
+#### Does Azure Site Recovery support Linux VMs with shared disks?
+No, Azure Site Recovery does not support Linux VMs with shared disks. Only VMs with WSFC-based shared disks are supported.
+
+#### Is PowerShell supported for Azure Site Recovery with shared disks?
+No, PowerShell support for shared disks is currently unavailable.
+
+#### Can we enable replication for only some of the VMs attached to a shared disk?
+No, enable replication can only be enabled successfully when all the VMs attached to a shared disk are selected.
+
+#### Is it possible to exclude shared disks and enable replication for only some of the VMs in a cluster?
+Yes, the first time you don’t select all the VMs in Enable Replication, a warning appears mentioning the unselected VMs attached to the shared disk. If you still proceed, unselect the shared disk replication by selecting ‘No’ for the storage option in Replication Settings tab.
+ 
+####  If the *enable replication* job fails for a cluster, can we restart it after fixing the issue without reselecting clusters again?
+Yes, you can restart the job without reselecting clusters, just like other A2A scenarios. However, since the *enable replication* process runs for each node, you need to restart the failed job for all nodes through the Site Recovery Jobs interface.
+
+#### Can new shared disks be added to a protected cluster?
+No, if new shared disks need to be added, disable the replication for the already protected cluster. Enable a new cluster protection with a new cluster name for the modified infrastructure.
+
+#### Can we select both crash-consistent and app-consistent recovery points?
+Yes, both types of recovery points are generated. However, during Public Preview only crash-consistent and the Latest Processed recovery points are supported. App-consistent recovery points and Latest recovery point will be available as part of General Availability.
+
+#### Can we use recovery plans to failover Azure Site Recovery enabled VMs with shared disks?
+No, recovery plans are not supported for shared disks in Azure Site Recovery.
+
+#### Why is there no health status for VMs with shared disks in the monitoring plane, whether test failover is completed or not?
+The health status warning due to test failover will be available as part of General Availability.
+
+## Next steps
+
+Learn more about:
+
+-  [Azure managed disk](/azure/virtual-machines/disks-shared).
+-  [Support matrix for shared disk in Azure Site Recovery](./shared-disk-support-matrix.md).

articles/site-recovery/tutorial-shared-disk.md

@@ -3,7 +3,7 @@ title: Shared disks in Azure Site Recovery (preview)
 description: This article describes how to enable replication, failover, and failback Azure virtual machines for shared disks.
 ms.topic: conceptual
 ms.service: azure-site-recovery
-ms.date: 05/08/2024
+ms.date: 03/26/2025
 ms.author: ankitadutta
 author: ankitaduttaMSFT
 ---
@@ -218,35 +218,6 @@ To disable replication of your cluster with Azure Site Recovery, follow these st
     :::image type="content" source="media/tutorial-shared-disk/disable-replication.png" alt-text="Screenshot showing disable replication.":::
 
 
-## Commonly asked questions
-
-#### Does Azure Site Recovery support Linux VMs with shared disks?
-No, Azure Site Recovery does not support Linux VMs with shared disks. Only VMs with WSFC-based shared disks are supported.
-
-#### Is PowerShell supported for Azure Site Recovery with shared disks?
-No, PowerShell support for shared disks is currently unavailable.
-
-#### Can we enable replication for only some of the VMs attached to a shared disk?
-No, enable replication can only be enabled successfully when all the VMs attached to a shared disk are selected.
-
-#### Is it possible to exclude shared disks and enable replication for only some of the VMs in a cluster?
-Yes, the first time you don’t select all the VMs in Enable Replication, a warning appears mentioning the unselected VMs attached to the shared disk. If you still proceed, unselect the shared disk replication by selecting ‘No’ for the storage option in Replication Settings tab.
- 
-####  If the *enable replication* job fails for a cluster, can we restart it after fixing the issue without reselecting clusters again?
-Yes, you can restart the job without reselecting clusters, just like other A2A scenarios. However, since the *enable replication* process runs for each node, you need to restart the failed job for all nodes through the Site Recovery Jobs interface.
-
-#### Can new shared disks be added to a protected cluster?
-No, if new shared disks need to be added, disable the replication for the already protected cluster. Enable a new cluster protection with a new cluster name for the modified infrastructure.
-
-#### Can we select both crash-consistent and app-consistent recovery points?
-Yes, both types of recovery points are generated. However, during Public Preview only crash-consistent and the Latest Processed recovery points are supported. App-consistent recovery points and Latest recovery point will be available as part of General Availability.
-
-#### Can we use recovery plans to failover Azure Site Recovery enabled VMs with shared disks?
-No, recovery plans are not supported for shared disks in Azure Site Recovery.
-
-#### Why is there no health status for VMs with shared disks in the monitoring plane, whether test failover is completed or not?
-The health status warning due to test failover will be available as part of General Availability.
-
 
 ## Next steps
 

articles/site-recovery/vmware-physical-azure-classic-deprecation.md

@@ -3,7 +3,7 @@ title: Deprecation of classic experience to protect VMware and physical machines
 description: Details about upcoming deprecation of classic experience to protect VMware and physical machines to Azure and alternate options
 ms.service: azure-site-recovery
 ms.topic: overview
-ms.date: 03/14/2023
+ms.date: 03/26/2025
 ms.author: ankitadutta
 
 ---
@@ -38,7 +38,7 @@ The [modernized experience](vmware-azure-architecture-modernized.md) is an alter
 
 Follow these steps to move your existing replications to the modernized experience:
 
-1. [Check the required infrastructure for your setup](move-from-classic-to-modernized-vmware-disaster-recovery.md#how-to-define-required-infrastructure) and the [FAQs](move-from-classic-to-modernized-vmware-disaster-recovery.md#faqs) for all related information.
+1. [Check the required infrastructure for your setup](move-from-classic-to-modernized-vmware-disaster-recovery.md#how-to-define-required-infrastructure) and the [FAQs](./classic-to-modernized-common-questions.md) for all related information.
 2. [Check the architecture and minimum version of all components](move-from-classic-to-modernized-vmware-disaster-recovery.md#architecture) required for this migration.
 3. Check all the [resources required](move-from-classic-to-modernized-vmware-disaster-recovery.md#required-infrastructure) and deploy the [Azure Site Recovery replication appliance](deploy-vmware-azure-replication-appliance-modernized.md).  
 4. [Prepare the classic Recovery Services vault](move-from-classic-to-modernized-vmware-disaster-recovery.md#prepare-classic-recovery-services-vault) used by your existing replications.
@@ -47,6 +47,6 @@ Follow these steps to move your existing replications to the modernized experien
 
 ## Next steps
 
-Plan ahead for the deprecation and move to the modernized experience to take advantage of its [benefits](move-from-classic-to-modernized-vmware-disaster-recovery.md#why-should-i-migrate-my-machines-to-the-modernized-architecture) and stay up-to-date. 
+Plan ahead for the deprecation and move to the modernized experience to take advantage of its [benefits](./classic-to-modernized-common-questions.md#why-should-i-migrate-my-machines-to-the-modernized-architecture) and stay up-to-date. 
 
 In case you have any queries regarding this deprecation, reach out to Microsoft Support.