firstcom Posted January 9, 2016 Report post Posted January 9, 2016 Hey all! I was looking over our ConfigManager environment and noticed something unusual. When I came into the company I'm part of, they had an existing ConfigManager environment with a CAS and two primary sites -- one that they use often, and the other acts as a DR server. Very rarely have I had to sign into the CAS. However, I noticed something that seems unusual. Before I go into this, I'll say this: The link between all servers show as active, with no errors. However, when the replication link analyzer is run on the CAS or the primary server, it suggests resetting queued replication messages on the SQL server. If you do it, it says it's successful - however, it repeatedly suggests having to do it. Everything else besides that shows up as green and good on the replication link analyzer. If you finally choose to skip resetting queued messages, it suggests there may be some messages stuck in the transmission queue on the primary site. Has anyone seen this before? How can I resolve it? On what could be an unrelated note, under the monitoring tab for database replication, *everything* shows as green on the primary server. On the CAS, everything under every tab shows as green except for "Secondary Site Data", "CloudDmp" and "Secondarty_Site_Replication_Configuration" -- I've tried to google research this, but haven't come across much. If anyone has seen or knows anything about either one of these items, please respond and let me know! Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted January 10, 2016 Report post Posted January 10, 2016 So you know that a second primary site is NOT a DR solution, right? Did you also know that you should be doing all of your Administration on the CAS, this is the whole point of a CAS? In fact it can be dangerous to not do your work on the CAS. Have you looked at the log files? Quote Share this post Link to post Share on other sites More sharing options...
firstcom Posted January 10, 2016 Report post Posted January 10, 2016 I have looked at all of the log files that I've read about and haven't found anything that indicates a problem. Then again, many of the articles out there in regards to replication aren't always the most straightforward. I'm still getting emails with alerts periodically about replication being down, even though the link shows as active and green. I wasn't aware that everything had to be done on the CAS, but I can adjust going forward. Can you provide any guidance on the errors and replication issue? So you know that a second primary site is NOT a DR solution, right? Did you also know that you should be doing all of your Administration on the CAS, this is the whole point of a CAS? In fact it can be dangerous to not do your work on the CAS. Have you looked at the log files? Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted January 10, 2016 Report post Posted January 10, 2016 Your best bet to fix, I hate to say it, it to contact Microsoft support (CSS). They have some non-public tools to help troubleshoot CAS and replication issue. SQL Replication is not simple, at all. I know this is not helpful but, personally unless you have 150,000 computers I would start looking at rebuilding your site using best practices. aka no CAS, understand what DR mean for CM12. Define your allowable downtime frame, this will dictate your design for example Cluster Hyper-v Hosts or define backup tasks. As soon as you have a CAS, you are begging for problems. IMO, It is a full time job to monitor and manage a CAS, because of SQL replicate. Quote Share this post Link to post Share on other sites More sharing options...
