Skip to content

Commit 65e6b4b

Browse files
committed
Resolved doc bugs
1 parent 9a55066 commit 65e6b4b

File tree

3 files changed

+6
-1
lines changed

3 files changed

+6
-1
lines changed

articles/site-recovery/hyper-v-deployment-planner-overview.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,8 @@ The tool provides the following details:
3232
* RPO that can be achieved for a given bandwidth
3333
* Impact on the desired RPO if lower bandwidth is provisioned.
3434

35+
> [!NOTE]
36+
> The recommended bandwidth in Deployment planner is applicable only for compatible Hyper-V VMs.
3537
3638
**Azure infrastructure requirements**
3739

articles/site-recovery/vmware-azure-reprotect.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -51,6 +51,9 @@ Enable replication. You can reprotect specific VMs, or a recovery plan:
5151
- If you want to fail back the Azure VM to an existing on-premises VM, mount the on-premises VM data stores with read/write access on the master target server's ESXi host.
5252
- If you want to fail back to an alternate location, for example if the on-premises VM doesn't exist, select the retention drive and data store that are configured for the master target server. When you fail back to the on-premises site, the VMware virtual machines in the failback protection plan use the same data store as the master target server. A new VM is then created in vCenter.
5353

54+
> [!NOTE]
55+
> It is strongly recommended that the mobility service agent is not uninstalled from the failed over machine (which is running in Azure). Performing re-protect or failback operations will not be possible post that.
56+
5457
Enable reprotection as follows:
5558

5659
1. Select **Vault** > **Replicated items**. Right-click the virtual machine that failed over, and then select **Re-protect**. Or, from the command buttons, select the machine, and then select **Re-protect**.

articles/site-recovery/vmware-physical-azure-support-matrix.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -323,7 +323,7 @@ Guest/server shared cluster disk | No
323323
Guest/server encrypted disk | No
324324
FIPS encryption | No
325325
Guest/server NFS | No
326-
Guest/server iSCSI | For Migration - Yes<br/>For Disaster Recovery - No, iSCSI will failback as an attached disk to the VM
326+
Guest/server iSCSI | For Migration - Yes but you must setup replication as a Physical machine.<br/>For Disaster Recovery - No, iSCSI will failback as an attached disk to the VM
327327
Guest/server SMB 3.0 | No
328328
Guest/server RDM | Yes<br/><br/> N/A for physical servers
329329
Guest/server disk > 1 GB | Yes, disk must be larger than 1024 MB<br/><br/>Up to 32,767 GB when replicating to managed disk (9.41 version onwards)<br></br> Up to 4,095 GB when replicating to storage accounts

0 commit comments

Comments
 (0)