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