Ops — Backups, Status Page, Logs, Updates
Quick Start
Open the admin panel and go to Backup Settings
Confirm backups are running and check that backup files are being created
Open the Status Page and verify all systems show as operational
Before any update, always create a backup first
Who This Is For
Platform administrators responsible for keeping Tally running and up to date.
What You Will Accomplish
Confirm automated backups are working
Monitor platform health on the status page
Review and export logs
Safely deploy updates
Prerequisites
Step-by-Step Setup
Open the admin panel and confirm backup settings are active. Backups should run automatically (typically every 15 minutes).
Check that backup files are appearing on schedule. You should see timestamped backup files in the storage location.
Open the status page and verify that all components show their expected status (operational, degraded, or outage).
Review recent logs from both the app and server when investigating issues or preparing for an update.
When it's time to update, follow this process:
Tell users about the maintenance window
Create a backup before starting
Deploy the update
Run basic tests to confirm everything works
Check the status page — all components should be operational
Important: Always create a backup before deploying any update. Run tests before and after every deployment.
Advanced Details Show / Hide
For administrators who manage the server directly, here are the technical details:
Backup environment variables:
DB_BACKUP_INTERVAL_MINUTES=15
BACKUP_DIR=/data/backups
BACKUP_ENCRYPTION_KEY=your-encryption-key
BACKUP_RETAIN_COUNT=96Checking backups from the command line:
ls -la /data/backups/You should see timestamped .sqlite.gz or .sqlite.gz.enc files.
If DB_BACKUP_INTERVAL_MINUTES is not set, backups default to every 15 minutes. A warning will appear at startup if no backup schedule is configured.
Validation Checklist
Common Issues and Fixes
| Symptom | Cause | Fix |
|---|---|---|
| No backups being created | Backup interval not configured | Ask your deployment admin to set the backup interval |
| Status page shows false alarm | Health check targets not configured correctly | Verify the check URLs; some expected errors shouldn't count as outages |
| Log files are too large | Too much detail being logged | Ask your admin to adjust logging levels |
| Update causes problems | No testing before/after deployment | Always run tests before and after every update |
Rollback / Fallback
Restore the most recent backup.
Go back to the previous version of the software.
Re-run health checks after rolling back.