4 Documentation to do: (a little bit at a time)
5 - Document running a test version.
6 - Document query file format.
7 - Document static linking
8 - Document how to automatically backup all local partitions
9 - Document problems with Verify and pruning.
10 - Document how to use multiple databases.
13 Testing to do: (painful)
14 - that console command line options work
15 - blocksize recognition code.
16 - multiple simultaneous Volumes
19 - Add chflags() code for FreeBSD file flags
20 - Add RunBeforeJob and RunAfterJob to the Client program.
21 - Have SD compute MD5 or SHA1 and compare to what FD computes.
22 - Make VolumeToCatalog calculate an MD5 or SHA1 from the
23 actual data on the Volume and compare it.
24 - Implement FileOptions (see end of this document)
25 - Implement Bacula plugins -- design API
26 - Make bcopy read through bad tape records.
27 - Fix read_record to handle multiple sessions.
28 - Program files (i.e. execute a program to read/write files).
29 Pass read date of last backup, size of file last time.
30 - Add Signature type to File DB record.
31 - Make Restore report an error if FD or SD term codes are not OK.
32 - CD into subdirectory when open()ing files for backup to
33 speed up things. Test with testfind().
34 - Add prefixlinks to where or not where absolute links to FD.
35 - Look at handling <> in smtp doesn't work with exim.
36 - Priority job to go to top of list.
37 - Implement Bar code handling
38 - Why is catreq.c:111 Find vol called twice for a job?
39 - Find out why Full saves run slower and slower (hashing?)
40 - Why are save/restore of device different sizes (sparse?) Yup! Fix it.
41 - Implement some way for the Console to dynamically create a job.
42 - Restore to a particular time -- e.g. before date, after date.
43 - Implement disk spooling
44 - Implement finer multiprocessing options.
45 - Solaris -I on tar for include list
46 - Enable avoid backing up archive device (findlib/find_one.c:128)
47 - Need a verbose mode in restore, perhaps to bsr.
48 - bscan without -v is too quiet -- perhaps show jobs.
49 - Add code to reject whole blocks if not wanted on restore.
50 - Start working on Base jobs.
51 - Make sure the MaxVolFiles is fully implemented in SD
52 - Check if both CatalogFiles and UseCatalog are set to SD.
53 - Check if we can increase Bacula FD priorty in Win2000
54 - Need return status on read_cb() from read_records(). Need multiple
55 records -- one per Job, maybe a JCR or some other structure with
57 - Figure out how to do a bare metal Windows restore
58 - Put system type returned by FD into catalog.
59 - Need to specify MaximumConcurrentJobs in the Job resource.
60 - Possibly add email to Watchdog if drive is unmounted too
61 long and a job is waiting on the drive.
62 - Strip trailing slashes from Include directory names in the FD.
63 - Use read_record.c in SD code.
64 - Why don't we get an error message from Win32 FD when bootstrap
65 file cannot be created for restore command?
66 - When Marking a file in Restore that is a hard link, also
67 mark the link so that the data will be reloaded.
68 - Restore program that errors in SD due to no tape reports
69 OK incorrectly in output.
70 - After unmount, if restore job started, ask to mount.
71 - Convert all %x substitution variables, which are hard to remember
72 and read to %(variable-name). Idea from TMDA.
73 - Add JobLevel in FD status (but make sure it is defined).
74 - Make Pool resource handle Counter resources.
75 - Remove NextId for SQLite. Optimize.
76 - Strip trailing / from Include
77 - Move all SQL statements into a single location.
78 - Add UA rc and history files.
79 - put termcap (used by console) in ./configure and
80 allow -with-termcap-dir.
81 - Enhance time and size scanning routines.
82 - Fix Autoprune for Volumes to respect need for full save.
83 - Fix Win32 config file definition name on /install
84 - No READLINE_SRC if found in alternate directory.
85 - Add Client FS/OS id (Linux, Win95/98, ...).
86 - Test a second language e.g. french.
87 - Compare tape to Client files (attributes, or attributes and data)
88 - Make all database Ids 64 bit.
89 - Write an applet for Linux.
90 - Add estimate to Console commands
91 - Find solution to blank filename (i.e. path only) problem.
92 - Implement new daemon communications protocol.
93 - Remove PoolId from Job table, it exists in Media.
94 - Allow console commands to detach or run in background.
95 - Fix status delay on storage daemon during rewind.
96 - Add SD message variables to control operator wait time
97 - Maximum Operator Wait
98 - Minimum Message Interval
99 - Maximum Message Interval
100 - Send Operator message when cannot read tape label.
101 - Verify level=Volume (scan only), level=Data (compare of data to file).
102 Verify level=Catalog, level=InitCatalog
104 - Add keyword search to show command in Console.
105 - Fix Win2000 error with no messages during startup.
106 - Events : tape has more than xxx bytes.
107 - Restrict characters permitted in a Resource name.
108 - Complete code in Bacula Resources -- this will permit
109 reading a new config file at any time.
110 - Handle ctl-c in Console
111 - Implement LabelTemplate (at least first cut).
112 - Implement script driven addition of File daemon to config files.
113 - Think about how to make Bacula work better with File (non-tape) archives.
114 - Write Unix emulator for Windows.
116 - Implement new serialize subroutines
117 send(socket, "string", &Vol, "uint32", &i, NULL)
118 - Audit all UA commands to ensure that we always prompt where possible.
119 - If ./btape is called without /dev, assume argument is a Storage resource name.
120 - Put memory utilization in Status output of each daemon
121 if full status requested or if some level of debug on.
122 - Make database type selectable by .conf files i.e. at runtime
123 - gethostbyname failure in bnet_connect() continues
124 generating errors -- should stop.
125 - Set flag for uname -a. Add to Volume label.
126 - Implement throttled work queue.
127 - Check for EOT at ENOSPC or EIO or ENXIO (unix Pc)
128 - Allow multiple Storage specifications (or multiple names on
129 a single Storage specification) in the Job record. Thus a job
130 can be backed up to a number of storage devices.
131 - Implement dump label to UA
132 - Concept of VolumeSet during restore which is a list
133 of Volume names needed.
134 - Restore files modified after date
135 - Restore file modified before date
136 - Emergency restore info:
138 - Backup working directory
140 - Restore -- do nothing but show what would happen
141 - SET LD_RUN_PATH=$HOME/mysql/lib/mysql
142 - Implement Restore FileSet=
143 - Create a protocol.h and protocol.c where all protocol messages
145 - If SD cannot open a drive, make it periodically retry.
146 - Remove duplicate fields from jcr (e.g. jcr.level and jcr.jr.Level, ...).
147 - Timout a job or terminate if link goes down, or reopen link and query.
148 - Find general solution for sscanf size problems (as well
149 as sprintf. Do at run time?
150 - Concept of precious tapes (cannot be reused).
151 - Make bcopy copy with a single tape drive.
152 - Permit changing ownership during restore.
154 - Autolabel should be specified by DIR instead of SD.
155 - Find out how to get the system tape block limits, e.g.:
156 Apr 22 21:22:10 polymatou kernel: st1: Block limits 1 - 245760 bytes.
157 Apr 22 21:22:10 polymatou kernel: st0: Block limits 2 - 16777214 bytes.
160 - AutoScan (check checksum of tape)
161 - Format command = "format /dev/nst0"
165 - Seek resolution (usually corresponds to buffer size)
166 - EODErrorCode=ENOSPC or code
167 - Partial Read error code
168 - Partial write error code
169 - Nonformatted read error
170 - Nonformatted write error
171 - WriteProtected error
175 - IgnoreCloseErrors=yes
185 - FD sends unsaved file list to Director at end of job (see
187 - File daemon should build list of files skipped, and then
188 at end of save retry and report any errors.
189 - Write a Storage daemon that uses pipes and
190 standard Unix programs to write to the tape.
192 - Need something that monitors the JCR queue and
193 times out jobs by asking the deamons where they are.
194 - Enhance Jmsg code to permit buffering and saving to disk.
195 - device driver = "xxxx" for drives.
196 - restart: paranoid: read label fsf to
197 eom read append block, and go
198 super-paranoid: read label, read all files
199 in between, read append block, and go
200 verify: backspace, read append block, and go
201 permissive: same as above but frees drive
202 if tape is not valid.
204 - Ensure that /dev/null works
205 - Need report class for messages. Perhaps
206 report resource where report=group of messages
207 - enhance scan_attrib and rename scan_jobtype, and
208 fill in code for "since" option
209 - Director needs a time after which the report status is sent
210 anyway -- or better yet, a retry time for the job.
211 Don't reschedule a job if previous incarnation is still running.
212 - Some way to automatically backup everything is needed????
213 - Need a structure for pending actions:
215 - termination status (part of buffered msgs?)
216 - Concept of grouping Storage devices and job can use
217 any of a number of devices
219 Read, Write, Clean, Delete
220 - Login to Bacula; Bacula users with different permissions:
221 owner, group, user, quotas
222 - Store info on each file system type (probably in the job header on tape.
223 This could be the output of df; or perhaps some sort of /etc/mtab record.
226 - Design at hierarchial storage for Bacula.
227 - Implement FSM (File System Modules).
228 - Identify unchanged or "system" files and save them to a
229 special tape thus removing them from the standard
230 backup FileSet -- BASE backup.
231 - Turn virutally all sprintfs into snprintfs.
232 - Heartbeat between daemons.
233 - Audit M_ error codes to ensure they are correct and consistent.
234 - Add variable break characters to lex analyzer.
235 Either a bit mask or a string of chars so that
236 the caller can change the break characters.
237 - Make a single T_BREAK to replace T_COMMA, etc.
238 - Ensure that File daemon and Storage daemon can
239 continue a save if the Director goes down (this
240 is NOT currently the case). Must detect socket error,
241 buffer messages for later.
242 - Enhance time/duration input to allow multiple qualifiers e.g. 3d2h
243 - Add ability to backup to two Storage devices (two SD sessions) at
244 the same time -- e.g. onsite, offsite.
245 - Add the ability to consolidate old backup sets (basically do a restore
246 to tape and appropriately update the catalog). Compress Volume sets.
247 Might need to spool via file is only one drive is available.
248 - Compress or consolidate Volumes of old possibly deleted files. Perhaps
249 someway to do so with every volume that has less than x% valid
254 Bacula Projects Roadmap
256 last update 5 January 2003
258 Item 1: Multiple simultaneous Jobs. (done)
259 Done -- Restore part needs better implementation to work correctly
261 What: Permit multiple simultaneous jobs in Bacula.
263 Why: An enterprise level solution needs to go fast without the
264 need for the system administrator to carefully tweak
265 timing. Based on the benchmarks, during a full
266 backup, NetWorker typically hit 10 times the bandwidth to
267 the tape compared to Bacula--largely. This is probably due to
268 running parallel jobs and multi-threaded filling of buffers
269 and writing them to tape. This should also make things work
270 better when you have a mix of fast and slow machines backing
273 Notes: Bacula was designed to run multiple simultaneous jobs. Thus
274 implementing this is a matter of some small cleanups and
278 Item 2: Make the Storage daemon use intermediate file storage to buffer data.
279 Deferred -- not necessary yet.
281 What: If data is coming into the SD too fast, buffer it to
282 disk if the user has configured this option.
284 Why: This would be nice, especially if it more or less falls out
285 when implementing (1) above. If not, it probably should not
286 be given a high priority because fundamentally the backup time
287 is limited by the tape bandwidth. Even though you may finish a
288 client job quicker by spilling to disk, you still have to
289 eventually get it onto tape. If intermediate disk buffering
290 allows us to improve write bandwidth to tape, it may make
293 Notes: Whether or not this is implemented will depend upon performance
294 testing after item 1 is implemented.
297 Item 3: Write the bscan program -- also write a bcopy program.
300 What: Write a program that reads a Bacula tape and puts all the
301 appropriate data into the catalog. This allows recovery
302 from a tape that is no longer in the database, or it allows
303 re-creation of a database if lost.
305 Why: This is a fundamental robustness and disaster recovery tool
306 which will increase the comfort level of a sysadmin
307 considering adopting Bacula.
309 Notes: A skeleton of this program already exists, but much work
310 needs to be done. Implementing this will also make apparent
311 any deficiencies in the current Bacula tape format.
314 Item 4: Implement Base jobs.
316 What: A base job is sort of like a Full save except that you
317 will want the FileSet to contain only files that are unlikely
318 to change in the future (i.e. a snapshot of most of your
319 system after installing it). After the base job has been run,
320 when you are doing a Full save, you can specify to exclude
321 all files saved by the base job that have not been modified.
323 Why: This is something none of the competition does, as far as we know
324 (except BackupPC, which is a Perl program that saves to disk
325 only). It is big win for the user, it makes Bacula stand out
326 as offering a unique optimization that immediately saves time
329 Notes: Big savings in tape usage. Will require more resources because
330 the e. DIR must send FD a list of files/attribs, and the FD must
331 search the list and compare it for each file to be saved.
334 Item 5: Implement Label templates
336 What: This is a mechanism whereby Bacula can automatically create
337 a tape label for new tapes according to a detailed specification
338 provided by the user.
340 Why: It is a major convenience item for folks who use automated label
343 Notes: Bacula already has a working form of automatic tape label
344 creation, but it is very crude. The design for the complete
345 tape labeling project is already documented in the manual.
348 Item 6: Write a regression script.
351 What: This is an automatic script that runs and tests as many features
352 of Bacula as possible. The output is compared to previous
353 versions of Bacula and any differences are reported.
355 Why: This is an enormous help in preventing introduction of new
356 errors in parts of the program that already work correctly.
358 Notes: This probably should be ranked higher, it's something the typical
359 user doesn't see. Depending on how it's implemented, it may
360 make sense to defer it until the archival tape format and
361 user interface mature.
364 Item 7: GUI for interactive restore
365 Item 8: GUI for interactive backup
367 What: The current interactive restore is implemented with a tty
368 interface. It would be much nicer to be able to "see" the
369 list of files backed up in typical GUI tree format.
370 The same mechanism could also be used for creating
371 ad-hoc backup FileSets (item 8).
373 Why: Ease of use -- especially for the end user.
375 Notes: Rather than implementing in Gtk, we probably should go directly
376 for a Browser implementation, even if doing so meant the
377 capability wouldn't be available until much later. Not only
378 is there the question of Windows sites, most
379 Solaris/HP/IRIX, etc, shops can't currently run Gtk programs
380 without installing lots of stuff admins are very wary about.
381 Real sysadmins will always use the command line anyway, and
382 the user who's doing an interactive restore or backup of his
383 own files will in most cases be on a Windows machine running
387 Item 9: Add SSL to daemon communications.
389 What: This provides for secure communications between the daemons.
391 Why: This would allow doing backup across the Internet without
392 privacy concerns (or with much less concern).
394 Notes: The vast majority of near term potential users will be backing up
395 a single site over a LAN and, correctly or not, they probably
396 won't be concerned with security, at least not enough to go to
397 the trouble to set up keys, etc. to screw things down. We suspect
398 that many users genuinely interested in multi-site backup
399 already run some form of VPN software in their internetwork
400 connections, and are willing to delegate security to that layer.
403 Item 10: Define definitive tape format.
406 What: Define that definitive tape format that will not change
407 for the next millennium.
409 Why: Stability, security.
411 Notes: See notes for item 11 below.
414 Item 11: New daemon communication protocol.
416 What: The current daemon to daemon protocol is basically an ASCII
417 printf() and sending the buffer. On the receiving end, the
418 buffer is sscanf()ed to unpack it. The new scheme would
419 be a binary format that allows quick packing and unpacking
420 of any data type with named fields.
422 Why: Using binary packing would be faster. Named fields will permit
423 error checking to ensure that what is sent is what the
424 receiver really wants.
426 Notes: These are internal improvements in the interest of the
427 long-term stability and evolution of the program. On the one
428 hand, the sooner they're done, the less code we have to rip
429 up when the time comes to install them. On the other hand, they
430 don't bring an immediately perceptible benefit to potential
431 users. Item 10 and possibly item 11 should be deferred until Bacula
432 is well established with a growing user community more or
433 less happy with the feature set. At that time, it will make a
434 good "next generation" upgrade in the interest of data
440 ======================================================
442 It is somewhat like a Full save becomes an incremental since
443 the Base job (or jobs) plus other non-base files.
445 - New BaseFile table that contains:
446 JobId, BaseJobId, FileId (from Base).
447 i.e. for each base file that exists but is not saved because
448 it has not changed, the File daemon sends the JobId, BaseId,
449 and FileId back to the Director who creates the DB entry.
450 - To initiate a Base save, the Director sends the FD
451 the FileId, and full filename for each file in the Base.
452 - When the FD finds a Base file, he requests the Director to
453 send him the full File entry (stat packet plus MD5), or
454 conversely, the FD sends it to the Director and the Director
455 says yes or no. This can be quite rapid if the FileId is kept
456 by the FD for each Base Filename.
457 - It is probably better to have the comparison done by the FD
458 despite the fact that the File entry must be sent across the
460 - An alternative would be to send the FD the whole File entry
461 from the start. The disadvantage is that it requires a lot of
462 space. The advantage is that it requires less communications
464 - The Job record must be updated to indicate that one or more
466 - At end of Job, FD returns:
467 1. Count of base files/bytes not written to tape (i.e. matches)
468 2. Count of base file that were saved i.e. had changed.
469 - No tape record would be written for a Base file that matches, in the
470 same way that no tape record is written for Incremental jobs where
471 the file is not saved because it is unchanged.
472 - On a restore, all the Base file records must explicitly be
473 found from the BaseFile tape. I.e. for each Full save that is marked
474 to have one or more Base Jobs, search the BaseFile for all occurrences
476 - An optimization might be to make the BaseFile have:
482 This would avoid the need to explicitly fetch each File record for
483 the Base job. The Base Job record will be fetched to get the
484 VolSessionId and VolSessionTime.
485 =========================================================
487 ==========================================================
489 For each Incremental job that is run, there may be files that
490 were found but not saved because they were locked (this applies
491 only to Windows). Such a system could send back to the Director
492 a list of Unsaved files.
494 - New UnSavedFiles table that contains:
498 - Then in the next Incremental job, the list of Unsaved Files will be
499 feed to the FD, who will ensure that they are explicitly chosen even
500 if standard date/time check would not have selected them.
501 =============================================================
505 =============================================================
507 Request For Comments For File Backup Options
510 Subject: File Backup Options
513 A few days ago, a Bacula user who is backing up to file volumes and
514 using compression asked if it was possible to suppress compressing
515 all .gz files since it was a waste of CPU time. Although Bacula
516 currently permits using different options (compression, ...) on
517 a directory by directory basis, it cannot do it on a file by
518 file basis, which is clearly what was desired.
520 Proposed Implementation:
521 To solve this problem, I propose the following:
523 - Add a new Director resource type called FileOptions.
525 - The FileOptions resource will have records for all
526 options that can currently be specified on the Include record
527 (in a FileSet). Examples below.
529 - The FileOptions resource will permit an exclude option as well
530 as a number of additional options.
532 - The heart of the FileOptions resource is the ability to
533 supply any number of ApplyTo records which specify POSIX
534 regular expressions. These ApplyTo regular expressions are
535 applied to the fully qualified filename (path and all). If
536 one matches, then the FileOptions will be used.
538 - When an ApplyTo specification matches an included file, the
539 options specified in the FileOptions resource will override
540 the default options specified on the Include record.
542 - Include records will be modified to permit referencing one or
543 more FileOptions resources. The FileOptions will be used
544 in the order listed on the Include record and the first
545 one that matches will be applied.
547 - Options (or specifications) currently supplied on the Include
548 record will be deprecated (i.e. removed in a later version a
549 year or so from now).
551 - The Exclude record will be deprecated as the same functionality
552 can be obtained by using an Exclude = yes in the FileOptions.
555 The following records can appear in the FileOptions resource. An
556 asterisk preceding the name indicates a feature not currently
560 - Compression= (GZIP, ...)
561 - Signature= (MD5, SHA1, ...)
563 - OneFs= (yes/no) - remain on one filesystem
564 - Recurse= (yes/no) - recurse into subdirectories
565 - Sparse= (yes/no) - do sparse file backup
566 - *Exclude= (yes/no) - exclude file from being saved
567 - *Reader= (filename) - external read (backup) program
568 - *Plugin= (filename) - read/write plugin module
571 - verify= (ipnougsamc5) - verify options
574 - replace= (always/ifnewer/ifolder/never) - replace options currently
576 - *Writer= (filename) - external write (restore) program
580 Currently options specifying compression, MD5 signatures, recursion,
581 ... of a FileSet are supplied on the Include record. These will now
582 all be collected into a FileOptions resource, which will be
583 specified on the Include in place of the options. Multiple FileOptions
584 may be specified. Since the FileOptions contain regular expressions
585 that are applied to the full filename, this will give the ability
586 to specify backup options on a file by file basis to whatever level
595 Include = compression=GZIP signature=MD5 {
604 Include = FileOptions=Opts {
615 That's a lot more to do the same thing, but it gives the ability to
616 apply options on a file by file basis. For example, suppose you
617 want to compress all files but not any file with extensions .gz or .Z.
618 You could do so as follows:
622 Include = FileOptions=NoCompress FileOptions=Opts {
630 ApplyTo = /*.?*/ # matches all files
635 # Note multiple ApplyTos are ORed
636 ApplyTo = /*.gz/ # matches .gz files */
637 ApplyTo = /*.Z/ # matches .Z files */
640 Now, since the NoCompress FileOptions is specified first on the
641 Include line, any *.gz or *.Z file will have an MD5 signature computed,
642 but will not be compressed. For all other files, the NoCompress will not
643 match, so the Opts options will be used which will include GZIP
647 - Is it necessary to provide some means of ANDing regular expressions
648 and negation? (not currently planned)
650 e.g. ApplyTo = /*.gz/ && !/big.gz/
652 - I see that Networker has a "null" module which, if specified, does not
653 backup the file, but does make an record of the file in the catalog
654 so that the catalog will reflect an exact picture of the filesystem.
655 The result is that the file can be "seen" when "browsing" the save
656 sets, but it cannot be restored.
658 Is this really useful? Should it be implemented in Bacula?
661 After implementing the above, the user will be able to specify
662 on a file by file basis (using regular expressions) what options are
663 applied for the backup.
664 ====================================
666 =========================================
667 Proposal by Bill Sellers
669 Return-Path: <w.a.sellers@larc.nasa.gov>
670 Received: from post.larc.nasa.gov (post.larc.nasa.gov [128.155.4.45]) by matou.sibbald.com (8.11.6/8.11.6) with ESMTP id h0ELUIm07622 for <kern@sibbald.com>; Tue, 14 Jan 2003 22:30:18 +0100
671 Received: from Baron.larc.nasa.gov (baron.larc.nasa.gov [128.155.40.132]) by post.larc.nasa.gov (pohub4.6) with ESMTP id QAA09768 for <kern@sibbald.com>; Tue, 14 Jan 2003 16:30:14 -0500 (EST)
672 Message-Id: <5.1.0.14.2.20030114153452.028dbae8@pop.larc.nasa.gov>
673 X-Sender: w.a.sellers@pop.larc.nasa.gov
674 X-Mailer: QUALCOMM Windows Eudora Version 5.1
675 Date: Tue, 14 Jan 2003 16:30:18 -0500
676 To: Kern Sibbald <kern@sibbald.com>
677 From: Bill Sellers <w.a.sellers@larc.nasa.gov>
678 Subject: Re: [Bacula-users] Bacula remote storage?
679 In-Reply-To: <1042565382.1845.177.camel@rufus>
680 References: <5.1.0.14.2.20030114113004.0293a210@pop.larc.nasa.gov> <5.1.0.14.2.20030113170650.028dad88@pop.larc.nasa.gov> <5.1.0.14.2.20030113170650.028dad88@pop.larc.nasa.gov> <5.1.0.14.2.20030114113004.0293a210@pop.larc.nasa.gov>
682 Content-Type: text/plain; charset="us-ascii"; format=flowed
683 X-Annoyance-Filter-Junk-Probability: 0
684 X-Annoyance-Filter-Classification: Mail
685 At 06:29 PM 1/14/2003 +0100, you wrote:
688 >Well, if you cannot put a Bacula client on the machine,
689 >then it is a big problem. If you know of some software
690 >that can do what you want, let me know, because I
691 >really just don't know how to do it -- at least not
697 We have been able to get Amanda to use the HSM as a storage
698 device. Someone here wrote a driver for Amanda. BUT, Amanda doesn't
699 handle Windows systems very well (or at all without Samba). So I am
700 looking for a backup system that has a Windows client. I really like the
701 Windows integration of Bacula.
703 From the command line, its rather trivial to move the data around. We use
706 tar cf - ./files | gzip -c | rsh hsm dd of=path/file.tgz
708 or if you use GNU tar:
710 tar czf hsm:path/file.tgz ./files
712 One idea for you to consider; Sendmail offers pipes in the aliases file;
713 (mailpipe: "|/usr/bin/vacation root") and Perl supports pipes in the
714 "open" statement (open FILE, "|/bin/nroff -man";) Could you could make a
715 pipe available, as a storage device? Then we could use any command that
716 handles stdin as a storage destination.
723 #Password is not used in rsh, but might be used in ftp.
724 Device = "| gzip -c | rsh hsm dd of=path/file.tgz"
731 Password = "foobar&-"
732 Device = "| ncftpput -c hsm /path/file.bacula"
736 >If you have some local storage available, you could
737 >use Bacula to backup to disk volumes, then use some
738 >other software (ftp, scp) to move them to the HSM
739 >machine. However, this is a bit kludgy.
742 It is, but maybe worth a try. Is there some function in Bacula to put
743 variables in filenames? i.e. backup.2003-01-15.root
750 w.a.sellers@larc.nasa.gov
752 ==============================================
753 The Project for the above
755 I finally realized that this is not at all
756 the same as reader/writer programs or plugins,
757 which are alternate ways of accessing the
758 files to be backed up. Rather, it is an alternate
759 form of storage device, and I have always planned
760 that Bacula should be able to handle all sorts
763 So, I propose the following phases:
765 1. OK from you to invest some time in testing
766 this as I implement it (requires that you
767 know how to download from the SourceForge
768 cvs -- which I imagine is a piece of cake
771 2. Dumb implementation by allowing a device to
772 be a fifo for write only.
773 Reason: easy to implement, proof of concept.
775 3. Try reading from fifo but with fixed block
777 Reason: proof of concept, easy to implement.
779 4. Extend reading from fifo (restores) to handle
781 Reason: requires some delicate low level coding
782 which could destabilize all of Bacula.
784 5. Implementation of above but to a program. E.g.
785 Device = "|program" (not full pipeline).
786 Reason: routines already exist, and program can
787 be a shell script which contains anything.
789 6. Add full pipeline as a possibility. E.g.
790 Device = "| gzip -c | rsh hsm dd of=path/file.tgz"
791 Reason: needs additional coding to implement full
792 pipeline (must fire off either a shell or all
793 programs and connect their pipes).
795 There are a good number of details in each step
796 that I have left out, but I will specify them at
797 every stage, and there may be a few changes as things
798 evolve. I expect that to get to stage 5 will take a
799 few weeks, and at that point, you will have
800 everything you need (just inside a script).
801 Stage 6 will probably take longer, but if this
802 project pleases you, what we do for 5 should
803 be adequate for some time.
807 =============================================
809 Done: (see kernsdone for more)
810 - Look into Pruning/purging problems or why there seem to
811 be so many files listed each night.
812 - Fix cancel in find_one -- need jcr.
813 - Cancel does not work for restore in FD.
814 - Write SetJobStatus() function so cancel status not lost.
815 - Add include list to end of chain in findlib
816 - Zap sd_auth_key after use
817 - Add Bar code reading capabilities (new mtx-changer)
818 - Figure out some way to automatically backup all local partitions
819 - Make hash table for linked files in findlib/find_one.c:161
821 - Rewrite find_one.c to use only pool_memory instead of
822 alloca and malloc (probably not necessary).
823 - Make sure btraceback goes into /sbin not sysconf directory.
824 - InitVerify is getting pruned and it shouldn't (document it)
825 - Make 1.28c release ??? NO do 1.29 directly
826 - Set timeout on opening fifo for save or restore (findlib)
827 - Document FIFO storage device.
828 - Document fifo and | and <
831 - Get correct error status from run_program or open_bpipe().
832 - Restrict permissions on File Volumes (now 0640).
833 - Umasked 022 daemons
834 - Fix restore of hard linked file.
835 - Figure out how to allow multiple simultaneous file Volumes on a single device.
836 - Implement multiple simultaneous file Volumes on a single device.
837 - Cleanup db_update_media and db_update_pool
838 - Flush all the daemon messages at the end of every job.
839 - Change stat1= fgets()!=NULL to stat1=fgest()==NULL; in
840 run_program -- bpipe.c