Your message dated Mon, 30 Jun 2008 10:08:17 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug #436407
has caused the Debian Bug report #436407,
regarding bacula: Uncompleted(Still active, Failed, Errored, Canceled) jobs
force Level=full when Incremental.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
436407: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=436407
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: bacula-director-sqlite3
Version: 2.0.3-4
Severity: normal
I understand this is a bit obscure and most certainly avoidable as
such avoidance is likely the best option. However this makes Amanda
look comparable to Bacula, in that to avoid this problem a Job must be
split into smaller more manageable sections.
When running a full backup that may take a long time(for example 3
days) to complete, Incremental jobs started during that time are
converted to Full. This was not as trouble some as you might imagine,
but it did not complete successfully and never would have.
First off the long running Job should be forcefully completed, with a
warning. It's no longer possible to backup the data that it was
assigned(that time has literally passed), actually now that I think
about it there may be an option I just need to turn on for this.
Recovering from this should not be as easy as just kicking off an
Incremental, albeit this would(should) pickup the missed files. After
a successful completion every thing should be fine. However I'd like
there to be a Run Level dedicated to this task, just like an
Incremental, but big enough for more then half a Full. These Recovery
backups will be much bigger then normal Incremental, even though they
should be created using the same(or much the same) code.
Since I'm off creating new levels of Jobs, why not defragment an
obsolete Full backup(with a read/compair, ALA rsync) and given more
then %20 space reduction, repack along with the new data. This would
conserve network bandwidth(rsync) from the fd to the sd, and allow a
Full backup to be reused/refreshed. When you would normally overwrite
a full backup with another full backup, you can "Freshen" instead.
So there you have it two new levels. One that's Incremental, but
completes and finalizes like a Full and An Differential/Incremental
that's as refreshing as a Full.
-- System Information:
Debian Release: lenny/sid
APT prefers stable
APT policy: (990, 'stable'), (800, 'testing'), (550, 'unstable'), (510,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.21-2-k7 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages bacula-director-sqlite3 depends on:
ii bacula-director-common 2.0.3-4 Network backup, recovery and verif
ii debconf [debconf-2.0] 1.5.13 Debian configuration management sy
ii libc6 2.6-2 GNU C Library: Shared libraries
ii libgcc1 1:4.2-20070627-1 GCC support library
ii libsqlite3-0 3.3.17-1 SQLite 3 shared library
ii libssl0.9.8 0.9.8e-5 SSL shared libraries
ii libstdc++6 4.2-20070627-1 The GNU Standard C++ Library v3
ii libwrap0 7.6.dbs-13 Wietse Venema's TCP wrappers libra
ii python2.4 2.4.4-4 An interactive high-level object-o
ii sqlite3 3.3.17-1 A command line interface for SQLit
bacula-director-sqlite3 recommends no packages.
-- debconf information:
bacula-director-sqlite3/create_tables: true
bacula-director-sqlite3/remove_catalog_on_purge: false
--- End Message ---
--- Begin Message ---
Hi Mike,
I got your Bacula bug report #436407 from last August. It requests a
number of changes that would be pretty core to Bacula, rather than
Debian. In addition, there are likely reasons that some poeple would
not want the changes to be made. Would you be willing to talk about
this with the Bacula developers directly, on their mailing list?
I do not believe this is a bug in Bacula (that is, that it is behaving
in a manner other than documented or intenteded).
-- John
--- End Message ---
