Why is my replication site partially registered to a replication policy

Jan Vávra 341

I am testing Recovery Services Site Recovery. I have on premises Hyper-V host and I want to register it to Recovery Services Vault.

I am at <my vault> / Site Recovery Infrastructure / Replocation Policies / <my policy>
After Adding my Recovery Site I've ended with Partially assosiated and I cannot see any details why.

SadiqhAhmed-MSFT 48,256 Reputation points Microsoft Employee

2023-10-05T07:30:17.9633333+00:00
Hello @Jan Vávra Thank you for posting your question on Microsoft Q&A platform. Happy to assist!

I see that you are trying to set up replication from your on-premise Hyper-V host to Azure and getting a message "partially associated" it means that the association between the Hyper-V host and the replication policy is incomplete. Here are some steps you can take to troubleshoot this issue:

Check the prerequisites: Make sure that the Hyper-V host meets all the prerequisites for Azure Site Recovery. You can find the prerequisites in the following article: https://docs.microsoft.com/en-us/azure/site-recovery/hyper-v-azure-tutorial#prerequisites

Check the registration status: Check the registration status of the Hyper-V host in the Azure Site Recovery portal. If the registration status is "Not registered", you will need to register the Hyper-V host before you can associate it with the replication policy.

Check the replication policy settings: Make sure that the replication policy settings are configured correctly. You can find more information on how to configure the replication policy settings in the following article: https://docs.microsoft.com/en-us/azure/site-recovery/hyper-v-azure-tutorial#configure-replication-policy-settings

Check the network connectivity: Make sure that there is no network connectivity issue between the Hyper-V host and the Azure Site Recovery vault. If there is a network connectivity issue, it can cause the association between the Hyper-V host and the replication policy to be incomplete.

Check the Azure Site Recovery logs: Check the Azure Site Recovery logs for any errors or warnings that might indicate the cause of the problem. You can find the logs in the following location: C: Program Files (x86)\Microsoft Azure Site Recovery\home\svsystems\logs.

If none of these steps resolve the issue, you may need to contact Microsoft Azure technical support team for further assistance.
SadiqhAhmed-MSFT 48,256 Reputation points Microsoft Employee

2023-10-06T14:42:17.11+00:00

@Jan Vávra Just checking in to see if you got a chance to see my response and if it helped, I would request you to "Accept Answer and Upvote" so that the relevancy of this post will improve when anyone in the community search for a similar query.
Jan Vávra 341 Reputation points

2023-10-06T14:49:16.8+00:00
I am currently solving this isssue with MS Azure Support.
I the Site Recovery Jobs there is a complaint about missing .avhd file - a Hyper-V snapshot file.
But this file isn't attached to any of virtual machines.

We've made serveral action yet:

Change Hyper-V host locale from Czech to English.

Deleted Recovery Services Vault, create new one, reregister the Hyper-V host to this new vault.

At Hyper-V host, recompile WMI db:
cd c:\windows\system32\wbem
mofcomp regevent.mof

Deleted all checkpoints (snapshots).

Nothing has helped for now. But I am optimistic and waiting for another Support input ;-)
SadiqhAhmed-MSFT 48,256 Reputation points Microsoft Employee

2023-10-06T19:59:22.5966667+00:00

@Jan Vávra Thanks for the update. Keep us posted!
SadiqhAhmed-MSFT 48,256 Reputation points Microsoft Employee

2023-10-11T10:30:33.8366667+00:00

@Jan Vávra Any progress on this?
Jan Vávra 76 Reputation points

2023-10-11T10:37:41.0766667+00:00

No progress. There is something wrong with the VMMS service that still insists on a avhx that is not assigned to any VM. We have deleted the VM and recreated using existing disks but nothing has helped.
SadiqhAhmed-MSFT 48,256 Reputation points Microsoft Employee

2023-10-11T12:31:04.9666667+00:00

@Jan Vávra Sorry to hear that it is still not resolved yet. I hope the technical support team will help you resolve the issue by providing an alternative solution to this problem.
SadiqhAhmed-MSFT 48,256 Reputation points Microsoft Employee

2023-10-16T10:08:28.5566667+00:00

@Jan Vávra Any good news?
Jan Vávra 341 Reputation points

2023-10-16T12:38:45.3+00:00

No, still waiting for support.
SadiqhAhmed-MSFT 48,256 Reputation points Microsoft Employee

2023-10-23T07:12:51.3766667+00:00

@Jan Vávra Were you able to get a solution from Azure support team?
Jan Vávra 341 Reputation points

2023-10-23T07:27:59.3933333+00:00

Had several calls with support with no resolution yet. The VMSS still insists on a avhdx - snaphost file - that is not required by any VM at the Hyper-V host. The original VM was recreated from a scratch several times.
SadiqhAhmed-MSFT 48,256 Reputation points Microsoft Employee

2023-10-23T07:31:52.8+00:00

@Jan Vávra Sorry for the painful experience. Let us know once the issue is resolved.
SadiqhAhmed-MSFT 48,256 Reputation points Microsoft Employee

2023-11-01T10:55:39.67+00:00

@Jan Vávra Any good news?
SadiqhAhmed-MSFT 48,256 Reputation points Microsoft Employee

2023-11-08T08:19:53.54+00:00

@Jan Vávra We haven't heard back from you. Please reply if you have any questions in this matter and we will gladly continue the discussion.
Jan Vávra 341 Reputation points

2023-11-08T08:21:14.82+00:00

Still waiting for MS Support.
SadiqhAhmed-MSFT 48,256 Reputation points Microsoft Employee

2023-11-13T06:25:30.9+00:00

@Jan Vávra Any progress on the support request?
SadiqhAhmed-MSFT 48,256 Reputation points Microsoft Employee

2023-11-15T10:43:45.7033333+00:00

@Jan Vávra For now, I'm closing this conversation. Please post updates from support if the issue is resolved.

Share via

Why is my replication site partially registered to a replication policy

Your answer