From: Fabrizio Cuseo <f.cuseo@panservice.it>
To: Hannes Laimer <h.laimer@proxmox.com>
Cc: pve-user <pve-user@lists.proxmox.com>
Subject: Re: Question regarding sync jobs
Date: Wed, 25 Mar 2026 11:27:09 +0100 (CET) [thread overview]
Message-ID: <416275216.1279057.1774434429647.JavaMail.zimbra@zimbra.panservice.it> (raw)
In-Reply-To: <7addffd6-592b-4e66-8d9a-9eae4b627a89@proxmox.com>
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
prev parent reply other threads:[~2026-03-25 10:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 10:50 Fabrizio Cuseo
2026-03-24 6:42 ` Hannes Laimer
2026-03-25 10:27 ` Fabrizio Cuseo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=416275216.1279057.1774434429647.JavaMail.zimbra@zimbra.panservice.it \
--to=f.cuseo@panservice.it \
--cc=h.laimer@proxmox.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox