[Bacula-users] 2.4.4 rpm binary build problem

2009-01-10 Thread Timo Neuvonen
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:



checking whether to use NLS... yes
checking where the gettext function comes from... libc
checking for msgfmt... (cached) /usr/bin/msgfmt
configure: error: Unable to find Gnome 2 installation
error: Bad exit status from /var/tmp/rpm-tmp.69060 (%build)


RPM build errors:
InstallSourcePackage: Header V3 DSA signature: NOKEY, key ID 10a792ad
user sbarn does not exist - using root
user sbarn does not exist - using root
user sbarn does not exist - using root
user sbarn does not exist - using root
user sbarn does not exist - using root
user sbarn does not exist - using root
user sbarn does not exist - using root
Bad exit status from /var/tmp/rpm-tmp.69060 (%build)


Well... I don't use a desktop lot, but I have gnome installed anyway, though 
the error claims otherwise.

This is quite new Centos install, and my first and only 64-bit system so 
far. So, there are good chances there may be missing something from this 
system. I already filled all the missing dependencies the build reported.

I also have a 32-bit Centos system where the build runs ok, and comparing 
the output of
# rpm -qa | grep gnome | sort
between these systems it looks I have the same "gnome-like" rpms installed 
here.

Any idea what might cause that error? Or is it some bug in the 64-bit build 
process, maybe?


Regards,
Timo 



--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


[Bacula-users] External "recylable" hard drives as Bacula storage -how?

2009-01-10 Thread Timo Neuvonen
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 pools
in mind, though it is possible to create volumes on hard disks too.

I haven't tried to plan this very much yet, so there certainly are some
holes in my scenario. But let's suppose I had (for example) 3 pcs of
one-terabyte drives like the one in the link above, I would keep at least
one of them in a "safehouse", and one or two (at a time) were attached to
computer running Bacula SD. This 3-disk system is a minimized scenario,
there would soon be a need for 4-5 disks, I guess.

The goal could be writing all the backups to one drive for, say, one month.
Then, this drive would be considered "used" (compare to "volume use
duration" in Bacula) and the next one were taken into daily use, though both
the disks were attached to the server at this time. Then, some day soon
thereafter I would take the "used" one to safehouse, and some day bring the
oldest one from the safehouse back to use, and attach it to the server
before it actually is needed. Very much like I move tapes between a
safehouse and an autoloader, making sure they are there when needed but not
forced to do it at certain preset day.

Basically, this is recycling the disk drives, like Bacula recycles volumes.
Both full and incremental jobs were written to same disk, and I would
propably like the system configured in a way that after a new disk is taken
into use (after the previous one was considered "used") the first jobs were
run as full backups.

How should this (or something even close to this) be set up? When the disks
were attached to the server, they would get different device names at
different times, and I wouldn't like to manually edit config files each
time. I'm sure someone has at least been thinking about this already, maybe
also implemented this. So, can Bacula currently handle this kind of setup in
a reasonable way?


Regards,
Timo



--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] FD Errors on Win2003

