NGA Split Mode

Split Mode is an operation mode for redundant systems that allows you to test configuration changes independently on one host (the test host) without affecting the operation of the other host (the production host). When you exit Split Mode and return to redundancy, you can choose whether to discard the changes made on the test side or apply them to both systems.

NGA supports Split Mode operation for the PostgreSQL® backend in both NGA-managed (dual database) and centralized configurations. The NGA Split Mode feature ensures there is no interruption or archiving loss. In dual database configurations, both databases remain synchronized with identical data.

When entering Split Mode, the active redundant host becomes the NGA split active host.
Note:
Note that you cannot switch the NGA split active host after entering Split Mode.

The NGA split active side continues to archive historical data as usual.

CAUTION:
The NGA split passive side does not modify the database(s); no historical data or metadata is written. When returning to redundancy, if you choose to apply the changes made on the NGA split passive host, the databases are synchronized with the updated configuration. This includes any added or removed archive configurations, added or removed NGA archive groups, and changes to the Alert Class Save alerts option.