Split Mode Restrictions
- For dual database configurations using a PostgreSQL® NGA managed database, consistency is only guaranteed when the driver configuration sets the timestamp by the device, not by the Event Manager.
- Split mode is not suitable for testing changes to the archiving configuration. When in split mode, archiving configuration modifications are not sent to the database, so their effects cannot be evaluated until these changes are committed to the database.
- Configuration changes related to NGA must not be made on the NGA split active host. These changes include adding or removing archive configurations, adding or removing NGA archive groups, and modifying the Alert Class Save alerts settings. If you must make these changes, we strongly recommend restarting the NGA manager on the host that was NGA split active after the system returns to redundancy. This is especially important if you chose to discard the changes on the NGA Split passive side.
Split mode is not suitable for upgrading the WinCC OA version. Please refer to the relevant chapter for more information Update Installation\Uninstall.
