Separated Duplex os4000

[persi01]

Hi guys need some basic help with regards to type of deployment in Os4000

I have deployed simplex & duplex os4000 Version 8 on eco server hardware. There is one more type separated
duplex. It will be helpful if anyone share some document or information related to this & how it is diffent from
simplex & duplex.

 

[donb01]

I would have to go back to all my notes from school to not lie to you, but I believe separated duplex is 2 servers that are remote to each other and stay synched to each other over the network so if something bad ever happens to one the other takes over just like regular duplex. One of the big differences is when you do upgrades and stuff because there are a few different steps. I don't think it is like APE processors where every morning the main 4K downloads a copy of it's data to the APE processor. An APE is designed to run one site as an island in an emergency, where I believe separated duplex would still allow the remote processor to see everything that is still in service.

That's from my head - all my notebooks are in my office.

Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA

 

[GZgidnick]

Separated duplex requires a Quorum Node.
This is yet another server you need to install. Either on industry standard hardware or a VM.
It will allow you to geographically split the cluster (L3 separation) and deal with conflict situations of Primary/Primary or Secondary/Secondary nodes requests.
It is referred to as a 'STONITH' server as well.
This means if both your NodeA and NodeB claim the Primary role and try to seize the DRDB shared resource/paritions the Quorum node will make a decision on which Node came first and assign the Primary role to this Node whilst Shoot The Other Node In The Head (STONITH).

From a deployment perspective there is not much difference, just select "Separated Duplex" config template in your XML Config Tool and allow an extra IP address for the Quorum server.
Use the XML file after to install and provision your (3) servers.

From a wiring perspective, you obviously can't plug in the Corosync cables directly from Node to Node, same with the Atlantic, and you need to have your VLANS configured for this subnets on the corporate switches where your servers will plug into.