Skip to content

Commit 970acbc

Browse files
Merge pull request #280457 from ankitaduttaMSFT/855
pbi 855
2 parents c07dcea + c4b2db0 commit 970acbc

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -232,6 +232,8 @@ No, enable replication can only be enabled successfully when all the VMs attache
232232
#### Is it possible to exclude shared disks and enable replication for only some of the VMs in a cluster?
233233
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.
234234

235+
#### If the *enable replication* job fails for a cluster, can we restart it after fixing the issue without reselecting clusters again?
236+
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.
235237

236238
#### Can new shared disks be added to a protected cluster?
237239
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.

0 commit comments

Comments
 (0)