URGENT: Azure to Azure Mobility agent version update

Hello TwickyBrain

Thank you for posting your query on Microsoft Q&A platform.

Manually Updating the ASR Mobility Agent on RHEL 7.9 (Azure‑to‑Azure DR):

1. Version clarification — the link you cited is stale

The page you referenced (azure-to-azure-autoupdate) still shows 9.36.5696.1 because that section of the doc was written in the classic era, it is not the currently shipping build.

The latest GA rollup is Update Rollup 83, which is Mobility Agent 9.66.7691.1 and it is the version that adds NVMe support and other A2A fixes. Since you are already on 9.65.7440.1, you are only one rollup behind, so upgrading to 9.66 is fully supported (well within the N to N‑4 support window).

For the RHEL 7.9 kernel matrix, 9.66 continues to cover RHEL 7.9 as documented in the Support Matrix for Azure VM Disaster Recovery.

2. Where to get the correct A2A installer for RHEL 7 (private‑endpoint friendly):

For Azure‑to‑Azure, Microsoft publishes the direct package links in the official Azure Site Recovery GitHub repo (not the "on‑premise to Azure" table):

Repo: Azure/Azure-SiteRecovery

A2A download links (all distros, incl. RHEL7‑64): MobilityAgent/AzureToAzure/AgentDownloadLinks.md in the same repo the latest set was refreshed for 9.66.7851.1 two weeks ago.

The equivalent on‑prem list (for reference of the layout) is here: OnPremiseToAzure/AgentDownloadLinks.md but for your case you must use the AzureToAzure file.

Download the RHEL7‑64 .tar.gz from an admin workstation (or a jump host that has internet), then copy it to the protected RHEL 7.9 VM via SCP/Bastion/Azure Files this bypasses the private endpoint restriction that is blocking the in‑portal push upgrade.

3. Manual upgrade steps on the RHEL 7.9 VM

The commands below follow the Microsoft‑documented syntax for a Linux Upgrade operation. Run everything as root.

# 1. Stage the package
mkdir -p /tmp/asr && cd /tmp/asr
# (copy Microsoft-ASR_UA_9.66.*_RHEL7-64_GA_*_release.tar.gz here)
# 2. Extract
tar -xvzf Microsoft-ASR_UA_9.66.*_RHEL7-64_GA_*_release.tar.gz
# 3. Run installer in Upgrade mode for Azure (A2A)
./install -q -r MS -v Azure -a Upgrade

Key flags (per the modernized Linux command reference):

• -q → quiet/unattended
• -r MS → role Master/Source
• -v Azure → platform Azure (A2A). Note: for VMware/physical you would use VmWarefor A2A you must use Azure.
• -a Upgrade → upgrade an already‑installed agent (no re‑registration needed; existing config is preserved)

4. Verify the upgrade:

# Version file
cat /usr/local/.vx_version | grep -i version
# Services
systemctl status vxagent # svagents
systemctl status InMage_ScoutAgent 2>/dev/null || true
# Registration health
/usr/local/ASR/Vx/bin/UnifiedAgentConfigurator.sh -c CSPrime -q

Then in the Azure portal → Recovery Services vault → Replicated items → → Overview confirm the Agent version now shows 9.66.x and health is green before running the failover drill.

5. Private endpoint considerations (do this before the drill):

Because auto‑update is failing over the private endpoint, verify that the RHEL VM can also reach the following through the private link/PE path otherwise even a manual agent upgrade will show "healthy but not replicating" during the drill:

Cache storage account (*.blob.core.windows.net) : private DNS zone privatelink.blob.core.windows.net must resolve to the PE IP.

Site Recovery service endpoints (*.hypervrecoverymanager.windowsazure.com, *.backup.windowsazure.com) via the ASR private endpoint on the vault.

Microsoft Entra ID (login.microsoftonline.com) and management.azure.com (these do NOT go through PE, ensure the NSG/UDR/firewall still permits them, otherwise use service tags AzureActiveDirectory and AzureResourceManager).

If DNS on the VM still resolves the cache storage account to a public IP, the extension‑based auto‑update will keep failing even after a successful manual install.

6. Fallback, if the manual install itself is blocked:

If the RHEL VM has zero outbound and you cannot even SCP the tarball in:

Stage the RHEL7‑64 tarball on a storage account with the same private endpoint that the VM already trusts, and pull it via azcopy/curl from that PE URL.

Or attach a temporary data disk with the installer already on it (recommended when you're doing this on many VMs).

As you are on 9.65.7440.1, one rollup behind. Grab the RHEL7‑64 package for 9.66 from the Azure‑SiteRecovery GitHub → MobilityAgent/AzureToAzure/AgentDownloadLinks.md, copy it to the VM, and run ./install -q -r MS -v Azure -a Upgrade. This is supported (within N‑4), does not require re‑registration, and does not disrupt replication.

Thanks,Suchitra.