now that all of my backup jobs are correctly compressed, I'd
like to check compression percentage globally, but there is
no way to get this value from the database, only in the
mails sent by the director :-( It could be interesting to
have it in the database ?
have a nice day !
-
>Should work fine, and is preferable to putting the signature
>at the end of the fileset, which might cause the FD to pickup
>walk off the end of the options into a bunch of garbage with possible
>fatal results.
>
>You might even put the "signature", "onefs" pair at the end o
> i'm using the deb's from Jose Luis on debian 4.0/etch.
> is this equal to your setup, Sebastien?
no, self-compiled
> Did excluding work with your filesets?
these filesets don't use exclusion, but some
others do, and they work (if not, my storage
servers would be full :)
--
Sébastien Guilba
> moving the "compression = GZIP" to the last include-line helps:
>
>
> garwein.gs.ic3s.de-fd: job.c:1034 Fileset: O SeZ6
> garwein.gs.ic3s.de-fd: job.c:663 O SeZ6
> garwein.gs.ic3s.de-fd: job.c:1002 Compression level=6
>
> grrr ... :)
?? no compression for me with the following fileset :
Fil
I've partially upgraded to bacula2 (director and sd), all of
my 1.38 fd's backups report software compression, and all recent
fd's backups (1.39 and 2.0) report no software compression. I've
verified the Options { } order trick in Fileset resource, all
configuration files are almost the same :
Fi
Dir/Storage/Catalog:
- Debian Sarge dual Xeon 2.8 Ghz
- 2 Gb of RAM.
- Backups stored on
- 16x300 Gb SATA HDDs on 3ware RAID , 2.7 Tb usable
- Overland Neo2000 LTO-3 (30 slots)
- 4 Intel Gigabit interfaces
- MySQL 5.0.22 (1.7 Gb database, 15M rows, full InnoDB)
- Bacula 1.38.
> Please let us know the results of your testing.
Works fine, deeply nested path fully backuped.
The only thing I have to investigate is why my
software compression options are not used
("Software Compression: None" in the mail report)
whereas it works flawlessly on all my other boxes
have a
> You need to read the ReleaseNotes *very* carefully as there are a number of
> changes/difficult areas to get it to load the first time mainly if you have
> an older version of Bacula running.
>
> The Win32 section of the online development manual also covers the
> installation.
sorry, mea c
> I have just released Bacula BETA 1.39.24.20061002 source and the Win32
> binaries to Source Forge. This is very likely to be the last beta release or
> next to last release before the official 1.40 production release in the
> second half of November.
anyone facing 'the bacula service could
>> A fairly recent version of 1.38.x is in the Debian unstable (or perhaps it
>> is
>> testing, I forget) -- it is possibly updated to version 1.38.11 by now, so
>> there is no need to compile Bacula, unless you have an aversion to
>> "unstable" (poor choice of names IMO).
>
> I rader compile
> I have released the source tar file for Bacula BETA 1.39.20-20060822 to the
> Bacula Source Forge bacula-beta release area. I have also released a
> cross-compiled Win32 1.39.20 installer. The major differenced between this
> beta release and the previous one are:
I can't find no win32 bet
> Sorry, I thought one thing and wrote another. It's not
> InnoDB - it's MyISAM. It's the adequate storage engine
> for Bacula. Regards,
and why no innodb ?? works fine for me, big tables, simpler
memory model than innodb (no tons of buffers to tune), and
negligeable performance hit...
have a ni
In addition to the other comments, if I am not mistaken, there is a Problems
section in the MySQL chapter of the manual that points you off to the MySQL
documentation on this.
This has nothing to do with you, Eric, but since we are on the subject of
MySQL timeouts: one user troubled by this
13 matches
Mail list logo
