question

protech-6243 avatar image
0 Votes"
protech-6243 asked LimitlessTechnology-2700 answered

Initial Replication to Azure issue

Hi,

We are trying to replicate on prem VM's to Azure, but keep encountering a similar issue.
We can initiate the replication fine, but the progress stays at 0% and after a period of time
the initial replication fails with the following errors. We have tried everything we can think
of with no luck. There are 2 errors and our comments are below. Anyone have any ideas? Cheers!


We have verified the the 3 boot files locations are present and correct.

Error ID
18097
Error Message
Replication for the virtual machine SERVER failed due to a workflow validation failure (ErrorCode: 8079002f Timestamp 9/20/2021 2:44:29 PM).
Associated Errors
{18026} Replication for the virtual machine SERVER failed (ErrorCode: 8079002f Timestamp 9/20/2021 2:44:30 PM).
Provider error
Failed to verify required boot config files on the virtual machine's os disk. Verify that on the EFI partition '\EFI\Microsoft\Boot\bootmgfw.efi' is present. And on the Windows partition '\Windows\system32\winload.efi' and '\Windows\System32\config\BCD-Template' files are present. 'SERVER'. (Virtual Machine ID 0faa33ca-ec73-46f8-b9b7-64d10bb6f9d2, Data Source ID 534225838, Task ID edf65cd4-9773-4a53-b61b-b3a340877e9c)

Possible causes


Identity is not enabled for this vault, so we would expect this is not the cause of the issue.

Error ID
68501
Error Message
The virtual machine couldn't be replicated.
Provider error
Replication for virtual machine 'SERVER' is in error. Fix the error(s) and resume replication.
Possible causes
Replication errors occurred for virtual machine 'SERVER' in cloud/site 'onprem-site' because of issues with connectivity to Azure storage.
Recommendation

   1. If Identity is enabled on the Recovery Services Vault, please make sure the log/target Azure storage account
   has the necessary permissions to access the storage account.
     a) Go to your Storage account -> Access Control (IAM).
     b) Add the below role-assignments (for ARM based storage account) to the Recovery services vault.
         1) "Contributor" and,
         2) "Storage Blob Data Contributor" for Standard storage or "Storage Blob Data Owner" for Premium storage
   2. Fix any issues in the Event Viewer logs (Applications and Service Logs - MicrosoftAzureRecoveryServices) on the Hyper-V host server and resume the replication.

Boot configuration check failed in a Gen2 virtual machine.
Recommendation
Resolve any issues on the Hyper-V server.

azure-site-recovery
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@protech-6243 - Sorry for the inconvenience this must have caused!

If you've already tried the recommendations and still facing issue, I suggest, disable and re-enable replication or contact Azure technical support team for further investigation.

0 Votes 0 ·
LimitlessTechnology-2700 avatar image
0 Votes"
LimitlessTechnology-2700 answered

Hello @protech-6243,

I find you have one of the common errors in Azure Site Recovery during replication and recovery of Azure virtual machines (VM) from one region to another.

Contact Azure billing support to enable your subscription to create VMs of the required sizes in the target location. Then, retry the failed operation.

If the target location has a capacity constraint, disable replication to that location. Then, enable replication to a different location where your subscription has a sufficient quota to create VMs of the required sizes.

If you use private endpoints, ensure that the VMs can resolve the private DNS records.

Follow the below link for a better understanding,

https://docs.microsoft.com/en-us/azure/site-recovery/azure-to-azure-troubleshoot-errors



Hope this answers all your queries, if not please do repost back.
If an Answer is helpful, please click "Accept Answer" and upvote it : )

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

LimitlessTechnology-2700 avatar image
0 Votes"
LimitlessTechnology-2700 answered

Hello @protech-6243,

I find you have one of the common errors in Azure Site Recovery during replication and recovery of Azure virtual machines (VM) from one region to another.

Contact Azure billing support to enable your subscription to create VMs of the required sizes in the target location. Then, retry the failed operation.

If the target location has a capacity constraint, disable replication to that location. Then, enable replication to a different location where your subscription has a sufficient quota to create VMs of the required sizes.

If you use private endpoints, ensure that the VMs can resolve the private DNS records.

Follow the below link for a better understanding,

https://docs.microsoft.com/en-us/azure/site-recovery/azure-to-azure-troubleshoot-errors

Hope this answers all your queries, if not please do repost back.
If an Answer is helpful, please click "Accept Answer" and upvote it : )

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.