2009-01-10 Thread Kevin Keane
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 error: Network error with FD during Backup: ERR=Connection reset by 
>> peer
>> 09-Jan 03:03 smartlink-sd: Enterprise_Backup_OFFICE.2009-01-08_21.50.00 
>> Fatal error: append.c:159 Error reading data header from FD. ERR=Connection 
>> reset by peer
>> 09-Jan 03:03 smartlink-sd: Job write elapsed time = 01:34:39, Transfer rate 
>> = 9.796 M bytes/second
>> 09-Jan 03:03 smartlink-dir: Enterprise_Backup_OFFICE.2009-01-08_21.50.00 
>> Fatal error: No Job status returned from FD.
>> 09-Jan 03:03 smartlink-dir: Enterprise_Backup_OFFICE.2009-01-08_21.50.00 
>> Error: Bacula smartlink-dir 2.2.2 (06Aug07): 09-Jan-2009 03:03:35
>>   Build OS:   i386-pc-solaris2.10 solaris 5.10
>>   JobId:  858
>>   Job:Enterprise_Backup_OFFICE.2009-01-08_21.50.00
>>   Backup Level:   Full
>>   Client: "office-fd" Windows Server 2003,MVS,NT 5.2.3790
>>   FileSet:"officeFileSet" 2008-12-22 21:50:00
>>   Pool:   "ThursdayPool" (From Run pool override)
>>   Storage:"QUANTUM" (From Job resource)
>>   Scheduled time: 08-Jan-2009 21:50:00
>>   Start time: 09-Jan-2009 01:28:52
>>   End time:   09-Jan-2009 03:03:35
>>   Elapsed time:   1 hour 34 mins 43 secs
>>   Priority:   10
>>   FD Files Written:   0
>>   SD Files Written:   71,801
>>   FD Bytes Written:   0 (0 B)
>>   SD Bytes Written:   55,635,942,980 (55.63 GB)
>>   Rate:   0.0 KB/s
>>   Software Compression:   None
>>   VSS:no
>>   Encryption: no
>>   Volume name(s): GIOVEDI2
>>   Volume Session Id:  4
>>   Volume Session Time:1231408365
>>   Last Volume Bytes:  246,756,142,080 (246.7 GB)
>>   Non-fatal FD errors:0
>>   SD Errors:  0
>>   FD termination status:  Error
>>   SD termination status:  Error
>>   Termination:*** Backup Error ***
>> As you can see, the machine was backed up for almost 1 hour and half.
>> This happened 10-12 times in the last few months.
>> I already investigated any possible network problem or anything out of 
>> Bacula happening during the night (when backup runs). There doesn't seem to 
>> be any other problem.
>> What may be the cause?
>> thanx for any help.
>> Gabriele.
>>
>>
>> 
> Dear Gabriele, on one site of my customers, we encounter hard time with one 
> windows server.
> It has work nicely during 10 month. And suddently make lot's of error with 
> the bacula server.
> like yours.
>
> It's twin other server doesn't have any trouble.
> It's start happening after a big update on hardware (firmware) and software 
> from hp ( note that both server was updated at the
> same time )
>
> I've run long ping test between server, and what was comic is that during 
> some days it work with a 0% packet loss other days
> this was around 25% ...
>
> Later we reboot all network component, swithches, hubs, routers : and 
> everything goes nicely.
> Why : continue to be a mystery for me. But the result is here.
> >From that reboot time, we don't see any trouble.
>   
You may want to check out the Ethernet wiring: cable quality, cable 
lengths, any kinks or breaks in the cables, ...

At one of my customers, a couple of computers show very similar 
problems. Some days, they would run fast, other days they'd crawl. Are 
you by any chance using a managed hub? If so, you may want to log on to 
the hub and see if it can test the cables.

At my customers, it turned out that the Ethernet cables were just 
marginal. The managed hub actually showed the problem: those computers 
that worked well showed a definite cable length, usually between 30 and 
50 feet. Those that were marginal showed "undetermined cable length". I 
haven't tracked all of them down yet, but in at least one case, a large 
part of the problem that the Ethernet cable from the wall port to the 
workstation was extremely long and coiled up under the desk. I suspect 
that the cable quality also was pretty poor, and the cable was kinked in 
a few places. Some strands may well have broken, too. I only just 
replaced the cable yesterday, so it's too early to tell if it fixed the 
problem.

-- 
Kevin Keane
Owner
The NetTech
Turn your NetWORRY into a NetWORK!

Office: 866-642-7116
http://www.4nettech.com

This e-mail and attachments, if any, may contain confidential and/or 
proprietary information. Please be advised that the unauthorized use or 
disclosure of the information is strictly prohibited. The information herein is 
intended only for use by the intended recipient(s) named above. If you have 
received this transmission in error, p

Re: [Bacula-users] [Bacula-devel] Bacula 2.4.4 Released

