Kern's ToDo List
- 13 August 2005
+ 22 October 2005
Major development:
Project Developer
Final items for 1.37 before release:
1. Fix bugs
-- Look at fixing restore status stats in SD.
+- Mount after manually unloading changer causes hang in SD
+- Check if ANSI tape labeling works with drive in
+ read-only mode.
+ > > btape: label.c:299 write_volume_label()
+ > > btape: label.c:302 Label type=0
+ > > btape: dev.c:648 rewind_dev fd=3 "VTS0" (/dev/tape0)
+ > > btape: label.c:530 Start create_volume_label()
+ > >
+ > > Volume Label:
+ > > Id : Bacula 1.0 immortal
+ > > VerNo : 11
+ > > VolName : 450340
+ > > PrevVolName :
+ > > VolFile : 0
+ > > LabelType : PRE_LABEL
+ > > LabelSize : 0
+ > > PoolName : Default
+ > > MediaType : VTS
+ > > PoolType : Backup
+ > > HostName : sysrmr.eia.doe.gov
+ > > btape: ansi_label.c:282 Write ANSI label type=2
+ > > 15-Sep 13:12 btape: btape Fatal error: ansi_label.c:303 Could not
+ > > write ANSI VOL1
+ > > label. ERR=Bad file descriptor
+
- Check "update slots=7 scan storage=DLT drive=0" with
non-bacula tape in the drive.
- --without-openssl breaks at least on Solaris.
-- Figure out how to package gui, and rescue programs.
-- Test TLS.
- Arno had to do -- to get update slots=x to work
UPDATE Media SET InChanger=0,Slot=0 WHERE InChanger>0 AND Slot>0; (MySQL)
-- Add recycle event.
-- Add scratch pool event.
-- Implement NeedVolume event
-- Add Win32 FileSet definition somewhere
-
-
Document:
-- datadir for po files.
-- AM_GNU_GETTEXT finds the library if you specify
- --with-libintl-prefix
+- Does ClientRunAfterJob fail the job on a bad return code?
- Document cleaning up the spool files:
db, pid, state, bsr, mail, conmsg, spool
- Document the multiple-drive-changer.txt script.
- Pruning with Admin job.
-- Restore of all files for a Job or set of jobs even if the file
- records have been removed from the catalog.
+- Does WildFile match against full name? Doc.
For 1.39:
+- Add a new Autochanger directive "Global lock = yes|no"
+ that provides a global lock on calling mtx-changer so
+ that multiple autochanger definitions can reference
+ the same physical autochanger.
+- Look at -D_FORTIFY_SOURCE=2
+- Close STDOUT if debug_level == 0
+- Add recycle event.
+- Add scratch pool event.
+- Implement NeedVolume event
+- Add Win32 FileSet definition somewhere
+- Look at fixing restore status stats in SD.
+- Make selection of Database used in restore correspond to
+ client.
+- implement a mode that says when a hard read error is
+ encountered, read many times (as it currently does), and if the
+ block cannot be read, skip to the next block, and try again. If
+ that fails, skip to the next file and try again, ...
+- Add ACL to restore only to original location.
+- Add a recursive mark command (rmark) to restore.
+- "Minimum Job Interval = nnn" sets minimum interval between Jobs
+ of the same level and does not permit multiple simultaneous
+ running of that Job (i.e. lets any previous invocation finish
+ before doing Interval testing).
+- Look at simplifying File exclusions.
+- Fix store_yesno to be store_bitmask.
+- New directive "Delete purged Volumes"
- new pool XXX with ScratchPoolId = MyScratchPool's PoolId and
let it fill itself, and RecyclePoolId = XXX's PoolId so I can
see if it become stable and I just have to supervise
} else {
Dmsg1(200, "Restore node: %s\n", attr->ofname);
if (mknod(attr->ofname, attr->statp.st_mode, attr->statp.st_rdev) != 0 && errno != EEXIST) {
+- From: Arunav Mandal <amandal@trolltech.com>
+ 1. When jobs are running and bacula for some reason crashes or if I do a
+ restart it remembers and jobs it was running before it crashed or restarted
+ as of now I loose all jobs if I restart it.
+
+ 2. When spooling and in the midway if client is disconnected for instance a
+ laptop bacula completely discard the spool. It will be nice if it can write
+ that spool to tape so there will be some backups for that client if not all.
+
+ 3. We have around 150 clients machines it will be nice to have a option to
+ upgrade all the client machines bacula version automatically.
+
+ 4. Atleast one connection should be reserved for the bconsole so at heavy load
+ I should connect to the director via bconsole which at sometimes I can't
+
+ 5. Another most important feature that is missing, say at 10am I manually
+ started backup of client abc and it was a full backup since client abc has
+ no backup history and at 10.30am bacula again automatically started backup of
+ client abc as that was in the schedule. So now we have 2 multiple Full
+ backups of the same client and if we again try to start a full backup of
+ client backup abc bacula won't complain. That should be fixed.
- Fix bpipe.c so that it does not modify results pointer.
***FIXME*** calling sequence should be changed.
wants a Volume that is released but in another drive --
chaos.
- Run the regression scripts on Solaris and FreeBSD
+- Figure out how to package gui, and rescue programs.
+- Add a .dir command to restore tree code to eliminate the problem
projects / bacula / bacula / blobdiff