I've never done clustering or SQL Always and from a quick look at it, it seems rather complicated :)
Is there a how-to guide, maybe specifically for OpsMgr? Is that one a good start, although not for OpsMgr? http://blogs.technet.com/b/canitpro/archive/2013/08/20/step-by-step-creating -a-sql-server-2012-alwayson-availability-group.aspx About your cluster. Those servers are shared and used for other DB's also? As with ConfigMgr, where I'm coming from, it was usually advised to have dedicated servers. Thanks, roland From: [email protected] [mailto:[email protected]] On Behalf Of Page, Stuart F. Sent: Montag, 18. August 2014 13:51 To: [email protected] Subject: RE: [msmom] SQL Always on? Roland, I would suggest a SQL cluster to provide high availability for your SQL DB's. Also, make sure you have a decent SQL backup strategy. We use SQL clustering heavily in our organization for lots of applications. We are currently in the same boat with our SCOM DB's, but we have plans to migrate them to our SQL cluster before too long. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Roland Janus Sent: Monday, August 18, 2014 7:32 AM To: [email protected] <mailto:[email protected]> Subject: [msmom] SQL Always on? My current design is two Mgt servers for some HA (no network yet) and the Ops and DW DB's on separate servers. But that makes SQL still single point of failure. So should I do Always on for both doubling SQL? Or can I do Always on with just those two, putting a copy of each to the other? OpsDB and DW DB on both? Should one fail, I still have both DB's but the same number of servers? Does that make even sense? :) Is there a point of doing two MgtServers for HA with just one SQL for each DB? -roland
