Routine maintenance

A self-hosted SummitPSA install needs little day-to-day attention, but a light routine keeps it healthy and recoverable. None of this requires downtime beyond the brief restart blip an update causes.

Regularly

• Back up. Run the mariadb-dump plus uploads archive on a schedule, and store copies off the host. See Backing up your database and files.
• Watch the license banner. Address expiring, over-seat, or “unable to verify” warnings before they become critical. Use Check now to re-poll after any change. Remember the verification interval is every 12 hours by default and tolerates an unreachable server for a grace window (default 7 days).
• Check the logs for errors:

  sudo docker compose -f /opt/summitpsa/docker-compose.yml logs --tail=100 app

• Check container health and disk:

  sudo docker compose -f /opt/summitpsa/docker-compose.yml ps
  df -h

  Backups and Docker images accumulate — prune old backups and unused images so the host does not fill up. Keep the previous app image for rollback.

When updating

1. Take a fresh database backup first.
2. Apply the update by repinning the image tag (migrations run on boot). See Updating SummitPSA to a new version.
3. Confirm the schema revision and a healthy login after the restart.

Periodically

• Test a restore into a scratch environment so you know your backups actually work.
• Review active agents against your seat limit to avoid an unexpected over-seat true-up.
• Renew TLS certificates if you terminate HTTPS yourself (for example via certbot).