Skip to main content
dbdock status
Shows configured schedules and, if DBdock is running as a long-lived process (via PM2), the service health.

Sample output

πŸ“… Scheduled Backups:

β”Œβ”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚  #  β”‚ Name         β”‚ Cron Expression β”‚ Status   β”‚
β”œβ”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚   1 β”‚ daily        β”‚ 0 2 * * *       β”‚ βœ“ Active β”‚
β”‚   2 β”‚ weekly       β”‚ 0 0 * * 0       β”‚ βœ— Paused β”‚
β””β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Total: 2 schedule(s) β€” 1 active, 1 paused

πŸš€ Service Status:

🟒 Running (PM2)
  PID: 12345
  Uptime: 2d 5h
  Memory: 45.23 MB

When there’s no service running

If DBdock isn’t running as a background process, the status section shows:
πŸ”΄ Not running

   Schedules won't execute automatically.
   See https://docs.dbdock.xyz/alerts/scheduling for setup.
This is normal if you trigger backups via system cron or CI β€” schedules in the config file are only used when DBdock itself is the scheduler.

Use cases

  • Check schedule configuration at a glance
  • Verify DBdock is running after a deploy
  • Quick health check before relying on a scheduled backup

See also

dbdock schedule

Add or modify schedules.

dbdock test

Validate connections and alert config.