PortivoDocs · v2.0.0Complete handbookportivo.orgGitHub
Administration

Backup and maintenance

Database export/import and operational retention.

v2.0.0Source-backed

Export

Admin database backup creates a consistent temporary SQLite snapshot and streams it from disk rather than loading the complete backup into process memory.

Import

Complete Portivo database restore is restricted to the bootstrap administrator. The current database is backed up automatically before replacement.

Secret continuity

A restored database containing encrypted Monitoring Credentials, Automation credentials or webhook endpoints requires the original APP_SECRET_KEY.

Maintenance

Administrators can run an immediate health scan and prune old operational records. The UI exposes retention periods for Audit Log and completed Jobs.

Source-backed detail

Backup, restore and retention in practice

The backup endpoint streams a consistent SQLite backup instead of loading the complete database into application memory. Treat the exported file as sensitive: it contains inventory, policy, normalized operational evidence and encrypted secret material.

Restore workflow

  1. Take a fresh backup and record the running application version.
  2. Stop operational changes and scheduled work before import.
  3. Import only a valid SQLite database through the administrative workflow.
  4. Allow startup migrations to complete, then verify users, inventory, roles, monitoring profiles and automation schedules.
  5. Run an explicit health scan before returning the system to normal use.

Maintenance pruning

Pruning is explicit and bounded. Completed job, audit and delivery history is trimmed according to platform retention controls; active work and current configuration are not maintenance targets. Keep an external backup before aggressive retention changes.