proxmox-tape backup-job run : Error: timeout while trying to lock

[2CsJkl8e]

Hi,
# Backup Server 3.1-4
having a TL4000 attached to our PBS, we're running tape backups any other day (using a single drive only).
Some backup-jobs (for dedicaed namespaces) get started by the PBS scheduler itself, some get fired off using "proxmox-tape backup-job run <id>".
Problem is, a PBS scheduler started backup-job seems to patiently wait for an already running backup-job to finish, there will be no timeout (I saw >10h lately).
However, a proxmox-tape console call triggered backup-job does not, it more or less imediately returns with "Error: timeout while trying to lock", if there is an ongoing backup-job active.
What's the difference here? It's all just jobs, only triggered diffently.
There's no info about timeout parameters for the proxmox-tape family of console commands afaics.
How can I have "proxmox-tape backup-job run <id>" wait for an already allocated tape drive / other running backup-job?
Thanks Peter

 

[dcsapak]

that behaviour is actually expected. the idea was that while schedule triggered job wait forever, a manually triggered job must be done by hand and then it can be checked if it can be run currently
the 'run now' functionality was not intended to implement a queuing system

what is the use case here?
as a workaround you could set the schedule to a time e.g. a minute from now, wait until it's started and revert the schedule back to it's original value

if there is a valid use case i'd be open to add a parameter to override the timeout from the default on the cli, for that you could open a feature request here: https://bugzilla.proxmox.com