[SOLVED] upgraded to 9.7 and now remote sync jobs now fails with owner check failed

[flexyz]

Hi

My remote PBS server have all synched jobs added as owner "backup@pam" and have been synching for days. Now I think the upgrade to 9.7 makes it fail

owner check failed (root@pam != backup@pam)

How do I change the ownership on my remote PBS or should I change it on the source PBS?

Thanks

 

[flexyz]

All my previous sync jobs and repositories have "backup@pam" as owner, but I can't find any user/reference on the offsite pbs server?

 

[fabian]

we dropped the fake 'backup@pam' owner for sync jobs. you can now set an explicit owner in the sync job configuration, and change the owner of all already synced groups to that. the new default if none is set is 'root@pam'.

 

[flexyz]

Yes I tried that, but new sync failed because previous sync/owner is backup@pam - can I change that, so I don't have to sync the whole thing again?

 

[fabian]

Yes I tried that, but new sync failed because previous sync/owner is backup@pam - can I change that, so I don't have to sync the whole thing again?

yes. use the 'change owner' action in the datastore content view (it's the small 'person' icon in-between the 'V.' for Verify and 'scissors' for pruning), or proxmox-backup-client change-owner. if you feel up to the task, you can also change the contents of the groups' 'owner' file with sed/a script/... .

 

[flexyz]

great it works! thanks for a great product - when is it released from BETA aprox?

 

[flexyz]

FYI. btw. If I change the schedule on a job, there is an GUI error and have to "select" owner user from dropdown before it works

 

[fabian]

FYI. btw. If I change the schedule on a job, there is an GUI error and have to "select" owner user from dropdown before it works

yes, the GUI now enforces having an owner set.
edit: misread, see @t.lamprecht reply below

 

[t.lamprecht]

FYI. btw. If I change the schedule on a job, there is an GUI error and have to "select" owner user from dropdown before it works

That error in your screenshot was fixed in git, not yet publicly available as package though.

 

[dbayer]

Looking at the /backupPool/pbs/store it still has owner and group set to backup after changing the owner in the GUI. Should I go and manually change those on the file system?

Thanks,
Daniel

 

[t.lamprecht]

Looking at the /backupPool/pbs/store it still has owner and group set to backup after changing the owner in the GUI. Should I go and manually change those on the file system?

The file system owner is OK to be backup, and should not be changed (that will break things). It needs to be that user, as the lower privileged process managing the backup runs as that user.

The backup group owner, which is the owner as seen from the Proxmox Backup Server access control layer, is not related to the underlying (internal) file owner, and is saved as string in a file named "owner" in each backup group.

 

[crmspezi]

yes. use the 'change owner' action in the datastore content view (it's the small 'person' icon in-between the 'V.' for Verify and 'scissors' for pruning), or proxmox-backup-client change-owner. if you feel up to the task, you can also change the contents of the groups' 'owner' file with sed/a script/... .

Danke für die Antwort, hat mir auch geholfen.

 

[dbayer]

Thanks! Glad I didn't try changing this first.