This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi Team,
We have ASR configured on a Windows 2012 R2 Server running SQL Server 2014 in Production. ASR has been healthy since its configuration (~3 years ago). However, it changed to "Critical", with an RPO of 13 hours as of now (which appears to be time elapsed since the last crash-consistent recovery point).
The Agent version installed on the VM is 9.33.5598.1 and is Healthy.
We tried running the vacp -systemlevel so as to troubleshoot the Replication Health above.
The command completed with the message below:
Exiting with status 10003 Host: ABCDXYZ:Change tracking not in data mode
Consistency::Conclude : error 0x0 0x2713 gExitCode 0x2713
main EXITING
Entered ExitVacp() at 4:0:50:589
Exited at 4:0:5:50:589 with 0x2713
I have tried looking up the above error code/message on Azure documentation, but couldn't specifically locate it. No luck on other fora either and hence this post.
Request your support to help analyze and sort this out.
Thanks,
Siva
Usually this issue occurs when there is a problem with SQL instance or SQL VSS writers. I suggest you to update any pending patches for your SQL and also restart VSS writers. If this doesn't help, would it be possible for you to upgrade your SQL server to a higher version?
Sure, Sad.
Thanks for the guidance.
We'll reach with a Support Case if this re-appears.
Thanks for the prompt replies & support.
Regards,
Siva
Glad to help. :)
Hi Sad,
Thanks for the reply.
We have already verified that VSS writers are 'Stable' and that there are no VSS shadows on the server.
The server is patched and up to date on that count too.
I am not too sure about the possibility of upgrading SQL Server, as that is a management decision.
Having said this, we see the VM's Replication Health is back to Healthy status now.
It is not clear how that happened, as we don't find any events related to that.
It'll be great if you could share any generic possibilities on how this may have got sorted and how this can be prevented, going forward.
Thank you :)
Siva
Thanks for the update! Glad to hear it is resolved :)
To understand what went wrong and how it got fixed requires a deeper investigation and that can be done through a technical support channel by raising a support request.
How to prevent such failures: As long as your configuration/set up is in line with the recommendations provided in the official documentation there is nothing specific that you need to be worried about. If there any changes or updates from service end you will get notified.