Azure Migrate: On-prem physical device unable to replicate to Storage account (agent based)

Milan Mladenovic 20 Reputation points
2024-04-01T19:24:28.2366667+00:00

Hello,

We have a problem where our on-prem machines wont start to replicate to azure. We have setup the replication appliance server and installed mobility agent on this one test machine that we want to replicate. We have express route from on prem to azure and we use private endpoints for all the services related to the migration (Storage account , Recovery services vault, Key Vault).

We have checked the connectivity from on-prem using nslookup and we get responses.

This is the latest event: Process Server is not able to accept more data for some disks. Error ID: 78217

I checked process server in azure and it's healthy and underutilized.

Any idea what is causing this server not to replicate?

edit: the issue was with the on prem machine it did not match the requirements for replication, the rest of the machines that we added for testing were replicating without too much issue.

Azure Storage Accounts
Azure Storage Accounts
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
2,696 questions
Azure Migrate
Azure Migrate
A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
718 questions
Azure Site Recovery
Azure Site Recovery
An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.
636 questions
0 comments
Accepted answer
  1. SadiqhAhmed-MSFT 37,686 Reputation points Microsoft Employee
    2024-04-02T06:23:16.4566667+00:00

    Hello @Milan Mladenovic Thank you for reaching out to us on Microsoft Q&A platform. Happy to help!

    Based on the information you provided, it seems that you have set up the replication appliance and installed the mobility agent on the on-premises machine that you want to replicate. You have also set up private endpoints for the services related to the migration, including the storage account used for replication.

    However, you mentioned that the storage account used for replication is located in Central US, while all other resources are located in East US. This could potentially cause issues with replication, as the latency between the replication appliance and the storage account could be higher than expected.

    To optimize replication performance, it is recommended to use a storage account that is located in the same region as the other resources. This can help reduce latency and improve replication performance.

    If possible, you may want to consider creating a new storage account in East US and using it for replication. You can then update the replication settings for the on-premises machine to use the new storage account.

    Please let us know if you have any other questions.

    0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest