Hi All
Experienced SCOM admin here, but SCORCH noob. Standing up a small SCORCH infrastructure for the first time and needing to consider HA and Site resilience.
The design will have an Always-On Clustered DB, and at least two Runbook Servers, but is it possible to have one node of the DB cluster and the secondary Runbook server, at another site? Will performance be an issue if, say, Site A DB server fails over to Site B DB server? I know with SCOM, it's really important for the Management Servers and DBs to be co-located, as anything more than 10ms latency can impact. Is this the case for SCORCH? We are literally setting it up to run one Runbook at the moment, which will be executing very often (ingesting alerts from SCOM).
If not, I'll literally need to have two instances of SCORCH, one at each site, which I'd prefer to avoid as the failover instance, complete with an expensive SQL install, will be redundant 99% of the time.
Also, it looks like the Management Server cannot be HA. So if you lose your MGT Server catastrophically, can you still rebuild that and reconnect with your Runbooks via Designer?