How to solve error Protection could not be configured for the machine when uploading a physical machine to AZURE

issau neshiri 76 Reputation points
2024-02-05T09:42:42.6966667+00:00

Error ID

310056

Error Message

Protection could not be configured for the machine 'docuBridge.varipharm.co.zw'.

Possible causes

Check the failed Enable Protection job for more information.

Recommendation

Resolve the issue, disable protection on the machine and then retry the enable protection operation.

Azure Migrate
Azure Migrate
A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
724 questions
{count} votes

1 answer

Sort by: Most helpful
  1. SadiqhAhmed-MSFT 39,126 Reputation points Microsoft Employee
    2024-02-06T17:05:44.7066667+00:00

    @issau neshiri Thank you for posting your question on Microsoft Q&A platform. Sorry for the inconvenience this must have caused you!

    From the description I understand that you want to migrate your on-premises physical server to Azure and while doing so, you received an error "Protection could not be configured for the machine" not sure which operating system you are migrating from the Physical servers. Please check the pre-requisites and verify all the steps are completed before you start the process - https://learn.microsoft.com/en-us/azure/migrate/tutorial-migrate-physical-virtual-machines

    Supported and Limitations of migrating Physical Servers - https://learn.microsoft.com/en-us/azure/migrate/migrate-support-matrix-physical-migration#physical-server-requirements https://learn.microsoft.com/en-us/azure/site-recovery/vmware-physical-azure-support-matrix#replicated-machines

    Also check this log file and upload here if possible - %ProgramData%\ASRSetupLogs\ASRUnifiedAgentInstaller.log

    Make sure the installer is not blocked and running with admin permissions.

    One more suggestion is to restart your Virtual Machine for the Mobility agent to start responding and communicating with your Recovery Services Vault. If the restart still does not fix it then uninstall the mobility agent from the machine, unprotect the machine and then re-protect again.

    Hope this helps. Let us know how it goes!

    0 comments No comments