Because the RAPStore may store and maintain several years’ worth of market data, a redundant configuration is not practical. If the data in the RAPStore becomes stale due to loss of the data stream or Subscriber, the RAPStore data must be manually loaded from the RAPCache.
You may choose to install a complete secondary system for the RAPStore, as in the case of the RAPCache (the secondary data stream does not preclude this configuration), but the expense of a secondary RAPStore could be prohibitive, as there may be many terabytes of data.
If you configure a secondary system for the RAPStore, the RAPStore is loaded only by a primary Subscriber.
If there is a failure anywhere in the primary data stream, data in the RAPStore becomes stale until manual intervention occurs. In this case, the RAPStore data is loaded from either the primary RAPCache or the secondary RAPCache, whichever is current.
A redundant RAPStore (an instance of an IQ multiplex server) and RAPStore Subscriber should be installed on a separate machine. The RAPStore Subscriber is configured to listen on the primary data stream. The redundant RAPStore and RAPStore Subscriber do not run, unless there is a hardware failure on the machine running the RAPStore. In the event of hardware failure of the RAPStore machine, you must, at the end of the trading day, launch the redundant RAPStore, load data from the current RAPCache into the RAPStore, and use the redundant RAPStore Subscriber for the operations of the following day, until the original hardware is repaired.
