From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id D059265083 for ; Mon, 2 Nov 2020 11:48:23 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id C704B220C1 for ; Mon, 2 Nov 2020 11:48:23 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [212.186.127.180]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 5C2D6220B7 for ; Mon, 2 Nov 2020 11:48:23 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 27AD545EDF for ; Mon, 2 Nov 2020 11:48:23 +0100 (CET) From: =?UTF-8?q?Fabian=20Gr=C3=BCnbichler?= To: pbs-devel@lists.proxmox.com Date: Mon, 2 Nov 2020 11:48:11 +0100 Message-Id: <20201102104811.1315280-3-f.gruenbichler@proxmox.com> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20201102104811.1315280-1-f.gruenbichler@proxmox.com> References: <20201102104811.1315280-1-f.gruenbichler@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.026 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pbs-devel] [PATCH proxmox-backup 3/3] docs: extend managing remotes X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2020 10:48:23 -0000 with information about required privileges and limitations Signed-off-by: Fabian Grünbichler --- docs/managing-remotes.rst | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/managing-remotes.rst b/docs/managing-remotes.rst index e8495db1..382ca84d 100644 --- a/docs/managing-remotes.rst +++ b/docs/managing-remotes.rst @@ -79,4 +79,17 @@ either start it manually on the GUI or provide it with a schedule (see └────────────┴───────┴────────┴──────────────┴───────────┴─────────┘ # proxmox-backup-manager sync-job remove pbs2-local +For setting up sync jobs, the configuring user needs the following permissions: +#. ``Remote.Read`` on the ``/remote/{remote}/{remote-store}`` path +#. at least ``Datastore.Backup`` on the local target datastore (``/datastore/{store}``) + +If the ``remove-vanished`` option is set, ``Datastore.Prune`` is required on +the local datastore as well. If the ``owner`` option is not set (defaulting to +``backup@pam``) or set to something other than the configuring user, +``Datastore.Modify`` is required as well. + +.. note:: A sync job can only sync backup groups that the configured remote's + user/API token can read. If a remote is configured with a user/API token that + only has ``Datastore.Backup`` privileges, only the limited set of accessible + snapshots owned by that user/API token can be synced. -- 2.20.1