Backups and recovery

Backups are part of the product surface, not an afterthought

BaserDB is designed to treat backups, restores, and audit as visible product capabilities so operators can understand where protection lives and what recovery actually means.

Native storage

Filesystem-based backup roots keep artifacts under infrastructure you control, while the console provides the management layer.

Governed restores

Restore actions are role-restricted, confirmation-oriented, and expected to remain auditable end to end.

Operational visibility

Operators should be able to see runs, timestamps, artifact targets, and recovery posture without dropping into guesswork.

Verify the backup root

ls -lah /var/lib/baserdb/backups
gzip -t /var/lib/baserdb/backups/manual/latest.sql.gz

Restore checklist

1. Confirm the target scope and snapshot.
2. Trigger the restore run from the control plane.
3. Wait for audit + completion status.
4. Verify the target group before reopening traffic.