From: Fabrizio Cuseo <f.cuseo@panservice.it>
To: pve-user <pve-user@lists.proxmox.com>
Subject: Question regarding sync jobs
Date: Mon, 23 Mar 2026 11:50:25 +0100 (CET) [thread overview]
Message-ID: <1303708809.1156748.1774263025991.JavaMail.zimbra@zimbra.panservice.it> (raw)
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 ?
Thanks, Fabrizio
next reply other threads:[~2026-03-23 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 10:50 Fabrizio Cuseo [this message]
2026-03-24 6:42 ` Hannes Laimer
2026-03-25 10:27 ` Fabrizio Cuseo
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=1303708809.1156748.1774263025991.JavaMail.zimbra@zimbra.panservice.it \
--to=f.cuseo@panservice.it \
--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