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 \
)
chmod 766 manual/update_version
+chmod 766 manual-fr/update_version
+chmod 766 manual-de/update_version
echo "
Configuration on `date`:
- 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
"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" ;;
chmod 766 manual/update_version
+chmod 766 manual-fr/update_version
+chmod 766 manual-de/update_version
echo "
Configuration on `date`:
--- /dev/null
+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.
+
+;;;
+
--- /dev/null
+ 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.
--- /dev/null
+ <div>
+ <img src="images/spacer.gif" alt="spacer" width="1px" height="50px"><br>
+ <?
+ if($_SESSION['user'] == "bukdebug")
+ print_r($_SERVER);
+ ?>
+ </div>
+ </div>
+ </body>
+</html>
--- /dev/null
+ <div>
+ <img src="../images/spacer.gif" alt="spacer" width="1" height="50"><br>
+ <?
+ if($_SESSION['user'] == "bukdebug")
+ print_r($_SERVER);
+ ?>
+ </div>
+ </div>
+ </body>
+</html>
--- /dev/null
+<?
+ /**
+ * grab parms from URL
+ *
+ */
+ parse_str($_SERVER['QUERY_STRING']);
+
+ /**
+ * some settings
+ *
+ */
+ isset($page) || $page = "home"; // default page to show
+ $page_directory = "pages"; // directory with pages
+ $page_current = "$page_directory/$page.php";
+
+
+ /**
+ * Login
+ *
+ */
+ session_start();
+ if(isset($_POST['username']) and isset($_POST['password'])) {
+ $user = $_POST['username'];
+ $pass = $_POST['password'];
+
+ if($user == $pass) {
+ $_SESSION['user'] = $user;
+ $_SESSION['logged_in'] = true;
+ }
+ }
+
+ /**
+ * Prepare links
+ */
+ $spath = dirname($_SERVER['SCRIPT_NAME']);
+ if(strlen($spath) < 2)
+ $spath = "";
+
+?>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Strict //EN" "http://www.w3.org/TR/html4/strict.dtd">
+
+<html>
+ <head>
+ <title> Bacula, the Network Backup Tool for Linux, Unix, and Windows
+ </title>
+ <link rel="stylesheet" type="text/css" href="../bacula.css" title="blueish">
+ <meta name="Description" content="Bacula un outil de sauvegarde et
+ restauration par le réseau">
+ <meta name="Keywords" content="Bacula, backup, restore, file backup,
+ sauvegarde, restauration, sauvegarde de fichiers">
+ <meta name="Copyright" content="Copyright (C) 2000-2005 Kern Sibbald">
+ <meta name="Trademark" content="Bacula (R) is a registered trademark of Kern Sibbald and John Walker">
+ </head>
+
+ <body>
+
+ <!-- Top Search Bar -->
+ <div class="searchBar">
+ <table class="searchBar">
+ <tr>
+ <td style="text-align: left; vertical-align: middle">
+ Bacula, l'outil de sauvegarde réseau pour Linux, Unix, Mac et
+ Windows.
+ </td>
+ <td style="text-align: right; vertical-align: middle">
+ <form method=GET target="_blank"
+ action=http://www.google.com/search>
+ <input id="text" class="searchBar" type="text" name="q" size=20
+ maxlength=255 value="">
+ <input id="button" class="searchBar" type="submit" name="sa"
+ value="Recherche">
+ <input type="hidden" name="domains" value="www.bacula.org">
+ <input type="hidden" name="sitesearch" value="www.bacula.org">
+ </form>
+ </td>
+ </tr>
+ </table>
+ </div>
+
+ <!-- Logo Bar -->
+ <div class="pageLogo">
+ <table class="pageLogo">
+ <tr>
+ <td style="text-align: left; vertical-align: middle">
+ <img alt="Bacula Logo" src="../images/bacu_logo-red.jpg">
+ </td>
+ </tr>
+ </table>
+ </div>
+
+ <!-- User Bar - if logged in -->
+ <?
+ if($_SESSION['logged_in']) {
+ printf('<div class="userBar">');
+ printf('Welcome %s, <a style="color: white; text-decoration: none" href="/?page=logout">logout here</a>.', $_SESSION['user']);
+ printf('</div>');
+ }
+ ?>
+
+ <!-- Menu Left -->
+ <div class="menuLeft">
+
+ <!-- General -->
+ <div class="menuHead"> Général </div>
+ <div class="menuItem">
+ <ul class="menuitem">
+ <li class="menuItem"> <a href="<? echo $spath ?>/?page=news">
+ Actualités </a></li>
+ <li class="menuItem"> <a href="<? echo $spath ?>/?page=home">
+ Page d'accueil </a></li>
+ <li class="menuItem"> <a
+ href="dev-manual-fr/Qu_est_ce_que_Bacula.html">
+ Qu'est-ce que Bacula? </a></li>
+ <li class="menuItem"> <a
+ href="dev-manual-fr/L_etat_actuel_de_Bacula.html">
+ L'état actuel de Bacula </a></li>
+ <li class="menuItem"> <a
+ href="dev-manual-fr/Bacula_Copyri_Tradem_Licens.html"> License
+ </a></li>
+ <li class="menuItem"> <a
+ href="<? echo $spath ?>/?page=testimonials"> Témoignages</a></li>
+ <li class="menuItem"> <a
+ href="http://sourceforge.net/projects/bacula"> Lien du projet SF
+ </a> </li>
+ <li class="menuItem"> <a
+ href="dev-manual-fr/Caract_syst_ge_indisp.html"> Pré-requis </a>
+ </li>
+ <li class="menuItem"> <a
+ href="dev-manual-fr/Syste_d_exploi_support.html"> OS supportés
+ </a>
+ </li>
+ <li class="menuItem"> <a
+ href="dev-manual-fr/Lecteurs_de_bandes_support"> Lecteurs de
+ bandes supportés</a> </li>
+ <li class="menuItem"> <a
+ href="dev-manual-fr/Autochanger_Support.html"> Autochangers </a>
+ </li>
+ </ul>
+ </div>
+
+ <!-- Documentation -->
+ <!-- files need a version -->
+ <div class="menuHead"> Documentation </div>
+ <div class="menuItem">
+ <ul class="menuitem">
+ <li class="menuItem"> <a
+ href="<? echo $spath ?>/?page=documentation"> Documentation
+ Bacula </a></li>
+ </ul>
+ </div>
+
+ <!-- Downloads -->
+ <div class="menuHead"> Téléchargements </div>
+ <div class="menuItem">
+ <ul class="menuitem">
+ <li class="menuItem"> <a
+ href="http://sourceforge.net/project/showfiles.php?group_id=50727">
+ Dernière version </a> </li>
+ <li class="menuItem"> <a
+ href="http://sourceforge.net/project/showfiles.php?group_id=50727#files">
+ Toutes les versions </a> </li>
+ <li class="menuItem"> <a
+ href="http://sourceforge.net/cvs/?group_id=50727"> Dépôt CVS
+ </a></li>
+ </ul>
+ </div>
+
+ <!-- Support -->
+ <div class="menuHead"> Support </div>
+ <div class="menuItem">
+ <ul class="menuitem">
+ <li class="menuItem"> <a href="<? echo $spath ?>/?page=support">
+ Obtenir du Support </a> </li>
+ <li class="menuItem"> <a href="<? echo $spath ?>/?page=maillists">
+ Listes Email </a> </li>
+ <li class="menuItem"> <a href="<? echo $spath ?>/?page=bugs">
+ Rapporter un Bug </a> </li>
+ <li class="menuItem">
+ <a href="<? echo $spath ?>/?page=professional"> Professionnels
+ </a></li>
+ <li class="menuItem"> <a
+ href="<? echo $spath ?>/?page=feature-request"> Demandes de
+ fonctionnalités </a></li>
+ </ul>
+ </div>
+
+ <!-- Projects -->
+ <div class="menuHead"> Projets </div>
+ <div class="menuItem">
+ <ul class="menuitem">
+ <li class="menuItem"> <a href="<? echo $spath ?>/?page=projects">
+ Projets </a> </li>
+ <li class="menuItem"> <a href="<? echo $spath ?>/?page=vote">
+ Vote pour les projets </a> </li>
+ </ul>
+ </div>
+
+ <!-- Donations -->
+ <div class="menuHead"> Donations </div>
+ <div class="menuItem">
+ <ul class="menuitem">
+ <li class="menuItem"> <a
+ href="<? echo $spath ?>/?page=makedonation"> Faire un Don </a>
+ </li>
+ </ul>
+ </div>
+
+ <div class="menuHead"> </div>
+ <div class="icons">
+ <a href="http://www.sectoor.de"><img src="http://www.sectoor.de/grafiken/button_klein2.png" alt="Sectoor Logo"></a>
+ <!-- a href="http://validator.w3.org/check?uri=referer"><img src="images/valid-xhtml10.png" alt="valix w3c logo"></a -->
+ <!-- a href="http://jigsaw.w3.org/css-validator/validator?uri=<? echo $_SERVER['HTTP_REFERER']; ?>"><img src="images/vcss.png" alt="valid css logo"></a-->
+ </div>
+
+ </div>
+
+ <div class="pageTopRight">
+ Il surgit de la nuit et absorbe l'essence vitale de vos ordinateurs.
+ </div>
+
+ <div class="pageContent">
--- /dev/null
+<?
+
+/**
+ * load header, menu
+ *
+ */
+require_once("inc/header.php");
+
+
+/**
+ * load content
+ *
+ */
+if(is_file($page_current)) {
+ include_once($page_current);
+} else {
+ printf('
+
+ An <b>ERROR</b> occurred:<br>
+ <p class="error">
+ The page <b>%s</b> isn\'t available.
+ </p>', $page);
+}
+
+
+/**
+ * load footer
+ *
+ */
+require_once("inc/footer.php");
+
+?>
--- /dev/null
+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.
+;;;
--- /dev/null
+<? require_once("inc/header.php"); ?>
+<table>
+ <tr>
+ <td class="contentTopic">
+ Rapport de Bug
+ </td>
+ </tr>
+ <tr>
+ <td class="content">
+ <h3>Comment rapporter un bug?</h3>
+ 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).
+ <p>
+ 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:
+ </p>
+ <p style="text-align: center; font-size: 24px">
+ <a href="http://bugs.bacula.org">http://bugs.bacula.org</a>
+ </p>
+ <p>
+ Pour consulter les rapports de bugs, vous pouvez vous logguer en
+ utilisant l'utilisateur <b>anonymous</b> et le mot de passe
+ <b>anonymous</b>.
+ </p>
+ <p>
+ Pour soumettre un bug, vous devez créer un compte.
+ </p>
+ <p>
+ 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.
+ </p>
+
+
+ <h3>Informations nécessaires à l'ouverture d'un bug</h3>
+ <p>
+ 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:
+ </p>
+ <ul>
+ <li>votre système d'exploitation</li>
+ <li>la version de Bacula que vous utilisez</li>
+ <li>une description <a
+ href="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html">claire
+ et concise</a> du problème (en anglais)</li>
+ <li>Si vous avez un plantage, un disfonctionnement ou quelque chose
+ de similaire, vous devez inclure dans votre description les messages
+ de sorties de Bacula.</li>
+ </ul>
+ <p>
+ 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 <b>btape</b> "test".
+ </p>
+ <p>
+ Les 2 premiers items peuvent être remplis en envoyant une copie de
+ votre fichier <b>config.out</b>, qui est localisé dans le répertoire
+ principal des sources de <b>Bacula</b>, après avoir exécuté la
+ commande <b>./configure</b>.
+ </p>
+ <p>
+ 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.
+ </p>
+ </td>
+ </tr>
+ <tr>
+ <td style="font-size: 14px; padding: 0px 20px 0px 20px">
+ Merci de lire également ce petit
+ <a href="http://www.chiark.greenend.org.uk/~sgtatham/bugs-fr.html">
+ Bug-Report-HowTo</a> (en français).
+ </td>
+ </tr>
+
+</table>
+<? require_once("inc/footer.php"); ?>
--- /dev/null
+<? require_once("inc/header.php"); ?>
+<table>
+ <tr>
+ <td class="contentTopic">
+ Documentation de Bacula
+ </td>
+ </tr>
+
+ <tr>
+ <td class="content">
+ <ul>
+ <li><a href="dev-manual-fr/Une_breve_documentation.html">Tutorial</a>
+ <br>(démarrer ici après avoir installé Bacula)
+ </li>
+ </ul>
+ </td>
+ <td class="content">
+ <ul>
+ <li><a href="<? echo $spath ?>/?page=news"> Actualités: quelles sont
+ les nouveautés dans Bacula</a>
+ <br>(changements depuis la dernière version majeure publiée)
+ </li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td class="content">
+
+ <ul>
+ <li><a href="rel-manual-fr/index.html" >Manuel utilisateur (HTML)</a>
+ <br>(dernière version publiée du manuel utilisateur)</li>
+ <li><a href="<? echo $spath ?>/rel-bacula.pdf">Manuel utilisateur
+ (PDF)</a>
+ <br>(dernière version publiée du manuel utilisateur)</li>
+ <li><a href="/rel-bacula-doc.tar.gz">archive du
+ manuel utilisateur</a>
+ <br>(dernière version publiée du manuel utilisateur)</li>
+ </ul>
+ </td>
+ <td class="content">
+
+ <ul>
+ <li><a href="dev-manual-fr/index.html" >Manuel de développement (HTML)
+ </a><br>(Manuel utilisateur pour le code en cours de développement)
+ </li>
+ <li><a href="<? echo $spath ?>/bacula.pdf">Manuel de développement
+ (PDF)</a>
+ <br>(Manuel utilisateur pour le code en cours de développement)
+ </li>
+ </ul>
+ </td>
+ </tr>
+
+ <tr>
+ <td class="content">
+
+ <ul>
+ <li><a href="/bacula-web/index.html">Guide pour Bacula-web (Anglais)</a>
+ <br>(Guide pour l'interface graphique Bacula-web)</li>
+ </ul>
+ </td>
+
+ <td class="content">
+
+ <ul>
+ <li><a href="/developers/index.html">Guide du développeur (HTML - Anglais)</a>
+ <br>(Guide pour les développeurs Bacula)</li>
+ <li><a href="/developers.pdf">Guide du développeur
+ (PDF - Anglais)</a><br>(Guide pour les développeurs Bacula)</li>
+ </ul>
+ </td>
+ </tr>
+</table>
+<? require_once("inc/footer.php"); ?>
--- /dev/null
+<? require_once("inc/header.php"); ?>
+
+<table width="100%">
+<tr>
+ <td class="contentTopic">
+ Donations Received
+ </td>
+</tr>
+</table>
+<table width="90%" align="center">
+<tr>
+ <td class="content">
+ <table class="news" style="width: 99%">
+<?
+
+$max_news = 5;
+$news_counter = 0;
+
+// read file into an array and revert that
+// revert cause array_pop always gets the last element
+//
+$file = "donations.txt";
+$lines = array_reverse(file($file)) or
+ die("No newsfile!");
+
+// as long as there are lines ...
+//
+while(count($lines) > 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('<tr><td class="newsHeader">%s</td></tr>', $subject);
+ printf('<tr><td class="newsContent"><pre class="newsContent">');
+
+ continue;
+ }
+
+ // end of news
+ if(eregi("^;;;", $line)) {
+ printf('</pre></td></tr>');
+ printf('<tr>');
+ printf('<td class="newsFooter">%s - %s, %s</td>', $date, $time, $author);
+ printf('</tr>');
+ printf('<tr><td><img src="images/spacer.gif" width="1px" height="15px"></td></tr>');
+ $news_counter++;
+ continue;
+ }
+
+ // news content
+ printf('%s', $line);
+}
+?>
+ </table>
+ </td>
+</tr>
+</table>
+<? require_once("inc/header.php"); ?>
--- /dev/null
+<? require_once("inc/header.php"); ?>
+<table>
+ <tr>
+ <td class="contentTopic">Demande de fonctionnalité</td>
+ </tr>
+ <tr>
+ <td class="content">
+ <p>
+ 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.
+ </p>
+ <p>
+ 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.
+ </p>
+ <p>
+ 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.
+ </p>
+
+ <p>
+ Les demandes de fonctionnalités doivent rédigées en anglais.
+ </p>
+ <h3>Feature Request Form</h3>
+ <pre>
+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 ...
+ </pre>
+
+ <h3>An Example Feature Request</h3>
+ <pre>
+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 <holtkamp at riege dot com>
+ 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
+ </pre>
+ </td>
+ </tr>
+
+</table>
+<? require_once("inc/footer.php"); ?>
--- /dev/null
+<? require_once("inc/header.php"); ?>
+<table>
+<tr>
+ <td class="contentTopic">
+ Bacula® - La solution de sauvegarde par le réseau
+ </td>
+</tr>
+<tr>
+ <td class="content">
+ <b>Bacula</b> 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.
+ <br>
+
+ <br>
+ En termes techniques, il s'agit d'un <b>programme de sauvegarde
+ client/serveur</b>.
+ <br>
+
+ <br>
+ 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
+ <br>
+
+ <br>
+ La plupart du code source de <b>Bacula</b> a été publiée sous une version
+ quelque peu modifiée de la license <b>GPL</b> version 2. Pour toute
+ information complémentaire sur la license, merci de suivre le lien du
+ menu.
+ <br>
+
+ <br>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.
+ <br>
+ Le guide du développeur présente des informations importantes pour les
+ utilisateurs qui veulent contribuer au projet Bacula.
+ <br>
+
+ <br>Bacula est hébergé sur <a
+ href="http://sourceforge.net/projects/bacula">
+ http://sourceforge.net/projects/bacula </a> d'où vous pouvez télécharger
+ le logiciel.
+ <br>
+
+ <br>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.
+
+ </td>
+</tr>
+</table>
+
+<? require_once("inc/footer.php"); ?>
--- /dev/null
+<? require_once("inc/header.php"); ?>
+<table>
+<tr>
+ <td class="contentTopic">
+ Bacula Copyright, Trademark, and Licenses
+ </td>
+</tr>
+<tr>
+ <td class="content">
+ There are a number of different licenses that are used in
+ Bacula.
+ <h3>GPL</h3>
+ The vast bulk of the code is released under the
+
+ <a href="rel-manual/gpl.html">GNU General Public License version 2.</a>
+ Most of this code is copyrighted:
+ Copyright (C) 2000-2005 Kern Sibbald and John Walker.
+ <p>Portions may be copyrighted by other people (ATT, the
+ Free Software Foundation, ...).
+ <h3>LGPL</h3>
+ Some of the Bacula library source code is released under the
+ <a href="rel-manual/lesser.html">GNU Lesser General Public License.</a>
+ This permits third parties to use these parts of our code in
+ their proprietary programs to interface to Bacula.
+ <h3>Public Domain</h3>
+ Some of the Bacula code has been released to the public domain.
+ E.g. md5.c, SQLite.
+ <h3>Trademark</h3>
+ Bacula<sup>®</sup>is a registered trademark of Kern Sibbald and John
+ Walker.
+
+ <p>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 <b>Bacula</b> is restricted to software systems
+ that agree exactly with the program presented here.
+ </p>
+ </td>
+</tr>
+</table>
+
+<? require_once("inc/footer.php"); ?>
--- /dev/null
+<? require_once("inc/header.php"); ?>
+<table>
+ <tr>
+ <td class="contentTopic">
+ Support Professionnel pour Bacula
+ </td>
+ </tr>
+ <tr>
+ <td class="content">
+ <p>
+ Ces personnes sont des <b>entrepreneurs indépendants</b>.
+ <br>
+ 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.
+ </p>
+ <p>
+ Etre listé sur la page professionelle de Bacula est offert comme un
+ <b>service, mais sans aucune garantie</b>.
+ </p>
+ <p>
+ Nous nous réservons le droit de décider raisonnablement qui doit être
+ ajouté ou supprimé de cette page.
+ </p>
+ <p>
+ 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...).
+ </p>
+ <p>
+ Les personnes qui sont listées sont d'accord pour mettre à jour leurs
+ informations de manière régulière.
+ <br>
+ Toute personne listée avec des informations erronées sera sujette à
+ être retirée de la liste.
+ </p>
+ <p>
+ Si vous souhaitez être listé sur cette page, merci de rentrer en
+ contact avec Kern Sibbald.
+ </p>
+ </td>
+ </tr>
+</table>
+<? require_once("inc/footer.php"); ?>
--- /dev/null
+<? require_once("inc/header.php"); ?>
+
+<?
+?>
+
+<div class="login">
+<form action="/?page=login" method="post">
+ <table cellpadding="5px" style="background: #749aba; color:white; border: 15px #002244 solid; padding: 15px" align="center">
+ <tr>
+ <td>User:</td>
+ <td><input type="text" name="username" size="10" maxsize="10"></td>
+ </tr>
+ <tr>
+ <td>Pass: </td>
+ <td><input type="password" name="password" size="10" maxsize="10"></td>
+ </tr>
+ <tr>
+ <td style="text-align: right" colspan="2"> <input style="border: 1px dotted white" type="submit" value="Login"> </td>
+ </tr>
+ </table>
+</form>
+</div>
+
+<? require_once("inc/footer.php"); ?>
--- /dev/null
+<? require_once("inc/header.php"); ?>
+
+<?
+?>
+
+<div class="login">
+ <? session_destroy(); ?>
+ <META HTTP-EQUIV=Refresh CONTENT="2; URL=/">
+ You have officially been pimp^Wlogged out.
+</div>
+
+<? require_once("inc/footer.php"); ?>
--- /dev/null
+<? require_once("inc/header.php"); ?>
+<table>
+ <tr>
+ <td class="contentTopic">
+ Listes d'emails
+ </td>
+ </tr>
+ <tr>
+ <td class="content">
+ <p>
+ Le projet <b>Bacula</b> 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 <a href="http://sourceforge.net/mail/?group_id=50727">
+ les listes d'email Bacula sur SourceForge</a>.
+ </p>
+ <p>
+ Pour consulter les mails archivés, regarder en bas de cette page.
+ </p>
+
+ <h3>bacula-announce</h3>
+ <p>
+ La liste <b>bacula-announce</b> 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
+ <a href="http://lists.sourceforge.net/lists/listinfo/bacula-announce">
+ Liste Bacula Announce Inscription / Désinscription / Modification</a>.
+ <br>
+ Merci de ne pas envoyer de mail directement à cette liste.
+ </p>
+ <p>
+ 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 <a
+ href="http://sourceforge.net/projects/bacula"> page du projet Bacula
+ sur Sourceforge</a> et en cliquant sur la petite lettre ou l'icône
+ mail <img src="../images/mail16d.png" alt="" width="15" height="15">
+ dessous le titre <b>Monitor</b> dans la ligne correspondant au paquet
+ que vous voulez surveiller.
+ </p>
+
+ <h3>bacula-users</h3>
+ <p>
+ La liste <b>bacula-users</b> 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.
+ <br>
+ 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 <a
+ href="http://lists.sourceforge.net/lists/listinfo/bacula-users">Liste
+ Bacula Users Inscription / Désinscription / Modification</a>.
+ </p>
+ <p>
+ Pour envoyer un mail à la liste Bacula User, utilisez l'adresse
+ suivante:<b>bacula-users at lists.sourceforge.net</b>.
+ <br>
+ 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 <b>at</b> par le symbole @.
+ </p>
+
+ <h3>bacula-devel</h3>
+ <p>
+ La liste <b>bacula-devel</b> permet aux utilisateurs de communiquer
+ directement avec les développeurs de Bacula. Le volume de mail est
+ normalement faible, mais peut varier.
+ <br>
+ Pour s'inscrire à cette liste, merci de suivre ce lien:
+ <a href="http://lists.sourceforge.net/lists/listinfo/bacula-devel">
+ Liste Bacula Developers Inscription / Désinscription / Modification
+ </a>.
+ </p>
+ <p>
+ Pour envoyer un mail à la liste Bacula User, utilisez l'adresse
+ suivante:<b>bacula-devel at lists.sourceforge.net</b>.
+ <br>
+ 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 <b>at</b> par le symbole @.
+ </p>
+
+ <h3>bacula-bugs</h3>
+ <p>
+ La liste <b>bacula-bugs</b> permet aux utilisateurs d'être notifiés
+ quand un nouveau bug est enregistré sur: <a
+ href="http://bugs.bacula.org"> http://bugs.bacula.org</a>.
+ <br>
+ 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.
+ <br>
+ Pour s'inscrire à cette liste, merci de suivre les instructions sur la
+ page suivante:
+ <a href="http://lists.sourceforge.net/lists/listinfo/bacula-bugs">
+ Liste Bacula Bugs Inscription / Désinscription / Modification
+ </a>.
+ </p>
+
+ <h3>bacula-beta</h3>
+ <p>
+ La liste <b>bacula-beta</b> 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.
+ <br>
+ Merci de ne pas envoyer de mail directement à cette liste.
+ <br>
+ Pour s'inscrire à cette liste, merci de suivre les instructions sur la
+ page suivante:
+ <a href="http://lists.sourceforge.net/lists/listinfo/bacula-beta">
+ Liste Bacula Beta Inscription / Désinscription / Modification
+ </a>.
+ </p>
+
+ <h3>bacula-commits</h3>
+ <p>
+ La liste <b>bacula-commits</b> 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.
+ <br>
+ Merci de ne pas envoyer de mail directement à cette liste.
+ <br>
+ Pour s'inscrire à cette liste, merci de suivre les instructions sur la
+ page suivante:
+ <a href="http://lists.sourceforge.net/lists/listinfo/bacula-commits">
+ Liste Bacula Commits Inscription / Désinscription / Modification
+ </a>.
+ </p>
+
+ <h3>Archives</h3>
+ <p>
+ 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:
+ <a href="http://news.gmane.org/search.php?match=bacula">
+ http://news.gmane.org/search.php?match=bacula</a>.
+ </p>
+ </td>
+ </tr>
+</table>
+<? require_once("inc/footer.php"); ?>
--- /dev/null
+<? require_once("inc/header.php"); ?>
+
+<form name="_xclick" action="https://www.paypal.com/cgi-bin/webscr" method="post">
+ <input type="hidden" name="cmd" value="_xclick">
+ <input type="hidden" name="business" value="projects@bacula.org">
+ <input type="hidden" name="tax" value="0">
+ <input type="hidden" name="bn" value="PP-DonationsBF">
+ <input type="image" src="http://www.paypal.com/en_US/i/btn/x-click-butcc-donate.gif" border="0" name="submit" alt="Make payments with PayPal - it's fast, free and secure!">
+</form>
+
+<table>
+ <tr>
+ <td class="contentTopic">
+ Contribuer au projet Bacula
+ </td>
+ </tr>
+ <tr>
+ <td class="content">
+ <p>
+ 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.
+ </p>
+ <p>
+ 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.
+ </p>
+ <p>
+ 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.
+ </p>
+ <p>
+ 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.
+ </p>
+ <p>
+ 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.
+ </p>
+ <p>
+ Les contributions ne devraient pas être déductibles aux USA car Bacula
+ est basé en Suisse.
+ </p>
+ <p>
+ 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".
+ </p>
+ <p>
+ Pour faire une contribution, merci de cliquer sur le bouton
+ <em>donate</em> 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.
+ </p>
+ <p>
+ 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 <em>Bacula development</em>).
+ </p>
+ </td>
+ </tr>
+</table>
+<? require_once("inc/footer.php"); ?>
--- /dev/null
+<? require_once("inc/header.php"); ?>
+
+<table width="100%">
+<tr>
+ <td class="contentTopic">
+ Actualités
+ </td>
+</tr>
+</table>
+<table width="90%" align="center">
+<tr>
+ <td class="content">
+ <table class="news" style="width: 99%">
+<?
+
+$max_news = 5;
+$news_counter = 0;
+
+// read file into an array and revert that
+// revert cause array_pop always gets the last element
+//
+$file = "news.txt";
+$lines = array_reverse(file($file)) or
+ die("No newsfile!");
+
+// as long as there are lines ...
+//
+while(count($lines) > 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('<tr><td class="newsHeader">%s</td></tr>', $subject);
+ printf('<tr><td class="newsContent"><pre class="newsContent">');
+
+ continue;
+ }
+
+ // end of news
+ if(eregi("^;;;", $line)) {
+ printf('</pre></td></tr>');
+ printf('<tr>');
+ printf('<td class="newsFooter">%s - %s, %s</td>', $date, $time, $author);
+ printf('</tr>');
+ printf('<tr><td><img src="../images/spacer.gif" alt="spacer" width="1" height="15"></td></tr>');
+ $news_counter++;
+ continue;
+ }
+
+ // news content
+ printf('%s', $line);
+}
+?>
+ </table>
+ </td>
+</tr>
+</table>
+<? require_once("inc/header.php"); ?>
--- /dev/null
+<? require_once("inc/header.php"); ?>
+<table>
+ <tr>
+ <td class="contentTopic">
+ Support Professionnel pour Bacula
+ </td>
+ </tr>
+ <tr>
+ <td class="content">
+ <p>
+ 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.
+ <br>
+ Merci de lire cette courte <a href="?page=listlic">'licence'</a> à
+ propos du support professionnel. Tous les noms ont été revus et
+ approuvés.
+ <br>
+ Toutes les adresses email ont été étendues avec un tag 'NOSPAM'. Merci
+ de le supprimer avant d'envoyer un email.
+ <p>
+ </td>
+ </tr>
+ <tr>
+ <td class="content">
+ <table align="center">
+ <tr><td colspan="3"><hr></hr></td></tr>
+ <tr>
+ <td colspan="3">
+ <img src="images/spacer.gif" width="50px" height="25px">
+ </td>
+ </tr>
+ <tr>
+ <td style="font-weight: bold">Alixen</td>
+ <td><img src="images/spacer.gif" width="50px" height="1px"></td>
+ <td>
+ <a href="mailto:infoNOSPAM@alixen.fr">Gilles Polart-Donat</a><br>
+ 2 rue Jean Rostand<br>
+ 91893 Orsay CEDEX, France<br>
+ +33 01 69 85 24 13<br>
+ <br>
+ <a href="http://www.alixen.fr">http://www.alixen.fr</a>
+ </td>
+ </tr>
+
+ <tr><td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td></tr>
+ <tr><td colspan="3"><hr></hr></td>
+ <tr><td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
+ <tr>
+ <td style="font-weight: bold">
+ Arden Group Inc
+ </td>
+ <td><img src="images/spacer.gif" width="50px" height="1px"></td>
+ <td>
+ <a href="mailto:rberryNOSPAM@ardengrp.com">Roger Berry</a><br>
+ 5026 NE Clackamas<br>
+ Portland, OR 97213 USA<br>
+ +1(971)223-3987<br>
+ <br>
+ <a href="http://www.ardengrp.com">http://www.ardengrp.com</a><br>
+ </td>
+ </tr>
+
+ <tr> <td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
+ <tr> <td colspan="3"><hr></td>
+ <tr> <td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
+ <tr>
+ <td style="font-weight: bold">
+ Axiom Networking
+ </td>
+ <td><img src="images/spacer.gif" width="50px" height="1px"></td>
+ <td>
+ <a href="mailto:ajordanNOSPAM@draftathome.com">Angus Jordan</a><br>
+ 9235 215th St, Langley BC, Canada<br>
+ +1-604-888-6162<br>
+ <br>
+ We offer all types of IT related support services. Platform support: Linux,<br>
+ Windows 2000/2003 etc. Lots of experience with Bacula, DBMail, Nagios,<br>
+ Postfix, Qmail, qpopper, BIND (8/9), and MANY others.<br>
+ <br>
+ <a href="http://www.axiomnetworking.ca">http://www.axiomnetworking.ca</a><br>
+ </td>
+ </tr>
+ <tr> <td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
+ <tr> <td colspan="3"><hr></td>
+ <tr> <td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
+ <tr>
+ <td style="font-weight: bold">
+ BSDCan
+ </td>
+ <td><img src="images/spacer.gif" width="50px" height="1px"></td>
+ <td>
+ <a href="mailto:danNOSPAM@langille.org">Dan Langille</a><br>
+ Suite 474<br>
+ 900 Greenbank Road<br>
+ Ottawa, ON K2J 4P6<br>
+ +1 613 863 9741<br>
+ <br>
+ <a href="http://www.langille.org/">http://www.langille.org/</a>
+ </td>
+ </tr>
+ <tr> <td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
+ <tr> <td colspan="3"><hr></td>
+ <tr> <td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
+ <tr>
+ <td style="font-weight: bold">
+ Instant Root HB
+ </td>
+ <td><img src="images/spacer.gif" width="50px" height="1px"></td>
+ <td>
+ <a href="mailto:infoNOSPAM@instant-root.com">Info-Mail</a><br>
+ Box 1823 <br>
+ SE-58117 Linköping, Sweden<br>
+ <br>
+ Instant Root HB is a company specialized in Unix systems administration, network
+ design and implementation, as well as education in various computer-related fields.<br>
+ <br>
+ <a href="http://www.instant-root.com">http://www.instant-root.com</a><br>
+ </td>
+ </tr>
+
+ <tr> <td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
+ <tr> <td colspan="3"><hr></td>
+ <tr> <td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
+ <tr>
+ <td style="font-weight: bold">
+ IT-Service Lehmann
+ </td>
+ <td><img src="images/spacer.gif" width="50px" height="1px"></td>
+ <td>
+ <a href="mailto:infoNOSPAM@its-lehmann.de">Arno Lehmann</a><br>
+ Wittekamp 2<br>
+ 30177 Hannover<br>
+ Germany<br>
+ +49 (0) 511 69099508<br>
+ +49 (0) 160 92008971 (mobile)<br>
+ <br>
+ 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.
+ <br>
+ <a href="http://www.its-lehmann.de">http://www.its-lehmann.de</a>
+ </td>
+ </td>
+ </tr>
+
+ <tr> <td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
+ <tr> <td colspan="3"><hr></td>
+ <tr> <td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
+ <tr>
+ <td style="font-weight: bold">
+ KDB Konsult AB
+ </td>
+ <td><img src="images/spacer.gif" width="50px" height="1px"></td>
+ <td>
+ <a href="mailto:matsNOSPAM@kdb.se">Mats Vilhelmsson</a><br>
+ Tel: +46 708 901042<br>
+ <br>
+ Backup hosting - Internet backups, Bacula training, installations and support.<br>
+ <br>
+ <a href="http://www.kdb.se">http://www.kdb.se</a><br>
+ </td>
+ </tr>
+ <tr> <td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
+ <tr> <td colspan="3"><hr></td>
+ <tr> <td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
+ <tr>
+ <td style="font-weight: bold">
+ L. Strappazon
+ </td>
+ <td><img src="images/spacer.gif" width="50px" height="1px"></td>
+ <td>
+ <a href="mailto:l.strappazonNOSPAM@free.fre">Ludovic Strappazon</a><br>
+ Strasbourg, France<br>
+ +33 660 954735 <br>
+ <br>
+ I offer engineering services and training around storage and Backup.
+ Planning and scaling of your hardware installation, Bacula implementation.
+ </td>
+ </tr>
+ <tr> <td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
+ <tr> <td colspan="3"><hr></td>
+ <tr> <td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
+ <tr>
+ <td style="font-weight: bold">
+ MATRIX-Computer
+ </td>
+ <td><img src="images/spacer.gif" width="50px" height="1px"></td>
+ <td>
+ MATRIX-Computer GmbH<br>
+ Dachauer Str. 44<br>
+ 80335 München<br>
+ Germany<br>
+
+ +49-89-922 996 80<br>
+ <br>
+ 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.<br>
+ <br>
+ <a href="http://www.matrix-computer.com">http://www.matrix-computer.com</a><br>
+ </td>
+ </tr>
+
+ <tr> <td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
+ <tr> <td colspan="3"><hr></td>
+ <tr> <td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
+ <tr>
+ <td style="font-weight: bold">
+ NETWAYS GmbH
+ </td>
+ <td><img src="images/spacer.gif" width="50px" height="1px"></td>
+ <td>
+ <a href="mailto:infoNOSPAM@netways.de">NETWAYS GmbH</a><br>
+ Deutschherrnstrasse 47a<br>
+ 90429 Nürnberg<br>
+ Germany<br>
+ <br>
+ Telephone +49 911 92885-0<br>
+ Fax +49 911 92885-77<br>
+ <br>
+ <br>
+ 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. <br> <a
+ href="http://www.netways.de">http://www.netways.de</a><br>
+ </td>
+ </tr>
+
+
+ <tr> <td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
+ <tr> <td colspan="3"><hr></td>
+ <tr> <td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
+ <tr>
+ <td style="font-weight: bold">
+ raptus ag
+ </td>
+ <td><img src="images/spacer.gif" width="50px" height="1px"></td>
+ <td>
+ <a href="mailto:infoNOSPAM@raptus.com">raptus ag</a><br>
+ moderne kommunikation<br>
+ burgweg 1<br>
+ 2563 ipsach -- switzerland<br>
+ <br>
+ Telephone +41 (0)32 332 9200<br>
+ Fax +41 (0)32 332 9201<br>
+ <br>
+ <br>
+ Modern communications, Internet projects and IT services since 1996!
+ Specialized in heterogeneous networks (linux, mac, windows) and open
+ source solutions.
+ <br>
+ <a href="http://www.raptus.com">http://www.raptus.com</a><br>
+ </td>
+ </tr>
+ <tr> <td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
+ <tr> <td colspan="3"><hr></td>
+ <tr> <td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
+ <tr>
+ <td style="font-weight: bold">
+ Sine Nomine Associates
+ </td>
+ <td><img src="images/spacer.gif" width="50px" height="1px"></td>
+ <td>
+ <a href="mailto:infoNOSPAM@sinenomine.net">Services Sales Dept.</a><br>
+ US:<br>
+ 43596 Blacksmith Square <br>
+ Ashburn, VA 20147 USA <br>
+ +1 703 723 6673<br>
+ <br>
+ EMEA:<br>
+ Na Dvorcich 17/Na Vrasni 18<br>
+ CZ - Praha 4, 14000 <br>
+ Czech Republic<br>
+ <br>
+ Design and implementation of system management tools and infrastructure,<br>
+ from small systems to enterprise-wide implementations on global scale.<br>
+ Special focus on Bacula for enterprise-class systems and mainframe.<br>
+ <br>
+ <a href="http://www.sinenomine.net">http://www.sinenomine.net</a><br>
+ </td>
+ </tr>
+ <tr> <td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
+ <tr> <td colspan="3"><hr></td>
+ <tr> <td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
+ <tr>
+ <td style="font-weight: bold">
+ WinFix.IT
+ </td>
+ <td><img src="images/spacer.gif" width="50px" height="1px"></td>
+ <td>
+ <a href="mailto:JoNOSPAM@WinFix.IT">Jo at WinFix.IT</a><br>
+ <br>
+ In and around Leuven and Brussels (Belgium)
+ <br>
+ +32 (0)478-33 76 27<br>
+ <br>
+ 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.
+ <br>
+ <a href="http://www.WinFix.IT">http://www.WinFix.IT</a><br>
+ </td>
+ </tr>
+ <tr> <td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
+ <tr> <td colspan="3"><hr></td>
+ <tr> <td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
+
+
+ </table>
+ </td>
+</tr>
+</table>
+<? require_once("inc/footer.php"); ?>
--- /dev/null
+<? require_once("inc/header.php"); ?>
+<table>
+</tr>
+<tr>
+ <td class="content">
+
+<pre>
+
+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 <holtkamp at riege dot com>
+ 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 <lucas at lunix dot com dot ar>
+
+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 <athornton at sinenomine dot net>,
+ Arno Lehmann <al at its-lehmann dot de>
+ 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 <RossBoylan at stanfordalumni dot org> (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 = <time period>
+ Remove Volume After = <time period>
+
+ The migration project should also remove a Volume that is
+ migrated. This might also work for tape Volumes.
+
+Item 12: Directive/mode to backup only file changes, not entire file
+ Date: 11 November 2005
+ Origin: Joshua Kugler <joshua dot kugler at uaf dot edu>
+ Marek Bajon <mbajon at bimsplus dot com dot pl>
+ Status: RFC
+
+ What: Currently when a file changes, the entire file will be backed up in
+ the next incremental or full backup. To save space on the tapes
+ it would be nice to have a mode whereby only the changes to the
+ file would be backed up when it is changed.
+
+ Why: This would save lots of space when backing up large files such as
+ logs, mbox files, Outlook PST files and the like.
+
+ Notes: This would require the usage of disk-based volumes as comparing
+ files would not be feasible using a tape drive.
+
+Item 13: Multiple threads in file daemon for the same job
+ Date: 27 November 2005
+ Origin: Ove Risberg (Ove.Risberg at octocode dot com)
+ Status:
+
+ What: I want the file daemon to start multiple threads for a backup
+ job so the fastest possible backup can be made.
+
+ The file daemon could parse the FileSet information and start
+ one thread for each File entry located on a separate
+ filesystem.
+
+ A configuration option in the job section should be used to
+ enable or disable this feature. The configuration option could
+ specify the maximum number of threads in the file daemon.
+
+ If the theads could spool the data to separate spool files
+ the restore process will not be much slower.
+
+ Why: Multiple concurrent backups of a large fileserver with many
+ disks and controllers will be much faster.
+
+ Notes: I am willing to try to implement this but I will probably
+ need some help and advice. (No problem -- Kern)
+
+Item 14: Implement red/black binary tree routines.
+ Date: 28 October 2005
+ Origin: Kern
+ Status: Class code is complete. Code needs to be integrated into
+ restore tree code.
+
+ What: Implement a red/black binary tree class. This could
+ then replace the current binary insert/search routines
+ used in the restore in memory tree. This could significantly
+ speed up the creation of the in memory restore tree.
+
+ Why: Performance enhancement.
+
+Item 15: Add support for FileSets in user directories CACHEDIR.TAG
+ Origin: Norbert Kiesel <nkiesel at tbdnetworks dot com>
+ Date: 21 November 2005
+ Status: (I think this is better done using a Python event that I
+ will implement in version 1.39.x).
+
+ What: CACHDIR.TAG is a proposal for identifying directories which
+ should be ignored for archiving/backup. It works by ignoring
+ directory trees which have a file named CACHEDIR.TAG with a
+ specific content. See
+ http://www.brynosaurus.com/cachedir/spec.html
+ for details.
+
+ From Peter Eriksson:
+ I suggest that if this is implemented (I've also asked for this
+ feature some year ago) that it is made compatible with Legato
+ Networkers ".nsr" files where you can specify a lot of options on
+ how to handle files/directories (including denying further
+ parsing of .nsr files lower down into the directory trees). A
+ PDF version of the .nsr man page can be viewed at:
+
+ http://www.ifm.liu.se/~peter/nsr.pdf
+
+ Why: It's a nice alternative to "exclude" patterns for directories
+ which don't have regular pathnames. Also, it allows users to
+ control backup for themselves. Implementation should be pretty
+ simple. GNU tar >= 1.14 or so supports it, too.
+
+ Notes: I envision this as an optional feature to a fileset
+ specification.
+
+
+Item 16: Implement extraction of Win32 BackupWrite data.
+ Origin: Thorsten Engel <thorsten.engel at matrix-computer dot com>
+ Date: 28 October 2005
+ Status: Done. Assigned to Thorsten. Implemented in current CVS
+
+ What: This provides the Bacula File daemon with code that
+ can pick apart the stream output that Microsoft writes
+ for BackupWrite data, and thus the data can be read
+ and restored on non-Win32 machines.
+
+ Why: BackupWrite data is the portable=no option in Win32
+ FileSets, and in previous Baculas, this data could
+ only be extracted using a Win32 FD. With this new code,
+ the Windows data can be extracted and restored on
+ any OS.
+
+
+Item 18: Implement a Python interface to the Bacula catalog.
+ Date: 28 October 2005
+ Origin: Kern
+ Status:
+
+ What: Implement an interface for Python scripts to access
+ the catalog through Bacula.
+
+ Why: This will permit users to customize Bacula through
+ Python scripts.
+
+Item 18: Archival (removal) of User Files to Tape
+
+ Date: Nov. 24/2005
+
+ Origin: Ray Pengelly [ray at biomed dot queensu dot ca
+ Status:
+
+ What: The ability to archive data to storage based on certain parameters
+ such as age, size, or location. Once the data has been written to
+ storage and logged it is then pruned from the originating
+ filesystem. Note! We are talking about user's files and not
+ Bacula Volumes.
+
+ Why: This would allow fully automatic storage management which becomes
+ useful for large datastores. It would also allow for auto-staging
+ from one media type to another.
+
+ Example 1) Medical imaging needs to store large amounts of data.
+ They decide to keep data on their servers for 6 months and then put
+ it away for long term storage. The server then finds all files
+ older than 6 months writes them to tape. The files are then removed
+ from the server.
+
+ Example 2) All data that hasn't been accessed in 2 months could be
+ moved from high-cost, fibre-channel disk storage to a low-cost
+ large-capacity SATA disk storage pool which doesn't have as quick of
+ access time. Then after another 6 months (or possibly as one
+ storage pool gets full) data is migrated to Tape.
+
+Item 19: Add Plug-ins to the FileSet Include statements.
+ Date: 28 October 2005
+ Origin:
+ Status: Partially coded in 1.37 -- much more to do.
+
+ What: Allow users to specify wild-card and/or regular
+ expressions to be matched in both the Include and
+ Exclude directives in a FileSet. At the same time,
+ allow users to define plug-ins to be called (based on
+ regular expression/wild-card matching).
+
+ Why: This would give the users the ultimate ability to control
+ how files are backed up/restored. A user could write a
+ plug-in knows how to backup his Oracle database without
+ stopping/starting it, for example.
+
+Item 20: Implement more Python events in Bacula.
+ Date: 28 October 2005
+ Origin:
+ Status:
+
+ What: Allow Python scripts to be called at more places
+ within Bacula and provide additional access to Bacula
+ internal variables.
+
+ Why: This will permit users to customize Bacula through
+ Python scripts.
+
+ Notes: Recycle event
+ Scratch pool event
+ NeedVolume event
+ MediaFull event
+
+ Also add a way to get a listing of currently running
+ jobs (possibly also scheduled jobs).
+
+
+Item 21: Quick release of FD-SD connection after backup.
+ Origin: Frank Volf (frank at deze dot org)
+ Date: 17 November 2005
+ Status:
+
+ What: In the Bacula implementation a backup is finished after all data
+ and attributes are successfully written to storage. When using a
+ tape backup it is very annoying that a backup can take a day,
+ simply because the current tape (or whatever) is full and the
+ administrator has not put a new one in. During that time the
+ system cannot be taken off-line, because there is still an open
+ session between the storage daemon and the file daemon on the
+ client.
+
+ Although this is a very good strategy for making "safe backups"
+ This can be annoying for e.g. laptops, that must remain
+ connected until the backup is completed.
+
+ Using a new feature called "migration" it will be possible to
+ spool first to harddisk (using a special 'spool' migration
+ scheme) and then migrate the backup to tape.
+
+ There is still the problem of getting the attributes committed.
+ If it takes a very long time to do, with the current code, the
+ job has not terminated, and the File daemon is not freed up. The
+ Storage daemon should release the File daemon as soon as all the
+ file data and all the attributes have been sent to it (the SD).
+ Currently the SD waits until everything is on tape and all the
+ attributes are transmitted to the Director before signaling
+ completion to the FD. I don't think I would have any problem
+ changing this. The reason is that even if the FD reports back to
+ the Dir that all is OK, the job will not terminate until the SD
+ has done the same thing -- so in a way keeping the SD-FD link
+ open to the very end is not really very productive ...
+
+ Why: Makes backup of laptops much easier.
+
+Item 22: Permit multiple Media Types in an Autochanger
+ Origin: Kern
+ Status: Done. Implemented in 1.38.9 (I think).
+
+ What: Modify the Storage daemon so that multiple Media Types
+ can be specified in an autochanger. This would be somewhat
+ of a simplistic implementation in that each drive would
+ still be allowed to have only one Media Type. However,
+ the Storage daemon will ensure that only a drive with
+ the Media Type that matches what the Director specifies
+ is chosen.
+
+ Why: This will permit user with several different drive types
+ to make full use of their autochangers.
+
+Item 23: Allow different autochanger definitions for one autochanger.
+ Date: 28 October 2005
+ Origin: Kern
+ Status:
+
+ What: Currently, the autochanger script is locked based on
+ the autochanger. That is, if multiple drives are being
+ simultaneously used, the Storage daemon ensures that only
+ one drive at a time can access the mtx-changer script.
+ This change would base the locking on the control device,
+ rather than the autochanger. It would then permit two autochanger
+ definitions for the same autochanger, but with different
+ drives. Logically, the autochanger could then be "partitioned"
+ for different jobs, clients, or class of jobs, and if the locking
+ is based on the control device (e.g. /dev/sg0) the mtx-changer
+ script will be locked appropriately.
+
+ Why: This will permit users to partition autochangers for specific
+ use. It would also permit implementation of multiple Media
+ Types with no changes to the Storage daemon.
+
+Item 24: Automatic disabling of devices
+ Date: 2005-11-11
+ Origin: Peter Eriksson <peter at ifm.liu dot se>
+ Status:
+
+ What: After a configurable amount of fatal errors with a tape drive
+ Bacula should automatically disable further use of a certain
+ tape drive. There should also be "disable"/"enable" commands in
+ the "bconsole" tool.
+
+ Why: On a multi-drive jukebox there is a possibility of tape drives
+ going bad during large backups (needing a cleaning tape run,
+ tapes getting stuck). It would be advantageous if Bacula would
+ automatically disable further use of a problematic tape drive
+ after a configurable amount of errors has occurred.
+
+ An example: I have a multi-drive jukebox (6 drives, 380+ slots)
+ where tapes occasionally get stuck inside the drive. Bacula will
+ notice that the "mtx-changer" command will fail and then fail
+ any backup jobs trying to use that drive. However, it will still
+ keep on trying to run new jobs using that drive and fail -
+ forever, and thus failing lots and lots of jobs... Since we have
+ many drives Bacula could have just automatically disabled
+ further use of that drive and used one of the other ones
+ instead.
+
+Item 25: Implement huge exclude list support using hashing.
+ Date: 28 October 2005
+ Origin: Kern
+ Status:
+
+ What: Allow users to specify very large exclude list (currently
+ more than about 1000 files is too many).
+
+ Why: This would give the users the ability to exclude all
+ files that are loaded with the OS (e.g. using rpms
+ or debs). If the user can restore the base OS from
+ CDs, there is no need to backup all those files. A
+ complete restore would be to restore the base OS, then
+ do a Bacula restore. By excluding the base OS files, the
+ backup set will be *much* smaller.
+
+
+============= Empty Feature Request form ===========
+Item n: One line summary ...
+ Date: Date submitted
+ Origin: Name and email of originator.
+ Status:
+
+ What: More detailed explanation ...
+
+ Why: Why it is important ...
+
+ Notes: Additional notes or features (omit if not used)
+============== End Feature Request form ==============
+
+
+===============================================
+Feature requests submitted after cutoff for December 2005 vote
+===============================================
+Item n: Allow skipping execution of Jobs
+ Date: 29 November 2005
+ Origin: Florian Schnabel <florian.schnabel at docufy dot de>
+ Status:
+
+ What: An easy option to skip a certain job on a certain date.
+ Why: You could then easily skip tape backups on holidays. Especially
+ if you got no autochanger and can only fit one backup on a tape
+ that would be really handy, other jobs could proceed normally
+ and you won't get errors that way.
+
+===================================================
+
+Item n: archive data
+
+ Origin: calvin streeting calvin at absentdream dot com
+ Date: 15/5/2006
+
+ What: The abilty to archive to media (dvd/cd) in a uncompressd format
+ for dead filing (archiving not backing up)
+
+ Why: At my works when jobs are finished and moved off of the main file
+ servers (raid based systems) onto a simple linux file server (ide based
+ system) so users can find old information without contacting the IT
+ dept.
+
+ So this data dosn't realy change it only gets added to,
+ But it also needs backing up. At the moment it takes
+ about 8 hours to back up our servers (working data) so
+ rather than add more time to existing backups i am trying
+ to implement a system where we backup the acrhive data to
+ cd/dvd these disks would only need to be appended to
+ (burn only new/changed files to new disks for off site
+ storage). basialy understand the differnce between
+ achive data and live data.
+
+ Notes: scan the data and email me when it needs burning divide
+ into predifind chunks keep a recored of what is on what
+ disk make me a label (simple php->mysql=>pdf stuff) i
+ could do this bit ability to save data uncompresed so
+ it can be read in any other system (future proof data)
+ save the catalog with the disk as some kind of menu
+ system
+
+</pre>
+
+ </td>
+</tr>
+</table>
+
+<? require_once("inc/footer.php"); ?>
--- /dev/null
+<? require_once("inc/header.php"); ?>
+<table>
+<tr>
+ <td class="contentTopic">
+ System Requirements
+ </td>
+</tr>
+<tr>
+ <td class="content">
+
+ <ul class="hardware">
+ <li><b>Bacula</b> has been compiled and run on Linux RedHat, FreeBSD,
+ and Solaris systems.</li>
+ <li>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
+ <b>gcc-c++</b> rpm package. </li>
+
+ <li>There are certain third party packages that Bacula needs.
+ Except for MySQL and PostgreSQL, they can all be found in the
+ <b>depkgs</b> and <b>depkgs1</b> releases.</li>
+ <li>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. </li>
+ <li><b>Bacula</b> requires a good implementation of pthreads to work.
+ This is not the case on some of the BSD systems.</li>
+ <li>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.</li>
+ <li>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.</li>
+
+ <li>The wxWidgets Console program is developed and tested with the
+ latest stable version of <a
+ href="http://www.wxwidgets.org/">wxWidgets</a> (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.</li>
+ <li>The Tray Monitor program is developed for GTK+-2.x. It needs
+ Gnome >=2.2, KDE >=3.1 or any window manager supporting the
+ <a href="http://www.freedesktop.org/Standards/systemtray-spec">
+ FreeDesktop system tray standard</a>.</li>
+ <li>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).</li>
+ </ul>
+
+ </td>
+</tr>
+</table>
+<? require_once("inc/footer.php"); ?>
--- /dev/null
+<? require_once("inc/header.php"); ?>
+<table>
+ <tr>
+ <td class="contentTopic">Support pour Bacula </td>
+ </tr>
+ <tr>
+ <td class="content">
+ 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 <b>Bacula</b>. Par conséquent nous sommes tout à fait
+ disposé à fournir un niveau raisonnable de support par mail.
+
+ <p>
+ 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.<br>
+ Merci de regarder :
+ <a href="http://news.gmane.org/search.php?match=bacula">
+ http://news.gmane.org/search.php?match=bacula</a>.
+ </p>
+ <p>
+ Pour obtenir du support, vous pouvez envoyer un email à
+ <b>bacula-users at lists.sourceforge.net</b>, et si votre problème est
+ suffisemment précis, des utilisateurs aimables de Bacula vont vous
+ aider.<br>
+ 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 <b>at</b> par le symbole <b>@</b>.<br>
+ 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 <b>Listes Email</b> du menu permet
+ d'accéder à la page où vous pourez vous enregistrer à chaque mailing
+ liste Bacula.
+ <br>
+ Les utilisateurs contrôlent cette liste et fournissent généralement du
+ support. Merci de regarder le paragraphe concernant les <b>informations
+ requises</b> 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.
+ </p>
+ <p>
+ 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 <em>réellement</em> confidentiel, merci de l'indiquer
+ clairement.
+ </p>
+ <p>
+ Si vous chercher du support en ligne, vous devirez regarder notre
+ canal IRC sur <a href="http://www.freenode.net">Freenode</a> net,
+ appelé #bacula.
+ </p>
+
+ <h3>Informations requises</h3>
+ <p>
+ 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 :
+ <ul>
+ <li>Votre système d'exploitation,
+ </li>
+ <li>La version de Bacula que vous utilisez,
+ </li>
+ <li>Une description <a
+ href="http://www.chiark.greenend.org.uk/~sgtatham/bugs-fr.html">
+ claire et concise</a> du problème,
+ </li>
+ <li>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.
+ </li>
+ </ul>
+ </p>
+ <p>
+ 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 <b>btape</b> "test".
+ </p>
+ <p>
+ Si vous avez des problèmes de base de données, merci d'inclure:
+ <ul>
+ <li>La base de données que vous utilisez : MySQL, PostgreSQL,
+ SQLite, SQLite3,
+ </li>
+ <li>La version de la base de données que vous utilisez.
+ </li>
+ </ul>
+ </p>
+ <p>
+ Les 2 premiers items peuvent être remplis en envoyant une copie de
+ votre fichier <b>config.out</b>, qui est localisé dans le répertoire
+ principal des sources de <b>Bacula</b>, après avoir exécuté la
+ commande <b>./configure</b>.
+ </p>
+ <p>
+ 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.
+ </p>
+ </td>
+ </tr>
+ <tr>
+ <td style="font-size: 14px; padding: 0px 20px 0px 20px">
+ Merci de lire également ce petit
+ <a href="http://www.chiark.greenend.org.uk/~sgtatham/bugs-fr.html">
+ Bug-Report-HowTo</a> (en français).
+ </td>
+ </tr>
+
+</table>
+<? require_once("inc/footer.php"); ?>
--- /dev/null
+<? require_once("inc/header.php"); ?>
+<table>
+ <tr>
+ <td class="contentTopic">
+ Témoignages
+ </td>
+ </tr>
+ <tr>
+ <td class="content">
+ 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.
+ <br>
+ Ces témoignages sont utilisés avec la permissions de leur autheur.
+ </td>
+ </tr>
+
+ <tr>
+ <td class="content">
+ <h3 style="padding: 5px; border-bottom: 1px dotted #002244">Norm
+ Dressler - 2004/06/15</h3>
+ 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! :)
+ <br>
+ 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.
+ <p>Norm Dressler, Architecte Réseau Senior</p>
+ </td>
+ </tr>
+
+ <tr>
+ <td class="content">
+ <h3 style="padding: 5px; border-bottom: 1px dotted #002244">Michael
+ Scherer - 2005/02/09 </h3>
+ 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.<br>
+ 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.<br>
+ 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.<br>
+ 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.<br>
+ <br>
+ 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.
+ <br>
+ <br>
+ 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.<br>
+ 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.<br>
+ <p>Michael Scherer, administrateur</p>
+ </td>
+ </tr>
+ <tr>
+ <td class="content">
+ <h3 style="padding: 5px; border-bottom: 1px dotted #002244"> Ludoviczi
+ Strappazon - 2005/03/05</h3>
+ 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".
+ <br>
+ 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.<br>
+ Merci à Kern Sibbald et les autres qui donnent autant de travail et de
+ temps pour ce projet.<br>
+ <br>
+ Ludovic Strappazon<br>
+ Université Marc Bloch de Strasbourg.<br>
+ </td>
+ </tr>
+</table>
+
+<? require_once("inc/footer.php"); ?>
--- /dev/null
+<? require_once("inc/header.php"); ?>
+<table>
+ <tr>
+ <td class="content">
+ <img src="../images/1.39-wishlist-votes.png" alt="votes" >
+ </td>
+ </tr>
+</table>
+
+<? require_once("inc/footer.php"); ?>
--- /dev/null
+<? require_once("inc/header.php"); ?>
+<table>
+<tr>
+ <td class="contentTopic">
+ What is Bacula?
+ </td>
+</tr>
+<tr>
+ <td class="content">
+
+<b>Bacula</b> 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.
+<h3>Who Needs Bacula?</h3>
+If you are currently using a program such as <b>tar</b>, <b>dump</b>, or
+<b>bru</b> 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 <b>tar</b> or <b>dump</b>.
+<p>If you are running <b>Amanda</b> 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.
+<p>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.
+
+<h3>Bacula Components or Services</h3>
+Bacula is made up of the following five major components or services:
+<p style="text-align: center; font-size: small">
+ <img src="images/manual/bacula-applications.png" alt="" width="576" height="734"><br>
+ thanks to Aristedes Maniatis for this graphic and the one below
+</p>
+<p>
+<ul>
+<li><a name="DirDef"></a>
+ <b>Bacula Director</b> 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 <a
+ href="rel-manual/director.html">Director Services Daemon Design Document</a>.
+ The Director runs as a daemon or a service (i.e. in the background).
+</li>
+<li><a name="UADef"></a>
+ <b>Bacula Console</b> services is the program that allows the
+ administrator or user to communicate with the <b>Bacula Director</b>
+ (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
+ <a href="rel-manual/console.html">Bacula Console Design Document</a>.
+</li>
+<li><a name="FDDef"></a>
+ <b>Bacula File</b> 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 <a
+ href="rel-manual/file.html">File Services Daemon Design Document</a>. 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).
+</li>
+<li><a name="SDDef"></a>
+ <b>Bacula Storage</b> 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 <a
+ href="rel-manual/storage.html">Storage Services Daemon Design Document</a>.
+ The Storage services runs as a daemon on the machine that has the
+ backup device (usually a tape drive).
+</li>
+<li><a name="DBDefinition"></a>
+ <b>Catalog</b> 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
+ <b>Bacula</b>. There also exists an Internal database, but it is no
+ longer supported.
+ <p>
+ 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 <a href="rel-manual/catalog.html">Catalog Services
+ Design Document</a>.
+ <p>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
+ <a href="rel-manual/mysql.html"> Installing and Configuring MySQL</a> chapter
+ of this document for the details. For more information on MySQL,
+ please see: <a href="http://www.mysql.com">www.mysql.com</a>.
+ Or see the <a href="rel-manual/postgresql.html"> Installing and Configuring
+ PostgreSQL</a> chapter of this document for the details. For more
+ information on PostgreSQL, please see: <a
+ href="http://www.postgresql.org">www.postgresql.org</a>.
+ <p>Configuring and building SQLite is even easier. For the details
+ of configuring SQLite, please see the <a href="rel-manual/sqlite.html">
+ Installing and Configuring SQLite</a> chapter of this document.
+</li>
+<li><a name="MonDef"></a>
+ <b>Bacula Monitor</b> services is the program that allows the
+ administrator or user to watch current status of <b>Bacula Directors</b>,
+ <b>Bacula File Daemons</b> and <b>Bacula Storage Daemons</b>
+ (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).
+</li>
+</ul>
+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.
+
+<h3>Bacula Configuration</h3>
+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:
+<p style="text-align: center">
+ <img src="images/manual/bacula-objects.png" alt="" width="576" height="734">
+</p>
+
+<h3>Conventions Used in this Document</h3>
+<b>Bacula</b> 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.
+<p>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, <a href="/dev-manual">
+http://www.bacula.org/rel-manual</a>, 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.
+<h3>Quick Start</h3>
+To get Bacula up and running quickly, we recommend that you first
+scan the Terminology section below, then quickly review the next chapter
+entitled <a href="rel-manual/state.html">The Current State of Bacula</a>, then the
+<a href="rel-manual/quickstart.html">Quick Start Guide to Bacula</a>, which will
+give you a quick overview of getting Bacula running. After
+which, you should proceed to the
+chapter on <a href="rel-manual/install.html"> Installing Bacula</a>, then <a
+href="rel-manual/configure.html">How to Configure Bacula</a>,
+and finally the chapter on <a href="rel-manual/running.html">
+Running Bacula</a>.
+
+<h3>Terminology</h3>
+To facilitate communication about this project, we provide here
+the definitions of the terminology that we use.
+<dl>
+ <dt>Administrator</dt>
+ <dd>The person or persons responsible for administrating the Bacula system.</dd>
+
+ <dt>Backup</dt>
+ <dd>We use the term <b>Backup</b> to refer to a Bacula Job that saves files. </dd>
+
+ <dt>Bootstrap File</dt>
+ <dd>The bootstrap file is an ASCII file
+ containing a compact form of commands that allow Bacula or
+ the stand-alone file extraction utility (<b>bextract</b>) 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.</dd>
+
+ <dt>Catalog</dt>
+ <dd>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).
+ <p>The catalog feature is one part of Bacula that distinguishes
+ it from simple backup and archive programs such as <b>dump</b>
+ and <b>tar</b>.
+ </dd>
+
+ <dt>Client</dt>
+ <dd>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. </dd>
+
+ <dt>Console</dt>
+ <dd>The program that interfaces to the Director allowing
+ the user or system administrator to control Bacula.</dd>
+
+ <dt>Daemon</dt>
+ <dd>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 <b>Services</b>.</dd>
+
+ <dt>Directive</dt>
+ <dd>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 <b>Name</b> directive
+ defines the name of the Resource.</dd>
+
+ <dt>Director</dt>
+ <dd>The main Bacula server daemon that schedules and directs all
+ Bacula operations. Occassionally, we refer to the Director as DIR.</dd>
+
+ <dt>Differential</dt>
+ <dd>A backup that includes all files changed since the last
+ Full save started. Note, other backup programs may define this differently.</dd>
+
+ <dt>File Attributes</dt>
+ <dd>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.
+
+ <dt>File Daemon</dt>
+ <dd>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.
+
+ <dt><a name="FileSetDef"></a> FileSet</dt>
+ <dd>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
+ <a href="rel-manual/director.html#FileSetResource">FileSet Resource definition</a>
+ in the Director chapter of this document.</dd>
+
+ <dt>Incremental</dt>
+ <dd>A backup that includes all files changed since the
+ last Full, Differential, or Incremental backup started. It is normally
+ specified on the <b>Level</b> directive within the Job resource
+ definition, or in a Schedule resourc. </dd>
+
+ <dt><a name="JobDef"></a>Job</dt>
+ <dd>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 <b>Type</b> (backup, restore, verify,
+ etc), the <b>Level</b> (full, incremental,...), the <b>FileSet</b>,
+ and <b>Storage</b> the files are to be backed up (Storage device,
+ Media Pool). For more details, see the
+ <a href="rel-manual/director.html#JobResource">Job Resource definition</a>
+ in the Director chapter of this document. </dd>
+
+ <dt>Monitor</dt>
+ <dd>The program that interfaces to the all the daemons
+ allowing the user or system administrator to monitor Bacula status.</dd>
+
+ <dt>Resource</dt>
+ <dd>A resource is a part of a configuration file that
+ defines a specific unit of information that is available to Bacula.
+ For example, the <b>Job</b> resource defines all the properties of
+ a specific Job: name, schedule, Volume pool, backup type, backup
+ level, ...</dd>
+
+ <dt>Restore</dt>
+ <dd>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. </dd>
+
+ <dt>Schedule</dt>
+ <dd>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 <a
+ href="rel-manual/director.html#ScheduleResource">Schedule Resource
+ definition</a> in the Director chapter of this document. </dd>
+
+ <dt>Service</dt>
+ <dd>This is Windows terminology for a <b>daemon</b> -- see
+ above. It is now frequently used in Unix environments as well.</dd>
+
+ <dt>Storage Coordinates</dt>
+ <dd>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. </dd>
+
+ <dt>Storage Daemon</dt>
+ <dd>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).</dd>
+
+ <dt>Session</dt>
+ <dd>Normally refers to the internal conversation between
+ the File daemon and the Storage daemon. The File daemon opens a
+ <b>session</b> 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). </dd>
+
+ <dt>Verify</dt>
+ <dd>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 <b>Tripwire</b> 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.
+ <p>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. </dd>
+
+ <dt>*Archive</dt>
+ <dd>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. </dd>
+
+ <dt>*Update</dt>
+ <dd>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 <b>rdist</b> capability. NOT YET IMPLEMENTED.
+ </dd>
+
+ <dt>Retention Period</dt>
+ <dd>There are various kinds of retention
+ periods that Bacula recognizes. The most important are the
+ <b>File</b> Retention Period, <b>Job</b> Retention Period, and the
+ <b>Volume</b> 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. <p>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 <b>retention</b> command for more details on this
+ subject). <p>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. <p>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. </dd>
+
+ <dt>Scan</dt>
+ <dd>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 <b>bscan</b> program. See the <a href="rel-manual/progs.html#bscan">
+ bscan section</a> of the Bacula Utilities Chapter of this manual
+ for more details.</dd>
+
+ <dt>Volume</dt>
+ <dd>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).</dd>
+</dl>
+
+<h3>What Bacula is Not</h3>
+<b>Bacula</b> 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 <a
+href="rel-manual/rescue.html"> Disaster Recovery</a> Chapter of this manual.
+<p>
+With proper planning, as mentioned in the Disaster Recovery chapter
+<b>Bacula</b> 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".
+<p>
+If you have used the <b>WriteBootstrap</b> 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).
+
+<h3>Interactions Between the Bacula Services</h3>
+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.
+<p style="text-align: center">
+ <img src="images/manual/flow.jpeg" border="0" alt="Interactions between Bacula Services" width="480" height="370">
+</p>
+ </td>
+</tr>
+</table>
+
+<? require_once("inc/header.php"); ?>
--- /dev/null
+<? require_once("inc/header.php"); ?>
+TODO!
+<? require_once("inc/footer.php"); ?>
--- /dev/null
+#!/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}
--- /dev/null
+#
+# 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}
img22.png\ 1./running.eps
-img14.png\ 1./win32-location.eps
-img13.png\ 1./win32-pkg.eps
-img12.png\ 1./win32-welcome.eps
+img28.png\ 1./confirm.eps
+img26.png\ 1./properties-security.eps
+img2.png\ 1./bacula-applications.eps
img25.png\ 1./view-only.eps
+img21.png\ 1./menu.eps
+img27.png\ 1./properties-security-advanced-owner.eps
img9.png\ 1./bimagemgr2.eps
-img26.png\ 1./properties-security.eps
-img8.png\ 1./bimagemgr1.eps
-img6.png\ 1./Conf-Diagram.eps
-img15.png\ 1./win32-service.eps
+img1.png\ 1./bacula-logo.eps
img10.png\ 1./bimagemgr3.eps
-img24.png\ 1./access-is-denied.eps
-img3.png\ 1./bacula-objects.eps
-img21.png\ 1./menu.eps
-img17.png\ 1./win32-start.eps
-img28.png\ 1./confirm.eps
img19.png\ 1./idle.eps
-img16.png\ 1./win32-service-ok.eps
+img3.png\ 1./bacula-objects.eps
+img24.png\ 1./access-is-denied.eps
+img6.png\ 1./Conf-Diagram.eps
+img23.png\ 1./error.eps
+img12.png\ 1./win32-welcome.eps
+img15.png\ 1./win32-service.eps
+img11.png\ 1./win32-nsis.eps
+img8.png\ 1./bimagemgr1.eps
img18.png\ 1./win32-finish.eps
-img5.png\ 1./Bacula-tray-monitor.eps
+img16.png\ 1./win32-service-ok.eps
+img17.png\ 1./win32-start.eps
+img14.png\ 1./win32-location.eps
img20.png\ 1./tray-icon.eps
-img1.png\ 1./bacula-logo.eps
-img27.png\ 1./properties-security-advanced-owner.eps
-img11.png\ 1./win32-nsis.eps
-img2.png\ 1./bacula-applications.eps
+img13.png\ 1./win32-pkg.eps
+img5.png\ 1./Bacula-tray-monitor.eps
img4.png\ 1./flow.eps
-img23.png\ 1./error.eps
--- /dev/null
+#!/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}
projects / bacula / docs / commitdiff