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 297337D05F for ; Mon, 8 Nov 2021 13:13:32 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 1EAFC23E97 for ; Mon, 8 Nov 2021 13:13:32 +0100 (CET) Received: from mailhost2.inet.dkfz-heidelberg.de (mailhost2.inet.dkfz-heidelberg.de [193.174.53.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id DE77F23E85 for ; Mon, 8 Nov 2021 13:13:30 +0100 (CET) Received: from mx-ext.inet.dkfz-heidelberg.de (mx-ext.inet.dkfz-heidelberg.de [192.54.49.101]) by mailhost2.inet.dkfz-heidelberg.de (8.14.7/8.14.7) with ESMTP id 1A8C7C3l015707 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Mon, 8 Nov 2021 13:07:13 +0100 X-Virus-Scanned-DKFZ: amavisd-new at dkfz-heidelberg.de Received: from [172.22.167.4] (addr16.inet.dkfz-heidelberg.de [193.174.55.143]) (authenticated bits=0) by mx-ext.inet.dkfz-heidelberg.de (8.14.7/8.14.7/smtpin) with ESMTP id 1A8C7A6M008937 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Mon, 8 Nov 2021 13:07:11 +0100 DKIM-Filter: OpenDKIM Filter v2.11.0 mx-ext.inet.dkfz-heidelberg.de 1A8C7A6M008937 Message-ID: Date: Mon, 8 Nov 2021 13:07:10 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.3.0 To: Proxmox VE user list From: Frank Thommen Organization: DKFZ Heidelberg, Omics IT and Data Management Core Facility (ODCF) Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (mx-ext.inet.dkfz-heidelberg.de [192.54.49.101]); Mon, 08 Nov 2021 13:07:11 +0100 (CET) X-Spam-Status: No, score=-100.0 required=5.0 tests=ALL_TRUSTED autolearn=disabled version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mx-ext.inet.dkfz-heidelberg.de X-SPAM-LEVEL: Spam detection results: 0 AWL 0.950 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 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: [PVE-User] Excluding individual vdisks from PVE backups? 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, 08 Nov 2021 12:13:32 -0000 Dear all, we are doing daily backups of every VM in our PVE cluster to the internal Ceph storage (snapshot mode, ZSTD compression). However one of the VMs takes six to seven hours for the backup, which is unbearable and also interferes with other backup processes. The delay is probably due to a 50% filled 500G vdisk attached to the VM. Is there a way to exclude this specific vdisk from the PVE backup schedule, while still retaining the rest of the VM in the backup? We don't have PBS in place and will not have it in the near future for different reasons. So PBS would not be an option for us. Cheers, Frank