Checking replication status as an administrator
To view status information about a replication node:
Click Manage the system > Maintenance > Database replication.
Select a node.
Select the Status tab.
The status page includes the following information:
General
Product version
Database version
Commits to the database have been suspended
Replication from this node has been suspended
Unique identifier for this server
Send queue to <node><port>
Minimum size of the queue
Queue backlog
Maximum size of the queue (% of disk space)
Disk space used (%)
Queue has reached minimum free space threshold
Queue is empty
Time since last queue item was processed (seconds)
Last item completely processed
Queue delay of last item (seconds)
Size of failed procedure log
Current queue sequence number
Generation ID of this queue
Receive queue from <node><port>
Minimum size of the queue
Queue backlog
Maximum size of the queue (% of disk space)
Disk space used (%)
Queue has reached minimum free space threshold
Queue is empty
Time since last queue item was processed (seconds)
Last item completely processed
Queue delay of last item (seconds)
Size of failed procedure log (bytes)
Generation ID of this queue
Receive queue usage statistics for the last 5 minutes
Command
Total time spent processing (ms)
Number of executions
Send queue and Receive queue will show the queues for each connected node where:
<node> is the address of the replication node.
<port> is the port number for the Database Service.
Configuration notes
This database status refers to Bravura Security Fabric ’s Database Service, not to the actual database status, which must be monitored separately.
In shared schema (either hybrid or simple - only one database node with more than one application node), the local status and settings have to be configured separately on each application node that connect to the same database.
The settings for each node can be found in the application node’s file system in <instance>\service\iddb.cfg; as the previous note implies, after settings propagation these files should contain the same data in all nodes in direct replication (other than the local-node setting), but different on the nodes in shared schema.
Telemetry is enabled for replication by default, to periodically gather metrics on the replication queue state. These metrics are stored locally on each replication node and are not automatically transmitted, and do not contain sensitive information. These metrics may assist in troubleshooting possible replication queue issues. To opt-out from telemetry, contact support .