From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 5CEB71FF13B for ; Wed, 25 Feb 2026 12:48:15 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 5B7B436F31; Wed, 25 Feb 2026 12:48:58 +0100 (CET) Message-ID: Date: Wed, 25 Feb 2026 12:48:50 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: PBS: unable to create pull sync job To: uwe.sauter.de@gmail.com, Proxmox VE user list References: <51bd4380-15f7-4aa8-834e-70aa509a3823@gmail.com> Content-Language: en-US, de-DE From: Christian Ebner In-Reply-To: <51bd4380-15f7-4aa8-834e-70aa509a3823@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1772020114689 X-SPAM-LEVEL: Spam detection results: 0 AWL -1.014 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 1.113 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.358 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.659 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: FVRKNGN6XIDP5O7XON4GLYHDY7PPDWXI X-Message-ID-Hash: FVRKNGN6XIDP5O7XON4GLYHDY7PPDWXI X-MailFrom: c.ebner@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE user list List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Hi, On 2/25/26 12:23 PM, Uwe Sauter wrote: > 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. The user with RemoteSyncOperator permissions must be configured on the pulling (target) PBS instance on the corresponding remote path. This basically allows that user to read the remote configuration in order to connect and perform pruning on that remote. On the source side you will have to give Datastore.Backup or Datastore.PowerUser on the source datastore to the user configured for the remote connection. Details are documented in https://pbs.proxmox.com/docs/managing-remotes.html#sync-jobs > > 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. cygnus@pbs needs permissions to read the datastore on the remote host, which you are currently lacking. The RemoteSyncOperator does not allow this. > > 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? Hope this helps, Chris