public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>, David Lawley <davel@upilab.com>
Subject: Re: [pbs-devel] Proxmox Backup Server 2.2 available
Date: Fri, 20 May 2022 07:43:45 +0200	[thread overview]
Message-ID: <d0c334e2-335e-327f-f08d-f7cc2aa475a0@proxmox.com> (raw)
In-Reply-To: <5dc099cb-37ef-7eca-ff38-1502ec9ff8fa@upilab.com>

On 19/05/2022 12:28, David Lawley wrote:
> Off hand going to guess moving backups to a namespace not an easy task?  Or maybe there is a way?

As long as the backups stay in the same datastore it's relatively easy,
as that's just moving around folders. For cross datastore you need to use
sync-to-local-remote for now, as otherwise data chunk can be missing.

You could do the following on the CLI, note that it'd be best to enable
the new offline maintenance mode to avoid interfering with the PBS daemons,
as this example ignores locking completely.

# change pwd to datastore root dir, e.g.:
cd /mnt/datastore
# create the namespace "foo" manually (or via gui, which doesn't needs the ns/ prefix)
mkdir -p ns/foo

# ensure folder have correct owners to avoid issues on prune/delete
chown -R backup:backup ns

# move all groups of type vm, ct and host
mv vm ct host ns/foo

# or, move just a single group:
# first create the backup group type in the NS, if not already presen
mkdir ns/foo/vm
chown -R backup:backup ns/foo/vm
# move the group
mv vm/101 ns/foo/vm/

# or a deeper namespace "foo/bar"
mkdir -p ns/foo/ns/bar
chown -R backup:backup ns

Adapted from my post in
https://forum.proxmox.com/threads/proxmox-backup-server-2-2-available.109724/page-2#post-471949

cheers,
Thomas




  reply	other threads:[~2022-05-20  5:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18  9:02 Martin Maurer
2022-05-19 10:28 ` David Lawley
2022-05-20  5:43   ` Thomas Lamprecht [this message]
2022-05-20 10:04     ` David Lawley

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=d0c334e2-335e-327f-f08d-f7cc2aa475a0@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=davel@upilab.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