What is propagated

Not all files and registry entries are propagated. To determine which, there are whitelists and blacklists that specify what data to include and what data to omit in the context of file/registry replication. For example, log files (idmsuite.log) and database service configuration files (iddb.cfg) are not replicated by default, as this would be wasteful (log files) or cause incorrect configuration to be forwarded (database service configuration).

These lists are a combination of items built into the replication software plus user-configurable items set by editing a configuration file (psconfig/updinst.cfg).

The updinst utility allows you to check what files are copied and which are not by running the following command from from the instance's util directory:

updinst -showconfig

To determine the current configuration (including blacklists and whitelists), you can run in a command prompt opened in the instance's util directory:

updinst -showconfig

You can modify the configuration by using entries in the updinst.cfg file. A sample of updinst.cfg is located in the samples directory. This configuration file must be placed in the \ <instance> \ psconfig \ directory before the File Replication Service can use it. Use this configuration file to control which files and registry settings are replicated to other instances (whitelist) and which are not replicated (blacklist). The whitelist settings override blacklist settings.

See updinst.

The updproxy binary does not use a config file. All whitelists and blacklists are built into the binary. Contact support@bravurasecurity.com with the Bravura Security Fabric version installed on your instance to obtain the blacklist information.

See updproxy.

See also