Using Bacula 2.2.6 on Debian 4 with an Overland 2 drive, 24 tape library
We have some archive tapes that we hold beyond the normal pruning cycle.
Unfortunately we need to recover some data off these tapes. I have used blist
to find the tapes that the data we want is on and have used bscan to re
-Original Message-
From: Proskurin Kirill [mailto:proskurin...@fxclub.org]
Sent: Fri 25/09/2009 11:24
To: bacula-users@lists.sourceforge.net
Subject: [Bacula-users] Auto recycle volume
Hello all.
Im confused about recycle options in Bacula 2.4.4.
I have such options on some pools:
Recyc
Bacula 2.2.6 running on Debian 4 with an Overland 24 slot tape changer.
We had a situation this week where a back up job hung because it was waiting to
write to a tape that was not in the tape changer. Is this normal?
Below is from the bacula log:
02-Sep 22:43 ceres-sd JobId 10639: End of medi
We are using Bacula 2.2.5 with an Overland 24 slot tape drive.
I have just replaced some full tapes with tapes to be purged and reused. For
some reason some slots are showing both old and new tapes in them when I run
option 15 on the query command:
Choose a query (1-16): 15
+-+-
Will there be any conflict if I install/configure exim4 on a machine
running bacula 2.2.6 which uses bsmtp to send Bacula status emails?
Thanks,
John
--
John Kennedy
Linux System Administrator
Publishing Technology plc
T: +44 1865 397838
M: +44 7771 962776
john.kenn...@publishingtechnology.com
Martin Simmons wrote:
>>>>>> On Tue, 16 Jun 2009 14:29:25 +0100, John Kennedy said:
>> We keep getting the following errors when running backups and any time
>> we query:
>>
>> 16-Jun 13:56 ceres-dir JobId 8703: Fatal error: sql_get.c:359
>> sql_get.
RR=Input/output error
3912 Failed to label Volume: ERR=dev.c:1526 ioctl MTBSR error on
"ArcVaultDrive-2" (/dev/nst1). ERR=Input/output error.
Label command failed for Volume AMD554L3.
AMD554L3 is the barcode on the tape. This happens on drive 1. Drive 0
will label but the tapes
We keep getting the following errors when running backups and any time
we query:
16-Jun 13:56 ceres-dir JobId 8703: Fatal error: sql_get.c:359
sql_get.c:359 query SELECT VolumeName,MAX(VolIndex) FROM JobMedia,Media
WHERE JobMedia.JobId=8703 AND JobMedia.MediaId=Media.MediaId GROUP BY
VolumeName O
We keep getting the following errors when running backups and any time
we query:
16-Jun 13:56 ceres-dir JobId 8703: Fatal error: sql_get.c:359
sql_get.c:359 query SELECT VolumeName,MAX(VolIndex) FROM JobMedia,Media
WHERE JobMedia.JobId=8703 AND JobMedia.MediaId=Media.MediaId GROUP BY
VolumeName OR
> - The FD isn't running. Use netstat -ltunp to confirm that it is running
> and listening on port 9102, and on the correct ethernet interface.
> - A firewall blocks access to the FD.
> - The new machine isn't properly set up on the network (use ping to
> confirm th
ectly
> or indirectly, use, disclose, distribute, print or copy any part of this
> message if you are not the intended recipient.
>
>
>
> -Original Message-
> From: John Kennedy [mailto:john.kenn...@publishingtechnology.com]
> Sent: Tuesday, June 09, 2009 7:16 AM
We had a Bacula client machine die recently.
I have reinstalled the machine with Debian - Lenny. I installed the
bacula-client package from the Lenny repos. Our Bacula server is running
version 2.2.6.
I have edited /etc/bacula/bacula.conf (on the client) to have:
FDAddress =
but when trying to r
12 matches
Mail list logo