From: Uwe Sauter <uwe.sauter.de@gmail.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: PBS: unable to create pull sync job
Date: Wed, 25 Feb 2026 12:23:33 +0100 [thread overview]
Message-ID: <51bd4380-15f7-4aa8-834e-70aa509a3823@gmail.com> (raw)
Dear all,
as there is no separate list for the Proxmox Backup Server I hope to find some help here.
TL;DR: On the pulling server, I cannot see the datastore that is the source for the job. Permissions?
Situation:
I have two servers named corvus and cygnus.
corvus:
- corvus is the main backup server where my PVE cluster puts the daily backups.
- The datastore has different namespaces for daily and weekly backups.
- There are two additional users configured, one for the PVE cluster (pve@pbs), the other one for
cygnus (cygnus@pbs). Both are managed by the Proxmox Backup authentication server.
- cygnus@pbs has the RemoteSyncOperator permissions on the corvus datastore.
cygnus:
- Shall pull the weekly backups for long term storage.
- Datastore has currently no namespaces yet.
- Has no additional users (yet).
- corvus was added to the "remotes" using the credentials from cygnus@pbs on corvus.
So, when I try to create a pull sync job on cygnus' datastore I can select Source Remote "corvus"
but I cannot select a Source Datastore.
My impression is that either the permissions for cygnus@pbs on corvus are wrong or that the
communication between the two hosts does not work.
Unfortunately I couldn't find any logs regarding the communication between the hosts, neither
positive nor negative.
So I assume that the issue lies with the permissions.
As I am currently playing around as root@pam I don't think that the local permissions are relevant.
Any suggestions what permissions are missing on cygnus@pbs on corvus? Any ideas on debugging this?
Thanks, I appreciate any input.
Uwe
next reply other threads:[~2026-02-25 11:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 11:23 Uwe Sauter [this message]
2026-02-25 11:48 ` Christian Ebner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51bd4380-15f7-4aa8-834e-70aa509a3823@gmail.com \
--to=uwe.sauter.de@gmail.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox