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