8 Data encryption Meno Abels (see projects)
9 Communication encryption Meno Abels
10 Version 1.35 Kern (see below)
11 ========================================================
13 1.37 Items to do for release:
17 - Tell the "restore" user when browsing is no longer possible.
18 - Write non-optimized bsrs from the JobMedia and Media records,
19 even after Files are pruned.
20 - Document that Bootstrap files can be written with cataloging
22 - Add dump of VolSessionId/Time and FileIndex with bls.
23 - Look at adding full Volume and Pool information to a Volume.
24 - Promote to Full = Time period
25 - Scratch Pool where the volumes can be re-assigned to any Pool.
26 - Update StartTime if job held in Job Queue.
27 - Despool attributes simultaneously with data in a separate
28 thread, rejoined at end of data spooling.
29 - Implement Files/Bytes,... stats for restore job.
30 - Implement Total Bytes Written, ... for restore job.
31 - Check dates entered by user for correctness (month/day/... ranges)
32 - Compress restore Volume listing by date and first file.
33 - Add Pool/Storage override regression test.
34 - Add delete JobId to regression.
35 - Add bscan to four-concurrent-jobs regression.
36 - Look at patches/bacula_db.b2z postgresql that loops during restore.
38 - Add IPv6 to regression
39 - Perhaps add read/write programs and/or plugins to FileSets.
40 - How to handle backing up portables ...
41 - Add "Rerun failed levels = yes/no" to Job resource.
42 - Add some sort of guaranteed Interval for upgrading jobs.
43 - Can we write the state file after every job terminates? On Win32
44 the system crashes and the state file is not updated.
47 Documentation to do: (any release a little bit at a time)
48 - Doc to do unmount before removing magazine.
49 - Alternative to static linking "ldd prog" save all binaries listed,
50 restore them and point LD_LIBRARY_PATH to them.
51 - Document add "</dev/null >/dev/null 2>&1" to the bacula-fd command line
52 - Document query file format.
53 - Add more documentation for bsr files.
54 - Document problems with Verify and pruning.
55 - Document how to use multiple databases.
56 - VXA drives have a "cleaning required"
57 indicator, but Exabyte recommends preventive cleaning after every 75
60 In this context, it should be noted that Exabyte has a command-line
61 vxatool utility available for free download. (The current version is
62 vxatool-3.72.) It can get diagnostic info, read, write and erase tapes,
63 test the drive, unload tapes, change drive settings, flash new firmware,
65 Of particular interest in this context is that vxatool <device> -i will
66 report, among other details, the time since last cleaning in tape motion
67 minutes. This information can be retrieved (and settings changed, for
68 that matter) through the generic-SCSI device even when Bacula has the
69 regular tape device locked. (Needless to say, I don't recommend
70 changing tape settings while a job is running.)
71 - Lookup HP cleaning recommendations.
72 - Lookup HP tape replacement recommendations (see trouble shooting autochanger)
73 - Document doing table repair
76 Testing to do: (painful)
79 For 1.37 Testing/Documentation:
80 - Add bandwidth limiting.
81 - Add acks every once and a while from the SD to keep
82 the line from timing out.
83 - When an error in input occurs and conio beeps, you can back
84 up through the prompt.
85 - Detect fixed tape block mode during positioning by looking at
86 block numbers in btape "test". Possibly adjust in Bacula.
87 - Fix list volumes to output volume retention in some other
88 units, perhaps via a directive.
89 - If opening a tape in read/write mode fails attempt to open
90 it in read-only mode, and mark the tape for read only.
91 - Add a read-only mode to the mount option.
92 - Allow Simultaneous Priorities = yes => run up to Max concurrent jobs even
93 with multiple priorities.
94 - Add db check test to regression. Test each function like delete,
96 - If you use restore replace=never, the directory attributes for
97 non-existent directories will not be restored properly.
99 - see lzma401.zip in others directory for new compression
101 - Minimal autochanger handling in Bacula and in btape.
102 - Look into how tar does not save sockets and the possiblity of
103 not saving them in Bacula (Martin Simmons reported this).
104 - Add All Local Partitions = yes to new style saves.
105 - localmounts=`awk '/ext/ { print $2 }' /proc/mounts` # or whatever
106 find $localmounts -xdev -type s -ls
107 - Fix restore jobs so that multiple jobs can run if they
108 are not using the same tape(s).
109 - Allow the user to select JobType for manual pruning/purging.
110 - Look at adding Client run command that will use the
111 port opened by the client.
112 - bscan does not put first of two volumes back with all info in
114 - Implement the FreeBSD nodump flag in chflags.
115 - Figure out how to make named console messages go only to that
116 console and to the non-restricted console (new console class?).
117 - Make restricted console prompt for password if *ask* is set or
118 perhaps if password is undefined.
119 - Implement "from ISO-date/time every x hours/days/weeks/months" in
121 ==== from Marc Schoechlin
122 - the help-command should be more verbose
123 (it should explain the paramters of the different
125 -> it´s time-comsuming to consult the manual anytime
126 you need a special parameter
127 -> maybe it´s more easy to maintain this, if the
128 descriptions of that commands are outsourced to
130 - the cd-command should allow complete paths
131 i.e. cd /foo/bar/foo/bar
132 -> if a customer mails me the path to a certain file,
133 it´s faster to enter the specified directory
134 - if the password is not configured in bconsole.conf
135 you should be asked for it.
136 -> sometimes you like to do restore on a customer-machine
137 which shouldn´t know the password for bacula.
138 -> adding the password to the file favours admins
139 to forget to remove the password after usage
141 the protection of that file is less important
142 - long-listed-output of commands should be scrollable
143 like the unix more/less-command does
144 -> if someone runs 200 and more machines, the lists could
145 be a little long and complex
146 - command-output should be shown column by column
147 to reduce scrolling and to increase clarity
149 - lsmark should list the selected files with full
151 - wildcards for selecting and file and directories would be nice
152 - any actions should be interuptable with STRG+C
153 - command-expansion would be pretty cool
155 - Compaction of Disk space by "migrating" Volumes that have pruned
156 Jobs (what criteria? size, #jobs, time).
157 - Add prune all command
158 - Document fact that purge can destroy a part of a restore by purging
159 one volume while others remain valid -- perhaps mark Jobs.
160 - Add multiple-media-types.txt
161 - look at mxt-changer.html
162 - Make ? do a help command (no return needed).
163 - Implement restore directory.
164 - Document streams and how to implement them.
165 - Try not to re-backup a file if a new hard link is added.
166 - Add feature to backup hard links only, but not the data.
167 - Fix stream handling to be simpler.
168 - Add Priority and Bootstrap to Run a Job.
169 - Eliminate Restore "Run Restore Job" prompt by allowing new "run command
171 - Remove View FileSet button from Run a Job dialog.
172 - Handle prompt for restore job at end of Restore command.
173 - Add display of total selected files to Restore window.
174 - Add tree pane to left of window.
175 - Add progress meter.
176 - Max wait time or max run time causes seg fault -- see runtime-bug.txt
177 - Document writing to a CD/DVD with Bacula.
178 - Add a "base" package to the window installer for pthreadsVCE.dll
179 which is needed by all packages.
180 - Add message to user to check for fixed block size when the forward
181 space test fails in btape.
182 - When unmarking a directory check if all files below are unmarked and
183 then remove the + flag -- in the restore tree.
184 - Possibly implement: Action = Unmount Device="TapeDrive1" in Admin jobs.
185 - Setup lrrd graphs: (http://www.linpro.no/projects/lrrd/) Mike Acar.
186 - Revisit the question of multiple Volumes (disk) on a single device.
187 - Add a block copy option to bcopy.
188 - Investigate adding Mac Resource Forks.
189 - Finish work on Gnome restore GUI.
190 - Fix "llist jobid=xx" where no fileset or client exists.
192 it seems to be complaining about 12:00pm which should be a valid 12
193 hour time. I changed the time to 11:59am and everything works fine.
194 Also 12:00am works fine. 0:00pm also works (which I don't think
195 should). None of the values 12:00pm - 12:59pm work for that matter.
196 - Add level to estimate command.
197 - For each job type (Admin, Restore, ...) require only the really necessary
199 - Fix option 2 of restore -- list where file is backed up -- require Client,
200 then list last 20 backups.
201 - Pass Director resource name as an option to the Console.
202 - Add a "batch" mode to the Console (no unsolicited queries, ...).
203 - Add a .list all files in the restore tree (probably also a list all files)
204 Do both a long and short form.
205 - Allow browsing the catalog to see all versions of a file (with
206 stat data on each file).
207 - Restore attributes of directory if replace=never set but directory
209 - Use SHA1 on authentication if possible.
210 - See comtest-xxx.zip for Windows code to talk to USB.
211 - Add Events and Perl scripting.
212 - Add John's appended files:
213 Appended = { /files/server/logs/http/*log }
214 and such files would be treated as follows.On a FULL backup, they would
215 be backed up like any other file.On an INCREMENTAL backup, where a
216 previous INCREMENTAL or FULL was already in thecatalogue and the length
217 of the file wasgreater than the length of the last backup, only thedata
218 added since the last backup will be dumped.On an INCREMENTAL backup, if
219 the length of the file is less than thelength of the file with the same
220 name last backed up, the completefile is dumped.On Windows systems, with
221 creation date of files, we can be evensmarter about this and not count
222 entirely upon the length.On a restore, the full and all incrementals
223 since it will beapplied in sequence to restore the file.
224 - Add a regression test for dbcheck.
225 - Add disk seeking on restore. - Allow
226 for optional cancelling of SD and FD in case DIR
227 gets a fatal error. Requested by Jesse Guardiani <jesse@wingnet.net>
228 - Add "limit=n" for "list jobs"
229 - Check new HAVE_WIN32 open bits.
230 - Check if the tape has moved before writing.
231 - Handling removable disks -- see below:
232 - Keep track of tape use time, and report when cleaning is necessary.
233 - Add FromClient and ToClient keywords on restore command (or
234 BackupClient RestoreClient).
235 - Implement a JobSet, which groups any number of jobs. If the
236 JobSet is started, all the jobs are started together.
237 Allow Pool, Level, and Schedule overrides.
238 - Enhance cancel to timeout BSOCK packets after a specific delay.
239 - Do scheduling by UTC using gmtime_r() in run_conf, scheduler, and
240 ua_status.!!! Thanks to Alan Brown for this tip.
241 - Look at updating Volume Jobs so that Max Volume Jobs = 1 will work
242 correctly for multiple simultaneous jobs.
243 - Correct code so that FileSet MD5 is calculated for < and | filename
245 - Implement the Media record flag that indicates that the Volume does disk
247 - Implement VolAddr, which is used when Volume is addressed like a disk,
248 and form it from VolFile and VolBlock.
249 - Make multiple restore jobs for multiple media types specifying
250 the proper storage type.
251 - Implement MediaType keyword in bsr?
252 - Fix fast block rejection (stored/read_record.c:118). It passes a null
253 pointer (rec) to try_repositioning().
254 - Look at extracting Win data from BackupRead.
255 - Implement RestoreJobRetention? Maybe better "JobRetention" in a Job,
256 which would take precidence over the Catalog "JobRetention".
257 - Implement Label Format in Add and Label console commands.
258 - Possibly up network buffers to 65K. Put on variable.
259 - Put email tape request delays on one or more variables. User wants
260 to cancel the job after a certain time interval. Maximum Mount Wait?
261 - Job, Client, Device, Pool, or Volume?
262 Is it possible to make this a directive which is *optional* in multiple
263 resources, like Level? If so, I think I'd make it an optional directive
264 in Job, Client, and Pool, with precedence such that Job overrides Client
265 which in turn overrides Pool.
267 - New Storage specifications:
268 - Want to write to multiple storage devices simultaneously
269 - Want to write to multiple storage devices sequentially (in one job)
270 - Want to read/write simultaneously
271 - Key is MediaType -- it must match
273 Passed to SD as a sort of BSR record called Storage Specification
277 MediaType -> Next MediaType
279 Device -> Next Device
281 Allow multiple Storage specifications
289 Allow Multiple Pool specifications (note, Pool currently
291 Allow Multiple MediaType specifications in Dir conf
292 Allow Multiple Device specifications in Dir conf
293 Perhaps keep this in a single SSR
294 Tie a Volume to a specific device by using a MediaType that
295 is contained in only one device.
296 In SD allow Device to have Multiple MediaTypes
298 - Look at www.nu2.nu/pebuilder as a helper for full windows
300 - Ideas from Jerry Scharf:
301 First let's point out some big pluses that bacula has for this
303 more importantly it's active. Thank you so much for that
304 even more important, it's not flaky
305 it has an open access catalog, opening many possibilities
306 it's pushing toward heterogeneous systems capability
308 Macintosh file client
309 macs are an interesting niche, but I fear a server is a rathole
310 working bare iron recovery for windows
311 the option for inc/diff backups not reset on fileset revision
312 a) use both change and inode update time against base time
313 b) do the full catalog check (expensive but accurate)
314 sizing guide (how much system is needed to back up N systems/files)
315 consultants on using bacula in building a disaster recovery system
317 or how to get at fancy things that one could do with bacula
318 logwatch code for bacula logs (or similar)
319 linux distro inclusion of bacula (brings good and bad, but necessary)
320 win2k/XP server capability (icky but you asked)
321 support for Oracle database ??
323 - Look at adding SQL server and Exchange support for Windows.
324 - Each DVD-RAM disk would be a volume, just like each tape is
325 a volume. It's a 4.7GB media with random access, but there's nothing about
326 it that I can see that makes it so different than a tape from bacula's
327 perspective. Why couldn't I back up to a bare floppy as a volume (ignoring
329 - Make dev->file and dev->block_num signed integers so that -1 can
330 be an invalid value which happens with BSR.
331 - Create VolAddr for disk files in place of VolFile and VolBlock. This
332 is needed to properly specify ranges.
333 - Add progress of files/bytes to SD and FD.
334 - Print warning message if FileId > 4 billion
335 - do a "messages" before the first prompt in Console
336 - Add a date and time stamp at the beginning of every line in the
337 Job report (Volker Sauer).
338 - Client does not show busy during Estimate command.
339 - Implement Console mtx commands.
340 - Implement a Mount Command and an Unmount Command where
341 the users could specify a system command to be performed
342 to do the mount, after which Bacula could attempt to
343 read the device. This is for Removeable media such as a CDROM.
344 - Most likely, this mount command would be invoked explicitly
345 by the user using the current Console "mount" and "unmount"
346 commands -- the Storage Daemon would do the right thing
347 depending on the exact nature of the device.
348 - As with tape drives, when Bacula wanted a new removable
349 disk mounted, it would unmount the old one, and send a message
350 to the user, who would then use "mount" as described above
351 once he had actually inserted the disk.
352 - Implement dump/print label to UA
353 - Spool to disk only when the tape is full, then when a tape is hung move
355 - bextract is sending everything to the log file ****FIXME****
356 - Allow multiple Storage specifications (or multiple names on
357 a single Storage specification) in the Job record. Thus a job
358 can be backed up to a number of storage devices.
359 - Implement some way for the File daemon to contact the Director
360 to start a job or pass its DHCP obtained IP number.
361 - Implement a query tape prompt/replace feature for a console
362 - Copy console @ code to gnome2-console
363 - Make AES the only encryption algorithm see
364 http://csrc.nist.gov/CryptoToolkit/aes/). It's
365 an officially adopted standard, has survived peer
366 review, and provides keys up to 256 bits.
367 - Take a careful look at SetACL http://setacl.sourceforge.net
368 - Take a careful look at Level for the estimate command, maybe make
369 it a command line option.
370 - Add Volume name to "I cannot write on this volume because"
371 - Make tree walk routines like cd, ls, ... more user friendly
372 by handling spaces better.
373 - Make sure that Bacula rechecks the tape after the 20 min wait.
374 - Set IO_NOWAIT on Bacula TCP/IP packets.
375 - Try doing a raw partition backup and restore by mounting a
378 Yes, it would allow to highly automatic the request for new tapes. If a
379 tape is empty, bacula reads the barcodes (native or simulated), and if
380 an unused tape is found, it runs the label command with all the
381 necessary parameters.
383 By the way can bacula automatically "move" an empty/purged volume say
384 in the "short" pool to the "long" pool if this pool runs out of volume
386 - What to do about "list files job=xxx".
387 - Make Dmsg look at global before calling subroutine.
388 - Get and test MySQL 4.0
389 - Look at how fuser works and /proc/PID/fd that is how Nic found the
390 file descriptor leak in Bacula.
391 - Implement WrapCounters in Counters.
392 - Add heartbeat from FD to SD if hb interval expires.
393 - Can we dynamically change FileSets?
394 - If pool specified to label command and Label Format is specified,
395 automatically generate the Volume name.
396 - Why can't SQL do the filename sort for restore?
397 - Look into Microsoft Volume Shadowcopy Service VSS for backing
398 up system state components (Active Directory, System Volume, ...)
399 - Add ExhautiveRestoreSearch
400 - Look at the possibility of loading only the necessary
401 data into the restore tree (i.e. do it one directory at a
402 time as the user walks through the tree).
403 - Possibly use the hash code if the user selects all for a restore command.
404 - Fix "restore all" to bypass building the tree.
405 - Prohibit backing up archive device (findlib/find_one.c:128)
406 - Implement Release Device in the Job resource to unmount a drive.
407 - Implement Acquire Device in the Job resource to mount a drive,
408 be sure this works with admin jobs so that the user can get
409 prompted to insert the correct tape. Possibly some way to say to
410 run the job but don't save the files.
411 - Make things like list where a file is saved case independent for
414 - Use autochanger to handle multiple devices.
415 - Add SuSE install doc to list.
416 - Check and rechedk "Invalid block number"
417 - User wants to NOT backup up certain big files (email files).
418 - Maybe remove multiple simultaneous devices code in SD.
419 - On Windows with very long path names, it may be impossible to create
420 a file (and thus restore it) because the total length is too long.
421 We must cd into the directory then create the file without the
423 - Implement a Recycle command
424 - Add client name to cram-md5 challenge so Director can immediately
425 verify if it is the correct client.
426 - Audit all UA commands to ensure that we always prompt where possible.
427 - Make bootstrap filename unique.
428 - Test a second language e.g. french.
429 - Start working on Base jobs.
430 - Implement UnsavedFiles DB record.
431 - Implement argc/argv for daemon command line scanning using table driven
433 - From Phil Stracchino:
434 It would probably be a per-client option, and would be called
435 something like, say, "Automatically purge obsoleted jobs". What it
436 would do is, when you successfully complete a Differential backup of a
437 client, it would automatically purge all Incremental backups for that
438 client that are rendered redundant by that Differential. Likewise,
439 when a Full backup on a client completed, it would automatically purge
440 all Differential and Incremental jobs obsoleted by that Full backup.
441 This would let people minimize the number of tapes they're keeping on
442 hand without having to master the art of retention times.
443 - Implement a M_SECURITY message class.
444 - When doing a Backup send all attributes back to the Director, who
445 would then figure out what files have been deleted.
446 - Currently in mount.c:236 the SD simply creates a Volume. It should have
447 explicit permission to do so. It should also mark the tape in error
448 if there is an error.
449 - SD Bytes Read is wrong.
450 - Investigate doing RAW backup of Win32 partition.
451 - Cancel waiting for Client connect in SD if FD goes away.
453 - Implement timeout in response() when it should come quickly.
454 - Implement console @echo command.
455 - Implement a Slot priority (loaded/not loaded).
456 - Implement "vacation" Incremental only saves.
457 - Implement single pane restore (much like the Gftp panes).
458 - Implement Automatic Mount even in operator wait.
459 - Implement create "FileSet"?
460 - Implement restore "current system", but take all files without
461 doing selection tree -- so that jobs without File records can
463 - Add prefixlinks to where or not where absolute links to FD.
464 - Issue message to mount a new tape before the rewind.
465 - Simplified client job initiation for portables.
466 - If SD cannot open a drive, make it periodically retry.
467 - Add more of the config info to the tape label.
469 - If tape is marked read-only, then try opening it read-only rather than
470 failing, and remember that it cannot be written.
471 - Refine SD waiting output:
472 Device is being positioned
473 > Device is being positioned for append
474 > Device is being positioned to file x
476 - Figure out some way to estimate output size and to avoid splitting
477 a backup across two Volumes -- this could be useful for writing CDROMs
478 where you really prefer not to have it split -- not serious.
479 - Have SD compute MD5 or SHA1 and compare to what FD computes.
480 - Make VolumeToCatalog calculate an MD5 or SHA1 from the
481 actual data on the Volume and compare it.
482 - Implement Bacula plugins -- design API
483 - Make bcopy read through bad tape records.
484 - Program files (i.e. execute a program to read/write files).
485 Pass read date of last backup, size of file last time.
486 - Add Signature type to File DB record.
487 - CD into subdirectory when open()ing files for backup to
488 speed up things. Test with testfind().
489 - Priority job to go to top of list.
490 - Why are save/restore of device different sizes (sparse?) Yup! Fix it.
491 - Implement some way for the Console to dynamically create a job.
492 - Restore to a particular time -- e.g. before date, after date.
493 - Solaris -I on tar for include list
494 - Need a verbose mode in restore, perhaps to bsr.
495 - bscan without -v is too quiet -- perhaps show jobs.
496 - Add code to reject whole blocks if not wanted on restore.
497 - Check if we can increase Bacula FD priorty in Win2000
498 - Make sure the MaxVolFiles is fully implemented in SD
499 - Check if both CatalogFiles and UseCatalog are set to SD.
500 - Figure out how to do a bare metal Windows restore
501 - Possibly add email to Watchdog if drive is unmounted too
502 long and a job is waiting on the drive.
503 - After unmount, if restore job started, ask to mount.
504 - Convert all %x substitution variables, which are hard to remember
505 and read to %(variable-name). Idea from TMDA.
506 - Remove NextId for SQLite. Optimize.
507 - Move all SQL statements into a single location.
508 - Add UA rc and history files.
509 - put termcap (used by console) in ./configure and
510 allow -with-termcap-dir.
511 - Fix Autoprune for Volumes to respect need for full save.
512 - Fix Win32 config file definition name on /install
513 - Compare tape to Client files (attributes, or attributes and data)
514 - Make all database Ids 64 bit.
515 - Write an applet for Linux.
516 - Allow console commands to detach or run in background.
517 - Fix status delay on storage daemon during rewind.
518 - Add SD message variables to control operator wait time
519 - Maximum Operator Wait
520 - Minimum Message Interval
521 - Maximum Message Interval
522 - Send Operator message when cannot read tape label.
523 - Verify level=Volume (scan only), level=Data (compare of data to file).
524 Verify level=Catalog, level=InitCatalog
526 - Add keyword search to show command in Console.
527 - Events : tape has more than xxx bytes.
528 - Complete code in Bacula Resources -- this will permit
529 reading a new config file at any time.
530 - Handle ctl-c in Console
531 - Implement script driven addition of File daemon to config files.
532 - Think about how to make Bacula work better with File (non-tape) archives.
533 - Write Unix emulator for Windows.
534 - Put memory utilization in Status output of each daemon
535 if full status requested or if some level of debug on.
536 - Make database type selectable by .conf files i.e. at runtime
537 - Set flag for uname -a. Add to Volume label.
538 - Restore files modified after date
539 - SET LD_RUN_PATH=$HOME/mysql/lib/mysql
540 - Remove duplicate fields from jcr (e.g. jcr.level and jcr.jr.Level, ...).
541 - Timout a job or terminate if link goes down, or reopen link and query.
542 - Concept of precious tapes (cannot be reused).
543 - Make bcopy copy with a single tape drive.
544 - Permit changing ownership during restore.
547 > My suggestion: Add a feature on the systray menu-icon menu to request
548 > an immediate backup now. This would be useful for laptop users who may
549 > not be on the network when the regular scheduled backup is run.
551 > My wife's suggestion: Add a setting to the win32 client to allow it to
552 > shut down the machine after backup is complete (after, of course,
553 > displaying a "System will shut down in one minute, click here to cancel"
554 > warning dialog). This would be useful for sites that want user
555 > woorkstations to be shut down overnight to save power.
558 - Autolabel should be specified by DIR instead of SD.
561 - AutoScan (check checksum of tape)
562 - Format command = "format /dev/nst0"
566 - Seek resolution (usually corresponds to buffer size)
567 - EODErrorCode=ENOSPC or code
568 - Partial Read error code
569 - Partial write error code
570 - Nonformatted read error
571 - Nonformatted write error
572 - WriteProtected error
576 - IgnoreCloseErrors=yes
586 - FD sends unsaved file list to Director at end of job (see
588 - File daemon should build list of files skipped, and then
589 at end of save retry and report any errors.
590 - Write a Storage daemon that uses pipes and
591 standard Unix programs to write to the tape.
593 - Need something that monitors the JCR queue and
594 times out jobs by asking the deamons where they are.
595 - Enhance Jmsg code to permit buffering and saving to disk.
596 - device driver = "xxxx" for drives.
598 - Ensure that /dev/null works
599 - Need report class for messages. Perhaps
600 report resource where report=group of messages
601 - enhance scan_attrib and rename scan_jobtype, and
602 fill in code for "since" option
603 - Director needs a time after which the report status is sent
604 anyway -- or better yet, a retry time for the job.
605 - Don't reschedule a job if previous incarnation is still running.
606 - Some way to automatically backup everything is needed????
607 - Need a structure for pending actions:
609 - termination status (part of buffered msgs?)
611 Read, Write, Clean, Delete
612 - Login to Bacula; Bacula users with different permissions:
613 owner, group, user, quotas
614 - Store info on each file system type (probably in the job header on tape.
615 This could be the output of df; or perhaps some sort of /etc/mtab record.
617 ========= ideas ===============
618 From: "Jerry K. Schieffer" <jerry@skylinetechnology.com>
619 To: <kern@sibbald.com>
620 Subject: RE: [Bacula-users] future large programming jobs
621 Date: Thu, 26 Feb 2004 11:34:54 -0600
623 I noticed the subject thread and thought I would offer the following
624 merely as sources of ideas, i.e. something to think about, not even as
625 strong as a request. In my former life (before retiring) I often
626 dealt with backups and storage management issues/products as a
627 developer and as a consultant. I am currently migrating my personal
628 network from amanda to bacula specifically because of the ability to
629 cross media boundaries during storing backups.
630 Are you familiar with the commercial product called ADSM (I think IBM
631 now sells it under the Tivoli label)? It has a couple of interesting
632 ideas that may apply to the following topics.
634 1. Migration: Consider that when you need to restore a system, there
635 may be pressure to hurry. If all the information for a single client
636 can eventually end up on the same media (and in chronological order),
637 the restore is facillitated by not having to search past information
638 from other clients. ADSM has the concept of "client affinity" that
639 may be associated with it's storage pools. It seems to me that this
640 concept (as an optional feature) might fit in your architecture for
643 ADSM also has the concept of defining one or more storage pools as
644 "copy pools" (almost mirrors, but only in the sense of contents).
645 These pools provide the ability to have duplicte data stored both
646 onsite and offsite. The copy process can be scheduled to be handled
647 by their storage manager during periods when there is no backup
648 activity. Again, the migration process might be a place to consider
649 implementing something like this.
652 > It strikes me that it would be very nice to be able to do things
654 > have the Job(s) backing up the machines run, and once they have all
655 > completed, start a migration job to copy the data from disks Volumes
657 > a tape library and then to offsite storage. Maybe this can already
659 > done with some careful scheduling and Job prioritzation; the events
660 > mechanism described below would probably make it very easy.
662 This is the goal. In the first step (before events), you simply
664 the Migration to tape later.
666 2. Base jobs: In ADSM, each copy of each stored file is tracked in
667 the database. Once a file (unique by path and metadata such as dates,
668 size, ownership, etc.) is in a copy pool, no more copies are made. In
669 other words, when you start ADSM, it begins like your concept of a
670 base job. After that it is in the "incremental" mode. You can
671 configure the number of "generations" of files to be retained, plus a
672 retention date after which even old generations are purged. The
673 database tracks the contents of media and projects the percentage of
674 each volume that is valid. When the valid content of a volume drops
675 below a configured percentage, the valid data are migrated to another
676 volume and the old volume is marked as empty. Note, this requires
677 ADSM to have an idea of the contents of a client, i.e. marking the
678 database when an existing file was deleted, but this would solve your
679 issue of restoring a client without restoring deleted files.
681 This is pretty far from what bacula now does, but if you are going to
682 rip things up for Base jobs,.....
683 Also, the benefits of this are huge for very large shops, especially
684 with media robots, but are a pain for shops with manual media
688 > Base jobs sound pretty useful, but I'm not dying for them.
690 Nobody is dying for them, but when you see what it does, you will die
693 3. Restoring deleted files: Since I think my comments in (2) above
694 have low probability of implementation, I'll also suggest that you
695 could approach the issue of deleted files by a mechanism of having the
696 fd report to the dir, a list of all files on the client for every
697 backup job. The dir could note in the database entry for each file
698 the date that the file was seen. Then if a restore as of date X takes
699 place, only files that exist from before X until after X would be
700 restored. Probably the major cost here is the extra date container in
701 each row of the files table.
703 Thanks for "listening". I hope some of this helps. If you want to
704 contact me, please send me an email - I read some but not all of the
705 mailing list traffic and might miss a reply there.
707 Please accept my compliments for bacula. It is doing a great job for
708 me!! I sympathize with you in the need to wrestle with excelence in
709 execution vs. excelence in feature inclusion.
714 ==============================
717 - Design at hierarchial storage for Bacula. Migration and Clone.
718 - Implement FSM (File System Modules).
719 - Audit M_ error codes to ensure they are correct and consistent.
720 - Add variable break characters to lex analyzer.
721 Either a bit mask or a string of chars so that
722 the caller can change the break characters.
723 - Make a single T_BREAK to replace T_COMMA, etc.
724 - Ensure that File daemon and Storage daemon can
725 continue a save if the Director goes down (this
726 is NOT currently the case). Must detect socket error,
727 buffer messages for later.
728 - Enhance time/duration input to allow multiple qualifiers e.g. 3d2h
729 - Add ability to backup to two Storage devices (two SD sessions) at
730 the same time -- e.g. onsite, offsite.
731 - Add the ability to consolidate old backup sets (basically do a restore
732 to tape and appropriately update the catalog). Compress Volume sets.
733 Might need to spool via file is only one drive is available.
734 - Compress or consolidate Volumes of old possibly deleted files. Perhaps
735 someway to do so with every volume that has less than x% valid
739 Migration: Move a backup from one Volume to another
740 Clone: Copy a backup -- two Volumes
742 Bacula Migration is based on Jobs (apparently Networker is file by file).
744 Migration triggered by:
748 Highwater mark (keep total size)
753 ======================================================
755 It is somewhat like a Full save becomes an incremental since
756 the Base job (or jobs) plus other non-base files.
758 - A Base backup is same as Full backup, just different type.
759 - New BaseFiles table that contains:
761 BaseJobId - Base JobId referenced for this FileId (needed ???)
762 JobId - JobId currently running
763 FileId - File not backed up, exists in Base Job
764 FileIndex - FileIndex from Base Job.
765 i.e. for each base file that exists but is not saved because
766 it has not changed, the File daemon sends the JobId, BaseId,
767 FileId, FileIndex back to the Director who creates the DB entry.
768 - To initiate a Base save, the Director sends the FD
769 the FileId, and full filename for each file in the Base.
770 - When the FD finds a Base file, he requests the Director to
771 send him the full File entry (stat packet plus MD5), or
772 conversely, the FD sends it to the Director and the Director
773 says yes or no. This can be quite rapid if the FileId is kept
774 by the FD for each Base Filename.
775 - It is probably better to have the comparison done by the FD
776 despite the fact that the File entry must be sent across the
778 - An alternative would be to send the FD the whole File entry
779 from the start. The disadvantage is that it requires a lot of
780 space. The advantage is that it requires less communications
782 - The Job record must be updated to indicate that one or more
784 - At end of Job, FD returns:
785 1. Count of base files/bytes not written to tape (i.e. matches)
786 2. Count of base file that were saved i.e. had changed.
787 - No tape record would be written for a Base file that matches, in the
788 same way that no tape record is written for Incremental jobs where
789 the file is not saved because it is unchanged.
790 - On a restore, all the Base file records must explicitly be
791 found from the BaseFile tape. I.e. for each Full save that is marked
792 to have one or more Base Jobs, search the BaseFile for all occurrences
794 - An optimization might be to make the BaseFile have:
800 This would avoid the need to explicitly fetch each File record for
801 the Base job. The Base Job record will be fetched to get the
802 VolSessionId and VolSessionTime.
803 =========================================================
806 ==========================================================
808 For each Incremental job that is run, there may be files that
809 were found but not saved because they were locked (this applies
810 only to Windows). Such a system could send back to the Director
811 a list of Unsaved files.
813 - New UnSavedFiles table that contains:
817 - Then in the next Incremental job, the list of Unsaved Files will be
818 feed to the FD, who will ensure that they are explicitly chosen even
819 if standard date/time check would not have selected them.
820 =============================================================
823 Done: (see kernsdone for more)
826 - John's Full save failed with 1.32c FD and 1.31 Dir no FD status,
827 and no error message.
828 - Add fd and st as Console keywords.
829 - Recycling volume with a Slot requires an operator intervention:
830 rufus-dir: Start Backup JobId 18, Job=kernsave.2003-11-01_21.23.52
831 rufus-dir: Pruned 1 Job on Volume Vol01 from catalog.
832 rufus-dir: There are no Jobs associated with Volume Vol01. Marking it purged.
833 rufus-dir: Recycled volume "Vol01"
834 rufus-sd: Please mount Volume "Vol01" on Storage Device "DDS-4" for Job kernsave.2003-11-01_21.23.52
835 Use "mount" command to release Job.
836 - Implement Dan's bacula script (email of 26 Oct).
837 - Add JobName= to VerifyToCatalog so that all verifies can be done at the end.
838 - Edit the Client/Storage name into authentication failure messages.
839 - Fix packet too big problem. This is most likely a Windows TCP stack
841 - Implement ClientRunBeforeJob and ClientRunAfterJob.
842 - Implement forward spacing block/file: position_device(bsr) --
843 just before read_block_from_device();
846 Multiple drive autochanger data: see Alan Brown
847 mtx -f xxx unloadStorage Element 1 is Already Full(drive 0 was empty)
848 Unloading Data Transfer Element into Storage Element 1...source Element
851 (drive 0 was empty and so was slot 1)
852 > mtx -f xxx load 15 0
853 no response, just returns to the command prompt when complete.
854 > mtx -f xxx status Storage Changer /dev/changer:2 Drives, 60 Slots ( 2 Import/Export )
855 Data Transfer Element 0:Full (Storage Element 15 Loaded):VolumeTag = HX001
856 Data Transfer Element 1:Empty
857 Storage Element 1:Empty
858 Storage Element 2:Full :VolumeTag=HX002
859 Storage Element 3:Full :VolumeTag=HX003
860 Storage Element 4:Full :VolumeTag=HX004
861 Storage Element 5:Full :VolumeTag=HX005
862 Storage Element 6:Full :VolumeTag=HX006
863 Storage Element 7:Full :VolumeTag=HX007
864 Storage Element 8:Full :VolumeTag=HX008
865 Storage Element 9:Full :VolumeTag=HX009
866 Storage Element 10:Full :VolumeTag=HX010
867 Storage Element 11:Empty
868 Storage Element 12:Empty
869 Storage Element 13:Empty
870 Storage Element 14:Empty
871 Storage Element 15:Empty
872 Storage Element 16:Empty....
873 Storage Element 28:Empty
874 Storage Element 29:Full :VolumeTag=CLNU01L1
875 Storage Element 30:Empty....
876 Storage Element 57:Empty
877 Storage Element 58:Full :VolumeTag=NEX261L2
878 Storage Element 59 IMPORT/EXPORT:Empty
879 Storage Element 60 IMPORT/EXPORT:Empty
881 Unloading Data Transfer Element into Storage Element 15...done
883 (just to verify it remembers where it came from, however it can be
884 overrriden with mtx unload {slotnumber} to go to any storage slot.)
886 There needs to be a table of drive # to devices somewhere - If there are
887 multiple changers or drives there may not be a 1:1 correspondance between
888 changer drive number and system device name - and depending on the way the
889 drives are hooked up to scsi busses, they may not be linearly numbered
890 from an offset point either.something like
892 Autochanger drives = 2
893 Autochanger drive 0 = /dev/nst1
894 Autochanger drive 1 = /dev/nst2
895 IMHO, it would be _safest_ to use explicit mtx unload commands at all
896 times, not just for multidrive changers. For a 1 drive changer, that's
902 MTX's manpage (1.2.15):
903 unload [<slotnum>] [ <drivenum> ]
904 Unloads media from drive <drivenum> into slot
905 <slotnum>. If <drivenum> is omitted, defaults to
906 drive 0 (as do all commands). If <slotnum> is
907 omitted, defaults to the slot that the drive was
908 loaded from. Note that there's currently no way
909 to say 'unload drive 1's media to the slot it
910 came from', other than to explicitly use that
911 slot number as the destination.AB
917 undef# camcontrol devlist
918 <WANGTEK 51000 SCSI M74H 12B3> at scbus0 target 2 lun 0 (pass0,sa0)
919 <ARCHIVE 4586XX 28887-XXX 4BGD> at scbus0 target 4 lun 0 (pass1,sa1)
920 <ARCHIVE 4586XX 28887-XXX 4BGD> at scbus0 target 4 lun 1 (pass2)
922 tapeinfo -f /dev/sg0 with a bad tape in drive 1:
923 [kern@rufus mtx-1.2.17kes]$ ./tapeinfo -f /dev/sg0
924 Product Type: Tape Drive
926 Product ID: 'C5713A '
929 TapeAlert[3]: Hard Error: Uncorrectable read/write error.
930 TapeAlert[20]: Clean Now: The tape drive neads cleaning NOW.
937 Medium Type: Not Loaded
942 DataDeCompEnabled: yes
949 Handling removable disks
951 From: Karl Cunningham <karlc@keckec.com>
953 My backups are only to hard disk these days, in removable bays. This is my
954 idea of how a backup to hard disk would work more smoothly. Some of these
955 things Bacula does already, but I mention them for completeness. If others
956 have better ways to do this, I'd like to hear about it.
958 1. Accommodate several disks, rotated similar to how tapes are. Identified
959 by partition volume ID or perhaps by the name of a subdirectory.
960 2. Abort & notify the admin if the wrong disk is in the bay.
961 3. Write backups to different subdirectories for each machine to be backed
963 4. Volumes (files) get created as needed in the proper subdirectory, one
965 5. When a disk is recycled, remove or zero all old backup files. This is
966 important as the disk being recycled may be close to full. This may be
967 better done manually since the backup files for many machines may be
968 scattered in many subdirectories.