Page tree
Skip to end of metadata
Go to start of metadata

CME Group defines a Disaster Recovery (DR) event as the transfer of the CME Globex production environment to the CME Globex DR environment due to failure or abnormal termination of the production environment. This topic describes possible DR scenarios and the disaster recovery recommendations available to Co-Location customers.

CME Globex Co-Location customer equipment is housed in the same facility as the CME Globex Production environment. As a result, Co-Location customers may have special considerations in the event of a CME Globex production failure.

Important: Co-Location customers are responsible for their own DR strategy. Co-Location customers must have disaster recovery procedures in place to continue business accordingly.

CME Group identifies three scenarios that would initiate DR procedures for the Co-Location facility:

  • Co-Location Services available / CME Globex unavailable
  • Co-Location Services unavailable / CME Globex available
  • Co-Location Services unavailable / CME Globex unavailable (entire facility unavailable)
 CME Group Certification and New Release environments are unavailable if a DR event occurs.

Co-Location Outage Event Notification

DR event notifications are communicated by the Co-Location Customer Support team if the Co-Location Production environment fails as result of a disaster. DR notifications are sent to registered contacts enrolled via the Co-Location Services Customer Support Portal.  Firm Administrators can register emergency contacts from the Firm Administration tab on the Customer Support portal.

CME Globex DR Event Notification by the CME Global Command Center (GCC)

If the CME Globex Production environment fails, CME Globex DR event notifications are communicated by the GCC. DR Notifications are sent to registered contacts and non-registered contacts who are enrolled in GCC Notifications. 

  • To become a registered contact, your Clearing Firm will have to register you for FirmSoft access. A CME Group Login ID and token are required. If you do not have a CME Group Login ID, please obtain one here.
  • Non-registered contacts can enroll in GCC Notifications by sending their name, e-mail address, and firm to gcc@cmegroup.com. Messages are sent via email, SMS text, mobile and land line phones.

CME Group Data Center Environments

Co-Location customers may lose connectivity to the CME Globex Production environment in the event of a production failure. If this occurs, customers are responsible for connecting to the CME Globex DR environment. The sections below provide guidelines to ensure a successful re-connection for business continuity.

Disaster Scenarios for CME Globex and Co-Location Facilities

The Production facility houses CME Globex Production and Co-Location services. The following table details each of the three scenarios for which the Co-Location customer must be prepared.

Disaster Scenario

Availability

Description

CME Responsibility

Customer Responsibility

Scenario 1

  • Co-Location Services available
  • CME Globex Production unavailable

Co-Location Services are operable, but CME Globex Production is inoperable.

CME initiates CME Globex DR procedures.

If carrier services remain up, CME Secondary feed will be available.

G-link is available in this scenario---customer routing is enabled by CME to the CME Globex DR Datacenter.

No customer action required.

Scenario 2

  • Co-Location Services unavailable
  • CME Globex Production available

Customer has lost connectivity to CME Globex Production within Co-Location facility.

N/A

Customer initiates their internal DR strategy.

Scenario 3

  • Co-Location Services unavailable
  • CME Globex Production unavailable

Site failure; Co-Location Services and CME Globex Production are inoperable.

CME initiates CME Globex DR procedures.

Customer initiates their internal DR strategy AND connects to Backup CME Globex Data Center.

Connectivity Options

For complete details on connectivity options and DR testing scenarios, please refer to: Disaster Recovery Scenarios.

  • No labels