Re: [Bacula-users] convincing Bacula to use a different tape than it requested

Normally when Bacula asks for a specific volume and the volume is not "available" it will put up a message requesting the volume. If you then put a different volume into the drive (assuming it is a tape), Bacula will use that volume if it is appropriate (correct Media Type, Pool, Volume

Re: [Bacula-users] convincing Bacula to use a different tape than it requested

You can disable the volume or change the volume status to Full if you don't intend to append any additional data. If you disable the volume, you will need to enable it in order to use it. I deal in sets of 10 volumes and run into situations where Bacula want a volume that has an earlier

Re: [Bacula-users] convincing Bacula to use a different tape than it requested

Hello, 2018-02-12 0:11 GMT+01:00 Tilman Schmidt : > (...) > > So what is the appropriate action when Bacula decides to use a tape that > for whatever reason is not available for use? > > Could you define "is not available for use"? For Bacula the tape available for use has a

Re: [Bacula-users] convincing Bacula to use a different tape than it requested

Forcing Bacula to use particular tapes is not my objective. (That would be easy - just put every tape in a pool of its own.) What I'm asking for is a sensible way to handle the situation when Bacula requests an unavailable volume. That does happen. It's more frequent with standalone drives but it

Re: [Bacula-users] convincing Bacula to use a different tape than it requested

Bacula is designed to decide itself which tapes to use and when. If you are trying to force it to use particular tapes it is possible, but it is outside the design envelop, so you will almost surely run into problems. On 06.02.2018 00:54, Tilman Schmidt wrote: Just encountered the situation

Re: [Bacula-users] convincing Bacula to use a different tape than it requested

Just encountered the situation again. Bacula requested last month's tape "Januar" since its use period hadn't expired yet, but it's the next full backup which should go onto the new month's tape "Februar". Tape "Januar" has VolStatus=Append. Tape "Februar" has VolStatus=Used with VolFiles=0 since

Re: [Bacula-users] convincing Bacula to use a different tape than it requested

Hello Heitor, Am 15.12.2017 um 15:41 schrieb Heitor Faria: >> running Bacula 7.4.4 (same problem with version 5.2.13) on openSUSE Leap >> 42.3 with a standalone LTO tape drive. Note: Meanwhile upgraded to 9.0.6. >> [Sometimes Bacula requests] a tape that for some >> reason cannot or should not

Re: [Bacula-users] convincing Bacula to use a different tape than it requested

On 15/12/17 15:07, Tilman Schmidt wrote: On my server I see tapes staying in the "Used" status long after their retention has expired. Correct. Retention is the _minimum_ period before the tape can be marked for reuse Only when Bacula needs a tape *and* it cannot find one with status

Re: [Bacula-users] convincing Bacula to use a different tape than it requested

Hello Heitor, thanks for your answer. On Fri, Dec 15, 2017, at 15:41, Heitor Faria wrote: > If tape has Used status, its volume retention is not over yet. That doesn't match what I observe. On my server I see tapes staying in the "Used" status long after their retention has expired. Only when

Re: [Bacula-users] convincing Bacula to use a different tape than it requested

> Hello list, Hello, Tilman, > running Bacula 7.4.4 (same problem with version 5.2.13) on openSUSE Leap > 42.3 with a standalone LTO tape drive. > When the loaded tape is full, or unsuitable for the backup job for some > other reason, Bacula will eject it, select another tape from the >

[Bacula-users] convincing Bacula to use a different tape than it requested

Hello list, running Bacula 7.4.4 (same problem with version 5.2.13) on openSUSE Leap 42.3 with a standalone LTO tape drive. When the loaded tape is full, or unsuitable for the backup job for some other reason, Bacula will eject it, select another tape from the appropriate pool, and emit an