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