Backup, restore and software updates
Create and verify Finetic backups, understand restore boundaries and install entitled signed releases safely from the browser.
What a backup protects#
Finetic backups protect configuration and PostgreSQL-backed application state according to the selected scope. Source media is not duplicated into application backups.
Backup workflow#
- Choose the backup scope and destination.
- Create a consistent database export and configuration archive.
- Calculate integrity information.
- Verify that the archive can be read.
- Record size, created time and verification result.
- Apply retention without deleting active work.
A tar warning that files changed while being read means the backup was not a consistent snapshot. Finetic stages stable inputs rather than archiving its actively changing working directory.
Restore#
Restore is a controlled workflow: select an archive, verify it, review included scopes, stop conflicting services, restore state and restart. A destructive confirmation identifies what current data will be replaced.
Software updates#
Only administrators can check, download and install updates. Finetic compares the selected channel with entitlement-aware signed release metadata. The archive is compiled; it does not include private source, signing keys or repository history.
Before installation Finetic creates recovery state, verifies checksum and signature, validates the staged runtime, then performs an atomic switch and service restart.
Release channels#
Stable contains validated releases. Beta contains newer development intended for testers. A future nightly channel may contain automated builds and should not be treated as a stable household server.
Switching channels invalidates a cached candidate and performs a fresh comparison against the selected channel.