2009-01-10 Thread Angel Alvarez
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 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 complete information on all changes.
> 
> 
> *
> * Miscellaneous *
> *
> 
> Added build target for su111
> 
> Added nobuild_rescue switch to supress building the rescue package
> 
> Removed libtermcap dependency for fc9
> 
> Added build target for su110
> 
> Added build target for fc9
> 
> File location changes for compatibility with FHS.
> 
> Force stripping of binaries for SuSE packages.
> 
> Fixed bug 1037.
> 
> Added nobuild_mtx switch to supress build of mtx package.
> 
> Added missing files now required by the rescue configure script.
> 
> Corrected dist target for rhel5.
> 
> Corrected QT dependency name for RedHat flavors.
> 
> Added fix for RHEL5 64 bit QT paths.
> 
> Added build target for su103.
> 
> Added build targets for rhel5 and clones.
> 
> Build target added for Scientific Linux (RHEL clone) thanks to Jon
> Peatfield.
> 
> Merged Otto Mueller's patch changing some directory locations for FHS
> compatibility
> but retaining the script directory as /etc/bacula.
> 
> gnome-console and wxconsole have been renamed to bgnome-console and
> bwx-console 
> respectively.
> 
> ***
> * New Build Option to Install in Single Directory *
> ***
> 
> A new build define has been added which will build packages that install
> most of the 
> files to /opt/bacula. Only the man pages, init scripts, logwatch and
> menu entries are 
> installed to the root filesystem.
> 
> --define "single_dir_install 1"
> 
> *
> * Buffer Overflow Error and Crash in fd *
> *
> 
> Fedora 8/9 now set -D_FORTIFY_SOURCE=2 as default compiler option. This 
> will probably be true on other platforms as they move to glibc >= 2.7.
> This 
> causes a false "buffer overflow detected" error and crash in bacula-fd
> and 
> other executables. 
> 
> To avoid this problem a workaround for Redhat platforms is to set the
> CFLAGS 
> in your ~/.rpmmacros file as follows:
> 
> # uncomment for bacula
> #%__global_cflags -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=0
> -fno-exceptions -fno-strict-aliasing -fno-rtti
> 
> For SuSE platforms set as follows in your ~/.rpmrc file:
> 
> optflags: i586 -O2 -g -m32 -march=i586 -mtune=i686 -fmessage-length=0
> -D_FORTIFY_SOURCE=0
> optflags: x86_64 -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=0
> 
> See the discussion thread on bacula-devel for more information:
> http://sourceforge.net/search/?ml_name=bacula-devel&type_of_search=mlists&group_id=50727&words=%22buffer+overflow+detected%22
> 
> ***
> * bat (Bacula Admin Tool) *
> ***
> 
> A new subpackage has been added for the new bat QT-based GUI
> administration tool.
> This requires QT >= 4.2
> 
> --define "build_bat 1"
> 
> If you encounter problems building the bat package on platforms where 
> you do have the proper QT4 support (QT >= 4.2) it may be necessary to 
> adjust your $QTDIR and $PATH variables. On Fedora 8/9 it was necessary
> to:
> 
> export QTDIR=/usr/lib/qt4;export PATH=/usr/lib/qt4/bin:$PATH;rpmbuild
> blah...
> 
> As of 2.4.4 this should no longer be necessary as we sniff the paths
> with pkgconfig.
> 
> ***
> * Gnome console dropped on some platforms *
> ***
> 
> The gconsole package has been dropped on older gnome platforms (gtk+ <
> 2.4). 
> Changes in the gnome api and code produced by Glade no longer build. 
> In addition, the tray monitor now fails to build on < 2.10 platforms.
> gconsole is now not built on the following platforms:
> rh7, rh8, rh9, rhel3 (and clones), fc1, fc3, fc4, mdk, su9, su10
> 
> 
> * Third party packager support *
> 
> 
> A new build tag added to support third party packagers to replace the
> information in the Packager: tag in the rpm. Invoking
> --define "contrib_packager Your Name "
> will substitute your packager identification.
> 
> Users interested in building packages for platforms not normally
> published
> should examine the platforms/contrib-rpm directory in the source code.
> 
> ***
> * Option to build client only *
> ***
> 
> A build define to build the client rpm package only added. This turns 
> off all database builds, gnome console and wxconsole.
> --define "build_c

Re: [Bacula-users] [Bacula-devel] Bacula 2.4.4 Released

2009-01-10 Thread Scott Barninger
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 complete information on all changes.


*
* Miscellaneous *
*

Added build target for su111

Added nobuild_rescue switch to supress building the rescue package

Removed libtermcap dependency for fc9

Added build target for su110

Added build target for fc9

File location changes for compatibility with FHS.

Force stripping of binaries for SuSE packages.

Fixed bug 1037.

Added nobuild_mtx switch to supress build of mtx package.

Added missing files now required by the rescue configure script.

Corrected dist target for rhel5.

Corrected QT dependency name for RedHat flavors.

Added fix for RHEL5 64 bit QT paths.

Added build target for su103.

Added build targets for rhel5 and clones.

