Operations Guide
This guide covers operational procedures for running Enprivacy 3.0, including backup, restore, and reference RTO/RPO targets.
Backup
Section titled “Backup”Backup and recovery is your responsibility as the operator. The following outlines the recommended backup scope and frequency.
What to Back Up
Section titled “What to Back Up”| Component | Description |
|---|---|
| Application database | Primary data store (user data, workspace config, audit logs) |
| Object / blob storage | Uploaded files and attachments |
| Application configuration | Environment variables and secrets (back up separately and securely) |
Recommended Backup Frequency
Section titled “Recommended Backup Frequency”| Component | Recommended frequency |
|---|---|
| Application database | TODO |
| Object / blob storage | TODO |
Restore Procedures
Section titled “Restore Procedures”Restoring the Database
Section titled “Restoring the Database”Restoring Object Storage
Section titled “Restoring Object Storage”Reference RTO / RPO
Section titled “Reference RTO / RPO”These are reference targets for typical reference architectures. Actual values depend on your infrastructure and backup configuration.
| Architecture | RTO | RPO |
|---|---|---|
| Single-node (development) | TODO | TODO |
| High-availability (production) | TODO | TODO |
Database Credential Rotation
Section titled “Database Credential Rotation”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.
Durable Storage
Section titled “Durable Storage”The Web, Job and Inference Adapter services need no durable storage for models: the adapter’s models and the platform’s address data are baked into their images, and nothing is downloaded at runtime. See Model data.
A self-hosted LLM caches its models locally; mounting that cache on durable storage speeds its restarts. It needs no backup — it can be repopulated.
Health Checks
Section titled “Health Checks”The Inference Adapter exposes unauthenticated /health and /ready on its TLS
listener; see Start-up and health.
Log Management
Section titled “Log Management”Enprivacy 3.0 emits structured JSON audit logs to stdout. These should be forwarded to your SIEM or log aggregation platform.
Upgrades
Section titled “Upgrades”See the Deployment Guide for upgrade procedures. A release that renames stored names deploys in a maintenance window instead of a rolling deploy; see Maintenance-Window Upgrades.