Azure Site Recovery Error 153017: Unable to Upload Replication Logs to Cache Storage Account

Pritam Jangid 0 Reputation points
2026-10-27T12:02:50.54+00:00

Hi everyone,

I'm encountering Azure Site Recovery Error 153017 while configuring Azure-to-Azure VM replication. I've already tried the suggested troubleshooting steps, but the issue persists. I'd appreciate any guidance on identifying and resolving the root cause.

Environment Details

Source VM: Central India

Target Region: West US

Recovery Services Vault: East Asia

Replication Type: Azure-to-Azure

Vault Configuration: Private endpoints enabled and system-assigned managed identity configured.

Cache Storage Account: Custom storage account in Central India, with a Blob private endpoint in the source VNet and public network access disabled.

Network Configuration: Private DNS zones (privatelink.blob.core.windows.net and privatelink.siterecovery.windowsazure.com) are linked to the source, hub, and target VNets. Global VNet peering is configured between these VNets.

Troubleshooting Already Performed

Verified that the cache storage account's Blob FQDN and the vault FQDNs resolve to private IP addresses from the source VM.

Confirmed that Test-NetConnection on port 443 succeeds for both the storage and vault endpoints.

Assigned Contributor and Storage Blob Data Contributor roles to the vault's system-assigned managed identity on the cache storage account.

Enabled Allow trusted Microsoft services to access this storage account.

Error Details

Error ID: 153017

The machine is unable to upload replication logs to the cache storage account for the disks: ''

Questions

What could cause Error 153017 when DNS resolution and TCP connectivity on port 443 are successful, particularly when the cache storage account is accessible only through a private endpoint? Could authentication settings, shared key access, storage account configuration, or the Mobility agent's network path be responsible?

Which Mobility agent log files should I inspect on the source VM to identify the actual upload failure, including any HTTP status codes or authentication errors?

Does the Mobility agent require any additional outbound connectivity beyond the cache storage private endpoint and Microsoft Entra ID endpoints?

Are there any specific Azure Site Recovery requirements or limitations for using a custom cache storage account with public network access disabled and a private endpoint?

I'd appreciate any suggestions, relevant documentation, or troubleshooting steps that could help identify the root cause.

Thank you!

Azure Site Recovery
Azure Site Recovery

An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.

0 comments No comments

2 answers

