Backups and recovery
Compiled text through Nov 15, 2021
Register checked through Jul 29, 2026
Later Register activity found — review the notice before relying on the compiled text.
Dates and status
- Compiling agency
- Executive Department
- Text status
- Source receipt
- Compiled text through
- Nov 15, 2021
- Register checked through
- July 29, 2026/Vol. XLVIII, Issue 30 (2026-07-29)
- Activity status
- Later Register activity found — review the notice before relying on the compiled text.
- Latest notice
- TAF-46-21-00009-P · Proposed rule · Nov 17, 2021
- Source snapshot
- Jun 6, 2026
(a)Backup requirements.
The MCS shall have sufficient redundancy and modularity so that if any single component or part of a component fails, gaming can continue. There shall be redundant copies of each log file or system database, or both, on the MCS, with open support for backups and restoration.
(b)Recovery requirements.
In the event of a catastrophic failure when the MCS cannot be restarted in any other way, the system shall have the capability of being reloaded from the last viable backup point and fully recovering the contents of such backup, which should consist of at least the following information:
(1)significant events;
(2)accounting information;
(3)auditing information;
(4)specific site information, such as slot file, employee file, progressive set-up, etc.; and
(5)if voucher issuance is supported, all information used in the voucher redemption process, including information specific to the redemption of offline vouchers, if applicable.