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.
11 - Document Maximum File Size
13 - Add a section to the doc on Manual cycling of Volumes.
15 Testing to do: (painful)
16 - that ALL console command line options work and are always implemented
17 - blocksize recognition code.
18 - multiple simultaneous Volumes
21 - Update volume=Test01 requests pool, then lists volumes.
22 - Add IP address to authentication failures. Implement M_SECURITY
24 - Look at Python for a Bacula scripting language -- www.python.org
25 - add #define ENABLE_NLS for Gnome compile on SuSE.
26 - Figure out how to use ssh to protect Bacula communications.
27 - Fix "access not allowed" for backup of files on WinXP.
28 - Issue message to mount a new tape before the rewind.
29 - Simplified client job initiation for portables.
30 - If SD cannot open a drive, make it periodically retry.
31 - Implement LabelTemplate (at least first cut).
32 - Add more of the config info to the tape label.
33 - Add a default File storage so that new users can do backup
34 and restores right away.
35 - Implement a Mount Command and an Unmount Command where
36 the users could specify a system command to be performed
37 to do the mount, after which Bacula could attempt to
38 read the device. This is for Removeable media such as a CDROM.
39 - Most likely, this mount command would be invoked explicitly
40 by the user using the current Console "mount" and "unmount"
41 commands -- the Storage Daemon would do the right thing
42 depending on the exact nature of the device.
43 - As with tape drives, when Bacula wanted a new removable
44 disk mounted, it would unmount the old one, and send a message
45 to the user, who would then use "mount" as described above
46 once he had actually inserted the disk.
48 - Make some way so that if a machine is skipped because it is not up
49 that Bacula will continue retrying for a specified period of time --
51 - If tape is marked read-only, then try opening it read-only rather than
52 failing, and remember that it cannot be written.
53 - Refine SD waiting output:
54 Device is being positioned
55 > Device is being positioned for append
56 > Device is being positioned to file x
58 - Figure out some way to estimate output size and to avoid splitting
59 a backup across two Volumes -- this could be useful for writing CDROMs
60 where you really prefer not to have it split -- not serious.
61 - Add RunBeforeJob and RunAfterJob to the Client program.
62 - Have SD compute MD5 or SHA1 and compare to what FD computes.
63 - Make VolumeToCatalog calculate an MD5 or SHA1 from the
64 actual data on the Volume and compare it.
65 - Implement FileOptions (see end of this document)
66 - Implement Bacula plugins -- design API
67 - Make bcopy read through bad tape records.
68 - Fix read_record to handle multiple sessions.
69 - Program files (i.e. execute a program to read/write files).
70 Pass read date of last backup, size of file last time.
71 - Add Signature type to File DB record.
72 - Make Restore report an error if FD or SD term codes are not OK.
73 - CD into subdirectory when open()ing files for backup to
74 speed up things. Test with testfind().
75 - Add prefixlinks to where or not where absolute links to FD.
76 - Priority job to go to top of list.
77 - Find out why Full saves run slower and slower (hashing?)
78 - Why are save/restore of device different sizes (sparse?) Yup! Fix it.
79 - Implement some way for the Console to dynamically create a job.
80 - Restore to a particular time -- e.g. before date, after date.
81 - Implement disk spooling
82 - Solaris -I on tar for include list
83 - Prohibit backing up archive device (findlib/find_one.c:128)
84 - Need a verbose mode in restore, perhaps to bsr.
85 - bscan without -v is too quiet -- perhaps show jobs.
86 - Add code to reject whole blocks if not wanted on restore.
87 - Start working on Base jobs.
88 - Make sure the MaxVolFiles is fully implemented in SD
89 - Check if both CatalogFiles and UseCatalog are set to SD.
90 - Check if we can increase Bacula FD priorty in Win2000
91 - Need return status on read_cb() from read_records(). Need multiple
92 records -- one per Job, maybe a JCR or some other structure with
94 - Figure out how to do a bare metal Windows restore
95 - Put system type returned by FD into catalog.
96 - Possibly add email to Watchdog if drive is unmounted too
97 long and a job is waiting on the drive.
98 - Use read_record.c in SD code.
99 - Why don't we get an error message from Win32 FD when bootstrap
100 file cannot be created for restore command?
101 - When Marking a file in Restore that is a hard link, also
102 mark the link so that the data will be reloaded.
103 - Restore program that errors in SD due to no tape reports
104 OK incorrectly in output.
105 - After unmount, if restore job started, ask to mount.
106 - Convert all %x substitution variables, which are hard to remember
107 and read to %(variable-name). Idea from TMDA.
108 - Add JobLevel in FD status (but make sure it is defined).
109 - Make Pool resource handle Counter resources.
110 - Remove NextId for SQLite. Optimize.
111 - Move all SQL statements into a single location.
112 - Add UA rc and history files.
113 - put termcap (used by console) in ./configure and
114 allow -with-termcap-dir.
115 - Enhance time and size scanning routines.
116 - Fix Autoprune for Volumes to respect need for full save.
117 - Fix Win32 config file definition name on /install
118 - No READLINE_SRC if found in alternate directory.
119 - Add Client FS/OS id (Linux, Win95/98, ...).
120 - Test a second language e.g. french.
121 - Compare tape to Client files (attributes, or attributes and data)
122 - Make all database Ids 64 bit.
123 - Write an applet for Linux.
124 - Add estimate to Console commands
125 - Find solution to blank filename (i.e. path only) problem.
126 - Implement new daemon communications protocol.
127 - Remove PoolId from Job table, it exists in Media.
128 - Allow console commands to detach or run in background.
129 - Fix status delay on storage daemon during rewind.
130 - Add SD message variables to control operator wait time
131 - Maximum Operator Wait
132 - Minimum Message Interval
133 - Maximum Message Interval
134 - Send Operator message when cannot read tape label.
135 - Verify level=Volume (scan only), level=Data (compare of data to file).
136 Verify level=Catalog, level=InitCatalog
138 - Add keyword search to show command in Console.
139 - Fix Win2000 error with no messages during startup.
140 - Events : tape has more than xxx bytes.
141 - Restrict characters permitted in a Resource name.
142 - Complete code in Bacula Resources -- this will permit
143 reading a new config file at any time.
144 - Handle ctl-c in Console
145 - Implement script driven addition of File daemon to config files.
146 - Think about how to make Bacula work better with File (non-tape) archives.
147 - Write Unix emulator for Windows.
149 - Implement new serialize subroutines
150 send(socket, "string", &Vol, "uint32", &i, NULL)
151 - Audit all UA commands to ensure that we always prompt where possible.
152 - If ./btape is called without /dev, assume argument is a Storage resource name.
153 - Put memory utilization in Status output of each daemon
154 if full status requested or if some level of debug on.
155 - Make database type selectable by .conf files i.e. at runtime
156 - Set flag for uname -a. Add to Volume label.
157 - Implement throttled work queue.
158 - Check for EOT at ENOSPC or EIO or ENXIO (unix Pc)
159 - Allow multiple Storage specifications (or multiple names on
160 a single Storage specification) in the Job record. Thus a job
161 can be backed up to a number of storage devices.
162 - Implement dump label to UA
163 - Concept of VolumeSet during restore which is a list
164 of Volume names needed.
165 - Restore files modified after date
166 - Restore file modified before date
167 - Emergency restore info:
169 - Backup working directory
171 - Restore -- do nothing but show what would happen
172 - SET LD_RUN_PATH=$HOME/mysql/lib/mysql
173 - Implement Restore FileSet=
174 - Create a protocol.h and protocol.c where all protocol messages
176 - Remove duplicate fields from jcr (e.g. jcr.level and jcr.jr.Level, ...).
177 - Timout a job or terminate if link goes down, or reopen link and query.
178 - Find general solution for sscanf size problems (as well
179 as sprintf. Do at run time?
180 - Concept of precious tapes (cannot be reused).
181 - Make bcopy copy with a single tape drive.
182 - Permit changing ownership during restore.
184 - Autolabel should be specified by DIR instead of SD.
185 - Find out how to get the system tape block limits, e.g.:
186 Apr 22 21:22:10 polymatou kernel: st1: Block limits 1 - 245760 bytes.
187 Apr 22 21:22:10 polymatou kernel: st0: Block limits 2 - 16777214 bytes.
190 - AutoScan (check checksum of tape)
191 - Format command = "format /dev/nst0"
195 - Seek resolution (usually corresponds to buffer size)
196 - EODErrorCode=ENOSPC or code
197 - Partial Read error code
198 - Partial write error code
199 - Nonformatted read error
200 - Nonformatted write error
201 - WriteProtected error
205 - IgnoreCloseErrors=yes
215 - FD sends unsaved file list to Director at end of job (see
217 - File daemon should build list of files skipped, and then
218 at end of save retry and report any errors.
219 - Write a Storage daemon that uses pipes and
220 standard Unix programs to write to the tape.
222 - Need something that monitors the JCR queue and
223 times out jobs by asking the deamons where they are.
224 - Enhance Jmsg code to permit buffering and saving to disk.
225 - device driver = "xxxx" for drives.
226 - restart: paranoid: read label fsf to
227 eom read append block, and go
228 super-paranoid: read label, read all files
229 in between, read append block, and go
230 verify: backspace, read append block, and go
231 permissive: same as above but frees drive
232 if tape is not valid.
234 - Ensure that /dev/null works
235 - Need report class for messages. Perhaps
236 report resource where report=group of messages
237 - enhance scan_attrib and rename scan_jobtype, and
238 fill in code for "since" option
239 - Director needs a time after which the report status is sent
240 anyway -- or better yet, a retry time for the job.
241 Don't reschedule a job if previous incarnation is still running.
242 - Some way to automatically backup everything is needed????
243 - Need a structure for pending actions:
245 - termination status (part of buffered msgs?)
246 - Concept of grouping Storage devices and job can use
247 any of a number of devices
249 Read, Write, Clean, Delete
250 - Login to Bacula; Bacula users with different permissions:
251 owner, group, user, quotas
252 - Store info on each file system type (probably in the job header on tape.
253 This could be the output of df; or perhaps some sort of /etc/mtab record.
256 - Design at hierarchial storage for Bacula. Migration and Clone.
257 - Implement FSM (File System Modules).
258 - Identify unchanged or "system" files and save them to a
259 special tape thus removing them from the standard
260 backup FileSet -- BASE backup.
261 - Turn virutally all sprintfs into snprintfs.
262 - Heartbeat between daemons.
263 - Audit M_ error codes to ensure they are correct and consistent.
264 - Add variable break characters to lex analyzer.
265 Either a bit mask or a string of chars so that
266 the caller can change the break characters.
267 - Make a single T_BREAK to replace T_COMMA, etc.
268 - Ensure that File daemon and Storage daemon can
269 continue a save if the Director goes down (this
270 is NOT currently the case). Must detect socket error,
271 buffer messages for later.
272 - Enhance time/duration input to allow multiple qualifiers e.g. 3d2h
273 - Add ability to backup to two Storage devices (two SD sessions) at
274 the same time -- e.g. onsite, offsite.
275 - Add the ability to consolidate old backup sets (basically do a restore
276 to tape and appropriately update the catalog). Compress Volume sets.
277 Might need to spool via file is only one drive is available.
278 - Compress or consolidate Volumes of old possibly deleted files. Perhaps
279 someway to do so with every volume that has less than x% valid
284 Bacula Projects Roadmap
286 last update 5 January 2003
288 Item 1: Multiple simultaneous Jobs. (done)
289 Done -- Restore part needs better implementation to work correctly
291 What: Permit multiple simultaneous jobs in Bacula.
293 Why: An enterprise level solution needs to go fast without the
294 need for the system administrator to carefully tweak
295 timing. Based on the benchmarks, during a full
296 backup, NetWorker typically hit 10 times the bandwidth to
297 the tape compared to Bacula--largely. This is probably due to
298 running parallel jobs and multi-threaded filling of buffers
299 and writing them to tape. This should also make things work
300 better when you have a mix of fast and slow machines backing
303 Notes: Bacula was designed to run multiple simultaneous jobs. Thus
304 implementing this is a matter of some small cleanups and
308 Item 2: Make the Storage daemon use intermediate file storage to buffer data.
309 Deferred -- not necessary yet.
311 What: If data is coming into the SD too fast, buffer it to
312 disk if the user has configured this option.
314 Why: This would be nice, especially if it more or less falls out
315 when implementing (1) above. If not, it probably should not
316 be given a high priority because fundamentally the backup time
317 is limited by the tape bandwidth. Even though you may finish a
318 client job quicker by spilling to disk, you still have to
319 eventually get it onto tape. If intermediate disk buffering
320 allows us to improve write bandwidth to tape, it may make
323 Notes: Whether or not this is implemented will depend upon performance
324 testing after item 1 is implemented.
327 Item 3: Write the bscan program -- also write a bcopy program.
330 What: Write a program that reads a Bacula tape and puts all the
331 appropriate data into the catalog. This allows recovery
332 from a tape that is no longer in the database, or it allows
333 re-creation of a database if lost.
335 Why: This is a fundamental robustness and disaster recovery tool
336 which will increase the comfort level of a sysadmin
337 considering adopting Bacula.
339 Notes: A skeleton of this program already exists, but much work
340 needs to be done. Implementing this will also make apparent
341 any deficiencies in the current Bacula tape format.
344 Item 4: Implement Base jobs.
346 What: A base job is sort of like a Full save except that you
347 will want the FileSet to contain only files that are unlikely
348 to change in the future (i.e. a snapshot of most of your
349 system after installing it). After the base job has been run,
350 when you are doing a Full save, you can specify to exclude
351 all files saved by the base job that have not been modified.
353 Why: This is something none of the competition does, as far as we know
354 (except BackupPC, which is a Perl program that saves to disk
355 only). It is big win for the user, it makes Bacula stand out
356 as offering a unique optimization that immediately saves time
359 Notes: Big savings in tape usage. Will require more resources because
360 the e. DIR must send FD a list of files/attribs, and the FD must
361 search the list and compare it for each file to be saved.
364 Item 5: Implement Label templates
366 What: This is a mechanism whereby Bacula can automatically create
367 a tape label for new tapes according to a detailed specification
368 provided by the user.
370 Why: It is a major convenience item for folks who use automated label
373 Notes: Bacula already has a working form of automatic tape label
374 creation, but it is very crude. The design for the complete
375 tape labeling project is already documented in the manual.
378 Item 6: Write a regression script.
381 What: This is an automatic script that runs and tests as many features
382 of Bacula as possible. The output is compared to previous
383 versions of Bacula and any differences are reported.
385 Why: This is an enormous help in preventing introduction of new
386 errors in parts of the program that already work correctly.
388 Notes: This probably should be ranked higher, it's something the typical
389 user doesn't see. Depending on how it's implemented, it may
390 make sense to defer it until the archival tape format and
391 user interface mature.
394 Item 7: GUI for interactive restore
395 Item 8: GUI for interactive backup
397 What: The current interactive restore is implemented with a tty
398 interface. It would be much nicer to be able to "see" the
399 list of files backed up in typical GUI tree format.
400 The same mechanism could also be used for creating
401 ad-hoc backup FileSets (item 8).
403 Why: Ease of use -- especially for the end user.
405 Notes: Rather than implementing in Gtk, we probably should go directly
406 for a Browser implementation, even if doing so meant the
407 capability wouldn't be available until much later. Not only
408 is there the question of Windows sites, most
409 Solaris/HP/IRIX, etc, shops can't currently run Gtk programs
410 without installing lots of stuff admins are very wary about.
411 Real sysadmins will always use the command line anyway, and
412 the user who's doing an interactive restore or backup of his
413 own files will in most cases be on a Windows machine running
417 Item 9: Add SSL to daemon communications.
419 What: This provides for secure communications between the daemons.
421 Why: This would allow doing backup across the Internet without
422 privacy concerns (or with much less concern).
424 Notes: The vast majority of near term potential users will be backing up
425 a single site over a LAN and, correctly or not, they probably
426 won't be concerned with security, at least not enough to go to
427 the trouble to set up keys, etc. to screw things down. We suspect
428 that many users genuinely interested in multi-site backup
429 already run some form of VPN software in their internetwork
430 connections, and are willing to delegate security to that layer.
433 Item 10: Define definitive tape format.
436 What: Define that definitive tape format that will not change
437 for the next millennium.
439 Why: Stability, security.
441 Notes: See notes for item 11 below.
444 Item 11: New daemon communication protocol.
446 What: The current daemon to daemon protocol is basically an ASCII
447 printf() and sending the buffer. On the receiving end, the
448 buffer is sscanf()ed to unpack it. The new scheme would
449 be a binary format that allows quick packing and unpacking
450 of any data type with named fields.
452 Why: Using binary packing would be faster. Named fields will permit
453 error checking to ensure that what is sent is what the
454 receiver really wants.
456 Notes: These are internal improvements in the interest of the
457 long-term stability and evolution of the program. On the one
458 hand, the sooner they're done, the less code we have to rip
459 up when the time comes to install them. On the other hand, they
460 don't bring an immediately perceptible benefit to potential
461 users. Item 10 and possibly item 11 should be deferred until Bacula
462 is well established with a growing user community more or
463 less happy with the feature set. At that time, it will make a
464 good "next generation" upgrade in the interest of data
470 ======================================================
472 It is somewhat like a Full save becomes an incremental since
473 the Base job (or jobs) plus other non-base files.
475 - New BaseFile table that contains:
476 JobId, BaseJobId, FileId (from Base).
477 i.e. for each base file that exists but is not saved because
478 it has not changed, the File daemon sends the JobId, BaseId,
479 and FileId back to the Director who creates the DB entry.
480 - To initiate a Base save, the Director sends the FD
481 the FileId, and full filename for each file in the Base.
482 - When the FD finds a Base file, he requests the Director to
483 send him the full File entry (stat packet plus MD5), or
484 conversely, the FD sends it to the Director and the Director
485 says yes or no. This can be quite rapid if the FileId is kept
486 by the FD for each Base Filename.
487 - It is probably better to have the comparison done by the FD
488 despite the fact that the File entry must be sent across the
490 - An alternative would be to send the FD the whole File entry
491 from the start. The disadvantage is that it requires a lot of
492 space. The advantage is that it requires less communications
494 - The Job record must be updated to indicate that one or more
496 - At end of Job, FD returns:
497 1. Count of base files/bytes not written to tape (i.e. matches)
498 2. Count of base file that were saved i.e. had changed.
499 - No tape record would be written for a Base file that matches, in the
500 same way that no tape record is written for Incremental jobs where
501 the file is not saved because it is unchanged.
502 - On a restore, all the Base file records must explicitly be
503 found from the BaseFile tape. I.e. for each Full save that is marked
504 to have one or more Base Jobs, search the BaseFile for all occurrences
506 - An optimization might be to make the BaseFile have:
512 This would avoid the need to explicitly fetch each File record for
513 the Base job. The Base Job record will be fetched to get the
514 VolSessionId and VolSessionTime.
515 =========================================================
517 ==========================================================
519 For each Incremental job that is run, there may be files that
520 were found but not saved because they were locked (this applies
521 only to Windows). Such a system could send back to the Director
522 a list of Unsaved files.
524 - New UnSavedFiles table that contains:
528 - Then in the next Incremental job, the list of Unsaved Files will be
529 feed to the FD, who will ensure that they are explicitly chosen even
530 if standard date/time check would not have selected them.
531 =============================================================
535 =============================================================
537 Request For Comments For File Backup Options
540 Subject: File Backup Options
543 A few days ago, a Bacula user who is backing up to file volumes and
544 using compression asked if it was possible to suppress compressing
545 all .gz files since it was a waste of CPU time. Although Bacula
546 currently permits using different options (compression, ...) on
547 a directory by directory basis, it cannot do it on a file by
548 file basis, which is clearly what was desired.
550 Proposed Implementation:
551 To solve this problem, I propose the following:
553 - Add a new Director resource type called FileOptions.
555 - The FileOptions resource will have records for all
556 options that can currently be specified on the Include record
557 (in a FileSet). Examples below.
559 - The FileOptions resource will permit an exclude option as well
560 as a number of additional options.
562 - The heart of the FileOptions resource is the ability to
563 supply any number of ApplyTo records which specify POSIX
564 regular expressions. These ApplyTo regular expressions are
565 applied to the fully qualified filename (path and all). If
566 one matches, then the FileOptions will be used.
568 - When an ApplyTo specification matches an included file, the
569 options specified in the FileOptions resource will override
570 the default options specified on the Include record.
572 - Include records will be modified to permit referencing one or
573 more FileOptions resources. The FileOptions will be used
574 in the order listed on the Include record and the first
575 one that matches will be applied.
577 - Options (or specifications) currently supplied on the Include
578 record will be deprecated (i.e. removed in a later version a
579 year or so from now).
581 - The Exclude record will be deprecated as the same functionality
582 can be obtained by using an Exclude = yes in the FileOptions.
585 The following records can appear in the FileOptions resource. An
586 asterisk preceding the name indicates a feature not currently
590 - Compression= (GZIP, ...)
591 - Signature= (MD5, SHA1, ...)
593 - OneFs= (yes/no) - remain on one filesystem
594 - Recurse= (yes/no) - recurse into subdirectories
595 - Sparse= (yes/no) - do sparse file backup
596 - *Exclude= (yes/no) - exclude file from being saved
597 - *Reader= (filename) - external read (backup) program
598 - *Plugin= (filename) - read/write plugin module
601 - verify= (ipnougsamc5) - verify options
604 - replace= (always/ifnewer/ifolder/never) - replace options currently
606 - *Writer= (filename) - external write (restore) program
610 Currently options specifying compression, MD5 signatures, recursion,
611 ... of a FileSet are supplied on the Include record. These will now
612 all be collected into a FileOptions resource, which will be
613 specified on the Include in place of the options. Multiple FileOptions
614 may be specified. Since the FileOptions contain regular expressions
615 that are applied to the full filename, this will give the ability
616 to specify backup options on a file by file basis to whatever level
625 Include = compression=GZIP signature=MD5 {
634 Include = FileOptions=Opts {
645 That's a lot more to do the same thing, but it gives the ability to
646 apply options on a file by file basis. For example, suppose you
647 want to compress all files but not any file with extensions .gz or .Z.
648 You could do so as follows:
652 Include = FileOptions=NoCompress FileOptions=Opts {
660 ApplyTo = /*.?*/ # matches all files
665 # Note multiple ApplyTos are ORed
666 ApplyTo = /*.gz/ # matches .gz files */
667 ApplyTo = /*.Z/ # matches .Z files */
670 Now, since the NoCompress FileOptions is specified first on the
671 Include line, any *.gz or *.Z file will have an MD5 signature computed,
672 but will not be compressed. For all other files, the NoCompress will not
673 match, so the Opts options will be used which will include GZIP
677 - Is it necessary to provide some means of ANDing regular expressions
678 and negation? (not currently planned)
680 e.g. ApplyTo = /*.gz/ && !/big.gz/
682 - I see that Networker has a "null" module which, if specified, does not
683 backup the file, but does make an record of the file in the catalog
684 so that the catalog will reflect an exact picture of the filesystem.
685 The result is that the file can be "seen" when "browsing" the save
686 sets, but it cannot be restored.
688 Is this really useful? Should it be implemented in Bacula?
691 After implementing the above, the user will be able to specify
692 on a file by file basis (using regular expressions) what options are
693 applied for the backup.
694 ====================================
696 =========================================
697 Proposal by Bill Sellers
699 Return-Path: <w.a.sellers@larc.nasa.gov>
700 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
701 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)
702 Message-Id: <5.1.0.14.2.20030114153452.028dbae8@pop.larc.nasa.gov>
703 X-Sender: w.a.sellers@pop.larc.nasa.gov
704 X-Mailer: QUALCOMM Windows Eudora Version 5.1
705 Date: Tue, 14 Jan 2003 16:30:18 -0500
706 To: Kern Sibbald <kern@sibbald.com>
707 From: Bill Sellers <w.a.sellers@larc.nasa.gov>
708 Subject: Re: [Bacula-users] Bacula remote storage?
709 In-Reply-To: <1042565382.1845.177.camel@rufus>
710 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>
712 Content-Type: text/plain; charset="us-ascii"; format=flowed
713 X-Annoyance-Filter-Junk-Probability: 0
714 X-Annoyance-Filter-Classification: Mail
715 At 06:29 PM 1/14/2003 +0100, you wrote:
718 >Well, if you cannot put a Bacula client on the machine,
719 >then it is a big problem. If you know of some software
720 >that can do what you want, let me know, because I
721 >really just don't know how to do it -- at least not
727 We have been able to get Amanda to use the HSM as a storage
728 device. Someone here wrote a driver for Amanda. BUT, Amanda doesn't
729 handle Windows systems very well (or at all without Samba). So I am
730 looking for a backup system that has a Windows client. I really like the
731 Windows integration of Bacula.
733 From the command line, its rather trivial to move the data around. We use
736 tar cf - ./files | gzip -c | rsh hsm dd of=path/file.tgz
738 or if you use GNU tar:
740 tar czf hsm:path/file.tgz ./files
742 One idea for you to consider; Sendmail offers pipes in the aliases file;
743 (mailpipe: "|/usr/bin/vacation root") and Perl supports pipes in the
744 "open" statement (open FILE, "|/bin/nroff -man";) Could you could make a
745 pipe available, as a storage device? Then we could use any command that
746 handles stdin as a storage destination.
753 #Password is not used in rsh, but might be used in ftp.
754 Device = "| gzip -c | rsh hsm dd of=path/file.tgz"
761 Password = "foobar&-"
762 Device = "| ncftpput -c hsm /path/file.bacula"
766 >If you have some local storage available, you could
767 >use Bacula to backup to disk volumes, then use some
768 >other software (ftp, scp) to move them to the HSM
769 >machine. However, this is a bit kludgy.
772 It is, but maybe worth a try. Is there some function in Bacula to put
773 variables in filenames? i.e. backup.2003-01-15.root
780 w.a.sellers@larc.nasa.gov
782 ==============================================
783 The Project for the above
785 I finally realized that this is not at all
786 the same as reader/writer programs or plugins,
787 which are alternate ways of accessing the
788 files to be backed up. Rather, it is an alternate
789 form of storage device, and I have always planned
790 that Bacula should be able to handle all sorts
793 So, I propose the following phases:
795 1. OK from you to invest some time in testing
796 this as I implement it (requires that you
797 know how to download from the SourceForge
798 cvs -- which I imagine is a piece of cake
801 2. Dumb implementation by allowing a device to
802 be a fifo for write only.
803 Reason: easy to implement, proof of concept.
805 3. Try reading from fifo but with fixed block
807 Reason: proof of concept, easy to implement.
809 4. Extend reading from fifo (restores) to handle
811 Reason: requires some delicate low level coding
812 which could destabilize all of Bacula.
814 5. Implementation of above but to a program. E.g.
815 Device = "|program" (not full pipeline).
816 Reason: routines already exist, and program can
817 be a shell script which contains anything.
819 6. Add full pipeline as a possibility. E.g.
820 Device = "| gzip -c | rsh hsm dd of=path/file.tgz"
821 Reason: needs additional coding to implement full
822 pipeline (must fire off either a shell or all
823 programs and connect their pipes).
825 There are a good number of details in each step
826 that I have left out, but I will specify them at
827 every stage, and there may be a few changes as things
828 evolve. I expect that to get to stage 5 will take a
829 few weeks, and at that point, you will have
830 everything you need (just inside a script).
831 Stage 6 will probably take longer, but if this
832 project pleases you, what we do for 5 should
833 be adequate for some time.
837 =============================================
839 Done: (see kernsdone for more)
840 - Look into Pruning/purging problems or why there seem to
841 be so many files listed each night.
842 - Fix cancel in find_one -- need jcr.
843 - Cancel does not work for restore in FD.
844 - Write SetJobStatus() function so cancel status not lost.
845 - Add include list to end of chain in findlib
846 - Zap sd_auth_key after use
847 - Add Bar code reading capabilities (new mtx-changer)
848 - Figure out some way to automatically backup all local partitions
849 - Make hash table for linked files in findlib/find_one.c:161
851 - Rewrite find_one.c to use only pool_memory instead of
852 alloca and malloc (probably not necessary).
853 - Make sure btraceback goes into /sbin not sysconf directory.
854 - InitVerify is getting pruned and it shouldn't (document it)
855 - Make 1.28c release ??? NO do 1.29 directly
856 - Set timeout on opening fifo for save or restore (findlib)
857 - Document FIFO storage device.
858 - Document fifo and | and <
861 - Get correct error status from run_program or open_bpipe().
862 - Restrict permissions on File Volumes (now 0640).
863 - Umasked 022 daemons
864 - Fix restore of hard linked file.
865 - Figure out how to allow multiple simultaneous file Volumes on a single device.
866 - Implement multiple simultaneous file Volumes on a single device.
867 - Cleanup db_update_media and db_update_pool
868 - Flush all the daemon messages at the end of every job.
869 - Change stat1= fgets()!=NULL to stat1=fgest()==NULL; in
870 run_program -- bpipe.c
871 - Apparently cancel does not work for jobs waiting to be
873 - Implement TCP/IP connection for MySQL
874 - Pull a canceled job from the Scheduling queue.
875 - Implement max_file_size in block.c (already done, just tweaked).
876 - Look at purge jobs volume (at least document it, and see if it is
878 - Add list volumes does all pools. list volumes pool=xxx now works.
879 - Add pool= to "list media" in ua_output.c
880 - Strip trailing slashes from Include directory names in the FD.
881 - Fix Error: bnet.c:408 gethostbyname() for lpmatou failed:
882 ERR=Operation not permited loop.
883 - Add code if there is no mtio.h (cannot do -- too many ioctl defines needed)
884 - Produce better error messages in when error/eof writing block.
885 - Cancelling of a queued job does NOT work!!!!!!
887 rufus-dir: Volume used once. Marking Volume "File0003" as Used.
888 rufus-sd: Recycled volume File0003 on device /home/kern/bacula/working, all previous data lost.
889 rufus-dir: Volume used once. Marking Volume "File0003" as Used.
890 - Ability to backup to a file then later transfer to a tape -- Migration.
891 Migration based on MaxJobs(MinJobs),MaxVols(MinVols),AgeJobs,MaxBytes(MinBytes)
892 (i.e. HighwaterMark, LowwaterMark).
893 - Eugeny Fisher <efischer@vip-rus.com> wants to cycle through a
894 set of volumes recycling the oldest volume when it is needed.
895 - gethostbyname failure in bnet_connect() continues
896 generating errors -- should stop.
897 - Add chflags() code for FreeBSD file flags
898 - Bevan Anderson suggests having a run queue for each device
899 so that multiple simultaneous jobs can run but each writing
900 to a different Volume.
901 - Look at handling <> in smtp doesn't work with exim.
902 - Need to specify MaximumConcurrentJobs in the Job resource.
903 - ***test GetFileAttributexEx, and remove MessageBox at 335 of winservice.cpp ****
904 - Implement finer multiprocessing options.
905 - Implement | and < in Exclude statements.
906 - Figure out some way to specify a retention period for files
907 that no longer exist on the machine -- so that we maintain
908 say backups for 30 days, but if the file is deleted, we maintain
909 the last copy for 1 year. -- answer Volume retention.
910 - Make non-zero status from RunJobBefore/After error the job.
911 - Need define of int_least16_t in sha1.h for SuSE.
912 - Implement bar code reader for autochangers
913 - Document new MaximumConcurrentJob records (Job, Client, Storage)
914 - Write up how to use/manage disk Volume Storage. ******
915 - Remove kern and kelvin from mysql_grant...
916 - Install grant_mysql...
917 - Strip trailing / from Include