Build target added for Scientific Linux (RHEL clone) thanks to Jon
Peatfield.

Merged Otto Mueller's patch changing some directory locations for FHS
compatibility
but retaining the script directory as /etc/bacula.

gnome-console and wxconsole have been renamed to bgnome-console and
bwx-console 
respectively.

***
* New Build Option to Install in Single Directory *
***

A new build define has been added which will build packages that install
most of the 
files to /opt/bacula. Only the man pages, init scripts, logwatch and
menu entries are 
installed to the root filesystem.

--define "single_dir_install 1"

*
* Buffer Overflow Error and Crash in fd *
*

Fedora 8/9 now set -D_FORTIFY_SOURCE=2 as default compiler option. This 
will probably be true on other platforms as they move to glibc >= 2.7.
This 
causes a false "buffer overflow detected" error and crash in bacula-fd
and 
other executables. 

To avoid this problem a workaround for Redhat platforms is to set the
CFLAGS 
in your ~/.rpmmacros file as follows:

# uncomment for bacula
#%__global_cflags -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=0
-fno-exceptions -fno-strict-aliasing -fno-rtti

For SuSE platforms set as follows in your ~/.rpmrc file:

optflags: i586 -O2 -g -m32 -march=i586 -mtune=i686 -fmessage-length=0
-D_FORTIFY_SOURCE=0
optflags: x86_64 -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=0

See the discussion thread on bacula-devel for more information:
http://sourceforge.net/search/?ml_name=bacula-devel&type_of_search=mlists&group_id=50727&words=%22buffer+overflow+detected%22

***
* bat (Bacula Admin Tool) *
***

A new subpackage has been added for the new bat QT-based GUI
administration tool.
This requires QT >= 4.2

--define "build_bat 1"

If you encounter problems building the bat package on platforms where 
you do have the proper QT4 support (QT >= 4.2) it may be necessary to 
adjust your $QTDIR and $PATH variables. On Fedora 8/9 it was necessary
to:

export QTDIR=/usr/lib/qt4;export PATH=/usr/lib/qt4/bin:$PATH;rpmbuild
blah...

As of 2.4.4 this should no longer be necessary as we sniff the paths
with pkgconfig.

***
* Gnome console dropped on some platforms *
***

The gconsole package has been dropped on older gnome platforms (gtk+ <
2.4). 
Changes in the gnome api and code produced by Glade no longer build. 
In addition, the tray monitor now fails to build on < 2.10 platforms.
gconsole is now not built on the following platforms:
rh7, rh8, rh9, rhel3 (and clones), fc1, fc3, fc4, mdk, su9, su10


* Third party packager support *


A new build tag added to support third party packagers to replace the
information in the Packager: tag in the rpm. Invoking
--define "contrib_packager Your Name "
will substitute your packager identification.

Users interested in building packages for platforms not normally
published
should examine the platforms/contrib-rpm directory in the source code.

***
* Option to build client only *
***

A build define to build the client rpm package only added. This turns 
off all database builds, gnome console and wxconsole.
--define "build_client_only 1"


* Python support added *


Support for compiling with python scripting support added. This is off 
by default but can be enabled with:
--define "build_python 1"
Released binary packages are built with python support.

***
* Database update *
***

The 2.x release requires an update to the bacula database structure
from version 9 to version 10. A pre-install routine has been added to

Re: [Bacula-users] FD Errors on Win2003

