Skip to main content

Triggering file/registry propagation

While database replication is instant (happens every second), file and registry propagation from the primary node happens manually or on schedule:

  • Manually by an administrator logged in to the primary node’s web-based interface:

    • Manage the system > Maintenance > Auto discovery > Execute auto discovery

      or

    • Manage the system > Maintenance > File synchronization

  • Scheduled:

    • In Manage the system > Maintenance > Scheduled jobs > PSUPDATE (or additional psupdate jobs).

      Note

      psupdate triggers updinst and updproxy only if the system variable "PSUPDATE FILE REPLICATION" is enabled.

    • In the Windows Administrative tools > Task Scheduler > Library > Bravura Security External Database Replicator task. This copies the external database and components database only.

    • With any other scheduler by running updinst and updproxy, or psupdate.

    Caution

    The updinst utility should be triggered only from the primary node (except for the -extdb option that is to be used only for the rare troubleshooting step of recovering from secondaries external databases corrupted on the primary node). When starting updinst from a secondary node you will receive a warning that the current node is not the primary and the service will close again.

In this section: