Closed pandaflourishingfish closed 10 months ago
It should. I just ran a test by stopping the SQL VSS writer on a host and refreshed the source to produce an error, and the script detected it:
Cluster,Status,Source Name, Environment,Protected,Unprotected,Auth Status,Auth Error,Last Refresh,Refresh Error,App Health Checks
"VE4","Healthy","oracle19a.seltzer.net","Oracle","1","0","Finished","","1/16/2024 1:52:06 PM","","n/a"
"VE4","Healthy","oracle19b.seltzer.net","Oracle","1","0","Finished","","1/16/2024 1:52:12 PM","","n/a"
"VE4","Healthy","sql2016.seltzer.net","SQL","7","0","Finished","","1/16/2024 4:00:25 PM","","Passed"
"VE4","Unhealthy","sql2016b.seltzer.net","SQL","0","5","Finished","","1/16/2024 5:18:27 PM","","IsSQLWriterRunning: The service SQL Server VSS Writer is not running. Current state: SERVICE_STOPPED"
I should have taken a screenshot the other day, of course today all of my sources have VSS working as it’s supposed to. When I have a good example, I can open a new issue. Sorry for the hassle.
No worries, I believe you, I'm just not seeing the same issue in my testing. Let me know when you have a live example we can jump on zoom to debug...
When running the "Registered Sources" script,I have a server that returns as "Healthy". However, if you look at the source in the GUI, it reports "An error occurred while querying state of the VSS writer SqlServerWriter. Please try restarting the service SQL Server VSS Writer."
Does the registered sources script check for this?