9 - Does ClientRunAfterJob fail the job on a bad return code?
10 - Document cleaning up the spool files:
11 db, pid, state, bsr, mail, conmsg, spool
12 - Document the multiple-drive-changer.txt script.
13 - Pruning with Admin job.
14 - Does WildFile match against full name? Doc.
15 - %d and %v only valid on Director, not for ClientRunBefore/After.
18 - Implement status that shows why a job is being held in reserve, or
19 rather why none of the drives are suitable.
20 - Implement a way to disable a drive (so you can use the second
21 drive of an autochanger, and the first one will not be used or
23 - Implement code that makes the Dir aware that a drive is an
24 autochanger (so the user doesn't need to use the Autochanger = yes
28 - Make hardlink code at line 240 of find_one.c use binary search.
29 - Queue warning/error messages during restore so that they
30 are reported at the end of the report rather than being
31 hidden in the file listing ...
32 - A Volume taken from Scratch should take on the retention period
34 - Correct doc for Maximum Changer Wait (and others) accepting only
36 - Fix Maximum Changer Wait (and others) to accept qualifiers.
37 - Look at -D_FORTIFY_SOURCE=2
38 - Add Win32 FileSet definition somewhere
39 - Look at fixing restore status stats in SD.
40 - Make selection of Database used in restore correspond to
42 - Implement a mode that says when a hard read error is
43 encountered, read many times (as it currently does), and if the
44 block cannot be read, skip to the next block, and try again. If
45 that fails, skip to the next file and try again, ...
47 create table LevelType (LevelType binary(1), LevelTypeLong tinyblob);
48 insert into LevelType (LevelType,LevelTypeLong) values
52 - Add ACL to restore only to original location.
53 - Add a recursive mark command (rmark) to restore.
54 - "Minimum Job Interval = nnn" sets minimum interval between Jobs
55 of the same level and does not permit multiple simultaneous
56 running of that Job (i.e. lets any previous invocation finish
57 before doing Interval testing).
58 - Look at simplifying File exclusions.
59 - Fix store_yesno to be store_bitmask.
60 - New directive "Delete purged Volumes"
61 - new pool XXX with ScratchPoolId = MyScratchPool's PoolId and
62 let it fill itself, and RecyclePoolId = XXX's PoolId so I can
63 see if it become stable and I just have to supervise
65 - If I want to remove this pool, I set RecyclePoolId = MyScratchPool's
66 PoolId, and when it is empty remove it.
67 - Figure out how to recycle Scratch volumes back to the Scratch
70 - Allow Check Labels to be used with Bacula labels.
71 - "Resuming" a failed backup (lost line for example) by using the
72 failed backup as a sort of "base" job.
74 - Email to the user when the tape is about to need changing x
75 days before it needs changing.
76 - Command to show next tape that will be used for a job even
77 if the job is not scheduled.
78 --- create_file.c.orig Fri Jul 8 12:13:05 2005
79 +++ create_file.c Fri Jul 8 12:13:07 2005
81 attr->ofname, be.strerror());
84 + } else if(S_ISSOCK(attr->statp.st_mode)) {
85 + Dmsg1(200, "Skipping socket: %s\n", attr->ofname);
87 Dmsg1(200, "Restore node: %s\n", attr->ofname);
88 if (mknod(attr->ofname, attr->statp.st_mode, attr->statp.st_rdev) != 0 && errno != EEXIST) {
89 - From: Arunav Mandal <amandal@trolltech.com>
90 1. When jobs are running and bacula for some reason crashes or if I do a
91 restart it remembers and jobs it was running before it crashed or restarted
92 as of now I loose all jobs if I restart it.
94 2. When spooling and in the midway if client is disconnected for instance a
95 laptop bacula completely discard the spool. It will be nice if it can write
96 that spool to tape so there will be some backups for that client if not all.
98 3. We have around 150 clients machines it will be nice to have a option to
99 upgrade all the client machines bacula version automatically.
101 4. Atleast one connection should be reserved for the bconsole so at heavy load
102 I should connect to the director via bconsole which at sometimes I can't
104 5. Another most important feature that is missing, say at 10am I manually
105 started backup of client abc and it was a full backup since client abc has
106 no backup history and at 10.30am bacula again automatically started backup of
107 client abc as that was in the schedule. So now we have 2 multiple Full
108 backups of the same client and if we again try to start a full backup of
109 client backup abc bacula won't complain. That should be fixed.
111 - Fix bpipe.c so that it does not modify results pointer.
112 ***FIXME*** calling sequence should be changed.
114 #3 Migration (Move, Copy, Archive Jobs)
115 #7 Single Job Writing to Multiple Storage Devices
116 - Reserve blocks other restore jobs when first cannot connect
118 - Add true/false to conf same as yes/no
119 - For Windows disaster recovery see http://unattended.sf.net/
120 - regardless of the retention period, Bacula will not prune the
121 last Full, Diff, or Inc File data until a month after the
122 retention period for the last Full backup that was done.
123 - update volume=xxx --- add status=Full
124 - Remove old spool files on startup.
125 - Exclude SD spool/working directory.
126 - Refuse to prune last valid Full backup. Same goes for Catalog.
128 - Make a callback when Rerun failed levels is called.
129 - Give Python program access to Scheduled jobs.
130 - Add setting Volume State via Python.
131 - Python script to save with Python, not save, save with Bacula.
132 - Python script to do backup.
134 - Change the Priority, Client, Storage, JobStatus (error)
135 at the start of a job.
136 - Why is SpoolDirectory = /home/bacula/spool; not reported
137 as an error when writing a DVD?
138 - Make bootstrap file handle multiple MediaTypes (SD)
139 - Remove all old Device resource code in Dir and code to pass it
140 back in SD -- better, rework it to pass back device statistics.
141 - Check locking of resources -- be sure to lock devices where previously
142 resources were locked.
143 - The last part is left in the spool dir.
146 - In restore don't compare byte count on a raw device -- directory
147 entry does not contain bytes.
148 - To mark files as deleted, run essentially a Verify to disk, and
149 when a file is found missing (MarkId != JobId), then create
150 a new File record with FileIndex == -1. This could be done
151 by the FD at the same time as the backup.
155 MA = (last_MA * 3 + rate) / 4
156 rate = (bytes - last_bytes) / (runtime - last_runtime)
157 - Max Vols limit in Pool off by one?
158 - Implement Files/Bytes,... stats for restore job.
159 - Implement Total Bytes Written, ... for restore job.
160 - Despool attributes simultaneously with data in a separate
161 thread, rejoined at end of data spooling.
162 - 7. Implement new Console commands to allow offlining/reserving drives,
163 and possibly manipulating the autochanger (much asked for).
164 - Add start/end date editing in messages (%t %T, %e?) ...
165 - Add ClientDefs similar to JobDefs.
166 - Print more info when bextract -p accepts a bad block.
167 - Fix FD JobType to be set before RunBeforeJob in FD.
168 - Look at adding full Volume and Pool information to a Volume
169 label so that bscan can get *all* the info.
170 - If the user puts "Purge Oldest Volume = yes" or "Recycle Oldest Volume = yes"
171 and there is only one volume in the pool, refuse to do it -- otherwise
172 he fills the Volume, then immediately starts reusing it.
173 - Implement copies and stripes.
174 - Add history file to console.
175 - Each file on tape creates a JobMedia record. Peter has 4 million
176 files spread over 10000 tape files and four tapes. A restore takes
177 16 hours to build the restore list.
178 - Add and option to check if the file size changed during backup.
179 - Make sure SD deletes spool files on error exit.
180 - Delete old spool files when SD starts.
181 - When labeling tapes, if you enter 000026, Bacula uses
182 the tape index rather than the Volume name 000026.
183 - Add offline tape command to Bacula console.
185 Enter MediaId or Volume name: 32
186 Enter new Volume name: DLT-20Dec04
187 Automatically selected Pool: Default
188 Connecting to Storage daemon DLTDrive at 192.168.68.104:9103 ...
189 Sending relabel command from "DLT-28Jun03" to "DLT-20Dec04" ...
190 block.c:552 Write error at 0:0 on device /dev/nst0. ERR=Bad file descriptor.
191 Error writing final EOF to tape. This tape may not be readable.
192 dev.c:1207 ioctl MTWEOF error on /dev/nst0. ERR=Permission denied.
193 askdir.c:219 NULL Volume name. This shouldn't happen!!!
194 3912 Failed to label Volume: ERR=dev.c:1207 ioctl MTWEOF error on /dev/nst0. ERR=Permission denied.
195 Label command failed for Volume DLT-20Dec04.
196 Do not forget to mount the drive!!!
197 - Bug: if a job is manually scheduled to run later, it does not appear
198 in any status report and cannot be cancelled.
200 ==== Keeping track of deleted files ====
201 My "trick" for keeping track of deletions is the following.
202 Assuming the user turns on this option, after all the files
203 have been backed up, but before the job has terminated, the
204 FD will make a pass through all the files and send their
205 names to the DIR (*exactly* the same as what a Verify job
206 currently does). This will probably be done at the same
207 time the files are being sent to the SD avoiding a second
208 pass. The DIR will then compare that to what is stored in
209 the catalog. Any files in the catalog but not in what the
210 FD sent will receive a catalog File entry that indicates
211 that at that point in time the file was deleted.
213 During a restore, any file initially picked up by some
214 backup (Full, ...) then subsequently having a File entry
215 marked "delete" will be removed from the tree, so will not
216 be restored. If a file with the same name is later OK it
217 will be inserted in the tree -- this already happens. All
218 will be consistent except for possible changes during the
221 Since I'm on the subject, some of you may be wondering what
222 the utility of the in memory tree is if you are going to
223 restore everything (at least it comes up from time to time
224 on the list). Well, it is still *very* useful because it
225 allows only the last item found for a particular filename
226 (full path) to be entered into the tree, and thus if a file
227 is backed up 10 times, only the last copy will be restored.
228 I recently (last Friday) restored a complete directory, and
229 the Full and all the Differential and Incremental backups
230 spanned 3 Volumes. The first Volume was not even mounted
231 because all the files had been updated and hence backed up
232 since the Full backup was made. In this case, the tree
233 saved me a *lot* of time.
235 Make sure this information is stored on the tape too so
236 that it can be restored directly from the tape.
238 Comments from Martin Simmons (I think they are all covered):
239 Ok, that should cover the basics. There are few issues though:
241 - Restore will depend on the catalog. I think it is better to include the
242 extra data in the backup as well, so it can be seen by bscan and bextract.
244 - I'm not sure if it will preserve multiple hard links to the same inode. Or
245 maybe adding or removing links will cause the data to be dumped again?
247 - I'm not sure if it will handle renamed directories. Possibly it will work
248 by dumping the whole tree under a renamed directory?
250 - It remains to be seen how the backup performance of the DIR's will be
251 affected when comparing the catalog for a large filesystem.
256 - Add Pool/Storage override regression test.
257 - Add delete JobId to regression.
258 - Add a regression test for dbcheck.
259 - New test to add bscan to four-concurrent-jobs regression,
260 i.e. after the four-concurrent jobs zap the
261 database as is done in the bscan-test, then use bscan to
262 restore the database, do a restore and compare with the
264 - Add restore of specific JobId to regression (item 3
265 on the restore prompt)
266 - Add IPv6 to regression
267 - Add database test to regression. Test each function like delete,
270 - AntiVir can slow down backups on Win32 systems.
271 - Win32 systems with FAT32 can be much slower than NTFS for
272 more than 1000 files per directory.
276 - A HOLD command to stop all jobs from starting.
277 - A PAUSE command to pause all running jobs ==> release the
279 - Media Type = LTO,LTO-2,LTO-3
280 Media Type Read = LTO,LTO2,LTO3
281 Media Type Write = LTO2, LTO3
283 === From Carsten Menke <bootsy52@gmx.net>
285 Following is a list of what I think in the situations where I'm faced with,
286 could be a usefull enhancement to bacula, which I'm certain other users will
287 benefit from as well.
289 1. NextJob/NextJobs Directive within a Job Resource in the form of
290 NextJobs = job1,job2.
293 I currently solved the problem with running multiple jobs each after each
294 by setting the Max Wait Time for a job to 8 hours, and give
295 the jobs different Priorities. However, there scenarios where
296 1 Job is directly depending on another job, so if the former job fails,
297 the job after it needn't to be run
298 while maybe other jobs should run despite of that
301 A Backup Job and a Verify job, if the backup job fails there is no need to run
302 the verify job, as the backup job already failed. However, one may like
303 to backup the Catalog to disk despite of that the main backup job failed.
306 I see that this is related to the Event Handlers which are on the ToDo
307 list, also it is maybe a good idea to check for the return value and
308 execute different actions based on the return value
311 3. offline capability to bconsole
314 Currently I use a script which I execute within the last Job via the
315 RunAfterJob Directive, to release and eject the tape.
316 So I have to call bconsole "release=Storage-Name" and afterwards
317 mt -f /dev/nst0 eject to get the tape out.
319 If I have multiple Storage Devices, than these may not be /dev/nst0 and
320 I have to modify the script or call it with parameters etc.
321 This would actually not be needed, as everything is already defined
322 in bacula-sd.conf and if I can invoke bconsole with the
323 storage name via $1 in the script than I'm done and information is
326 4. %s for Storage Name added to the chars being substituted in "RunAfterJob"
330 For the reason mentioned in 3. to have the ability to call a
331 script with /scripts/foobar %s and in the script use $1
332 to pass the Storage Name to bconsole
334 5. Setting Volume State within a Job Resource
337 Instead of using "Maximum Volume Jobs" in the Pool Resource,
338 I would have the possibilty to define
339 in a Job Resource that after this certain job is run, the Volume State
340 should be set to "Volume State = Used", this give more flexibility (IMHO).
342 6. Localization of Bacula Messages
345 Unfortunatley many,many people I work with don't speak english very well.
346 So if at least the Reporting messages would be localized then they
347 would understand that they have to change the tape,etc. etc.
349 I volunteer to do the german translations, and if I can convince my wife also
350 french and Morre (western african language).
352 7. OK, this is evil, probably bound to security risks and maybe not possible
353 due to the design of bacula.
355 Implementation of Backtics ( `command` ) for shell comand execution to
356 the "Label Format" Directive.
360 Currently I have defined BACULA_DAY_OF_WEEK="day1|day2..." resulting in
361 Label Format = "HolyBackup-${BACULA_DAY_OF_WEEK[${WeekDay}]}". If I could
362 use backticks than I could use "Label Format = HolyBackup-`date +%A` to have
363 the localized name for the day of the week appended to the
364 format string. Then I have the tape labeled automatically with weekday
365 name in the correct language.
367 - Yes, that is surely the case. I probably should turn those into Warning
368 errors. In addition, you just made me think that it might not be bad to
369 add an option to check the file size after backing up the file and
370 report if it changes. This would be done as an option because it would
373 Kern, good idea. If you do do that, mention in the output: file
374 shrunk, or file expanded, just to make it obvious to the user
375 (without having to the refer to file size), just how the file size
378 Would this option be for all file, or just one file? Or a fileset?
379 - Make output from status use html table tags for nicely
380 presenting in a browser.
381 - Can one write tapes faster with 8192 byte block sizes?
382 - Document security problems with the same password for everyone in
383 rpm and Win32 releases.
384 - Browse generations of files.
385 - I've seen an error when my catalog's File table fills up. I
386 then have to recreate the File table with a larger maximum row
387 size. Relevant information is at
388 http://dev.mysql.com/doc/mysql/en/Full_table.html ; I think the
389 "Installing and Configuring MySQL" chapter should talk a bit
390 about this potential problem, and recommend a solution.
391 - For Solaris must use POSIX awk.
392 - Want speed of writing to tape while despooling.
393 - Supported autochanger:
401 Wangtek 6525ES (SCSI-1 QIC drive, 525MB), under Linux 2.4.something,
402 bacula 1.36.0/1 works with blocksize 16k INSIDE bacula-sd.conf.
403 - Add regex from http://www.pcre.org to Bacula for Win32.
404 - Use only shell tools no make in CDROM package.
405 - Include within include does it work?
406 - Implement a Pool of type Cleaning?
407 - Implement VolReadTime and VolWriteTime in SD
408 - Modify Backing up Your Database to include a bootstrap file.
409 - Think about making certain database errors fatal.
410 - Look at correcting the time jump in the scheduler for daylight
411 savings time changes.
412 - Add a "real" timer to network connections.
413 - Promote to Full = Time period
414 - Check dates entered by user for correctness (month/day/... ranges)
415 - Compress restore Volume listing by date and first file.
416 - Look at patches/bacula_db.b2z postgresql that loops during restore.
418 - Perhaps add read/write programs and/or plugins to FileSets.
419 - How to handle backing up portables ...
420 - Add some sort of guaranteed Interval for upgrading jobs.
421 - Can we write the state file after every job terminates? On Win32
422 the system crashes and the state file is not updated.
425 Documentation to do: (any release a little bit at a time)
426 - Doc to do unmount before removing magazine.
427 - Alternative to static linking "ldd prog" save all binaries listed,
428 restore them and point LD_LIBRARY_PATH to them.
429 - Document add "</dev/null >/dev/null 2>&1" to the bacula-fd command line
430 - Document query file format.
431 - Add more documentation for bsr files.
432 - Document problems with Verify and pruning.
433 - Document how to use multiple databases.
434 - VXA drives have a "cleaning required"
435 indicator, but Exabyte recommends preventive cleaning after every 75
438 In this context, it should be noted that Exabyte has a command-line
439 vxatool utility available for free download. (The current version is
440 vxatool-3.72.) It can get diagnostic info, read, write and erase tapes,
441 test the drive, unload tapes, change drive settings, flash new firmware,
443 Of particular interest in this context is that vxatool <device> -i will
444 report, among other details, the time since last cleaning in tape motion
445 minutes. This information can be retrieved (and settings changed, for
446 that matter) through the generic-SCSI device even when Bacula has the
447 regular tape device locked. (Needless to say, I don't recommend
448 changing tape settings while a job is running.)
449 - Lookup HP cleaning recommendations.
450 - Lookup HP tape replacement recommendations (see trouble shooting autochanger)
451 - Document doing table repair
454 ===================================
455 - Add macro expansions in JobDefs.
456 Run Before Job = "SomeFile %{Level} %{Client}"
457 Write Bootstrap="/some/dir/%{JobName}_%{Client}.bsr"
458 - Use non-blocking network I/O but if no data is available, use
460 - Use gather write() for network I/O.
461 - Autorestart on crash.
462 - Add bandwidth limiting.
463 - Add acks every once and a while from the SD to keep
464 the line from timing out.
465 - When an error in input occurs and conio beeps, you can back
466 up through the prompt.
467 - Detect fixed tape block mode during positioning by looking at
468 block numbers in btape "test". Possibly adjust in Bacula.
469 - Fix list volumes to output volume retention in some other
470 units, perhaps via a directive.
471 - If opening a tape in read/write mode fails attempt to open
472 it in read-only mode, and mark the tape for read only.
473 - Allow Simultaneous Priorities = yes => run up to Max concurrent jobs even
474 with multiple priorities.
475 - If you use restore replace=never, the directory attributes for
476 non-existent directories will not be restored properly.
478 - see lzma401.zip in others directory for new compression
480 - Minimal autochanger handling in Bacula and in btape.
481 - Look into how tar does not save sockets and the possiblity of
482 not saving them in Bacula (Martin Simmons reported this).
483 - Fix restore jobs so that multiple jobs can run if they
484 are not using the same tape(s).
485 - Allow the user to select JobType for manual pruning/purging.
486 - bscan does not put first of two volumes back with all info in
488 - Implement the FreeBSD nodump flag in chflags.
489 - Figure out how to make named console messages go only to that
490 console and to the non-restricted console (new console class?).
491 - Make restricted console prompt for password if *ask* is set or
492 perhaps if password is undefined.
493 - Implement "from ISO-date/time every x hours/days/weeks/months" in
496 ==== from Marc Schoechlin
497 - the help-command should be more verbose
498 (it should explain the paramters of the different
500 -> its time-comsuming to consult the manual anytime
501 you need a special parameter
502 -> maybe its more easy to maintain this, if the
503 descriptions of that commands are outsourced to
505 - the cd-command should allow complete paths
506 i.e. cd /foo/bar/foo/bar
507 -> if a customer mails me the path to a certain file,
508 its faster to enter the specified directory
509 - if the password is not configured in bconsole.conf
510 you should be asked for it.
511 -> sometimes you like to do restore on a customer-machine
512 which shouldnt know the password for bacula.
513 -> adding the password to the file favours admins
514 to forget to remove the password after usage
516 the protection of that file is less important
517 - long-listed-output of commands should be scrollable
518 like the unix more/less-command does
519 -> if someone runs 200 and more machines, the lists could
520 be a little long and complex
521 - command-output should be shown column by column
522 to reduce scrolling and to increase clarity
524 - lsmark should list the selected files with full
526 - wildcards for selecting and file and directories would be nice
527 - any actions should be interuptable with STRG+C
528 - command-expansion would be pretty cool
530 - When the replace Never option is set, new directory permissions
531 are not restored. See bug 213. To fix this requires creating a
532 list of newly restored directories so that those directory
533 permissions *can* be restored.
534 - Compaction of Disk space by "migrating" Volumes that have pruned
535 Jobs (what criteria? size, #jobs, time).
536 - Add prune all command
537 - Document fact that purge can destroy a part of a restore by purging
538 one volume while others remain valid -- perhaps mark Jobs.
539 - Add multiple-media-types.txt
540 - look at mxt-changer.html
541 - Make ? do a help command (no return needed).
542 - Implement restore directory.
543 - Document streams and how to implement them.
544 - Try not to re-backup a file if a new hard link is added.
545 - Add feature to backup hard links only, but not the data.
546 - Fix stream handling to be simpler.
547 - Add Priority and Bootstrap to Run a Job.
548 - Eliminate Restore "Run Restore Job" prompt by allowing new "run command
550 - Remove View FileSet button from Run a Job dialog.
551 - Handle prompt for restore job at end of Restore command.
552 - Add display of total selected files to Restore window.
553 - Add tree pane to left of window.
554 - Add progress meter.
555 - Max wait time or max run time causes seg fault -- see runtime-bug.txt
556 - Document writing to a CD/DVD with Bacula.
557 - Add a "base" package to the window installer for pthreadsVCE.dll
558 which is needed by all packages.
559 - Add message to user to check for fixed block size when the forward
560 space test fails in btape.
561 - When unmarking a directory check if all files below are unmarked and
562 then remove the + flag -- in the restore tree.
563 - Possibly implement: Action = Unmount Device="TapeDrive1" in Admin jobs.
564 - Setup lrrd graphs: (http://www.linpro.no/projects/lrrd/) Mike Acar.
565 - Revisit the question of multiple Volumes (disk) on a single device.
566 - Add a block copy option to bcopy.
567 - Investigate adding Mac Resource Forks.
568 - Finish work on Gnome restore GUI.
569 - Fix "llist jobid=xx" where no fileset or client exists.
570 - For each job type (Admin, Restore, ...) require only the really necessary
571 fields.- Pass Director resource name as an option to the Console.
572 - Add a "batch" mode to the Console (no unsolicited queries, ...).
573 - Add a .list all files in the restore tree (probably also a list all files)
574 Do both a long and short form.
575 - Allow browsing the catalog to see all versions of a file (with
576 stat data on each file).
577 - Restore attributes of directory if replace=never set but directory
579 - Use SHA1 on authentication if possible.
580 - See comtest-xxx.zip for Windows code to talk to USB.
581 - Add John's appended files:
582 Appended = { /files/server/logs/http/*log }
583 and such files would be treated as follows.On a FULL backup, they would
584 be backed up like any other file.On an INCREMENTAL backup, where a
585 previous INCREMENTAL or FULL was already in thecatalogue and the length
586 of the file wasgreater than the length of the last backup, only thedata
587 added since the last backup will be dumped.On an INCREMENTAL backup, if
588 the length of the file is less than thelength of the file with the same
589 name last backed up, the completefile is dumped.On Windows systems, with
590 creation date of files, we can be evensmarter about this and not count
591 entirely upon the length.On a restore, the full and all incrementals
592 since it will beapplied in sequence to restore the file.
593 - Check new HAVE_WIN32 open bits.
594 - Check if the tape has moved before writing.
595 - Handling removable disks -- see below:
596 - Keep track of tape use time, and report when cleaning is necessary.
597 - Add FromClient and ToClient keywords on restore command (or
598 BackupClient RestoreClient).
599 - Implement a JobSet, which groups any number of jobs. If the
600 JobSet is started, all the jobs are started together.
601 Allow Pool, Level, and Schedule overrides.
602 - Enhance cancel to timeout BSOCK packets after a specific delay.
603 - Do scheduling by UTC using gmtime_r() in run_conf, scheduler, and
604 ua_status.!!! Thanks to Alan Brown for this tip.
605 - Look at updating Volume Jobs so that Max Volume Jobs = 1 will work
606 correctly for multiple simultaneous jobs.
607 - Correct code so that FileSet MD5 is calculated for < and | filename
609 - Implement the Media record flag that indicates that the Volume does disk
611 - Implement VolAddr, which is used when Volume is addressed like a disk,
612 and form it from VolFile and VolBlock.
613 - Make multiple restore jobs for multiple media types specifying
614 the proper storage type.
615 - Fix fast block rejection (stored/read_record.c:118). It passes a null
616 pointer (rec) to try_repositioning().
617 - Look at extracting Win data from BackupRead.
618 - Implement RestoreJobRetention? Maybe better "JobRetention" in a Job,
619 which would take precidence over the Catalog "JobRetention".
620 - Implement Label Format in Add and Label console commands.
621 - Possibly up network buffers to 65K. Put on variable.
622 - Put email tape request delays on one or more variables. User wants
623 to cancel the job after a certain time interval. Maximum Mount Wait?
624 - Job, Client, Device, Pool, or Volume?
625 Is it possible to make this a directive which is *optional* in multiple
626 resources, like Level? If so, I think I'd make it an optional directive
627 in Job, Client, and Pool, with precedence such that Job overrides Client
628 which in turn overrides Pool.
630 - New Storage specifications:
631 - Want to write to multiple storage devices simultaneously
632 - Want to write to multiple storage devices sequentially (in one job)
633 - Want to read/write simultaneously
634 - Key is MediaType -- it must match
636 Passed to SD as a sort of BSR record called Storage Specification
640 MediaType -> Next MediaType
642 Device -> Next Device
644 Allow multiple Storage specifications
652 Allow Multiple Pool specifications (note, Pool currently
654 Allow Multiple MediaType specifications in Dir conf
655 Allow Multiple Device specifications in Dir conf
656 Perhaps keep this in a single SSR
657 Tie a Volume to a specific device by using a MediaType that
658 is contained in only one device.
659 In SD allow Device to have Multiple MediaTypes
661 - Ideas from Jerry Scharf:
662 First let's point out some big pluses that bacula has for this
664 more importantly it's active. Thank you so much for that
665 even more important, it's not flaky
666 it has an open access catalog, opening many possibilities
667 it's pushing toward heterogeneous systems capability
669 Macintosh file client
670 macs are an interesting niche, but I fear a server is a rathole
671 working bare iron recovery for windows
672 the option for inc/diff backups not reset on fileset revision
673 a) use both change and inode update time against base time
674 b) do the full catalog check (expensive but accurate)
675 sizing guide (how much system is needed to back up N systems/files)
676 consultants on using bacula in building a disaster recovery system
678 or how to get at fancy things that one could do with bacula
679 logwatch code for bacula logs (or similar)
680 linux distro inclusion of bacula (brings good and bad, but necessary)
681 win2k/XP server capability (icky but you asked)
682 support for Oracle database ??
684 - Look at adding SQL server and Exchange support for Windows.
685 - Make dev->file and dev->block_num signed integers so that -1 can
686 be an invalid value which happens with BSR.
687 - Create VolAddr for disk files in place of VolFile and VolBlock. This
688 is needed to properly specify ranges.
689 - Add progress of files/bytes to SD and FD.
690 - Print warning message if FileId > 4 billion
691 - do a "messages" before the first prompt in Console
692 - Client does not show busy during Estimate command.
693 - Implement Console mtx commands.
694 - Implement a Mount Command and an Unmount Command where
695 the users could specify a system command to be performed
696 to do the mount, after which Bacula could attempt to
697 read the device. This is for Removeable media such as a CDROM.
698 - Most likely, this mount command would be invoked explicitly
699 by the user using the current Console "mount" and "unmount"
700 commands -- the Storage Daemon would do the right thing
701 depending on the exact nature of the device.
702 - As with tape drives, when Bacula wanted a new removable
703 disk mounted, it would unmount the old one, and send a message
704 to the user, who would then use "mount" as described above
705 once he had actually inserted the disk.
706 - Implement dump/print label to UA
707 - Spool to disk only when the tape is full, then when a tape is hung move
709 - bextract is sending everything to the log file ****FIXME****
710 - Allow multiple Storage specifications (or multiple names on
711 a single Storage specification) in the Job record. Thus a job
712 can be backed up to a number of storage devices.
713 - Implement some way for the File daemon to contact the Director
714 to start a job or pass its DHCP obtained IP number.
715 - Implement a query tape prompt/replace feature for a console
716 - Copy console @ code to gnome2-console
717 - Make AES the only encryption algorithm see
718 http://csrc.nist.gov/CryptoToolkit/aes/). It's
719 an officially adopted standard, has survived peer
720 review, and provides keys up to 256 bits.
721 - Take a careful look at SetACL http://setacl.sourceforge.net
722 - Make tree walk routines like cd, ls, ... more user friendly
723 by handling spaces better.
724 - Make sure that Bacula rechecks the tape after the 20 min wait.
725 - Set IO_NOWAIT on Bacula TCP/IP packets.
726 - Try doing a raw partition backup and restore by mounting a
729 Yes, it would allow to highly automatic the request for new tapes. If a
730 tape is empty, bacula reads the barcodes (native or simulated), and if
731 an unused tape is found, it runs the label command with all the
732 necessary parameters.
734 By the way can bacula automatically "move" an empty/purged volume say
735 in the "short" pool to the "long" pool if this pool runs out of volume
737 - What to do about "list files job=xxx".
738 - Get and test MySQL 4.0
739 - Look at how fuser works and /proc/PID/fd that is how Nic found the
740 file descriptor leak in Bacula.
741 - Implement WrapCounters in Counters.
742 - Add heartbeat from FD to SD if hb interval expires.
743 - Can we dynamically change FileSets?
744 - If pool specified to label command and Label Format is specified,
745 automatically generate the Volume name.
746 - Why can't SQL do the filename sort for restore?
747 - Add ExhautiveRestoreSearch
748 - Look at the possibility of loading only the necessary
749 data into the restore tree (i.e. do it one directory at a
750 time as the user walks through the tree).
751 - Possibly use the hash code if the user selects all for a restore command.
752 - Fix "restore all" to bypass building the tree.
753 - Prohibit backing up archive device (findlib/find_one.c:128)
754 - Implement Release Device in the Job resource to unmount a drive.
755 - Implement Acquire Device in the Job resource to mount a drive,
756 be sure this works with admin jobs so that the user can get
757 prompted to insert the correct tape. Possibly some way to say to
758 run the job but don't save the files.
759 - Make things like list where a file is saved case independent for
762 - Use autochanger to handle multiple devices.
763 - On Windows with very long path names, it may be impossible to create
764 a file (and thus restore it) because the total length is too long.
765 We must cd into the directory then create the file without the
767 - Implement a Recycle command
768 - Test a second language e.g. french.
769 - Start working on Base jobs.
770 - Implement UnsavedFiles DB record.
771 - From Phil Stracchino:
772 It would probably be a per-client option, and would be called
773 something like, say, "Automatically purge obsoleted jobs". What it
774 would do is, when you successfully complete a Differential backup of a
775 client, it would automatically purge all Incremental backups for that
776 client that are rendered redundant by that Differential. Likewise,
777 when a Full backup on a client completed, it would automatically purge
778 all Differential and Incremental jobs obsoleted by that Full backup.
779 This would let people minimize the number of tapes they're keeping on
780 hand without having to master the art of retention times.
781 - When doing a Backup send all attributes back to the Director, who
782 would then figure out what files have been deleted.
783 - Currently in mount.c:236 the SD simply creates a Volume. It should have
784 explicit permission to do so. It should also mark the tape in error
785 if there is an error.
786 - Cancel waiting for Client connect in SD if FD goes away.
788 - Implement timeout in response() when it should come quickly.
789 - Implement a Slot priority (loaded/not loaded).
790 - Implement "vacation" Incremental only saves.
791 - Implement create "FileSet"?
792 - Add prefixlinks to where or not where absolute links to FD.
793 - Issue message to mount a new tape before the rewind.
794 - Simplified client job initiation for portables.
795 - If SD cannot open a drive, make it periodically retry.
796 - Add more of the config info to the tape label.
798 - If tape is marked read-only, then try opening it read-only rather than
799 failing, and remember that it cannot be written.
800 - Refine SD waiting output:
801 Device is being positioned
802 > Device is being positioned for append
803 > Device is being positioned to file x
805 - Figure out some way to estimate output size and to avoid splitting
806 a backup across two Volumes -- this could be useful for writing CDROMs
807 where you really prefer not to have it split -- not serious.
808 - Have SD compute MD5 or SHA1 and compare to what FD computes.
809 - Make VolumeToCatalog calculate an MD5 or SHA1 from the
810 actual data on the Volume and compare it.
811 - Implement Bacula plugins -- design API
812 - Make bcopy read through bad tape records.
813 - Program files (i.e. execute a program to read/write files).
814 Pass read date of last backup, size of file last time.
815 - Add Signature type to File DB record.
816 - CD into subdirectory when open()ing files for backup to
817 speed up things. Test with testfind().
818 - Priority job to go to top of list.
819 - Why are save/restore of device different sizes (sparse?) Yup! Fix it.
820 - Implement some way for the Console to dynamically create a job.
821 - Solaris -I on tar for include list
822 - Need a verbose mode in restore, perhaps to bsr.
823 - bscan without -v is too quiet -- perhaps show jobs.
824 - Add code to reject whole blocks if not wanted on restore.
825 - Check if we can increase Bacula FD priorty in Win2000
826 - Make sure the MaxVolFiles is fully implemented in SD
827 - Check if both CatalogFiles and UseCatalog are set to SD.
828 - Possibly add email to Watchdog if drive is unmounted too
829 long and a job is waiting on the drive.
830 - After unmount, if restore job started, ask to mount.
831 - Add UA rc and history files.
832 - put termcap (used by console) in ./configure and
833 allow -with-termcap-dir.
834 - Fix Autoprune for Volumes to respect need for full save.
835 - Compare tape to Client files (attributes, or attributes and data)
836 - Make all database Ids 64 bit.
837 - Allow console commands to detach or run in background.
838 - Fix status delay on storage daemon during rewind.
839 - Add SD message variables to control operator wait time
840 - Maximum Operator Wait
841 - Minimum Message Interval
842 - Maximum Message Interval
843 - Send Operator message when cannot read tape label.
844 - Verify level=Volume (scan only), level=Data (compare of data to file).
845 Verify level=Catalog, level=InitCatalog
847 - Add keyword search to show command in Console.
848 - Events : tape has more than xxx bytes.
849 - Complete code in Bacula Resources -- this will permit
850 reading a new config file at any time.
851 - Handle ctl-c in Console
852 - Implement script driven addition of File daemon to config files.
853 - Think about how to make Bacula work better with File (non-tape) archives.
854 - Write Unix emulator for Windows.
855 - Put memory utilization in Status output of each daemon
856 if full status requested or if some level of debug on.
857 - Make database type selectable by .conf files i.e. at runtime
858 - Set flag for uname -a. Add to Volume label.
859 - Restore files modified after date
860 - SET LD_RUN_PATH=$HOME/mysql/lib/mysql
861 - Remove duplicate fields from jcr (e.g. jcr.level and jcr.jr.Level, ...).
862 - Timout a job or terminate if link goes down, or reopen link and query.
863 - Concept of precious tapes (cannot be reused).
864 - Make bcopy copy with a single tape drive.
865 - Permit changing ownership during restore.
868 > My suggestion: Add a feature on the systray menu-icon menu to request
869 > an immediate backup now. This would be useful for laptop users who may
870 > not be on the network when the regular scheduled backup is run.
872 > My wife's suggestion: Add a setting to the win32 client to allow it to
873 > shut down the machine after backup is complete (after, of course,
874 > displaying a "System will shut down in one minute, click here to cancel"
875 > warning dialog). This would be useful for sites that want user
876 > woorkstations to be shut down overnight to save power.
879 - Autolabel should be specified by DIR instead of SD.
882 - AutoScan (check checksum of tape)
883 - Format command = "format /dev/nst0"
887 - Seek resolution (usually corresponds to buffer size)
888 - EODErrorCode=ENOSPC or code
889 - Partial Read error code
890 - Partial write error code
891 - Nonformatted read error
892 - Nonformatted write error
893 - WriteProtected error
897 - IgnoreCloseErrors=yes
907 - FD sends unsaved file list to Director at end of job (see
909 - File daemon should build list of files skipped, and then
910 at end of save retry and report any errors.
911 - Write a Storage daemon that uses pipes and
912 standard Unix programs to write to the tape.
914 - Need something that monitors the JCR queue and
915 times out jobs by asking the deamons where they are.
916 - Enhance Jmsg code to permit buffering and saving to disk.
917 - device driver = "xxxx" for drives.
919 - Ensure that /dev/null works
920 - Need report class for messages. Perhaps
921 report resource where report=group of messages
922 - enhance scan_attrib and rename scan_jobtype, and
923 fill in code for "since" option
924 - Director needs a time after which the report status is sent
925 anyway -- or better yet, a retry time for the job.
926 - Don't reschedule a job if previous incarnation is still running.
927 - Some way to automatically backup everything is needed????
928 - Need a structure for pending actions:
930 - termination status (part of buffered msgs?)
932 Read, Write, Clean, Delete
933 - Login to Bacula; Bacula users with different permissions:
934 owner, group, user, quotas
935 - Store info on each file system type (probably in the job header on tape.
936 This could be the output of df; or perhaps some sort of /etc/mtab record.
938 ========= ideas ===============
939 From: "Jerry K. Schieffer" <jerry@skylinetechnology.com>
940 To: <kern@sibbald.com>
941 Subject: RE: [Bacula-users] future large programming jobs
942 Date: Thu, 26 Feb 2004 11:34:54 -0600
944 I noticed the subject thread and thought I would offer the following
945 merely as sources of ideas, i.e. something to think about, not even as
946 strong as a request. In my former life (before retiring) I often
947 dealt with backups and storage management issues/products as a
948 developer and as a consultant. I am currently migrating my personal
949 network from amanda to bacula specifically because of the ability to
950 cross media boundaries during storing backups.
951 Are you familiar with the commercial product called ADSM (I think IBM
952 now sells it under the Tivoli label)? It has a couple of interesting
953 ideas that may apply to the following topics.
955 1. Migration: Consider that when you need to restore a system, there
956 may be pressure to hurry. If all the information for a single client
957 can eventually end up on the same media (and in chronological order),
958 the restore is facillitated by not having to search past information
959 from other clients. ADSM has the concept of "client affinity" that
960 may be associated with it's storage pools. It seems to me that this
961 concept (as an optional feature) might fit in your architecture for
964 ADSM also has the concept of defining one or more storage pools as
965 "copy pools" (almost mirrors, but only in the sense of contents).
966 These pools provide the ability to have duplicte data stored both
967 onsite and offsite. The copy process can be scheduled to be handled
968 by their storage manager during periods when there is no backup
969 activity. Again, the migration process might be a place to consider
970 implementing something like this.
973 > It strikes me that it would be very nice to be able to do things
975 > have the Job(s) backing up the machines run, and once they have all
976 > completed, start a migration job to copy the data from disks Volumes
978 > a tape library and then to offsite storage. Maybe this can already
980 > done with some careful scheduling and Job prioritzation; the events
981 > mechanism described below would probably make it very easy.
983 This is the goal. In the first step (before events), you simply
985 the Migration to tape later.
987 2. Base jobs: In ADSM, each copy of each stored file is tracked in
988 the database. Once a file (unique by path and metadata such as dates,
989 size, ownership, etc.) is in a copy pool, no more copies are made. In
990 other words, when you start ADSM, it begins like your concept of a
991 base job. After that it is in the "incremental" mode. You can
992 configure the number of "generations" of files to be retained, plus a
993 retention date after which even old generations are purged. The
994 database tracks the contents of media and projects the percentage of
995 each volume that is valid. When the valid content of a volume drops
996 below a configured percentage, the valid data are migrated to another
997 volume and the old volume is marked as empty. Note, this requires
998 ADSM to have an idea of the contents of a client, i.e. marking the
999 database when an existing file was deleted, but this would solve your
1000 issue of restoring a client without restoring deleted files.
1002 This is pretty far from what bacula now does, but if you are going to
1003 rip things up for Base jobs,.....
1004 Also, the benefits of this are huge for very large shops, especially
1005 with media robots, but are a pain for shops with manual media
1009 > Base jobs sound pretty useful, but I'm not dying for them.
1011 Nobody is dying for them, but when you see what it does, you will die
1014 3. Restoring deleted files: Since I think my comments in (2) above
1015 have low probability of implementation, I'll also suggest that you
1016 could approach the issue of deleted files by a mechanism of having the
1017 fd report to the dir, a list of all files on the client for every
1018 backup job. The dir could note in the database entry for each file
1019 the date that the file was seen. Then if a restore as of date X takes
1020 place, only files that exist from before X until after X would be
1021 restored. Probably the major cost here is the extra date container in
1022 each row of the files table.
1024 Thanks for "listening". I hope some of this helps. If you want to
1025 contact me, please send me an email - I read some but not all of the
1026 mailing list traffic and might miss a reply there.
1028 Please accept my compliments for bacula. It is doing a great job for
1029 me!! I sympathize with you in the need to wrestle with excelence in
1030 execution vs. excelence in feature inclusion.
1035 ==============================
1038 - Design at hierarchial storage for Bacula. Migration and Clone.
1039 - Implement FSM (File System Modules).
1040 - Audit M_ error codes to ensure they are correct and consistent.
1041 - Add variable break characters to lex analyzer.
1042 Either a bit mask or a string of chars so that
1043 the caller can change the break characters.
1044 - Make a single T_BREAK to replace T_COMMA, etc.
1045 - Ensure that File daemon and Storage daemon can
1046 continue a save if the Director goes down (this
1047 is NOT currently the case). Must detect socket error,
1048 buffer messages for later.
1049 - Enhance time/duration input to allow multiple qualifiers e.g. 3d2h
1050 - Add ability to backup to two Storage devices (two SD sessions) at
1051 the same time -- e.g. onsite, offsite.
1052 - Add the ability to consolidate old backup sets (basically do a restore
1053 to tape and appropriately update the catalog). Compress Volume sets.
1054 Might need to spool via file is only one drive is available.
1055 - Compress or consolidate Volumes of old possibly deleted files. Perhaps
1056 someway to do so with every volume that has less than x% valid
1060 Migration: Move a backup from one Volume to another
1061 Clone: Copy a backup -- two Volumes
1063 Bacula Migration is based on Jobs (apparently Networker is file by file).
1065 Migration triggered by:
1069 Highwater mark (keep total size)
1074 ======================================================
1076 It is somewhat like a Full save becomes an incremental since
1077 the Base job (or jobs) plus other non-base files.
1079 - A Base backup is same as Full backup, just different type.
1080 - New BaseFiles table that contains:
1082 BaseJobId - Base JobId referenced for this FileId (needed ???)
1083 JobId - JobId currently running
1084 FileId - File not backed up, exists in Base Job
1085 FileIndex - FileIndex from Base Job.
1086 i.e. for each base file that exists but is not saved because
1087 it has not changed, the File daemon sends the JobId, BaseId,
1088 FileId, FileIndex back to the Director who creates the DB entry.
1089 - To initiate a Base save, the Director sends the FD
1090 the FileId, and full filename for each file in the Base.
1091 - When the FD finds a Base file, he requests the Director to
1092 send him the full File entry (stat packet plus MD5), or
1093 conversely, the FD sends it to the Director and the Director
1094 says yes or no. This can be quite rapid if the FileId is kept
1095 by the FD for each Base Filename.
1096 - It is probably better to have the comparison done by the FD
1097 despite the fact that the File entry must be sent across the
1099 - An alternative would be to send the FD the whole File entry
1100 from the start. The disadvantage is that it requires a lot of
1101 space. The advantage is that it requires less communications
1103 - The Job record must be updated to indicate that one or more
1105 - At end of Job, FD returns:
1106 1. Count of base files/bytes not written to tape (i.e. matches)
1107 2. Count of base file that were saved i.e. had changed.
1108 - No tape record would be written for a Base file that matches, in the
1109 same way that no tape record is written for Incremental jobs where
1110 the file is not saved because it is unchanged.
1111 - On a restore, all the Base file records must explicitly be
1112 found from the BaseFile tape. I.e. for each Full save that is marked
1113 to have one or more Base Jobs, search the BaseFile for all occurrences
1115 - An optimization might be to make the BaseFile have:
1121 This would avoid the need to explicitly fetch each File record for
1122 the Base job. The Base Job record will be fetched to get the
1123 VolSessionId and VolSessionTime.
1124 =========================================================
1127 ==========================================================
1129 For each Incremental job that is run, there may be files that
1130 were found but not saved because they were locked (this applies
1131 only to Windows). Such a system could send back to the Director
1132 a list of Unsaved files.
1134 - New UnSavedFiles table that contains:
1138 - Then in the next Incremental job, the list of Unsaved Files will be
1139 feed to the FD, who will ensure that they are explicitly chosen even
1140 if standard date/time check would not have selected them.
1141 =============================================================
1145 Multiple drive autochanger data: see Alan Brown
1146 mtx -f xxx unloadStorage Element 1 is Already Full(drive 0 was empty)
1147 Unloading Data Transfer Element into Storage Element 1...source Element
1148 Address 480 is Empty
1150 (drive 0 was empty and so was slot 1)
1151 > mtx -f xxx load 15 0
1152 no response, just returns to the command prompt when complete.
1153 > mtx -f xxx status Storage Changer /dev/changer:2 Drives, 60 Slots ( 2 Import/Export )
1154 Data Transfer Element 0:Full (Storage Element 15 Loaded):VolumeTag = HX001
1155 Data Transfer Element 1:Empty
1156 Storage Element 1:Empty
1157 Storage Element 2:Full :VolumeTag=HX002
1158 Storage Element 3:Full :VolumeTag=HX003
1159 Storage Element 4:Full :VolumeTag=HX004
1160 Storage Element 5:Full :VolumeTag=HX005
1161 Storage Element 6:Full :VolumeTag=HX006
1162 Storage Element 7:Full :VolumeTag=HX007
1163 Storage Element 8:Full :VolumeTag=HX008
1164 Storage Element 9:Full :VolumeTag=HX009
1165 Storage Element 10:Full :VolumeTag=HX010
1166 Storage Element 11:Empty
1167 Storage Element 12:Empty
1168 Storage Element 13:Empty
1169 Storage Element 14:Empty
1170 Storage Element 15:Empty
1171 Storage Element 16:Empty....
1172 Storage Element 28:Empty
1173 Storage Element 29:Full :VolumeTag=CLNU01L1
1174 Storage Element 30:Empty....
1175 Storage Element 57:Empty
1176 Storage Element 58:Full :VolumeTag=NEX261L2
1177 Storage Element 59 IMPORT/EXPORT:Empty
1178 Storage Element 60 IMPORT/EXPORT:Empty
1180 Unloading Data Transfer Element into Storage Element 15...done
1182 (just to verify it remembers where it came from, however it can be
1183 overrriden with mtx unload {slotnumber} to go to any storage slot.)
1185 There needs to be a table of drive # to devices somewhere - If there are
1186 multiple changers or drives there may not be a 1:1 correspondance between
1187 changer drive number and system device name - and depending on the way the
1188 drives are hooked up to scsi busses, they may not be linearly numbered
1189 from an offset point either.something like
1191 Autochanger drives = 2
1192 Autochanger drive 0 = /dev/nst1
1193 Autochanger drive 1 = /dev/nst2
1194 IMHO, it would be _safest_ to use explicit mtx unload commands at all
1195 times, not just for multidrive changers. For a 1 drive changer, that's
1201 MTX's manpage (1.2.15):
1202 unload [<slotnum>] [ <drivenum> ]
1203 Unloads media from drive <drivenum> into slot
1204 <slotnum>. If <drivenum> is omitted, defaults to
1205 drive 0 (as do all commands). If <slotnum> is
1206 omitted, defaults to the slot that the drive was
1207 loaded from. Note that there's currently no way
1208 to say 'unload drive 1's media to the slot it
1209 came from', other than to explicitly use that
1210 slot number as the destination.AB
1216 undef# camcontrol devlist
1217 <WANGTEK 51000 SCSI M74H 12B3> at scbus0 target 2 lun 0 (pass0,sa0)
1218 <ARCHIVE 4586XX 28887-XXX 4BGD> at scbus0 target 4 lun 0 (pass1,sa1)
1219 <ARCHIVE 4586XX 28887-XXX 4BGD> at scbus0 target 4 lun 1 (pass2)
1221 tapeinfo -f /dev/sg0 with a bad tape in drive 1:
1222 [kern@rufus mtx-1.2.17kes]$ ./tapeinfo -f /dev/sg0
1223 Product Type: Tape Drive
1225 Product ID: 'C5713A '
1227 Attached Changer: No
1228 TapeAlert[3]: Hard Error: Uncorrectable read/write error.
1229 TapeAlert[20]: Clean Now: The tape drive neads cleaning NOW.
1236 Medium Type: Not Loaded
1239 DataCompEnabled: yes
1240 DataCompCapable: yes
1241 DataDeCompEnabled: yes
1248 Handling removable disks
1250 From: Karl Cunningham <karlc@keckec.com>
1252 My backups are only to hard disk these days, in removable bays. This is my
1253 idea of how a backup to hard disk would work more smoothly. Some of these
1254 things Bacula does already, but I mention them for completeness. If others
1255 have better ways to do this, I'd like to hear about it.
1257 1. Accommodate several disks, rotated similar to how tapes are. Identified
1258 by partition volume ID or perhaps by the name of a subdirectory.
1259 2. Abort & notify the admin if the wrong disk is in the bay.
1260 3. Write backups to different subdirectories for each machine to be backed
1262 4. Volumes (files) get created as needed in the proper subdirectory, one
1264 5. When a disk is recycled, remove or zero all old backup files. This is
1265 important as the disk being recycled may be close to full. This may be
1266 better done manually since the backup files for many machines may be
1267 scattered in many subdirectories.
1272 - Make sure that all do_prompt() calls in Dir check for
1273 -1 (error) and -2 (cancel) returns.