About file synchronization

In addition to database replication, there is a need to replicate the contents of each application node’s files and registry key belonging to the instance. This is to forward configuration changes, user interface customization, copies of software updates, and so on, from the primary application node to all other application nodes and proxies. File replication should only send required files from the primary node to secondaries and proxies primarily to reduce resource use, especially the time needed to complete auto discovery.

File synchronization scheduling and programs

File/registry replication happens at the end of the nightly auto-discovery process on the "primary" Bravura Security Fabric application node; the primary application node sends files and relevant registry entries to each each "secondary" application node and each configured Bravura Security Fabric proxy server. If a configuration change is made on the primary node that needs to be replicated earlier than the scheduled process, replication can be triggered either by running the entire auto-discovery process manually, using the administrative console (Manage the system > Maintenance > File synchronization) or from the command-line by running updinst , located in the <Program Files path>\Bravura Security\Bravura Security Fabric\<instance>\ util\ directory.

The product installer creates a Windows Scheduled Task that uses updinst to propagate changes in the external databases (by copying the extdb.db and component.db) from the primary node to secondaries, every five minutes. As part of the initial configuration, and later if the primary application node changes, that scheduled task should be disabled on secondary nodes, and even on replicated instances whose configuration and other data saved in those databases does not change.