From: Kern Sibbald Date: Sun, 23 Jul 2006 12:20:30 +0000 (+0000) Subject: Add French home-page, correct build of French manual X-Git-Tag: Release-2.0.0~730 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=446772be6ec5496bd8dd47a0e513c58d11614125;p=bacula%2Fdocs Add French home-page, correct build of French manual --- diff --git a/docs/autoconf/configure.in b/docs/autoconf/configure.in index b3c8d156..54044eb4 100644 --- a/docs/autoconf/configure.in +++ b/docs/autoconf/configure.in @@ -95,8 +95,10 @@ AC_OUTPUT([ \ manual/version.tex \ manual-de/Makefile \ manual-de/version.tex \ + manual-de/update_version \ manual-fr/Makefile \ manual-fr/version.tex \ + manual-fr/update_version \ developers/Makefile \ developers/version.tex \ bacula-web/Makefile \ @@ -106,6 +108,8 @@ AC_OUTPUT([ \ ) chmod 766 manual/update_version +chmod 766 manual-fr/update_version +chmod 766 manual-de/update_version echo " Configuration on `date`: diff --git a/docs/configure b/docs/configure index ad632159..54abe447 100755 --- a/docs/configure +++ b/docs/configure @@ -1768,7 +1768,7 @@ MCOMMON=./autoconf/Make.common - ac_config_files="$ac_config_files autoconf/Make.common Makefile manual/Makefile manual/update_version manual/version.tex manual-de/Makefile manual-de/version.tex manual-fr/Makefile manual-fr/version.tex developers/Makefile developers/version.tex bacula-web/Makefile bacula-web/version.tex $PFILES" + ac_config_files="$ac_config_files autoconf/Make.common Makefile manual/Makefile manual/update_version manual/version.tex manual-de/Makefile manual-de/version.tex manual-de/update_version manual-fr/Makefile manual-fr/version.tex manual-fr/update_version developers/Makefile developers/version.tex bacula-web/Makefile bacula-web/version.tex $PFILES" ac_config_commands="$ac_config_commands default" cat >confcache <<\_ACEOF # This file is a shell script that caches the results of configure @@ -2331,8 +2331,10 @@ do "manual/version.tex" ) CONFIG_FILES="$CONFIG_FILES manual/version.tex" ;; "manual-de/Makefile" ) CONFIG_FILES="$CONFIG_FILES manual-de/Makefile" ;; "manual-de/version.tex" ) CONFIG_FILES="$CONFIG_FILES manual-de/version.tex" ;; + "manual-de/update_version" ) CONFIG_FILES="$CONFIG_FILES manual-de/update_version" ;; "manual-fr/Makefile" ) CONFIG_FILES="$CONFIG_FILES manual-fr/Makefile" ;; "manual-fr/version.tex" ) CONFIG_FILES="$CONFIG_FILES manual-fr/version.tex" ;; + "manual-fr/update_version" ) CONFIG_FILES="$CONFIG_FILES manual-fr/update_version" ;; "developers/Makefile" ) CONFIG_FILES="$CONFIG_FILES developers/Makefile" ;; "developers/version.tex" ) CONFIG_FILES="$CONFIG_FILES developers/version.tex" ;; "bacula-web/Makefile" ) CONFIG_FILES="$CONFIG_FILES bacula-web/Makefile" ;; @@ -2831,6 +2833,8 @@ fi chmod 766 manual/update_version +chmod 766 manual-fr/update_version +chmod 766 manual-de/update_version echo " Configuration on `date`: diff --git a/docs/home-page/fr/donations.txt b/docs/home-page/fr/donations.txt new file mode 100644 index 00000000..9b1e61d5 --- /dev/null +++ b/docs/home-page/fr/donations.txt @@ -0,0 +1,10 @@ +Kern;;;2006/04/04;;;12:30 +Bacula is now able to accept direct donations. +Please follow the Make a Donation link for more +information. + +Many thanks to the many Bacula supporters who +have made donations. + +;;; + diff --git a/docs/home-page/fr/fdl.txt b/docs/home-page/fr/fdl.txt new file mode 100644 index 00000000..4a0fe1c8 --- /dev/null +++ b/docs/home-page/fr/fdl.txt @@ -0,0 +1,397 @@ + GNU Free Documentation License + Version 1.2, November 2002 + + + Copyright (C) 2000,2001,2002 Free Software Foundation, Inc. + 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. + + +0. PREAMBLE + +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. + + +1. APPLICABILITY AND DEFINITIONS + +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 "Document", below, +refers to any such manual or work. Any member of the public is a +licensee, and is addressed as "you". You accept the license if you +copy, modify or distribute the work in a way requiring permission +under copyright law. + +A "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 "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 "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 "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 "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 "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 "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 "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 "Acknowledgements", +"Dedications", "Endorsements", or "History".) To "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. + + +2. VERBATIM COPYING + +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. + + +3. COPYING IN QUANTITY + +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. + + +4. MODIFICATIONS + +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: + +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. +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. +C. State on the Title page the name of the publisher of the + Modified Version, as the publisher. +D. Preserve all the copyright notices of the Document. +E. Add an appropriate copyright notice for your modifications + adjacent to the other copyright notices. +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. +G. Preserve in that license notice the full lists of Invariant Sections + and required Cover Texts given in the Document's license notice. +H. Include an unaltered copy of this License. +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. +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. +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. +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. +M. Delete any section Entitled "Endorsements". Such a section + may not be included in the Modified Version. +N. Do not retitle any existing section to be Entitled "Endorsements" + or to conflict in title with any Invariant Section. +O. Preserve any Warranty Disclaimers. + +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. + + +5. COMBINING DOCUMENTS + +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". + + +6. COLLECTIONS OF DOCUMENTS + +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. + + +7. AGGREGATION WITH INDEPENDENT WORKS + +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. + + +8. TRANSLATION + +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. + + +9. TERMINATION + +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. + + +10. FUTURE REVISIONS OF THIS LICENSE + +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. + + +ADDENDUM: How to use this License for your documents + +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: + + Copyright (c) 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". + +If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, +replace the "with...Texts." line with this: + + with the Invariant Sections being LIST THEIR TITLES, with the + Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. + +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/home-page/fr/footer.php b/docs/home-page/fr/footer.php new file mode 100644 index 00000000..286806ac --- /dev/null +++ b/docs/home-page/fr/footer.php @@ -0,0 +1,10 @@ +
+ spacer
+ +
+ + + diff --git a/docs/home-page/fr/inc/footer.php b/docs/home-page/fr/inc/footer.php new file mode 100644 index 00000000..13dbecd9 --- /dev/null +++ b/docs/home-page/fr/inc/footer.php @@ -0,0 +1,10 @@ +
+ spacer
+ +
+ + + diff --git a/docs/home-page/fr/inc/header.php b/docs/home-page/fr/inc/header.php new file mode 100644 index 00000000..2342e42c --- /dev/null +++ b/docs/home-page/fr/inc/header.php @@ -0,0 +1,221 @@ + + + + + + Bacula, the Network Backup Tool for Linux, Unix, and Windows + + + + + + + + + + + +
+ + + + + +
+ Bacula, l'outil de sauvegarde réseau pour Linux, Unix, Mac et + Windows. + +
+ + + + +
+
+
+ + + + + + '); + printf('Welcome %s, logout here.', $_SESSION['user']); + printf(''); + } + ?> + + +
+ + +
Général
+
+ +
+ + + +
Documentation
+
+ +
+ + +
Téléchargements
+
+ +
+ + +
Support
+
+ +
+ + +
Projets
+
+ +
+ + +
Donations
+
+ +
+ +
+
+ Sectoor Logo + + +
+ +
+ +
+ Il surgit de la nuit et absorbe l'essence vitale de vos ordinateurs. +
+ +
diff --git a/docs/home-page/fr/index.php b/docs/home-page/fr/index.php new file mode 100644 index 00000000..804203d8 --- /dev/null +++ b/docs/home-page/fr/index.php @@ -0,0 +1,32 @@ +ERROR occurred:
+

+ The page %s isn\'t available. +

', $page); +} + + +/** + * load footer + * + */ +require_once("inc/footer.php"); + +?> diff --git a/docs/home-page/fr/news.txt b/docs/home-page/fr/news.txt new file mode 100644 index 00000000..37c53f47 --- /dev/null +++ b/docs/home-page/fr/news.txt @@ -0,0 +1,704 @@ +Kern;;;2006/05/02;;;14:30 + Release Notes pour Bacula 1.38.9 + +Attention pour les versions ultérieures à 1.38.8: + +- le File Daemon Windows est désormais sensible à la casse. Pour retrouver le +comportement des versions antérieures, vous devez explicitement utiliser +"Ignore case = yes" dans la définition du FileSet. + +- Le caractère anti-slash n'est désormais plus autorisé dans les directives +File (erreur typique pour les utilisateurs Windows), à moins que la chaîne +soit encadrée de guillemets, auquel cas les caractères anti-slash doivent +être doublés. + +- Le nouvel algorithme pour la sélection des volumes issus du "Scratch Pool" +qui était implémenté dans les version 1.38.6 et 1.38.7 a été abandonné au +profit de la version corrigée de l'algorithme de la version +1.38.5. + +Nouvelle fonctionnalité pour la version 1.38.9: +- un bouton "Dir Status" a été ajouté pour la console Gnome. + +Cette version contient principalement des corrections de bugs mineurs pour la +version 1.38.8. + +;;; + +Kern;;;2006/05/02;;;14:30 +Erreur de segmentation pour les versions antérieures à la version 1.38.5 + +Important ! +Dans les versions 1.38.5 et antérieures, il y avait apparemment un bug qui +engendrait une erreur de segmentation pour le démon de stockage. + +Un contournement a été implémenté dans la version 1.38.6 et supérieure qui +semble fonctionner. Toutefois si vous rencontrez des problèmes, suivez les +instructions ci-dessous. + +Si vous compilez Bacula sur un machine 64 bits, vous devez vous assurer que +le code est compilé avec l'option -O0 sinon le SD devrait se planter sur +presque toutes les opérations. Ceci est apparemment dû à un bug du +compilateur gcc lors de la génération du code 64 bits. + +;;; + +Kern;;;2006/04/14;;;14:30 + Release Notes for Bacula 1.38.8 + +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. +- 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 + binaries. They are not available on Win32 systems. + +Fixes: +- See below. + +New Features from pre-1.38.8 releases: +- For autochanger get Scratch tape if in autochanger if + no appendable Volumes are available. +- New virtual disk autochanger. See scripts/disk-changer for + documentation. +- New optional Device resource directive in SD. 'Device Type =', + which may have types: File, DVD, Tape, or FIFO. This can + be useful for writing DVDs on FreeBSD where Bacula cannot + correctly detect the DVD. +- Faster restore tree building and uses less memory. +- The command line keyword job (or jobname) now refers to the + name of the job specified in the Job resource; jobid refers + as before to the non-unique numeric jobid; and ujobid refers + to the unique job identification that Bacula creates for each + job. +- The job report for Backups has a few more user friendly ways + of displaying the information. +- The wait command can now be made to wait for jobids. +- New command line keywords are permitted in update volume. They + are Inchanger=yes/no, slot=nn. +- Add two new console commands: enable job=<job-name> and + disable job=<job-name>. When a job is disabled, it will not + be started by the scheduler. If you disable a job and restart + Bacula or reload the .conf file, the job will be re-enabled. +- Add a new Job resource directive "enable = yes|no". +- There is a new program named regex in the tools directory that + allows you to try regular expressions on your system. + +Major bug fixes: +- Fix race condition in multiple-drive autochangers where + both drives want the same Volume. +- Do not allow opening default catalog for restricted console + if it is not in ACL. +- Writable FIFOs now work for restore. +- ACLs are now checked in all dot commands. +- Multiple drive autochangers and multiple different autochangers + should now work correctly (no race conditions for Volume names, + update slots use correct StorageId). +- Fix bug where drive was always reserved if a restore job failed + while in the reservation process. + + +Minor bug fixes: +- See below: +14Apr06 +- Correct Makefile for Solaris /bin/sh +- Correct mtx-changer.in for Solaris /bin/sh +- Abort if a conf resource does not have a Name = +12Apr06 +- Change the name of the regex program to bregex. +- Add the bwild program to the tools directory. It is similar + to the bregex program. +- Implement create bregex.h and bregex.c in src/lib from the + Python regexp program. +- Use the new bregex.c to implement Regex expressions on Win32. +11Apr06 +- Modify Makefile to change the permissions on Working Directory + to 770 if the directory is created. +- Do not fail the Makefile if changing the permissions or + owner/group on WorkingDir fails. +- Correct the old recycling algorithm so that Scratch Volumes + are selected when looking for a Volume in the changer. +- Correct a typo in the Verify SQL reported by Joe Park. +10Apr06 +- Remove automatic case folding on Windows FDs. You must + explictly use the 'Ignore Case = yes' option. +- Remove the code added to 1.38.6 and 1.38.7 that pulls a + scratch volume in an Autochanger early in the 'recycling' + algorithm. +08Apr06 +- Tweak license to include Microsoft restrictions. +- Move mysql.reconnect to after real_connect(). Thanks to + Frank Sweetser for the patch. +- Disallow a backslash in a File = directive (Windows junk) + unless the string is quoted. +- Apply Eric's patch to ua_label.c so that daemon protocol + is not translated. + +;;; + +Kern;;;2006/04/07;;;14:30 + Release Notes for Bacula 1.38.7 +06Apr06 +- Remove timed wait for VSS on Win2K3 as it is not yet + implemented. +- Correct bacula.in script to reference bacula-ctl-xx in the + sysconfig directory rather than the bin directory. + +Release 1.38.6 (28Mar06) released 29Mar06 +28Mar06 +- Back port from 1.39 fixes to lib/jcr.c to use foreach_jcr() + and new jcr chain locking. +26Mar06 +- Fix a long standing bug in the bacula start/stop scripts. +- Attempt to add the new bacula-ctl-* files to the rpm. +- Switch to using typeof() for list traversing to avoid + as many FC5 g++ compiler warnings as possible. +25Mar06 +- Split the bacula start/start script into four files: + bacula -- starts and stops calling other scripts + bacula-ctl-dir -- starts/stops the director + bacula-ctl-fd -- starts/stops the File daemon + bacula-ctl-sd -- starts/stops the Storage daemon +- Create datestyle fix for PostgreSQL. Fixes bug #574. +- Correct editing of JobId from int to int64 in fd_cmds.c +- Eliminate FileSet name race with bash_spaces() and multiple + threads by bashing in a local. +- Fix error return from 'use storage' to print a correct error + message rather than nothing. +- Correct false re-read last block error message when two jobs + are simultaneously writing at the end of a tape. +- Simplify exit conditions in the reserve.c code to avoid + possible non-release of reservation_lock(). +- Suffle lock order in reserve to avoid deadlock between + reservation lock and device mutex. +- Add Thorsten's VSS timeout code to 1.38 branch. +- Initialize jcr mutex before first use. Thanks to Thorsten for + tracking this down for me !!!! as it broke the Win32 build. +- Integrate addition of line count limitation to bsmtp -l from + Sebastian Stark <stark at tuebingen.mpg.de> +- Implement regex test program in tools directory. +- Attempt to fix time problem with bsmtp with foreign langs. +- Add strip_trailing_newline() submitted by user. + +Release 1.38.6 beta6 16Mar06 +- Fix bug #537 to allow arbitrary time to mount a volume for + restore, if polling is turned on. +- Disallow multiple storage specifications for a job. Should fix Arno's + problem. +- Add back a missing store of poolid in jr.poolid. +- If dir_user or dir-group is specified in ./configure apply it to + the working-dir. Fixes bug #533. +- If rescheduling a job cancel the previous incarnation with the SD. + Fixes bugs #566 and 557. +- Fix bug #567 do_message() definition type conflict. + +Release 1.38.6 beta5 14Mar06 +- Add more jcr methods and make mutex and use_count private. +- Create lock/unlock methods for jcr. +- Fix PostgreSQL bug doing sql_data_seeek() by explicitly reading + records to get to seek position. +- Integrate patch from bug #561 to correct conio.c signal definitions. +- Fix Rescheduling failed Jobs. Ensure that SD message thread + terminates correctly by doing pthread_kill(). Do not destroy + SD cond wait variable between executions of the job. Use local + mutex for cond variable to avoid blocking jcr chain. Fix poor + use of jcr use count in jobq.c for restarted jobs. +- Fix obsolete usage of foreach_dlist() to use foreach_jcr() in + lib/jcr.c -- prevents locking the jcr chaing. +- Apply patch from bug #564, which corrects listing volumes with + multiple autochangers. Apply same fix to next volume list. +- Fix bug #562 where restore bootstrap file is not unique. +- Use new routine lock_reservations() to lock the reservations + system, and call it while looking for a volume in askdir.c. + This could possibly fix bug #543. +- Stop SD command loop if job is canceled. + +Release 1.38.6 beta3 4Mar06 +04Mar06 +- The po files should now be current. +- Fix new sql_use_result() code to properly release the + buffers in all cases. +- Convert to using new Python class definitons with (object). +- Use the keyword ujobid to mean the unique job id; job or jobname + to mean the Job name given on the Name directive, and jobid to + be the numeric (non-unique) job id. +- Allow listing by any of the above. +- Add the user friendly job report code for reporting job elapsed time + and rates with suffexes. +- Add Priority and JobLevel as Python settable items. +- Use TEMPORARY table creation where the table is created by + Bacula. +- Add new code submitted by Eric for waiting on specific jobid. +- Add ACL checking for the dot commands. +- Fix restore of writable FIFOs. +- Fix a bug in bpipe where the string was freed too early. + +26Feb06 +- Fix bug reported by Arno listing blocks with bls +- Update the po files at Eric's request. + +Release 1.38.6-beta2 25Feb06 +25Feb06 +- Add sql_use_result() define. + +Changes to 1.38.6-beta1 +- Don't open default catalog if not in ACL. +- Add virtual disk autochanger code. +- Add user supplied bug fix to make two autochangers work + correctly using StorageId with InChanger checks. +- Correct new/old_jcr confusion in copy_storage(). +- Remove & from Job during scan in msgchan.c -- probably + trashed the stack. +- When getting the next Volume if no Volume in Append mode + exists and we are dealing with an Autochanger, search + for a Scratch Volume. +- Check for missing value in dot commands -- bug fix. +- Fix bug in update barcodes command line scanning. +- Make sure Pool Max Vols is respected. +- Check that user supplied a value before referencing + it in restore -- pointed out by Karl Hakimian. +- Add Karl Hakimian's table insert code. +- Don't ask user to select a specific Volume when + updating all volumes in a Pool. +- Remove reservation if set for read when removing dcr. +- Lock code that requests next appendable volume so that + two jobs to get the same Volume at the same time. +- Add new Device Type = xxx code. Values are file, tape, + dvd, and fifo. +- Preserve certain modes (ST_LABEL|ST_APPEND|ST_READ) across + a re-open to change read/write permission on a device. +- Correct a misplaced double quote in certain autochanger + scripts. +- Make make_catalog_backup.in a bit more portable. +- Implement Karl Hakimian's sql_use_result(), which speeds + up restore tree building and reduces the memory load. +- Correct a number of minor bugs in getting a Volume from + the Scratch Pool. +- Implement additional command line options for update Volume. +- Don't require user to enter a Volume name when updating + all Volumes in a pool. + +Release 1.38.5 released 19Jan06: +- Apply label barcodes fix supplied by Rudolf Cejka. +- Modify standard rpm installation to set SD group to disk + so that SD will by default have access to tape drives. +- Allow users to specify user/group and start options + for each daemon in /etc/sysconf/bacula file. + +Changes to 1.38.4 released 17Jan06: +- The main changes are to the Director and the Storage daemon, + thus there is no need to update your File daemons. Just the + same, I do recommend running with the release 1.38.3 Win32 + FD or later. +- Add two new queries to query.sql provided by Arno. One + list volumes known to the Storage device, and the other + lists volumes possibly needing replacement (error, ...). +- Add periodic (every 24 hours) garbage collection of memory + pool by releasing free buffers. +- Correct bug counting sized (for display only) in smartall.c +- Print FD mempool stats if debug > 0 rather than 5. +- Correct bug in alist.c that re-allocated the list if the + number of items goes to zero. +- Move the reservation system thread locking to the top level + so that one job at a time tries all possible drives before + waiting. +- Implement a reservation 'fail' message queue that is built + and destroyed on each pass through the reservation system. + These messages are displayed in a 'Jobs waiting to reserve + a drive' list during a 'status storage='. Note, multiple + messages will generally print for each JobId because they + represent the different problems with either the same drive + or different drives. If this output proves too confusing + of voluminous, I will display it only when debug level 1 + or greater is enabled in the SD. +- Add enable/disable job=<job-name>. This command prevents + the specified job from being scheduled. Even when disabled, + the job can be manually started from the console. +- During 'update slots' clear all InChanger flags where the + StorageId is zero (old Media records). +- Fix autochanger code to strip leading spaces from returned + slots number. Remove bc from chio-changer. +- Back port a bit of 1.39 crypto code to reduce diffs. +- Fix first call to autochanger that missed close()ing the + drive. Put close() just before each run_program(). Fixes + Arno's changer bug. +- Add PoolId to Job record when updating it at job start time. +- Pull in more code from 1.39 so that there are fewer file + differences (the new ua_dotcmds.c, base64.h, crypto.h + hmac.c jcr.c (dird and lib) lib.h md5.h parse_conf.c + util.c. Aside from ua_dotcmds.c these are mostly crypto + upgrades. +- Implement new method of walking the jcr chain. The + incr/dec of the use_count is done within the walking + routines. This should prevent a jcr from being freed + from under the walk routines. + + +Changes to 1.38.3 released 05Jan06: +- This is mainly a bug release fix. In addition, the multiple drive + reservation algorithm has been rewritten. +- In addition, the method of handling waiting for tapes to be + mounted and the mount messages has been modified. + (the above two items are a potential source of problems). +- Simplify code in askdir.c that waits for creating an appendable + volume so that it can handle multiple returns from the wait code. +- Modify the wait code to permit multiple returns. +- Return a zero when 'autochanger drives' is called and + it is not an autochanger. +- Make rewind_dev() a method taking a DCR as an argument. + This permits closing and reopening the drive if the + rewind fails as happens if the drive was loaded while the + file descriptor was open. This refreshes the file descriptor. +- Remove the ST_OPENED flag and always rely on fd < 0 for knowing + if the device is open or not. This should eliminate + Arnos problem. +- Return error if reserve cannot find at least one suitable device. +- Make wait_for_sysop() return correct state information. +- Fix Win32 state file problem. write was not using compat + code. This should fix bug #500. +- Modify gui on command to set only GUI mode and not batch. +- Modify .messages command to always print messages regardless + of the mode. +- If GUI mode is on, suppress automatic printing of + You have messages. +- Modify restore command in wx-console to set gui on and to use + only .messages instead of messages. Hopefully this fixes bug + #514. +- Implement load balancing code with multiple drive autochangers. +- Rewrite reservation algorithm again. Rename variables to be + more logical, add HEARTBEAT with Director, allow cancel of + jobs stuck in reservation, add last resourt any_drive. +- Fix seg fault if user labels a drive directly bug #513 +- Remove quotes around Version as it breaks things. +- Merge in Aleksandar Milivojevic's mods to the spec file. +- Apply sparse code fix for raw drives and fifos. Bug 506 +- Thorsten fixed Unicode cd problem with wx-console bug 505. +- Correct reservation system to do a last ditch try + for any mounted volume, then anyone anywhere. +- Updates to ssh-tunnel from Joshua Kugler. +- Added a report.pl program from Jonas Bjorklund. +- Simplify the O_NONBLOCK open() code for tape drives, + and always open nonblocking. +- Do not wait for open() if EIO returned (shouldn't happen). +- Eliminate 3 argument to tape open(). +- Correct the slot # edited in the 3995 Bad autochanger unload + message. +- With -S on bscan (show progress) do not divide by zero. +- Make cancel pthread_cond_signal() pthread_cond_broadcast(). +- When dcr is freed, also broadcast dev->wait_next_vol signal. +- Remove unused code in wait_for_device. +- Make wait_for_device() always return after 60 seconds of wait. +- Use localhost if no network configured +- Eliminated duplicate MaxVolBytes in cat update -- bug 509. +- Update specs to include mysql4 define. +- Return rec->FileIndex in dcr->VolLastIndex for normal + and partial records in read_record(). This allows bscan + to get FileIndex at EOT correct. +- Fix butil.c to correctly set dcr -- fixes seg fault in bls. +- Apply patch supplied by user (slightly modified) to fix + correct detection of holes in block devices and FIFOs. + Bug # 506. +- Apply patch supplied by user (slightly modified) + to fix SD hang with multiple pools and bad client + IP. Fixes bug # 508. +- Add nagios plugin to the examples directory. Submitted by + Christian Masopust. +- Remove warning message about multiple saves of hardlinked files + from find_one.c as it can generate too many warning messages. +- Reset timeout values before select() per patch from + Frank Sweetser for problems with non-blocking sockets. +- Unlink the state file if either reading or writing it gets + errors. Hopefully this will fix Win32 exit problems. +- Get next volume from Scratch pool before creating a volume. +- Set new Pool defaults in Vol when moved from Scratch Pool. +- Remove argument from create_bacula_database for SQLite as it + caused an error. +- Fix reservation so that mutexes are properly applied. +- Rework reservation algorithm so that two drives can be used + at the same time. +- Apply days keyword patch from Alexander.Bergolth at wu-wien.ac.at + If this patch is applied, the number of days can be specified with + 'list nextvol days=xx' + or + 'status dir days=xx' + My use case is to be able to preview the next scheduled job (and the + next tape to be used) on fridays if there are no scheduled jobs during + the weekend. +- Fix font code in gnome2 console user patch. Fixes bug #501. +- Fix malformatted bnet error message that caused seg fault + fixes bug 502 +- Applied user patch to improve README.vc8 in src/win32. +- Ensure that StorageId is stored in Media record when ever possible. +- Remove old code from winservice.cpp +- Break on error in scan. +- Fix typo in signal.c +- Separate read/write DCR in SD. Add jcr->read_dcr. +- Cleanup how find_device() works. +- Remove abs() in bfile.c so that it compiles on Solaris. Bug #491. + +Changes to 1.38.2: +- Fix crash in tray-monitor when daemon disconnects. Bug #479. +- Fix bnet-server bug found on OpenBSD. Bug #486 +- Fix cancel failure bug. Bug #481 +- Fix failure when Pool name has spaces. Bug #487 +- Fix SD crash in autochanger code. Mutex failure. Bug #488 +- Fix a couple of free()s in src/filed/acl.c +- Fix memory overrun in bfile.c in building OS X resource + fork filename. Bug #489 +- Add Pool name to SD status output. +- Add Python install dir for Solaris to configure. Bug #492 + +Changes to 1.38.1: +- Corrected ACL for Solaris (David Duchscher and Attila Fulop). +- Add bacula_mail_summary.sh to examples directory. It makes + a single email summary of any number of jobs. Submitted + by Adrew J. Millar. +- Unmount command now unloads autochanger. +- Fix hang in FD (Martin Simmons) +- Fix Win98 stat() problem in FD (Thorsten Engel) +- Fix update slots which did not clear missing tapes. +- Fix autostart install for FreeBSD (user reported) +- Fix several problems with PostgreSQL scripts (Eric Bollinger) +- Critical: allow restore of the first file of non-portable Win32 backup. +- Important: with muliple concurrent jobs the autochanger could get + confused because of a missing mutex. +- Fix accessing last slot in label and update slots. +- Modify configure.in to add execute option to sqlite3 catalog + scripts. +- Create update_xxx_table_8_to_9 scripts for updatedb +- Move the -lcrypt for PostgreSQL after the PostgreSQL libs in + autoconf/bacula-macros/db.m4 as suggested by user. Fixes bug #457. +- Remove @STATIC_CONS@ from tray-monitor Makefile as suggested + by user. Fixes bug #456. +- AMD64 users see compiler bug warning below!!!!!!!!! + +Major Changes in 1.38: +- Fixed out of order Volumes in restore. +- Improved algorithm for reserving drives in multiple drive + autochangers. Autochange users MUST use the new Autochanger + resource in the Storage daemon. +- There is a new database format that is not compatible + with previous databases. You must upgrade if converting + from 1.36.x. No changes from version 1.37.30. +- The Director, Storage daemon, and File daemons are + Deamons are not compatible with prior versions. + All FDs must be upgraded at the same time. +- Support for ANSI/IBM labels. +- Faster database inserts due to combining the MD5/SHA1 into + the attributes record, eliminating one INSERT/file backed up. +- Python Event support has been added. See below for + configuration and details. The implementation is somewhat minimal, + so the functionality is not complete. The Python interface + has not been extensively tested, so please consider it BETA. +- DVD writing support, using parts, and some new directives in + the Device resource of the Storage configuration file thanks + to Nicolas Boichat. Please note that this code is still + BETA and should be carefully tested before using in + production. +- Seven new options keywords in a FileSet resource: + ignorecase, fstype, hfsplussupport, wilddir, wildfile, regexdir, + and regexfile thanks to Pruben Guldberg). See below for details. +- Restore of all files for a Job or set of jobs even if the file + records have been removed from the catalog. +- Restore of a directory (non-recursive, i.e. only one level). +- Support for TLS (ssl) between all the daemon connections thanks + to Landon Fuller. +- Any Volume in the Pool named Scratch may be reassigned to any + other Pool when a new Volume is needed. +- You may clone a Job and thus write (almost) the same data + to multiple Volumes simultaneously (see below). Actually, + any Job may start any other Job with this mechanism, so it + also be used to group jobs. +- Unicode filename support for Win32 (thanks to Thorsten Engel) +- Volume Shadow Copy support for Win32 thus the capability to + backup exclusively opened files (thanks to Thorsten Engel). + A VSS enabled Win32 FD is available. You must explicitly + turn on VSS with 'Enable VSS = yes' in your FileSet resource. +- New manual format with an index (thanks to Karl Cunningham). +- New Web site format (thanks to Michael Scherer). +- SQLite3 support. +- Web-bacula, previously a separate project by Juan Luis Frances, + is now included in the Bacula GUI release. This is a management + level tool for reporting the state of Bacula jobs. +- The code is now Internationalized so that it can be localized + in native languages. Thanks to Nicolas Boichat. + +New Directives: +- New Job directive 'Prefer Mounted Volumes = yes|no' causes the + SD to select either an Autochanger or a drive with a valid + Volume already mounted in preference. If none is available, + it will select the first available drive. +- New Run directive in Job resource of DIR. It permits + cloning of jobs. To clone a copy of the current job, use + Run = 'job-name level=%l since=\'%s\'' + Note, job-name is normally the same name as the job that + is running but there is no restriction on what you put. If you + want to start the job by hand and use job overrides such as + storage=xxx, realize that the job will be started with the + default storage values not the overrides. The level=%l guarantees + that the chosen level of the job is the same, and the since=... + ensures that the job uses *exactly* the same time/date for incremental + and differential jobs. The since=... is ignored when level=Full. + A cloned job will not start additional clones, so it is not possible + to recurse. +- New Options keywords in a FileSet directive (backported to 1.36.3): + - WildDir xxx + Will do a wild card match against directories (files will not + be matched). + - WildFile xxx + Will do a wild card match against files (directories will not + be matched). + - RegexDir xxx + Will do a regular expression match against directories (files + will not be matched). + - RegexFile xxx + Will do a regular expression match against files( directories + will not be matched). + - IgnoreCase = yes | no + Will ignore case in wild card and regular expression matches. + This is handy for Windows where filename case is not significant. + - FsType = string + where string is a filesystem type: ext2, jfs, ntfs, proc, + reiserfs, xfs, usbdevfs, sysfs, smbfs, iso9660. For ext3 + systems, use ext2. You may have multiple fstype directives + and thus permit multiple filesystem types. If the type + specified on the fstype directive does not match the + filesystem for a particular directive, that directory will + not be backed up. This directive can be used to prevent + backing up non-local filesystems. + - HFS Plus Support = yes | no + If set, Mac OS X resource forks will be saved and restored. +- Label Type = ANSI | IBM | Bacula + Implemented in Director Pool resource and in SD Device resource. + If it is specified in the SD Device resource, it will take + precedence over the value passed from the Director to the SD. +- Check Labels = yes | no + Implemented in the SD Device resource. If you intend to read + ANSI or IBM labels, this *must* be set. Even if the volume + is not ANSI labeled, you can set this to yes, and Bacula will + check the label type. +- Scripts Directory = <directory> name. Defines the directory from + which Bacula scripts will be called for events. In fact, Bacula + appends this name to the standard Python list of search directories, + so the script could also be in any of the Python system directories. +- In FileSet, you can exclude backing up of hardlinks (if you have + a lot, it can be very expensive), by using: + HardLinks = no + in the Options section. Patch supplied by David R Bosso. Thanks. +- MaximumPartSize = bytes (SD, Device resource) + Defines the maximum part size. +- Requires Mount = Yes/No (SD, Device resource) + Defines if the device require to be mounted to be read, and if it + must be written in a special way. If it set, the following directives + must be defined in the same Device resource: + + Mount Point = directory + Directory where the device must be mounted. + + Mount Command = name-string + Command that must be executed to mount the device. Before the command + is executed, %a is replaced with the Archive Device, and %m with the + Mount Point. + + Unmount Command = name-string + Command that must be executed to unmount the device. Before the + command is executed, %a is replaced with the Archive Device, and + %m with the Mount Point. + + Write Part Command = name-string + Command that must be executed to write a part to the device. Before + the command is executed, %a is replaced with the Archive Device, %m + with the Mount Point, %n with the current part number (0-based), + and %v with the current part filename. + + Free Space Command = name-string + Command that must be executed to check how much free space is left + on the device. Before the command is executed, %a is replaced with + the Archive Device, %m with the Mount Point, %n with the current part + number (0-based), and %v with the current part filename. +- Write Part After Job = Yes/No (DIR, Job Resource, and Schedule Resource) + If this directive is set to yes (default no), a new part file will be + created after the job is finished. +- A pile of new Directives to support TLS. Please see the TLS chapter + of the manual. + +New Commands: +- 'python restart' restarts the Python interpreter. Rather brutal, make + sure no Python scripts are running. This permits you to change + a Python script and get Bacula to use the new script. + +New configure options: +- --with-libintl-prefix for defining alternate locations for + the NLS internationalization libraries. Not normally required. +- --datadir for defining where the language files will be installed + required only if you do not want the default /usr/share. + +Items to note!!! +- The Storage daemon now keeps track of what tapes it is using + (was not the case in 1.36.x). This means that you must be much + more careful when removing tapes and putting up a new one. In + general, you should always do a 'unmount' prior to removing a + tape, and a 'mount' after putting a new one into the drive. +- If you use an Autochanger, you MUST update your SD conf file + to use the new Autochanger resource. Otherwise, certain commands + such as 'update slots' may not work. +- You must add --with-python=[DIR] to the configure command line + if you want Python support. Python 2.2, 2.3 and 2.4 should be + automatically detected if in the standard place. +- When linking with --with-python, there are a few warnings that + can be ignored. +- You must either create a new catalog database or upgrade your + old database. After installation, run from your scripts + directory: + + ./upgrade_bacula_tables + + You can also find this script in the <bacula-source>/src/cats + directory. +- The Director, Storage daemon, and File daemons are + Deamons are not compatible with prior versions. + All FDs must be upgraded at the same time. +- You must add --with-openssl to the configure command line if + you want TLS communications encryption support. +- Disk seeking during restores does not yet work correctly in + all cases, so it is turned off. +- Note, with gcc (GCC) 4.0.1 20050727 (Red Hat 4.0.1-5) on an + AMD64 CPU running 64 bit CentOS4, there is a compiler bug that + generates bad code that causes Bacula to segment fault. + Typically you will see this in the Storage daemon first. The + solution is to compile Bacula ensuring that no optimization is + turned on (normally it is -O2). + This same compiler bug has been reported and confirmed with + gcc (GCC) 4.0.2 20050901 (prerelease) (SUSE Linux) running on + an AMD64 CPU. This for the moment, I would recommend that all + users of GCC 4.0.1 or greater turn off all optimization when + compiling. + + +Other Items Fixed: +- Security fixes for temp files created in mtx-changer, during + ./configure, and during making of Rescue disk. +- A new script, dvd-handler, in the scripts directory, + which is designed to be used as parameters to Write Part Command and + Free Space Command. They need the dvd+rw-tools to be installed + (http://fy.chalmers.se/~appro/linux/DVD+RW/) AND, the growisofs + program must be patched using the + <bacula-source>/patches/dvd+rw-tools-5.21.4.10.8.bacula.patch + You must have Python installed to run the scripts. +- Part files support: File volumes can now be split into multiple + files, called 'parts'. +- For the details of the Python scripting support, please see the new + Python Scripting chapter in the manual. +- The default user/group for the Director and Storage daemon installed + by rpms is bacula/bacula, thus you may need to add additional permissions + to your database, or modify the permissions of the tape drive. If + 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* +through the new Bacula-News-System. + +Its file-based, no fancy database need. +;;; diff --git a/docs/home-page/fr/pages/bugs.php b/docs/home-page/fr/pages/bugs.php new file mode 100644 index 00000000..3279ed9a --- /dev/null +++ b/docs/home-page/fr/pages/bugs.php @@ -0,0 +1,83 @@ + + + + + + + + + + + + +
+ Rapport de Bug +
+

Comment rapporter un bug?

+ Avant de rapporter un bug, merci de vérifier qu'il s'agisse bien d'un + bug et non d'une demande de support (voir la rubrique support du menu). +

+ Le projet Bacula possède maintenant un système de rapport de bug + implémenté par Dan Langille et hébergé sur son serveur. Il s'agit d'une + application web facile à utiliser que nous vous recommandons + d'essayer. Vous pouvez soumettre un bug ou voir la liste des bugs + ouverts ou fermés sur la page: +

+

+ http://bugs.bacula.org +

+

+ Pour consulter les rapports de bugs, vous pouvez vous logguer en + utilisant l'utilisateur anonymous et le mot de passe + anonymous. +

+

+ Pour soumettre un bug, vous devez créer un compte. +

+

+ La plupart des problèmes soulevés à propos de Bacula sont des questions + de support, donc si vous n'êtes pas sûr si votre problème est un bug, + merci de consulter la page de support sur ce site afin d'obtenir + les adresses des listes d'emails. +

+ + +

Informations nécessaires à l'ouverture d'un bug

+

+ Pour que nous puissions répondre à un rapport de bug, nous avons + normalement besoin d'un minimum d'informations, que vous pouvez entrer + dans les champs appropriés du système de rapport de bug: +

+
    +
  • votre système d'exploitation
    • +
  • la version de Bacula que vous utilisez
    • +
  • une description claire + et concise du problème (en anglais)
    • +
  • Si vous avez un plantage, un disfonctionnement ou quelque chose + de similaire, vous devez inclure dans votre description les messages + de sorties de Bacula.
    • +
+

+ Si vous avez des problème de bande, merci d'inclure la marque et le + type de lecteur de bandes que vous utilisez. Assurez-vous également + d'avoir exécuté la commande btape "test". +

+

+ Les 2 premiers items peuvent être remplis en envoyant une copie de + votre fichier config.out, qui est localisé dans le répertoire + principal des sources de Bacula, après avoir exécuté la + commande ./configure. +

+

+ Vous pouvez également ajouter une copie de vos fichiers de + configuration (tout particulièrement bacula-dir.conf) qui est + nécessaire parfois. Si vous pensez qu'il s'agit d'un problème de + configuration, n'hésitez pas à nous les envoyer si nécessaire. +

+
+ Merci de lire également ce petit + + Bug-Report-HowTo (en français). +
+ diff --git a/docs/home-page/fr/pages/documentation.php b/docs/home-page/fr/pages/documentation.php new file mode 100644 index 00000000..14233c89 --- /dev/null +++ b/docs/home-page/fr/pages/documentation.php @@ -0,0 +1,74 @@ + + + + + + + + + + + + + + + + + + + + +
+ Documentation de Bacula +
+
    +
  • Tutorial +
    (démarrer ici après avoir installé Bacula) +
    • +
+ 		+ +
+   + + +   + +
+   + + +   + +
+ diff --git a/docs/home-page/fr/pages/donations.php b/docs/home-page/fr/pages/donations.php new file mode 100644 index 00000000..b38f7c1f --- /dev/null +++ b/docs/home-page/fr/pages/donations.php @@ -0,0 +1,64 @@ + + + + + + +
+ Donations Received +
+ + + + +
+ + 0 && $news_counter < $max_news) { + // next line + $line = array_pop($lines); + + // start of news + if(eregi("^[a-z0-9]+;;;", $line)) { + // news header + list($author,$date,$time) = explode(";;;",$line); + + // news subject + $subject = array_pop($lines); + printf('', $subject); + printf(''); + printf(''); + printf('', $date, $time, $author); + printf(''); + printf(''); + $news_counter++; + continue; + } + + // news content + printf('%s', $line); +} +?> +
%s
');
+
+                continue;
+        }
+
+        // end of news
+        if(eregi("^;;;", $line)) {
+                printf('
%s - %s, %s
+
+ diff --git a/docs/home-page/fr/pages/feature-request.php b/docs/home-page/fr/pages/feature-request.php new file mode 100644 index 00000000..9d2acd56 --- /dev/null +++ b/docs/home-page/fr/pages/feature-request.php @@ -0,0 +1,80 @@ + + + + + + + + + +
Demande de fonctionnalité
+

+ Par le passé, les utilisateurs envoyaient des demandes de + fonctionnalité de manière informelle par mail et je les collectais. + Puis dès que la version courante était publiée, je publiais la liste + des nouvelles fonctionnalités pour que les utilisateurs votent pour + les prochaines fonctionnalités à implémenter. +

+

+ Maintenant que Bacula est devenu un plus gros projet, je voulais + formaliser un peu plus le procédé. Le changement principal va être de + demander aux utilisateurs de penser avec attention à leur + fonctionnalité, et de l'envoyer grâce à un formulaire de demande de + fonctionnalité. Un formulaire quasiment vide est montré ci-dessous + ainsi qu'un exemple d'un formulaire rempli. +

+

+ Dès que je reçois et approuve la demande de fonctionnalité, ou + possiblement demande des modifications, je l'ajoute au fichier des + projets, qui contient la liste de toutes les demande de fonctionnalité + ouvertes. +

+ +

+ Les demandes de fonctionnalités doivent rédigées en anglais. +

+

Feature Request Form

+ 
+Item n:   One line summary ...
+  Origin: Name and email of originator.
+  Date:   Date submitted (e.g. 28 October 2005)
+  Status:
+
+  What:   More detailed explanation ...
+
+  Why:    Why it is important ...
+
+  Notes:  Additional notes or features ...
+
+ +

An Example Feature Request

+ 
+Item 1:   Implement a Migration job type that will move the job
+          data from one device to another.
+  Date:   28 October 2005
+  Origin: Sponsored by Riege Sofware International GmbH. Contact:
+          Daniel Holtkamp 
+  Status: Partially coded in 1.37 -- much more to do. Assigned to
+          Kern.
+
+  What:   The ability to copy, move, or archive data that is on a
+          device to another device is very important.
+
+  Why:    An ISP might want to backup to disk, but after 30 days
+          migrate the data to tape backup and delete it from
+          disk.  Bacula should be able to handle this
+          automatically.  It needs to know what was put where,
+          and when, and what to migrate -- it is a bit like
+          retention periods.  Doing so would allow space to be
+          freed up for current backups while maintaining older
+          data on tape drives.
+
+  Notes:  Migration could be triggered by:
+           Number of Jobs
+           Number of Volumes
+           Age of Jobs
+           Highwater size (keep total size)
+           Lowwater mark
+
+
+ diff --git a/docs/home-page/fr/pages/home.php b/docs/home-page/fr/pages/home.php new file mode 100644 index 00000000..ada4d31b --- /dev/null +++ b/docs/home-page/fr/pages/home.php @@ -0,0 +1,59 @@ + + + + + + + + +
+ Bacula® - La solution de sauvegarde par le réseau +
+ Bacula est un ensemble de programmes qui vous permet de gérer vos + sauvegardes, restaurations ou vérifications de données d'un ordinateur + sur un réseau hétérogène. +
+ +
+ En termes techniques, il s'agit d'un programme de sauvegarde + client/serveur. +
+ +
+ Bacula est relativement facile d'utilisation et efficace, tout en offant + de nombreuses fonctions avancées de gestion de stockage qui facilitent la + recherche et la restauration de fichiers perdus ou endommagés +
+ +
+ La plupart du code source de Bacula a été publiée sous une version + quelque peu modifiée de la license GPL version 2. Pour toute + information complémentaire sur la license, merci de suivre le lien du + menu. +
+ +
Le lien Documentation pointe sur une page qui permet d'accéder à + toutes les documentations de Bacula disponibles (HTML, PDF et TGZ) que ce + soit pour la dernière version officielle ou bien pour le code + actuellement en cours de développement dans le CVS SourceForge. + La version de développement du manuel contient plus de documentation, mais + aussi la documentation des dernières fonctionnalités qui ne sont pas + encore incluses dans la dernière version publiée. +
+ Le guide du développeur présente des informations importantes pour les + utilisateurs qui veulent contribuer au projet Bacula. +
+ +
Bacula est hébergé sur + http://sourceforge.net/projects/bacula d'où vous pouvez télécharger + le logiciel. +
+ +
Vous pouvez également utiliser les liens du menu pour accéder + directement à la version courante ou bien à toutes les versions déjà + publiées sur SourceForge. + +
+ + diff --git a/docs/home-page/fr/pages/license.php b/docs/home-page/fr/pages/license.php new file mode 100644 index 00000000..2dc6e2ed --- /dev/null +++ b/docs/home-page/fr/pages/license.php @@ -0,0 +1,41 @@ + + + + + + + + +
+ Bacula Copyright, Trademark, and Licenses +
+ There are a number of different licenses that are used in + Bacula. +

GPL

+ The vast bulk of the code is released under the + + GNU General Public License version 2. + Most of this code is copyrighted: + Copyright (C) 2000-2005 Kern Sibbald and John Walker. +

Portions may be copyrighted by other people (ATT, the + Free Software Foundation, ...). +

LGPL

+ Some of the Bacula library source code is released under the + GNU Lesser General Public License. + This permits third parties to use these parts of our code in + their proprietary programs to interface to Bacula. +

Public Domain

+ Some of the Bacula code has been released to the public domain. + E.g. md5.c, SQLite. +

Trademark

+ Bacula®is a registered trademark of Kern Sibbald and John + Walker. + +

We have done this to ensure that any variant of Bacula will + be exactly compatible with the program that we have released. + The use of the name Bacula is restricted to software systems + that agree exactly with the program presented here. +

+
+ + diff --git a/docs/home-page/fr/pages/listlic.php b/docs/home-page/fr/pages/listlic.php new file mode 100644 index 00000000..3d437232 --- /dev/null +++ b/docs/home-page/fr/pages/listlic.php @@ -0,0 +1,45 @@ + + + + + + + + +
+ Support Professionnel pour Bacula +
+

+ Ces personnes sont des entrepreneurs indépendants. +
+ Nous ne prenons aucune responsabilité pour leurs actions lorsque vous + faîtes appel à eux, mais nous apprécions tout retour d'expérience, + positif ou négatif. +

+

+ Etre listé sur la page professionelle de Bacula est offert comme un + service, mais sans aucune garantie. +

+

+ Nous nous réservons le droit de décider raisonnablement qui doit être + ajouté ou supprimé de cette page. +

+

+ Pour être listé, vous devez avoir une bonne connaissance de Bacula et + reconnue (c'est à dire être développeur, contribuer au code/patches, + être inscrit aux listes bacula-users, bacula-users, de préférence + avoir un site web...). +

+

+ Les personnes qui sont listées sont d'accord pour mettre à jour leurs + informations de manière régulière. +
+ Toute personne listée avec des informations erronées sera sujette à + être retirée de la liste. +

+

+ Si vous souhaitez être listé sur cette page, merci de rentrer en + contact avec Kern Sibbald. +

+
+ diff --git a/docs/home-page/fr/pages/login.php b/docs/home-page/fr/pages/login.php new file mode 100644 index 00000000..31690ee3 --- /dev/null +++ b/docs/home-page/fr/pages/login.php @@ -0,0 +1,24 @@ + + + + + + + diff --git a/docs/home-page/fr/pages/logout.php b/docs/home-page/fr/pages/logout.php new file mode 100644 index 00000000..63bd3f85 --- /dev/null +++ b/docs/home-page/fr/pages/logout.php @@ -0,0 +1,12 @@ + + + + + + + diff --git a/docs/home-page/fr/pages/maillists.php b/docs/home-page/fr/pages/maillists.php new file mode 100644 index 00000000..f38b7021 --- /dev/null +++ b/docs/home-page/fr/pages/maillists.php @@ -0,0 +1,145 @@ + + + + + + + + +
+ Listes d'emails +
+

+ Le projet Bacula propose plusieurs mailing listes qui sont + décrites ci-dessous, avec les liens pour s'inscrire, se désinscrire ou + modifier son compte. + Pour obtenir des informations générales au sujet de ces listes, merci + de regarder + les listes d'email Bacula sur SourceForge. +

+

+ Pour consulter les mails archivés, regarder en bas de cette page. +

+ +

bacula-announce

+

+ La liste bacula-announce est une liste avec peu d'envois et en + consultation seulement pour les utilsateurs qui souhaitent être + informés des évènements importants (bugs importants, nouvelles + versions...). Nous recommandons à tous les utilisateurs de s'inscrire + sur cette liste. Pour ce faire, suivre les instructions sur la page + + Liste Bacula Announce Inscription / Désinscription / Modification. +
+ Merci de ne pas envoyer de mail directement à cette liste. +

+

+ Il est également possible de recevoir un mail de notification à chaque + fois qu'un nouveau paquet est versionné sur SourceForge. Ceci peut + être fait en allant sur la page du projet Bacula + sur Sourceforge et en cliquant sur la petite lettre ou l'icône + mail + dessous le titre Monitor dans la ligne correspondant au paquet + que vous voulez surveiller. +

+ +

bacula-users

+

+ La liste bacula-users est le forum général pour poser des + questions au sujet de Bacula ou répondre aux questions des autres + utilisateurs. Le volume de cette liste est généralement modéré, mais + peut varier. Tous les utilisateurs sont encouragés à y souscrire et y + participer. +
+ A cause du nombre croissant de spams, vous devez vous enregistrer + avant de pouvoir envoyer un mail à cette liste. Pour s'enregistrer, + merci de suivre les instructions sur la page Liste + Bacula Users Inscription / Désinscription / Modification. +

+

+ Pour envoyer un mail à la liste Bacula User, utilisez l'adresse + suivante:bacula-users at lists.sourceforge.net. +
+ L'adresse ci-dessus a été modifiée pour se prémunir contre les + techniques basiques utilisées par les spammeurs. Pour l'utiliser, vous + devez remplacer le at par le symbole @. +

+ +

bacula-devel

+

+ La liste bacula-devel permet aux utilisateurs de communiquer + directement avec les développeurs de Bacula. Le volume de mail est + normalement faible, mais peut varier. +
+ Pour s'inscrire à cette liste, merci de suivre ce lien: + + Liste Bacula Developers Inscription / Désinscription / Modification + . +

+

+ Pour envoyer un mail à la liste Bacula User, utilisez l'adresse + suivante:bacula-devel at lists.sourceforge.net. +
+ L'adresse ci-dessus a été modifiée pour se prémunir contre les + techniques basiques utilisées par les spammeurs. Pour l'utiliser, vous + devez remplacer le at par le symbole @. +

+ +

bacula-bugs

+

+ La liste bacula-bugs permet aux utilisateurs d'être notifiés + quand un nouveau bug est enregistré sur: http://bugs.bacula.org. +
+ Merci de ne pas envoyer de mail de rapport de bug directement à cette + liste, mais d'utiliser la base de données de bugs mentionné ci-dessus. +
+ Pour s'inscrire à cette liste, merci de suivre les instructions sur la + page suivante: + + Liste Bacula Bugs Inscription / Désinscription / Modification + . +

+ +

bacula-beta

+

+ La liste bacula-beta est une liste en réception seulement qui + permet aux packagers et aux utilisateurs qui le veulent d'être + notifiés quand une nouvelle version est en préparation ou prête. +
+ Merci de ne pas envoyer de mail directement à cette liste. +
+ Pour s'inscrire à cette liste, merci de suivre les instructions sur la + page suivante: + + Liste Bacula Beta Inscription / Désinscription / Modification + . +

+ +

bacula-commits

+

+ La liste bacula-commits est une liste en réception seulement + pour les utilisateurs qui souhaitent recevoir les différences de + chaque modification sur le dépôt CVS. +
+ Merci de ne pas envoyer de mail directement à cette liste. +
+ Pour s'inscrire à cette liste, merci de suivre les instructions sur la + page suivante: + + Liste Bacula Commits Inscription / Désinscription / Modification + . +

+ +

Archives

+

+ La plupart des listes d'email ci-dessus sont archivées sur Source + Forge, mais ils sont également archivés sur Gmane, qui propose de + meilleures fonctionnalités. Les archives Gmane sont consultables sur: + + http://news.gmane.org/search.php?match=bacula. +

+
+ diff --git a/docs/home-page/fr/pages/makedonation.php b/docs/home-page/fr/pages/makedonation.php new file mode 100644 index 00000000..3da09b06 --- /dev/null +++ b/docs/home-page/fr/pages/makedonation.php @@ -0,0 +1,90 @@ + + +
+ + + + + +
+ + + + + + + + +
+ Contribuer au projet Bacula +
+

+ Bien que nous parlons de logiciels libres, en fait, les logiciels open + sources tel que Bacula ne sont pas développés sans aucun coût. Le + logiciel peut être gratuit pour l'utilisateur, mais il ne l'est pas + pour le ou les développeurs, ni en terme de temps, ni en terme de coût + financier. +

+

+ Par exemple, depuis le début du projet Bacula en janvier 2000 jusqu'à + octobre 2005, j'ai (Kern) dépensé approximativement 8 000 $ + par an pour l'achat d'ordinateurs, de lecteurs de bandes, de dépenses + de communications, d'électricité, de licenses de logiciels et d'autres + dépenses. Je ne suis pas en train de me plaindre et je suis heureux + d'avoir pû faire face à ces dépenses. De plus, je n'ai aucun désir + d'être remboursé de ces frais. +

+

+ Bacula est maintenant un projet assez mature, et pour assurer sa + survie à long terme, je crois qu'il est temps que Bacula commence à + être autonome tant financièrement que pour les développements. +

+

+ Il y a plusieurs façons de contribuer au projet Bacula, parmi + lesquelles : donnéer des idées, participer au support pour les + utilisateurs, faire des revues de documentation, des traductions, + programmer et contribuer au code, tester les nouvelles versions, + héberger des services, tester des machines, donner des équipements + nécessaires, apporter un soutien financier. +

+

+ Avant, tout mise à part la dernière (soutien financier) était + possible. Il vous est maintenant possible d'apporter une aide + financière au projet Bacula. Tous les fonds récoltés vont être + utilisés pour aider d'avantage le projet Bacula à couvrir les dépenses + engagées par le projet (pas de salarié). Les exemples de dépenses sont + le matériel, les licences logicielles (oui Micro$oft), et possiblement + une partie des dépenses liés aux voyages et conférences. +

+

+ Les contributions ne devraient pas être déductibles aux USA car Bacula + est basé en Suisse. +

+

+ Si vous êtes une organisation gouvernementale ou une association à but + non lucratif et ne pouvez faire de dons, vous pouvez tout de même + payer une rémunération (non-obligatoire) pour tous les binaires de + Bacula que vous téléchargez. En faisant en sorte que ces binaires + pré-construits et pré-testés soient disponibles, nous fournissons aux + utilisateurs qui les téléchargent un service supplémentaire, qui + mérite une considération particulière pour faire une contribution ou + payer une "rémunération pour la licence". +

+

+ Pour faire une contribution, merci de cliquer sur le bouton + donate en haut de la page, et votre transaction va être + sécurisée et confirmée directement par PayPal. Si vous contribuez, ou + avez des questions, merci de m'envoyer un mail (en anglais) + directement à kerl at sibbald dot com. +

+

+ Si vous avez besoin d'un reçu, je peux vous en envoyer un, mais afin + de limiter mon travail administratif, je vous demande aimablement de + faire un don d'au moins 200 $ avant de demander un reçu. Pour + obtenir votre reçu, il vous suffit simplement de m'envoyer par email + le nom exact qui doit apparaître sur le reçu ainsi que l'adresse mail, + le montant de votre contribution, et le projet que vous supportez (ou + simplement Bacula development). +

+
+ diff --git a/docs/home-page/fr/pages/news.php b/docs/home-page/fr/pages/news.php new file mode 100644 index 00000000..68497508 --- /dev/null +++ b/docs/home-page/fr/pages/news.php @@ -0,0 +1,64 @@ + + + + + + +
+ Actualités +
+ + + + +
+ + 0 && $news_counter < $max_news) { + // next line + $line = array_pop($lines); + + // start of news + if(eregi("^[a-z0-9]+;;;", $line)) { + // news header + list($author,$date,$time) = explode(";;;",$line); + + // news subject + $subject = array_pop($lines); + printf('', $subject); + printf(''); + printf(''); + printf('', $date, $time, $author); + printf(''); + printf(''); + $news_counter++; + continue; + } + + // news content + printf('%s', $line); +} +?> +
%s
');
+
+		continue;
+	}
+
+	// end of news
+	if(eregi("^;;;", $line)) {
+		printf('
%s - %s, %s
spacer
+
+ diff --git a/docs/home-page/fr/pages/professional.php b/docs/home-page/fr/pages/professional.php new file mode 100644 index 00000000..57110a20 --- /dev/null +++ b/docs/home-page/fr/pages/professional.php @@ -0,0 +1,319 @@ + + + + + + + + + + + +
+ Support Professionnel pour Bacula +
+

+ Les personnes suivantes sont des entrepreneurs indépendants. Ils ont + tous travaillé avec Bacula et nous sommes heureux de lister leur nom + ici comme un service, mais sans garanties. +
+ Merci de lire cette courte 'licence' à + propos du support professionnel. Tous les noms ont été revus et + approuvés. +
+ Toutes les adresses email ont été étendues avec un tag 'NOSPAM'. Merci + de le supprimer avant d'envoyer un email. +

+

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ +
Alixen + Gilles Polart-Donat
+ 2 rue Jean Rostand
+ 91893 Orsay CEDEX, France
+ +33 01 69 85 24 13
+
+ http://www.alixen.fr +
+ Arden Group Inc + + Roger Berry
+ 5026 NE Clackamas
+ Portland, OR 97213 USA
+ +1(971)223-3987
+
+ http://www.ardengrp.com
+
+ Axiom Networking + + Angus Jordan
+ 9235 215th St, Langley BC, Canada
+ +1-604-888-6162
+
+ We offer all types of IT related support services. Platform support: Linux,
+ Windows 2000/2003 etc. Lots of experience with Bacula, DBMail, Nagios,
+ Postfix, Qmail, qpopper, BIND (8/9), and MANY others.
+
+ http://www.axiomnetworking.ca
+
+ BSDCan + + Dan Langille
+ Suite 474
+ 900 Greenbank Road
+ Ottawa, ON K2J 4P6
+ +1 613 863 9741
+
+ http://www.langille.org/ +
+ Instant Root HB + + Info-Mail
+ Box 1823
+ SE-58117 Linköping, Sweden
+
+ Instant Root HB is a company specialized in Unix systems administration, network + design and implementation, as well as education in various computer-related fields.
+
+ http://www.instant-root.com
+
+ IT-Service Lehmann + + Arno Lehmann
+ Wittekamp 2
+ 30177 Hannover
+ Germany
+ +49 (0) 511 69099508
+ +49 (0) 160 92008971 (mobile)
+
+ Storage, Communication, Backup and Monitoring using + Open-Source solutions. Services from + network design to system administration and + user education, with a focus on Small + Businesses looking for cost-effective solutions. +
+ http://www.its-lehmann.de +
+ KDB Konsult AB + + Mats Vilhelmsson
+ Tel: +46 708 901042
+
+ Backup hosting - Internet backups, Bacula training, installations and support.
+
+ http://www.kdb.se
+
+ L. Strappazon + + Ludovic Strappazon
+ Strasbourg, France
+ +33 660 954735
+
+ I offer engineering services and training around storage and Backup. + Planning and scaling of your hardware installation, Bacula implementation. +
+ MATRIX-Computer + + MATRIX-Computer GmbH
+ Dachauer Str. 44
+ 80335 München
+ Germany
+ + +49-89-922 996 80
+
+ We are a team of software developers with experience in C++, Windows, PHP, + Linux and more. We have done lots of the Think Tools software.
+
+ http://www.matrix-computer.com
+
+ NETWAYS GmbH + + NETWAYS GmbH
+ Deutschherrnstrasse 47a
+ 90429 Nürnberg
+ Germany
+
+ Telephone +49 911 92885-0
+ Fax +49 911 92885-77
+
+
+ We support our customers managing complex and + heterogeneous networks. Our services and + solutions, based on Open Source software, help + you run your servers and applications + failure-free. Special focus on Nagios, Bacula, + Request Tracker, and cluster solutions.
http://www.netways.de
+
+ raptus ag + + raptus ag
+ moderne kommunikation
+ burgweg 1
+ 2563 ipsach -- switzerland
+
+ Telephone +41 (0)32 332 9200
+ Fax +41 (0)32 332 9201
+
+
+ Modern communications, Internet projects and IT services since 1996! + Specialized in heterogeneous networks (linux, mac, windows) and open + source solutions. +
+ http://www.raptus.com
+
+ Sine Nomine Associates + + Services Sales Dept.
+ US:
+   43596 Blacksmith Square
+   Ashburn, VA 20147 USA
+   +1 703 723 6673
+
+ EMEA:
+   Na Dvorcich 17/Na Vrasni 18
+   CZ - Praha 4, 14000
+   Czech Republic
+
+ Design and implementation of system management tools and infrastructure,
+ from small systems to enterprise-wide implementations on global scale.
+ Special focus on Bacula for enterprise-class systems and mainframe.
+
+ http://www.sinenomine.net
+
+ WinFix.IT + + Jo at WinFix.IT
+
+   In and around Leuven and Brussels (Belgium) +
+   +32 (0)478-33 76 27
+
+ Set up of SAMBA File and Print servers/domain controllers, mail + servers (Postfix) with spam/virus killers + (Spamassassin/Amavis/Clamav/BitDefender) + and backup (with Bacula of course). Network monitoring with Nagios. +
+ http://www.WinFix.IT
+
+
+ diff --git a/docs/home-page/fr/pages/projects.php b/docs/home-page/fr/pages/projects.php new file mode 100644 index 00000000..a1b400b2 --- /dev/null +++ b/docs/home-page/fr/pages/projects.php @@ -0,0 +1,816 @@ + + + + + + +
+ +
+                
+Projects:
+                     Bacula Projects Roadmap 
+                       07 December 2005
+                    (prioritized by user vote)
+
+Summary:
+Item  1:  Implement data encryption (as opposed to comm encryption)
+Item  2:  Implement Migration that moves Jobs from one Pool to another.
+Item  3:  Accurate restoration of renamed/deleted files from
+Item  4:  Implement a Bacula GUI/management tool using Python.
+Item  5:  Implement Base jobs.
+Item  6:  Allow FD to initiate a backup
+Item  7:  Improve Bacula's tape and drive usage and cleaning management.
+Item  8:  Implement creation and maintenance of copy pools
+Item  9:  Implement new {Client}Run{Before|After}Job feature.
+Item 10:  Merge multiple backups (Synthetic Backup or Consolidation).
+Item 11:  Deletion of Disk-Based Bacula Volumes
+Item 12:  Directive/mode to backup only file changes, not entire file
+Item 13:  Multiple threads in file daemon for the same job
+Item 14:  Implement red/black binary tree routines.
+Item 15:  Add support for FileSets in user directories  CACHEDIR.TAG
+Item 16:  Implement extraction of Win32 BackupWrite data.
+Item 17:  Implement a Python interface to the Bacula catalog.
+Item 18:  Archival (removal) of User Files to Tape
+Item 19:  Add Plug-ins to the FileSet Include statements.
+Item 20:  Implement more Python events in Bacula.
+Item 21:  Quick release of FD-SD connection after backup.
+Item 22:  Permit multiple Media Types in an Autochanger
+Item 23:  Allow different autochanger definitions for one autochanger.
+Item 24:  Automatic disabling of devices
+Item 25:  Implement huge exclude list support using hashing.
+
+
+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 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
+          the File daemon level is essential. 
+          Data encryption encrypts the data in the File daemon and
+          decrypts the data in the File daemon during a restore.
+
+  Why:    Large sites require this.
+
+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 working in 1.39, more to do. Assigned to
+          Kern.
+
+  What:   The ability to copy, move, or archive data that is on a
+          device to another device is very important. 
+
+  Why:    An ISP might want to backup to disk, but after 30 days
+          migrate the data to tape backup and delete it from
+          disk.  Bacula should be able to handle this
+          automatically.  It needs to know what was put where,
+          and when, and what to migrate -- it is a bit like
+          retention periods.  Doing so would allow space to be
+          freed up for current backups while maintaining older
+          data on tape drives.
+
+  Notes:   Riege Software have asked for the following migration
+           triggers:
+           Age of Job
+           Highwater mark (stopped by Lowwater mark?)
+                            
+  Notes:  Migration could be additionally triggered by:
+           Number of Jobs
+           Number of Volumes
+
+Item  3:  Accurate restoration of renamed/deleted files from
+          Incremental/Differential backups
+  Date:   28 November 2005
+  Origin: Martin Simmons (martin at lispworks dot com)
+  Status:
+
+  What:   When restoring a fileset for a specified date (including "most
+          recent"), Bacula should give you exactly the files and directories
+          that existed at the time of the last backup prior to that date.
+
+          Currently this only works if the last backup was a Full backup.
+          When the last backup was Incremental/Differential, files and
+          directories that have been renamed or deleted since the last Full
+          backup are not currently restored correctly.  Ditto for files with
+          extra/fewer hard links than at the time of the last Full backup.
+
+  Why:    Incremental/Differential would be much more useful if this worked.
+
+  Notes:  Item 14 (Merging of multiple backups into a single one) seems to
+          rely on this working, otherwise the merged backups will not be
+          truly equivalent to a Full backup.  
+
+          Kern: notes shortened. This can be done without the need for 
+          inodes. It is essentially the same as the current Verify job,
+          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: Lucus is working on this for Python GTK+.
+
+  What:   Implement a Bacula console, and management tools
+          using Python and Qt or GTK.
+
+  Why:    Don't we already have a wxWidgets GUI?  Yes, but
+          it is written in C++ and changes to the user interface
+          must be hand tailored using C++ code. By developing
+          the user interface using Qt designer, the interface
+          can be very easily updated and most of the new Python       
+          code will be automatically created.  The user interface
+          changes become very simple, and only the new features
+          must be implement.  In addition, the code will be in
+          Python, which will give many more users easy (or easier)
+          access to making additions or modifications.
+
+ Notes:   This is currently being implemented using Python-GTK by       
+          Lucas Di Pentima 
+
+Item 5:   Implement Base jobs.
+  Date:   28 October 2005
+  Origin: Kern
+  Status: 
+  
+  What:   A base job is sort of like a Full save except that you 
+          will want the FileSet to contain only files that are
+          unlikely to change in the future (i.e.  a snapshot of
+          most of your system after installing it).  After the
+          base job has been run, when you are doing a Full save,
+          you specify one or more Base jobs to be used.  All
+          files that have been backed up in the Base job/jobs but
+          not modified will then be excluded from the backup.
+          During a restore, the Base jobs will be automatically
+          pulled in where necessary.
+
+  Why:    This is something none of the competition does, as far as
+          we know (except perhaps BackupPC, which is a Perl program that
+          saves to disk only).  It is big win for the user, it
+          makes Bacula stand out as offering a unique
+          optimization that immediately saves time and money.
+          Basically, imagine that you have 100 nearly identical
+          Windows or Linux machine containing the OS and user
+          files.  Now for the OS part, a Base job will be backed
+          up once, and rather than making 100 copies of the OS,
+          there will be only one.  If one or more of the systems
+          have some files updated, no problem, they will be
+          automatically restored.
+
+  Notes:  Huge savings in tape usage even for a single machine.
+          Will require more resources because the DIR must send
+          FD a list of files/attribs, and the FD must search the
+          list and compare it for each file to be saved.
+
+Item  6:  Allow FD to initiate a backup
+  Origin: Frank Volf (frank at deze dot org)
+  Date:   17 November 2005
+  Status:
+
+   What:  Provide some means, possibly by a restricted console that
+          allows a FD to initiate a backup, and that uses the connection
+          established by the FD to the Director for the backup so that
+          a Director that is firewalled can do the backup.
+
+   Why:   Makes backup of laptops much easier.
+
+Item  7:  Improve Bacula's tape and drive usage and cleaning management.
+  Date:   8 November 2005, November 11, 2005
+  Origin: Adam Thornton ,
+          Arno Lehmann 
+  Status:
+
+  What:   Make Bacula manage tape life cycle information, tape reuse
+          times and drive cleaning cycles.
+
+  Why:    All three parts of this project are important when operating
+          backups.
+          We need to know which tapes need replacement, and we need to
+          make sure the drives are cleaned when necessary.  While many
+          tape libraries and even autoloaders can handle all this
+          automatically, support by Bacula can be helpful for smaller
+          (older) libraries and single drives.  Limiting the number of
+          times a tape is used might prevent tape errors when using
+          tapes until the drives can't read it any more.  Also, checking
+          drive status during operation can prevent some failures (as I
+          [Arno] had to learn the hard way...)
+
+  Notes:  First, Bacula could (and even does, to some limited extent)
+          record tape and drive usage.  For tapes, the number of mounts,
+          the amount of data, and the time the tape has actually been
+          running could be recorded.  Data fields for Read and Write
+          time and Number of mounts already exist in the catalog (I'm
+          not sure if VolBytes is the sum of all bytes ever written to
+          that volume by Bacula).  This information can be important
+          when determining which media to replace.  The ability to mark
+          Volumes as "used up" after a given number of write cycles
+          should also be implemented so that a tape is never actually
+          worn out.  For the tape drives known to Bacula, similar
+          information is interesting to determine the device status and
+          expected life time: Time it's been Reading and Writing, number
+          of tape Loads / Unloads / Errors.  This information is not yet
+          recorded as far as I [Arno] know.  A new volume status would
+          be necessary for the new state, like "Used up" or "Worn out".
+          Volumes with this state could be used for restores, but not
+          for writing. These volumes should be migrated first (assuming
+          migration is implemented) and, once they are no longer needed,
+          could be moved to a Trash pool.
+
+          The next step would be to implement a drive cleaning setup.
+          Bacula already has knowledge about cleaning tapes.  Once it
+          has some information about cleaning cycles (measured in drive
+          run time, number of tapes used, or calender days, for example)
+          it can automatically execute tape cleaning (with an
+          autochanger, obviously) or ask for operator assistance loading
+          a cleaning tape.
+
+          The final step would be to implement TAPEALERT checks not only
+          when changing tapes and only sending the information to the
+          administrator, but rather checking after each tape error,
+          checking on a regular basis (for example after each tape
+          file), and also before unloading and after loading a new tape.
+          Then, depending on the drives TAPEALERT state and the known
+          drive cleaning state Bacula could automatically schedule later
+          cleaning, clean immediately, or inform the operator.
+
+          Implementing this would perhaps require another catalog change
+          and perhaps major changes in SD code and the DIR-SD protocol,
+          so I'd only consider this worth implementing if it would
+          actually be used or even needed by many people.
+
+          Implementation of these projects could happen in three distinct
+          sub-projects: Measuring Tape and Drive usage, retiring
+          volumes, and handling drive cleaning and TAPEALERTs.
+
+Item  8:  Implement creation and maintenance of copy pools
+  Date:   27 November 2005
+  Origin: David Boyes (dboyes at sinenomine dot net)
+  Status:
+
+  What:   I would like Bacula to have the capability to write copies
+          of backed-up data on multiple physical volumes selected
+          from different pools without transferring the data
+          multiple times, and to accept any of the copy volumes
+          as valid for restore.
+
+  Why:    In many cases, businesses are required to keep offsite
+          copies of backup volumes, or just wish for simple
+          protection against a human operator dropping a storage
+          volume and damaging it. The ability to generate multiple
+          volumes in the course of a single backup job allows
+          customers to simple check out one copy and send it
+          offsite, marking it as out of changer or otherwise
+          unavailable. Currently, the library and magazine
+          management capability in Bacula does not make this process
+          simple.
+
+          Restores would use the copy of the data on the first
+          available volume, in order of copy pool chain definition.
+
+          This is also a major scalability issue -- as the number of
+          clients increases beyond several thousand, and the volume
+          of data increases, transferring the data multiple times to
+          produce additional copies of the backups will become
+          physically impossible due to transfer speed
+          issues. Generating multiple copies at server side will
+          become the only practical option. 
+
+  How:    I suspect that this will require adding a multiplexing
+          SD that appears to be a SD to a specific FD, but 1-n FDs
+          to the specific back end SDs managing the primary and copy
+          pools.  Storage pools will also need to acquire parameters
+          to define the pools to be used for copies. 
+
+  Notes:  I would commit some of my developers' time if we can agree
+          on the design and behavior. 
+
+Item  9:  Implement new {Client}Run{Before|After}Job feature.
+  Date:   26 September 2005
+  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
+          jobs.  At the time, there was a suggestion to add a
+          RunAfterFailedJob directive (and, presumably, a matching
+          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 like this example:
+
+          RunScript {
+              Command = "/opt/bacula/etc/checkhost %c"
+              RunsOnClient = No          # default
+              AbortJobOnError = Yes      # default
+              RunsWhen = Before
+          }
+          RunScript {
+              Command = c:/bacula/systemstate.bat
+              RunsOnClient = yes
+              AbortJobOnError = No
+              RunsWhen = After
+              RunsOnFailure = yes
+          }
+
+          RunScript {
+              Command = c:/bacula/deletestatefile.bat
+              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
+          RunAfter commands that will run regardless of whether the job
+          succeeds, or RunBefore tasks that still allow the job to run even
+          if that specific RunBefore fails.
+
+  Notes:  (More notes from Phil, Kern, David and Eric)
+          I would prefer to have a single new Resource called
+          RunScript.
+
+            RunsWhen = After|Before|Always
+            RunsAtJobLevels = All|Full|Diff|Inc # not yet implemented
+
+          The AbortJobOnError, RunsOnSuccess and RunsOnFailure directives
+          could be optional, and possibly RunWhen as well.
+
+          AbortJobOnError would be ignored unless RunsWhen was set to Before
+          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
+          (or RunsBeforeJob set to No), and default to Yes.
+
+          RunsOnFailure would be ignored unless RunsWhen was set to After,
+          and default to No.
+
+          Allow having the before/after status on the script command
+          line so that the same script can be used both before/after.
+
+Item 10:  Merge multiple backups (Synthetic Backup or Consolidation).
+  Origin: Marc Cousin and Eric Bollengier 
+  Date:   15 November 2005
+  Status: Depends on first implementing project Item 1 (Migration).
+
+  What:   A merged backup is a backup made without connecting to the Client.
+          It would be a Merge of existing backups into a single backup.
+          In effect, it is like a restore but to the backup medium.
+
+          For instance, say that last Sunday we made a full backup.  Then
+          all week long, we created incremental backups, in order to do
+          them fast.  Now comes Sunday again, and we need another full.
+          The merged backup makes it possible to do instead an incremental
+          backup (during the night for instance), and then create a merged
+          backup during the day, by using the full and incrementals from
+          the week.  The merged backup will be exactly like a full made
+          Sunday night on the tape, but the production interruption on the
+          Client will be minimal, as the Client will only have to send
+          incrementals.
+
+          In fact, if it's done correctly, you could merge all the
+          Incrementals into single Incremental, or all the Incrementals
+          and the last Differential into a new Differential, or the Full,
+          last differential and all the Incrementals into a new Full
+          backup.  And there is no need to involve the Client.
+
+  Why:    The benefit is that :
+          - the Client just does an incremental ;
+          - the merged backup on tape is just as a single full backup,
+            and can be restored very fast.
+
+          This is also a way of reducing the backup data since the old
+          data can then be pruned (or not) from the catalog, possibly
+          allowing older volumes to be recycled
+
+Item 11:  Deletion of Disk-Based Bacula Volumes
+  Date:   Nov 25, 2005
+  Origin: Ross Boylan  (edited
+          by Kern)
+  Status:         
+
+   What:  Provide a way for Bacula to automatically remove Volumes
+          from the filesystem, or optionally to truncate them.
+          Obviously, the Volume must be pruned prior removal.
+
+  Why:    This would allow users more control over their Volumes and
+          prevent disk based volumes from consuming too much space.
+
+  Notes:  The following two directives might do the trick:
+
+          Volume Data Retention =
+ +
+ + diff --git a/docs/home-page/fr/pages/requirements.php b/docs/home-page/fr/pages/requirements.php new file mode 100644 index 00000000..6ede6962 --- /dev/null +++ b/docs/home-page/fr/pages/requirements.php @@ -0,0 +1,56 @@ + + + + + + + + +
+ System Requirements +
+ +
    +
  • Bacula has been compiled and run on Linux RedHat, FreeBSD, + and Solaris systems.
    • +
  • It requires GNU C++ version 2.95 or higher to compile. You can try + with other compilers and older versions, but you are on your + own. We have successfully compiled and used Bacula on + RH8.0/RH9/RHEL 3.0 with GCC 3.2. Note, in general GNU C++ is a + separate package (e.g. RPM) from GNU C, so you need them both + loaded. On RedHat systems, the C++ compiler is part of the + gcc-c++ rpm package.
    • + +
  • There are certain third party packages that Bacula needs. + Except for MySQL and PostgreSQL, they can all be found in the + depkgs and depkgs1 releases.
    • +
  • If you want to build the Win32 binaries, you will need a + Microsoft Visual C++ compiler (or Visual Studio). + Although all components build (console has + some warnings), only the File daemon has been tested.
    • +
  • Bacula requires a good implementation of pthreads to work. + This is not the case on some of the BSD systems.
    • +
  • The source code has been written with portability in mind and is + mostly POSIX compatible. Thus porting to any POSIX compatible + operating system should be relatively easy.
    • +
  • The GNOME Console program is developed and tested under GNOME 2.x. + It also runs under GNOME 1.4 but this version is deprecated and + thus no longer maintained.
    • + +
  • The wxWidgets Console program is developed and tested with the + latest stable version of wxWidgets (2.6). It + works fine with the Windows and GTK+-1.x version of wxWidgets, + and should also works on other platforms supported by + wxWidgets.
    • +
  • The Tray Monitor program is developed for GTK+-2.x. It needs + Gnome >=2.2, KDE >=3.1 or any window manager supporting the + + FreeDesktop system tray standard.
    • +
  • If you want to enable command line editing and history, you will + need to have /usr/include/termcap.h and either the termcap or the + ncurses library loaded (libtermcap-devel or ncurses-devel).
    • +
+ +
+ diff --git a/docs/home-page/fr/pages/support.php b/docs/home-page/fr/pages/support.php new file mode 100644 index 00000000..b9b47ef7 --- /dev/null +++ b/docs/home-page/fr/pages/support.php @@ -0,0 +1,121 @@ + + + + + + + + + + + + +
Support pour Bacula
+ Merci de garder à l'esprit que nous ne sommes pas payés pour ça. + Toutefois, notre désir est de voir le plus grand nombre possible de + personnes utiliser Bacula. Par conséquent nous sommes tout à fait + disposé à fournir un niveau raisonnable de support par mail. + +

+ Avant de demander de l'aide, il peut être intéressant de regarder si + le problème a déjà été posé dans les archives des emails et si une + solution a déjà été proposée ou un patch publié pour répondre au + problème.
+ Merci de regarder : + + http://news.gmane.org/search.php?match=bacula. +

+

+ Pour obtenir du support, vous pouvez envoyer un email à + bacula-users at lists.sourceforge.net, et si votre problème est + suffisemment précis, des utilisateurs aimables de Bacula vont vous + aider.
+ L'adresse donnée a été modifiée pour se prémunir contre les techniques + basiques utilisées par les spammeurs. Pour l'utiliser, vous devez + remplacer le at par le symbole @.
+ A cause de la croissance du volume des messages non désirés sur les + listes, vous devez vous enregistrer sur la liste pour être autorisé à + lui envoyer un message. Le lien Listes Email du menu permet + d'accéder à la page où vous pourez vous enregistrer à chaque mailing + liste Bacula. +
+ Les utilisateurs contrôlent cette liste et fournissent généralement du + support. Merci de regarder le paragraphe concernant les informations + requises ci-dessous pour savoir quoi inclure avec votre demande de + support. Si vous ne fournissez pas les informations nécessaires, cela + risque de prendre plus de temps pour obtenir une réponse. De plus les + utilisateurs risquent d'être un peu effrayés pour essayer de vous + répondre si votre requête est trop compliquée ou pas très bien + formulée. +

+

+ J'ai (Kern) un certain nombre d'emails hors liste qui me sont envoyés + directement. Malheureusement je ne suis plus capable de fournir du + support directement aux utilisateurs. Toutefois, je lis tous les mails + envoyés et occasionnellement donne une ou 2 astuces. Si vous m'envoyez + des mails directement, merci de toujours mettre la liste appropriée en + copie. Si aucune liste n'est en copie, je ne vous répondrais peut-être + pas ou vous répondrais en postant votre mail à la liste. Si vous avez + quelque chose de réellement confidentiel, merci de l'indiquer + clairement. +

+

+ Si vous chercher du support en ligne, vous devirez regarder notre + canal IRC sur Freenode net, + appelé #bacula. +

+ +

Informations requises

+

+ Pour que nous puissions répondre à un rapport de bug, nous avons + besoin normalement des informations minimales ci-dessous, que vous + pourrez entrer dans les champs appropriés du système de rapport de + bug : +

    +
  • Votre système d'exploitation, +
    • +
  • La version de Bacula que vous utilisez, +
    • +
  • Une description + claire et concise du problème, +
    • +
  • Si vous avez un plantage, un disfonctionnement ou quelque chose + de similaire, vous devez inclure dans votre description les + messages de sorties de Bacula qui le montre. +
    • +
+

+

+ Si vous avez des problème de bande, merci d'inclure la marque et le + type de lecteur de bandes que vous utilisez. Assurez-vous également + d'avoir exécuté la commande btape "test". +

+

+ Si vous avez des problèmes de base de données, merci d'inclure: +

    +
  • La base de données que vous utilisez : MySQL, PostgreSQL, + SQLite, SQLite3, +
    • +
  • La version de la base de données que vous utilisez. +
    • +
+

+

+ Les 2 premiers items peuvent être remplis en envoyant une copie de + votre fichier config.out, qui est localisé dans le répertoire + principal des sources de Bacula, après avoir exécuté la + commande ./configure. +

+

+ Vous pouvez également ajouter une copie de vos fichiers de + configuration (tout particulièrement bacula-dir.conf) qui est + nécessaire parfois. Si vous pensez qu'il s'agit d'un problème de + configuration, n'hésitez pas à nous les envoyer si nécessaire. +

+
+ Merci de lire également ce petit + + Bug-Report-HowTo (en français). +
+ diff --git a/docs/home-page/fr/pages/testimonials.php b/docs/home-page/fr/pages/testimonials.php new file mode 100644 index 00000000..dc4eca1e --- /dev/null +++ b/docs/home-page/fr/pages/testimonials.php @@ -0,0 +1,104 @@ + + + + + + + + + + + + + + + + + + + +
+ Témoignages +
+ Ci-dessous, vous allez trouver des extraits d'email que des utilisateurs + nous ont envoyé. Le but est de donner une idée de quelle sorte de sites + utilisent Bacula et comment ils l'utilisent. +
+ Ces témoignages sont utilisés avec la permissions de leur autheur. +
+

Norm + Dressler - 2004/06/15

+ Bacula a été impressionnant pour nous. Nous avions l'habitude d'utiliser + Ar**** mais j'ai toujours détesté l'interface. Et le coût était + scandaleux. Et puis j'ai trouvé Bacula et wow! On retrouve tout ce qu'il + y a dans Ar**** et même plus! La console est facile à utiliser, facile à + comprendre une fois que vous la prenez en main, et d'ordinaire je + n'ai aucun problème à restaurer des fichiers! :) +
+ J'ai plus de 15 machines que je sauvegarde avec Bacula avec un + autochangeur, et je suis extrêmement content avec ce produit. A chaque + fois que quelqu'un me demande quoi utiliser, je leur recommande Bacula. +

Norm Dressler, Architecte Réseau Senior

+
+

Michael + Scherer - 2005/02/09

+ Notre précédent système de sauvegarde était ARGHserve qui tournait sous + NT4. Dû au fait que nous remplacions la plupart de nos serveurs avec des + machines Linux nous devions trouver d'autres solutions.
+ Au début nous avions essayé ARGHserve sous Linux, pas très confortable. + Les mises à jour de la base de données ont pris des jours pour se + terminer, et la base a énormément grossie... pas vraiment quelque chose + que vous attendez d'un logiciel aussi cher.
+ J'ai commencé à partir en quête d'une nouvelle solution de sauvegarde, + et testé presque tout ce que j'ai pu trouver sur Sourceforge et + Freshmeat et finalement j'ai décidé de partir sur Bacula.
+ C'est maintenu à la perfection par Kern et pleins d'autres, et un projet + (très) actif avec un bon support à travers les listes d'email et un + canal IRC, qui peut être trouvé sur Freenode.
+
+ Aujourd'hui nous faisons tourner Bacula sur une machine x86 sous SuSe + avec un noyau 2.6, des systèmes RAID5 et un autochangeur IBM Ultrium + sans soucis ni plus de travail que de changer 2 bandes le matin. +
+
+ Les restaurations ne sont pas compliquées non plus, vous choisissez soit + un numéro de job à restaurer ou laissez Bacula trouver le bon numéro de + job pour un fichier ou un répertoire que vous avez à restaurer. Vous + marquez tout ce que vous voulez, Bacula vous demande les bandes dont il + a besoin, et c'est fait.
+ Vous n'avez même pas besoin d'attendre que les démons finissent les + mises à jour de la base de données pour les fichiers sauvegardés, vous + pouvez démarrer une restauration directement après que le job de + sauvegarde soit terminé. Parfait.
+

Michael Scherer, administrateur

+
+

Ludoviczi + Strappazon - 2005/03/05

+ J'utilisais au praravent Veritas Netbackup, mait c'était vraiment trop + cher pour une université. Bacula nous a permis d'acheter un + autochangeur. Maintenant, nous utilisons Bacula depuis 10/2002 avec un + autochangeur ADIC Scalar 24 bandes et des LTO Ultrium, sans aucun + problème. Je pense qu'il peut faire tout ce que Netbackup peut faire + avec notre configuration. Nous sauvegardons 7 serveurs sous Linux, 1 + serveur NT, 4 serveurs Windows 2003 et quelques stations XP. Certains de + ces serveurs sont sauvegardés à travers un firewall en utilisant ssh; + d'autres sont sur un réseau privé. Nous avons essayé avec succès la + procédure de restauration après un désastre sous Linux et nous avons eu + de bons résultats en restaurant Windows "from bare metal". +
+ Pourquoi j'aime bien Bacula? C'est très flexible et sérieux. Avec son + interface console légère, je peux gérer les sauvegardes depuis n'importe + où. Quelques mots à propos du support : il est gratuit mais efficace. Je + ne dois pas croiser helpdesk de niveau 1, niveau 2 pour avoir de l'aide, + je ne me sens jamais seul, et la mailing list bacula-users est un mix de + courtoisie et de discussions honnêtes. Enfin, vous n'avez pas besoin + d'être une grosse société pour faire entendre vos demandes de + fonctionnalités.
+ Merci à Kern Sibbald et les autres qui donnent autant de travail et de + temps pour ce projet.
+
+ Ludovic Strappazon
+ Université Marc Bloch de Strasbourg.
+
+ + diff --git a/docs/home-page/fr/pages/vote.php b/docs/home-page/fr/pages/vote.php new file mode 100644 index 00000000..d459bd88 --- /dev/null +++ b/docs/home-page/fr/pages/vote.php @@ -0,0 +1,10 @@ + + + + + +
+ votes +
+ + diff --git a/docs/home-page/fr/pages/what.php b/docs/home-page/fr/pages/what.php new file mode 100644 index 00000000..24e10f3f --- /dev/null +++ b/docs/home-page/fr/pages/what.php @@ -0,0 +1,453 @@ + + + + + + + + +
+ What is Bacula? +
+ +Bacula is a set of computer programs that permit you (or the +system administrator) to manage backup, recovery, and verification of +computer data across a network of computers of different kinds. In +technical terms, it is a network Client/Server based backup program. +Bacula is relatively easy to use and efficient, while offering many +advanced storage management features that make it easy to find and +recover lost or damaged files. Due to its modular design, Bacula is +scalable from small single computer systems to systems consisting of +hundreds of computers located over a large network. +

Who Needs Bacula?

+If you are currently using a program such as tar, dump, or +bru to backup your computer data, and you would like a network +solution, more flexibility, or catalog services, Bacula will most +likely provide the additional features you want. However, if you are +new to Unix systems or do not have offsetting experience with a sophisticated +backup package, we do not recommend using Bacula as it is +much more difficult to setup and use than tar or dump. +

If you are running Amanda and would like a backup program that +can write to multiple volumes (i.e. is not limited by your tape drive +capacity), Bacula can most likely fill your needs. In addition, +quite a number of our users report that Bacula is simpler to +setup and use than other equivalent programs. +

If you are +currently using a sophisticated commercial package such as Legato +Networker. ARCserveIT, Arkeia, or PerfectBackup+, you may be interested +in Bacula, which provides many of the same features, and is free +software available under the GNU Version 2 software license. + +

Bacula Components or Services

+Bacula is made up of the following five major components or services: +

+
+ thanks to Aristedes Maniatis for this graphic and the one below +

+

+

    +
  • + Bacula Director service consists of the program that + supervises all the backup, restore, verify and archive operations. + The system administrator uses the Bacula Director to schedule + backups and to recover files. For more details see the Director Services Daemon Design Document. + The Director runs as a daemon or a service (i.e. in the background). +
    • +
  • + Bacula Console services is the program that allows the + administrator or user to communicate with the Bacula Director + (see above). Currently, the Bacula Console is available in three + versions. The first and simplest is to run the Console program in a + shell window (i.e. TTY interface). Most system administrators will + find this completely adequate. The second version is a GNOME GUI + interface that for the moment (23 November 2003) is far from complete, + but quite functional as it has most the capabilities of the shell + Console. The third version is a wxWidgets GUI with an interactive file + restore. It also has most the capabilities of the shell console, + allows command completion with tabulation, and gives you instant + help about the command you are typing. For more details see the + Bacula Console Design Document. +
    • +
  • + Bacula File services (or Client program) is the software + program that is installed on the machine to be backed up. It is + specific to the operating system on which it runs and is responsible + for providing the file attributes and data when requested by the + Director. The File services are also responsible for the file + system dependent part of restoring the file attributes and data + during a recovery operation. For more details see the File Services Daemon Design Document. This + program runs as a daemon on the machine to be backed up, and in some + of the documentation, the File daemon is referred to as the Client + (for example in Bacula's configuration file). In addition to + Unix/Linux File daemons, there is a Windows File daemon (normally + distributed in binary format). The Windows File daemon runs on + all currently known Windows versions (95, 98, Me, NT, 2000, XP). +
    • +
  • + Bacula Storage services consist of the software programs that + perform the storage and recovery of the file attributes and data to + the physical backup media or volumes. In other words, the Storage daemon + is responsible for reading and writing your tapes (or other + storage media, e.g. files). For more details see the Storage Services Daemon Design Document. + The Storage services runs as a daemon on the machine that has the + backup device (usually a tape drive). +
    • +
  • + Catalog services are comprised of the software programs + responsible for maintaining the file indexes and volume databases for + all files backed up. The Catalog services permit the System + Administrator or user to quickly locate and restore any desired + file. The Catalog services sets Bacula apart from simple backup + programs like tar and bru, because the catalog maintains a record + of all Volumes used, all Jobs run, and all Files saved, permitting + efficicient restoration and Volume management. + Bacula currently supports three different databases, MySQL, + PostgreSQL, and SQLite, one of which must be chosen when building + Bacula. There also exists an Internal database, but it is no + longer supported. +

    + The three SQL databases currently supported (MySQL, PostgreSQL or SQLite) + provide quite a number of features, + including rapid indexing, arbitrary queries, and security. Although + we plan to support other major SQL databases, the current + Bacula implementation interfaces only to MySQL, PostgreSQL and SQLite. + For more details see the Catalog Services + Design Document. +

    The RPMs for MySQL and PostgreSQL ship as part of the Linux RedHat release, + or building it from the source is quite easy, see the + Installing and Configuring MySQL chapter + of this document for the details. For more information on MySQL, + please see: www.mysql.com. + Or see the Installing and Configuring + PostgreSQL chapter of this document for the details. For more + information on PostgreSQL, please see: www.postgresql.org. +

    Configuring and building SQLite is even easier. For the details + of configuring SQLite, please see the + Installing and Configuring SQLite chapter of this document. +

    • +
  • + Bacula Monitor services is the program that allows the + administrator or user to watch current status of Bacula Directors, + Bacula File Daemons and Bacula Storage Daemons + (see above). Currently, only a GTK+ version is available, which + works with Gnome and KDE (or any window manager that supports the + FreeDesktop.org system tray standard). +
    • +
+To perform a successful save or restore, the following four daemons +must be configured and running: the Director daemon, the File daemon, +the Storage daemon, and MySQL, PostgreSQL or SQLite. + +

Bacula Configuration

+In order for Bacula to understand your system, what clients you +want backed up, and how, you must create a number of configuration +files containing resources (or objects). The following presents an +overall picture of this: +

+ +

+ +

Conventions Used in this Document

+Bacula is in a state of evolution, and as a consequence, +this manual will not always agree with the code. If an +item in this manual is preceded by an asterisk (*), it indicates +that the particular feature is not implemented. If it is preceded +by a plus sign (+), it indicates that the feature may be partially +implemented. +

If you are reading this manual as supplied in a released version +of the software, the above paragraph holds true. If you are reading +the online version of the manual, +http://www.bacula.org/rel-manual, please bear in mind that this version +describes the current version in development (in the CVS) that may +contain features not in the released version. Just the same, +it generally lags behind the code a bit. +

Quick Start

+To get Bacula up and running quickly, we recommend that you first +scan the Terminology section below, then quickly review the next chapter +entitled The Current State of Bacula, then the +Quick Start Guide to Bacula, which will +give you a quick overview of getting Bacula running. After +which, you should proceed to the +chapter on Installing Bacula, then How to Configure Bacula, +and finally the chapter on +Running Bacula. + +

Terminology

+To facilitate communication about this project, we provide here +the definitions of the terminology that we use. +
+
Administrator
+
The person or persons responsible for administrating the Bacula system.
+ +
Backup
+
We use the term Backup to refer to a Bacula Job that saves files.
+ +
Bootstrap File
+
The bootstrap file is an ASCII file + containing a compact form of commands that allow Bacula or + the stand-alone file extraction utility (bextract) to + restore the contents of one or more Volumes, for example, the + current state of a system just backed up. With a bootstrap file, + Bacula can restore your system without a Catalog. You can + create a bootstrap file from a Catalog to extract any file or + files you wish.
+ +
Catalog
+
The Catalog is used to store summary information + about the Jobs, Clients, and Files that were backed up and on + what Volume or Volumes. The information saved in the Catalog + permits the administrator or user to determine what jobs were + run, their status as well as the important characteristics + of each file that was backed up. The Catalog is an online resource, + but does not contain the data for the files backed up. Most of + the information stored in the catalog is also stored on the + backup volumes (i.e. tapes). Of course, the tapes will also have + a copy of the file in addition to the File Attributes (see below). +

The catalog feature is one part of Bacula that distinguishes + it from simple backup and archive programs such as dump + and tar. +

+ +
Client
+
In Bacula's terminology, the word Client + refers to the machine being backed up, and it is synonymous + with the File services or File daemon, and quite often, we + refer to it as the FD. A Client is defined in a configuration + file resource.
+ +
Console
+
The program that interfaces to the Director allowing + the user or system administrator to control Bacula.
+ +
Daemon
+
Unix terminology for a program that is always present in + the background to carry out a designated task. On Windows systems, as + well as some Linux systems, daemons are called Services.
+ +
Directive
+
The term directive is used to refer to a statement + or a record within a Resource in a configuration file that + defines one specific thing. For example, the Name directive + defines the name of the Resource.
+ +
Director
+
The main Bacula server daemon that schedules and directs all + Bacula operations. Occassionally, we refer to the Director as DIR.
+ +
Differential
+
A backup that includes all files changed since the last + Full save started. Note, other backup programs may define this differently.
+ +
File Attributes
+
The File Attributes are all the information + necessary about a file to identify it and all its properties such as + size, creation date, modification date, permissions, etc. Normally, the + attributes are handled entirely by Bacula so that the user never + needs to be concerned about them. The attributes do not include the + file's data. + +
File Daemon
+
The daemon running on the client + computer to be backed up. This is also referred to as the File + services, and sometimes as the Client services or the FD. + +
FileSet
+
A FileSet is a Resource contained in a configuration + file that defines the files to be backed up. It consists + of a list of included files or directories, a list of excluded files, and + how the file is to be stored (compression, encryption, signatures). + For more details, see the + FileSet Resource definition + in the Director chapter of this document.
+ +
Incremental
+
A backup that includes all files changed since the + last Full, Differential, or Incremental backup started. It is normally + specified on the Level directive within the Job resource + definition, or in a Schedule resourc.
+ +
Job
+
A Bacula Job is a configuration resource that defines + the work that Bacula must perform to backup or restore a particular + Client. It consists of the Type (backup, restore, verify, + etc), the Level (full, incremental,...), the FileSet, + and Storage the files are to be backed up (Storage device, + Media Pool). For more details, see the + Job Resource definition + in the Director chapter of this document.
+ +
Monitor
+
The program that interfaces to the all the daemons + allowing the user or system administrator to monitor Bacula status.
+ +
Resource
+
A resource is a part of a configuration file that + defines a specific unit of information that is available to Bacula. + For example, the Job resource defines all the properties of + a specific Job: name, schedule, Volume pool, backup type, backup + level, ...
+ +
Restore
+
A restore is a configuration resource that + describes the operation of recovering a file (lost or damaged) from + backup media. It is the inverse of a save, except that in most + cases, a restore will normally have a small set of files to restore, + while normally a Save backs up all the files on the system. Of + course, after a disk crash, Bacula can be called upon to do + a full Restore of all files that were on the system.
+ +
Schedule
+
A Schedule is a configuration resource that + defines when the Bacula Job will be scheduled for + execution. To use the Schedule, the Job resource will refer to + the name of the Schedule. For more details, see the Schedule Resource + definition in the Director chapter of this document.
+ +
Service
+
This is Windows terminology for a daemon -- see + above. It is now frequently used in Unix environments as well.
+ +
Storage Coordinates
+
The information returned from the + Storage Services that uniquely locates a file on a backup medium. It + consists of two parts: one part pertains to each file saved, and the + other part pertains to the whole Job. Normally, this information is + saved in the Catalog so that the user doesn't need specific knowledge + of the Storage Coordinates. The Storage Coordinates include the + File Attributes (see above) plus the unique location of the information on + the backup Volume.
+ +
Storage Daemon
+
The Storage daemon, sometimes referred to as + the SD, is the code that writes the attributes and data to a storage + Volume (usually a tape or disk).
+ +
Session
+
Normally refers to the internal conversation between + the File daemon and the Storage daemon. The File daemon opens a + session with the Storage daemon to save a FileSet, or to restore + it. A session has a one to one correspondence to a Bacula Job (see + above).
+ +
Verify
+
A verify is a job that compares the current file + attributes to the attributes that have previously been stored in the + Bacula Catalog. This feature can be used for detecting changes to + critical system files similar to what Tripwire does. One + of the major advantages of using Bacula to do this is that + on the machine you want protected such as a server, you can run + just the File daemon, and the Director, Storage daemon, and Catalog + reside on a different machine. As a consequence, if your server is + ever compromised, it is unlikely that your verification database + will be tampered with. +

Verify can also be used to check that the most recent Job + data written to a Volume agrees with what is stored in the Catalog + (i.e. it compares the file attributes), *or it can check the + Volume contents against the original files on disk.

+ +
*Archive
+
An Archive operation is done after a Save, and it + consists of removing the Volumes on which data is saved from active + use. These Volumes are marked as Archived, and many no longer be + used to save files. All the files contained on an Archived Volume + are removed from the Catalog. NOT YET IMPLEMENTED.
+ +
*Update
+
An Update operation causes the files on the remote + system to be updated to be the same as the host system. This is + equivalent to an rdist capability. NOT YET IMPLEMENTED. +
+ +
Retention Period
+
There are various kinds of retention + periods that Bacula recognizes. The most important are the + File Retention Period, Job Retention Period, and the + Volume Retention Period. Each of these retention periods + applies to the time that specific records will be kept in the + Catalog database. This should not be confused with the time that + the data saved to a Volume is valid.

The File Retention Period + determines the time that File records are kept in the catalog + database. This period is important because the volume of the + database File records by far use the most storage space in the + database. As a consequence, you must ensure that regular + "pruning" of the database file records is done. (See + the Console retention command for more details on this + subject).

The Job Retention Period is the length of time that + Job records will be kept in the database. Note, all the File + records are tied to the Job that saved those files. The File + records can be purged leaving the Job records. In this case, + information will be available about the jobs that ran, but not the + details of the files that were backed up. Normally, when a Job + record is purged, all its File records will also be purged.

The + Volume Retention Period is the minimum of time that a Volume will be + kept before it is reused. Bacula will normally never + overwrite a Volume that contains the only backup copy of a file. + Under ideal conditions, the Catalog would retain entries for all + files backed up for all current Volumes. Once a Volume is + overwritten, the files that were backed up on that Volume are + automatically removed from the Catalog. However, if there is a very + large pool of Volumes or a Volume is never overwritten, the Catalog + database may become enormous. To keep the Catalog to a manageable + size, the backup information should removed from the Catalog after + the defined File Retention Period. Bacula provides the + mechanisms for the catalog to be automatically pruned according to + the retention periods defined.

+ +
Scan
+
A Scan operation causes the contents of a Volume or a + series of Volumes to be scanned. These Volumes with the information + on which files they contain are restored to the Bacula Catalog. + Once the information is restored to the Catalog, the files contained + on those Volumes may be easily restored. This function is + particularly useful if certain Volumes or Jobs have exceeded + their retention period and have been pruned or purged from the + Catalog. Scanning data from Volumes into the Catalog is done + by using the bscan program. See the + bscan section of the Bacula Utilities Chapter of this manual + for more details.
+ +
Volume
+
A Volume is an archive unit, normally a tape or + a named disk file where Bacula stores the data from one or more + backup jobs. All Bacula Volumes have a software label written to + the Volume by Bacula so that it identify what Volume it is really + reading. (Normally there should be no confusion with disk files, + but with tapes, it is easy to mount the wrong one).
+
+ +

What Bacula is Not

+Bacula is a backup, restore and verification program and is not a +complete disaster recovery system in itself, but it can be a key part +of one if you plan carefully and follow the instructions included in the Disaster Recovery Chapter of this manual. +

+With proper planning, as mentioned in the Disaster Recovery chapter +Bacula can be a central component of your disaster recovery +system. For example, if you have created an emergency boot disk, a +Bacula Rescue disk to save the current partitioning information of your +hard disk, and maintain a complete Bacula backup, it is possible to +completely recover your system from "bare metal". +

+If you have used the WriteBootstrap record in your job or some +other means to save a valid bootstrap file, you will be able to use it +to extract the necessary files (without using the catalog or manually +searching for the files to restore). + +

Interactions Between the Bacula Services

+The following block diagram shows the typical interactions +between the Bacula Services for a backup job. Each block +represents in general a separate process (normally a daemon). +In general, the Director oversees the flow of information. It also +maintains the Catalog. +

+ Interactions between Bacula Services +

+
+ + diff --git a/docs/home-page/fr/pages/wxconsole.php b/docs/home-page/fr/pages/wxconsole.php new file mode 100644 index 00000000..b544c956 --- /dev/null +++ b/docs/home-page/fr/pages/wxconsole.php @@ -0,0 +1,3 @@ + +TODO! + diff --git a/docs/manual-de/update_version.in b/docs/manual-de/update_version.in new file mode 100644 index 00000000..2766245f --- /dev/null +++ b/docs/manual-de/update_version.in @@ -0,0 +1,10 @@ +#!/bin/sh +# +# Script file to update the Bacula version +# +out=/tmp/$$ +VERSION=`sed -n -e 's/^.*VERSION.*"\(.*\)"$/\1/p' @bacula@/src/version.h` +DATE=`sed -n -e 's/^.*[ \t]*BDATE.*"\(.*\)"$/\1/p' @bacula@/src/version.h` +. ./do_echo +sed -f ${out} version.tex.in >version.tex +rm -f ${out} diff --git a/docs/manual-fr/do_echo b/docs/manual-fr/do_echo new file mode 100644 index 00000000..04b9f79a --- /dev/null +++ b/docs/manual-fr/do_echo @@ -0,0 +1,6 @@ +# +# Avoid that @VERSION@ and @DATE@ are changed by configure +# This file is sourced by update_version +# +echo "s%@VERSION@%${VERSION}%g" >${out} +echo "s%@DATE@%${DATE}%g" >>${out} diff --git a/docs/manual-fr/imagename_translations b/docs/manual-fr/imagename_translations index 3f671ca5..c1c0bead 100644 --- a/docs/manual-fr/imagename_translations +++ b/docs/manual-fr/imagename_translations @@ -1,27 +1,27 @@ img22.png./running.eps -img14.png./win32-location.eps -img13.png./win32-pkg.eps -img12.png./win32-welcome.eps +img28.png./confirm.eps +img26.png./properties-security.eps +img2.png./bacula-applications.eps img25.png./view-only.eps +img21.png./menu.eps +img27.png./properties-security-advanced-owner.eps img9.png./bimagemgr2.eps -img26.png./properties-security.eps -img8.png./bimagemgr1.eps -img6.png./Conf-Diagram.eps -img15.png./win32-service.eps +img1.png./bacula-logo.eps img10.png./bimagemgr3.eps -img24.png./access-is-denied.eps -img3.png./bacula-objects.eps -img21.png./menu.eps -img17.png./win32-start.eps -img28.png./confirm.eps img19.png./idle.eps -img16.png./win32-service-ok.eps +img3.png./bacula-objects.eps +img24.png./access-is-denied.eps +img6.png./Conf-Diagram.eps +img23.png./error.eps +img12.png./win32-welcome.eps +img15.png./win32-service.eps +img11.png./win32-nsis.eps +img8.png./bimagemgr1.eps img18.png./win32-finish.eps -img5.png./Bacula-tray-monitor.eps +img16.png./win32-service-ok.eps +img17.png./win32-start.eps +img14.png./win32-location.eps img20.png./tray-icon.eps -img1.png./bacula-logo.eps -img27.png./properties-security-advanced-owner.eps -img11.png./win32-nsis.eps -img2.png./bacula-applications.eps +img13.png./win32-pkg.eps +img5.png./Bacula-tray-monitor.eps img4.png./flow.eps -img23.png./error.eps diff --git a/docs/manual-fr/update_version.in b/docs/manual-fr/update_version.in new file mode 100644 index 00000000..2766245f --- /dev/null +++ b/docs/manual-fr/update_version.in @@ -0,0 +1,10 @@ +#!/bin/sh +# +# Script file to update the Bacula version +# +out=/tmp/$$ +VERSION=`sed -n -e 's/^.*VERSION.*"\(.*\)"$/\1/p' @bacula@/src/version.h` +DATE=`sed -n -e 's/^.*[ \t]*BDATE.*"\(.*\)"$/\1/p' @bacula@/src/version.h` +. ./do_echo +sed -f ${out} version.tex.in >version.tex +rm -f ${out}