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 A17BA91548 for ; Fri, 10 Mar 2023 16:12:07 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 82A1022B3A for ; Fri, 10 Mar 2023 16:12:07 +0100 (CET) Received: from mail.shelldog.de (mail.shelldog.de [37.120.183.226]) (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 firstgate.proxmox.com (Proxmox) with ESMTPS for ; Fri, 10 Mar 2023 16:12:07 +0100 (CET) Received: from roundcube.shelldog.de (unknown [10.0.3.11]) by mail.shelldog.de (Postfix) with ESMTPSA id 7405C169FCC for ; Fri, 10 Mar 2023 16:02:09 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shelldog.de; s=default; t=1678460529; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=n9B+RTX9YipyQoM1xIuoyUJ/M0uMTUUSoyBautMk93Y=; b=iX4zHSUoiN4eMSuRYURZDqUh7ZqDHBGlKi6gQrWutlr8OJgMRH5EUFC5Lbw6m60XXefOEt 2mbV7JOaNAMaX98VhaaWBELeA15RETY6DlpV/g22qVmoqgJdBxJchYNduOkU7+1Aao76Mk A/tA5OQrj5JF1lgCKpt/PMd68yFAr5w= MIME-Version: 1.0 Date: Fri, 10 Mar 2023 16:02:09 +0100 From: Sven To: pve-user@lists.proxmox.com User-Agent: Roundcube Webmail/1.4.13 Message-ID: <4443ef0f136aed8ca4ef76b9de88677a@shelldog.de> X-Sender: sven@shelldog.de Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.834 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% 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 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] Timeouts while creating backups on PBS 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: Fri, 10 Mar 2023 15:12:07 -0000 Hello we have several clusters (~250 VMs) attached to one PBS and run daily backups. Each day, there are random timeouts causing some backups to fail. I've disabled the instant verification process to reduce IO-load on the PBS during that time. The timeouts are gone since then. Because we do want to have verified backups, we tried out scheduled verification tasks. Then we have the problem, that it takes to long (>1d) to verify all ~250 new snapshots sequentially. 50 parallel verify jobs works well. My current idea is to write a custom scheduler to make sure that there is a custom amount of verify jobs simultaneously when no backups are running. Is there a better way I don't see? If I may place a feature request: It would be nice to be able to specify how many verify jobs can work simultaneously. Thanks! Sven