Enable replication for VM failed in Azure sste recovery.

Shah, Darshan (Contractor) 26 Reputation points
2022-01-20T06:41:48.527+00:00

Hello,

We are facing one issue while enabling replication for one database VM in Azure site recovery. These VMs have Always on Availability group configured and these VMs are behind the internal standard load balancer.

We have already configured below required outbound rules for NSG.
166646-microsoftteams-image.png

Still while enabling replication got below error.

Error Details

Installing Mobility Service and preparing target

Error ID
539

Error Message
The requested action couldn't be performed by the Replication Provider.

Possible causes
The Provider action failed. Check other errors for more information.

Recommendation
Resolve the issue and retry the operation.

First Seen At
1/17/2022, 4:10:50 PM

Error ID
151196

Error Message
Site recovery configuration failed.

Possible causes
Connection cannot be established to Office 365 authentication and identity IP4 endpoints.

Recommendation
Azure Site Recovery required access to Office 365 IPs ranges for authentication. 1. If you are using standard load balancer, then enable outbound access for login.microsoftonline.com. 2. If you are using Azure Network Security group (NSG) rules/firewall proxy to control outbound network connectivity on the VM, ensure you allow communication to the prerequisite URLs or service tags. Refer to https://aka.ms/a2a-troubleshoot-151196

Related links
https://aka.ms/a2a-troubleshoot-151196
First Seen At
1/17/2022, 4:10:50 PM

These are production database VMs so assigning public IP or changing the standard load balancer to Basic is not recommended.
Could anyone please guide on this ?

Azure Site Recovery
Azure Site Recovery
An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.
626 questions
{count} votes

2 answers

Sort by: Most helpful
  1. SadiqhAhmed-MSFT 36,881 Reputation points Microsoft Employee
    2022-01-27T10:43:13.71+00:00

    The error - "no app-consistent recovery point in the last 'x' hours" when seen together with the continuous occurrence of the event- "app-consistent recovery tag generation failed" indicates that these errors are occurring due to failures while attempting to generate VSS snapshots.

    On Windows servers, often times this can happen due to applications such as SQL or third party backup software attempting to generate VSS snapshots and failing/resulting in a clash with ASR's attempts to generate an application consistent snapshot.

    You can find out if this is being caused due to a specific application/writer by running the following command from command prompt on the virtual machine on which this problem is being seen

    "VSSadmin.exe list writers"

    If the output of this command indicates failure for one particular writer, it is probably that application that is causing the VSS snapshots to fail. In such a case, most likely you'll be able to remediate this problem by restarting the service associated with the VSS writer that is failing.

    If all the writers are in a healthy/stable state, try restarting the following services from services.msc

    • Volume Shadow Copy
    • Azure Site Recovery VSS Provider

    Wait for a couple of hours once this is done to see if App-consistent snapshots are being generated successfully

    Rebooting the VM is a another way to achieve what I've described here.

    If you aren't interested in generating app-consistent recovery points for this virtual machine, you can change the app-consistent snapshot frequency in the replication policy to 0. Please not this will impact all virtual machines using this replication policy and ASR will stop attempting to generate app-consistent recovery points for virtual machines using this policy (ASR will then generate only crash consistent recovery points for these virtual machines)

    Hope this helps!

    If the response helped, do "Accept Answer" and up-vote it


  2. Shah, Darshan (Contractor) 26 Reputation points
    2022-02-04T08:12:37.993+00:00

    To resolve below error ,I have added NAT Gateway , now we are able to enable replication.
    Error ID
    539

    Error Message
    The requested action couldn't be performed by the Replication Provider.