Synchronization of configurations between master and standby servers, to minimize problems in the event of a failover.
Many high-availability deployments involve the use of hot standby systems. In these scenarios, one priority reduces configuration differences between the master and standby systems. Synchronization of defined parts of a configuration between the master server and standby server minimizes configuration differences that could cause problems in the event of a failover. Synchronization puts the least possible burden on the master system to reduce this risk.
By default, all configuration is excluded from synchronization and you must explicitly include a configuration node for it to be synchronized. Only a single standby system is currently supported.
Every time the master system starts or a commit, load, or merge command is run on the master system, the standby system is synchronously updated and its configuration is saved. The system tries to make all parameter values on the standby system within the
sync-map identical to the master. Partial commits, in the event of a commit failure, synchronize only the sections that were successfully committed on the master system.