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 510B579182 for ; Mon, 3 May 2021 18:53:04 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 3F28C20951 for ; Mon, 3 May 2021 18:53:04 +0200 (CEST) Received: from mout.web.de (mout.web.de [212.227.17.12]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 658DC20943 for ; Mon, 3 May 2021 18:53:02 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=web.de; s=dbaedf251592; t=1620060775; bh=UclEd1kFM0OCSWe6SgaAP+z1OOyETOglXcMUUoW8cas=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=ixKyXADEJqe8S2R6AKF1DkyqT1i67K9uD2GXnBsejnIvHkbdOmIAT7hOqEP85aksD qkFPKSmNI5GgiXMwnywWkN+PBWmuQlBrUvmB9iR+5Gfx6MbR3jJQgPsOG06co64/qg mze+sFf3gM5pftdqxZHzTM5SBLERKzn2fyt2CtL0= X-UI-Sender-Class: c548c8c5-30a9-4db5-a2e7-cb6cb037b8f9 Received: from Rolands-MacBook-Pro.cybercon.de ([87.79.220.86]) by smtp.web.de (mrweb106 [213.165.67.124]) with ESMTPSA (Nemesis) id 1My6lR-1lLxAu2CJb-00zV7U; Mon, 03 May 2021 18:52:55 +0200 To: Thomas Lamprecht , Proxmox VE user list References: <3538b9a7-3b60-f603-6b66-c694fb5b225c@web.de> From: Roland Message-ID: <95223646-5b37-7092-7ad8-1866dc7195cb@web.de> Date: Mon, 3 May 2021 18:53:09 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:78.0) Gecko/20100101 Thunderbird/78.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:LG9qvX4rFA5Ad8HZDYiYabnyWSg4iOKe6ohREhMVR4xIepML+bp CT6qmNySKDjQiJTuuE7Hk1eW2N4bGvBdbys8GiYnCfyLu+E7ttV/PMXOpKpEOiv6Mkv9+JR 88yRIVHgdq+0XobTElhasc5+LE2c2cOZMnfJLtCiJkQmWviQ9kE5Ub/IifC/4u1Pa4ZJURo 2odtQT6bf1oMxVjAX5naw== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:4J/41opox3o=:xorTGidJ26m6WHDa5F37Ni 3DthZZEiUkLx7Vov9HrdNbOBw6aP1z3U3/37+Sv4f0JxneUJaHHe//lLjIIQBQXV8oP5BGXUB j2ph3mZ2iqA79fTZy6x0a05cF94fqxFTLmL6DU4hP382lISM5BmxzHCYN3U+cyg9sp5GBgewf spcNsZLAZFEZKTle8OVxibartYzzNkuS2iXYdWdBEENXOUZtpExFrklQW1aDHcbcFnBmr65m6 hviXdZJ9QVSsdilJUKKdPEXEehZ20jP/yNwHm9pQCYFHL+hM90dhc4Vb33CQAcLl7SFKBJGt8 l9ZR//X9qtD/fU2qoFoEdY85aZfQRMzWzj0Veq03quGR+98Nx6gG9VKy2JG2LaPw0nn4JOvvV pXJ5w2Uw1h9OXQpcy8KcdRQtVNrq0Gxp49OPWE+l1i0rXYemrxaUg3T1vc6QX8DyDE4jfbOdR Z26iFnZBpWIeEtAl63rcpqvBdGPQ0DbsBK5DaBHWN4UWGcMEWcCUEgNNFf7jD/xpHT3U2aZh9 xtHgbJXS0rZQbTZCq9Afodzl0wSskQ2q2uZ8ar9iZPmYpZabxwLNQGjFzdsEqUBIa/DILnJ/4 kbJijtruk4gWS4kh9DXqkKqQjI0tz6pfT0KmP+/yhecUbg5thQCSrW8jbAycPUz0b0iDsyOll xMBalVzUPBWtO6hmKC52Tj2osARbfwGW6aKZwAIppNZ/EKkU93kDRrABM8kBq7XdbSHZPkayT wXI6YONkSOTQqj8N4EaGXesLoLLUp07teUPcY493+GOuZ9fhdsHmTDruriHmtgxem4WrigKQt bFhyflJS6aqo+YNTFcEj4ql/sL/oSulSvztsRxJYDbcoxuyxcHr0xPGtL/nAEkx4uAzL9RZM/ 4QSomav23m5LnDZ0DSGnKz/NE/7lMF0Tu9yAAzjsg6aSPctv3K0XChi7B4FNJ9iyLgKlM3A+P oKT4ytKy289E1i1P5FQsZWTkMDA1Z6jOocqLaMMFO8t2MMfXHp+sr7rcN0DLzPeDm6+m7zJDC 8cuogopr+VUVugjABKTtAlhGFRXq4jpV3HrPXz5VCU+0yhWqZ18QRtfx3vEM3klRh90Ap1Rbb CgsDnY1gV8RwifAP9vf0rLPG2nHQ3LHiN4OVRjTlxWV43iWZwhS3GP0QgoK8BMGCwvzkZfxvW Fn1OuKZnw0KB58CvJCrClOALZc5xc0Z9bY30WYkO7qIseHsripUwxkDpBeHRHe4iQ317w= X-SPAM-LEVEL: Spam detection results: 0 AWL -0.247 Adjusted score from AWL reputation of From: address DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain FREEMAIL_FROM 0.001 Sender email is commonly abused enduser mail provider NICE_REPLY_A -0.001 Looks like a legit reply (A) RCVD_IN_DNSWL_LOW -0.7 Sender listed at https://www.dnswl.org/, low trust RCVD_IN_MSPIKE_H3 0.001 Good reputation (+3) RCVD_IN_MSPIKE_WL 0.001 Mailspike good senders SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [PVE-User] pbs prune from commandline ? X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 May 2021 16:53:04 -0000 Hi, > You can change the prune-schedule via CLI with the manager > > # proxmox-backup-manager datastore update DATASTORE --prune-schedule '..= .' > yes, thanks >> i only find prune option with proxmox-backup-client. > > And why exactly doesn't `proxmox-backup-client` counts as CLI? > yes, it counts. but isn't that somewhat pruning "at the remote" level, where you need a privileged (...@pbs) user for? i find using it complicated, too. >> this should be be equivalent to:=C2=A0 pve -> storage -> pbs-ds -> Back= up >> Retention=C2=A0 tab, i.e. it's the prune definition on the client side. >> >> shouldn't there exist prune option in proxmox-backup-manager, too !? > > The manager is more for server-admin commands, GC is always a datastore = wide operation > not affecting any backups, so no client notices it. > > Pruning, on the other hand, should be done by the client making the back= ups itself, > as it has a big impact on the actual backup availability. > > But the client is available in all our repositories (PBS, PVE, PMG) so y= ou can just > install it, if not already done, and use that: > > # proxmox-backup-client prune vm/100/2021-03-23T12:32:02Z --keep-last 10= 0 > --keep-daily 42 ... > > If you do not want to always login you can just edit your .bashrc (or wh= atever your shell uses) > and setup the environment variables for your local server there. > > https://pbs.proxmox.com/docs/backup-client.html#environment-variables yes, but i'm just asking because i'd wonder if this is a "consistent" interface - i don't use prune on the client side and don't think it's easy to handle to iterate trough every single VM for pruning, as number of VMs may change and you need to adjust a commandline prune/script. i simply wonder if there isn't a commandline prune for pruning at datastore level (like you can do gc or verify via commandline at datastore level) roland