2009-01-10 Thread Kevin Keane
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 error: Network error with FD during Backup: ERR=Connection reset by 
>> peer
>> 09-Jan 03:03 smartlink-sd: Enterprise_Backup_OFFICE.2009-01-08_21.50.00 
>> Fatal error: append.c:159 Error reading data header from FD. ERR=Connection 
>> reset by peer
>> 09-Jan 03:03 smartlink-sd: Job write elapsed time = 01:34:39, Transfer rate 
>> = 9.796 M bytes/second
>> 09-Jan 03:03 smartlink-dir: Enterprise_Backup_OFFICE.2009-01-08_21.50.00 
>> Fatal error: No Job status returned from FD.
>> 09-Jan 03:03 smartlink-dir: Enterprise_Backup_OFFICE.2009-01-08_21.50.00 
>> Error: Bacula smartlink-dir 2.2.2 (06Aug07): 09-Jan-2009 03:03:35
>>   Build OS:   i386-pc-solaris2.10 solaris 5.10
>>   JobId:  858
>>   Job:Enterprise_Backup_OFFICE.2009-01-08_21.50.00
>>   Backup Level:   Full
>>   Client: "office-fd" Windows Server 2003,MVS,NT 5.2.3790
>>   FileSet:"officeFileSet" 2008-12-22 21:50:00
>>   Pool:   "ThursdayPool" (From Run pool override)
>>   Storage:"QUANTUM" (From Job resource)
>>   Scheduled time: 08-Jan-2009 21:50:00
>>   Start time: 09-Jan-2009 01:28:52
>>   End time:   09-Jan-2009 03:03:35
>>   Elapsed time:   1 hour 34 mins 43 secs
>>   Priority:   10
>>   FD Files Written:   0
>>   SD Files Written:   71,801
>>   FD Bytes Written:   0 (0 B)
>>   SD Bytes Written:   55,635,942,980 (55.63 GB)
>>   Rate:   0.0 KB/s
>>   Software Compression:   None
>>   VSS:no
>>   Encryption: no
>>   Volume name(s): GIOVEDI2
>>   Volume Session Id:  4
>>   Volume Session Time:1231408365
>>   Last Volume Bytes:  246,756,142,080 (246.7 GB)
>>   Non-fatal FD errors:0
>>   SD Errors:  0
>>   FD termination status:  Error
>>   SD termination status:  Error
>>   Termination:*** Backup Error ***
>> As you can see, the machine was backed up for almost 1 hour and half.
>> This happened 10-12 times in the last few months.
>> I already investigated any possible network problem or anything out of 
>> Bacula happening during the night (when backup runs). There doesn't seem to 
>> be any other problem.
>> What may be the cause?
>> thanx for any help.
>> Gabriele.
>>
>>
>> 
> Dear Gabriele, on one site of my customers, we encounter hard time with one 
> windows server.
> It has work nicely during 10 month. And suddently make lot's of error with 
> the bacula server.
> like yours.
>
> It's twin other server doesn't have any trouble.
> It's start happening after a big update on hardware (firmware) and software 
> from hp ( note that both server was updated at the
> same time )
>
> I've run long ping test between server, and what was comic is that during 
> some days it work with a 0% packet loss other days
> this was around 25% ...
>
> Later we reboot all network component, swithches, hubs, routers : and 
> everything goes nicely.
> Why : continue to be a mystery for me. But the result is here.
> >From that reboot time, we don't see any trouble.
>   
You may want to check out the Ethernet wiring: cable quality, cable 
lengths, any kinks or breaks in the cables, ...

At one of my customers, a couple of computers show very similar 
problems. Some days, they would run fast, other days they'd crawl. Are 
you by any chance using a managed hub? If so, you may want to log on to 
the hub and see if it can test the cables.

At my customers, it turned out that the Ethernet cables were just 
marginal. The managed hub actually showed the problem: those computers 
that worked well showed a definite cable length, usually between 30 and 
50 feet. Those that were marginal showed "undetermined cable length". I 
haven't tracked all of them down yet, but in at least one case, a large 
part of the problem that the Ethernet cable from the wall port to the 
workstation was extremely long and coiled up under the desk. I suspect 
that the cable quality also was pretty poor, and the cable was kinked in 
a few places. Some strands may well have broken, too. I only just 
replaced the cable yesterday, so it's too early to tell if it fixed the 
problem.

-- 
Kevin Keane
Owner
The NetTech
Turn your NetWORRY into a NetWORK!

Office: 866-642-7116
http://www.4nettech.com

This e-mail and attachments, if any, may contain confidential and/or 
proprietary information. Please be advised that the unauthorized use or 
disclosure of the information is strictly prohibited. The information herein is 
intended only for use by the intended recipient(s) named above. If you have 
received this transmission in error, p

Re: [Bacula-users] FD Errors on Win2003

