Skip to content

Commit 6c5c301

Browse files
Merge pull request #262109 from Sharmistha-Rai/main
vMotion not supported
2 parents f683339 + a8d6493 commit 6c5c301

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -113,7 +113,7 @@ To reprotect and fail back VMware machines and physical servers from Azure to on
113113
- Replication appliance doesn’t require additional network connection/ports (as compared with forward protection) during failback. Same appliance can be used for forward and backward protections if it is in healthy state. It should not impact the performance of the replications.
114114
- When selecting the appliance, ensure that the target datastore where the source machine is located, is accessible by the appliance. The datastore of the source machine should always be accessible by the appliance. Even if the machine and appliance are located in different ESX servers, as long as the data store is shared between them, reprotection succeeds.
115115
> [!NOTE]
116-
> - Storage vMotion of replication appliance is not supported after re-protect operation.
116+
> - Storage vMotion of replicated items is not supported. Storage vMotion of replication appliance is not supported after re-protect operation.
117117
> - When selecting the appliance, ensure that the target datastore where the source machine is located, is accessible by the appliance.
118118
119119

0 commit comments

Comments
 (0)