SuiteCRM operations: an in-depth administrator checklist
- Stable systems result from recurring, mundane checks, rather than occasional heroics after an outage.
- After upgrades, permissions, cache and smoke tests are mandatory, not optional.
- Backup without restore practice is hope, not strategy.
The silent scheduler
Jobs appear active but do not run, or fail without a UI alert. Workflow emails and reminders stop, and business teams notice only later.
Permissions after upgrades/CLI commands
Console commands run as a different user leave files the web server cannot write. Symptoms include failed uploads, cache problems and blank error pages.
Logs and disk
Unrotated logs and growing temporary files fill the disk. The CRM stops working even though the application logic has not changed.
Operations check: does your instance meet the minimum standard?
SuiteCRM production systems rarely fail because features are missing. They fail because schedulers stop silently, permissions break after CLI upgrades, backups go untested and knowledge resides with one person.
1. An operating model in layers
| Frequency | Focus |
|---|---|
| Daily / automatic | Monitor host, disk, HTTP and, where appropriate, job errors |
| Weekly | Scheduler last runs, log patterns and queue backlogs |
| After a release | Permissions, cache, smoke tests and critical flows |
| Monthly | Sample restore, user lifecycle and documentation updates |
2. Scheduler and background processing
- OS cron/timer assigned to the documented user
- Critical jobs: last successful run, not just “active”
- Failing jobs have an owner and ticket, rather than staying red indefinitely
3. Post-upgrade checks
Official guidance covers permissions after console commands and cache issues. In practice:
- Read the release notes for the specific version
- Set permissions as required for the web server user
- Follow documented cache/container steps
- Smoke tests: login, core process, email and report
4. Backup and recovery
Test restoration in an isolated environment — at least with sample checks of files and database contents. A backup nobody has ever restored is a file, not a plan.
The Health Center can bring diagnostics together in the CRM. It does not replace host monitoring, tested backups or clear ownership of cron.
Health Center ↗