Alerts: Could Not Connect to Database



  • Could not connect to database
  • Email alerts are sent indicating cannot connect to database

Possible Causes

  • These can be normal if the system was undergoing maintenance, updates, or other actions that would prevent subsystems from accessing the database normally and can generally be ignored.
  • Under heavy load, the backup system may generate these messages even though there are no problems with the connection to the database.


To reduce the frequency of seeing this error, in the Legacy UI, adjust the setting under the Alertman section of the Settings file (Settings > System, Updates, and Licensing > General Configuration) to increase the number of minutes a connection cannot be made before generating an email. This setting is:

// Minutes the system database must be down before an email is sent

If this issue persists contact support to review the system I/O performance and/or database health.

Have more questions?

Contact us

Was this article helpful?
0 out of 0 found this helpful

Provide feedback for the Documentation team!

Browse this section