是的，由于 VM 最初是在错误的复制方案（物理主机而不是 Azure VM）下注册的，因此需要使用正确的 Azure 到 Azure 工作流在恢复服务保管库中重新启用复制。无需“删除”保管库本身，但应禁用这些 VM 的不正确复制设置，然后正确重新注册它们。
我希望你觉得这条建议在某种程度上有用。感谢您 接受答案 ，将其作为与社区分享宝贵经验的一种方式。谢谢:)
维 维 安
在asr里 我无法为虚机启用复制
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(6.4, 50%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
刘寅
20
信誉分
在azure上的asr里，我无法为注册的虚机启用保护，报错信息为“The mobility agent on the machine 'web-app01' is not yet registered with Proxy server.” 但我在源主机上已经用命令“.\UnifiedAgentConfigurator.exe /SourceConfigFilePath ".\b808a635-a4b1-48a5-a8a6-f33003fc5dff_config.json" /CSType CSPrime”注册过了 请问如何处理？ 我的源主机是azure上的虚机，但我选择复制的架构是物理主机
Windows 商业版 | Windows Server | Windows 云 | 其他
问题作者接受的答案
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 16%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EV%3C/text%3E%3C/svg%3E)
VPHAN 45,825 信誉分 独立顾问2025-11-12T01:55:12.92+00:00 Your error occurs because the VM is being treated as a physical server in Azure Site Recovery (ASR), but the source host is actually an Azure VM. The mobility agent registration command you ran is valid for physical/VMware scenarios, not for Azure‑to‑Azure replication. To fix this, you need to configure replication using the Azure‑to‑Azure method instead of the physical host workflow. To be specific:
- Confirm your scenario
- If your source VM is in Azure and you want to replicate it to another Azure region, you must use Azure‑to‑Azure replication.
- If your source VM is truly on‑premises, then the physical/VMware workflow is correct.
- For Azure‑to‑Azure replication
- Go to the Recovery Services Vault in the Azure portal.
- Select Replicate → Source: Azure VM.
- Choose the VM (
web-app01) from your subscription. - ASR will automatically install and register the mobility agent on the VM. No manual
UnifiedAgentConfigurator.exestep is needed.
- If you intended physical/VMware replication
- Ensure the configuration server is deployed and reachable.
- Verify that the mobility agent service is running on the source machine.
- Check outbound connectivity to ASR endpoints (proxy/firewall may block registration).
- Re‑run the configurator with correct parameters and confirm the agent shows as “Healthy” in the ASR portal.
I hope you find this piece of advice useful to some extent. It's appreciated of you to accept the answer as a way to share your valuable experience with the community. Thank you :)
Vivian
- Confirm your scenario