Backup concept of a Q.wiki Now! System

Chosen Strategy

We rely on the 3-2-1 backup concept. This means:

• At least 3 copies of data
• At least 2 different storage media
• At least 1 physically external location

Backed Up Data

Backups include the entire database (processes, users, tenants, etc.) and all attachments (files) from Q.wiki.

The search index (Solr) is not backed up because it is transient and can be restored by reindexing if needed.

Implementing the Backup Strategy

Database and attachments are backed up separately. All backups are retained for 3 months.

The 3-2-1 strategy is implemented for both data categories as follows:

Database (PostgreSQL)

The 3-2-1 strategy is already met indirectly through the use of our S3 cluster as a backup target (see section "S3 Storage Used").

Implementation

• Disk (PVC – PersistentVolumeClaim)
  • Data is continuously persisted on a multi-zone, non-volatile storage.
  • Achieved: additional data copy
• WAL Archive (Write Ahead Logs)
  • WAL archives are continuously written to both the disk (PVC) and our S3 bucket (offsite).
  • Achieved: additional data copy · additional medium (S3) · additional location (RXAC, Relaix Aachen)
• Physical Base Backup
  • Every second night, a complete copy of the database is created and stored in our S3 bucket (offsite). This base backup serves as the starting point for recovery from WAL archives.
  • Achieved: additional data copy · additional medium (S3) · additional location (RXAC, Relaix Aachen)
• Nightly Bucket Replication
  • S3 buckets are copied to a GCS bucket once per night.
  • Achieved: additional data copy · additional medium (GCS – Google Cloud Storage) · additional location (Google, Frankfurt)

Summary

Attachments (S3 Bucket)

Attachments are backed up according to the 3-2-1 strategy as they are persisted in our S3 cluster (see section "S3 Storage Used").

S3 Storage Used

By using our S3 cluster, all data stored there automatically complies with the 3-2-1 backup rule.

Implementation

• S3 File Storage
  • Data is persisted on non-volatile storage.
  • Achieved: additional data copy · additional medium (NVMe – Non-Volatile Memory Express)
• S3 Bucket Replication
  • Every night, S3 buckets are transferred to an additional external S3 bucket. Applicable data processing agreements (DPA) are taken into account.
  • Achieved: additional data copy · additional medium (external S3) · additional location
• S3 Cluster Replication
  • Our S3 cluster is continuously replicated to another fire compartment.
  • Achieved: additional data copy · additional location (RXAC, Fire compartment 2)

Summary