From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 55DDB1FF13B for ; Wed, 25 Mar 2026 11:28:03 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 677AF12BD1; Wed, 25 Mar 2026 11:28:02 +0100 (CET) X-Virus-Scanned: amavis at zimbra.panservice.it Date: Wed, 25 Mar 2026 11:27:09 +0100 (CET) From: Fabrizio Cuseo To: Hannes Laimer Message-ID: <416275216.1279057.1774434429647.JavaMail.zimbra@zimbra.panservice.it> In-Reply-To: <7addffd6-592b-4e66-8d9a-9eae4b627a89@proxmox.com> References: <1303708809.1156748.1774263025991.JavaMail.zimbra@zimbra.panservice.it> <7addffd6-592b-4e66-8d9a-9eae4b627a89@proxmox.com> Subject: Re: Question regarding sync jobs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.16.27.148] X-Mailer: Zimbra 10.1.16_GA_4850 (ZimbraWebClient - GC146 (Mac)/10.1.16_GA_4863) Thread-Topic: Question regarding sync jobs Thread-Index: lmYhHF7lDNWfhy0Zdd8s5AaB0O9O6w== X-SPAM-LEVEL: Spam detection results: 0 AWL 0.767 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_PASS -0.001 SPF: HELO matches SPF record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: SAOVXTDXNDKHL4BW3UXKPW7LKTEAMNEO X-Message-ID-Hash: SAOVXTDXNDKHL4BW3UXKPW7LKTEAMNEO X-MailFrom: fabry@zimbra.panservice.it X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: pve-user X-Mailman-Version: 3.3.10 Precedence: list Reply-To: Fabrizio Cuseo List-Id: Proxmox VE user list List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Yes, is working :) Thank you very much. ----- Il 24-mar-26, alle 7:42, Hannes Laimer h.laimer@proxmox.com ha scritto: > Hey Fabrizio, > > On 2026-03-23 12:00, Fabrizio Cuseo wrote: >> Hello. >> I have searched with no results, so I ask if is possibile: >> >> - several PBS servers with backups for different PVE clusters >> - remote PBS server that handles USB drives for remote ad offline backup sync >> - several sync jobs for each USB drive repository; this is needed because a >> single USB drive contains different remote PBS sources. >> >> If I flag "execute on mount", and "unmount after synced" on a single script, no >> problems. But If have more than one sync job, I would like to have a sequence, >> so: >> - first job, "executed on mount" >> - second job, "executed after first" >> - third job, "executed after second" - "unmount at end". >> >> Is this possible or scheduled for a next release ? > > this is what should be happening, if you have multiple jobs marked with > "run on mount" they should run sequentially(ordered by job-id)[1], and > if any of the jobs has "unmount after" set the datastore will be > unmounted after the last one finishes. > > If this is not happening, it's a bug :) > >> >> Thanks, Fabrizio >> >> >> > > ~ Hannes > > [1] > https://git.proxmox.com/?p=proxmox-backup.git;a=blob;f=src/api2/admin/datastore.rs;h=cca34055353273585327dcd38a2b5e5648ceb811;hb=refs/heads/master#l2535