Skip to content

Backup Configuration

Web.Casa uses Kopia as its backup engine. All backup data is password-encrypted and stored to the target of your choice. This page covers storage setup, scheduling, and retention policies.

Kopia CLI must be installed on the server. If it is not already present, Web.Casa can auto-install it directly from the panel.

See the Kopia Backend page for details on installation and the underlying engine.

Web.Casa supports four storage target types:

TargetUse Case
Local FilesystemBackup to another disk, partition, or mounted drive on the server
S3 / MinIOCloud object storage (Amazon S3, MinIO, Backblaze B2, Wasabi, etc.)
WebDAVNetwork storage via Nextcloud, NAS devices, or any WebDAV server
SFTPRemote server over SSH
  • Endpoint URL — S3-compatible API endpoint
  • Bucket name — target bucket
  • Access key and Secret key — API credentials
  • Region (optional)
  • Host and Port — remote server address
  • Username — SSH login user
  • Authentication — password or path to SSH private key
  • Remote path — directory on the remote server for backup storage
  • URL — full WebDAV endpoint
  • Username and Password
  • Path — absolute directory path on the server

All backup data is encrypted with a repository password set during initial configuration.

This password is the only way to decrypt your backups. Store it in a separate, secure location. If lost, backup data cannot be recovered.

Choose what data to include in each backup:

ScopeWhat It Backs Up
PanelWeb.Casa database and Caddyfile configuration
Docker VolumesAll Docker volumes managed by Web.Casa
Database DumpsSQL dumps from all database instances

You can enable one or more scopes per backup configuration.

Backups are scheduled using cron expressions. The panel provides presets for common schedules:

PresetCron ExpressionDescription
Daily at 2:00 AM0 2 * * *Every day at 02:00
Daily at 4:00 AM0 4 * * *Every day at 04:00
Weekly Sunday 3:00 AM0 3 * * 0Every Sunday at 03:00

You can also enter a custom cron expression for any other schedule.

Control how many snapshots to keep and for how long:

SettingDescription
Keep latest N snapshotsAlways retain the N most recent snapshots
Keep N daysRetain snapshots created within the last N days

A sensible starting point: keep the latest 10 snapshots and retain for 30 days.

The backup dashboard displays the current state of each backup configuration:

  • Status — Idle or Running
  • Last backup — timestamp of the most recent completed backup
  • Next scheduled — when the next backup will run

You can trigger a manual backup at any time using the Run Now button.