2009-01-10 Thread Kevin Keane
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 error: Network error with FD during Backup: ERR=Connection reset by 
>> peer
>> 09-Jan 03:03 smartlink-sd: Enterprise_Backup_OFFICE.2009-01-08_21.50.00 
>> Fatal error: append.c:159 Error reading data header from FD. ERR=Connection 
>> reset by peer
>> 09-Jan 03:03 smartlink-sd: Job write elapsed time = 01:34:39, Transfer rate 
>> = 9.796 M bytes/second
>> 09-Jan 03:03 smartlink-dir: Enterprise_Backup_OFFICE.2009-01-08_21.50.00 
>> Fatal error: No Job status returned from FD.
>> 09-Jan 03:03 smartlink-dir: Enterprise_Backup_OFFICE.2009-01-08_21.50.00 
>> Error: Bacula smartlink-dir 2.2.2 (06Aug07): 09-Jan-2009 03:03:35
>>   Build OS:   i386-pc-solaris2.10 solaris 5.10
>>   JobId:  858
>>   Job:Enterprise_Backup_OFFICE.2009-01-08_21.50.00
>>   Backup Level:   Full
>>   Client: "office-fd" Windows Server 2003,MVS,NT 5.2.3790
>>   FileSet:"officeFileSet" 2008-12-22 21:50:00
>>   Pool:   "ThursdayPool" (From Run pool override)
>>   Storage:"QUANTUM" (From Job resource)
>>   Scheduled time: 08-Jan-2009 21:50:00
>>   Start time: 09-Jan-2009 01:28:52
>>   End time:   09-Jan-2009 03:03:35
>>   Elapsed time:   1 hour 34 mins 43 secs
>>   Priority:   10
>>   FD Files Written:   0
>>   SD Files Written:   71,801
>>   FD Bytes Written:   0 (0 B)
>>   SD Bytes Written:   55,635,942,980 (55.63 GB)
>>   Rate:   0.0 KB/s
>>   Software Compression:   None
>>   VSS:no
>>   Encryption: no
>>   Volume name(s): GIOVEDI2
>>   Volume Session Id:  4
>>   Volume Session Time:1231408365
>>   Last Volume Bytes:  246,756,142,080 (246.7 GB)
>>   Non-fatal FD errors:0
>>   SD Errors:  0
>>   FD termination status:  Error
>>   SD termination status:  Error
>>   Termination:*** Backup Error ***
>> As you can see, the machine was backed up for almost 1 hour and half.
>> This happened 10-12 times in the last few months.
>> I already investigated any possible network problem or anything out of 
>> Bacula happening during the night (when backup runs). There doesn't seem to 
>> be any other problem.
>> What may be the cause?
>> thanx for any help.
>> Gabriele.
>>
>>
>> 
> Dear Gabriele, on one site of my customers, we encounter hard time with one 
> windows server.
> It has work nicely during 10 month. And suddently make lot's of error with 
> the bacula server.
> like yours.
>
> It's twin other server doesn't have any trouble.
> It's start happening after a big update on hardware (firmware) and software 
> from hp ( note that both server was updated at the
> same time )
>
> I've run long ping test between server, and what was comic is that during 
> some days it work with a 0% packet loss other days
> this was around 25% ...
>
> Later we reboot all network component, swithches, hubs, routers : and 
> everything goes nicely.
> Why : continue to be a mystery for me. But the result is here.
> >From that reboot time, we don't see any trouble.
>   
You may want to check out the Ethernet wiring: cable quality, cable 
lengths, any kinks or breaks in the cables, ...

At one of my customers, a couple of computers show very similar 
problems. Some days, they would run fast, other days they'd crawl. Are 
you by any chance using a managed hub? If so, you may want to log on to 
the hub and see if it can test the cables.

At my customers, it turned out that the Ethernet cables were just 
marginal. The managed hub actually showed the problem: those computers 
that worked well showed a definite cable length, usually between 30 and 
50 feet. Those that were marginal showed "undetermined cable length". I 
haven't tracked all of them down yet, but in at least one case, a large 
part of the problem that the Ethernet cable from the wall port to the 
workstation was extremely long and coiled up under the desk. I suspect 
that the cable quality also was pretty poor, and the cable was kinked in 
a few places. Some strands may well have broken, too. I only just 
replaced the cable yesterday, so it's too early to tell if it fixed the 
problem.

-- 
Kevin Keane
Owner
The NetTech
Turn your NetWORRY into a NetWORK!

Office: 866-642-7116
http://www.4nettech.com

This e-mail and attachments, if any, may contain confidential and/or 
proprietary information. Please be advised that the unauthorized use or 
disclosure of the information is strictly prohibited. The information herein is 
intended only for use by the intended recipient(s) named above. If you have 
received this transmission in error, p

Re: [Bacula-users] scsi help

