I'm trying to build Bacula rpm binaries on 64-bit Centos 5.2
Script I'm using:
#!/bin/bash
rpmbuild --rebuild \
--define "build_centos5 1" \
--define "build_x86_64 1" \
--define "build_mysql5 1" \
--define "build_python 1" \
bacula-2.4.4-1.src.rpm
It results in the following:
ch
I'm considering the use of reasonably-priced external hard drives to replace
my oldish tape drive. In the beginning this would apply my home system.
Drives like this:
http://www.wdc.com/en/products/products.asp?driveid=563
AFAIK Bacula has been very much designed with tapes (volumes) and tape pool
Bruno Friedmann wrote:
> Gabriele Bulfon wrote:
>
>> Hello,
>> I'm having trouble with a win2003 client running the agent.
>> >From time to time only that client stops the backup with the following
>> >error:
>> 09-Jan 03:03 smartlink-dir: Enterprise_Backup_OFFICE.2009-01-08_21.50.00
>> Fatal
HI!
Is needed some db modifications for upgrading?
or just upgrading rpms and restarting do the trick?
Regards, Angel
El Sábado, 10 de Enero de 2009 Scott Barninger escribió:
> Bacula-2.4 RPM Release Notes
> 10 January 2009
> D. Scott Barninger
>
>
> Release 2.4.4-1
>
> This release incorpora
Bacula-2.4 RPM Release Notes
10 January 2009
D. Scott Barninger
Release 2.4.4-1
This release incorporates a number of significant changes since 1.38.
These release notes refer to the rpm packaging only.
Please refer to the release notes and changelog in the
tarball or on sourceforge for complet
Bruno Friedmann wrote:
> Gabriele Bulfon wrote:
>
>> Hello,
>> I'm having trouble with a win2003 client running the agent.
>> >From time to time only that client stops the backup with the following
>> >error:
>> 09-Jan 03:03 smartlink-dir: Enterprise_Backup_OFFICE.2009-01-08_21.50.00
>> Fatal
Bruno Friedmann wrote:
> Gabriele Bulfon wrote:
>
>> Hello,
>> I'm having trouble with a win2003 client running the agent.
>> >From time to time only that client stops the backup with the following
>> >error:
>> 09-Jan 03:03 smartlink-dir: Enterprise_Backup_OFFICE.2009-01-08_21.50.00
>> Fatal
On Sat, Jan 10, 2009 at 12:53:59PM +0200, Timo Neuvonen wrote:
>
> If the library was replaced with another one (factory-replacement avove),
> are there any chances that the scsi addresses (14 vs 15) in drive
> configuration were swapped? It's also possible you (or someone else at your
> site)
>> I had a similar situation awhile back. I think my st0 corresponded to
>> nst1, st1 didn't have nst equiv. Something like that.
>>
>> I don't know what O/S you're running there? It's obviously different to
>> mine.
>>
>
> its centos5:
> [r...@molbio ~]# cat /etc/redhat-release
> CentOS release
Andrea Conti wrote:
> Update: I think I found the cause. After I added the logging option
>> /l:f, the system state backup is suddenly running without a problem. No
>> idea why that would make a difference.
>>
>
> I just do:
>
> start /w "" ntbackup backup systemstate /F ""
>
> and it works w
Gabriele Bulfon wrote:
> Hello,
> I'm having trouble with a win2003 client running the agent.
>>From time to time only that client stops the backup with the following error:
> 09-Jan 03:03 smartlink-dir: Enterprise_Backup_OFFICE.2009-01-08_21.50.00
> Fatal error: Network error with FD during Backu
11 matches
Mail list logo
