[SOLVED] backups cannot be synchronized to the remote

D

Dataaja95

New Member
Jan 10, 2024
15
0
1
I have two proxmox backup servers, the first localbackup and the second offsite, on which I have configured localbackup for remote synchronization, so my purpose is to synchronize the backups of the localbackup server to that offsite server. the user remotesync, which logs into the localbackup server during synchronization, has the rights datastorereader, and the user on the offsite server has the rights datastorebackup. However, when I start the synchronization, I get such an error message in the logs, as I understand it
everything should be configured correctly which could cause this error message

2024-02-26T10:14:50+02:00: Starting datastore sync job 'localbackup:localbackup:offsite::pbs-localbackup'
2024-02-26T10:14:50+02:00: sync datastore 'offsite' from 'localbackup/localbackup'
2024-02-26T10:14:50+02:00: ----
2024-02-26T10:14:50+02:00: Syncing datastore 'localbackup', root namespace into datastore 'offsite', root namespace
2024-02-26T10:14:50+02:00: found 0 groups to sync (out of 0 total)
2024-02-26T10:14:50+02:00: Finished syncing namespace , current progress: 0 groups, 0 snapshots
2024-02-26T10:14:50+02:00: ----
2024-02-26T10:14:50+02:00: Syncing datastore 'localbackup', namespace 'localbackup' into datastore 'offsite', namespace 'localbackup'
2024-02-26T10:14:50+02:00: found 46 groups to sync (out of 46 total)
2024-02-26T10:14:50+02:00: sync snapshot vm/100/2023-08-31T18:00:01Z
2024-02-26T10:14:50+02:00: sync archive qemu-server.conf.blob
2024-02-26T10:14:50+02:00: sync archive drive-virtio0.img.fidx
2024-02-26T10:14:50+02:00: percentage done: 0.08% (0/46 groups, 1/26 snapshots in group #1)
2024-02-26T10:14:50+02:00: sync group vm/100 failed - inserting chunk on store 'offsite' failed for bb9f8df61474d25e71fa00722318cd387396ca1736605e1248821cc0de3d3af8 - mkstemp "/offsite/.chunks/bb9f/bb9f8df61474d25e71fa00722318cd387396ca1736605e1248821cc0de3d3af8.tmp_XXXXXX" failed: ENOENT: No such file or directory
2024-02-26T10:14:50+02:00: sync snapshot vm/101/2023-08-31T18:00:24Z
2024-02-26T10:14:50+02:00: sync archive qemu-server.conf.blob
2024-02-26T10:14:50+02:00: sync archive drive-virtio0.img.fidx
2024-02-26T10:14:50+02:00: percentage done: 2.26% (1/46 groups, 1/26 snapshots in group #2)
2024-02-26T10:14:50+02:00: sync group vm/101 failed - inserting chunk on store 'offsite' failed for 8374a1b285963e5e46dbec86b18890a8c94fb7f5adad26dc54cb786e07fbc75c - mkstemp "/offsite/.chunks/8374/8374a1b285963e5e46dbec86b18890a8c94fb7f5adad26dc54cb786e07fbc75c.tmp_XXXXXX" failed: ENOENT: No such file or directory
2024-02-26T10:14:50+02:00: sync snapshot vm/102/2023-08-31T18:00:28Z
2024-02-26T10:14:50+02:00: sync archive qemu-server.conf.blob
2024-02-26T10:14:50+02:00: sync archive drive-virtio0.img.fidx
2024-02-26T10:14:50+02:00: percentage done: 4.43% (2/46 groups, 1/26 snapshots in group #3)
2024-02-26T10:14:50+02:00: sync group vm/102 failed - inserting chunk on store 'offsite' failed for bb9f8df61474d25e71fa00722318cd387396ca1736605e1248821cc0de3d3af8 - mkstemp "/offsite/.chunks/bb9f/bb9f8df61474d25e71fa00722318cd387396ca1736605e1248821cc0de3d3af8.tmp_XXXXXX" failed: ENOENT: No such file or directory
2024-02-26T10:14:50+02:00: sync snapshot vm/103/2023-08-31T18:00:34Z
2024-02-26T10:14:50+02:00: sync archive qemu-server.conf.blob
2024-02-26T10:14:50+02:00: sync archive drive-virtio0.img.fidx
2024-02-26T10:14:50+02:00: percentage done: 6.61% (3/46 groups, 1/26 snapshots in group #4)
2024-02-26T10:14:50+02:00: sync group vm/103 failed - inserting chunk on store 'offsite' failed for 8374a1b285963e5e46dbec86b18890a8c94fb7f5adad26dc54cb786e07fbc75c - mkstemp "/offsite/.chunks/8374/8374a1b285963e5e46dbec86b18890a8c94fb7f5adad26dc54cb786e07fbc75c.tmp_XXXXXX" failed: ENOENT: No such file or directory
2024-02-26T10:14:50+02:00: sync snapshot vm/104/2023-08-31T18:00:37Z
2024-02-26T10:14:50+02:00: sync archive qemu-server.conf.blob
2024-02-26T10:14:50+02:00: sync archive drive-virtio0.img.fidx
2024-02-26T10:14:50+02:00: percentage done: 8.78% (4/46 groups, 1/26 snapshots in group #5)
2024-02-26T10:14:50+02:00: sync group vm/104 failed - inserting chunk on store 'offsite' failed for bb9f8df61474d25e71fa00722318cd387396ca1736605e1248821cc0de3d3af8 - mkstemp "/offsite/.chunks/bb9f/bb9f8df61474d25e71fa00722318cd387396ca1736605e1248821cc0de3d3af8.tmp_XXXXXX" failed: ENOENT: No such file or directory
2024-02-26T10:14:50+02:00: sync snapshot vm/105/2023-08-31T18:00:41Z
2024-02-26T10:14:50+02:00: sync archive qemu-server.conf.blob
2024-02-26T10:14:50+02:00: sync archive drive-virtio0.img.fidx
2024-02-26T10:14:51+02:00: percentage done: 10.95% (5/46 groups, 1/26 snapshots in group #6)
2024-02-26T10:14:51+02:00: sync group vm/105 failed - inserting chunk on store 'offsite' failed for 8374a1b285963e5e46dbec86b18890a8c94fb7f5adad26dc54cb786e07fbc75c - mkstemp "/offsite/.chunks/8374/8374a1b285963e5e46dbec86b18890a8c94fb7f5adad26dc54cb786e07fbc75c.tmp_XXXXXX" failed: ENOENT: No such file or directory
2024-02-26T10:14:51+02:00: sync snapshot vm/106/2023-08-31T18:00:44Z
2024-02-26T10:14:51+02:00: sync archive qemu-server.conf.blob
2024-02-26T10:14:51+02:00: sync archive drive-virtio0.img.fidx
2024-02-26T10:14:51+02:00: percentage done: 13.13% (6/46 groups, 1/26 snapshots in group #7)
2024-02-26T10:14:51+02:00: sync group vm/106 failed - inserting chunk on store 'offsite' failed for bb9f8df61474d25e71fa00722318cd387396ca1736605e1248821cc0de3d3af8 - mkstemp "/offsite/.chunks/bb9f/bb9f8df61474d25e71fa00722318cd387396ca1736605e1248821cc0de3d3af8.tmp_XXXXXX" failed: ENOENT: No such file or directory
2024-02-26T10:14:51+02:00: sync snapshot vm/107/2023-08-31T18:00:48Z
2024-02-26T10:14:51+02:00: sync archive qemu-server.conf.blob
2024-02-26T10:14:51+02:00: sync archive drive-virtio0.img.fidx
 
This:
Dataaja95 said:
2024-02-26T10:14:51+02:00: sync group vm/106 failed - inserting chunk on store 'offsite' failed for bb9f8df61474d25e71fa00722318cd387396ca1736605e1248821cc0de3d3af8 - mkstemp "/offsite/.chunks/bb9f/bb9f8df61474d25e71fa00722318cd387396ca1736605e1248821cc0de3d3af8.tmp_XXXXXX" failed: ENOENT: No such file or directory
Click to expand...

make me think that the datastore in the offsite PBS isn't configured properly.

What's the output for proxmox-backup-manager datastore list in the offsite PBS?
Does the directory /offsite exists an has write permissions for user "backup"?
 
VictorSTS said:
This:


make me think that the datastore in the offsite PBS isn't configured properly.

What's the output for proxmox-backup-manager datastore list in the offsite PBS?
Does the directory /offsite exists an has write permissions for user "backup"?
Click to expand...
proxmox-backup-manager datastore list name path comment
offsite /offsite
folder rights are as follows
total 4
drwxr-xr-x 3 backup backup 4096 Feb 26 10:43 ns
 
If I change the remotesync user on the localbackup server to datastorepoweruse, the synchronization seems to go through, but nothing
back up
2024-02-26T11:04:15+02:00: Starting datastore sync job 'localbackup:localbackup:offsite::pbs-localbackup'
2024-02-26T11:04:15+02:00: sync datastore 'offsite' from 'localbackup/localbackup'
2024-02-26T11:04:16+02:00: ----
2024-02-26T11:04:16+02:00: Syncing datastore 'localbackup', root namespace into datastore 'offsite', root namespace
2024-02-26T11:04:16+02:00: found 0 groups to sync (out of 0 total)
2024-02-26T11:04:16+02:00: Finished syncing namespace , current progress: 0 groups, 0 snapshots
2024-02-26T11:04:16+02:00: ----
2024-02-26T11:04:16+02:00: Syncing datastore 'localbackup', namespace 'localbackup' into datastore 'offsite', namespace 'localbackup'
2024-02-26T11:04:16+02:00: found 0 groups to sync (out of 0 total)
2024-02-26T11:04:16+02:00: Finished syncing namespace localbackup, current progress: 0 groups, 0 snapshots
2024-02-26T11:04:16+02:00: sync job 'localbackup:localbackup:offsite::pbs-localbackup' end
2024-02-26T11:04:16+02:00: TASK OK
 
That datastore is not ok. You are missing the .chunks directory that is created when you provision the datastore. Should look like this:

Code: 
drwxr-xr-x     4 backup backup     6 Feb 25 14:15 .
drwxr-xr-x     6 root   root       6 Dec  4 17:43 ..
drwxr-x--- 65538 backup backup 65538 Mar  2  2023 .chunks
-rw-r--r--     1 backup backup   348 Feb 25 14:15 .gc-status
-rw-r--r--     1 backup backup     0 Mar  2  2023 .lock
drwxr-xr-x     3 backup backup     3 Mar  2  2023 ns

Recreate the datastore from PBS on the /offsite directory.
 
  • Like
Reactions: Dataaja95
VictorSTS said:
That datastore is not ok. You are missing the .chunks directory that is created when you provision the datastore. Should look like this:

Code: 
drwxr-xr-x     4 backup backup     6 Feb 25 14:15 .
drwxr-xr-x     6 root   root       6 Dec  4 17:43 ..
drwxr-x--- 65538 backup backup 65538 Mar  2  2023 .chunks
-rw-r--r--     1 backup backup   348 Feb 25 14:15 .gc-status
-rw-r--r--     1 backup backup     0 Mar  2  2023 .lock
drwxr-xr-x     3 backup backup     3 Mar  2  2023 ns

Recreate the datastore from PBS on the /offsite directory.
Click to expand...
Thanks, this solved the problem.
 
Dataaja95 said:
Merci, cela a résolu le problème.
Click to expand...
j'ai le même problème que vous, dites-nous si votre problème à été résolu. et soyez plus clair.

dans le processus que vous utilisez pour régler le problème.

je vous envoie la sorti de ls -la de ma datastore, apparemment le dossier .chunks existe belle et bien.
 
VictorSTS said:
Je ne sais pas si je vous comprends bien (je ne parle pas français, désolé), mais effectuez une vérification complète de cette banque de données. Peut-être que vous avez le .chunksrépertoire mais qu'il manque certaines données à l'intérieur.
Click to expand...
 
Merci @VictorSTS j'ai pu regler mon problème, éffectivement, il y avait dans mon repertoire .chunks certaines données manquantes au bon fonctionnement de mes backups. j'ai dû supprimer totalement avec la commande: "proxmox-backup manager datastore remove' name of backup' puis le recreer à nouveau en affectant les differents droits, groupe et proprietaire au repertoire '.chunks' et 'new backup'. Thinks you very much.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom