# BLOB_BAK_PUT_F: Backup S3 PUT failed (R2 → Hetzner mirror)

- Module: BLOB. Blob storage replication R2 → Hetzner (scout sync-blob-backup)
- Severity: Warning
- Impact: No impact. Bookkeeping only. Nobody is affected.
- Retry: Automatic. The platform retries or self-heals on its own.
- Reference: https://docs.bizkithub.com/en/system-codes/BLOB_BAK_PUT_F

## What happened

Scout's `sync-blob-backup` worker could not copy a blob from the primary R2 bucket into the Hetzner backup bucket. The row keeps `backup_date NULL` and is retried on the next 1-min tick. Investigate backup credentials, endpoint reachability, bucket quota, or the specific object (missing on primary?).

## Likely causes

- Copying a stored file to the backup bucket failed because the backup storage was unreachable or rejected the upload.
- The original file is missing in primary storage.

## How to resolve

1. No customer action is needed; the copy is retried automatically.
2. If the same file keeps failing, BizKitHub operations will check whether it still exists in primary storage.

## Related codes

- BLOB_BAK_CRASH: File backup worker crashed mid-run
- BLOB_BAK_NOENV: Blob backup worker ran without backup credentials