From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <t.lamprecht@proxmox.com> 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 4759271B6E for <pbs-devel@lists.proxmox.com>; Fri, 20 May 2022 07:43:49 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 3C7F3E10E for <pbs-devel@lists.proxmox.com>; Fri, 20 May 2022 07:43:49 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (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 firstgate.proxmox.com (Proxmox) with ESMTPS id 911CBE102 for <pbs-devel@lists.proxmox.com>; Fri, 20 May 2022 07:43:47 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 5BBAF43723; Fri, 20 May 2022 07:43:47 +0200 (CEST) Message-ID: <d0c334e2-335e-327f-f08d-f7cc2aa475a0@proxmox.com> Date: Fri, 20 May 2022 07:43:45 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:101.0) Gecko/20100101 Thunderbird/101.0 Content-Language: en-GB To: Proxmox Backup Server development discussion <pbs-devel@lists.proxmox.com>, David Lawley <davel@upilab.com> References: <4934e0fe-26da-048e-973c-93c60ba3083b@proxmox.com> <5dc099cb-37ef-7eca-ff38-1502ec9ff8fa@upilab.com> From: Thomas Lamprecht <t.lamprecht@proxmox.com> In-Reply-To: <5dc099cb-37ef-7eca-ff38-1502ec9ff8fa@upilab.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.376 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment NICE_REPLY_A -0.717 Looks like a legit reply (A) SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [proxmox.com] Subject: Re: [pbs-devel] Proxmox Backup Server 2.2 available X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion <pbs-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pbs-devel>, <mailto:pbs-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pbs-devel/> List-Post: <mailto:pbs-devel@lists.proxmox.com> List-Help: <mailto:pbs-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel>, <mailto:pbs-devel-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Fri, 20 May 2022 05:43:49 -0000 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