Hi,
One of my Proxmox Backup Client systems has recently started generating errors when backing up - along the lines of -
Error downloading .didx from previous manifest: unable to read dynmamic index 'data00.pxar.didx' - Invalid argument (os error 22)
I know for a fact that the syntax is correct as the same syntax i use (detail below) i use on my other PBS Client systems too.
If i do a `journalctl -f` during a test backup, on PBS, i see nothing out of the ordinary either -
Equally, I dont see anything in syslog or elseware that would point to an issue, but to start with, what is error 22?
Right now, I'm thinking its maybe a red-herring and a client side error, but it does appear to be stopping backups from completing (the above script is ran on a cron schedule).
Anyone got any ideas?
Thanks!
One of my Proxmox Backup Client systems has recently started generating errors when backing up - along the lines of -
Error downloading .didx from previous manifest: unable to read dynmamic index 'data00.pxar.didx' - Invalid argument (os error 22)
I know for a fact that the syntax is correct as the same syntax i use (detail below) i use on my other PBS Client systems too.
Bash:
# env variables
export PBS_REPOSITORY="user@pbs!token-name@backup-server.com:datastore"
export PBS_PASSWORD="123456789"
# Backup
proxmox-backup-client backup --skip-lost-and-found true data00.pxar:/data/
If i do a `journalctl -f` during a test backup, on PBS, i see nothing out of the ordinary either -
Code:
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: starting new backup on datastore 'datastore' from ::ffff:1.2.3.4: "host/client-01/2024-04-08T15:42:10Z"
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: protocol upgrade done
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: GET /previous_backup_time
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: GET /previous
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: download 'index.json.blob' from previous backup.
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: GET /previous
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: POST /dynamic_index
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: register chunks in 'client-01-data-00.pxar.didx' from previous backup.
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: created new dynamic index 1 ("host/client-01/2024-04-08T15:42:10Z/catalog.pcat1.didx")
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: download 'client-01-data-00.pxar.didx' from previous backup.
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: POST /dynamic_index
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: created new dynamic index 2 ("host/client-01/2024-04-08T15:42:10Z/client-01-data-00.pxar.didx")
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: POST /dynamic_chunk
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: upload_chunk done: 3694 bytes, d79f0fa0f9351b3098aa344263a403bce551971277817571644ac4b88ff3cc9a
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: PUT /dynamic_index
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: dynamic_append 1 chunks
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: successfully added chunk d79f0fa0f9351b3098aa344263a403bce551971277817571644ac4b88ff3cc9a to dynamic index 2 (offset 0, size 36
94)
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: POST /dynamic_close
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: Upload statistics for 'client-01-data-00.pxar.didx'
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: UUID: 123abc
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: Checksum: 456xyz
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: Size: 3694
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: Chunk count: 1
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: Upload size: 3694 (100%)
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: Compression: 30%
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: successfully closed dynamic index 2
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: POST /dynamic_chunk
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: upload_chunk done: 127 bytes, 99d415c795f1194274d8429c71db12049be8263b12463d484bfcaac0e1d66f12
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: PUT /dynamic_index
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: dynamic_append 1 chunks
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: successfully added chunk 99d415c795f1194274d8429c71db12049be8263b12463d484bfcaac0e1d66f12 to dynamic index 1 (offset 0, size 12
7)
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: POST /dynamic_close
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: Upload statistics for 'catalog.pcat1.didx'
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: UUID: 123abc
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: Checksum: 456xyz
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: Size: 127
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: Chunk count: 1
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: Upload size: 127 (100%)
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: Duplicates: 0+1 (100%)
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: Compression: 108%
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: successfully closed dynamic index 1
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: POST /blob
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: add blob "/mnt/datastore/datastore/host/client-01/2024-04-08T15:42:10Z/index.json.blob" (322 bytes, comp: 322)
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: POST /finish
Apr 08 11:42:10 backup-01 proxmox-backup-[845]: backup-01 proxmox-backup-proxy[845]: syncing filesystem
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: successfully finished backup
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: backup finished successfully
Apr 08 11:42:10 backup-01 proxmox-backup-proxy[845]: TASK OK
Equally, I dont see anything in syslog or elseware that would point to an issue, but to start with, what is error 22?
Right now, I'm thinking its maybe a red-herring and a client side error, but it does appear to be stopping backups from completing (the above script is ran on a cron schedule).
Anyone got any ideas?
Thanks!