-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Simmons wrote:
>> On Thu, 28 Feb 2008 11:20:26 -0500 (EST), Steve Thompson said:
>> In the output of commands such as 'list jobs', is it possible to configure
>> bacula to display numeric quantities as digits alone (no commas)? I really
>>
John Drescher wrote:
>> > 23-Feb 06:21 khyber-sd JobId 1843: 3304 Issuing autochanger "load slot
>> > 1, drive 0" command.
>> >
>> > 23-Feb 06:26 khyber-sd JobId 1843: Fatal error: 3992 Bad autochanger
>> > "load slot 1, drive 0": ERR=Child died from signal 15: Termination.
>> > Results=Loadi
Hi,
28.02.2008 22:37, Peter Much wrote:
> Hallo Arno!
>
> <[EMAIL PROTECTED]> aka Arno Lehmann schrieb
> mit Datum Thu, 28 Feb 2008 17:38:55 +0100 in m2n.bacula.users:
>
> |> The only thing that has changed is two values in the catalog
> |> which mark the old job as migrated and the new job as
Hallo Arno!
<[EMAIL PROTECTED]> aka Arno Lehmann schrieb
mit Datum Thu, 28 Feb 2008 17:38:55 +0100 in m2n.bacula.users:
|> The only thing that has changed is two values in the catalog
|> which mark the old job as migrated and the new job as the target
|> of that migration. Now if one would some
From: Tilman Schmidt <[EMAIL PROTECTED]>
>> >OfflineOnUnmount = yes; # when unmounted, eject tape
>> > [...] has two unexpected side effects.
>> > a) If I label a new tape it is ejected after the operation, followed by
>> > a message from Bacula that it couldn't mount the new tape.
Hi,
Is it normal that while the volumes are being created in bacula, the labels
given to them are in crescent order?
Before, with the same configuration(unless I haven't noticed), when the
volumes were purged, the labels changes
i.e:
With 2 volumes for full backup:
Correct:
Full_Client1,FullCl
'A newbie here... please be kind&gentle.
I had differential backup scheduled to run. When it came time, it was
upgraded to full, citing "Prior failed job found..." But in fact, i had
a clean full backup (launched manually from the console) that finished
just a couple of days before. And if i tr
I stand corrected... It seems the data rate matching in LTO-3 drives
isn't as flexible as I'd have thought... One interesting thing to note
in the doc you mentioned is that if you think you may be shoe-shining,
try backing up onto an LTO-2 tape as this will run the drive at native
LTO-2 speeds
> On Thu, 28 Feb 2008 11:20:26 -0500 (EST), Steve Thompson said:
>
> In the output of commands such as 'list jobs', is it possible to configure
> bacula to display numeric quantities as digits alone (no commas)? I really
> find this difficult to read.
I don't think it is possible, except by
> > 23-Feb 06:21 khyber-sd JobId 1843: 3304 Issuing autochanger "load slot
> > 1, drive 0" command.
> >
> > 23-Feb 06:26 khyber-sd JobId 1843: Fatal error: 3992 Bad autochanger
> > "load slot 1, drive 0": ERR=Child died from signal 15: Termination.
> > Results=Loading media from Storage Eleme
Mark Nienberg wrote:
> Can anyone shed some light on the following fatal error? It happened
> during a tape change in the middle of a full backup. The autochanger
> has been working just fine prior to this and in fact the requested tape
> was successfully loaded into the drive (status storage
I really don't understand this.
I can run a backup to a tape, using my 'Server' volume/pool. It completes.
It moves on to the next client, which belongs to the same volume/pool, and
then Bacula reports that there are no appendable volumes and that I should
use the label command to resolve this.
I just tried to simulate a database crash and disaster recovery and came
to the point with restoring database with bacula-console and bootstrap file.
The documentation
http://bacula.org/en/dev-manual/Restore_Command.html#database_restore
shows the possibility to restore within console so I tried
In the message dated: Thu, 28 Feb 2008 11:21:31 EST,
The pithy ruminations from Bob Hetzel on
were:
=>
=> First a quick note... drives LTO 2nd generation and newer should not
=> shoeshine unless you're really running way to slow a cpu for what else
=> is going on with the computer.
Huh? Tha
Bob Hetzel wrote:
> First a quick note... drives LTO 2nd generation and newer should not
> shoeshine unless you're really running way to slow a cpu for what else
> is going on with the computer.
>
That is nice to know - Ive been doing lots of necessary things to avoid
shoeshining it seems.
>
Hi,
28.02.2008 15:48, Peter Much wrote:
> Hello Ryan,
>
> sorry this got a little delayed. I copy to Your email.
>
> <[EMAIL PROTECTED]> aka Ryan Novosielski schrieb
> mit Datum Sun, 10 Feb 2008 22:37:54 -0500 in m2n.bacula.users:
>
...
> It depends how You define "possible". It seems not to
Hi,
28.02.2008 12:49, Damian Brasher wrote:
> Hi List
>
> I have had some fairly regular job failures that I have pinpointed to be
> caused by tape status type error mismatches. The most common is that the
> tape status does not match that of the catalogue in a number of ways.
>
> The first is
First a quick note... drives LTO 2nd generation and newer should not
shoeshine unless you're really running way to slow a cpu for what else
is going on with the computer.
If the room air temp is less than 85 degrees or so it's unlikely in a
tape autoloader cabinet (i.e. good airflow by design)
In the output of commands such as 'list jobs', is it possible to configure
bacula to display numeric quantities as digits alone (no commas)? I really
find this difficult to read.
-s
-
This SF.net email is sponsored by: Micr
I have read the manual for verify jobs and I don't understand what the
directive "Verify Job" does.
The other question is where do i need to declare this?
http://www.bacula.org/en/dev-manual/Configuring_Director.html#SECTION00143
says If I run a verify job without this directive t
Hello Ryan,
sorry this got a little delayed. I copy to Your email.
<[EMAIL PROTECTED]> aka Ryan Novosielski schrieb
mit Datum Sun, 10 Feb 2008 22:37:54 -0500 in m2n.bacula.users:
|> |To the technical points you discuss, you will discover that tape
|> |mirroring is a problem, as currently cho
Hi List
I have had some fairly regular job failures that I have pinpointed to be
caused by tape status type error mismatches. The most common is that the
tape status does not match that of the catalogue in a number of ways.
The first is that if the catalogue reports the volume status to be
err
22 matches
Mail list logo
