This topic describes the EBS Central Post Trade impacts for a DR event on EBS Market and eFix, for both FIX and TOF sessions.

CME FirmSoft provides trade records for reconciliation. When required, trade information can also be obtained through an escalation to EBS Support in the Global Command Center. Contact details are available here: https://www.cmegroup.com/tools-information/contacts-list.html

After notification that a DR event has occurred, impacted customers will be required to connect to an out-of-region Central Post Trade gateway for trade confirmations. Refer to EBS Market and eFix DR Summary for all the reconnection details per system.

Contents

EBS Central Post Trade DR Impacts

Please review the full DR Process overview, then see below for EBS Central Post Trade  specifics.

State 1: Normal Production Processing (Pre-DR)

CPT in normal production state.

State 2: DR Event

In the affected Production environment, EBS Central Post Trade services will be unavailable. 

State 3: Connect and Trade in the DR Environment

EBS Central Post Trade sessions are only created on a single gateway. A EBS Central Post Trade client must use a session created in the DR data center to receive trade confirmations from DR.

Please see the EBS Central Post Trade scenarios below for examples.

Trades from both the Production and DR data center will be available via EBS Central Post Trade in DR.

State 4: Return to Production

For the return to Production EBS Central Post Trade clients must re-establish their sessions in the Production data center.

EBS Central Post Trade DR Scenarios

London LD4.2 DR Event

In this scenario, the EBS Market and eFix instruments trading in LD4.2 are failed over to the DR environment in NY5.

New York NY5 DR Event

In this scenario, the EBS Market and eFix instruments trading in NY5 are failed over to the DR environment in LD4.2.

Tokyo TY5 DR Event

In this scenario, TY5 fails. EBS Market and eFix instruments in New York and London continue trading on their Production environment.