Share via

Move from classic to modernized VMware disaster recovery

Fed Yunis Zapata 0 Reputation points
2024-12-17T04:38:52.8666667+00:00

Hello everyone,

I hope you can help me with the error indicated in the title.

I am upgrading the ASR service for VMware from classic to modern.

I already have a new recovery vault, a new replication server deployed locally and associated to the new recovery vault.

In Azure I have 2 recovery vault:

The classic one with its configuration server and the protected servers.

Configuration server version - the most current version 5.24.1021.6 and working without a problem.

VM agent version - 9.63.0.0 and working without a problem

The new recovery vault with the replication server already deployed and configured. this server was deployed 2 days ago by downloading the OVA, which I understand must be the latest version.

But when I start the migration it shows me the error indicated:

Error: None of the replicated items present in the Recovery Services vault can be migrated because the currently available configuration servers are not in a healthy state or have a version earlier than 9.50

Is it necessary to install the new agent on the servers again? the friendly name of the replication server must be the same as the configuration server?

I hope you guys can help me with this issue o tell me what i missing with the configuration.

Stay tuned.

Fed Yunis.

Azure Site Recovery
Azure Site Recovery
An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.
739 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Pavan Minukuri 915 Reputation points Microsoft Vendor
    2024-12-20T23:04:04.6466667+00:00

    Hi @Fed Yunis Zapata
    Welcome to Microsoft Q&A Froum, Thanks for asking question here...!
    To successfully upgrade your Azure Site Recovery (ASR) service for VMware from classic to modern architecture, follow these steps:

    1. Check Configuration Server Health: Ensure that your configuration server is healthy. Check for any alerts or warnings in the Azure portal under Site Recovery.

    Verify Versions: Confirm that the configuration server version is at least 9.50 or higher. Your current configuration server version (5.24.1021.6) is outdated. The VM agent (9.63.0.0) and replication server (1.41.9267.8996) are up-to-date.

    Reinstall or Upgrade Agents: If there are issues with agents, reinstall the latest version of the VM agent on your protected servers to ensure compatibility with the new replication server.

    Replication Server Friendly Name: Ensure that the friendly name of the replication server matches that of the configuration server, as this can affect migration recognition.

    Check Network Connectivity: Ensure proper network connectivity between your VMware environment and Azure to prevent communication failures.

    Follow Migration Procedures: Follow the steps in the Azure portal to upgrade to modernized VMware replication. Navigate to the classic Recovery Services vault and select "Upgrade to modernized VMware replication."

    1. Post-Migration Considerations: After migration, monitor replication jobs to ensure they are working correctly. Remember that recovery plans must be manually recreated in the modernized environment.
      If you required anything let us know.

Your answer

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