2009-01-10 Thread Michael Galloway
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) had done that years ago to fix this kind of inconsistency in the old 
> unit, so there doesn't have to be anything wrong with the new, replaced 
> unit.
> 
> I don't know this spesific hardware, so don't know if the addresses are set 
> with jumpers/switches, or thru some more modern configuration system. But 
> for me it just looks like this could be fixed with swapping the address 
> settings of the two drives.
> 
> 
> --
> TiN 

Yes! following your suggestion, i started digging aound in the library 
configuration, and
buried in the partition library panels was the scsi id settings, looks 'sane' 
now. thanks!

[r...@molbio ~]# lsscsi
[0:0:0:0]diskATA  TOSHIBA MK2035GS DK02  /dev/sda
[1:0:0:0]diskATA  TOSHIBA MK2035GS DK02  /dev/sdb
[4:0:0:0]diskAMCC 9650SE-16M DISK  3.08  /dev/sdc
[5:0:14:0]   tapeIBM  ULTRIUM-TD4  89B8  /dev/st0
[5:0:14:1]   mediumx SPECTRA  PYTHON   2000  -   
[5:0:15:0]   tapeIBM  ULTRIUM-TD4  89B8  /dev/st1

-- michael

--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] scsi help

2009-01-10 Thread Timo Neuvonen
>> 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 5 (Final)
>
> [r...@molbio ~]# uname -a
> Linux molbio.ornl.gov 2.6.18-8.1.14.el5 #1 SMP Thu Sep 27 19:05:32 EDT 
> 2007 x86_64 x86_64 x86_64 GNU/Linux
>
>
>> You could try looking here:
>>
>> ls -l /dev/st[0-9] /dev/nst[0-9]
>>
>> Look at the major and minor numbers.
>>
>
> [r...@molbio ~]# ls -l /dev/st*
> crw-rw 1 root disk 9,  0 Jan  9 07:28 /dev/st0
> crw-rw 1 root disk 9, 96 Jan  9 07:28 /dev/st0a
> crw-rw 1 root disk 9, 32 Jan  9 07:28 /dev/st0l
> crw-rw 1 root disk 9, 64 Jan  9 07:28 /dev/st0m
> crw-rw 1 root disk 9,  1 Jan  9 07:28 /dev/st1
> crw-rw 1 root disk 9, 97 Jan  9 07:28 /dev/st1a
> crw-rw 1 root disk 9, 33 Jan  9 07:28 /dev/st1l
> crw-rw 1 root disk 9, 65 Jan  9 07:28 /dev/st1m
> [r...@molbio ~]# ls -l /dev/nst*
> crw-rw 1 root disk 9, 128 Jan  9 07:28 /dev/nst0
> crw-rw 1 root disk 9, 224 Jan  9 07:28 /dev/nst0a
> crw-rw 1 root disk 9, 160 Jan  9 07:28 /dev/nst0l
> crw-rw 1 root disk 9, 192 Jan  9 07:28 /dev/nst0m
> crw-rw 1 root disk 9, 129 Jan  9 07:28 /dev/nst1
> crw-rw 1 root disk 9, 225 Jan  9 07:28 /dev/nst1a
> crw-rw 1 root disk 9, 161 Jan  9 07:28 /dev/nst1l
> crw-rw 1 root disk 9, 193 Jan  9 07:28 /dev/nst1m
>
> st0 and nst0 have lower minor numbers.
>
>
>> On linux, st? and nst? are created in order of discovery; while mtx is
>> talking about the library's internal concept of drive numbering.  Why 
>> they
>> are out of sync: various possibilities.  It could be that your SCSI buses
>> are wired up in an unusual way, although your lsscsi above looks OK.  Or
>> something in the O/S config...?
>>
>
> this same configuration worked as expected before i swapped out the 
> library (its
> been making backups for a year, then replaced library with factory 
> replacement).
>

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) had done that years ago to fix this kind of inconsistency in the old 
unit, so there doesn't have to be anything wrong with the new, replaced 
unit.

I don't know this spesific hardware, so don't know if the addresses are set 
with jumpers/switches, or thru some more modern configuration system. But 
for me it just looks like this could be fixed with swapping the address 
settings of the two drives.


--
TiN 



--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] How to do a systemstate backup?

