Martin,
John Drescher e-mailed that the unmount command (which we had been using
after each job) causes the drive to enter into a blocked state such that
manual intervention is required afterward to load the drive again. John
suggested using the release command instead and I have found that doing
> On Wed, 16 May 2012 08:51:57 +0200, Robert Kromoser said:
>
> When I do a "list media pool=" then I see that the 2 Volumes
> in the pool
>
> has VolStatus Error. When I start a backup job "list jobs" show me the
>
> status R for running. But when I start "list media pool="
> later,
>
> no
> On Thu, 17 May 2012 09:05:27 -0400, Jack Cobb said:
> We are running Bacula 5.0.1 on a 64-bit Ubuntu 10.04 server connected to a
> Dell TL2000 tape library with two LTO-4 drives. Before our Bacula jobs run
> each we load the proper tapes (from running the list nextvol command) into a
> slot
Hello,
We are running Bacula 5.0.1 on a 64-bit Ubuntu 10.04 server connected to a
Dell TL2000 tape library with two LTO-4 drives. Before our Bacula jobs run
each we load the proper tapes (from running the list nextvol command) into a
slot in the library's magazine. Then we run the update stat
On Thu, 17 May 2012 00:11:23 -0500
David Clements wrote:
> I have a laptop running Win XP Professional, after a normal startup
> or a reboot the Bacula client is started and runs under the SYSTEM
> user.
>
> If I check the status of the Win client from bconsole on the Linux
> server I get:
>
Il giorno gio, 10/05/2012 alle 09.28 -0700, Tim Krieger ha scritto:
> I think you have two options...
>
> Probably the simplest and most straight forward would be to create a copy job
> for each pool, then a simple SQL select query for that pool to grab the
> latest full backup. This seems to b
