Try TT Now

Post Recovery

Overview

Customer will be notified by their TT Technical Account Manager (TAM) or a member of the Customer Service Center when connectivity and functionality to the primary gateway is restored.

Following recovery from a failover event, users must follow the steps below to resume trading via the recovered primary gateway.

Note

Backup gateways exists as a temporary method to continue trading during a failover event. Once the primary gateway has recovered, TT advises all users to restart trading via the recovered gateway.

Migrating Users to a Recovered Primary Gateway

Following a Recovery Event, you as the administrator must perform the following steps in order to migrate users to the primary TT Gateway and setup regular trading activity for the next trading session.

Migrating Users to the Primary Gateway

Sequence

Details

1. Traders must cancel any working orders, and close open positions on the backup gateway.

This step ensures that there are no working orders in the market and helps facilitate order book reconciliation at the end of the trading day.

2. Contact BVMF and request that the sessions IDs are logged out of the exchange.

Allows users to log in to the exchange with the same session IDs via the primary TT Gateway.

3. Verify the primary TT Gateway is “available to user” in TT User Setup

Allows traders to access the primary gateway.

4. Uncheck the “available to user” setting for the backup TT Gateway in TT User Setup.

Prevents traders from accidentally logging into the backup TT Gateway.

5. Users must log out of X_TRADER and re-login by only using the primary TT Gateway.

Workspaces will be converted to the primary TT Gateway however Algos must be manually updated to reflect the primary TT Gateway flavor (e.g., BVMF-A).

6. If Autotrader and/or RTD links are used, users will need to edit the spreadsheets to use the primary BVMF Gateway Flavor via the find / replace feature in Excel

You must update the exchange-flavor in both Autotrader and Excel.

7. Reconcile the Order Book

At the end of the trading session, the administrator may manually transfer fills from the backup gateway using X_RISK, so that traders may resume normal trading during the next trading session.

Order and Fill Behavior Post Recovery

The following table highlights the behavior of orders and fills after a recovery event.

Order and Fill Behavior - Post Recovery

Data

Behavior

Non-GTC Orders (including GTD)

The exchange will update the traders’ order books to reflect any fills received for non-GTC orders that were originally submitted on the primary gateway, as well as any remaining working GTD orders that were originally submitted via the primary gateway. However, fills and orders from the backup gateway will not be available.

Warning: Users must contact the exchange to verify their current position and status of working orders from the primary Gateway.

GTC Orders

Once reconnected to the primary gateway, the exchange will update the traders’ order book with any remaining working GTC orders that were originally submitted via the primary gateway. However, GTC orders placed on the backup gateway cannot be moved to the primary backup after recovery.

Working Orders/Fills

Fills for orders submitted on the backup gateway will not appear in the order book and must be manually reconciled at the end of the trading session.

Risk Limits

Ensure that all risk settings are the same on the primary and backup gateway. Since fills for orders on the backup gateway are not available, all risk limits will only account for activity from the primary gateway.

Any P/L based on activity through the backup gateway will not be factored into the users’ overall risk limits.

AutospreaderSE

Once reconnected to the primary Gateway, any affected Autospreader synthetic orders will attempt to re-synchronize its child orders to account for events that may have taken place while the Gateway was down. If re-synchronization is successful, the Autospreader synthetic order will continue, otherwise, it will be deleted.

AlgoSE

Affected Algo synthetic orders will be in a paused state and may be resumed manually, but it should be noted that order events (e.g. fill, delete) that took place while the Gateway was down may not be recognized in the Algo logic.

SyntheticSE

Following recovery, users may recreate staged and/or synthetic orders on the primary gateway.