Back up and recover data

Define what must be recoverable

A complete recovery needs matching configuration, installation identity, credentials and persistent application data. A configuration archive alone is not a tracking-data backup. The installer does not create an automatic full backup for you.

Build a backup plan

1. Inventory the data locations and databases used by the installed Compose configuration.
2. Preserve the private configuration and identity material under /root/nevect in a restricted archive.
3. Export PostgreSQL through its supported logical backup procedure.
4. Back up ClickHouse data through a consistent procedure suited to its version and storage.
5. Include hosted landing files and other persistent assets.
6. Keep the exact Nevect version and backup time with the archive.

Do not treat copying a live database directory as a verified consistent backup. Use database-supported tooling or a coordinated filesystem snapshot with the required application and database consistency.

Validate recovery separately

Restore into an isolated environment before relying on the backup. Verify login, Tracker ID, campaign resources, historical statistics and file assets. Keep restored test services from receiving production traffic or sending live partner notifications.

Recovering production

Stop new writes through a planned maintenance procedure, restore the matching configuration and data, then validate services and license binding before returning traffic. Never run a fresh installation over a populated directory as a substitute for a restore.

Storage and privacy

Encrypt and restrict access to archives containing keys or personal data. Keep an off-server copy and test that it can be opened. Record what the backup excludes so its limitations are explicit.