A backup copy failed
Weik.io 2026.2The newest backup was taken but its copy to the place in the settings, such as an S3 bucket, failed, and the archive exists 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 was taken, but copying it to the place the settings name, such as an S3 bucket, failed. The archive is kept only on the server that took it, so losing that server loses the backup too.
What raises it#
The installation’s settings name a backupCopyTo and the copy of the newest backup that tried one failed. The detail gives the archive kept on the server, the copy’s error and the settings to check, the bucket’s lines in the stack’s .env or the rclone remote.
What to check#
See where the backups are copied:
$ 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 what the error names, such as an expired access key, a bucket that doesn’t exist or a network rule that blocks the hub. The service copies the next backup again, and you can copy the archive the detail names by hand in the meantime. To keep the archives only on the server, turn the copy off:
$ weikio settings set --no-backup-copy