This is very very minor issue, but chapter '10.4 Tape Specifications' in
Bacula's Main Manual lists Exabyte VXA-4 tape.
AFAIK, that VXA-4 tape technology does not nor will not exist, unless in
some abandoned lab at experimental level only. Several years ago VXA-4 and
VXA-5 used to be in Exabyt
"Scott Barninger" kirjoitti viestissä
news:201002071341.20222.sc...@barninger.com...
On Sunday 07 February 2010 01:03:44 pm you wrote:
"Scott Barninger" kirjoitti viestissä
news:201002070701.32693.sc...@barninger.com...
Hmm, this is the script that should have run during the upgrade for a 3
Bacula-devel] Some issues on 5.0.0 srpm
>> Date: Wednesday 03 February 2010
>> From: "Timo Neuvonen"
>> To: bacula-devel@lists.sourceforge.net
>>
>> I built 5.0.0 binary rpms from the srpm on SF
>> CentOS 5, 64-bit, mysql
>>
>> rpmbuil
I built 5.0.0 binary rpms from the srpm on SF
CentOS 5, 64-bit, mysql
rpmbuild --rebuild \
--define "build_centos5 1" \
--define "build_mysql5 1" \
--define "build_python 1" \
--define "nobuild_gconsole 1" \
bacula-5.0.0-1.src.rpm
Then, I upgraded my 3.0.3 system:
rpm -Uvh bacula-mysql-5.0.0-1.x8
"Kern Sibbald" kirjoitti viestissä
news:201001032008.34298.k...@sibbald.com...
> Hello,
>
> The other day, Eric pointed out to me that some of the manuals that we
> have
> posted in different languages are quite out of date -- in fact, the
> partial
> French translation apparently dates from ve
"Kern Sibbald" kirjoitti viestissä
news:200907302233.19300.k...@sibbald.com...
> On Thursday 30 July 2009 22:24:25 Scott Barninger wrote:
>> On Wednesday 29 July 2009 08:21:50 am Timo Neuvonen wrote:
>> > I tried to build 3.0.2 binary rpms with the following scrip
I tried to build 3.0.2 binary rpms with the following script, on CentOS 5.3
x86_64
#!/bin/bash
rpmbuild --rebuild \
--define "build_centos5 1" \
--define "build_x86_64 1" \
--define "build_mysql5 1" \
--define "build_python 1" \
--define "nobuild_
com...
> If I am not mistaken, Bacula only unmounts a disk on explicit user
> command,
> much like it does with tapes where once the tape is mounted, it is
> unmounted
> only by the user.
>
> If the unmount command does not work, then we could look at the problem.
>
> Regar
I'm sorry to write this into developers list, but I've asked this a couple
of times in the past months in the user list with no reply.
Is this possibly some simple configuration bug from my side, or is there
some deeper problem with SD's "Unmount Command"?
Attached is a "-d 200" debug output of
> when manually recycling a (used) volume with
> "update volume=xxx VolStatus=Recycle"
> this volume will be accepted for overwriting. Nonetheless, Jobs that have
> been written to that volume will NOT be removed from the catalog. This
> results in invalid data, as the catalog will still contain da
"Kern Sibbald" <[EMAIL PROTECTED]> kirjoitti viestissä
news:[EMAIL PROTECTED]
> On Saturday 25 October 2008 21:53:00 Ulrich Leodolter wrote:
>> On Sat, 2008-10-25 at 21:11 +0200, Eric Bollengier wrote:
>> > Le Saturday 25 October 2008 13:41:15 Ulrich Leodolter, vous avez écrit
>> > :
>> > > On Sa
Currently http://www.bacula.org/en/?page=documentation starts with a number
of links to all-in-one manuals that AFAIK are not updated nor planned to be
updated any more. Then, in the bottom of the page, there are links to new
manuals.
Could the order of the links be reversed? Or at least the older
"Scott Barninger" <[EMAIL PROTECTED]> kirjoitti viestissä
news:[EMAIL PROTECTED]
> Bacula-2.2 RPM Release Notes
> 27 January 2008
> D. Scott Barninger
>
>
> Release 2.2.8-1
Thanks once again for the rpms!
I built the binaries on CentOS 5.1
Dir, fd and sd all start and run (in simple test) ok.
This is definitely a very minor issue, but anyway...
I have a Pool=Default line in job defaults, that pool doesn't actually exist
in my system (the definition exists, but it has no tapes).
Further, in Schedule section I always specify pool to be used (typically
"Cycle" or "Archieve"), it works co
"Scott Barninger" <[EMAIL PROTECTED]> kirjoitti viestissä
news:[EMAIL PROTECTED]
>
> Sorry for the delay but I have been out of town until this evening. Not
> sure what went wrong with the release but I have re-uploaded the srpm
> now. It should be available now and the file size looks correct.
>
> > bacula-2.2.6 has been released to sourceforge. This release should
> > address the RedHat (and clone) issues discussed recently as well as
> > introducing support for SuSE 10.3.
>
> Could someone pls. check if the bacula-2.2.6-1.src.rpm is ok?
> Size shown by Sourceforge is less than 8 megs, wh
> >16.09.2007 17:46,, Eric Böse-Wolf wrote::
> > As I am now using bacula-2.2.4 from BartPE it restores files with
> > umlauts correct, but I get a lot of those messages, but only with
> > filenames containing umlauts:
> >
> > 16-Sep 19:13 laptop_ute-fd: RestoreWindowsSystem.2007-09-16_17.14.10
> >
> Bacula-2.2 RPM Release Notes
> 03 September 2007
> The spec file currently supports building on the following platforms:
> # Whitebox Enterprise build
> --define "build_wb3 1"
>
> # RedHat Enterprise builds
> --define "build_rhel3 1"
> --define "build_rhel4 1"
>
> # CentOS build
> --define "bui
While the packagers are propably preparing for upcoming 2.2 release, I'd
like to throw a question where Bacula's log files should be put into?
At least Red Hat based systems traditionally have log files under /var/log/
directory. However, Bacula's log files are now under /var/bacula/ where
Bacu
I made a complete re-install of my file/backup server, from FC5 to
CentOS (RHEL) 5.
At this time, I also upgraded Bacula from 1.38.11 to 2.0.3, the latest
stable release available as rpms.
My configuration uses RunAfterJob to invoke a shell script that emails the
bootstap file to me. The idea is t
20 matches
Mail list logo
