Hello,
The newer versions of the bacula file daemon do not work properly on
pre-unicode windows versions - the filenames became unusable when written to
the 2.2.5 server catalog, where all non-utf characters were stripped out of
the filename. I'm speaking specifically about Hebrew file names but
In message [EMAIL PROTECTED] you wrote:
Curious as to why tar worked when btape did not, I found this. For
portability reasons, tar appears to always use a physical block size of
512 bytes. See
http://www.gnu.org/software/tar/manual/html_section/tar_73.html. Perhaps
that explains the
On 10/24/07, Michael Short [EMAIL PROTECTED] wrote:
Just make sure that the files have an older creation/modification date
and bacula will ignore them.
thx
Is there a way to configure bacula to only backup files which have a changed
mtime?
On Sun, October 28, 2007 5:54 pm, Martin Vogt wrote:
Is there a way to configure bacula to only backup files which have a
changed
mtime?
mtimeonly=yes—no If enabled, tells the Client that the selection of
#64257;les
during Incremental and Di#64256;erential backups should based only on
the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Search the list. IIRC, there is a minimum PostgreSQL version associated
with Bacula 2.2.x
Disaster wrote:
Dear all,
after an upgrade I get those error (via Bacula daemon message). I've
upgraded from 1.36 to 2.2.5 on gentoo running postgres (I've
