public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Dylan Whyte <d.whyte@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH docs 2/7] backup-client: add section on change-owner command
Date: Fri,  6 Nov 2020 15:46:25 +0100	[thread overview]
Message-ID: <20201106144630.21538-3-d.whyte@proxmox.com> (raw)
In-Reply-To: <20201106144630.21538-1-d.whyte@proxmox.com>

Add section "Changing the Owner of a Backup Group"

Signed-off-by: Dylan Whyte <d.whyte@proxmox.com>
---
 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





  parent reply	other threads:[~2020-11-06 14:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-06 14:46 [pbs-devel] [PATCH docs 0/7] Update for new content and sections Dylan Whyte
2020-11-06 14:46 ` [pbs-devel] [PATCH docs 1/7] installation & gui: Formatting fixup Dylan Whyte
2020-11-06 15:51   ` Dietmar Maurer
2020-11-06 14:46 ` Dylan Whyte [this message]
2020-11-06 14:46 ` [pbs-devel] [PATCH docs 3/7] datastore: description of new datastore view Dylan Whyte
2020-11-06 14:46 ` [pbs-devel] [PATCH docs 4/7] Update where to find certain items since GUI update Dylan Whyte
2020-11-06 14:46 ` [pbs-devel] [PATCH docs 5/7] maintenance: add verification and prune to section Dylan Whyte
2020-11-06 14:46 ` [pbs-devel] [PATCH docs 6/7] Remove reference to backup@pam & old console msg Dylan Whyte
2020-11-06 15:34   ` Dietmar Maurer
2020-11-09  7:38     ` Dylan Whyte
2020-11-06 14:46 ` [pbs-devel] [PATCH docs 7/7] Add screenshots Dylan Whyte
2020-11-06 15:33 ` [pbs-devel] applied: [PATCH docs 0/7] Update for new content and sections Dietmar Maurer

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=20201106144630.21538-3-d.whyte@proxmox.com \
    --to=d.whyte@proxmox.com \
    --cc=pbs-devel@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal