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)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 75E68667EF for ; Fri, 6 Nov 2020 15:46:43 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 7274C23691 for ; Fri, 6 Nov 2020 15:46:43 +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 EDFB223688 for ; Fri, 6 Nov 2020 15:46:42 +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 B916E46059 for ; Fri, 6 Nov 2020 15:46:42 +0100 (CET) From: Dylan Whyte To: pbs-devel@lists.proxmox.com Date: Fri, 6 Nov 2020 15:46:25 +0100 Message-Id: <20201106144630.21538-3-d.whyte@proxmox.com> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20201106144630.21538-1-d.whyte@proxmox.com> References: <20201106144630.21538-1-d.whyte@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.025 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 docs 2/7] backup-client: add section on change-owner command 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: Fri, 06 Nov 2020 14:46:43 -0000 Add section "Changing the Owner of a Backup Group" Signed-off-by: Dylan Whyte --- docs/backup-client.rst | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/docs/backup-client.rst b/docs/backup-client.rst index 0b91c353..a23535fa 100644 --- a/docs/backup-client.rst +++ b/docs/backup-client.rst @@ -535,6 +535,29 @@ To remove the ticket, issue a logout: # proxmox-backup-client logout +.. _changing-backup-owner: + +Changing the Owner of a Backup Group +------------------------------------ + +By default, the owner of a backup group is the user which was used to originally +create that backup group (or in the case of sync jobs, ``root@pam``). This +means that if a user ``mike@pbs`` created a backup, another user ``john@pbs`` +can not be used to create backups in that same backup group. In case you want +to change the owner of a backup, you can do so with the below command, using a +user that has ``Datastore.Modify`` privileges on the datastore. + +.. code-block:: console + + # proxmox-backup-client change-owner vm/103 john@pbs + +This can also be done from within the web interface, by navigating to the +`Content` section of the datastore that contains the backup group and +selecting the user icon under the `Actions` column. Common cases for this could +be to change the owner of a sync job from ``root@pam``, or to repurpose a +backup group. + + .. _backup-pruning: Pruning and Removing Backups -- 2.20.1