Can a Failover MID Server Cluster contain MID servers hosted in different cloud environments such as AWS and Azure?

[cynlink1]

In my scenario, I want to cluster two MID servers from different cloud environments (AWS and Azure) in a failover MID Server cluster to create redundancy if one environment becomes unavailable. The MID servers run on Windows hosts located in different cloud environments but in the same Active Directory domain.

For those of you experienced in this area, would you be for or against this configuration? If against, please let me know if you are against it because it simply will not work or because it is not recommended, or for some other reason.

@doug.schulze - I'd love your expert advice.

Many thanks!
Cyn

[DaveHertel]

Hi Cyn -- while I haven't tried your specific scenario, I doubt it'll work especially if the MID cluster type is "Failover".   For this type of cluster to work, the 2 (or more) MIDS would have to be configured identically (same IP access, ACLs, etc., etc.).  Since you mention these are 2 different cloud env's (AWS and Azure), I would guess they each have very unique setup per the env they are intended to serve.    Theoretically, maybe you could make this work if both mids are given identical access/setup to the targets... if in that situation, I don't know why 1 set of mids -in a load balanced type cluster -couldn't serve both cloud envs.

What I would do:

1. Avoid use a Fail-over type MID cluster.   a waste of time and resource IMHO.  Long story but short story is: FO cluster is a big waste compared to LB cluster type.

2. Consider a load-balanced type MID cluster to serve both cloud envs.   Set up all member mids in that cluster to service both cloud envs.  this might take some special network/acl work to allow an azure-host to connect to AWS network and vice-versa... (never tried this... but image it'll require jumping thru some hoops to knock down barricades)

3. If option 2 doesn't work, setup two mid-load balanced clusters, 1 for each cloud env.  i.e.  A LB type cluster in Azure with 2+ hosts for redundancy with access for azure-specific targets.   Then another LB cluster in AWS cloud only for aws-specifc targets

my 2 cents - hope this helps?

[cynlink1]

Dave,

Thanks for the feedback. 

I have been working with my internal teams to ensure the access to the targets is the same in both environments. You are correct in stating that it requires jumping thru some hoops.

Message received regarding using LB cluster type over FO cluster type.

Thanks again,

Cyn

[ServiceNow Tec2 · Accepted solution]

This has been resolved by ServiceNow Technical Support. Please refer to KB1024173 for more information.

[cynlink1]

When I click on the link for  KB1024173, I am directed to Configure a MID Server cluster in the ServiceNow docs. Is this the intended experience?