9 - Document cleaning up the spool files:
10 db, pid, state, bsr, mail, conmsg, spool
11 - Document the multiple-drive-changer.txt script.
12 - Pruning with Admin job.
13 - Does WildFile match against full name? Doc.
14 - %d and %v only valid on Director, not for ClientRunBefore/After.
19 - Fix re-read of last block to check if job has actually written
20 a block, and check if block was written by a different job
21 (i.e. multiple simultaneous jobs writing).
22 - JobStatus and Termination codes.
23 - Some users claim that they must do two prune commands to get a
24 Volume marked as purged.
25 - Print warning message if LANG environment variable does not specify
27 === Migration from David ===
31 Name = "<poolname>-migrate"
35 Migration Selection Type = LowestUtil | OldestVol | PoolOccupancy |
36 Client | PoolResidence | Volume | JobName | SQLquery
37 Migration Selection Pattern = "regexp"
38 Next Pool = <override>
41 There should be no need for a Level (migration is always Full, since you
42 don't calculate differential/incremental differences for migration),
43 Storage should be determined by the volume types in the pool, and Client
44 is really a selection issue. Migration should always occur to the
45 NextPool defined in the pool definition. If no nextpool is defined, the
46 job should end with a reason of "no place to go". If Next Pool statement
47 is present, we override the check in the pool definition and use the
50 Here's how I'd define Migration Selection Types:
52 LowestUtil -- Identify the volume in the pool with the least data on it
53 and empty it. No Migration Selection Pattern required.
55 OldestVol -- Identify the LRU volume with data written, and empty it. No
56 Migration Selection Pattern required.
58 PoolOccupancy -- if pool occupancy exceeds <highmig>, migrate volumes
59 (starting with most full volumes) until pool occupancy drops below
60 <lowmig>. Pool highmig and lowmig values are in pool definition, no
61 Migration Selection Pattern required.
63 Client -- Migrate data from selected client only. Migration Selection
64 Pattern regexp provides pattern to select client names, eg ^FS00* makes
65 all client names starting with FS00 eligible for migration.
67 PoolResidence -- Migrate data sitting in pool for longer than
68 PoolResidence value in pool definition. Migration Selection Pattern
69 optional; if specified, override value in pool definition (value in
72 Volume -- Migrate all data on specified volumes. Migration Selection
73 Pattern regexp provides selection criteria for volumes to be migrated.
74 Volumes must exist in pool to be eligible for migration.
76 Jobname -- Migration all jobs matching name. Migration Selection Pattern
77 regexp provides pattern to select jobnames existing in pool.
79 SQLQuery -- Migrate all jobuids returned by the supplied SQL query.
80 Migration Selection Pattern contains SQL query to execute; should return
81 a list of 1 or more jobuids to migrate.
83 [ possibly a Python event -- kes ]
85 - Network error on Win32 should set Win32 error code.
86 - What happens when you rename a Disk Volume?
87 - Job retention period in a Pool (and hence Volume). The job would
89 - Detect resource deadlock in Migrate when same job wants to read
90 and write the same device.
91 - Make hardlink code at line 240 of find_one.c use binary search.
92 - Queue warning/error messages during restore so that they
93 are reported at the end of the report rather than being
94 hidden in the file listing ...
95 - Look at -D_FORTIFY_SOURCE=2
96 - Add Win32 FileSet definition somewhere
97 - Look at fixing restore status stats in SD.
98 - Make selection of Database used in restore correspond to
100 - Implement a mode that says when a hard read error is
101 encountered, read many times (as it currently does), and if the
102 block cannot be read, skip to the next block, and try again. If
103 that fails, skip to the next file and try again, ...
105 create table LevelType (LevelType binary(1), LevelTypeLong tinyblob);
106 insert into LevelType (LevelType,LevelTypeLong) values
110 - Add ACL to restore only to original location.
111 - Add a recursive mark command (rmark) to restore.
112 - "Minimum Job Interval = nnn" sets minimum interval between Jobs
113 of the same level and does not permit multiple simultaneous
114 running of that Job (i.e. lets any previous invocation finish
115 before doing Interval testing).
116 - Look at simplifying File exclusions.
117 - New directive "Delete purged Volumes"
118 - new pool XXX with ScratchPoolId = MyScratchPool's PoolId and
119 let it fill itself, and RecyclePoolId = XXX's PoolId so I can
120 see if it become stable and I just have to supervise
122 - If I want to remove this pool, I set RecyclePoolId = MyScratchPool's
123 PoolId, and when it is empty remove it.
124 - Figure out how to recycle Scratch volumes back to the Scratch Pool.
126 - Allow Check Labels to be used with Bacula labels.
127 - "Resuming" a failed backup (lost line for example) by using the
128 failed backup as a sort of "base" job.
130 - Email to the user when the tape is about to need changing x
131 days before it needs changing.
132 - Command to show next tape that will be used for a job even
133 if the job is not scheduled.
134 - From: Arunav Mandal <amandal@trolltech.com>
135 1. When jobs are running and bacula for some reason crashes or if I do a
136 restart it remembers and jobs it was running before it crashed or restarted
137 as of now I loose all jobs if I restart it.
139 2. When spooling and in the midway if client is disconnected for instance a
140 laptop bacula completely discard the spool. It will be nice if it can write
141 that spool to tape so there will be some backups for that client if not all.
143 3. We have around 150 clients machines it will be nice to have a option to
144 upgrade all the client machines bacula version automatically.
146 4. Atleast one connection should be reserved for the bconsole so at heavy load
147 I should connect to the director via bconsole which at sometimes I can't
149 5. Another most important feature that is missing, say at 10am I manually
150 started backup of client abc and it was a full backup since client abc has
151 no backup history and at 10.30am bacula again automatically started backup of
152 client abc as that was in the schedule. So now we have 2 multiple Full
153 backups of the same client and if we again try to start a full backup of
154 client backup abc bacula won't complain. That should be fixed.
156 - Fix bpipe.c so that it does not modify results pointer.
157 ***FIXME*** calling sequence should be changed.
158 - For Windows disaster recovery see http://unattended.sf.net/
159 - regardless of the retention period, Bacula will not prune the
160 last Full, Diff, or Inc File data until a month after the
161 retention period for the last Full backup that was done.
162 - update volume=xxx --- add status=Full
163 - Remove old spool files on startup.
164 - Exclude SD spool/working directory.
165 - Refuse to prune last valid Full backup. Same goes for Catalog.
167 - Make a callback when Rerun failed levels is called.
168 - Give Python program access to Scheduled jobs.
169 - Add setting Volume State via Python.
170 - Python script to save with Python, not save, save with Bacula.
171 - Python script to do backup.
173 - Change the Priority, Client, Storage, JobStatus (error)
174 at the start of a job.
175 - Why is SpoolDirectory = /home/bacula/spool; not reported
176 as an error when writing a DVD?
177 - Make bootstrap file handle multiple MediaTypes (SD)
178 - Remove all old Device resource code in Dir and code to pass it
179 back in SD -- better, rework it to pass back device statistics.
180 - Check locking of resources -- be sure to lock devices where previously
181 resources were locked.
182 - The last part is left in the spool dir.
185 - In restore don't compare byte count on a raw device -- directory
186 entry does not contain bytes.
187 - To mark files as deleted, run essentially a Verify to disk, and
188 when a file is found missing (MarkId != JobId), then create
189 a new File record with FileIndex == -1. This could be done
190 by the FD at the same time as the backup.
194 MA = (last_MA * 3 + rate) / 4
195 rate = (bytes - last_bytes) / (runtime - last_runtime)
196 - Max Vols limit in Pool off by one?
197 - Implement Files/Bytes,... stats for restore job.
198 - Implement Total Bytes Written, ... for restore job.
199 - Despool attributes simultaneously with data in a separate
200 thread, rejoined at end of data spooling.
201 - 7. Implement new Console commands to allow offlining/reserving drives,
202 and possibly manipulating the autochanger (much asked for).
203 - Add start/end date editing in messages (%t %T, %e?) ...
204 - Add ClientDefs similar to JobDefs.
205 - Print more info when bextract -p accepts a bad block.
206 - Fix FD JobType to be set before RunBeforeJob in FD.
207 - Look at adding full Volume and Pool information to a Volume
208 label so that bscan can get *all* the info.
209 - If the user puts "Purge Oldest Volume = yes" or "Recycle Oldest Volume = yes"
210 and there is only one volume in the pool, refuse to do it -- otherwise
211 he fills the Volume, then immediately starts reusing it.
212 - Implement copies and stripes.
213 - Add history file to console.
214 - Each file on tape creates a JobMedia record. Peter has 4 million
215 files spread over 10000 tape files and four tapes. A restore takes
216 16 hours to build the restore list.
217 - Add and option to check if the file size changed during backup.
218 - Make sure SD deletes spool files on error exit.
219 - Delete old spool files when SD starts.
220 - When labeling tapes, if you enter 000026, Bacula uses
221 the tape index rather than the Volume name 000026.
222 - Add offline tape command to Bacula console.
224 Enter MediaId or Volume name: 32
225 Enter new Volume name: DLT-20Dec04
226 Automatically selected Pool: Default
227 Connecting to Storage daemon DLTDrive at 192.168.68.104:9103 ...
228 Sending relabel command from "DLT-28Jun03" to "DLT-20Dec04" ...
229 block.c:552 Write error at 0:0 on device /dev/nst0. ERR=Bad file descriptor.
230 Error writing final EOF to tape. This tape may not be readable.
231 dev.c:1207 ioctl MTWEOF error on /dev/nst0. ERR=Permission denied.
232 askdir.c:219 NULL Volume name. This shouldn't happen!!!
233 3912 Failed to label Volume: ERR=dev.c:1207 ioctl MTWEOF error on /dev/nst0. ERR=Permission denied.
234 Label command failed for Volume DLT-20Dec04.
235 Do not forget to mount the drive!!!
236 - Bug: if a job is manually scheduled to run later, it does not appear
237 in any status report and cannot be cancelled.
239 ==== Keeping track of deleted files ====
240 My "trick" for keeping track of deletions is the following.
241 Assuming the user turns on this option, after all the files
242 have been backed up, but before the job has terminated, the
243 FD will make a pass through all the files and send their
244 names to the DIR (*exactly* the same as what a Verify job
245 currently does). This will probably be done at the same
246 time the files are being sent to the SD avoiding a second
247 pass. The DIR will then compare that to what is stored in
248 the catalog. Any files in the catalog but not in what the
249 FD sent will receive a catalog File entry that indicates
250 that at that point in time the file was deleted.
252 During a restore, any file initially picked up by some
253 backup (Full, ...) then subsequently having a File entry
254 marked "delete" will be removed from the tree, so will not
255 be restored. If a file with the same name is later OK it
256 will be inserted in the tree -- this already happens. All
257 will be consistent except for possible changes during the
260 Since I'm on the subject, some of you may be wondering what
261 the utility of the in memory tree is if you are going to
262 restore everything (at least it comes up from time to time
263 on the list). Well, it is still *very* useful because it
264 allows only the last item found for a particular filename
265 (full path) to be entered into the tree, and thus if a file
266 is backed up 10 times, only the last copy will be restored.
267 I recently (last Friday) restored a complete directory, and
268 the Full and all the Differential and Incremental backups
269 spanned 3 Volumes. The first Volume was not even mounted
270 because all the files had been updated and hence backed up
271 since the Full backup was made. In this case, the tree
272 saved me a *lot* of time.
274 Make sure this information is stored on the tape too so
275 that it can be restored directly from the tape.
277 Comments from Martin Simmons (I think they are all covered):
278 Ok, that should cover the basics. There are few issues though:
280 - Restore will depend on the catalog. I think it is better to include the
281 extra data in the backup as well, so it can be seen by bscan and bextract.
283 - I'm not sure if it will preserve multiple hard links to the same inode. Or
284 maybe adding or removing links will cause the data to be dumped again?
286 - I'm not sure if it will handle renamed directories. Possibly it will work
287 by dumping the whole tree under a renamed directory?
289 - It remains to be seen how the backup performance of the DIR's will be
290 affected when comparing the catalog for a large filesystem.
294 How about introducing a Type = MgmtPolicy job type? That job type would
295 be responsible for scanning the Bacula environment looking for specific
296 conditions, and submitting the appropriate jobs for implementing said
300 Name = "Migration-Policy"
302 Policy Selection Job Type = Migrate
303 Scope = "<keyword> <operator> <regexp>"
304 Threshold = "<keyword> <operator> <regexp>"
305 Job Template = <template-name>
308 Where <keyword> is any legal job keyword, <operator> is a comparison
309 operator (=,<,>,!=, logical operators AND/OR/NOT) and <regexp> is a
310 appropriate regexp. I could see an argument for Scope and Threshold
311 being SQL queries if we want to support full flexibility. The
312 Migration-Policy job would then get scheduled as frequently as a site
313 felt necessary (suggested default: every 15 minutes).
318 Name = "Migration-Policy"
320 Policy Selection Job Type = Migration
322 Threshold = "Migration Selection Type = LowestUtil"
323 Job Template = "MigrationTemplate"
326 would select all pools for examination and generate a job based on
327 MigrationTemplate to automatically select the volume with the lowest
328 usage and migrate it's contents to the nextpool defined for that pool.
330 This policy abstraction would be really handy for adjusting the behavior
331 of Bacula according to site-selectable criteria (one thing that pops
332 into mind is Amanda's ability to automatically adjust backup levels
333 depending on various criteria).
339 - Add Pool/Storage override regression test.
340 - Add delete JobId to regression.
341 - Add a regression test for dbcheck.
342 - New test to add bscan to four-concurrent-jobs regression,
343 i.e. after the four-concurrent jobs zap the
344 database as is done in the bscan-test, then use bscan to
345 restore the database, do a restore and compare with the
347 - Add restore of specific JobId to regression (item 3
348 on the restore prompt)
349 - Add IPv6 to regression
350 - Add database test to regression. Test each function like delete,
353 - AntiVir can slow down backups on Win32 systems.
354 - Win32 systems with FAT32 can be much slower than NTFS for
355 more than 1000 files per directory.
359 - A HOLD command to stop all jobs from starting.
360 - A PAUSE command to pause all running jobs ==> release the
362 - Media Type = LTO,LTO-2,LTO-3
363 Media Type Read = LTO,LTO2,LTO3
364 Media Type Write = LTO2, LTO3
366 === From Carsten Menke <bootsy52@gmx.net>
368 Following is a list of what I think in the situations where I'm faced with,
369 could be a usefull enhancement to bacula, which I'm certain other users will
370 benefit from as well.
372 1. NextJob/NextJobs Directive within a Job Resource in the form of
373 NextJobs = job1,job2.
376 I currently solved the problem with running multiple jobs each after each
377 by setting the Max Wait Time for a job to 8 hours, and give
378 the jobs different Priorities. However, there scenarios where
379 1 Job is directly depending on another job, so if the former job fails,
380 the job after it needn't to be run
381 while maybe other jobs should run despite of that
384 A Backup Job and a Verify job, if the backup job fails there is no need to run
385 the verify job, as the backup job already failed. However, one may like
386 to backup the Catalog to disk despite of that the main backup job failed.
389 I see that this is related to the Event Handlers which are on the ToDo
390 list, also it is maybe a good idea to check for the return value and
391 execute different actions based on the return value
394 3. offline capability to bconsole
397 Currently I use a script which I execute within the last Job via the
398 RunAfterJob Directive, to release and eject the tape.
399 So I have to call bconsole "release=Storage-Name" and afterwards
400 mt -f /dev/nst0 eject to get the tape out.
402 If I have multiple Storage Devices, than these may not be /dev/nst0 and
403 I have to modify the script or call it with parameters etc.
404 This would actually not be needed, as everything is already defined
405 in bacula-sd.conf and if I can invoke bconsole with the
406 storage name via $1 in the script than I'm done and information is
409 4. %s for Storage Name added to the chars being substituted in "RunAfterJob"
413 For the reason mentioned in 3. to have the ability to call a
414 script with /scripts/foobar %s and in the script use $1
415 to pass the Storage Name to bconsole
417 5. Setting Volume State within a Job Resource
420 Instead of using "Maximum Volume Jobs" in the Pool Resource,
421 I would have the possibilty to define
422 in a Job Resource that after this certain job is run, the Volume State
423 should be set to "Volume State = Used", this give more flexibility (IMHO).
425 6. Localization of Bacula Messages
428 Unfortunatley many,many people I work with don't speak english very well.
429 So if at least the Reporting messages would be localized then they
430 would understand that they have to change the tape,etc. etc.
432 I volunteer to do the german translations, and if I can convince my wife also
433 french and Morre (western african language).
435 7. OK, this is evil, probably bound to security risks and maybe not possible
436 due to the design of bacula.
438 Implementation of Backtics ( `command` ) for shell comand execution to
439 the "Label Format" Directive.
443 Currently I have defined BACULA_DAY_OF_WEEK="day1|day2..." resulting in
444 Label Format = "HolyBackup-${BACULA_DAY_OF_WEEK[${WeekDay}]}". If I could
445 use backticks than I could use "Label Format = HolyBackup-`date +%A` to have
446 the localized name for the day of the week appended to the
447 format string. Then I have the tape labeled automatically with weekday
448 name in the correct language.
450 - Yes, that is surely the case. I probably should turn those into Warning
451 errors. In addition, you just made me think that it might not be bad to
452 add an option to check the file size after backing up the file and
453 report if it changes. This would be done as an option because it would
456 Kern, good idea. If you do do that, mention in the output: file
457 shrunk, or file expanded, just to make it obvious to the user
458 (without having to the refer to file size), just how the file size
461 Would this option be for all file, or just one file? Or a fileset?
462 - Make output from status use html table tags for nicely
463 presenting in a browser.
464 - Can one write tapes faster with 8192 byte block sizes?
465 - Document security problems with the same password for everyone in
466 rpm and Win32 releases.
467 - Browse generations of files.
468 - I've seen an error when my catalog's File table fills up. I
469 then have to recreate the File table with a larger maximum row
470 size. Relevant information is at
471 http://dev.mysql.com/doc/mysql/en/Full_table.html ; I think the
472 "Installing and Configuring MySQL" chapter should talk a bit
473 about this potential problem, and recommend a solution.
474 - For Solaris must use POSIX awk.
475 - Want speed of writing to tape while despooling.
476 - Supported autochanger:
484 Wangtek 6525ES (SCSI-1 QIC drive, 525MB), under Linux 2.4.something,
485 bacula 1.36.0/1 works with blocksize 16k INSIDE bacula-sd.conf.
486 - Add regex from http://www.pcre.org to Bacula for Win32.
487 - Use only shell tools no make in CDROM package.
488 - Include within include does it work?
489 - Implement a Pool of type Cleaning?
490 - Implement VolReadTime and VolWriteTime in SD
491 - Modify Backing up Your Database to include a bootstrap file.
492 - Think about making certain database errors fatal.
493 - Look at correcting the time jump in the scheduler for daylight
494 savings time changes.
495 - Add a "real" timer to network connections.
496 - Promote to Full = Time period
497 - Check dates entered by user for correctness (month/day/... ranges)
498 - Compress restore Volume listing by date and first file.
499 - Look at patches/bacula_db.b2z postgresql that loops during restore.
501 - Perhaps add read/write programs and/or plugins to FileSets.
502 - How to handle backing up portables ...
503 - Add some sort of guaranteed Interval for upgrading jobs.
504 - Can we write the state file after every job terminates? On Win32
505 the system crashes and the state file is not updated.
508 Documentation to do: (any release a little bit at a time)
509 - Doc to do unmount before removing magazine.
510 - Alternative to static linking "ldd prog" save all binaries listed,
511 restore them and point LD_LIBRARY_PATH to them.
512 - Document add "</dev/null >/dev/null 2>&1" to the bacula-fd command line
513 - Document query file format.
514 - Add more documentation for bsr files.
515 - Document problems with Verify and pruning.
516 - Document how to use multiple databases.
517 - VXA drives have a "cleaning required"
518 indicator, but Exabyte recommends preventive cleaning after every 75
521 In this context, it should be noted that Exabyte has a command-line
522 vxatool utility available for free download. (The current version is
523 vxatool-3.72.) It can get diagnostic info, read, write and erase tapes,
524 test the drive, unload tapes, change drive settings, flash new firmware,
526 Of particular interest in this context is that vxatool <device> -i will
527 report, among other details, the time since last cleaning in tape motion
528 minutes. This information can be retrieved (and settings changed, for
529 that matter) through the generic-SCSI device even when Bacula has the
530 regular tape device locked. (Needless to say, I don't recommend
531 changing tape settings while a job is running.)
532 - Lookup HP cleaning recommendations.
533 - Lookup HP tape replacement recommendations (see trouble shooting autochanger)
534 - Document doing table repair
537 ===================================
538 - Add macro expansions in JobDefs.
539 Run Before Job = "SomeFile %{Level} %{Client}"
540 Write Bootstrap="/some/dir/%{JobName}_%{Client}.bsr"
541 - Use non-blocking network I/O but if no data is available, use
543 - Use gather write() for network I/O.
544 - Autorestart on crash.
545 - Add bandwidth limiting.
546 - Add acks every once and a while from the SD to keep
547 the line from timing out.
548 - When an error in input occurs and conio beeps, you can back
549 up through the prompt.
550 - Detect fixed tape block mode during positioning by looking at
551 block numbers in btape "test". Possibly adjust in Bacula.
552 - Fix list volumes to output volume retention in some other
553 units, perhaps via a directive.
554 - If opening a tape in read/write mode fails attempt to open
555 it in read-only mode, and mark the tape for read only.
556 - Allow Simultaneous Priorities = yes => run up to Max concurrent jobs even
557 with multiple priorities.
558 - If you use restore replace=never, the directory attributes for
559 non-existent directories will not be restored properly.
561 - see lzma401.zip in others directory for new compression
563 - Minimal autochanger handling in Bacula and in btape.
564 - Look into how tar does not save sockets and the possiblity of
565 not saving them in Bacula (Martin Simmons reported this).
566 - Fix restore jobs so that multiple jobs can run if they
567 are not using the same tape(s).
568 - Allow the user to select JobType for manual pruning/purging.
569 - bscan does not put first of two volumes back with all info in
571 - Implement the FreeBSD nodump flag in chflags.
572 - Figure out how to make named console messages go only to that
573 console and to the non-restricted console (new console class?).
574 - Make restricted console prompt for password if *ask* is set or
575 perhaps if password is undefined.
576 - Implement "from ISO-date/time every x hours/days/weeks/months" in
579 ==== from Marc Schoechlin
580 - the help-command should be more verbose
581 (it should explain the paramters of the different
583 -> its time-comsuming to consult the manual anytime
584 you need a special parameter
585 -> maybe its more easy to maintain this, if the
586 descriptions of that commands are outsourced to
588 - the cd-command should allow complete paths
589 i.e. cd /foo/bar/foo/bar
590 -> if a customer mails me the path to a certain file,
591 its faster to enter the specified directory
592 - if the password is not configured in bconsole.conf
593 you should be asked for it.
594 -> sometimes you like to do restore on a customer-machine
595 which shouldnt know the password for bacula.
596 -> adding the password to the file favours admins
597 to forget to remove the password after usage
599 the protection of that file is less important
600 - long-listed-output of commands should be scrollable
601 like the unix more/less-command does
602 -> if someone runs 200 and more machines, the lists could
603 be a little long and complex
604 - command-output should be shown column by column
605 to reduce scrolling and to increase clarity
607 - lsmark should list the selected files with full
609 - wildcards for selecting and file and directories would be nice
610 - any actions should be interuptable with STRG+C
611 - command-expansion would be pretty cool
613 - When the replace Never option is set, new directory permissions
614 are not restored. See bug 213. To fix this requires creating a
615 list of newly restored directories so that those directory
616 permissions *can* be restored.
617 - Compaction of Disk space by "migrating" Volumes that have pruned
618 Jobs (what criteria? size, #jobs, time).
619 - Add prune all command
620 - Document fact that purge can destroy a part of a restore by purging
621 one volume while others remain valid -- perhaps mark Jobs.
622 - Add multiple-media-types.txt
623 - look at mxt-changer.html
624 - Make ? do a help command (no return needed).
625 - Implement restore directory.
626 - Document streams and how to implement them.
627 - Try not to re-backup a file if a new hard link is added.
628 - Add feature to backup hard links only, but not the data.
629 - Fix stream handling to be simpler.
630 - Add Priority and Bootstrap to Run a Job.
631 - Eliminate Restore "Run Restore Job" prompt by allowing new "run command
633 - Remove View FileSet button from Run a Job dialog.
634 - Handle prompt for restore job at end of Restore command.
635 - Add display of total selected files to Restore window.
636 - Add tree pane to left of window.
637 - Add progress meter.
638 - Max wait time or max run time causes seg fault -- see runtime-bug.txt
639 - Document writing to a CD/DVD with Bacula.
640 - Add a "base" package to the window installer for pthreadsVCE.dll
641 which is needed by all packages.
642 - Add message to user to check for fixed block size when the forward
643 space test fails in btape.
644 - When unmarking a directory check if all files below are unmarked and
645 then remove the + flag -- in the restore tree.
646 - Possibly implement: Action = Unmount Device="TapeDrive1" in Admin jobs.
647 - Setup lrrd graphs: (http://www.linpro.no/projects/lrrd/) Mike Acar.
648 - Revisit the question of multiple Volumes (disk) on a single device.
649 - Add a block copy option to bcopy.
650 - Investigate adding Mac Resource Forks.
651 - Finish work on Gnome restore GUI.
652 - Fix "llist jobid=xx" where no fileset or client exists.
653 - For each job type (Admin, Restore, ...) require only the really necessary
654 fields.- Pass Director resource name as an option to the Console.
655 - Add a "batch" mode to the Console (no unsolicited queries, ...).
656 - Add a .list all files in the restore tree (probably also a list all files)
657 Do both a long and short form.
658 - Allow browsing the catalog to see all versions of a file (with
659 stat data on each file).
660 - Restore attributes of directory if replace=never set but directory
662 - Use SHA1 on authentication if possible.
663 - See comtest-xxx.zip for Windows code to talk to USB.
664 - Add John's appended files:
665 Appended = { /files/server/logs/http/*log }
666 and such files would be treated as follows.On a FULL backup, they would
667 be backed up like any other file.On an INCREMENTAL backup, where a
668 previous INCREMENTAL or FULL was already in thecatalogue and the length
669 of the file wasgreater than the length of the last backup, only thedata
670 added since the last backup will be dumped.On an INCREMENTAL backup, if
671 the length of the file is less than thelength of the file with the same
672 name last backed up, the completefile is dumped.On Windows systems, with
673 creation date of files, we can be evensmarter about this and not count
674 entirely upon the length.On a restore, the full and all incrementals
675 since it will beapplied in sequence to restore the file.
676 - Check new HAVE_WIN32 open bits.
677 - Check if the tape has moved before writing.
678 - Handling removable disks -- see below:
679 - Keep track of tape use time, and report when cleaning is necessary.
680 - Add FromClient and ToClient keywords on restore command (or
681 BackupClient RestoreClient).
682 - Implement a JobSet, which groups any number of jobs. If the
683 JobSet is started, all the jobs are started together.
684 Allow Pool, Level, and Schedule overrides.
685 - Enhance cancel to timeout BSOCK packets after a specific delay.
686 - Do scheduling by UTC using gmtime_r() in run_conf, scheduler, and
687 ua_status.!!! Thanks to Alan Brown for this tip.
688 - Look at updating Volume Jobs so that Max Volume Jobs = 1 will work
689 correctly for multiple simultaneous jobs.
690 - Correct code so that FileSet MD5 is calculated for < and | filename
692 - Implement the Media record flag that indicates that the Volume does disk
694 - Implement VolAddr, which is used when Volume is addressed like a disk,
695 and form it from VolFile and VolBlock.
696 - Make multiple restore jobs for multiple media types specifying
697 the proper storage type.
698 - Fix fast block rejection (stored/read_record.c:118). It passes a null
699 pointer (rec) to try_repositioning().
700 - Look at extracting Win data from BackupRead.
701 - Implement RestoreJobRetention? Maybe better "JobRetention" in a Job,
702 which would take precidence over the Catalog "JobRetention".
703 - Implement Label Format in Add and Label console commands.
704 - Possibly up network buffers to 65K. Put on variable.
705 - Put email tape request delays on one or more variables. User wants
706 to cancel the job after a certain time interval. Maximum Mount Wait?
707 - Job, Client, Device, Pool, or Volume?
708 Is it possible to make this a directive which is *optional* in multiple
709 resources, like Level? If so, I think I'd make it an optional directive
710 in Job, Client, and Pool, with precedence such that Job overrides Client
711 which in turn overrides Pool.
713 - New Storage specifications:
714 - Want to write to multiple storage devices simultaneously
715 - Want to write to multiple storage devices sequentially (in one job)
716 - Want to read/write simultaneously
717 - Key is MediaType -- it must match
719 Passed to SD as a sort of BSR record called Storage Specification
723 MediaType -> Next MediaType
725 Device -> Next Device
727 Allow multiple Storage specifications
735 Allow Multiple Pool specifications (note, Pool currently
737 Allow Multiple MediaType specifications in Dir conf
738 Allow Multiple Device specifications in Dir conf
739 Perhaps keep this in a single SSR
740 Tie a Volume to a specific device by using a MediaType that
741 is contained in only one device.
742 In SD allow Device to have Multiple MediaTypes
744 - Ideas from Jerry Scharf:
745 First let's point out some big pluses that bacula has for this
747 more importantly it's active. Thank you so much for that
748 even more important, it's not flaky
749 it has an open access catalog, opening many possibilities
750 it's pushing toward heterogeneous systems capability
752 Macintosh file client
753 macs are an interesting niche, but I fear a server is a rathole
754 working bare iron recovery for windows
755 the option for inc/diff backups not reset on fileset revision
756 a) use both change and inode update time against base time
757 b) do the full catalog check (expensive but accurate)
758 sizing guide (how much system is needed to back up N systems/files)
759 consultants on using bacula in building a disaster recovery system
761 or how to get at fancy things that one could do with bacula
762 logwatch code for bacula logs (or similar)
763 linux distro inclusion of bacula (brings good and bad, but necessary)
764 win2k/XP server capability (icky but you asked)
765 support for Oracle database ??
767 - Look at adding SQL server and Exchange support for Windows.
768 - Make dev->file and dev->block_num signed integers so that -1 can
769 be an invalid value which happens with BSR.
770 - Create VolAddr for disk files in place of VolFile and VolBlock. This
771 is needed to properly specify ranges.
772 - Add progress of files/bytes to SD and FD.
773 - Print warning message if FileId > 4 billion
774 - do a "messages" before the first prompt in Console
775 - Client does not show busy during Estimate command.
776 - Implement Console mtx commands.
777 - Implement a Mount Command and an Unmount Command where
778 the users could specify a system command to be performed
779 to do the mount, after which Bacula could attempt to
780 read the device. This is for Removeable media such as a CDROM.
781 - Most likely, this mount command would be invoked explicitly
782 by the user using the current Console "mount" and "unmount"
783 commands -- the Storage Daemon would do the right thing
784 depending on the exact nature of the device.
785 - As with tape drives, when Bacula wanted a new removable
786 disk mounted, it would unmount the old one, and send a message
787 to the user, who would then use "mount" as described above
788 once he had actually inserted the disk.
789 - Implement dump/print label to UA
790 - Spool to disk only when the tape is full, then when a tape is hung move
792 - bextract is sending everything to the log file ****FIXME****
793 - Allow multiple Storage specifications (or multiple names on
794 a single Storage specification) in the Job record. Thus a job
795 can be backed up to a number of storage devices.
796 - Implement some way for the File daemon to contact the Director
797 to start a job or pass its DHCP obtained IP number.
798 - Implement a query tape prompt/replace feature for a console
799 - Copy console @ code to gnome2-console
800 - Make AES the only encryption algorithm see
801 http://csrc.nist.gov/CryptoToolkit/aes/). It's
802 an officially adopted standard, has survived peer
803 review, and provides keys up to 256 bits.
804 - Take a careful look at SetACL http://setacl.sourceforge.net
805 - Make tree walk routines like cd, ls, ... more user friendly
806 by handling spaces better.
807 - Make sure that Bacula rechecks the tape after the 20 min wait.
808 - Set IO_NOWAIT on Bacula TCP/IP packets.
809 - Try doing a raw partition backup and restore by mounting a
812 Yes, it would allow to highly automatic the request for new tapes. If a
813 tape is empty, bacula reads the barcodes (native or simulated), and if
814 an unused tape is found, it runs the label command with all the
815 necessary parameters.
817 By the way can bacula automatically "move" an empty/purged volume say
818 in the "short" pool to the "long" pool if this pool runs out of volume
820 - What to do about "list files job=xxx".
821 - Get and test MySQL 4.0
822 - Look at how fuser works and /proc/PID/fd that is how Nic found the
823 file descriptor leak in Bacula.
824 - Implement WrapCounters in Counters.
825 - Add heartbeat from FD to SD if hb interval expires.
826 - Can we dynamically change FileSets?
827 - If pool specified to label command and Label Format is specified,
828 automatically generate the Volume name.
829 - Why can't SQL do the filename sort for restore?
830 - Add ExhautiveRestoreSearch
831 - Look at the possibility of loading only the necessary
832 data into the restore tree (i.e. do it one directory at a
833 time as the user walks through the tree).
834 - Possibly use the hash code if the user selects all for a restore command.
835 - Fix "restore all" to bypass building the tree.
836 - Prohibit backing up archive device (findlib/find_one.c:128)
837 - Implement Release Device in the Job resource to unmount a drive.
838 - Implement Acquire Device in the Job resource to mount a drive,
839 be sure this works with admin jobs so that the user can get
840 prompted to insert the correct tape. Possibly some way to say to
841 run the job but don't save the files.
842 - Make things like list where a file is saved case independent for
845 - Use autochanger to handle multiple devices.
846 - On Windows with very long path names, it may be impossible to create
847 a file (and thus restore it) because the total length is too long.
848 We must cd into the directory then create the file without the
850 - Implement a Recycle command
851 - Test a second language e.g. french.
852 - Start working on Base jobs.
853 - Implement UnsavedFiles DB record.
854 - From Phil Stracchino:
855 It would probably be a per-client option, and would be called
856 something like, say, "Automatically purge obsoleted jobs". What it
857 would do is, when you successfully complete a Differential backup of a
858 client, it would automatically purge all Incremental backups for that
859 client that are rendered redundant by that Differential. Likewise,
860 when a Full backup on a client completed, it would automatically purge
861 all Differential and Incremental jobs obsoleted by that Full backup.
862 This would let people minimize the number of tapes they're keeping on
863 hand without having to master the art of retention times.
864 - When doing a Backup send all attributes back to the Director, who
865 would then figure out what files have been deleted.
866 - Currently in mount.c:236 the SD simply creates a Volume. It should have
867 explicit permission to do so. It should also mark the tape in error
868 if there is an error.
869 - Cancel waiting for Client connect in SD if FD goes away.
871 - Implement timeout in response() when it should come quickly.
872 - Implement a Slot priority (loaded/not loaded).
873 - Implement "vacation" Incremental only saves.
874 - Implement create "FileSet"?
875 - Add prefixlinks to where or not where absolute links to FD.
876 - Issue message to mount a new tape before the rewind.
877 - Simplified client job initiation for portables.
878 - If SD cannot open a drive, make it periodically retry.
879 - Add more of the config info to the tape label.
881 - If tape is marked read-only, then try opening it read-only rather than
882 failing, and remember that it cannot be written.
883 - Refine SD waiting output:
884 Device is being positioned
885 > Device is being positioned for append
886 > Device is being positioned to file x
888 - Figure out some way to estimate output size and to avoid splitting
889 a backup across two Volumes -- this could be useful for writing CDROMs
890 where you really prefer not to have it split -- not serious.
891 - Have SD compute MD5 or SHA1 and compare to what FD computes.
892 - Make VolumeToCatalog calculate an MD5 or SHA1 from the
893 actual data on the Volume and compare it.
894 - Implement Bacula plugins -- design API
895 - Make bcopy read through bad tape records.
896 - Program files (i.e. execute a program to read/write files).
897 Pass read date of last backup, size of file last time.
898 - Add Signature type to File DB record.
899 - CD into subdirectory when open()ing files for backup to
900 speed up things. Test with testfind().
901 - Priority job to go to top of list.
902 - Why are save/restore of device different sizes (sparse?) Yup! Fix it.
903 - Implement some way for the Console to dynamically create a job.
904 - Solaris -I on tar for include list
905 - Need a verbose mode in restore, perhaps to bsr.
906 - bscan without -v is too quiet -- perhaps show jobs.
907 - Add code to reject whole blocks if not wanted on restore.
908 - Check if we can increase Bacula FD priorty in Win2000
909 - Make sure the MaxVolFiles is fully implemented in SD
910 - Check if both CatalogFiles and UseCatalog are set to SD.
911 - Possibly add email to Watchdog if drive is unmounted too
912 long and a job is waiting on the drive.
913 - After unmount, if restore job started, ask to mount.
914 - Add UA rc and history files.
915 - put termcap (used by console) in ./configure and
916 allow -with-termcap-dir.
917 - Fix Autoprune for Volumes to respect need for full save.
918 - Compare tape to Client files (attributes, or attributes and data)
919 - Make all database Ids 64 bit.
920 - Allow console commands to detach or run in background.
921 - Fix status delay on storage daemon during rewind.
922 - Add SD message variables to control operator wait time
923 - Maximum Operator Wait
924 - Minimum Message Interval
925 - Maximum Message Interval
926 - Send Operator message when cannot read tape label.
927 - Verify level=Volume (scan only), level=Data (compare of data to file).
928 Verify level=Catalog, level=InitCatalog
930 - Add keyword search to show command in Console.
931 - Events : tape has more than xxx bytes.
932 - Complete code in Bacula Resources -- this will permit
933 reading a new config file at any time.
934 - Handle ctl-c in Console
935 - Implement script driven addition of File daemon to config files.
936 - Think about how to make Bacula work better with File (non-tape) archives.
937 - Write Unix emulator for Windows.
938 - Put memory utilization in Status output of each daemon
939 if full status requested or if some level of debug on.
940 - Make database type selectable by .conf files i.e. at runtime
941 - Set flag for uname -a. Add to Volume label.
942 - Restore files modified after date
943 - SET LD_RUN_PATH=$HOME/mysql/lib/mysql
944 - Remove duplicate fields from jcr (e.g. jcr.level and jcr.jr.Level, ...).
945 - Timout a job or terminate if link goes down, or reopen link and query.
946 - Concept of precious tapes (cannot be reused).
947 - Make bcopy copy with a single tape drive.
948 - Permit changing ownership during restore.
951 > My suggestion: Add a feature on the systray menu-icon menu to request
952 > an immediate backup now. This would be useful for laptop users who may
953 > not be on the network when the regular scheduled backup is run.
955 > My wife's suggestion: Add a setting to the win32 client to allow it to
956 > shut down the machine after backup is complete (after, of course,
957 > displaying a "System will shut down in one minute, click here to cancel"
958 > warning dialog). This would be useful for sites that want user
959 > woorkstations to be shut down overnight to save power.
962 - Autolabel should be specified by DIR instead of SD.
965 - AutoScan (check checksum of tape)
966 - Format command = "format /dev/nst0"
970 - Seek resolution (usually corresponds to buffer size)
971 - EODErrorCode=ENOSPC or code
972 - Partial Read error code
973 - Partial write error code
974 - Nonformatted read error
975 - Nonformatted write error
976 - WriteProtected error
980 - IgnoreCloseErrors=yes
990 - FD sends unsaved file list to Director at end of job (see
992 - File daemon should build list of files skipped, and then
993 at end of save retry and report any errors.
994 - Write a Storage daemon that uses pipes and
995 standard Unix programs to write to the tape.
997 - Need something that monitors the JCR queue and
998 times out jobs by asking the deamons where they are.
999 - Enhance Jmsg code to permit buffering and saving to disk.
1000 - device driver = "xxxx" for drives.
1001 - Verify from Volume
1002 - Ensure that /dev/null works
1003 - Need report class for messages. Perhaps
1004 report resource where report=group of messages
1005 - enhance scan_attrib and rename scan_jobtype, and
1006 fill in code for "since" option
1007 - Director needs a time after which the report status is sent
1008 anyway -- or better yet, a retry time for the job.
1009 - Don't reschedule a job if previous incarnation is still running.
1010 - Some way to automatically backup everything is needed????
1011 - Need a structure for pending actions:
1013 - termination status (part of buffered msgs?)
1015 Read, Write, Clean, Delete
1016 - Login to Bacula; Bacula users with different permissions:
1017 owner, group, user, quotas
1018 - Store info on each file system type (probably in the job header on tape.
1019 This could be the output of df; or perhaps some sort of /etc/mtab record.
1021 ========= ideas ===============
1022 From: "Jerry K. Schieffer" <jerry@skylinetechnology.com>
1023 To: <kern@sibbald.com>
1024 Subject: RE: [Bacula-users] future large programming jobs
1025 Date: Thu, 26 Feb 2004 11:34:54 -0600
1027 I noticed the subject thread and thought I would offer the following
1028 merely as sources of ideas, i.e. something to think about, not even as
1029 strong as a request. In my former life (before retiring) I often
1030 dealt with backups and storage management issues/products as a
1031 developer and as a consultant. I am currently migrating my personal
1032 network from amanda to bacula specifically because of the ability to
1033 cross media boundaries during storing backups.
1034 Are you familiar with the commercial product called ADSM (I think IBM
1035 now sells it under the Tivoli label)? It has a couple of interesting
1036 ideas that may apply to the following topics.
1038 1. Migration: Consider that when you need to restore a system, there
1039 may be pressure to hurry. If all the information for a single client
1040 can eventually end up on the same media (and in chronological order),
1041 the restore is facillitated by not having to search past information
1042 from other clients. ADSM has the concept of "client affinity" that
1043 may be associated with it's storage pools. It seems to me that this
1044 concept (as an optional feature) might fit in your architecture for
1047 ADSM also has the concept of defining one or more storage pools as
1048 "copy pools" (almost mirrors, but only in the sense of contents).
1049 These pools provide the ability to have duplicte data stored both
1050 onsite and offsite. The copy process can be scheduled to be handled
1051 by their storage manager during periods when there is no backup
1052 activity. Again, the migration process might be a place to consider
1053 implementing something like this.
1056 > It strikes me that it would be very nice to be able to do things
1058 > have the Job(s) backing up the machines run, and once they have all
1059 > completed, start a migration job to copy the data from disks Volumes
1061 > a tape library and then to offsite storage. Maybe this can already
1063 > done with some careful scheduling and Job prioritzation; the events
1064 > mechanism described below would probably make it very easy.
1066 This is the goal. In the first step (before events), you simply
1068 the Migration to tape later.
1070 2. Base jobs: In ADSM, each copy of each stored file is tracked in
1071 the database. Once a file (unique by path and metadata such as dates,
1072 size, ownership, etc.) is in a copy pool, no more copies are made. In
1073 other words, when you start ADSM, it begins like your concept of a
1074 base job. After that it is in the "incremental" mode. You can
1075 configure the number of "generations" of files to be retained, plus a
1076 retention date after which even old generations are purged. The
1077 database tracks the contents of media and projects the percentage of
1078 each volume that is valid. When the valid content of a volume drops
1079 below a configured percentage, the valid data are migrated to another
1080 volume and the old volume is marked as empty. Note, this requires
1081 ADSM to have an idea of the contents of a client, i.e. marking the
1082 database when an existing file was deleted, but this would solve your
1083 issue of restoring a client without restoring deleted files.
1085 This is pretty far from what bacula now does, but if you are going to
1086 rip things up for Base jobs,.....
1087 Also, the benefits of this are huge for very large shops, especially
1088 with media robots, but are a pain for shops with manual media
1092 > Base jobs sound pretty useful, but I'm not dying for them.
1094 Nobody is dying for them, but when you see what it does, you will die
1097 3. Restoring deleted files: Since I think my comments in (2) above
1098 have low probability of implementation, I'll also suggest that you
1099 could approach the issue of deleted files by a mechanism of having the
1100 fd report to the dir, a list of all files on the client for every
1101 backup job. The dir could note in the database entry for each file
1102 the date that the file was seen. Then if a restore as of date X takes
1103 place, only files that exist from before X until after X would be
1104 restored. Probably the major cost here is the extra date container in
1105 each row of the files table.
1107 Thanks for "listening". I hope some of this helps. If you want to
1108 contact me, please send me an email - I read some but not all of the
1109 mailing list traffic and might miss a reply there.
1111 Please accept my compliments for bacula. It is doing a great job for
1112 me!! I sympathize with you in the need to wrestle with excelence in
1113 execution vs. excelence in feature inclusion.
1118 ==============================
1121 - Design at hierarchial storage for Bacula. Migration and Clone.
1122 - Implement FSM (File System Modules).
1123 - Audit M_ error codes to ensure they are correct and consistent.
1124 - Add variable break characters to lex analyzer.
1125 Either a bit mask or a string of chars so that
1126 the caller can change the break characters.
1127 - Make a single T_BREAK to replace T_COMMA, etc.
1128 - Ensure that File daemon and Storage daemon can
1129 continue a save if the Director goes down (this
1130 is NOT currently the case). Must detect socket error,
1131 buffer messages for later.
1132 - Enhance time/duration input to allow multiple qualifiers e.g. 3d2h
1133 - Add ability to backup to two Storage devices (two SD sessions) at
1134 the same time -- e.g. onsite, offsite.
1135 - Add the ability to consolidate old backup sets (basically do a restore
1136 to tape and appropriately update the catalog). Compress Volume sets.
1137 Might need to spool via file is only one drive is available.
1138 - Compress or consolidate Volumes of old possibly deleted files. Perhaps
1139 someway to do so with every volume that has less than x% valid
1143 Migration: Move a backup from one Volume to another
1144 Clone: Copy a backup -- two Volumes
1146 Bacula Migration is based on Jobs (apparently Networker is file by file).
1148 Migration triggered by:
1152 Highwater mark (keep total size)
1157 ======================================================
1159 It is somewhat like a Full save becomes an incremental since
1160 the Base job (or jobs) plus other non-base files.
1162 - A Base backup is same as Full backup, just different type.
1163 - New BaseFiles table that contains:
1165 BaseJobId - Base JobId referenced for this FileId (needed ???)
1166 JobId - JobId currently running
1167 FileId - File not backed up, exists in Base Job
1168 FileIndex - FileIndex from Base Job.
1169 i.e. for each base file that exists but is not saved because
1170 it has not changed, the File daemon sends the JobId, BaseId,
1171 FileId, FileIndex back to the Director who creates the DB entry.
1172 - To initiate a Base save, the Director sends the FD
1173 the FileId, and full filename for each file in the Base.
1174 - When the FD finds a Base file, he requests the Director to
1175 send him the full File entry (stat packet plus MD5), or
1176 conversely, the FD sends it to the Director and the Director
1177 says yes or no. This can be quite rapid if the FileId is kept
1178 by the FD for each Base Filename.
1179 - It is probably better to have the comparison done by the FD
1180 despite the fact that the File entry must be sent across the
1182 - An alternative would be to send the FD the whole File entry
1183 from the start. The disadvantage is that it requires a lot of
1184 space. The advantage is that it requires less communications
1186 - The Job record must be updated to indicate that one or more
1188 - At end of Job, FD returns:
1189 1. Count of base files/bytes not written to tape (i.e. matches)
1190 2. Count of base file that were saved i.e. had changed.
1191 - No tape record would be written for a Base file that matches, in the
1192 same way that no tape record is written for Incremental jobs where
1193 the file is not saved because it is unchanged.
1194 - On a restore, all the Base file records must explicitly be
1195 found from the BaseFile tape. I.e. for each Full save that is marked
1196 to have one or more Base Jobs, search the BaseFile for all occurrences
1198 - An optimization might be to make the BaseFile have:
1204 This would avoid the need to explicitly fetch each File record for
1205 the Base job. The Base Job record will be fetched to get the
1206 VolSessionId and VolSessionTime.
1207 =========================================================
1210 ==========================================================
1212 For each Incremental job that is run, there may be files that
1213 were found but not saved because they were locked (this applies
1214 only to Windows). Such a system could send back to the Director
1215 a list of Unsaved files.
1217 - New UnSavedFiles table that contains:
1221 - Then in the next Incremental job, the list of Unsaved Files will be
1222 feed to the FD, who will ensure that they are explicitly chosen even
1223 if standard date/time check would not have selected them.
1224 =============================================================
1228 Multiple drive autochanger data: see Alan Brown
1229 mtx -f xxx unloadStorage Element 1 is Already Full(drive 0 was empty)
1230 Unloading Data Transfer Element into Storage Element 1...source Element
1231 Address 480 is Empty
1233 (drive 0 was empty and so was slot 1)
1234 > mtx -f xxx load 15 0
1235 no response, just returns to the command prompt when complete.
1236 > mtx -f xxx status Storage Changer /dev/changer:2 Drives, 60 Slots ( 2 Import/Export )
1237 Data Transfer Element 0:Full (Storage Element 15 Loaded):VolumeTag = HX001
1238 Data Transfer Element 1:Empty
1239 Storage Element 1:Empty
1240 Storage Element 2:Full :VolumeTag=HX002
1241 Storage Element 3:Full :VolumeTag=HX003
1242 Storage Element 4:Full :VolumeTag=HX004
1243 Storage Element 5:Full :VolumeTag=HX005
1244 Storage Element 6:Full :VolumeTag=HX006
1245 Storage Element 7:Full :VolumeTag=HX007
1246 Storage Element 8:Full :VolumeTag=HX008
1247 Storage Element 9:Full :VolumeTag=HX009
1248 Storage Element 10:Full :VolumeTag=HX010
1249 Storage Element 11:Empty
1250 Storage Element 12:Empty
1251 Storage Element 13:Empty
1252 Storage Element 14:Empty
1253 Storage Element 15:Empty
1254 Storage Element 16:Empty....
1255 Storage Element 28:Empty
1256 Storage Element 29:Full :VolumeTag=CLNU01L1
1257 Storage Element 30:Empty....
1258 Storage Element 57:Empty
1259 Storage Element 58:Full :VolumeTag=NEX261L2
1260 Storage Element 59 IMPORT/EXPORT:Empty
1261 Storage Element 60 IMPORT/EXPORT:Empty
1263 Unloading Data Transfer Element into Storage Element 15...done
1265 (just to verify it remembers where it came from, however it can be
1266 overrriden with mtx unload {slotnumber} to go to any storage slot.)
1268 There needs to be a table of drive # to devices somewhere - If there are
1269 multiple changers or drives there may not be a 1:1 correspondance between
1270 changer drive number and system device name - and depending on the way the
1271 drives are hooked up to scsi busses, they may not be linearly numbered
1272 from an offset point either.something like
1274 Autochanger drives = 2
1275 Autochanger drive 0 = /dev/nst1
1276 Autochanger drive 1 = /dev/nst2
1277 IMHO, it would be _safest_ to use explicit mtx unload commands at all
1278 times, not just for multidrive changers. For a 1 drive changer, that's
1284 MTX's manpage (1.2.15):
1285 unload [<slotnum>] [ <drivenum> ]
1286 Unloads media from drive <drivenum> into slot
1287 <slotnum>. If <drivenum> is omitted, defaults to
1288 drive 0 (as do all commands). If <slotnum> is
1289 omitted, defaults to the slot that the drive was
1290 loaded from. Note that there's currently no way
1291 to say 'unload drive 1's media to the slot it
1292 came from', other than to explicitly use that
1293 slot number as the destination.AB
1299 undef# camcontrol devlist
1300 <WANGTEK 51000 SCSI M74H 12B3> at scbus0 target 2 lun 0 (pass0,sa0)
1301 <ARCHIVE 4586XX 28887-XXX 4BGD> at scbus0 target 4 lun 0 (pass1,sa1)
1302 <ARCHIVE 4586XX 28887-XXX 4BGD> at scbus0 target 4 lun 1 (pass2)
1304 tapeinfo -f /dev/sg0 with a bad tape in drive 1:
1305 [kern@rufus mtx-1.2.17kes]$ ./tapeinfo -f /dev/sg0
1306 Product Type: Tape Drive
1308 Product ID: 'C5713A '
1310 Attached Changer: No
1311 TapeAlert[3]: Hard Error: Uncorrectable read/write error.
1312 TapeAlert[20]: Clean Now: The tape drive neads cleaning NOW.
1319 Medium Type: Not Loaded
1322 DataCompEnabled: yes
1323 DataCompCapable: yes
1324 DataDeCompEnabled: yes
1331 Handling removable disks
1333 From: Karl Cunningham <karlc@keckec.com>
1335 My backups are only to hard disk these days, in removable bays. This is my
1336 idea of how a backup to hard disk would work more smoothly. Some of these
1337 things Bacula does already, but I mention them for completeness. If others
1338 have better ways to do this, I'd like to hear about it.
1340 1. Accommodate several disks, rotated similar to how tapes are. Identified
1341 by partition volume ID or perhaps by the name of a subdirectory.
1342 2. Abort & notify the admin if the wrong disk is in the bay.
1343 3. Write backups to different subdirectories for each machine to be backed
1345 4. Volumes (files) get created as needed in the proper subdirectory, one
1347 5. When a disk is recycled, remove or zero all old backup files. This is
1348 important as the disk being recycled may be close to full. This may be
1349 better done manually since the backup files for many machines may be
1350 scattered in many subdirectories.
1355 - Make sure that all do_prompt() calls in Dir check for
1356 -1 (error) and -2 (cancel) returns.
1357 - Fix foreach_jcr() to have free_jcr() inside next().
1358 jcr=jcr_walk_start();
1359 for ( ; jcr; (jcr=jcr_walk_next(jcr)) )
1362 - A Volume taken from Scratch should take on the retention period
1364 - Correct doc for Maximum Changer Wait (and others) accepting only
1366 - Implement status that shows why a job is being held in reserve, or
1367 rather why none of the drives are suitable.
1368 - Implement a way to disable a drive (so you can use the second
1369 drive of an autochanger, and the first one will not be used or
1371 - Make sure Maximum Volumes is respected in Pools when adding
1372 Volumes (e.g. when pulling a Scratch volume).
1373 - Keep same dcr when switching device ...
1374 - Implement code that makes the Dir aware that a drive is an
1375 autochanger (so the user doesn't need to use the Autochanger = yes
1377 - Make catalog respect ACL.
1378 - Add recycle count to Media record.
1379 - Add initial write date to Media record.
1380 - Fix store_yesno to be store_bitmask.
1381 --- create_file.c.orig Fri Jul 8 12:13:05 2005
1382 +++ create_file.c Fri Jul 8 12:13:07 2005
1384 attr->ofname, be.strerror());
1387 + } else if(S_ISSOCK(attr->statp.st_mode)) {
1388 + Dmsg1(200, "Skipping socket: %s\n", attr->ofname);
1390 Dmsg1(200, "Restore node: %s\n", attr->ofname);
1391 if (mknod(attr->ofname, attr->statp.st_mode, attr->statp.st_rdev) != 0 && errno != EEXIST) {
1392 - Add true/false to conf same as yes/no
1393 - Reserve blocks other restore jobs when first cannot connect to SD.
1394 - Fix Maximum Changer Wait, Maximum Open Wait, Maximum Rewind Wait to
1395 accept time qualifiers.
1396 - Does ClientRunAfterJob fail the job on a bad return code?