Skip to main content

Database Replication

in Instance Problems
Authors list
Diterbitkan: 5 Jul 2022|Last updated: 13 Jul 2022

An instance may have a read-only database configured by the OPC. The following warnings are raised if any errors are detected:

Severity

Trigger

High

Unable to connect to the instance read-only database for any reason

High

There is no replication status to report (this indicates replication has not been setup on the server)

High

The status of database replication has reported some errors

High

The replica is more than 10 seconds behind the primary database.

Medium

The replica is between 5-10 seconds behind the primary database.

Low

The replica is between 1-5 seconds behind the primary database.

Low

The configured user doesn't have sufficient permissions to check replica status.

Remediation Copy link to Remediation to clipboard

Please review the message that is presented in the Problem GUI and take action as required (e.g. start the database service if it is not running).

MembantuUnhelpful
next pageCron jobs
previous pageInstance Deskpro Version

Please log in or register to submit a comment.

Page sections