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
No, in this production environment there is no shared disks are used in cluster.
The issue needs a further deeper dive technically. I recommend you to create a technical support ticket. The ticket enables you to work closely with the support engineers and get a quick resolution to your issue.
Here is the link - https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request to create support case.
Feel free to reply if you have any challenged contacting Azure technical support team.
After adding NAT Gateway , now we are able to enable replication. After synchronization process since long time replication status is "Waiting for first recovery point".
In Events - Last 72 hours(24) we found below messages since last 3 hours.
Recovery point generation failed.
App-consistent recovery point generation failed.
Do you have any hint ?
Sign in to comment