一項 Azure 原生災害復原服務。 先前稱為 Microsoft Azure Hyper-V 復原管理員。
Hello 周聖堂 CHOU SHENG TANG
Thank you for posting your query on Microsoft Q&A platform.
In your “Enable replication” job, the step “Installing Mobility Service and enabling replication” failed. That tells us the Mobility Service couldn’t be pushed/registered on the source VM, so replication never starts.
This happens due to below reasons:
- Ports do not open between the source VM and your ASR OVA appliance (configuration server/process server).
- Push‑install prerequisites missing (Windows needs WMI/SMB; Linux needs SSH/SFTP).
- The appliance can’t reach Azure on 443 (egress restricted).
- Account/privilege issues for the push‑install.
Try the below workarounds as per your source VM OS (Windows/Linux)
Do Network checks: Source VM → OVA appliance (process server)
- TCP 9443 inbound on the appliance must be reachable from the source VM. The Mobility Service sends replication data on this port.
If the test fails, open 9443/TCP on firewalls between the source VM and the appliance.Windows Test: Test-NetConnection <Appliance_IP> -Port 9443 Linux Test: nc -vz <Appliance_IP> 9443
Appliance → Azure:
- The OVA appliance needs TCP 443 outbound to Azure endpoints (ASR service, Storage, AAD). If you use egress filtering or a proxy, allow typical ASR URLs (e.g.
*.backup.windowsazure.com,*.blob.core.windows.net,*.hypervrecoverymanager.windowsazure.com) and auth endpoints. - Quick check from the appliance:
Test-NetConnection backup.windowsazure.com -Port 443
Appliance ↔ vCenter/ESXi: TCP 443 for discovery/orchestration. Keep this open between the appliance and vCenter/ESXi.
If you have any queries please feel free to reach out.
Thanks,
Suchitra.