2009-01-10 Thread Kevin Keane
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 without a hitch, on both xp and xp x64; I had to add the
> "start /w" bit in order to halt the script until ntbackup is done.
>
> andrea
>   
I spoke too soon. It worked that one time, but the next time a scheduled 
backup ran, it again didn't work. At least I know why now: I am running 
seven VMWare virtual machines but only have one host. The host also acts 
as director and SD. The server I was backing up is in one of the VMs and 
was simply overloaded, and the VSS writer timed out. The NTBackup log 
shows error 0x80042319. During my nightly backups, everything slows down 
to a crawl.

-- 
Kevin Keane
Owner
The NetTech
Turn your NetWORRY into a NetWORK!

Office: 866-642-7116
http://www.4nettech.com

This e-mail and attachments, if any, may contain confidential and/or 
proprietary information. Please be advised that the unauthorized use or 
disclosure of the information is strictly prohibited. The information herein is 
intended only for use by the intended recipient(s) named above. If you have 
received this transmission in error, please notify the sender immediately and 
permanently delete the e-mail and any copies, printouts or attachments thereof.


--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] FD Errors on Win2003

2009-01-10 Thread Bruno Friedmann
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 Backup: ERR=Connection reset by peer
> 09-Jan 03:03 smartlink-sd: Enterprise_Backup_OFFICE.2009-01-08_21.50.00 Fatal 
> error: append.c:159 Error reading data header from FD. ERR=Connection reset 
> by peer
> 09-Jan 03:03 smartlink-sd: Job write elapsed time = 01:34:39, Transfer rate = 
> 9.796 M bytes/second
> 09-Jan 03:03 smartlink-dir: Enterprise_Backup_OFFICE.2009-01-08_21.50.00 
> Fatal error: No Job status returned from FD.
> 09-Jan 03:03 smartlink-dir: Enterprise_Backup_OFFICE.2009-01-08_21.50.00 
> Error: Bacula smartlink-dir 2.2.2 (06Aug07): 09-Jan-2009 03:03:35
>   Build OS:   i386-pc-solaris2.10 solaris 5.10
>   JobId:  858
>   Job:Enterprise_Backup_OFFICE.2009-01-08_21.50.00
>   Backup Level:   Full
>   Client: "office-fd" Windows Server 2003,MVS,NT 5.2.3790
>   FileSet:"officeFileSet" 2008-12-22 21:50:00
>   Pool:   "ThursdayPool" (From Run pool override)
>   Storage:"QUANTUM" (From Job resource)
>   Scheduled time: 08-Jan-2009 21:50:00
>   Start time: 09-Jan-2009 01:28:52
>   End time:   09-Jan-2009 03:03:35
>   Elapsed time:   1 hour 34 mins 43 secs
>   Priority:   10
>   FD Files Written:   0
>   SD Files Written:   71,801
>   FD Bytes Written:   0 (0 B)
>   SD Bytes Written:   55,635,942,980 (55.63 GB)
>   Rate:   0.0 KB/s
>   Software Compression:   None
>   VSS:no
>   Encryption: no
>   Volume name(s): GIOVEDI2
>   Volume Session Id:  4
>   Volume Session Time:1231408365
>   Last Volume Bytes:  246,756,142,080 (246.7 GB)
>   Non-fatal FD errors:0
>   SD Errors:  0
>   FD termination status:  Error
>   SD termination status:  Error
>   Termination:*** Backup Error ***
> As you can see, the machine was backed up for almost 1 hour and half.
> This happened 10-12 times in the last few months.
> I already investigated any possible network problem or anything out of Bacula 
> happening during the night (when backup runs). There doesn't seem to be any 
> other problem.
> What may be the cause?
> thanx for any help.
> Gabriele.
> 
> 
Dear Gabriele, on one site of my customers, we encounter hard time with one 
windows server.
It has work nicely during 10 month. And suddently make lot's of error with the 
bacula server.
like yours.

It's twin other server doesn't have any trouble.
It's start happening after a big update on hardware (firmware) and software 
from hp ( note that both server was updated at the
same time )

I've run long ping test between server, and what was comic is that during some 
days it work with a 0% packet loss other days
this was around 25% ...

Later we reboot all network component, swithches, hubs, routers : and 
everything goes nicely.
Why : continue to be a mystery for me. But the result is here.
>From that reboot time, we don't see any trouble.



-- 

 Bruno Friedmann


--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users