8 Data encryption Meno Abels (see projects)
9 Communication encryption Meno Abels
10 Version 1.35 Kern (see below)
11 ========================================================
13 1.35 Items to do for release:
14 - Backspace to beginning of line (conio) does not erase first char.
16 - Document a get out of jail procedure if everything breaks if
17 you lost/broke the Catalog -- do the same for "I know my
18 file is there how do I get it back?".
20 - Add "Rerun failed levels = yes/no" to Job resource.
24 - Look at patches/bacula_db.b2z postgresql that loops during restore.
26 - Add delete JobId to regression.
27 - Add bscan to four-concurrent-jobs regression.
28 - Add IPv6 to regression
29 - Perhaps add read/write programs and/or plugins to FileSets.
30 - How to handle backing up portables ...
32 Documentation to do: (any release a little bit at a time)
33 - Alternative to static linking "ldd prog" save all binaries listed,
34 restore them and point LD_LIBRARY_PATH to them.
35 - Document add "</dev/null >/dev/null 2>&1" to the bacula-fd command line
36 - Document query file format.
37 - Add more documentation for bsr files.
38 - Document problems with Verify and pruning.
39 - Document how to use multiple databases.
40 - VXA drives have a "cleaning required"
41 indicator, but Exabyte recommends preventive cleaning after every 75
44 In this context, it should be noted that Exabyte has a command-line
45 vxatool utility available for free download. (The current version is
46 vxatool-3.72.) It can get diagnostic info, read, write and erase tapes,
47 test the drive, unload tapes, change drive settings, flash new firmware,
49 Of particular interest in this context is that vxatool <device> -i will
50 report, among other details, the time since last cleaning in tape motion
51 minutes. This information can be retrieved (and settings changed, for
52 that matter) through the generic-SCSI device even when Bacula has the
53 regular tape device locked. (Needless to say, I don't recommend
54 changing tape settings while a job is running.)
55 - Lookup HP cleaning recommendations.
56 - Lookup HP tape replacement recommendations (see trouble shooting autochanger)
57 - Add more obvious documentation of @ for conf files.
58 - Document doing table repair
61 Testing to do: (painful)
64 For 1.37 Testing/Documentation:
65 - Add "Allow multiple connections" in Catalog resource to open a new
66 database connection for each job.
67 - Allow Simultaneous Priorities = yes => run up to Max concurrent jobs even
68 with multiple priorities.
69 - Fix find_device in stored/dircmd.c:462 (see code)
70 - Add db check test to regression. Test each function like delete,
72 - If you use restore replace=never, the directory attributes for
73 non-existent directories will not be restored properly.
78 mt status and tapeinfo output are attached. Default blocksize was
79 originally 512 bytes. I ran the following test on my machine:
81 - set defblksize to 512
82 - started bacula, labelled tape, ran job
83 - job completes with the following in log
84 SD termination status: OK
85 Termination: Backup OK
86 - restore attempts with blocksize set to 0 or 512 result in the familiar
87 "Volume data error! Wanted block-id BB02, got . Buffer discarded."
90 # tapeinfo -f /dev/sg0
91 Product Type: Tape Drive
93 Product ID: 'TSL-11000 '
96 SerialNumber: '0010000443'
103 Medium Type: Not Loaded
108 DataDeCompEnabled: yes
114 # mt -f /dev/nst0 status
116 File number=0, block number=132, partition=0.
117 Tape block size 512 bytes. Density code 0x26 (DDS-4 or QIC-4GB).
118 Soft error count since last status=0
119 General status bits on (1010000):
125 - see lzma401.zip in others directory for new compression
127 - Minimal autochanger handling in Bacula and in btape.
128 - Look into how tar does not save sockets and the possiblity of
129 not saving them in Bacula (Martin Simmons reported this).
130 - Add All Local Partitions = yes to new style saves.
131 - localmounts=`awk '/ext/ { print $2 }' /proc/mounts` # or whatever
132 find $localmounts -xdev -type s -ls
133 - Fix restore jobs so that multiple jobs can run if they
134 are not using the same tape(s).
135 - Allow the user to select JobType for manual pruning/purging.
136 - Look at adding Client run command that will use the
137 port opened by the client.
138 - bscan does not put first of two volumes back with all info in
140 - Implement the FreeBSD nodump flag in chflags.
141 - Figure out how to make named console messages go only to that
142 console and to the non-restricted console (new console class?).
143 - Make restricted console prompt for password if *ask* is set or
144 perhaps if password is undefined.
145 - Implement "from ISO-date/time every x hours/days/weeks/months" in
147 ==== from Marc Schoechlin
148 - the help-command should be more verbose
149 (it should explain the paramters of the different
151 -> it´s time-comsuming to consult the manual anytime
152 you need a special parameter
153 -> maybe it´s more easy to maintain this, if the
154 descriptions of that commands are outsourced to
156 - the cd-command should allow complete paths
157 i.e. cd /foo/bar/foo/bar
158 -> if a customer mails me the path to a certain file,
159 it´s faster to enter the specified directory
160 - if the password is not configured in bconsole.conf
161 you should be asked for it.
162 -> sometimes you like to do restore on a customer-machine
163 which shouldn´t know the password for bacula.
164 -> adding the password to the file favours admins
165 to forget to remove the password after usage
167 the protection of that file is less important
168 - long-listed-output of commands should be scrollable
169 like the unix more/less-command does
170 -> if someone runs 200 and more machines, the lists could
171 be a little long and complex
172 - command-output should be shown column by column
173 to reduce scrolling and to increase clarity
175 - lsmark should list the selected files with full
177 - wildcards for selecting and file and directories would be nice
178 - any actions should be interuptable with STRG+C
179 - command-expansion would be pretty cool
181 - Compaction of Disk space by "migrating" Volumes that have pruned
182 Jobs (what criteria? size, #jobs, time).
183 - Add prune all command
184 - Document fact that purge can destroy a part of a restore by purging
185 one volume while others remain valid -- perhaps mark Jobs.
186 - Add multiple-media-types.txt
187 - look at mxt-changer.html
188 - Make ? do a help command (no return needed).
189 - Implement restore directory.
190 - Document streams and how to implement them.
191 - Possibly implement "Ensure Full Backup = yes" looks for a failed full backup
192 and upgrades the current backup if one exists.
193 - Check that barcode reading and update slots scan works.
194 - Try not to re-backup a file if a new hard link is added.
195 - Add feature to backup hard links only, but not the data.
196 - Fix stream handling to be simpler.
197 - Add Priority and Bootstrap to Run a Job.
198 - Eliminate Restore "Run Restore Job" prompt by allowing new "run command
200 - Remove View FileSet button from Run a Job dialog.
201 - Don't count higher level non-saved directories in Files expected
203 - Handle prompt for restore job at end of Restore command.
204 - Add display of total selected files to Restore window.
205 - Add tree pane to left of window.
206 - Add progress meter.
207 - Max wait time or max run time causes seg fault -- see runtime-bug.txt
208 - Document writing to a CD/DVD with Bacula.
209 - Add a "base" package to the window installer for pthreadsVCE.dll
210 which is needed by all packages.
211 - Add message to user to check for fixed block size when the forward
212 space test fails in btape.
213 - When unmarking a directory check if all files below are unmarked and
214 then remove the + flag -- in the restore tree.
215 - Possibly implement: Action = Unmount Device="TapeDrive1" in Admin jobs.
216 - Setup lrrd graphs: (http://www.linpro.no/projects/lrrd/) Mike Acar.
217 - Revisit the question of multiple Volumes (disk) on a single device.
218 - Add a block copy option to bcopy.
219 - Investigate adding Mac Resource Forks.
220 - Finish work on Gnome restore GUI.
221 - Fix "llist jobid=xx" where no fileset or client exists.
223 it seems to be complaining about 12:00pm which should be a valid 12
224 hour time. I changed the time to 11:59am and everything works fine.
225 Also 12:00am works fine. 0:00pm also works (which I don't think
226 should). None of the values 12:00pm - 12:59pm work for that matter.
227 - Add level to estimate command.
228 - For each job type (Admin, Restore, ...) require only the really necessary
230 - Fix option 2 of restore -- list where file is backed up -- require Client,
231 then list last 20 backups.
232 - Add all pools in Dir conf to DB also update them to catch changed
233 LabelFormats and such.
234 - Pass Director resource name as an option to the Console.
235 - Add a "batch" mode to the Console (no unsolicited queries, ...).
236 - Add a .list all files in the restore tree (probably also a list all files)
237 Do both a long and short form.
238 - Allow browsing the catalog to see all versions of a file (with
239 stat data on each file).
240 - Restore attributes of directory if replace=never set but directory
242 - Use SHA1 on authentication if possible.
243 - See comtest-xxx.zip for Windows code to talk to USB.
244 - Make btape accept Device Names in addition to Archive names.
245 - Add Events and Perl scripting.
246 - Add John's appended files:
247 Appended = { /files/server/logs/http/*log }
248 and such files would be treated as follows.On a FULL backup, they would
249 be backed up like any other file.On an INCREMENTAL backup, where a
250 previous INCREMENTAL or FULL was already in thecatalogue and the length
251 of the file wasgreater than the length of the last backup, only thedata
252 added since the last backup will be dumped.On an INCREMENTAL backup, if
253 the length of the file is less than thelength of the file with the same
254 name last backed up, the completefile is dumped.On Windows systems, with
255 creation date of files, we can be evensmarter about this and not count
256 entirely upon the length.On a restore, the full and all incrementals
257 since it will beapplied in sequence to restore the file.
258 - Add a regression test for dbcheck.
259 - Add disk seeking on restore. - Allow
260 for optional cancelling of SD and FD in case DIR
261 gets a fatal error. Requested by Jesse Guardiani <jesse@wingnet.net>
262 - Add "limit=n" for "list jobs"
263 - Check new HAVE_WIN32 open bits.
264 - Check if the tape has moved before writing.
265 - Handling removable disks -- see below:
266 - Keep track of tape use time, and report when cleaning is necessary.
267 - Add FromClient and ToClient keywords on restore command (or
268 BackupClient RestoreClient).
269 - Implement a JobSet, which groups any number of jobs. If the
270 JobSet is started, all the jobs are started together.
271 Allow Pool, Level, and Schedule overrides.
272 - Enhance cancel to timeout BSOCK packets after a specific delay.
273 - Do scheduling by UTC using gmtime_r() in run_conf, scheduler, and
274 ua_status.!!! Thanks to Alan Brown for this tip.
275 - Look at updating Volume Jobs so that Max Volume Jobs = 1 will work
276 correctly for multiple simultaneous jobs.
277 - Correct code so that FileSet MD5 is calculated for < and | filename
279 - Implement the Media record flag that indicates that the Volume does disk
281 - Implement VolAddr, which is used when Volume is addressed like a disk,
282 and form it from VolFile and VolBlock.
283 - Make multiple restore jobs for multiple media types specifying
284 the proper storage type.
285 - Implement MediaType keyword in bsr?
286 - Fix fast block rejection (stored/read_record.c:118). It passes a null
287 pointer (rec) to try_repositioning().
288 - Look at extracting Win data from BackupRead.
289 - Implement RestoreJobRetention? Maybe better "JobRetention" in a Job,
290 which would take precidence over the Catalog "JobRetention".
291 - Implement Label Format in Add and Label console commands.
292 - Possibly up network buffers to 65K. Put on variable.
293 - Put email tape request delays on one or more variables. User wants
294 to cancel the job after a certain time interval. Maximum Mount Wait?
295 - Job, Client, Device, Pool, or Volume?
296 Is it possible to make this a directive which is *optional* in multiple
297 resources, like Level? If so, I think I'd make it an optional directive
298 in Job, Client, and Pool, with precedence such that Job overrides Client
299 which in turn overrides Pool.
301 - Spooling ideas taken from Volker Sauer's and other's emails:
302 > IMHO job spooling should be turned on
308 > where and 2) overrides 1) and 3) is independent.
310 Yes, this is the minimum that I think is necessary.
314 > It should be switched by job, because the job that backs up the machine
315 > with the bacula-sd on doesn't need spooling.
316 > It should be switched by schedule, because for full-backups I don't need
317 > spooling, so I can switch it off (because the network faster then the
320 True, with the exception that if you have enough disk spool space,
321 and you want to run concurrent jobs, spooling can eliminate the block
322 interleaving restore inefficiencies.
324 > And you should be able to turn it of by sd for sd-machines with low disk
325 > capacity or if you just don't need or want this feature.
328 > - definitly the possibility for multipe spool direcories
330 Having multiple directories is no problem -- having different maximum
331 sizes creates specification problems. At some point, I will probably
332 have a common SD pool of spool directories as well as a set of
333 private spool directories for each device. The first implementation
334 will be a set of private spool directories for each device since
335 managing a global pool with a bunch of threads writing into the same
336 directory is *much* more complicated and prone to error.
338 > - the ability to spool parts of a backup (not the whole client)
340 This may change in the future, but for the moment, it will spool
341 either to a job high water mark, or until the directory is full
342 (reaches max spool size or I/O error). It will then write to tape,
343 truncate the spool file, and begin spooling again.
345 > - spooling while writing to tape
347 Not within a job, but yes, if you run concurrent jobs -- each is a
348 different thread. Within a job could be a feature, but *much* later.
350 > - parallel spooling (like parallel jobs/ concurrent jobs) of clients
352 Yes, this is one of my main motivations for doing it (aside from
353 eliminating tape "shoe shine" during incremental backups.
355 > - flushing a backup that only went to disk (like amflush in amanda)
357 This will be a future feature, since spooling is different from backing
358 up to disk. The future feature will be "migration" which will move a job
359 from one backup Volume to another.
361 - New Storage specifications:
362 - Want to write to multiple storage devices simultaneously
363 - Want to write to multiple storage devices sequentially (in one job)
364 - Want to read/write simultaneously
365 - Key is MediaType -- it must match
367 Passed to SD as a sort of BSR record called Storage Specification
371 MediaType -> Next MediaType
373 Device -> Next Device
375 Allow multiple Storage specifications
383 Allow Multiple Pool specifications (note, Pool currently
385 Allow Multiple MediaType specifications in Dir conf
386 Allow Multiple Device specifications in Dir conf
387 Perhaps keep this in a single SSR
388 Tie a Volume to a specific device by using a MediaType that
389 is contained in only one device.
390 In SD allow Device to have Multiple MediaTypes
393 - Look at www.nu2.nu/pebuilder as a helper for full windows
395 Ideas from Jerry Scharf:
396 First let's point out some big pluses that bacula has for this
398 more importantly it's active. Thank you so much for that
399 even more important, it's not flaky
400 it has an open access catalog, opening many possibilities
401 it's pushing toward heterogeneous systems capability
403 Macintosh file client
404 macs are an interesting niche, but I fear a server is a rathole
405 working bare iron recovery for windows
406 the option for inc/diff backups not reset on fileset revision
407 a) use both change and inode update time against base time
408 b) do the full catalog check (expensive but accurate)
409 sizing guide (how much system is needed to back up N systems/files)
410 consultants on using bacula in building a disaster recovery system
412 or how to get at fancy things that one could do with bacula
413 logwatch code for bacula logs (or similar)
414 linux distro inclusion of bacula (brings good and bad, but necessary)
415 win2k/XP server capability (icky but you asked)
416 support for Oracle database ??
418 - Look at adding SQL server and Exchange support for Windows.
419 - Restore: Enter Filename: 'C:/Documents and Settings/Comercial/My
420 Documents/MOP/formulário de registro BELAS ARTES.doc' causes Bacula to
422 - Each DVD-RAM disk would be a volume, just like each tape is
423 a volume. It's a 4.7GB media with random access, but there's nothing about
424 it that I can see that makes it so different than a tape from bacula's
425 perspective. Why couldn't I back up to a bare floppy as a volume (ignoring
427 - Make dev->file and dev->block_num signed integers so that -1 can
428 be an invalid value which happens with BSR.
429 - Create VolAddr for disk files in place of VolFile and VolBlock. This
430 is needed to properly specify ranges.
431 - Print bsmtp output to job report so that problems will be seen.
432 - Pass the number of files to be restored to the FD for reporting
433 - Add progress of files/bytes to SD and FD.
434 - Don't continue Restore if no files selected.
435 - Print warning message if FileId > 4 billion
436 - do a "messages" before the first prompt in Console
437 - Add a date and time stamp at the beginning of every line in the
438 Job report (Volker Sauer).
439 - Client does not show busy during Estimate command.
440 - Implement Console mtx commands.
441 - Add a default DB password to MySQL.
442 GRANT all privileges ON bacula.* TO bacula@localhost IDENTIFIED BY
445 - Implement a Mount Command and an Unmount Command where
446 the users could specify a system command to be performed
447 to do the mount, after which Bacula could attempt to
448 read the device. This is for Removeable media such as a CDROM.
449 - Most likely, this mount command would be invoked explicitly
450 by the user using the current Console "mount" and "unmount"
451 commands -- the Storage Daemon would do the right thing
452 depending on the exact nature of the device.
453 - As with tape drives, when Bacula wanted a new removable
454 disk mounted, it would unmount the old one, and send a message
455 to the user, who would then use "mount" as described above
456 once he had actually inserted the disk.
457 - Implement dump/print label to UA
458 - Spool to disk only when the tape is full, then when a tape is hung move
460 - Scratch Pool where the volumes can be re-assigned to any Pool.
461 - bextract is sending everything to the log file ****FIXME****
462 - Add Progress command that periodically reports the progress of
464 - Restrict characters permitted in a Resource name, and don't permit
466 - Allow multiple Storage specifications (or multiple names on
467 a single Storage specification) in the Job record. Thus a job
468 can be backed up to a number of storage devices.
469 - Implement some way for the File daemon to contact the Director
470 to start a job or pass its DHCP obtained IP number.
471 - Implement multiple Consoles.
472 - Implement a query tape prompt/replace feature for a console
474 Two jobs ready to go, first one blocked waiting for media
475 Cancel 2nd job ("waiting execution" one)
478 - Copy console @ code to gnome2-console
479 - Make AES the only encryption algorithm see
480 http://csrc.nist.gov/CryptoToolkit/aes/). It's
481 an officially adopted standard, has survived peer
482 review, and provides keys up to 256 bits.
483 - Think about how space could be freed up on a tape -- perhaps this
484 is a Merge or Compact feature that is needed.
485 - Modify FileSet, did not upgrade the current Increment job, but
486 waited for the next job to be upgraded.
487 - Take a careful look at SetACL http://setacl.sourceforge.net
488 - Implement a where command for the tree telling where a file
490 - Take a careful look at Level for the estimate command, maybe make
491 it a command line option.
492 - Add Volume name to "I cannot write on this volume because"
493 - Make tree walk routines like cd, ls, ... more user friendly
494 by handling spaces better.
495 - Write your PID file and chown root:wheel before drop.
496 - Make sure there is no symlink in a file before creating a
498 - Look at mktemp or mkstemp(3).
499 mktemp and mkstemp create files with predictable names too. That's
500 not the vulnerability. The vulnerability is in creating files without
501 using the O_EXCL flag, which means "only create this file if it doesn't
502 exist, including if the file is a dangling symlink."
504 It is *NOT* enough to do the equivalent of
506 if doesn't exist $filename
507 then create $filename
509 because between the test and the create another process could have
510 gotten the CPU and created the file. You must use atomic functions
511 (those that don't get interrupted by other processes) and O_EXCL is
512 the only way for this particular example.
513 - Automatically create pools, but instead of looking for what
514 in in Job records, walk through the pool resources.
515 - Check and double check tree code, why does it take so long?
516 - Add device name to "Current Volume not acceptable because ..."
517 - Make sure that Bacula rechecks the tape after the 20 min wait.
518 - Set IO_NOWAIT on Bacula TCP/IP packets.
519 - Try doing a raw partition backup and restore by mounting a
522 Yes, it would allow to highly automatic the request for new tapes. If a
523 tape is empty, bacula reads the barcodes (native or simulated), and if
524 an unused tape is found, it runs the label command with all the
525 necessary parameters.
527 By the way can bacula automatically "move" an empty/purged volume say
528 in the "short" pool to the "long" pool if this pool runs out of volume
530 - Eliminate orphaned jobs: dbcheck, normal pruning, delete job command.
531 Hm. Well, there are the remaining orphaned job records:
533 | 105 | Llioness Save | 0000-00-00 00:00:00 | B | D | 0 | 0 | f |
534 | 110 | Llioness Save | 0000-00-00 00:00:00 | B | I | 0 | 0 | f |
535 | 115 | Llioness Save | 2003-09-10 02:22:03 | B | I | 0 | 0 | A |
536 | 128 | Catalog Save | 2003-09-11 03:53:32 | B | I | 0 | 0 | C |
537 | 131 | Catalog Save | 0000-00-00 00:00:00 | B | I | 0 | 0 | f |
539 As you can see, three of the five are failures. I already deleted the
540 one restore and one other failure using the by-client option. Deciding
541 what is an orphaned job is a tricky problem though, I agree. All these
542 records have or had 0 files/ 0 bytes, except for the restore. With no
543 files, of course, I don't know of the job ever actually becomes
544 associated with a Volume.
546 (I'm not sure if this is documented anywhere -- what are the meanings of
547 all the possible JobStatus codes?)
549 Looking at my database, it appears to me as though all the "orphaned"
550 jobs fit into one of two categories:
552 1) The Job record has a StartTime but no EndTime, and the job is not
555 2) The Job record has an EndTime, indicating that it completed, but
556 it has no associated JobMedia record.
559 This does suggest an approach. If failed jobs (or jobs that, for some
560 other reason, write no files) are associated with a volume via a
561 JobMedia record, then they should be purged when the associated volume
562 is purged. I see two ways to handle jobs that are NOT associated with a
565 1) purge them automatically whenever any volume is manually purged;
567 2) add an option to the purge command to manually purge all jobs with
568 no associated volume.
570 I think Restore jobs also fall into category 2 above .... so one might
571 want to make that "The Job record has an EndTime,, but no associated
572 JobMedia record, and is not a Restore job."
573 - make "btape /tmp" work.
574 - Make sure a rescheduled job is properly reported by status.
575 - Walk through the Pool records rather than the Job records
576 in dird.c to create/update pools.
577 - What to do about "list files job=xxx".
578 - When job rescheduled, status gives is waiting for Client Rufus
579 to connect to Storage File. Dir needs to inform SD that job
581 - Make Dmsg look at global before calling subroutine.
582 - Enable trace output at runtime for Win32
583 - Available volumes for autochangers (see patrick@baanboard.com 3 Sep 03
584 and 4 Sep) scan slots.
585 - Get and test MySQL 4.0
586 - Do a complete audit of all pthreads_mutex, cond, ... to ensure that
587 any that are dynamically initialized are destroyed when no longer used.
588 - Look at how fuser works and /proc/PID/fd that is how Nic found the
589 file descriptor leak in Bacula.
590 - Implement WrapCounters in Counters.
591 - Turn on SIGHUP in dird.c and test.
592 - Use system dependent calls to get more precise info on tape errors.
593 - Add heartbeat from FD to SD if hb interval expires.
594 - Suppress read error on blank tape when doing a label.
595 - Can we dynamically change FileSets?
596 - If pool specified to label command and Label Format is specified,
597 automatically generate the Volume name.
598 - Why can't SQL do the filename sort for restore?
599 - Look at libkse (man kse) for FreeBSD threading.
600 - Look into Microsoft Volume Shadowcopy Service VSS for backing
601 up system state components (Active Directory, System Volume, ...)
602 - Add ExhautiveRestoreSearch
603 - Look at the possibility of loading only the necessary
604 data into the restore tree (i.e. do it one directory at a
605 time as the user walks through the tree).
606 - Possibly use the hash code if the user selects all for a restore command.
607 - Orphaned Dir buffer at parse_conf.c:373 => store_dir
608 - Fix "restore all" to bypass building the tree.
609 - Prohibit backing up archive device (findlib/find_one.c:128)
610 - Implement Release Device in the Job resource to unmount a drive.
611 - Implement Acquire Device in the Job resource to mount a drive,
612 be sure this works with admin jobs so that the user can get
613 prompted to insert the correct tape. Possibly some way to say to
614 run the job but don't save the files.
615 - Implement FileOptions (see end of this document)
616 - Make things like list where a file is saved case independent for
619 - Bacula needs to propagate SD errors.
620 > > cluster-dir: Start Backup JobId 252, Job=REUTERS.2003-08-11_15.04.12
621 > > prod4-sd: REUTERS.2003-08-11_15.04.12 Error: Write error on device
622 /dev/nst0. ERR=Input/output error.
623 > > prod4-sd: REUTERS.2003-08-11_15.04.12 Error: Re-read of last block failed.
624 Last block=5162 Current block=5164.
625 > > prod4-sd: End of medium on Volume "REU007" Bytes=16,303,521,933
627 - Use autochanger to handle multiple devices.
628 - Add SuSE install doc to list.
629 - Check and rechedk "Invalid block number"
630 - Make bextract release the drive properly between tapes
631 so that an autochanger can be made to work.
632 - User wants to NOT backup up certain big files (email files).
633 - Maybe remove multiple simultaneous devices code in SD.
634 - On Windows with very long path names, it may be impossible to create
635 a file (and thus restore it) because the total length is too long.
636 We must cd into the directory then create the file without the
638 - lstat() is not going to work on Win32 for testing date.
639 - Implement a Recycle command
640 - Add client name to cram-md5 challenge so Director can immediately
641 verify if it is the correct client.
642 - Add JobLevel in FD status (but make sure it is defined).
643 - Audit all UA commands to ensure that we always prompt where possible.
644 - Check Jmsg in bnet, may not work, must dup bsock.
645 - Suppress Job Name in Jmsg for console
646 - Create Pools that are referenced in a Run statement at startup if possible.
647 - Use runbeforejob to unload, then reload a volume previously used,
648 then the next job run gets an error reading the drive.
649 - Make bootstrap filename unique.
650 - Test a second language e.g. french.
651 - Start working on Base jobs.
652 - Make "make binary-release" work from any directory.
653 - Implement UnsavedFiles DB record.
654 - Implement argc/argv for daemon command line scanning using table driven
656 - Implement table driven single argc/argv scanner to pickup all arguments.
657 Much like xxx_conf.c scan table.
658 keyword, handler(store_routine), store_address, code, flags, default.
659 - From Phil Stracchino:
660 It would probably be a per-client option, and would be called
661 something like, say, "Automatically purge obsoleted jobs". What it
662 would do is, when you successfully complete a Differential backup of a
663 client, it would automatically purge all Incremental backups for that
664 client that are rendered redundant by that Differential. Likewise,
665 when a Full backup on a client completed, it would automatically purge
666 all Differential and Incremental jobs obsoleted by that Full backup.
667 This would let people minimize the number of tapes they're keeping on
668 hand without having to master the art of retention times.
669 - Implement a M_SECURITY message class.
670 - When doing a Backup send all attributes back to the Director, who
671 would then figure out what files have been deleted.
672 - Currently in mount.c:236 the SD simply creates a Volume. It should have
673 explicit permission to do so. It should also mark the tape in error
674 if there is an error.
675 - Make sure all restore counters are working correctly in the FD.
676 - SD Bytes Read is wrong.
677 - Look at ALL higher level routines that call block.c to be sure
678 they don't expect something in errmsg.
679 - Investigate doing RAW backup of Win32 partition.
680 - Add thread specific data to hold the jcr -- send error messages from
681 low level routines by accessing it and using Jmsg().
682 - Cancel waiting for Client connect in SD if FD goes away.
684 - Examine Bare Metal restore problem (a FD crash exists somewhere ...).
685 - Implement timeout in response() when it should come quickly.
686 - Implement console @echo command.
687 - Implement a Slot priority (loaded/not loaded).
688 - Implement "vacation" Incremental only saves.
689 - Implement single pane restore (much like the Gftp panes).
690 - Implement Automatic Mount even in operator wait.
691 - Implement create "FileSet"?
692 - Fix watchdog pthread crash on Win32 (this is pthread_kill() Cygwin bug)
693 - Implement "scratch pool" where tapes are defined and can be
694 taken by any pool that needs them.
695 - Implement restore "current system", but take all files without
696 doing selection tree -- so that jobs without File records can
698 - Add prefixlinks to where or not where absolute links to FD.
699 - Issue message to mount a new tape before the rewind.
700 - Simplified client job initiation for portables.
701 - If SD cannot open a drive, make it periodically retry.
702 - Add more of the config info to the tape label.
704 - If tape is marked read-only, then try opening it read-only rather than
705 failing, and remember that it cannot be written.
706 - Refine SD waiting output:
707 Device is being positioned
708 > Device is being positioned for append
709 > Device is being positioned to file x
711 - Figure out some way to estimate output size and to avoid splitting
712 a backup across two Volumes -- this could be useful for writing CDROMs
713 where you really prefer not to have it split -- not serious.
714 - Have SD compute MD5 or SHA1 and compare to what FD computes.
715 - Make VolumeToCatalog calculate an MD5 or SHA1 from the
716 actual data on the Volume and compare it.
717 - Implement Bacula plugins -- design API
718 - Make bcopy read through bad tape records.
719 - Program files (i.e. execute a program to read/write files).
720 Pass read date of last backup, size of file last time.
721 - Add Signature type to File DB record.
722 - CD into subdirectory when open()ing files for backup to
723 speed up things. Test with testfind().
724 - Priority job to go to top of list.
725 - Why are save/restore of device different sizes (sparse?) Yup! Fix it.
726 - Implement some way for the Console to dynamically create a job.
727 - Restore to a particular time -- e.g. before date, after date.
728 - Solaris -I on tar for include list
729 - Need a verbose mode in restore, perhaps to bsr.
730 - bscan without -v is too quiet -- perhaps show jobs.
731 - Add code to reject whole blocks if not wanted on restore.
732 - Check if we can increase Bacula FD priorty in Win2000
733 - Make sure the MaxVolFiles is fully implemented in SD
734 - Check if both CatalogFiles and UseCatalog are set to SD.
735 - Figure out how to do a bare metal Windows restore
736 - Possibly add email to Watchdog if drive is unmounted too
737 long and a job is waiting on the drive.
738 - Restore program that errs in SD due to no tape, reports
739 OK incorrectly in output.
740 - After unmount, if restore job started, ask to mount.
741 - Convert all %x substitution variables, which are hard to remember
742 and read to %(variable-name). Idea from TMDA.
743 - Remove NextId for SQLite. Optimize.
744 - Move all SQL statements into a single location.
745 - Add UA rc and history files.
746 - put termcap (used by console) in ./configure and
747 allow -with-termcap-dir.
748 - Fix Autoprune for Volumes to respect need for full save.
749 - Fix Win32 config file definition name on /install
750 - Compare tape to Client files (attributes, or attributes and data)
751 - Make all database Ids 64 bit.
752 - Write an applet for Linux.
753 - Allow console commands to detach or run in background.
754 - Fix status delay on storage daemon during rewind.
755 - Add SD message variables to control operator wait time
756 - Maximum Operator Wait
757 - Minimum Message Interval
758 - Maximum Message Interval
759 - Send Operator message when cannot read tape label.
760 - Verify level=Volume (scan only), level=Data (compare of data to file).
761 Verify level=Catalog, level=InitCatalog
763 - Add keyword search to show command in Console.
764 - Events : tape has more than xxx bytes.
765 - Complete code in Bacula Resources -- this will permit
766 reading a new config file at any time.
767 - Handle ctl-c in Console
768 - Implement script driven addition of File daemon to config files.
769 - Think about how to make Bacula work better with File (non-tape) archives.
770 - Write Unix emulator for Windows.
771 - Put memory utilization in Status output of each daemon
772 if full status requested or if some level of debug on.
773 - Make database type selectable by .conf files i.e. at runtime
774 - Set flag for uname -a. Add to Volume label.
775 - Restore files modified after date
776 - SET LD_RUN_PATH=$HOME/mysql/lib/mysql
777 - Remove duplicate fields from jcr (e.g. jcr.level and jcr.jr.Level, ...).
778 - Timout a job or terminate if link goes down, or reopen link and query.
779 - Concept of precious tapes (cannot be reused).
780 - Make bcopy copy with a single tape drive.
781 - Permit changing ownership during restore.
784 > My suggestion: Add a feature on the systray menu-icon menu to request
785 > an immediate backup now. This would be useful for laptop users who may
786 > not be on the network when the regular scheduled backup is run.
788 > My wife's suggestion: Add a setting to the win32 client to allow it to
789 > shut down the machine after backup is complete (after, of course,
790 > displaying a "System will shut down in one minute, click here to cancel"
791 > warning dialog). This would be useful for sites that want user
792 > woorkstations to be shut down overnight to save power.
795 - Autolabel should be specified by DIR instead of SD.
798 - AutoScan (check checksum of tape)
799 - Format command = "format /dev/nst0"
803 - Seek resolution (usually corresponds to buffer size)
804 - EODErrorCode=ENOSPC or code
805 - Partial Read error code
806 - Partial write error code
807 - Nonformatted read error
808 - Nonformatted write error
809 - WriteProtected error
813 - IgnoreCloseErrors=yes
823 - FD sends unsaved file list to Director at end of job (see
825 - File daemon should build list of files skipped, and then
826 at end of save retry and report any errors.
827 - Write a Storage daemon that uses pipes and
828 standard Unix programs to write to the tape.
830 - Need something that monitors the JCR queue and
831 times out jobs by asking the deamons where they are.
832 - Enhance Jmsg code to permit buffering and saving to disk.
833 - device driver = "xxxx" for drives.
835 - Ensure that /dev/null works
836 - Need report class for messages. Perhaps
837 report resource where report=group of messages
838 - enhance scan_attrib and rename scan_jobtype, and
839 fill in code for "since" option
840 - Director needs a time after which the report status is sent
841 anyway -- or better yet, a retry time for the job.
842 - Don't reschedule a job if previous incarnation is still running.
843 - Some way to automatically backup everything is needed????
844 - Need a structure for pending actions:
846 - termination status (part of buffered msgs?)
848 Read, Write, Clean, Delete
849 - Login to Bacula; Bacula users with different permissions:
850 owner, group, user, quotas
851 - Store info on each file system type (probably in the job header on tape.
852 This could be the output of df; or perhaps some sort of /etc/mtab record.
854 ========= ideas ===============
855 From: "Jerry K. Schieffer" <jerry@skylinetechnology.com>
856 To: <kern@sibbald.com>
857 Subject: RE: [Bacula-users] future large programming jobs
858 Date: Thu, 26 Feb 2004 11:34:54 -0600
860 I noticed the subject thread and thought I would offer the following
861 merely as sources of ideas, i.e. something to think about, not even as
862 strong as a request. In my former life (before retiring) I often
863 dealt with backups and storage management issues/products as a
864 developer and as a consultant. I am currently migrating my personal
865 network from amanda to bacula specifically because of the ability to
866 cross media boundaries during storing backups.
867 Are you familiar with the commercial product called ADSM (I think IBM
868 now sells it under the Tivoli label)? It has a couple of interesting
869 ideas that may apply to the following topics.
871 1. Migration: Consider that when you need to restore a system, there
872 may be pressure to hurry. If all the information for a single client
873 can eventually end up on the same media (and in chronological order),
874 the restore is facillitated by not having to search past information
875 from other clients. ADSM has the concept of "client affinity" that
876 may be associated with it's storage pools. It seems to me that this
877 concept (as an optional feature) might fit in your architecture for
880 ADSM also has the concept of defining one or more storage pools as
881 "copy pools" (almost mirrors, but only in the sense of contents).
882 These pools provide the ability to have duplicte data stored both
883 onsite and offsite. The copy process can be scheduled to be handled
884 by their storage manager during periods when there is no backup
885 activity. Again, the migration process might be a place to consider
886 implementing something like this.
889 > It strikes me that it would be very nice to be able to do things
891 > have the Job(s) backing up the machines run, and once they have all
892 > completed, start a migration job to copy the data from disks Volumes
894 > a tape library and then to offsite storage. Maybe this can already
896 > done with some careful scheduling and Job prioritzation; the events
897 > mechanism described below would probably make it very easy.
899 This is the goal. In the first step (before events), you simply
901 the Migration to tape later.
903 2. Base jobs: In ADSM, each copy of each stored file is tracked in
904 the database. Once a file (unique by path and metadata such as dates,
905 size, ownership, etc.) is in a copy pool, no more copies are made. In
906 other words, when you start ADSM, it begins like your concept of a
907 base job. After that it is in the "incremental" mode. You can
908 configure the number of "generations" of files to be retained, plus a
909 retention date after which even old generations are purged. The
910 database tracks the contents of media and projects the percentage of
911 each volume that is valid. When the valid content of a volume drops
912 below a configured percentage, the valid data are migrated to another
913 volume and the old volume is marked as empty. Note, this requires
914 ADSM to have an idea of the contents of a client, i.e. marking the
915 database when an existing file was deleted, but this would solve your
916 issue of restoring a client without restoring deleted files.
918 This is pretty far from what bacula now does, but if you are going to
919 rip things up for Base jobs,.....
920 Also, the benefits of this are huge for very large shops, especially
921 with media robots, but are a pain for shops with manual media
925 > Base jobs sound pretty useful, but I'm not dying for them.
927 Nobody is dying for them, but when you see what it does, you will die
930 3. Restoring deleted files: Since I think my comments in (2) above
931 have low probability of implementation, I'll also suggest that you
932 could approach the issue of deleted files by a mechanism of having the
933 fd report to the dir, a list of all files on the client for every
934 backup job. The dir could note in the database entry for each file
935 the date that the file was seen. Then if a restore as of date X takes
936 place, only files that exist from before X until after X would be
937 restored. Probably the major cost here is the extra date container in
938 each row of the files table.
940 Thanks for "listening". I hope some of this helps. If you want to
941 contact me, please send me an email - I read some but not all of the
942 mailing list traffic and might miss a reply there.
944 Please accept my compliments for bacula. It is doing a great job for
945 me!! I sympathize with you in the need to wrestle with excelence in
946 execution vs. excelence in feature inclusion.
951 ==============================
954 - Design at hierarchial storage for Bacula. Migration and Clone.
955 - Implement FSM (File System Modules).
956 - Audit M_ error codes to ensure they are correct and consistent.
957 - Add variable break characters to lex analyzer.
958 Either a bit mask or a string of chars so that
959 the caller can change the break characters.
960 - Make a single T_BREAK to replace T_COMMA, etc.
961 - Ensure that File daemon and Storage daemon can
962 continue a save if the Director goes down (this
963 is NOT currently the case). Must detect socket error,
964 buffer messages for later.
965 - Enhance time/duration input to allow multiple qualifiers e.g. 3d2h
966 - Add ability to backup to two Storage devices (two SD sessions) at
967 the same time -- e.g. onsite, offsite.
968 - Add the ability to consolidate old backup sets (basically do a restore
969 to tape and appropriately update the catalog). Compress Volume sets.
970 Might need to spool via file is only one drive is available.
971 - Compress or consolidate Volumes of old possibly deleted files. Perhaps
972 someway to do so with every volume that has less than x% valid
976 Migration: Move a backup from one Volume to another
977 Clone: Copy a backup -- two Volumes
979 Bacula Migration is based on Jobs (apparently Networker is file by file).
981 Migration triggered by:
985 Highwater mark (keep total size)
990 ======================================================
992 It is somewhat like a Full save becomes an incremental since
993 the Base job (or jobs) plus other non-base files.
995 - A Base backup is same as Full backup, just different type.
996 - New BaseFiles table that contains:
998 BaseJobId - Base JobId referenced for this FileId (needed ???)
999 JobId - JobId currently running
1000 FileId - File not backed up, exists in Base Job
1001 FileIndex - FileIndex from Base Job.
1002 i.e. for each base file that exists but is not saved because
1003 it has not changed, the File daemon sends the JobId, BaseId,
1004 FileId, FileIndex back to the Director who creates the DB entry.
1005 - To initiate a Base save, the Director sends the FD
1006 the FileId, and full filename for each file in the Base.
1007 - When the FD finds a Base file, he requests the Director to
1008 send him the full File entry (stat packet plus MD5), or
1009 conversely, the FD sends it to the Director and the Director
1010 says yes or no. This can be quite rapid if the FileId is kept
1011 by the FD for each Base Filename.
1012 - It is probably better to have the comparison done by the FD
1013 despite the fact that the File entry must be sent across the
1015 - An alternative would be to send the FD the whole File entry
1016 from the start. The disadvantage is that it requires a lot of
1017 space. The advantage is that it requires less communications
1019 - The Job record must be updated to indicate that one or more
1021 - At end of Job, FD returns:
1022 1. Count of base files/bytes not written to tape (i.e. matches)
1023 2. Count of base file that were saved i.e. had changed.
1024 - No tape record would be written for a Base file that matches, in the
1025 same way that no tape record is written for Incremental jobs where
1026 the file is not saved because it is unchanged.
1027 - On a restore, all the Base file records must explicitly be
1028 found from the BaseFile tape. I.e. for each Full save that is marked
1029 to have one or more Base Jobs, search the BaseFile for all occurrences
1031 - An optimization might be to make the BaseFile have:
1037 This would avoid the need to explicitly fetch each File record for
1038 the Base job. The Base Job record will be fetched to get the
1039 VolSessionId and VolSessionTime.
1040 =========================================================
1043 ==========================================================
1045 For each Incremental job that is run, there may be files that
1046 were found but not saved because they were locked (this applies
1047 only to Windows). Such a system could send back to the Director
1048 a list of Unsaved files.
1050 - New UnSavedFiles table that contains:
1054 - Then in the next Incremental job, the list of Unsaved Files will be
1055 feed to the FD, who will ensure that they are explicitly chosen even
1056 if standard date/time check would not have selected them.
1057 =============================================================
1060 Done: (see kernsdone for more)
1063 - John's Full save failed with 1.32c FD and 1.31 Dir no FD status,
1064 and no error message.
1065 - Add fd and st as Console keywords.
1066 - Recycling volume with a Slot requires an operator intervention:
1067 rufus-dir: Start Backup JobId 18, Job=kernsave.2003-11-01_21.23.52
1068 rufus-dir: Pruned 1 Job on Volume Vol01 from catalog.
1069 rufus-dir: There are no Jobs associated with Volume Vol01. Marking it purged.
1070 rufus-dir: Recycled volume "Vol01"
1071 rufus-sd: Please mount Volume "Vol01" on Storage Device "DDS-4" for Job kernsave.2003-11-01_21.23.52
1072 Use "mount" command to release Job.
1073 - Implement Dan's bacula script (email of 26 Oct).
1074 - Add JobName= to VerifyToCatalog so that all verifies can be done at the end.
1075 - Edit the Client/Storage name into authentication failure messages.
1076 - Fix packet too big problem. This is most likely a Windows TCP stack
1078 - Implement ClientRunBeforeJob and ClientRunAfterJob.
1079 - Implement forward spacing block/file: position_device(bsr) --
1080 just before read_block_from_device();
1083 Multiple drive autochanger data: see Alan Brown
1084 mtx -f xxx unloadStorage Element 1 is Already Full(drive 0 was empty)
1085 Unloading Data Transfer Element into Storage Element 1...source Element
1086 Address 480 is Empty
1088 (drive 0 was empty and so was slot 1)
1089 > mtx -f xxx load 15 0
1090 no response, just returns to the command prompt when complete.
1091 > mtx -f xxx status Storage Changer /dev/changer:2 Drives, 60 Slots ( 2 Import/Export )
1092 Data Transfer Element 0:Full (Storage Element 15 Loaded):VolumeTag = HX001
1093 Data Transfer Element 1:Empty
1094 Storage Element 1:Empty
1095 Storage Element 2:Full :VolumeTag=HX002
1096 Storage Element 3:Full :VolumeTag=HX003
1097 Storage Element 4:Full :VolumeTag=HX004
1098 Storage Element 5:Full :VolumeTag=HX005
1099 Storage Element 6:Full :VolumeTag=HX006
1100 Storage Element 7:Full :VolumeTag=HX007
1101 Storage Element 8:Full :VolumeTag=HX008
1102 Storage Element 9:Full :VolumeTag=HX009
1103 Storage Element 10:Full :VolumeTag=HX010
1104 Storage Element 11:Empty
1105 Storage Element 12:Empty
1106 Storage Element 13:Empty
1107 Storage Element 14:Empty
1108 Storage Element 15:Empty
1109 Storage Element 16:Empty....
1110 Storage Element 28:Empty
1111 Storage Element 29:Full :VolumeTag=CLNU01L1
1112 Storage Element 30:Empty....
1113 Storage Element 57:Empty
1114 Storage Element 58:Full :VolumeTag=NEX261L2
1115 Storage Element 59 IMPORT/EXPORT:Empty
1116 Storage Element 60 IMPORT/EXPORT:Empty
1118 Unloading Data Transfer Element into Storage Element 15...done
1120 (just to verify it remembers where it came from, however it can be
1121 overrriden with mtx unload {slotnumber} to go to any storage slot.)
1123 There needs to be a table of drive # to devices somewhere - If there are
1124 multiple changers or drives there may not be a 1:1 correspondance between
1125 changer drive number and system device name - and depending on the way the
1126 drives are hooked up to scsi busses, they may not be linearly numbered
1127 from an offset point either.something like
1129 Autochanger drives = 2
1130 Autochanger drive 0 = /dev/nst1
1131 Autochanger drive 1 = /dev/nst2
1132 IMHO, it would be _safest_ to use explicit mtx unload commands at all
1133 times, not just for multidrive changers. For a 1 drive changer, that's
1139 MTX's manpage (1.2.15):
1140 unload [<slotnum>] [ <drivenum> ]
1141 Unloads media from drive <drivenum> into slot
1142 <slotnum>. If <drivenum> is omitted, defaults to
1143 drive 0 (as do all commands). If <slotnum> is
1144 omitted, defaults to the slot that the drive was
1145 loaded from. Note that there's currently no way
1146 to say 'unload drive 1's media to the slot it
1147 came from', other than to explicitly use that
1148 slot number as the destination.AB
1154 undef# camcontrol devlist
1155 <WANGTEK 51000 SCSI M74H 12B3> at scbus0 target 2 lun 0 (pass0,sa0)
1156 <ARCHIVE 4586XX 28887-XXX 4BGD> at scbus0 target 4 lun 0 (pass1,sa1)
1157 <ARCHIVE 4586XX 28887-XXX 4BGD> at scbus0 target 4 lun 1 (pass2)
1159 tapeinfo -f /dev/sg0 with a bad tape in drive 1:
1160 [kern@rufus mtx-1.2.17kes]$ ./tapeinfo -f /dev/sg0
1161 Product Type: Tape Drive
1163 Product ID: 'C5713A '
1165 Attached Changer: No
1166 TapeAlert[3]: Hard Error: Uncorrectable read/write error.
1167 TapeAlert[20]: Clean Now: The tape drive neads cleaning NOW.
1174 Medium Type: Not Loaded
1177 DataCompEnabled: yes
1178 DataCompCapable: yes
1179 DataDeCompEnabled: yes
1186 Handling removable disks
1188 From: Karl Cunningham <karlc@keckec.com>
1190 My backups are only to hard disk these days, in removable bays. This is my
1191 idea of how a backup to hard disk would work more smoothly. Some of these
1192 things Bacula does already, but I mention them for completeness. If others
1193 have better ways to do this, I'd like to hear about it.
1195 1. Accommodate several disks, rotated similar to how tapes are. Identified
1196 by partition volume ID or perhaps by the name of a subdirectory.
1197 2. Abort & notify the admin if the wrong disk is in the bay.
1198 3. Write backups to different subdirectories for each machine to be backed
1200 4. Volumes (files) get created as needed in the proper subdirectory, one
1202 5. When a disk is recycled, remove or zero all old backup files. This is
1203 important as the disk being recycled may be close to full. This may be
1204 better done manually since the backup files for many machines may be
1205 scattered in many subdirectories.
1210 - To pass Include 1 or two letter commands
1211 I Name Include name - first record
1212 B Name Base name - repeat
1215 E zzz Exclude expression (wild card)
1217 D "reader" Reader program
1218 T "writer" Writer program
1219 O Options In current commpressed format
1220 (compression, signature, onefs, recurse, sparse,
1221 replace, verify options, ...)
1223 B BaseName Start second option set any letter
1226 F Number Number of filenames to follow
1231 F Number Number of filenames to follow
1234 - Add regression of btape "fill"
1236 - Implement "label slots=1,2... pool=yyy barcodes"
1237 - Mark a non-removable disk Volume in error rather than asking sys op to
1239 - Implement Fixed storage LabelFormat test.
1240 - Add reporting in attr despooling.
1241 - Figure out how to use ssh or stunnel to protect Bacula communications.
1242 Add Dan's work to manual See ssl.txt
1245 - Implement fast tree insert (doubly linked list)
1246 - Disallow using Internal database
1247 - Feedback while the restore tree is being built.
1248 - Add detection of Whitebox release in ./configure
1249 - Add InChanger to "list media"
1250 - Implement second cut of SIGHUP in Dir
1251 (Implement resources on a single pointer)
1252 - Add regular expressions to FileSets (needs testing).
1253 - Test new despooling error recovery code when partition fills.
1254 - Sort Scheduled jobs status listing by start time.
1255 - Add priority to Scheduled jobs status listing.
1256 - Look at Win32 inc problem when new directory added files not saved???
1257 - Require resource names to be unique.
1258 - Make sure that all errors from libacl are printed.
1259 - Make FD run on Win95 if possible (not really possible).
1260 - Fix GROUP BYs in all SQL (done by Dan -- thanks)
1261 - Make entering multiple Storage names in Dir illegal.
1262 - Make btape release the drive during the "test" append.
1264 You have selected the following JobIds: 739,856,797
1265 Building directory tree for JobId 739 ...
1266 Building directory tree for JobId 856 ...
1267 Building directory tree for JobId 797 ...3
1268 Jobs inserted into the tree.
1269 - Fix errno handling in win32 compat routines.
1270 - Add better error codes to run_program (10000+)
1271 - Revisit and revise Disaster Recovery (fix SCSI and RAID
1273 - When passwords do not match, print message that points the
1275 - Do tape alerts -- see tapealert.txt
1276 - Find memory leaks in address_conf.c
1277 - Network order of port and ip addresses.
1278 - SetIP in dird/fd_cmds.c is broken.
1279 - don't use inet_addr() it is deprecated.
1280 - Fix code in filed.c for init_bsock();
1281 - Fix code in console.c for init_bsock();
1282 - Solve the termcap.h problem on Solaris configure.
1283 - Make Verify jobs require exclusive use of Volume as Restore
1285 - Fix restore ++++ that get intermingled with "Building directory tree"
1286 - Fix doc in dirdconf.html for @, where the file must
1287 have not a list of files, but
1290 - Test Win32 errno handling.
1291 - port 1.34.6-block.patch to 1.35
1292 - Look at Chris' patch for bscan bug.
1293 - Fix error handling in spooling both data and attribute.
1294 - Implement Ignore FileSet Change.
1295 - Doc new duration time input editing.
1296 - Bacula rescue CDROM implement isolinux
1297 - Make sure Qmsgs are dequeued by FD and SD.
1298 - Check if ACLs allocated at dird_conf.c:1214 are being properly
1300 - Test/doc Tape Alerts
1301 - Doc dbcheck eliminate orphaned clients.
1302 - Doc Phil's new delete job jobid scanning code.
1303 - Document that console commands can be abbreviated.
1304 - Doc update AllFromVol
1305 - Doc -p option in stored
1306 - New IP address specification is used as follows:
1307 [sdaddresses|diraddresses|fdaddresses] = { [[ip|ipv4|ipv6] = {
1308 [[addr|port] = [^ ]+[\n;]+] }] }
1310 so it could look for example like this:
1311 SDaddresses = { ip = {
1312 addr = 1.2.3.4; port = 1205; }
1314 addr = 1.2.3.4; port = http; }
1327 addr = 201:220:222::2
1330 addr = bluedot.thun.net
1333 as a consequence, you can now specify multiple IP addresses and
1334 ports to be used. In the case of a server, it will listen on
1335 all those that you specify. In the case of connecting to the server,
1336 Bacula will attempt connecting to one at a time until it succeeds.
1337 And, in a few other special cases, Bacula will use only the first
1340 The default port numbers are still the same and the services and hosts
1341 are also resolved by name. So now you could use the real names for the
1344 An ip section will allow resolution to either an ipv4 or an ipv6 address.
1345 An ipv4 section forces the resolution to be only ipv4, and an ipv6 section
1346 forces the resolution to be only ipv6.
1347 - Fix silly restriction requiring Include { Options { xxx } } to be
1349 - Restore c: with a prefix into /prefix/c/ to prevent c: and d:
1350 files with the same name from overwritting each other.
1351 - Add "Multiple connections = yes/no" to catalog resource.
1352 - Add new DCR calling sequences everywhere in SD. This will permit
1353 simultaneous use of multiple devices by a single job.