Page Comparison

...

Up to 99.99% Availability

The…

...

The following setup illustrates a typical bare-metal hardware

...

environment. MediationZone is deployed in at least 1 site/region, with a minimum of 2 nodes

...

.

...

Prerequisites for achieving high availability:

• Redundant disk and database storage

  Configured and deployed

  , that is configured to meet the availability target.

• HA A High Availability Cluster Monitor 3PP Required

  Cluster

  . This application monitors process

  health via status interfaceCluster orchestrates process

  availability and health, and orchestrates an ordered fail-over when an issue is detected:

  Migrated

  1. Migration of the Virtual IP address.

  Mounts

  1. Mounting of storage.

  Starts process

  1. Startup of processes on the stand-by machine.

Up to 99.99% Availability via VM Failover

The…

...

Virtual Machine (VM) monitoring and failover to alternate host, used when deploying on Virtual Machines (VMs)

• VMWare vMotion, VMWare HA

• AWS EC2 Auto-scaling

• Etc.

...

The following setup illustrates a typical Virtual Machine environment. MediationZone is deployed in at least 1 site/region, with a minimum of 2 compute nodes

...

.

...

Prerequisites for achieving high availability:

• Redundant disk and database storage

  Configured and deployed

  , that is configured to meet the availability target

  Process monitoring .

• A 3PP handling Virtual Machine (VM) monitoring and failover to alternate host. For instance VMWare vMotion, VMWare HA, AWS EC2 Auto-scaling, etc. The process monitoring/recovery is achieved by scheduling a script that starts all PICO processes not running on the local VM.

Up to 99.999% Availability Geo-redundant Deployment

The…

...

A geo-redundant setup spans at least 2 sites/regions, minimum of 2 compute nodes per site/region

...

Active – Active Scenarios

...

Independent sites/Platforms

...

. MediationZone can be deployed in an Active-Active or Active-Passive configuration.

...

Active–Active scenarios are typically used for real-time

...

deployments, and consist of two independent sites/installations. Replication requirements:

• Filesystem: not required.

• System Database

  replication

  :

  System (NOT required), Audit (NOT required), Runtime state (optional, case dependent)

• Filesystem replication: Not required

Active – Passive Scenarios

Typically

not required.

• Audit: not required.

• Runtime state: optional, depending on use case. An example of a case where it is required is aggregation/correlation scenarios with database back-end, where the sites act as each others fail-over.

Active–Passive scenarios are typically used for batch applications, and consist of a single Platform instance running

...

Replication requirements:

• Database replication: System (required), Audit (optional), and Runtime state (optional)

• Filesystem replication: Runtime data stored to disk

. The Passive site is a replica of the Active site, and needs to be started

...

in case the Active site goes down. Replication requirements:

• Filesystem: required when runtime data is stored to disk. For example File System aggregation/correlation and Duplicate UDR Detection.

• System Database: required.

• Audit: optional.

• Runtime state: optional, depending on use case.

VM-based High Availability Deployment

...