Sort by: Most helpful
  1. Jose Benjamin Solis Nolasco 13,376 Reputation points Volunteer Moderator
    2026-10-28T12:30:46.5166667+00:00

    Welcome to Microsoft Q&A

    Hello @Pritam Jangid

    Based on the details you've provided, you've already validated the two most common causes of Error 153017:

    • DNS resolution to the private endpoints is working.
    • TCP connectivity on port 443 is working.

    That narrows the investigation significantly because Error 153017 is raised when ASR cannot upload replication data/logs to the cache storage account, and successful DNS/TCP tests don't guarantee that the actual Blob write operation is succeeding.

    A few areas I'd focus on:

    1. Validate the cache storage account configuration

    For Azure-to-Azure replication, the cache account has specific requirements. Verify that:

    • The cache account is General Purpose v2.
    • The cache account is located in the same region as the source VM (Central India in your case).
    • The cache account still exists and is the account currently selected for replication.
    • Any unsupported storage features are not enabled.

    Reference:

    2. Verify actual Blob write access, not just connectivity

    Test-NetConnection only proves the endpoint is reachable.

    The most useful next step is to perform an authenticated upload test from the source VM to the cache storage account using AzCopy. If the upload fails, the HTTP response and storage request ID can often reveal whether the issue is:

    • Authorization (403)
    • Storage account policy
    • Network/NVA/proxy interference
    • Private endpoint routing

    Reference:

    3. Review outbound dependencies beyond the storage account

    Even when using private endpoints, ASR still requires connectivity to several Azure services. In particular, verify that outbound HTTPS access isn't being restricted by:

    • Proxy servers
    • Azure Firewall
    • NVA appliances
    • Forced tunneling

    Reference:

    4. Enable ASR diagnostics and inspect the failed job

    To get the actual backend error:

    1. Open Recovery Services Vault → Site Recovery Jobs.
    2. Locate the failed replication/protection job.
    3. Export the job details.
    4. Enable Site Recovery diagnostic logs and send them to Log Analytics.
    5. Reproduce the failure and review the corresponding records.

    References:

    5. Private endpoint support

    Using a cache storage account with public network access disabled and a Blob private endpoint is a supported scenario, provided all private networking requirements are met.

    Reference:

    One question that would help narrow this down further:

    Did you disable storage account key access ("Allow storage account key access") on the cache account, or are you using the newer managed identity-based cache account configuration?

    That distinction can be important in isolating authentication-related causes for Error 153017.

    If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find similar solutions. Thanks!

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-10-27T12:03:58.5633333+00:00

    A private cache endpoint is supported for Azure-to-Azure replication, so the next decisive check is an authenticated AzCopy upload from the source VM to the cache account; this distinguishes a working TCP handshake from the authorization, storage-policy, routing, or proxy failure represented by error 153017.

    1. Reproduce the actual storage operation

    Test-NetConnection proves only that TCP 443 opens. It does not prove that the Mobility service can authenticate and write a blob.

    1. From the source VM, use AzCopy to upload a test file to a temporary container in the cache account.
    2. Use the same Blob FQDN that resolves to the private endpoint.
    3. Record the HTTP result and request ID:
      • 403 points toward authorization, storage policy, or the request reaching an unintended endpoint.
      • Timeout/reset points toward routing, firewall, proxy, or NVA handling.
      • A successful upload shifts the investigation to the ASR agent/service operation.

    Microsoft specifically recommends AzCopy from the source VM for testing uploads to the cache account and identifying latency or NVA-path problems.^1^

    Example using interactive Microsoft Entra authentication and a temporary container:

    'ASR upload test' | Set-Content C:\Temp\asr-test.txt
    azcopy login
    
    azcopy copy `
      'C:\Temp\asr-test.txt' `
      'https://<cache-account>.blob.core.windows.net/<test-container>/asr-test.txt' `
      --overwrite=true `
      --log-level=DEBUG
    

    This test validates the user’s identity, not the vault identity, but it confirms whether a complete authenticated Blob request can traverse the source VM’s actual network path. Preserve the AzCopy debug log and storage request ID.

    2. Validate the supported cache configuration

    Check Storage account → Overview/Configuration/Data protection:

    • The account must be General-purpose v2 for a storage private endpoint.
    • It must be in Central India, the same region as the protected VM.
    • Blob soft delete must be disabled; soft delete is not supported for an ASR cache account.
    • The cache container/account must still exist and be the resource selected in the replicated item.
    • The Blob private endpoint connection must show Approved.

    These are Azure-to-Azure cache requirements.^2^ A storage private endpoint is supported, but it must be for the cache/log account in the source network and have network line of sight from the source machine.^3^

    Because DNS and TCP tests already succeed, do not repeat those checks. Instead, verify the path actually used:

    • Private endpoint → Metrics → Bytes In/Bytes Out while reproducing the error.
    • Check effective routes on the source VM NIC for the private endpoint IP.
    • If a proxy is configured, bypass it for the exact cache FQDN. Private-endpoint traffic must follow the VNet route, not be sent to an outbound web proxy.
    • Check whether an NVA or forced-tunnel route is intercepting replication traffic. Microsoft notes that an NVA can throttle or disrupt cache uploads.^4^

    3. Authentication and shared-key access

    Disabling shared-key access is supported. ASR can use a cache account with key-based authentication disabled when:

    • Managed identity is enabled on the Recovery Services vault.
    • That identity has read/write access to the cache account.

    Therefore, shared-key access should not need to be re-enabled solely because of 153017.^5^

    Since the managed identity and data-plane role are already configured, inspect Storage account → Activity log for failed role-assignment changes and enable Blob diagnostic logging to capture failed requests. A 403 with its storage error code is substantially more useful than 153017 alone.

    4. Required outbound connectivity

    The cache private endpoint is not the Mobility agent’s only dependency. The source VM also requires outbound HTTPS access to:

    • The cache account Blob FQDN
    • login.microsoftonline.com
    • *.hypervrecoverymanager.windowsazure.com
    • *.servicebus.windows.net
    • *.vault.azure.net for ADE-enabled VMs
    • *.automation.ext.azure.com when Mobility agent automatic upgrade is enabled

    Authenticated outbound proxies are not supported, and IP-based filtering is not recommended; use the documented service tags or URL allow-list.^4^ Microsoft Entra ID itself does not support private endpoints, so it still requires permitted outbound access even when both the vault and cache use Private Link.^3^

    5. Logs and escalation

    The published svagents*.log locations apply to VMware/physical-server Mobility agents, not Azure-to-Azure VM replication, so they should not be treated as the authoritative log path for this case.

    For Azure-to-Azure:

    1. Open Recovery Services vault → Site Recovery jobs.
    2. Select the failed operation.
    3. Use ExportJob → Export and retain the exported job details.^6^
    4. Configure Vault → Diagnostic settings → Add diagnostic setting, send all AzureSiteRecovery* categories to Log Analytics, then reproduce the failure.^7^
    5. If AzCopy succeeds but ASR continues returning 153017, open an Azure support request and attach:
      • Exported Site Recovery job
      • Exact failure timestamp and correlation/request IDs
      • AzCopy debug log
      • Storage Blob diagnostic events
      • Effective route table and proxy/NVA details

    References

    1. Troubleshoot replication in Azure VM disaster recovery
    2. Support matrix for Azure VM disaster recovery between Azure regions
    3. Replicate machines with private endpoints in Azure Site Recovery
    4. About networking in Azure virtual machine disaster recovery
    5. Turn off key based access on cache account
    6. How to troubleshoot Azure Recovery Services
    7. Monitor Site Recovery with Azure Monitor Logs
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.