Recent content by Haabda

I just realized I was looking at the Garbage Collection logs from before I rebuilt the datastore. It can't even do a garbage collection yet because it isn't finishing syncing my VMs. If possible, please delete this thread as it is completely invalid.

root@alcaeus:~# cat /etc/proxmox-backup/datastore.cfg datastore: Backups path /mnt/datastore/Backups root@alcaeus:~# ls -lhR /mnt/datastore/Backups/vm/105 ls: cannot access '/mnt/datastore/Backups/vm/105': No such file or directory

There is not a backup for VM105. So to me, the error message doesn't make any sense.

EDIT June 15, 2022 - I was looking at old logs. This is NOT an issue. Board admins, please delete this entire thread as it is completely invalid. I manually deleted chunks. Because I did that, I was unable to perform syncs. To fix that, I deleted my Datastore and recreated it. (See...

Thank you for the clue. I was able to resolve my issue by deleting the datastore and recreating it. root@alcaeus:/mnt/datastore/Backups/ct# proxmox-backup-manager datastore list ┌─────────┬────────────────────────┬─────────┐ │ name │ path │ comment │...

Yes, that is exactly what I did. I had let the drive run out of space and could not do garbage collection. I decided I wanted to start over so I deleted every file inside the .chunks directory.

Upgrading to 2.2 did not resolve my problem. However, the error messages are different. 2022-06-09T11:14:11-05:00: Starting datastore sync job 'Perseus:Backups:Backups::s-12c4c6ca-f307' 2022-06-09T11:14:11-05:00: sync datastore 'Backups' from 'Perseus/Backups' 2022-06-09T11:14:11-05:00: ----...

I see that 2.2 is out. I'll try upgrading to it and see if my problem is resolved.

On both servers, I am on PBS 2.0-4 and no updates show as available. I have also rebooted both PBS servers to be sure the newest kernel is loaded.

Can anyone help me with this? Syncs used to work but I neglected to have a Garbage Collection task on the receiving server so the drive filled up. I have deleted all synced backups, removed and added back the remotes, but still get these errors. 2022-06-09T09:57:16-05:00: Starting datastore...