A backup copy failed
Weik.io 2026.2Weik.io couldn't copy the newest backup to the destination in the installation's settings, such as an S3 bucket. The archive is only on the server that took it.
| Kind | Severity | Who sees it |
|---|---|---|
backup- |
Error | Platform administrators, in a list that isn’t narrowed to an environment or a project |
What it means#
The newest backup is only on the server that took it. If you lose that server, you lose the backup too.
What raises it#
The newest copy to the backupCopyTo in the installation’s settings failed. In the problem’s detail you see the copy’s error and which archive is on the server. The detail also shows which settings to check, either the storage address and the RCLONE_S3_* lines of the hub stack’s .env, or the rclone remote.
What to check#
See where Weik.io copies the backups:
$ weikio settings getOn a hub server, in the stack’s folder, read the backup service’s log:
$ docker compose logs backupHow to fix it#
Fix the cause in the copy’s error. For an s3:// destination, check the storage address and the RCLONE_S3_* lines of the hub stack’s .env. For another rclone remote, check its RCLONE_CONFIG_* variables in the backup service.
The backup service tries the copy again with the next backup. Until then, you can copy by hand the archive shown in the problem’s detail. To keep the archives only on the server, turn the copy off:
$ weikio settings set --no-backup-copy