From 7c185de204114297ebb0fbe6d3e8a4d550a7b87f Mon Sep 17 00:00:00 2001 From: Kern Sibbald Date: Mon, 5 Jun 2006 21:37:58 +0000 Subject: [PATCH] Updates + license change --- docs/developers/version.tex | 2 +- docs/home-page/news.txt | 87 ++++- docs/home-page/pages/projects.php | 176 +++++++--- docs/manual-de/version.tex | 2 +- docs/manual/dirdconf.tex | 20 +- docs/manual/faq.tex | 2 + docs/manual/fdl.tex | 511 ++++++++++++++++++++++++++++++ docs/manual/filedconf.tex | 8 +- docs/manual/gpl.tex | 9 +- docs/manual/install.tex | 12 +- docs/manual/lesser.tex | 8 +- docs/manual/license.tex | 17 +- docs/manual/projects.tex | 4 +- docs/manual/recycling.tex | 7 +- docs/manual/restore.tex | 51 +-- docs/manual/spooling.tex | 2 +- docs/manual/state.tex | 14 +- docs/manual/tips.tex | 6 +- docs/manual/version.tex | 2 +- 19 files changed, 821 insertions(+), 119 deletions(-) create mode 100644 docs/manual/fdl.tex diff --git a/docs/developers/version.tex b/docs/developers/version.tex index 1b6a306b..b6045387 100644 --- a/docs/developers/version.tex +++ b/docs/developers/version.tex @@ -1 +1 @@ -1.38.9 (02 May 2006) +1.38.10 (04 June 2006) diff --git a/docs/home-page/news.txt b/docs/home-page/news.txt index de1d18fc..bd180987 100644 --- a/docs/home-page/news.txt +++ b/docs/home-page/news.txt @@ -1,10 +1,76 @@ -Kern;;;2006/04/16;;;14:30 +Kern;;;2006/05/02;;;14:30 - Release Notes for Bacula 1.38.8 + Release Notes for Bacula 1.38.9 Bacula code: Total files = 419 Total lines = 137,078 (*.h *.c *.in) 20,440 additional lines of code since version 1.36.3 +Warning for version 1.38.8 and greater: +- The Windows FD no longer automatically folds the case + in wild-card comparions. To get the same behavior as before, + you must explicitly use "Ignore Case = yes" in your FileSet. +- Backslashes are no longer permitted in File directives + (typical error for Windows users), unless the string is + enclosed in double quotes, in which case, the backslashes + must be doubled. +- The new algorithm for selecting Volumes from the Scratch + pool that was implemented in 1.38.6 and 1.38.7 is abandoned + in favor of a corrected version of the 1.38.5 algorithm. + +New features for 1.38.9: +- A "Dir Status" button in the Gnome console. + +Fixes: +This is mainly a bug fix release containing a collection of + minor fixes for 1.38.8. +- Added code to strip backslashes from Windows filenames during + a restore. +- Corrected Win32 License to use the correct LICENSE file. +- Corrected the buffer count and bytes reported in the heap + statistics. +- Fix a number of incorrect strings marked for translation, when + they should not be (e.g. commands). +- Fix StartTime bug reported for ClientRunBeforeJob and RunBeforeJob + Patches supplied by user in bugs #608 and #599. +- Use most recent of st_ctime and st_mtime in restore tree DIR + listing. This fixes some problems with Win32 printing incorrect + values. +- Correct the clock shift comm time calculation between the DIR + and the FD. It was added rather than subtracted. +- Strip all backslashes in filenames to be restored on Win32 + machines -- the names should all be in Unix format, and if + there are any backslashes it is most likely due to an improper + FileSet definition, and the files will not otherwise be + restorable. +- Delete src/win32/License.txt +- Modify installer to install LICENSE +- Add back ua_label barcode fix from Rufolf Cejka. +- Add 'Dir Status' button to the gnome console. +- Display heap stats in Storage daemon without debug level. +- Implement using pg_config for finding PostgreSQL files. + Fixes bug #600. Patch supplied by user. +- Remove -t option from mktemp in mtx_changer.in and use + working directory. Fixes bug #578. +- Update job start time after the any run before job so that + files created by the script are only backed up once. Fixes + bug #599. +- Strip trailing newline only from filenames entered in + the restore command when reading a file. This permits + the user to enter filenames with trailing spaces. Fixes + bug #549. The user supplied a patch that I modified slightly. +- Use the most recent time (st_mtime, st_ctime) in the dir + command in restore. This gives the user a better idea of what + the newest file really is. This fixes bug #574. The fix + was suggested by the user. +- Remove the -f option from the chown in Makefile.in for more + portability. +- Change setting the group in Makefile.in to use chgrp for + more portability. +- Implement a Bacula read/write lock for Python rather + than using the Python lock to avoid recursive problems. +- Correct the uninstall directory names in filed/Makefile.in + as reported by a user. + !!!! Important !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! In Bacula version 1.38.5 and prior, there was apparently a compiler bug that caused the Storage daemon to seg fault. @@ -18,27 +84,13 @@ Kern;;;2006/04/16;;;14:30 a compiler bug in gcc's 64 bit code generation. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -Warning: -- The Windows FD no longer automatically folds the case - in wild-card comparions. To get the same behavior as before, - you must explicitly use "Ignore Case = yes" in your FileSet. -- Backslashes are no longer permitted in File directives - (typical error for Windows users), unless the string is - enclosed in double quotes, in which case, the backslashes - must be doubled. -- The new algorithm for selecting Volumes from the Scratch - pool that was implemented in 1.38.6 and 1.38.7 is abandoned - in favor of a corrected version of the 1.38.5 algorithm. New features for 1.38.8: - Regex, RegexFile, and RegexDir are now implemented in the Win32 FD. However, this is new experimental code that is largely untested. It may not work, it may cause memory leaks, or it may even crash the FD. Please test carefully - before using. Unfortunately, at this time, the Ignore Case - directive is not implemented in the Windows regex, so - you must explictly take into account the case in your - patterns. + before using. - On Linux/Unix systems there are two new programs, bregex and bwild that allow you to test regular expressions and wild-cards. These programs are installed with the other @@ -680,6 +732,7 @@ Other Items Fixed: all else fails, change to using user=root. However, it is more secure to use user=bacula. + Michael;;;2005/02/25;;;19:59 News-Page for the Bacula-Website finished When you read this, you read the first news posted by me *hehe* diff --git a/docs/home-page/pages/projects.php b/docs/home-page/pages/projects.php index cb854143..a1b400b2 100644 --- a/docs/home-page/pages/projects.php +++ b/docs/home-page/pages/projects.php @@ -44,7 +44,7 @@ Below, you will find more information on future projects: Item 1: Implement data encryption (as opposed to comm encryption) Date: 28 October 2005 Origin: Sponsored by Landon and 13 contributors to EFF. - Status: Landon Fuller is currently implementing this. + Status: Landon Fuller has implemented this in 1.39.x. What: Currently the data that is stored on the Volume is not encrypted. For confidentiality, encryption of data at @@ -58,7 +58,7 @@ Item 2: Implement Migration that moves Jobs from one Pool to another. Origin: Sponsored by Riege Software International GmbH. Contact: Daniel Holtkamp Date: 28 October 2005 - Status: Partially coded in 1.37 -- much more to do. Assigned to + Status: Partially working in 1.39, more to do. Assigned to Kern. What: The ability to copy, move, or archive data that is on a @@ -109,10 +109,16 @@ Item 3: Accurate restoration of renamed/deleted files from but one additional database record must be written, which does not need any database change. + Kern: see if we can correct restoration of directories if + replace=ifnewer is set. Currently, if the directory does not + exist, a "dummy" directory is created, then when all the files + are updated, the dummy directory is newer so the real values + are not updated. + Item 4: Implement a Bacula GUI/management tool using Python. Origin: Kern Date: 28 October 2005 - Status: + Status: Lucus is working on this for Python GTK+. What: Implement a Bacula console, and management tools using Python and Qt or GTK. @@ -289,8 +295,8 @@ Item 8: Implement creation and maintenance of copy pools Item 9: Implement new {Client}Run{Before|After}Job feature. Date: 26 September 2005 - Origin: Phil Stracchino - Status: + Origin: Phil Stracchino + Status: Done. This has been implemented by Eric Bollengier What: Some time ago, there was a discussion of RunAfterJob and ClientRunAfterJob, and the fact that they do not run after failed @@ -299,45 +305,63 @@ Item 9: Implement new {Client}Run{Before|After}Job feature. ClientRunAfterFailedJob directive), but to my knowledge these were never implemented. + The current implementation doesn't permit to add new feature easily. + An alternate way of approaching the problem has just occurred to me. Suppose the RunBeforeJob and RunAfterJob directives were - expanded in a manner something like this example: + expanded in a manner like this example: - RunBeforeJob { + RunScript { Command = "/opt/bacula/etc/checkhost %c" - RunsOnClient = No - RunsAtJobLevels = All # All, Full, Diff, Inc - AbortJobOnError = Yes + RunsOnClient = No # default + AbortJobOnError = Yes # default + RunsWhen = Before } - RunBeforeJob { + RunScript { Command = c:/bacula/systemstate.bat RunsOnClient = yes - RunsAtJobLevels = All # All, Full, Diff, Inc AbortJobOnError = No + RunsWhen = After + RunsOnFailure = yes } - RunAfterJob { + RunScript { Command = c:/bacula/deletestatefile.bat - RunsOnClient = Yes - RunsAtJobLevels = All # All, Full, Diff, Inc - RunsOnSuccess = Yes - RunsOnFailure = Yes - } - RunAfterJob { - Command = c:/bacula/somethingelse.bat - RunsOnClient = Yes - RunsAtJobLevels = All - RunsOnSuccess = No - RunsOnFailure = Yes - } - RunAfterJob { - Command = "/opt/bacula/etc/checkhost -v %c" - RunsOnClient = No - RunsAtJobLevels = All - RunsOnSuccess = No - RunsOnFailure = Yes + Target = rico-fd + RunsWhen = Always } + It's now possible to specify more than 1 command per Job. + (you can stop your database and your webserver without a script) + + ex : + Job { + Name = "Client1" + JobDefs = "DefaultJob" + Write Bootstrap = "/tmp/bacula/var/bacula/working/Client1.bsr" + FileSet = "Minimal" + + RunBeforeJob = "echo test before ; echo test before2" + RunBeforeJob = "echo test before (2nd time)" + RunBeforeJob = "echo test before (3rd time)" + RunAfterJob = "echo test after" + ClientRunAfterJob = "echo test after client" + + RunScript { + Command = "echo test RunScript in error" + Runsonclient = yes + RunsOnSuccess = no + RunsOnFailure = yes + RunsWhen = After # never by default + } + RunScript { + Command = "echo test RunScript on success" + Runsonclient = yes + RunsOnSuccess = yes # default + RunsOnFailure = no # default + RunsWhen = After + } + } Why: It would be a significant change to the structure of the directives, but allows for a lot more flexibility, including @@ -345,19 +369,19 @@ Item 9: Implement new {Client}Run{Before|After}Job feature. succeeds, or RunBefore tasks that still allow the job to run even if that specific RunBefore fails. - Notes: By Kern: I would prefer to have a single new Resource called - RunScript. More notes from Phil: + Notes: (More notes from Phil, Kern, David and Eric) + I would prefer to have a single new Resource called + RunScript. - RunBeforeJob = yes|no - RunAfterJob = yes|no - RunsAtJobLevels = All|Full|Diff|Inc + RunsWhen = After|Before|Always + RunsAtJobLevels = All|Full|Diff|Inc # not yet implemented The AbortJobOnError, RunsOnSuccess and RunsOnFailure directives - could be optional, and possibly RunsWhen as well. + could be optional, and possibly RunWhen as well. AbortJobOnError would be ignored unless RunsWhen was set to Before - (or RunsBefore Job set to Yes), and would default to Yes if - omitted. If AbortJobOnError was set to No, failure of the script + and would default to Yes if omitted. + If AbortJobOnError was set to No, failure of the script would still generate a warning. RunsOnSuccess would be ignored unless RunsWhen was set to After @@ -368,7 +392,6 @@ Item 9: Implement new {Client}Run{Before|After}Job feature. Allow having the before/after status on the script command line so that the same script can be used both before/after. - David Boyes. Item 10: Merge multiple backups (Synthetic Backup or Consolidation). Origin: Marc Cousin and Eric Bollengier @@ -471,7 +494,8 @@ Item 13: Multiple threads in file daemon for the same job Item 14: Implement red/black binary tree routines. Date: 28 October 2005 Origin: Kern - Status: + Status: Class code is complete. Code needs to be integrated into + restore tree code. What: Implement a red/black binary tree class. This could then replace the current binary insert/search routines @@ -483,7 +507,8 @@ Item 14: Implement red/black binary tree routines. Item 15: Add support for FileSets in user directories CACHEDIR.TAG Origin: Norbert Kiesel Date: 21 November 2005 - Status: + Status: (I think this is better done using a Python event that I + will implement in version 1.39.x). What: CACHDIR.TAG is a proposal for identifying directories which should be ignored for archiving/backup. It works by ignoring @@ -514,7 +539,7 @@ Item 15: Add support for FileSets in user directories CACHEDIR.TAG Item 16: Implement extraction of Win32 BackupWrite data. Origin: Thorsten Engel Date: 28 October 2005 - Status: Assigned to Thorsten. Implemented in current CVS + Status: Done. Assigned to Thorsten. Implemented in current CVS What: This provides the Bacula File daemon with code that can pick apart the stream output that Microsoft writes @@ -644,7 +669,7 @@ Item 21: Quick release of FD-SD connection after backup. Item 22: Permit multiple Media Types in an Autochanger Origin: Kern - Status: Now implemented + Status: Done. Implemented in 1.38.9 (I think). What: Modify the Storage daemon so that multiple Media Types can be specified in an autochanger. This would be somewhat @@ -719,6 +744,69 @@ Item 25: Implement huge exclude list support using hashing. complete restore would be to restore the base OS, then do a Bacula restore. By excluding the base OS files, the backup set will be *much* smaller. + + +============= Empty Feature Request form =========== +Item n: One line summary ... + Date: Date submitted + Origin: Name and email of originator. + Status: + + What: More detailed explanation ... + + Why: Why it is important ... + + Notes: Additional notes or features (omit if not used) +============== End Feature Request form ============== + + +=============================================== +Feature requests submitted after cutoff for December 2005 vote +=============================================== +Item n: Allow skipping execution of Jobs + Date: 29 November 2005 + Origin: Florian Schnabel + Status: + + What: An easy option to skip a certain job on a certain date. + Why: You could then easily skip tape backups on holidays. Especially + if you got no autochanger and can only fit one backup on a tape + that would be really handy, other jobs could proceed normally + and you won't get errors that way. + +=================================================== + +Item n: archive data + + Origin: calvin streeting calvin at absentdream dot com + Date: 15/5/2006 + + What: The abilty to archive to media (dvd/cd) in a uncompressd format + for dead filing (archiving not backing up) + + Why: At my works when jobs are finished and moved off of the main file + servers (raid based systems) onto a simple linux file server (ide based + system) so users can find old information without contacting the IT + dept. + + So this data dosn't realy change it only gets added to, + But it also needs backing up. At the moment it takes + about 8 hours to back up our servers (working data) so + rather than add more time to existing backups i am trying + to implement a system where we backup the acrhive data to + cd/dvd these disks would only need to be appended to + (burn only new/changed files to new disks for off site + storage). basialy understand the differnce between + achive data and live data. + + Notes: scan the data and email me when it needs burning divide + into predifind chunks keep a recored of what is on what + disk make me a label (simple php->mysql=>pdf stuff) i + could do this bit ability to save data uncompresed so + it can be read in any other system (future proof data) + save the catalog with the disk as some kind of menu + system + diff --git a/docs/manual-de/version.tex b/docs/manual-de/version.tex index 1b6a306b..b6045387 100644 --- a/docs/manual-de/version.tex +++ b/docs/manual-de/version.tex @@ -1 +1 @@ -1.38.9 (02 May 2006) +1.38.10 (04 June 2006) diff --git a/docs/manual/dirdconf.tex b/docs/manual/dirdconf.tex index fe18b9bd..3f03fe16 100644 --- a/docs/manual/dirdconf.tex +++ b/docs/manual/dirdconf.tex @@ -1177,6 +1177,10 @@ RunScript { \item [Spool Attributes = \lt{}yes|no\gt{}] \index[dir]{Spool Attributes} \index[dir]{Directive!Spool Attributes} + \index[dir]{slow} + \index[general]{slow} + \index[dir]{Backups!slow} + \index[general]{Backups!slow} The default is set to {\bf no}, which means that the File attributes are sent by the Storage daemon to the Director as they are stored on tape. However, @@ -2008,16 +2012,12 @@ resource that can run concurrently. Note, this directive limits only Jobs for Jobs using this Storage daemon. Any other restrictions on the maximum concurrent jobs such as in the Director, Job, or Client resources will also apply in addition to any limit specified here. The default is set to 1, but -you may set it to a larger number. We strongly recommend that you read the -WARNING documented under -\ilink{ Maximum Concurrent Jobs}{DirMaxConJobs} in the Director's -resource. - -While it is possible to set the Director's, Job's, or Client's maximum -concurrent jobs greater than one, you should take great care in setting the -Storage daemon's greater than one. By keeping this directive set to one, you -will avoid having two jobs simultaneously write to the same Volume. Although -this is supported, it is not currently recommended. +you may set it to a larger number. However, if you set the Storage +daemon's number of concurrent jobs greater than one, +we recommend that you read the +waring documented under \ilink{Maximum Concurrent Jobs}{DirMaxConJobs} +in the Director's resource or simply turn data spooling on as documented +in the \ilink{Data Spooling}{SpoolingChapter} chapter of this manual. \end{description} The following is an example of a valid Storage resource definition: diff --git a/docs/manual/faq.tex b/docs/manual/faq.tex index c30888c8..e27eb16c 100644 --- a/docs/manual/faq.tex +++ b/docs/manual/faq.tex @@ -743,6 +743,8 @@ directory, which you can examine to determine the problem. some other communications error. Why?] \index[general]{Communications Errors} \index[general]{Pipe Errors} +\index[general]{slow} +\index[general]{Backups!slow} There are a number of reasons why a connection might break. Most often, it is a router between your two computers that times out inactive lines (not respecting the keepalive feature that Bacula uses). diff --git a/docs/manual/fdl.tex b/docs/manual/fdl.tex new file mode 100644 index 00000000..ea027bba --- /dev/null +++ b/docs/manual/fdl.tex @@ -0,0 +1,511 @@ +%---------The file header--------------------------------------------- + +\usepackage[english]{babel} %language selection +\usepackage[T1]{fontenc} + +\pagenumbering{arabic} + +\usepackage{hyperref} +\hypersetup{colorlinks, + citecolor=black, + filecolor=black, + linkcolor=black, + urlcolor=black, + pdftex} + + +%--------------------------------------------------------------------- +\section*{GNU Free Documentation License} +\index[general]{GNU ree Documentation License} +\index[general]{License!GNU ree Documentation} +\addcontentsline{toc}{section}{GNU ree Documentation License} + +%\label{label_fdl} + + \begin{center} + + Version 1.2, November 2002 + + + Copyright \copyright 2000,2001,2002 Free Software Foundation, Inc. + + \bigskip + + 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA + + \bigskip + + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. +\end{center} + + +\begin{center} +{\bf\large Preamble} +\end{center} + +The purpose of this License is to make a manual, textbook, or other +functional and useful document "free" in the sense of freedom: to +assure everyone the effective freedom to copy and redistribute it, +with or without modifying it, either commercially or noncommercially. +Secondarily, this License preserves for the author and publisher a way +to get credit for their work, while not being considered responsible +for modifications made by others. + +This License is a kind of "copyleft", which means that derivative +works of the document must themselves be free in the same sense. It +complements the GNU General Public License, which is a copyleft +license designed for free software. + +We have designed this License in order to use it for manuals for free +software, because free software needs free documentation: a free +program should come with manuals providing the same freedoms that the +software does. But this License is not limited to software manuals; +it can be used for any textual work, regardless of subject matter or +whether it is published as a printed book. We recommend this License +principally for works whose purpose is instruction or reference. + + +\begin{center} +{\Large\bf 1. APPLICABILITY AND DEFINITIONS} +\addcontentsline{toc}{section}{1. APPLICABILITY AND DEFINITIONS} +\end{center} + +This License applies to any manual or other work, in any medium, that +contains a notice placed by the copyright holder saying it can be +distributed under the terms of this License. Such a notice grants a +world-wide, royalty-free license, unlimited in duration, to use that +work under the conditions stated herein. The \textbf{"Document"}, below, +refers to any such manual or work. Any member of the public is a +licensee, and is addressed as \textbf{"you"}. You accept the license if you +copy, modify or distribute the work in a way requiring permission +under copyright law. + +A \textbf{"Modified Version"} of the Document means any work containing the +Document or a portion of it, either copied verbatim, or with +modifications and/or translated into another language. + +A \textbf{"Secondary Section"} is a named appendix or a front-matter section of +the Document that deals exclusively with the relationship of the +publishers or authors of the Document to the Document's overall subject +(or to related matters) and contains nothing that could fall directly +within that overall subject. (Thus, if the Document is in part a +textbook of mathematics, a Secondary Section may not explain any +mathematics.) The relationship could be a matter of historical +connection with the subject or with related matters, or of legal, +commercial, philosophical, ethical or political position regarding +them. + +The \textbf{"Invariant Sections"} are certain Secondary Sections whose titles +are designated, as being those of Invariant Sections, in the notice +that says that the Document is released under this License. If a +section does not fit the above definition of Secondary then it is not +allowed to be designated as Invariant. The Document may contain zero +Invariant Sections. If the Document does not identify any Invariant +Sections then there are none. + +The \textbf{"Cover Texts"} are certain short passages of text that are listed, +as Front-Cover Texts or Back-Cover Texts, in the notice that says that +the Document is released under this License. A Front-Cover Text may +be at most 5 words, and a Back-Cover Text may be at most 25 words. + +A \textbf{"Transparent"} copy of the Document means a machine-readable copy, +represented in a format whose specification is available to the +general public, that is suitable for revising the document +straightforwardly with generic text editors or (for images composed of +pixels) generic paint programs or (for drawings) some widely available +drawing editor, and that is suitable for input to text formatters or +for automatic translation to a variety of formats suitable for input +to text formatters. A copy made in an otherwise Transparent file +format whose markup, or absence of markup, has been arranged to thwart +or discourage subsequent modification by readers is not Transparent. +An image format is not Transparent if used for any substantial amount +of text. A copy that is not "Transparent" is called \textbf{"Opaque"}. + +Examples of suitable formats for Transparent copies include plain +ASCII without markup, Texinfo input format, LaTeX input format, SGML +or XML using a publicly available DTD, and standard-conforming simple +HTML, PostScript or PDF designed for human modification. Examples of +transparent image formats include PNG, XCF and JPG. Opaque formats +include proprietary formats that can be read and edited only by +proprietary word processors, SGML or XML for which the DTD and/or +processing tools are not generally available, and the +machine-generated HTML, PostScript or PDF produced by some word +processors for output purposes only. + +The \textbf{"Title Page"} means, for a printed book, the title page itself, +plus such following pages as are needed to hold, legibly, the material +this License requires to appear in the title page. For works in +formats which do not have any title page as such, "Title Page" means +the text near the most prominent appearance of the work's title, +preceding the beginning of the body of the text. + +A section \textbf{"Entitled XYZ"} means a named subunit of the Document whose +title either is precisely XYZ or contains XYZ in parentheses following +text that translates XYZ in another language. (Here XYZ stands for a +specific section name mentioned below, such as \textbf{"Acknowledgements"}, +\textbf{"Dedications"}, \textbf{"Endorsements"}, or \textbf{"History"}.) +To \textbf{"Preserve the Title"} +of such a section when you modify the Document means that it remains a +section "Entitled XYZ" according to this definition. + +The Document may include Warranty Disclaimers next to the notice which +states that this License applies to the Document. These Warranty +Disclaimers are considered to be included by reference in this +License, but only as regards disclaiming warranties: any other +implication that these Warranty Disclaimers may have is void and has +no effect on the meaning of this License. + + +\begin{center} +{\Large\bf 2. VERBATIM COPYING} +\addcontentsline{toc}{section}{2. VERBATIM COPYING} +\end{center} + +You may copy and distribute the Document in any medium, either +commercially or noncommercially, provided that this License, the +copyright notices, and the license notice saying this License applies +to the Document are reproduced in all copies, and that you add no other +conditions whatsoever to those of this License. You may not use +technical measures to obstruct or control the reading or further +copying of the copies you make or distribute. However, you may accept +compensation in exchange for copies. If you distribute a large enough +number of copies you must also follow the conditions in section 3. + +You may also lend copies, under the same conditions stated above, and +you may publicly display copies. + + +\begin{center} +{\Large\bf 3. COPYING IN QUANTITY} +\addcontentsline{toc}{section}{3. COPYING IN QUANTITY} +\end{center} + + +If you publish printed copies (or copies in media that commonly have +printed covers) of the Document, numbering more than 100, and the +Document's license notice requires Cover Texts, you must enclose the +copies in covers that carry, clearly and legibly, all these Cover +Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on +the back cover. Both covers must also clearly and legibly identify +you as the publisher of these copies. The front cover must present +the full title with all words of the title equally prominent and +visible. You may add other material on the covers in addition. +Copying with changes limited to the covers, as long as they preserve +the title of the Document and satisfy these conditions, can be treated +as verbatim copying in other respects. + +If the required texts for either cover are too voluminous to fit +legibly, you should put the first ones listed (as many as fit +reasonably) on the actual cover, and continue the rest onto adjacent +pages. + +If you publish or distribute Opaque copies of the Document numbering +more than 100, you must either include a machine-readable Transparent +copy along with each Opaque copy, or state in or with each Opaque copy +a computer-network location from which the general network-using +public has access to download using public-standard network protocols +a complete Transparent copy of the Document, free of added material. +If you use the latter option, you must take reasonably prudent steps, +when you begin distribution of Opaque copies in quantity, to ensure +that this Transparent copy will remain thus accessible at the stated +location until at least one year after the last time you distribute an +Opaque copy (directly or through your agents or retailers) of that +edition to the public. + +It is requested, but not required, that you contact the authors of the +Document well before redistributing any large number of copies, to give +them a chance to provide you with an updated version of the Document. + + +\begin{center} +{\Large\bf 4. MODIFICATIONS} +\addcontentsline{toc}{section}{4. MODIFICATIONS} +\end{center} + +You may copy and distribute a Modified Version of the Document under +the conditions of sections 2 and 3 above, provided that you release +the Modified Version under precisely this License, with the Modified +Version filling the role of the Document, thus licensing distribution +and modification of the Modified Version to whoever possesses a copy +of it. In addition, you must do these things in the Modified Version: + +\begin{itemize} +\item[A.] + Use in the Title Page (and on the covers, if any) a title distinct + from that of the Document, and from those of previous versions + (which should, if there were any, be listed in the History section + of the Document). You may use the same title as a previous version + if the original publisher of that version gives permission. + +\item[B.] + List on the Title Page, as authors, one or more persons or entities + responsible for authorship of the modifications in the Modified + Version, together with at least five of the principal authors of the + Document (all of its principal authors, if it has fewer than five), + unless they release you from this requirement. + +\item[C.] + State on the Title page the name of the publisher of the + Modified Version, as the publisher. + +\item[D.] + Preserve all the copyright notices of the Document. + +\item[E.] + Add an appropriate copyright notice for your modifications + adjacent to the other copyright notices. + +\item[F.] + Include, immediately after the copyright notices, a license notice + giving the public permission to use the Modified Version under the + terms of this License, in the form shown in the Addendum below. + +\item[G.] + Preserve in that license notice the full lists of Invariant Sections + and required Cover Texts given in the Document's license notice. + +\item[H.] + Include an unaltered copy of this License. + +\item[I.] + Preserve the section Entitled "History", Preserve its Title, and add + to it an item stating at least the title, year, new authors, and + publisher of the Modified Version as given on the Title Page. If + there is no section Entitled "History" in the Document, create one + stating the title, year, authors, and publisher of the Document as + given on its Title Page, then add an item describing the Modified + Version as stated in the previous sentence. + +\item[J.] + Preserve the network location, if any, given in the Document for + public access to a Transparent copy of the Document, and likewise + the network locations given in the Document for previous versions + it was based on. These may be placed in the "History" section. + You may omit a network location for a work that was published at + least four years before the Document itself, or if the original + publisher of the version it refers to gives permission. + +\item[K.] + For any section Entitled "Acknowledgements" or "Dedications", + Preserve the Title of the section, and preserve in the section all + the substance and tone of each of the contributor acknowledgements + and/or dedications given therein. + +\item[L.] + Preserve all the Invariant Sections of the Document, + unaltered in their text and in their titles. Section numbers + or the equivalent are not considered part of the section titles. + +\item[M.] + Delete any section Entitled "Endorsements". Such a section + may not be included in the Modified Version. + +\item[N.] + Do not retitle any existing section to be Entitled "Endorsements" + or to conflict in title with any Invariant Section. + +\item[O.] + Preserve any Warranty Disclaimers. +\end{itemize} + +If the Modified Version includes new front-matter sections or +appendices that qualify as Secondary Sections and contain no material +copied from the Document, you may at your option designate some or all +of these sections as invariant. To do this, add their titles to the +list of Invariant Sections in the Modified Version's license notice. +These titles must be distinct from any other section titles. + +You may add a section Entitled "Endorsements", provided it contains +nothing but endorsements of your Modified Version by various +parties--for example, statements of peer review or that the text has +been approved by an organization as the authoritative definition of a +standard. + +You may add a passage of up to five words as a Front-Cover Text, and a +passage of up to 25 words as a Back-Cover Text, to the end of the list +of Cover Texts in the Modified Version. Only one passage of +Front-Cover Text and one of Back-Cover Text may be added by (or +through arrangements made by) any one entity. If the Document already +includes a cover text for the same cover, previously added by you or +by arrangement made by the same entity you are acting on behalf of, +you may not add another; but you may replace the old one, on explicit +permission from the previous publisher that added the old one. + +The author(s) and publisher(s) of the Document do not by this License +give permission to use their names for publicity for or to assert or +imply endorsement of any Modified Version. + + +\begin{center} +{\Large\bf 5. COMBINING DOCUMENTS} +\addcontentsline{toc}{section}{5. COMBINING DOCUMENTS} +\end{center} + + +You may combine the Document with other documents released under this +License, under the terms defined in section 4 above for modified +versions, provided that you include in the combination all of the +Invariant Sections of all of the original documents, unmodified, and +list them all as Invariant Sections of your combined work in its +license notice, and that you preserve all their Warranty Disclaimers. + +The combined work need only contain one copy of this License, and +multiple identical Invariant Sections may be replaced with a single +copy. If there are multiple Invariant Sections with the same name but +different contents, make the title of each such section unique by +adding at the end of it, in parentheses, the name of the original +author or publisher of that section if known, or else a unique number. +Make the same adjustment to the section titles in the list of +Invariant Sections in the license notice of the combined work. + +In the combination, you must combine any sections Entitled "History" +in the various original documents, forming one section Entitled +"History"; likewise combine any sections Entitled "Acknowledgements", +and any sections Entitled "Dedications". You must delete all sections +Entitled "Endorsements". + +\begin{center} +{\Large\bf 6. COLLECTIONS OF DOCUMENTS} +\addcontentsline{toc}{section}{6. COLLECTIONS OF DOCUMENTS} +\end{center} + +You may make a collection consisting of the Document and other documents +released under this License, and replace the individual copies of this +License in the various documents with a single copy that is included in +the collection, provided that you follow the rules of this License for +verbatim copying of each of the documents in all other respects. + +You may extract a single document from such a collection, and distribute +it individually under this License, provided you insert a copy of this +License into the extracted document, and follow this License in all +other respects regarding verbatim copying of that document. + + +\begin{center} +{\Large\bf 7. AGGREGATION WITH INDEPENDENT WORKS} +\addcontentsline{toc}{section}{7. AGGREGATION WITH INDEPENDENT WORKS} +\end{center} + + +A compilation of the Document or its derivatives with other separate +and independent documents or works, in or on a volume of a storage or +distribution medium, is called an "aggregate" if the copyright +resulting from the compilation is not used to limit the legal rights +of the compilation's users beyond what the individual works permit. +When the Document is included in an aggregate, this License does not +apply to the other works in the aggregate which are not themselves +derivative works of the Document. + +If the Cover Text requirement of section 3 is applicable to these +copies of the Document, then if the Document is less than one half of +the entire aggregate, the Document's Cover Texts may be placed on +covers that bracket the Document within the aggregate, or the +electronic equivalent of covers if the Document is in electronic form. +Otherwise they must appear on printed covers that bracket the whole +aggregate. + + +\begin{center} +{\Large\bf 8. TRANSLATION} +\addcontentsline{toc}{section}{8. TRANSLATION} +\end{center} + + +Translation is considered a kind of modification, so you may +distribute translations of the Document under the terms of section 4. +Replacing Invariant Sections with translations requires special +permission from their copyright holders, but you may include +translations of some or all Invariant Sections in addition to the +original versions of these Invariant Sections. You may include a +translation of this License, and all the license notices in the +Document, and any Warranty Disclaimers, provided that you also include +the original English version of this License and the original versions +of those notices and disclaimers. In case of a disagreement between +the translation and the original version of this License or a notice +or disclaimer, the original version will prevail. + +If a section in the Document is Entitled "Acknowledgements", +"Dedications", or "History", the requirement (section 4) to Preserve +its Title (section 1) will typically require changing the actual +title. + + +\begin{center} +{\Large\bf 9. TERMINATION} +\addcontentsline{toc}{section}{9. TERMINATION} +\end{center} + + +You may not copy, modify, sublicense, or distribute the Document except +as expressly provided for under this License. Any other attempt to +copy, modify, sublicense or distribute the Document is void, and will +automatically terminate your rights under this License. However, +parties who have received copies, or rights, from you under this +License will not have their licenses terminated so long as such +parties remain in full compliance. + + +\begin{center} +{\Large\bf 10. FUTURE REVISIONS OF THIS LICENSE} +\addcontentsline{toc}{section}{10. FUTURE REVISIONS OF THIS LICENSE} +\end{center} + + +The Free Software Foundation may publish new, revised versions +of the GNU Free Documentation License from time to time. Such new +versions will be similar in spirit to the present version, but may +differ in detail to address new problems or concerns. See +http://www.gnu.org/copyleft/. + +Each version of the License is given a distinguishing version number. +If the Document specifies that a particular numbered version of this +License "or any later version" applies to it, you have the option of +following the terms and conditions either of that specified version or +of any later version that has been published (not as a draft) by the +Free Software Foundation. If the Document does not specify a version +number of this License, you may choose any version ever published (not +as a draft) by the Free Software Foundation. + + +\begin{center} +{\Large\bf ADDENDUM: How to use this License for your documents} +\addcontentsline{toc}{section}{ADDENDUM: How to use this License for your documents} +\end{center} + +To use this License in a document you have written, include a copy of +the License in the document and put the following copyright and +license notices just after the title page: + +\bigskip +\begin{quote} + Copyright \copyright YEAR YOUR NAME. + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.2 + or any later version published by the Free Software Foundation; + with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. + A copy of the license is included in the section entitled "GNU + Free Documentation License". +\end{quote} +\bigskip + +If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, +replace the "with...Texts." line with this: + +\bigskip +\begin{quote} + with the Invariant Sections being LIST THEIR TITLES, with the + Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. +\end{quote} +\bigskip + +If you have Invariant Sections without Cover Texts, or some other +combination of the three, merge those two alternatives to suit the +situation. + +If your document contains nontrivial examples of program code, we +recommend releasing these examples in parallel under your choice of +free software license, such as the GNU General Public License, +to permit their use in free software. + +%--------------------------------------------------------------------- diff --git a/docs/manual/filedconf.tex b/docs/manual/filedconf.tex index 2c5e757f..5b95d36a 100644 --- a/docs/manual/filedconf.tex +++ b/docs/manual/filedconf.tex @@ -95,6 +95,8 @@ client program. \index[fd]{Directive!Heartbeat Interval} \index[general]{Heartbeat Interval} \index[general]{Broken pipe} + \index[general]{slow} + \index[general]{Backups!slow} This record defines an interval of time. For each heartbeat that the File daemon receives from the Storage daemon, it will forward it to the Director. In addition, if no heartbeat has been received from the @@ -137,9 +139,9 @@ client program. \item [FDAddresses = \lt{}IP-address-specification\gt{}] \index[fd]{FDAddresses} \index[fd]{Directive!FDAddresses} - Specify the ports and addresses on which the Director daemon will listen - for Bacula Console connections. Probably the simplest way to explain is - to show an example: + Specify the ports and addresses on which the File daemon listens for + Director connections. Probably the simplest way to explain is to show + an example: \footnotesize \begin{verbatim} diff --git a/docs/manual/gpl.tex b/docs/manual/gpl.tex index 9f92d762..ae1eb9ca 100644 --- a/docs/manual/gpl.tex +++ b/docs/manual/gpl.tex @@ -58,7 +58,7 @@ Version 2, June 1991 \footnotesize \begin{verbatim} Copyright (C) 1989, 1991 Free Software Foundation, Inc. -59 Temple Place - Suite 330, Boston, MA 02111-1307, USA +51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. \end{verbatim} @@ -367,7 +367,8 @@ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software -Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. +Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA +02110-1301 USA \end{verbatim} \normalsize @@ -424,7 +425,7 @@ questions to \elink{gnu@gnu.org}{mailto:gnu@gnu.org}. Copyright notice above. -Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111, -USA +Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, +Boston, MA 02110-1301 USA Updated: 3 Jan 2000 rms diff --git a/docs/manual/install.tex b/docs/manual/install.tex index b0b45a45..527f6c45 100644 --- a/docs/manual/install.tex +++ b/docs/manual/install.tex @@ -95,7 +95,13 @@ they will note if all daemons must be upgraded at the same time. Finally, please note that in general it is not necessary to do a {\bf make uninstall} before doing an upgrade. In fact, if you do so, you will most likely delete all your conf files, which could be disastrous. -The normal procedure during an upgrade is simply {\bf make install}. +The normal procedure during an upgrade is simply: +\begin{verbatim} +./configure (your options) +make +make install +\end{verbatim} + In general none of your existing .conf or .sql files will be overwritten. For additional information on upgrading, please see the \ilink{Upgrading Bacula @@ -270,7 +276,9 @@ continue on. \item make install - + Please be sure you have done a {\bf make} before entering this command, + and that everything has properly compiled and linked without errors. + \item If you are new to Bacula, we {\bf strongly} recommend that you skip the next step and use the default configuration files, then run the diff --git a/docs/manual/lesser.tex b/docs/manual/lesser.tex index 0a14d58e..4c038707 100644 --- a/docs/manual/lesser.tex +++ b/docs/manual/lesser.tex @@ -73,7 +73,7 @@ Version 2.1, February 1999 \footnotesize \begin{verbatim} Copyright (C) 1991, 1999 Free Software Foundation, Inc. -59 Temple Place, Suite 330, Boston, MA 02111-1307 USA +51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. [This is the first released version of the Lesser GPL. It also counts @@ -541,7 +541,8 @@ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software -Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA +Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 +USA \end{verbatim} \normalsize @@ -575,7 +576,8 @@ questions to \elink{gnu@gnu.org}{mailto:gnu@gnu.org}. Copyright notice above. -Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111, +Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, +Boston, MA 02110-1301 USA USA Updated: 27 Nov 2000 paulv diff --git a/docs/manual/license.tex b/docs/manual/license.tex index faaa3e50..a9bbbd9e 100644 --- a/docs/manual/license.tex +++ b/docs/manual/license.tex @@ -3,28 +3,35 @@ \section*{Bacula Copyright, Trademark, and Licenses} \label{_ChapterStart29} -\index[general]{Licenses!Bacula Copyright Trademark and } -\index[general]{Bacula Copyright, Trademark, and Licenses } +\index[general]{Licenses!Bacula Copyright Trademark} +\index[general]{Bacula Copyright, Trademark, and Licenses} \addcontentsline{toc}{section}{Bacula Copyright, Trademark, and Licenses} There are a number of different licenses that are used in Bacula. +\subsection*{FDL} +\index[general]{FDL } +\addcontentsline{toc}{subsection}{FDL} + +The GNU Free Documentation License (FDL) is used for this manual. + + \subsection*{GPL} \index[general]{GPL } \addcontentsline{toc}{subsection}{GPL} -The vast bulk of the code is released under a modified version of the +The vast bulk of the source code is released under a modified version of the \ilink{GNU General Public License version 2.}{_ChapterStart20} The modifications (actually additions) are described in the source file LICENSE, and their purpose is not to alter the essential qualities of the GPL but to permit more freedom in linking certain third party software supposedly non-GPL -compatible, provide termination for Patent (and IP) actions, clarify +compatible, and to clarify contributors IP and Copyright claims and non-infringment intentions. The details and governing text are in the file LICENSE in the main source directory. Most of this code is copyrighted: Copyright \copyright 2000-2004 Kern Sibbald and -John Walker or Copyright \copyright 2000-2005 Kern Sibbald. +John Walker or Copyright \copyright 2000-2006 Kern Sibbald. Portions may be copyrighted by other people (ATT, the Free Software Foundation, ...). Generally these portions are released under a diff --git a/docs/manual/projects.tex b/docs/manual/projects.tex index 86480b39..629fd044 100644 --- a/docs/manual/projects.tex +++ b/docs/manual/projects.tex @@ -11,7 +11,9 @@ Once a new major version of Bacula is released, the Bacula users will vote on a list of new features. This vote is used as the main element determining what new features will be implemented for the next version. Generally, the development time -for a new release is between 4 to 9 months. +for a new release is between 4 to 9 months. Sometimes it may be +a bit longer, but in that case, there will be a number of bug fix +updates to the currently released version. For the current list of project, please see the projects page in the CVS at: \elink{http://cvs.sourceforge.net/viewcvs.py/*checkout*/bacula/bacula/projects} diff --git a/docs/manual/recycling.tex b/docs/manual/recycling.tex index 2dad20fb..65e6c2cb 100644 --- a/docs/manual/recycling.tex +++ b/docs/manual/recycling.tex @@ -247,6 +247,11 @@ The full algorithm that Bacula uses when it needs a new Volume is: \index[general]{New Volume Algorithm} \index[general]{Algorithm!New Volume} +The algorithm described below assumes that AutoPrune is enabled, +that Recycling is turned on, and that you have defined +appropriate Retention periods, or used the defaults for all these +items. + \begin{itemize} \item If the request is for an Autochanger device, look only for Volumes in the Autochanger (i.e. with InChanger set and that have @@ -260,7 +265,7 @@ The full algorithm that Bacula uses when it needs a new Volume is: with the lowest MediaId is chosen). \item Try recycling any purged Volumes. \item Prune volumes applying Volume retention period (Volumes with VolStatus - Full, Used, or Append are pruned). + Full, Used, or Append are pruned). \item Search the Pool for a Volume with VolStatus=Purged \item If a Pool named "Scratch" exists, search for a Volume and if found move it to the current Pool for the Job and use it. Note, when diff --git a/docs/manual/restore.tex b/docs/manual/restore.tex index 45e3e2b0..fb676779 100644 --- a/docs/manual/restore.tex +++ b/docs/manual/restore.tex @@ -582,25 +582,38 @@ encounter, and for same machine restores, how to avoid them. \begin{itemize} \item You backed up on one machine and are restoring to another that is either a different OS or doesn't have the same users/groups defined. Bacula - does the best it can in these situations. -\item You are restoring into a directory that is already created and has file - creation restrictions. Bacula tries to reset everything but without walking - up the full chain of directories and modifying them all during the restore, - which Bacula does and will not do, getting permissions back correctly in -this - situation depends to a large extent on your OS. -\item You selected one or more files in a directory, but did not select the - directory entry to be restored. In that case, if the directory is not on -disk - Bacula simply creates the directory with some default attributes which may - not be the same as the original. If you do not select a directory and all -its - contents to be restored, you can still select items within the directory to - be restored by individually marking those files, but in that case, you -should - individually use the "markdir" command to select all higher level - directory entries (one at a time) to be restored if you want the directory - entries properly restored. + does the best it can in these situations. Note, Bacula has saved the + user/groups in numeric form, which means on a different machine, they + may map to different user/group names. +\item You are restoring into a directory that is already created and has + file creation restrictions. Bacula tries to reset everything but + without walking up the full chain of directories and modifying them all + during the restore, which Bacula does and will not do, getting + permissions back correctly in this situation depends to a large extent + on your OS. +\item You are doing a recursive restore of a directory tree. In this case + Bacula will restore a file before restoring the file's parent directory + entry. In the process of restoring the file Bacula will create the + parent directory with open permissions and ownership of the file being + restored. Then when Bacula tries to restore the parent directory Bacula + sees that it already exists (Similar to the previous situation). If you + had set the Restore job's "Replace" property to "never" then Bacula will + not change the directory's permissions and ownerships to match what it + backed up, you should also notice that the actual number of files + restored is less then the expected number. If you had set the Restore + job's "Replace" property to "always" then Bacula will change the + Directory's ownership and permissions to match what it backed up, also + the actual number of files restored should be equal to the expected + number. +\item You selected one or more files in a directory, but did not select the + directory entry to be restored. In that case, if the directory is not + on disk Bacula simply creates the directory with some default attributes + which may not be the same as the original. If you do not select a + directory and all its contents to be restored, you can still select + items within the directory to be restored by individually marking those + files, but in that case, you should individually use the "markdir" + command to select all higher level directory entries (one at a time) to + be restored if you want the directory entries properly restored. \end{itemize} \label{Windows} diff --git a/docs/manual/spooling.tex b/docs/manual/spooling.tex index 2e5b312e..c1a7a81f 100644 --- a/docs/manual/spooling.tex +++ b/docs/manual/spooling.tex @@ -2,7 +2,7 @@ %% \section*{Data Spooling} -\label{_ChapterStart5} +\label{SpoolingChapter} \index[general]{Data Spooling } \index[general]{Spooling!Data } \addcontentsline{toc}{section}{Data Spooling} diff --git a/docs/manual/state.tex b/docs/manual/state.tex index 944a07d7..95e2bd79 100644 --- a/docs/manual/state.tex +++ b/docs/manual/state.tex @@ -196,7 +196,7 @@ In other words, what is and what is not currently implemented and functional. not supported. They will be backed up, but they cannot be restored. By using the {\bf Portable=yes} directive in your FileSet, files with long names can be restored to Unix and Linux systems. - Long filenames for Win32 will be implemented in a later version. + Long filenames for Win32 will be implemented in version 1.40. \item If you have over 4 billion file entries stored in your database, the database FileId is likely to overflow. This is a monster database, but still possible. At some point, Bacula's FileId fields will be upgraded from 32 bits @@ -211,12 +211,18 @@ In other words, what is and what is not currently implemented and functional. moved files. Correcting this is a future project. \item File System Modules (configurable routines for saving/restoring special files) are not yet implemented. -\item Data encryption of the Volume contents. +\item Data encryption of the Volume contents. Bacula version 1.40 + will have this feature. \item Bacula cannot automatically restore files for a single Job from two or more different storage devices or different media types. That is, if you use more than one storage device or media type to backup a single job, the restore process will require some manual intervention. +\item Bacula does not currently support removable disk Volumes. + Some users seem to have it working, but you must take care to + have the correct volume mounted, and restores spanning removable + disk volumes are not likely to work. It is planned that Bacula + 1.40 will have this feature. \end{itemize} \subsection*{Design Limitations or Restrictions} @@ -230,6 +236,6 @@ In other words, what is and what is not currently implemented and functional. the limit is defined as 127 characters. Note, this does not apply to filenames, which may be arbitrarily long. \item On Win32 machines filenames are limited by the non-Unicode Windows - API that we use to 260 characters. This is planned to be corrected in - a future version by switching to the Unicode API. + API that we use to 260 characters. This is corrected in + version 1.39 and later by switching to the Unicode API. \end{itemize} diff --git a/docs/manual/tips.tex b/docs/manual/tips.tex index 07d2e3cd..06f0bc21 100644 --- a/docs/manual/tips.tex +++ b/docs/manual/tips.tex @@ -1013,8 +1013,10 @@ the same Client to the same Storage device, they will run concurrently only if you have set {\bf Maximum Concurrent Jobs} greater than one in the Director resource, the Client resource, and the Storage resource in bacula-dir.conf. -We recommend that you carefully test your multiple concurrent backup including -doing thorough restore testing before you put it into production. +We recommend that you carefully read the \ilink{Data +Spooling}{SpoolingChapter} of this manual first, then carefully +test your multiple concurrent backup including +restore testing before you put it into production. Below is a super stripped down bacula-dir.conf file showing you the four places where the the file has been modified to allow the same job {\bf diff --git a/docs/manual/version.tex b/docs/manual/version.tex index 1b6a306b..b6045387 100644 --- a/docs/manual/version.tex +++ b/docs/manual/version.tex @@ -1 +1 @@ -1.38.9 (02 May 2006) +1.38.10 (04 June 2006) -- 2.39.5