Open
System > Backups from the admin menu. This page shows existing backups, lets you create a manual backup and controls the scheduled backup settings. Scheduled backup runs are visible in Tasks.Every DCIM backup is a full installation backup. It includes the database dump, runtime configuration, license files and backup metadata. Partial backup selection is not supported.
Create a manual backup
Use the create action in the Backups page when you want an immediate restore point. This is useful after first setup, before large imports, before changing backup storage, or before planned maintenance.
The backup is created using the currently selected target. If the target is
LOCAL, the archive is stored on the DCIM server. If the target is R2, DCIM prepares the archive locally and uploads it to the configured bucket.Backup settings
Status
Use
DISABLED when you do not want scheduled backups to run. Use ENABLED after the target, frequency and retention are correct.Target
LOCAL stores backup archives on the DCIM host under /opt/dcim/backups.R2 uploads backup archives to a Cloudflare R2 bucket. Use this when you want backups stored outside the DCIM server.Frequency
Frequency uses five-field cron syntax. For example,
0 3 * * * runs once per day at 03:00.Choose a time when the platform is normally quiet. Backups are full archives, so avoid scheduling them during heavy imports or maintenance windows.
Keep
This is the number of successful backups to keep for the active target. The oldest successful backups are removed when retention is applied.
The value must be between
1 and 365. The default is 10.Cloudflare R2
These fields are only used when the backup target is
R2. R2 credentials are stored as secrets; after they are saved, leave the credential fields empty to keep the current values.Endpoint
Use the S3-compatible R2 endpoint, for example
https://account-id.r2.cloudflarestorage.com.Bucket
Enter the bucket name where DCIM should upload backup archives.
Region
For Cloudflare R2 this is normally
auto.Prefix
Prefix is the folder-style path used inside the bucket. The default is
dcim. Use a different prefix if the same bucket stores backups for multiple environments.Access Key ID
Enter the R2 S3-compatible access key ID. Do not use a general Cloudflare dashboard API token here.
Secret Access Key
Enter the R2 S3-compatible secret access key. If a secret is already saved, leave this field empty to keep the current secret.
Backup list
The backup table shows the target, status, archive size, installed version, checksum and creation time. Completed backups can be downloaded. Backups that are still creating cannot be deleted until the task finishes.
A failed backup remains visible with an error message so you can understand what needs to be fixed before the next run.
Restore from a backup
Restore is performed from the server, not from the dashboard. Download the full backup archive first, copy it to the DCIM host if needed, then run:
dcimctl restore /path/to/dcim-backup.tar.gzThe restore command validates the archive before changing the installation. It then creates a safety copy, restores runtime files and license files, restores the database, runs migrations and starts DCIM again.
Cross-domain restore is not supported. R2 direct restore is also not supported: download the archive first, then run the restore command on the host.
Backup video
