Skip to content

Commit 875b07f

Browse files
authored
Merge pull request #125970 from JozeMarkic/patch-1
Update hyper-v-deployment-planner-overview.md
2 parents 92f8a34 + 8aaa1e8 commit 875b07f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -104,7 +104,7 @@ The tool has three main phases for Hyper-V: get VM list, profiling, and report g
104104
105105
## Download and extract the deployment planner tool
106106
107-
1. Download the latest version of the [Azure Site Recovery deployment planner](https://aka.ms/asr-deployment-planner).
107+
1. Download the latest version of the [Azure Site Recovery deployment planner](https://download.microsoft.com/download/7491a137-315d-40ca-9307-f74f913f7e6a/ASRDeploymentPlanner-v3.2.zip).
108108
The tool is packaged in a .zip folder. The same tool supports both VMware to Azure and Hyper-V to Azure disaster recovery scenarios. You can use this tool for Hyper-V-to secondary site disaster recovery scenario as well but ignore the Azure infrastructure recommendation from the report.
109109
110110
1. Copy the .zip folder to the Windows Server on which you want to run the tool. You can run the tool on a Windows Server 2012 R2 or Windows Server 2016. The server must have network access to connect to the Hyper-V cluster or Hyper-V host that holds the VMs to be profiled. We recommend that you have the same hardware configuration of the VM, where the tool is going to run, as that of the Hyper-V server, which you want to protect. Such a configuration ensures that the achieved throughput that the tool reports matches the actual throughput that Azure Site Recovery can achieve during replication. The throughput calculation depends on available network bandwidth on the server and hardware configuration (CPU, storage, and so forth) of the server. The throughput is calculated from the server where the tool is running to Azure. If the hardware configuration of the server differs from the Hyper-V server, the achieved throughput that the tool reports will be inaccurate.

0 commit comments

Comments
 (0)