Skip to content

Operations Guide

This guide covers operational procedures for running Enprivacy 3.0, including backup, restore, and reference RTO/RPO targets.

Backup and recovery is your responsibility as the operator. The following outlines the recommended backup scope and frequency.

ComponentDescription
Application databasePrimary data store (user data, workspace config, audit logs)
Object / blob storageUploaded files and attachments
Application configurationEnvironment variables and secrets (back up separately and securely)
ComponentRecommended frequency
Application databaseTODO
Object / blob storageTODO

These are reference targets for typical reference architectures. Actual values depend on your infrastructure and backup configuration.

ArchitectureRTORPO
Single-node (development)TODOTODO
High-availability (production)TODOTODO

The service connects to PostgreSQL using a database user with privileges over the application schema. For improved security, rotate this user’s password regularly using either a single-user or dual-user configuration. See Database Setup in the Deployment Guide.

The Web, Job, and LLM services cache downloaded models in ~/.cache. Mount this path to durable storage to accelerate restarts. The model cache does not need to be backed up — it can be repopulated from the Hugging Face Hub or pre-loaded as a one-off action.

Enprivacy 3.0 emits structured JSON audit logs to stdout. These should be forwarded to your SIEM or log aggregation platform.

See the Deployment Guide for upgrade procedures.