errors in 0.30.0

[Str1atum]

Did a fresh install even, but still these errors in my log all the time. Even cleaned up all backup directories.
Local + rclone remote, files are written fine in a backup run.

[WARNING] Cloud storage: retention ignored 2 backup(s) that do not belong to pve (other hosts, or no readable manifest) (count: 1)
Example: Cloud storage: retention ignored 2 backup(s) that do not belong to pve (other hosts, or no readable manifest)

• [WARNING] Local storage: retention ignored 5 backup(s) that do not belong to pve (other hosts, or no readable manifest) (count: 1)
  Example: Local storage: retention ignored 5 backup(s) that do not belong to pve (other hosts, or no readable manifest)

[Str1atum]

Cause

The archives are written by 0.30.0 itself, and their metadata records the FQDN:
"hostname": "pve.home.arpa"
while the ownership check compares against the short name "pve".
Filenames carry the FQDN prefix too (pve.home.arpa-backup-.tar.xz.bundle.tar),
so the writing path resolves the FQDN while the retention path uses the short
hostname. Both names are correct for this host; they simply never match.

Expected

Ownership comparison should normalise both sides (e.g. compare the short name,
or accept an FQDN whose first label equals the local hostname).

[tis24dev]

@Str1atum Thanks, you were right, it's a real bug in 0.30.0.

ProxSave reads the machine name one way when writing a backup (full name, pve.home.arpa) and another way when checking ownership during cleanup (short name, pve). They never match, so every backup looks foreign.

Your backups are fine nothing lost, nothing wrongly deleted. But automatic cleanup is currently doing nothing, so the folders will grow past your limits.

Can you paste the output of these? Just to confirm it on your machine:

hostname
hostname -f
ls /path/to/your/backup/dir

Fix on the way.

[Str1atum]

hostname
pve

hostname -f
pve.home.arpa

ls
pve.home.arpa-backup-20260825-192531.tar.xz.bundle.tar

[hspindel]

Same issue here.

hostname: synopbs
hostname -f: synopbs.sci1.com

Is /mnt/synopbs/backup
synopbs.sci1.com-backup-20260807-020002.tar.xz.bundle.tar synopbs.sci1.com-backup-20260819-020003.tar.xz.bundle.tar
synopbs.sci1.com-backup-20260807-181034.tar.xz.bundle.tar synopbs.sci1.com-backup-20260820-020003.tar.xz.bundle.tar
synopbs.sci1.com-backup-20260808-020001.tar.xz.bundle.tar synopbs.sci1.com-backup-20260821-020002.tar.xz.bundle.tar
synopbs.sci1.com-backup-20260809-020003.tar.xz.bundle.tar synopbs.sci1.com-backup-20260822-020001.tar.xz.bundle.tar
synopbs.sci1.com-backup-20260810-020002.tar.xz.bundle.tar synopbs.sci1.com-backup-20260823-020001.tar.xz.bundle.tar
synopbs.sci1.com-backup-20260816-020001.tar.xz.bundle.tar synopbs.sci1.com-backup-20260824-020002.tar.xz.bundle.tar
synopbs.sci1.com-backup-20260817-020003.tar.xz.bundle.tar synopbs.sci1.com-backup-20260825-020006.tar.xz.bundle.tar
synopbs.sci1.com-backup-20260818-020001.tar.xz.bundle.tar synopbs.sci1.com-backup-20260825-172052.tar.xz.bundle.tar

(Note that the backup target is a networked drive.)

[tis24dev]

Hi, @hspindel
@Str1atum I'm working on the fix right now; I hope to release it by tomorrow.

[tis24dev]

Hi! Please update to v0.31.0 and give me some feedback.

[tis24dev]

plase here #293