4 Documentation to do: (any release a little bit at a time)
5 - Document running a test version.
6 - Document query file format.
7 - Document static linking
8 - Document problems with Verify and pruning.
9 - Document how to use multiple databases.
10 - For FreeBSD typical /dev/nrsa0 and for mtx /dev/pass1
11 - VXA drives have a "cleaning required"
12 indicator, but Exabyte recommends preventive cleaning after every 75
14 - Lookup HP cleaning recommendations.
15 - Lookup HP tape replacement recommendations (see trouble shooting autochanger)
16 - Document FInclude ...
17 - Document all the status codes JobLevel, JobType, JobStatus.
18 - Document SDConnectTimeout (in FD).
20 Testing to do: (painful)
21 - that ALL console command line options work and are always implemented
22 - blocksize recognition code.
23 - Test if rewind at end of tape waits for tape to rewind.
25 - Test not zeroing Autochanger slot when it is wrong.
26 - Test recycling and purging (code changed in db_find_next_volume and
28 - Figure out how to use ssh or stunnel to protect Bacula communications.
31 - Enhance autochanger interface to include a "scan" feature
32 scan 1; scan 1-5; scan 1,2,4 ... to update the catalog
33 - Allow a slot or range of slots on the label barcodes command.
34 when the magazine is changed.
35 - Specify list of files to restore
36 - Implement ClientRunBeforeJob and ClientRunAfterJob.
37 - Figure out what is interrupting sql command in console.
38 - Don't print "Warning: Wrong Volume mounted ..." if mounting second
40 - Implement List Volume Job=xxx or List scheduled volumes or Status Director
41 - Make | and < work on FD side.
44 - Why can't SQL do the filename sort for restore?
45 - Is a pool specification really needed for a restore? Yes, and
46 you may want to exclude archive Pools.
47 - Look at libkse (man kse) for FreeBSD threading.
48 - Look into Microsoft Volume Shadowcopy Service VSS for backing
49 up system state components (Active Directory, System Volume, ...)
50 - Add ExhautiveRestoreSearch
51 - Look at the possibility of loading only the necessary
52 data into the restore tree (i.e. do it one directory at a
53 time as the user walks through the tree).
54 - Possibly use the hash code if the user selects all for a restore command.
55 - Orphaned Dir buffer at parse_conf.c:373 => store_dir
56 - Implement some way for the File daemon to contact the Director
57 to start a job or pass its DHCP obtained IP number.
58 - Implement multiple Consoles.
59 - Add Console usr permissions.
60 - Fix "restore all" to bypass building the tree.
61 - Fix restore to list errors if Invalid block found, and if # files
62 restored does not match # expected.
63 - Prohibit backing up archive device (findlib/find_one.c:128)
64 - Implement Release Device in the Job resource to unmount a drive.
65 - Implement Acquire Device in the Job resource to mount a drive,
66 be sure this works with admin jobs so that the user can get
67 prompted to insert the correct tape. Possibly some way to say to
68 run the job but don't save the files.
69 - Add JobName= to VerifyToCatalog so that all verifies can be done at the end.
70 - Implement FileOptions (see end of this document)
71 - Make things like list where a file is saved case independent for
73 - Edit the Client/Storage name into authentication failure messages.
74 - Implement job in VerifyToCatalog
76 - Implement a PostgreSQL driver.
77 - Bacula needs to propagate SD errors.
78 > > cluster-dir: Start Backup JobId 252, Job=REUTERS.2003-08-11_15.04.12
79 > > prod4-sd: REUTERS.2003-08-11_15.04.12 Error: Write error on device
80 /dev/nst0. ERR=Input/output error.
81 > > prod4-sd: REUTERS.2003-08-11_15.04.12 Error: Re-read of last block failed.
82 Last block=5162 Current block=5164.
83 > > prod4-sd: End of medium on Volume "REU007" Bytes=16,303,521,933
85 - Use autochanger to handle multiple devices.
86 - Fix packet too big problem.
87 - Add SuSE install doc to list.
88 - Check and rechedk "Invalid block number"
89 - Make bextract release the drive properly between tapes
90 so that an autochanger can be made to work.
91 - User wants to NOT backup up certain big files (email files).
92 - Maybe remove multiple simultaneous devices code in SD.
93 - On Windows with very long path names, it may be impossible to create
94 a file (and thus restore it) because the total length is too long.
95 We must cd into the directory then create the file without the
97 - lstat() is not going to work on Win32 for testing date.
98 - Something is not right in last block of fill command.
99 - Implement a Recycle command
100 - Add FileSet to command line arguments for restore.
101 - Allow multiple Storage specifications (or multiple names on
102 a single Storage specification) in the Job record. Thus a job
103 can be backed up to a number of storage devices.
104 - Add client name to cram-md5 challenge so Director can immediately
105 verify if it is the correct client.
106 - Implement ClientRunBeforeJob and ClientRunAfterJob.
107 - Add JobLevel in FD status (but make sure it is defined).
108 - Audit all UA commands to ensure that we always prompt where possible.
109 - Restrict characters permitted in a Resource name, and don't permit
111 - Check Jmsg in bnet, may not work, must dup bsock.
112 - Suppress Job Name in Jmsg for console
113 - Create Pools that are referenced in a Run statement at startup if possible.
114 - Use runbeforejob to unload, then reload a volume previously used,
115 then the next job run gets an error reading the drive.
116 - Make bootstrap filename unique.
117 - Test a second language e.g. french.
118 - Start working on Base jobs.
119 - Make "make binary-release" work from any directory.
120 - Implement UnsavedFiles DB record.
121 - Implement argc/argv for daemon command line scanning using table driven
123 - Implement table driven single argc/argv scanner to pickup all arguments.
124 Much like xxx_conf.c scan table.
125 keyword, handler(store_routine), store_address, code, flags, default.
126 - From Phil Stracchino:
127 It would probably be a per-client option, and would be called
128 something like, say, "Automatically purge obsoleted jobs". What it
129 would do is, when you successfully complete a Differential backup of a
130 client, it would automatically purge all Incremental backups for that
131 client that are rendered redundant by that Differential. Likewise,
132 when a Full backup on a client completed, it would automatically purge
133 all Differential and Incremental jobs obsoleted by that Full backup.
134 This would let people minimize the number of tapes they're keeping on
135 hand without having to master the art of retention times.
136 - Implement new serialize subroutines
137 send(socket, "string", &Vol, "uint32", &i, NULL)
138 - Scratch Pool where the volumes can be re-assigned to any Pool.
139 - Implement a M_SECURITY message class.
140 - Implement forward spacing block/file: position_device(bsr) --
141 just before read_block_from_device();
142 - When doing a Backup send all attributes back to the Director, who
143 would then figure out what files have been deleted.
144 - Currently in mount.c:236 the SD simply creates a Volume. It should have
145 explicit permission to do so. It should also mark the tape in error
146 if there is an error.
147 - Make sure all restore counters are working correctly in the FD.
148 - SD Bytes Read is wrong.
149 - Look at ALL higher level routines that call block.c to be sure
150 they don't expect something in errmsg.
151 - Investigate doing RAW backup of Win32 partition.
152 - Add thread specific data to hold the jcr -- send error messages from
153 low level routines by accessing it and using Jmsg().
154 - Cancel waiting for Client connect in SD if FD goes away.
156 - Add Progress command that periodically reports the progress of
158 - One block was orphaned in the SD probably after cancel.
161 - Examine Bare Metal restore problem (a FD crash exists somewhere ...).
162 - Implement timeout in response() when it should come quickly.
163 - Implement console @echo command.
164 - Implement a Slot priority (loaded/not loaded).
165 - Implement "vacation" Incremental only saves.
166 - Implement single pane restore (much like the Gftp panes).
167 - Implement Automatic Mount even in operator wait.
168 - Implement create "FileSet"?
169 - Fix watchdog pthread crash on Win32 (this is pthread_kill() Cygwin bug)
170 - Implement "scratch pool" where tapes are defined and can be
171 taken by any pool that needs them.
172 - Implement restore "current system", but take all files without
173 doing selection tree -- so that jobs without File records can
175 - Implement disk spooling. Two parts: 1. Spool to disk then
176 immediately to tape to speed up tape operations. 2. Spool to
177 disk only when the tape is full, then when a tape is hung move
179 - Implement a relocatable bacula.spec
180 - Implement dump/print label to UA
181 - Add prefixlinks to where or not where absolute links to FD.
182 - Issue message to mount a new tape before the rewind.
183 - Simplified client job initiation for portables.
184 - If SD cannot open a drive, make it periodically retry.
185 - Implement LabelTemplate (at least first cut).
186 - Add more of the config info to the tape label.
187 - Implement a Mount Command and an Unmount Command where
188 the users could specify a system command to be performed
189 to do the mount, after which Bacula could attempt to
190 read the device. This is for Removeable media such as a CDROM.
191 - Most likely, this mount command would be invoked explicitly
192 by the user using the current Console "mount" and "unmount"
193 commands -- the Storage Daemon would do the right thing
194 depending on the exact nature of the device.
195 - As with tape drives, when Bacula wanted a new removable
196 disk mounted, it would unmount the old one, and send a message
197 to the user, who would then use "mount" as described above
198 once he had actually inserted the disk.
200 - If tape is marked read-only, then try opening it read-only rather than
201 failing, and remember that it cannot be written.
202 - Refine SD waiting output:
203 Device is being positioned
204 > Device is being positioned for append
205 > Device is being positioned to file x
207 - Figure out some way to estimate output size and to avoid splitting
208 a backup across two Volumes -- this could be useful for writing CDROMs
209 where you really prefer not to have it split -- not serious.
210 - Add RunBeforeJob and RunAfterJob to the Client program.
211 - Have SD compute MD5 or SHA1 and compare to what FD computes.
212 - Make VolumeToCatalog calculate an MD5 or SHA1 from the
213 actual data on the Volume and compare it.
214 - Implement Bacula plugins -- design API
215 - Make bcopy read through bad tape records.
216 - Program files (i.e. execute a program to read/write files).
217 Pass read date of last backup, size of file last time.
218 - Add Signature type to File DB record.
219 - CD into subdirectory when open()ing files for backup to
220 speed up things. Test with testfind().
221 - Priority job to go to top of list.
222 - Why are save/restore of device different sizes (sparse?) Yup! Fix it.
223 - Implement some way for the Console to dynamically create a job.
224 - Restore to a particular time -- e.g. before date, after date.
225 - Solaris -I on tar for include list
226 - Need a verbose mode in restore, perhaps to bsr.
227 - bscan without -v is too quiet -- perhaps show jobs.
228 - Add code to reject whole blocks if not wanted on restore.
229 - Check if we can increase Bacula FD priorty in Win2000
230 - Make sure the MaxVolFiles is fully implemented in SD
231 - Check if both CatalogFiles and UseCatalog are set to SD.
232 - Need return status on read_cb() from read_records(). Need multiple
233 records -- one per Job, maybe a JCR or some other structure with
234 a block and a record.
235 - Figure out how to do a bare metal Windows restore
236 - Possibly add email to Watchdog if drive is unmounted too
237 long and a job is waiting on the drive.
238 - Restore program that errs in SD due to no tape, reports
239 OK incorrectly in output.
240 - After unmount, if restore job started, ask to mount.
241 - Convert all %x substitution variables, which are hard to remember
242 and read to %(variable-name). Idea from TMDA.
243 - Remove NextId for SQLite. Optimize.
244 - Move all SQL statements into a single location.
245 - Add UA rc and history files.
246 - put termcap (used by console) in ./configure and
247 allow -with-termcap-dir.
248 - Enhance time and size scanning routines.
249 - Fix Autoprune for Volumes to respect need for full save.
250 - Fix Win32 config file definition name on /install
251 - Compare tape to Client files (attributes, or attributes and data)
252 - Make all database Ids 64 bit.
253 - Write an applet for Linux.
254 - Implement new inter-daemon communications protocol.
255 - Allow console commands to detach or run in background.
256 - Fix status delay on storage daemon during rewind.
257 - Add SD message variables to control operator wait time
258 - Maximum Operator Wait
259 - Minimum Message Interval
260 - Maximum Message Interval
261 - Send Operator message when cannot read tape label.
262 - Verify level=Volume (scan only), level=Data (compare of data to file).
263 Verify level=Catalog, level=InitCatalog
265 - Add keyword search to show command in Console.
266 - Events : tape has more than xxx bytes.
267 - Complete code in Bacula Resources -- this will permit
268 reading a new config file at any time.
269 - Handle ctl-c in Console
270 - Implement script driven addition of File daemon to config files.
271 - Think about how to make Bacula work better with File (non-tape) archives.
272 - Write Unix emulator for Windows.
273 - Put memory utilization in Status output of each daemon
274 if full status requested or if some level of debug on.
275 - Make database type selectable by .conf files i.e. at runtime
276 - Set flag for uname -a. Add to Volume label.
277 - Implement throttled work queue.
278 - Restore files modified after date
279 - SET LD_RUN_PATH=$HOME/mysql/lib/mysql
280 - Implement Restore FileSet=
281 - Create a protocol.h and protocol.c where all protocol messages
283 - Remove duplicate fields from jcr (e.g. jcr.level and jcr.jr.Level, ...).
284 - Timout a job or terminate if link goes down, or reopen link and query.
285 - Concept of precious tapes (cannot be reused).
286 - Make bcopy copy with a single tape drive.
287 - Permit changing ownership during restore.
290 > My suggestion: Add a feature on the systray menu-icon menu to request
291 > an immediate backup now. This would be useful for laptop users who may
292 > not be on the network when the regular scheduled backup is run.
294 > My wife's suggestion: Add a setting to the win32 client to allow it to
295 > shut down the machine after backup is complete (after, of course,
296 > displaying a "System will shut down in one minute, click here to cancel"
297 > warning dialog). This would be useful for sites that want user
298 > woorkstations to be shut down overnight to save power.
301 - From Terry Manderson <terry@apnic.net>
302 jobset { # new structure
303 name = "monthlyUnixBoxen"
306 jobs = "wakame;durian;soy;wasabi;miso" #new!
316 fileset = "genericUnixSet"
322 fileset = "genericUnixSet"
328 fileset = "UnixDevelBoxSet"
333 - Autolabel should be specified by DIR instead of SD.
336 - AutoScan (check checksum of tape)
337 - Format command = "format /dev/nst0"
341 - Seek resolution (usually corresponds to buffer size)
342 - EODErrorCode=ENOSPC or code
343 - Partial Read error code
344 - Partial write error code
345 - Nonformatted read error
346 - Nonformatted write error
347 - WriteProtected error
351 - IgnoreCloseErrors=yes
361 - FD sends unsaved file list to Director at end of job (see
363 - File daemon should build list of files skipped, and then
364 at end of save retry and report any errors.
365 - Write a Storage daemon that uses pipes and
366 standard Unix programs to write to the tape.
368 - Need something that monitors the JCR queue and
369 times out jobs by asking the deamons where they are.
370 - Enhance Jmsg code to permit buffering and saving to disk.
371 - device driver = "xxxx" for drives.
373 - Ensure that /dev/null works
374 - Need report class for messages. Perhaps
375 report resource where report=group of messages
376 - enhance scan_attrib and rename scan_jobtype, and
377 fill in code for "since" option
378 - Director needs a time after which the report status is sent
379 anyway -- or better yet, a retry time for the job.
380 - Don't reschedule a job if previous incarnation is still running.
381 - Some way to automatically backup everything is needed????
382 - Need a structure for pending actions:
384 - termination status (part of buffered msgs?)
386 Read, Write, Clean, Delete
387 - Login to Bacula; Bacula users with different permissions:
388 owner, group, user, quotas
389 - Store info on each file system type (probably in the job header on tape.
390 This could be the output of df; or perhaps some sort of /etc/mtab record.
393 - Design at hierarchial storage for Bacula. Migration and Clone.
394 - Implement FSM (File System Modules).
395 - Audit M_ error codes to ensure they are correct and consistent.
396 - Add variable break characters to lex analyzer.
397 Either a bit mask or a string of chars so that
398 the caller can change the break characters.
399 - Make a single T_BREAK to replace T_COMMA, etc.
400 - Ensure that File daemon and Storage daemon can
401 continue a save if the Director goes down (this
402 is NOT currently the case). Must detect socket error,
403 buffer messages for later.
404 - Enhance time/duration input to allow multiple qualifiers e.g. 3d2h
405 - Add ability to backup to two Storage devices (two SD sessions) at
406 the same time -- e.g. onsite, offsite.
407 - Add the ability to consolidate old backup sets (basically do a restore
408 to tape and appropriately update the catalog). Compress Volume sets.
409 Might need to spool via file is only one drive is available.
410 - Compress or consolidate Volumes of old possibly deleted files. Perhaps
411 someway to do so with every volume that has less than x% valid
415 Migration: Move a backup from one Volume to another
416 Clone: Copy a backup -- two Volumes
418 Bacula Migration is based on Jobs (apparently Networker is file by file).
420 Migration triggered by:
424 Highwater mark (keep total size)
428 Bacula Projects Roadmap
430 last update 8 May 2003
432 Item 1: Multiple simultaneous Jobs. (done)
433 Done -- Restore part needs better implementation to work correctly
434 Also, it needs considerable testing
436 What: Permit multiple simultaneous jobs in Bacula.
438 Why: An enterprise level solution needs to go fast without the
439 need for the system administrator to carefully tweak
440 timing. Based on the benchmarks, during a full
441 backup, NetWorker typically hit 10 times the bandwidth to
442 the tape compared to Bacula--largely. This is probably due to
443 running parallel jobs and multi-threaded filling of buffers
444 and writing them to tape. This should also make things work
445 better when you have a mix of fast and slow machines backing
448 Notes: Bacula was designed to run multiple simultaneous jobs. Thus
449 implementing this is a matter of some small cleanups and
453 Item 2: Make the Storage daemon use intermediate file storage to buffer data.
454 Deferred -- not necessary yet -- possibly implement with Migration.
456 What: If data is coming into the SD too fast, buffer it to
457 disk if the user has configured this option.
459 Why: This would be nice, especially if it more or less falls out
460 when implementing (1) above. If not, it probably should not
461 be given a high priority because fundamentally the backup time
462 is limited by the tape bandwidth. Even though you may finish a
463 client job quicker by spilling to disk, you still have to
464 eventually get it onto tape. If intermediate disk buffering
465 allows us to improve write bandwidth to tape, it may make
468 Notes: Whether or not this is implemented will depend upon performance
469 testing after item 1 is implemented.
472 Item 3: Write the bscan program -- also write a bcopy program.
475 What: Write a program that reads a Bacula tape and puts all the
476 appropriate data into the catalog. This allows recovery
477 from a tape that is no longer in the database, or it allows
478 re-creation of a database if lost.
480 Why: This is a fundamental robustness and disaster recovery tool
481 which will increase the comfort level of a sysadmin
482 considering adopting Bacula.
484 Notes: A skeleton of this program already exists, but much work
485 needs to be done. Implementing this will also make apparent
486 any deficiencies in the current Bacula tape format.
489 Item 4: Implement Base jobs.
491 What: A base job is sort of like a Full save except that you
492 will want the FileSet to contain only files that are unlikely
493 to change in the future (i.e. a snapshot of most of your
494 system after installing it). After the base job has been run,
495 when you are doing a Full save, you can specify to exclude
496 all files saved by the base job that have not been modified.
498 Why: This is something none of the competition does, as far as we know
499 (except BackupPC, which is a Perl program that saves to disk
500 only). It is big win for the user, it makes Bacula stand out
501 as offering a unique optimization that immediately saves time
504 Notes: Big savings in tape usage. Will require more resources because
505 the e. DIR must send FD a list of files/attribs, and the FD must
506 search the list and compare it for each file to be saved.
509 Item 5: Implement Label templates
512 What: This is a mechanism whereby Bacula can automatically create
513 a tape label for new tapes according to a detailed specification
514 provided by the user.
516 Why: It is a major convenience item for folks who use automated label
519 Notes: Bacula already has a working form of automatic tape label
520 creation, but it is very crude. The design for the complete
521 tape labeling project is already documented in the manual.
524 Item 6: Write a regression script.
525 Done -- Continue to expand its testing.
527 What: This is an automatic script that runs and tests as many features
528 of Bacula as possible. The output is compared to previous
529 versions of Bacula and any differences are reported.
531 Why: This is an enormous help in preventing introduction of new
532 errors in parts of the program that already work correctly.
534 Notes: This probably should be ranked higher, it's something the typical
535 user doesn't see. Depending on how it's implemented, it may
536 make sense to defer it until the archival tape format and
537 user interface mature.
540 Item 7: GUI for interactive restore
541 Item 8: GUI for interactive backup
543 What: The current interactive restore is implemented with a tty
544 interface. It would be much nicer to be able to "see" the
545 list of files backed up in typical GUI tree format.
546 The same mechanism could also be used for creating
547 ad-hoc backup FileSets (item 8).
549 Why: Ease of use -- especially for the end user.
551 Notes: Rather than implementing in Gtk, we probably should go directly
552 for a Browser implementation, even if doing so meant the
553 capability wouldn't be available until much later. Not only
554 is there the question of Windows sites, most
555 Solaris/HP/IRIX, etc, shops can't currently run Gtk programs
556 without installing lots of stuff admins are very wary about.
557 Real sysadmins will always use the command line anyway, and
558 the user who's doing an interactive restore or backup of his
559 own files will in most cases be on a Windows machine running
563 Item 9: Add SSL to daemon communications.
565 What: This provides for secure communications between the daemons.
567 Why: This would allow doing backup across the Internet without
568 privacy concerns (or with much less concern).
570 Notes: The vast majority of near term potential users will be backing up
571 a single site over a LAN and, correctly or not, they probably
572 won't be concerned with security, at least not enough to go to
573 the trouble to set up keys, etc. to screw things down. We suspect
574 that many users genuinely interested in multi-site backup
575 already run some form of VPN software in their internetwork
576 connections, and are willing to delegate security to that layer.
579 Item 10: Define definitive tape format.
582 What: Define that definitive tape format that will not change
583 for the next millennium.
585 Why: Stability, security.
587 Notes: See notes for item 11 below.
590 Item 11: New daemon communication protocol.
592 What: The current daemon to daemon protocol is basically an ASCII
593 printf() and sending the buffer. On the receiving end, the
594 buffer is sscanf()ed to unpack it. The new scheme would
595 be a binary format that allows quick packing and unpacking
596 of any data type with named fields.
598 Why: Using binary packing would be faster. Named fields will permit
599 error checking to ensure that what is sent is what the
600 receiver really wants.
602 Notes: These are internal improvements in the interest of the
603 long-term stability and evolution of the program. On the one
604 hand, the sooner they're done, the less code we have to rip
605 up when the time comes to install them. On the other hand, they
606 don't bring an immediately perceptible benefit to potential
607 users. Item 10 and possibly item 11 should be deferred until Bacula
608 is well established with a growing user community more or
609 less happy with the feature set. At that time, it will make a
610 good "next generation" upgrade in the interest of data
616 ======================================================
618 It is somewhat like a Full save becomes an incremental since
619 the Base job (or jobs) plus other non-base files.
621 - New BaseFile table that contains:
622 JobId, BaseJobId, FileId (from Base).
623 i.e. for each base file that exists but is not saved because
624 it has not changed, the File daemon sends the JobId, BaseId,
625 and FileId back to the Director who creates the DB entry.
626 - To initiate a Base save, the Director sends the FD
627 the FileId, and full filename for each file in the Base.
628 - When the FD finds a Base file, he requests the Director to
629 send him the full File entry (stat packet plus MD5), or
630 conversely, the FD sends it to the Director and the Director
631 says yes or no. This can be quite rapid if the FileId is kept
632 by the FD for each Base Filename.
633 - It is probably better to have the comparison done by the FD
634 despite the fact that the File entry must be sent across the
636 - An alternative would be to send the FD the whole File entry
637 from the start. The disadvantage is that it requires a lot of
638 space. The advantage is that it requires less communications
640 - The Job record must be updated to indicate that one or more
642 - At end of Job, FD returns:
643 1. Count of base files/bytes not written to tape (i.e. matches)
644 2. Count of base file that were saved i.e. had changed.
645 - No tape record would be written for a Base file that matches, in the
646 same way that no tape record is written for Incremental jobs where
647 the file is not saved because it is unchanged.
648 - On a restore, all the Base file records must explicitly be
649 found from the BaseFile tape. I.e. for each Full save that is marked
650 to have one or more Base Jobs, search the BaseFile for all occurrences
652 - An optimization might be to make the BaseFile have:
658 This would avoid the need to explicitly fetch each File record for
659 the Base job. The Base Job record will be fetched to get the
660 VolSessionId and VolSessionTime.
661 =========================================================
665 =============================================================
667 Request For Comments For File Backup Options
670 Subject: File Backup Options
673 A few days ago, a Bacula user who is backing up to file volumes and
674 using compression asked if it was possible to suppress compressing
675 all .gz files since it was a waste of CPU time. Although Bacula
676 currently permits using different options (compression, ...) on
677 a directory by directory basis, it cannot do it on a file by
678 file basis, which is clearly what was desired.
680 Proposed Implementation:
681 To solve this problem, I propose the following:
683 - Add a new Director resource type called FileOptions.
685 - The FileOptions resource will have records for all
686 options that can currently be specified on the Include record
687 (in a FileSet). Examples below.
689 - The FileOptions resource will permit an exclude option as well
690 as a number of additional options.
692 - The heart of the FileOptions resource is the ability to
693 supply any number of ApplyTo records which specify POSIX
694 regular expressions. These ApplyTo regular expressions are
695 applied to the fully qualified filename (path and all). If
696 one matches, then the FileOptions will be used.
698 - When an ApplyTo specification matches an included file, the
699 options specified in the FileOptions resource will override
700 the default options specified on the Include record.
702 - Include records will be modified to permit referencing one or
703 more FileOptions resources. The FileOptions will be used
704 in the order listed on the Include record and the first
705 one that matches will be applied.
707 - Options (or specifications) currently supplied on the Include
708 record will be deprecated (i.e. removed in a later version a
709 year or so from now).
711 - The Exclude record will be deprecated as the same functionality
712 can be obtained by using an Exclude = yes in the FileOptions.
715 The following records can appear in the FileOptions resource. An
716 asterisk preceding the name indicates a feature not currently
720 - Compression= (GZIP, ...)
721 - Signature= (MD5, SHA1, ...)
723 - OneFs= (yes/no) - remain on one filesystem
724 - Recurse= (yes/no) - recurse into subdirectories
725 - Sparse= (yes/no) - do sparse file backup
726 - *Exclude= (yes/no) - exclude file from being saved
727 - *Reader= (filename) - external read (backup) program
728 - *Plugin= (filename) - read/write plugin module
731 - verify= (ipnougsamc5) - verify options
734 - replace= (always/ifnewer/ifolder/never) - replace options currently
736 - *Writer= (filename) - external write (restore) program
740 Currently options specifying compression, MD5 signatures, recursion,
741 ... of a FileSet are supplied on the Include record. These will now
742 all be collected into a FileOptions resource, which will be
743 specified on the Include in place of the options. Multiple FileOptions
744 may be specified. Since the FileOptions contain regular expressions
745 that are applied to the full filename, this will give the ability
746 to specify backup options on a file by file basis to whatever level
755 Include = compression=GZIP signature=MD5 {
767 Match = /*.?*/ # matches all files.
772 That's a lot more to do the same thing, but it gives the ability to
773 apply options on a file by file basis. For example, suppose you
774 want to compress all files but not any file with extensions .gz or .Z.
775 You could do so as follows:
782 # Note multiple Matches are ORed
783 Match = /*.gz/ # matches .gz files */
784 Match = /*.Z/ # matches .Z files */
789 Match = /*.?*/ # matches all files
795 Now, since the NoCompress FileOptions is specified first on the
796 Include line, any *.gz or *.Z file will have an MD5 signature computed,
797 but will not be compressed. For all other files, the NoCompress will not
798 match, so the Opts options will be used which will include GZIP
802 - Is it necessary to provide some means of ANDing regular expressions
803 and negation? (not currently planned)
805 e.g. Match = /*.gz/ && !/big.gz/
807 - I see that Networker has a "null" module which, if specified, does not
808 backup the file, but does make an record of the file in the catalog
809 so that the catalog will reflect an exact picture of the filesystem.
810 The result is that the file can be "seen" when "browsing" the save
811 sets, but it cannot be restored.
813 Is this really useful? Should it be implemented in Bacula?
816 After implementing the above, the user will be able to specify
817 on a file by file basis (using regular expressions) what options are
818 applied for the backup.
821 =============================================
823 ==========================================================
825 For each Incremental job that is run, there may be files that
826 were found but not saved because they were locked (this applies
827 only to Windows). Such a system could send back to the Director
828 a list of Unsaved files.
830 - New UnSavedFiles table that contains:
834 - Then in the next Incremental job, the list of Unsaved Files will be
835 feed to the FD, who will ensure that they are explicitly chosen even
836 if standard date/time check would not have selected them.
837 =============================================================
840 Done: (see kernsdone for more)
841 - Implement new alist in FileSet scanning.
842 - bls should continue reading even if it finds Win32 data on the tape.
843 The error should be Warning rather the Error.
844 - Add user configurable timeout for connecting to SD.
845 - Unsaved Flag in Job record (use JobMissingFiles).
846 - Base Flag in Job record.
847 - Configure mtx-changer to have correct path to mtx.
848 - Add all command line arguments to "update", e.g. slot=nn volStatus=append, ...
849 - Make some way so that if a machine is skipped because it is not up
850 that Bacula will continue retrying for a specified period of time --
852 - Implement all command line args on run.
853 - Implement command line "restore" args.
854 - Implement "restore current select=no"
855 - Restore file modified before date
856 - Restore -- do nothing but show what would happen
857 - Add estimate to Console commands
858 - Use read_record.c in SD code.
859 - Fix read_record to handle multiple sessions.
860 - Tip from Steve Allam
861 mt -f /dev/nst0 defblksize 0
862 - Document "status" in the console.
863 - Document driving console from shell script.
864 - Write JobMedia records with max file size is reached on tape.
865 - Handle the case of multiple JobMedia records pending (i.e. the
866 thread is slow and multiple situations requiring a JobMedia
868 - Do performance analysis on the restore tree routines.
869 - Fix maximum file size (block.c) to generate JobMedia records.
870 - Make the default file size 1GB on the tape.
871 - Implement forward spacing between files.
872 - Add Machine type (Linux/Windows) to Status report for daemons.
874 - Use repositioning at the beginning of the tape.
875 - Do full check the command line args in update (e.g. VolStatus ...).