[SOLVED] remote sync using usb restore to start with Fail. try again later

[RobFantini]

at the remote sync results in this error:

2020-07-16T13:12:00-04:00: Starting datastore sync job 'get-LtBackups'
2020-07-16T13:12:00-04:00: task triggered by schedule '13:12'
2020-07-16T13:12:00-04:00: Sync datastore 'LtBackups' from 'pbs/LtBackups'
2020-07-16T13:12:00-04:00: sync group ct/121 failed - owner check failed (backup@pam != pbs-user@pbs)
2020-07-16T13:12:00-04:00: sync group vm/10784 failed - owner check failed (backup@pam != pbs-user@pbs)
2020-07-16T13:12:00-04:00: TASK ERROR: sync failed with some errors.

backup@pam is not in any of our configuration at remote or local pbs per grep backup@pam /etc/proxmox-backup/*

any suggestions are welcome

 

[RobFantini]

more info . at the remote system:

cat remote.cfg
remote: pbs
        fingerprint xx
        host pbs.ourdomain.com
        password xx
        userid pbs-user@pbs

cat sync.cfg
sync: get-LtBackups
        comment get long term backups
        remote pbs
        remote-store LtBackups
        remove-vanished true
        schedule 13:12
        store LtBackups

 

[RobFantini]

and acl.cfg on both local and remote:

acl:1:/datastore/LtBackups:pbs-user@pbs:Admin

 

[RobFantini]

proxmox-backup-manager remote list :
┌──────┬───────────────────────┬──────────────┬─────────────────────────────────────────────────────────────────────────────────────────
│ name │ host                  │ userid       │ fingerprint                                                                           
╞══════╪═══════════════════════╪══════════════╪═════════════════════════════════════════════════════════════════════════════════════════
│ pbs  │ pbs.ourdomain.com     │ pbs-user@pbs │ ....
└──────┴───────────────────────┴──────────────┴─────────────────────────────────────────────────────────────────────────────────────────
proxmox-backup-manager sync-job list :
┌───────────────┬───────────┬────────┬──────────────┬──────────┬───────────────────────┐
│ id            │ store     │ remote │ remote-store │ schedule │ comment               │
╞═══════════════╪═══════════╪════════╪══════════════╪══════════╪═══════════════════════╡
│ get-LtBackups │ LtBackups │ pbs    │ LtBackups    │ 13:12    │ get long term backups │
└───────────────┴───────────┴────────┴──────────────┴──────────┴───────────────────────┘

 

[fabian]

what does the 'owner' file contain on both ends for the backups that are not syncable?

 

[fabian]

are you syncing into an existing datastore that has backups? note that sync direction is pull, not push!

 

[RobFantini]

what does the 'owner' file contain on both ends for the backups that are not syncable?

at both source and destination the owner = pbs-user@pbs

 

[RobFantini]

are you syncing into an existing datastore that has backups? note that sync direction is pull, not push!

I am pulling.

Note the node host that is doing the pull -
the data store was
1- created
2- had a rsync transfer from USB
3- then tried to sync

 

[RobFantini]

on the pull side, this test works:
1- create a new datastore named test
2- sync to test

2020-07-17T08:04:00-04:00: Starting datastore sync job 'get-LtBackups'
2020-07-17T08:04:00-04:00: task triggered by schedule '08:04'
2020-07-17T08:04:00-04:00: Sync datastore 'test' from 'pbs/LtBackups'
2020-07-17T08:04:00-04:00: sync snapshot "ct/121/2020-07-13T20:33:15Z"
2020-07-17T08:04:00-04:00: sync archive pct.conf.blob
2020-07-17T08:04:00-04:00: sync archive root.pxar.didx
2020-07-17T08:39:00-04:00: sync archive catalog.pcat1.didx
2020-07-17T08:39:00-04:00: got backup log file "client.log.blob"
2020-07-17T08:39:00-04:00: sync snapshot "ct/121/2020-07-13T20:33:15Z" done
2020-07-17T08:39:00-04:00: sync snapshot "vm/10784/2020-07-13T12:43:02Z"
2020-07-17T08:39:00-04:00: sync archive qemu-server.conf.blob
2020-07-17T08:39:00-04:00: sync archive drive-ide0.img.fidx
2020-07-17T09:16:11-04:00: got backup log file "client.log.blob"
2020-07-17T09:16:11-04:00: sync snapshot "vm/10784/2020-07-13T12:43:02Z" done
2020-07-17T09:16:11-04:00: TASK OK
/CODE]

so the issue is caused by doing an initial sync using usb.

 

[RobFantini]

i am still working on this - will post more info after the current very long sync.

 

[RobFantini]

what is strange is that some syncs work and others do not.

as a reminder the initial sync was done using rsync and a usb drive

i am still debugging .

2020-07-18T08:44:00-04:00: sync group ct/113 failed - owner check failed (backup@pam != pbs-user@pbs)
2020-07-18T08:44:00-04:00: re-sync snapshot "ct/121/2020-07-16T04:01:12Z"
2020-07-18T08:44:00-04:00: no data changes
2020-07-18T08:44:00-04:00: re-sync snapshot "ct/121/2020-07-16T04:01:12Z" done
2020-07-18T08:44:00-04:00: sync group ct/122 failed - owner check failed (backup@pam != pbs-user@pbs)
2020-07-18T08:44:00-04:00: sync group ct/126 failed - owner check failed (backup@pam != pbs-user@pbs)
2020-07-18T08:44:00-04:00: sync group ct/128 failed - owner check failed (backup@pam != pbs-user@pbs)
2020-07-18T08:44:00-04:00: sync group ct/160 failed - owner check failed (backup@pam != pbs-user@pbs)
2020-07-18T08:44:00-04:00: re-sync snapshot "ct/602/2020-07-16T04:10:31Z"
2020-07-18T08:44:00-04:00: no data changes
2020-07-18T08:44:00-04:00: re-sync snapshot "ct/602/2020-07-16T04:10:31Z" done
2020-07-18T08:44:00-04:00: sync group ct/603 failed - owner check failed (backup@pam != pbs-user@pbs)
2020-07-18T08:44:00-04:00: sync group ct/604 failed - owner check failed (backup@pam != pbs-user@pbs)
2020-07-18T08:44:00-04:00: re-sync snapshot "ct/605/2020-07-17T05:41:23Z"
2020-07-18T08:44:00-04:00: no data changes
2020-07-18T08:44:00-04:00: re-sync snapshot "ct/605/2020-07-17T05:41:23Z" done
2020-07-18T08:44:00-04:00: sync group ct/606 failed - owner check failed (backup@pam != pbs-user@pbs)

 

[RobFantini]

I gave up on trying to use the rsync from usb datastore. as it was not done properly.


so instead just I am just using sync to a new datastore. that will take awhils on our 1G LAN , however should work.

on the next remote i think this would work with fewer issues:
1- create data store
2- restore usb to the data store.