Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article answers common questions about using shared disks (Azure to Azure) with Azure Site Recovery.
No, Azure Site Recovery does not support Linux VMs with shared disks. Only VMs with WSFC-based shared disks are supported.
Yes, it is supported.
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.
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.
No, Azure Site Recovery for Shared Disks supports only Crash consistent recovery points.
No, recovery plans are not supported for shared disks in Azure Site Recovery.
Learn more about: