From fc554c13e77cda391c2f6a6c0c303eb22f3b1739 Mon Sep 17 00:00:00 2001 From: Kern Sibbald Date: Wed, 20 May 2009 14:24:51 +0000 Subject: [PATCH] Add Spanish directory --- docs/home-page/de/inc/header.php | 3 + docs/home-page/en/inc/header.php | 4 + docs/home-page/en/index.php | 2 +- docs/home-page/es/LICENSE | 537 ++++++ docs/home-page/es/donations.txt | 18 + docs/home-page/es/inc/footer.php | 10 + docs/home-page/es/inc/header.php | 204 ++ docs/home-page/es/index.php | 32 + docs/home-page/es/news.txt | 1741 ++++++++++++++++++ docs/home-page/es/pages/articles.php | 31 + docs/home-page/es/pages/bugs.php | 97 + docs/home-page/es/pages/documentation.php | 85 + docs/home-page/es/pages/donations.php | 64 + docs/home-page/es/pages/feature-request.php | 108 ++ docs/home-page/es/pages/fsfe.php | 65 + docs/home-page/es/pages/home.php | 167 ++ docs/home-page/es/pages/license.php | 41 + docs/home-page/es/pages/listlic.php | 40 + docs/home-page/es/pages/login.php | 24 + docs/home-page/es/pages/logout.php | 12 + docs/home-page/es/pages/maillists.php | 198 ++ docs/home-page/es/pages/makedonation.php | 102 + docs/home-page/es/pages/news.php | 64 + docs/home-page/es/pages/old-professional.txt | 188 ++ docs/home-page/es/pages/presentations.php | 40 + docs/home-page/es/pages/presskits.php | 31 + docs/home-page/es/pages/professional.php | 423 +++++ docs/home-page/es/pages/projects.php | 1292 +++++++++++++ docs/home-page/es/pages/requirements.php | 57 + docs/home-page/es/pages/screenshot.php | 49 + docs/home-page/es/pages/support.php | 131 ++ docs/home-page/es/pages/testimonial.php | 1208 ++++++++++++ docs/home-page/es/pages/testimonials.php | 123 ++ docs/home-page/es/pages/vote.php | 12 + docs/home-page/es/pages/what.php | 453 +++++ docs/home-page/es/pages/wxconsole.php | 3 + docs/home-page/fr/inc/header.php | 3 + 37 files changed, 7661 insertions(+), 1 deletion(-) create mode 100644 docs/home-page/es/LICENSE create mode 100644 docs/home-page/es/donations.txt create mode 100644 docs/home-page/es/inc/footer.php create mode 100644 docs/home-page/es/inc/header.php create mode 100644 docs/home-page/es/index.php create mode 100644 docs/home-page/es/news.txt create mode 100644 docs/home-page/es/pages/articles.php create mode 100644 docs/home-page/es/pages/bugs.php create mode 100644 docs/home-page/es/pages/documentation.php create mode 100644 docs/home-page/es/pages/donations.php create mode 100644 docs/home-page/es/pages/feature-request.php create mode 100644 docs/home-page/es/pages/fsfe.php create mode 100644 docs/home-page/es/pages/home.php create mode 100644 docs/home-page/es/pages/license.php create mode 100644 docs/home-page/es/pages/listlic.php create mode 100644 docs/home-page/es/pages/login.php create mode 100644 docs/home-page/es/pages/logout.php create mode 100644 docs/home-page/es/pages/maillists.php create mode 100644 docs/home-page/es/pages/makedonation.php create mode 100644 docs/home-page/es/pages/news.php create mode 100644 docs/home-page/es/pages/old-professional.txt create mode 100644 docs/home-page/es/pages/presentations.php create mode 100644 docs/home-page/es/pages/presskits.php create mode 100644 docs/home-page/es/pages/professional.php create mode 100644 docs/home-page/es/pages/projects.php create mode 100644 docs/home-page/es/pages/requirements.php create mode 100644 docs/home-page/es/pages/screenshot.php create mode 100644 docs/home-page/es/pages/support.php create mode 100644 docs/home-page/es/pages/testimonial.php create mode 100644 docs/home-page/es/pages/testimonials.php create mode 100644 docs/home-page/es/pages/vote.php create mode 100644 docs/home-page/es/pages/what.php create mode 100644 docs/home-page/es/pages/wxconsole.php diff --git a/docs/home-page/de/inc/header.php b/docs/home-page/de/inc/header.php index cd767519..2a62cf4c 100644 --- a/docs/home-page/de/inc/header.php +++ b/docs/home-page/de/inc/header.php @@ -72,6 +72,9 @@     Français +     + + Español
diff --git a/docs/home-page/en/inc/header.php b/docs/home-page/en/inc/header.php index 074304f9..466c1aed 100644 --- a/docs/home-page/en/inc/header.php +++ b/docs/home-page/en/inc/header.php @@ -72,8 +72,12 @@     Deutsch +     + + Español + diff --git a/docs/home-page/en/index.php b/docs/home-page/en/index.php index 804203d8..6491d646 100644 --- a/docs/home-page/en/index.php +++ b/docs/home-page/en/index.php @@ -18,7 +18,7 @@ if(is_file($page_current)) {   An ERROR occurred:

- The page %s isn\'t available. + The page %s is not available.

', $page); } diff --git a/docs/home-page/es/LICENSE b/docs/home-page/es/LICENSE new file mode 100644 index 00000000..c1ec1a38 --- /dev/null +++ b/docs/home-page/es/LICENSE @@ -0,0 +1,537 @@ + +History: +The original Bacula code was Copyright Kern Sibbald and John Walker. +After November 2004, it became Copyright Kern Sibbald, and finally, +the copyright was transferred to the Free Software Foundation Europe +on 15 November 2006. + +Trademark: +The name Bacula is a registered trademark of Kern Sibbald. + +=================================== + +License: +For the most part, Bacula is licensed under the GPL version 2 this +code is listed under Copyright Free Software Foundation Europe e.V. +What follows is the addition(s) to the GPL version 2 license, that +applies to code that is copyrighted by the Free Software Foundation +Europe e.V. + +Linking: +As a special exception to the GPLv2, the Bacula Project gives +permission to link the code of its release of Bacula with the OpenSSL +project's "OpenSSL" library (or with modified versions of it that use +the same license as the "OpenSSL" library), and distribute the linked +executables. You must obey the GNU General Public License in all +respects for all of the code used other than "OpenSSL". + +As a special exception to the GPLv2, the Bacula Project gives +permission to link the code of its release of the Bacula Win32 File +daemon with the Microsoft supplied Volume Shadow Copy (VSS) libraries +and distribute the linked executables. You must obey the GNU General +Public License in all respects for all of the code used other than for +the Microsoft VSS code, where you must obey their license terms. + +The Bacula Project gives permission for plugins with GPLv2 compatible +licenses to be loaded and distributed with the Bacula executables as +long as the combined work is distributed under the terms listed in the +Bacula LICENSE file. A full list of GPLv2 compatible licenses can be +found at: http://www.fsf.org/licensing/licenses/. If you wish to load +or distribute plugins with different licensing terms please contact +the Bacula Project at: license@bacula.org + +=================================== + + +What follows is information from the authors of the code: + +License: +To the best of our knowledge, all code used in Bacula, which is +copyrighted by a third party, has licenses that are compatible +with the OpenSSL license, and so given the exception that we have +made to the GPLv2 above, Bacula can be freely linked and distributed +with the OpenSSL libraries. + +Intellectual Property rights: +Recipient understands that although each Contributor to Bacula grants +the licenses to its Contributions set forth herein, no assurances are +provided by any Contributor that the Program does not infringe the +patent or other intellectual property rights of any other entity. +Each Contributor disclaims any liability to Recipient for claims +brought by any other entity based on infringement of intellectual +property rights or otherwise. As a condition to exercising the rights +and licenses granted hereunder, each Recipient hereby assumes sole +responsibility to secure any other intellectual property rights +needed, if any. For example, if a third party patent license is +required to allow Recipient to distribute the Program, it is +Recipient's responsibility to acquire that license before distributing +the Program. + +Copyrights: +Each Contributor to Bacula represents that to its knowledge it has +sufficient copyright rights in its Contribution, if any, to grant +the copyright license set forth in this Agreement. + +Code falling under the above conditions will be marked as follows: + + Bacula® - The Network Backup Solution + + Copyright (C) 2000-2009 Free Software Foundation Europe e.V. + + The main author of Bacula is Kern Sibbald, with contributions from + many others, a complete list can be found in the file AUTHORS. + This program is Free Software; you can redistribute it and/or + modify it under the terms of version two of the GNU General Public + License as published by the Free Software Foundation plus additions + that are listed in the file LICENSE. + + This program is distributed in the hope that it will be useful, but + WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program; if not, write to the Free Software + Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA + 02110-1301, USA. + + Bacula® is a registered trademark of Kern Sibbald. + The licensor of Bacula is the Free Software Foundation Europe + (FSFE), Fiduciary Program, Sumatrastrasse 25, 8006 Zürich, + Switzerland, email:ftf@fsfeurope.org. + + +Windows: +Certain source code used to build the Windows version of the +Bacula File daemon is copyrighted and or trademarked by Microsoft +and may contain Microsoft intellectual property (examples: +Microsoft VC++, the source to the VSS libraries, the Microsoft C +runtime libraries). As such we cannot and do not distribute that +software. We are permitted however to distribute Bacula with the +necessary Microsoft libraries in binary form. + +You may obtain the parts that we cannot distribute as follows. The +Microsoft compiler available for purchase, and Microsoft provides a free +version of the compiler. The source code and libraries are available for +download from Microsoft public Web servers. We have documented in the +src/win32 directory the URLs from which we obtained the library source, and +how we build the Windows File daemon and many users have succeeded in doing +so themselves. Our intention is to respect as closely as possible Open +Source practices while maintaining full respect for proprietary and +copyrighted code. + +GPLv2 or later license: + src/tools/bsmtp.c + Copyright (C) 1997 Ralf S. Engelschall, All Rights Reserved. + (note, bsmtp.c does not use OpenSSL, nor is it used with the code + of any other part of Bacula) + +3 clause BSD License notice for inclusion with the binary: + src/lib/fnmatch.c + * Copyright (c) 1989, 1993, 1994 + * The Regents of the University of California. All rights reserved. + src/lib/fnmatch.h + * Copyright (c) 1992, 1993 + * The Regents of the University of California. All rights reserved. + +Permissive licenses: + src/lib/var.c/h + ** OSSP var - Variable Expansion + ** Copyright (c) 2001-2002 Ralf S. Engelschall + ** Copyright (c) 2001-2002 The OSSP Project (http://www.ossp.org/) + ** Copyright (c) 2001-2002 Cable & Wireless Deutschland (http://www.cw.com/de/) + + src/lib/bsnprintf.c + * Copyright Patrick Powell 1995 + + src/bregex.c/h + * Copyright (c) 1991 Tatu Ylonen, Espoo, Finland + + src/lib/sha1.c/h + Copyright (C) The Internet Society (2001). All Rights Reserved. + + src/win32/compat/getopt.c + "... licensed under IBM copyrights to use the IBM-provided source code + in any way he or she deems fit ..." + + src/win32/compat/sys/mtio.h (LGPL) + Copyright (C) 1996, 1997 Free Software Foundation, Inc. + + +Bacula can be enabled with data encryption and/or communications +encryption. If this is the case, you will be including OpenSSL code that +that contains cryptographic software written by Eric Young +(eay@cryptsoft.com) and also software written by Tim Hudson +(tjh@cryptsoft.com). + +There are parts of Bacula that are licensed under the LGPL so +that those files may be used in proprietary code to interface with +Bacula. + +Finally there are parts of Bacula that are in the public domain. + +THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS +IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A +PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER +OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, +EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, +PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR +PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF +LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING +NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS +SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + +===================================== + + +The entire GPL is reproduced below, in the manuals distributed with the +Bacula documentation and can also be found online on the GNU web site +as well as at www.bacula.org. You may also obtain a copy of the +GPL (or LGPL) by writing to: Free Software Foundation, Inc., +51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA + +============== Text of GPL version 2 license ======== + + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 + + Copyright (C) 1989, 1991 Free Software Foundation, Inc. + 51 Franklin Street, 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. + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +License is intended to guarantee your freedom to share and change free +software--to make sure the software is free for all its users. This +General Public License applies to most of the Free Software +Foundation's software and to any other program whose authors commit to +using it. (Some other Free Software Foundation software is covered by +the GNU Library General Public License instead.) You can apply it to +your programs, too. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +this service if you wish), that you receive source code or can get it +if you want it, that you can change the software or use pieces of it +in new free programs; and that you know you can do these things. + + To protect your rights, we need to make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if you +distribute copies of the software, or if you modify it. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must give the recipients all the rights that +you have. You must make sure that they, too, receive or can get the +source code. And you must show them these terms so they know their +rights. + + We protect your rights with two steps: (1) copyright the software, and +(2) offer you this license which gives you legal permission to copy, +distribute and/or modify the software. + + Also, for each author's protection and ours, we want to make certain +that everyone understands that there is no warranty for this free +software. If the software is modified by someone else and passed on, we +want its recipients to know that what they have is not the original, so +that any problems introduced by others will not reflect on the original +authors' reputations. + + Finally, any free program is threatened constantly by software +patents. We wish to avoid the danger that redistributors of a free +program will individually obtain patent licenses, in effect making the +program proprietary. To prevent this, we have made it clear that any +patent must be licensed for everyone's free use or not licensed at all. + + The precise terms and conditions for copying, distribution and +modification follow. + + GNU GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License applies to any program or other work which contains +a notice placed by the copyright holder saying it may be distributed +under the terms of this General Public License. The "Program", below, +refers to any such program or work, and a "work based on the Program" +means either the Program or any derivative work under copyright law: +that is to say, a work containing the Program or a portion of it, +either verbatim or with modifications and/or translated into another +language. (Hereinafter, translation is included without limitation in +the term "modification".) Each licensee is addressed as "you". + +Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running the Program is not restricted, and the output from the Program +is covered only if its contents constitute a work based on the +Program (independent of having been made by running the Program). +Whether that is true depends on what the Program does. + + 1. You may copy and distribute verbatim copies of the Program's +source code as you receive it, in any medium, provided that you +conspicuously and appropriately publish on each copy an appropriate +copyright notice and disclaimer of warranty; keep intact all the +notices that refer to this License and to the absence of any warranty; +and give any other recipients of the Program a copy of this License +along with the Program. + +You may charge a fee for the physical act of transferring a copy, and +you may at your option offer warranty protection in exchange for a fee. + + 2. You may modify your copy or copies of the Program or any portion +of it, thus forming a work based on the Program, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) You must cause the modified files to carry prominent notices + stating that you changed the files and the date of any change. + + b) You must cause any work that you distribute or publish, that in + whole or in part contains or is derived from the Program or any + part thereof, to be licensed as a whole at no charge to all third + parties under the terms of this License. + + c) If the modified program normally reads commands interactively + when run, you must cause it, when started running for such + interactive use in the most ordinary way, to print or display an + announcement including an appropriate copyright notice and a + notice that there is no warranty (or else, saying that you provide + a warranty) and that users may redistribute the program under + these conditions, and telling the user how to view a copy of this + License. (Exception: if the Program itself is interactive but + does not normally print such an announcement, your work based on + the Program is not required to print an announcement.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Program, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Program, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Program. + +In addition, mere aggregation of another work not based on the Program +with the Program (or with a work based on the Program) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may copy and distribute the Program (or a work based on it, +under Section 2) in object code or executable form under the terms of +Sections 1 and 2 above provided that you also do one of the following: + + a) Accompany it with the complete corresponding machine-readable + source code, which must be distributed under the terms of Sections + 1 and 2 above on a medium customarily used for software interchange; or, + + b) Accompany it with a written offer, valid for at least three + years, to give any third party, for a charge no more than your + cost of physically performing source distribution, a complete + machine-readable copy of the corresponding source code, to be + distributed under the terms of Sections 1 and 2 above on a medium + customarily used for software interchange; or, + + c) Accompany it with the information you received as to the offer + to distribute corresponding source code. (This alternative is + allowed only for noncommercial distribution and only if you + received the program in object code or executable form with such + an offer, in accord with Subsection b above.) + +The source code for a work means the preferred form of the work for +making modifications to it. For an executable work, complete source +code means all the source code for all modules it contains, plus any +associated interface definition files, plus the scripts used to +control compilation and installation of the executable. However, as a +special exception, the source code distributed need not include +anything that is normally distributed (in either source or binary +form) with the major components (compiler, kernel, and so on) of the +operating system on which the executable runs, unless that component +itself accompanies the executable. + +If distribution of executable or object code is made by offering +access to copy from a designated place, then offering equivalent +access to copy the source code from the same place counts as +distribution of the source code, even though third parties are not +compelled to copy the source along with the object code. + + 4. You may not copy, modify, sublicense, or distribute the Program +except as expressly provided under this License. Any attempt +otherwise to copy, modify, sublicense or distribute the Program 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. + + 5. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Program or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Program (or any work based on the +Program), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Program or works based on it. + + 6. Each time you redistribute the Program (or any work based on the +Program), the recipient automatically receives a license from the +original licensor to copy, distribute or modify the Program subject to +these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties to +this License. + + 7. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Program at all. For example, if a patent +license would not permit royalty-free redistribution of the Program by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Program. + +If any portion of this section is held invalid or unenforceable under +any particular circumstance, the balance of the section is intended to +apply and the section as a whole is intended to apply in other +circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system, which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 8. If the distribution and/or use of the Program is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Program under this License +may add an explicit geographical distribution limitation excluding +those countries, so that distribution is permitted only in or among +countries not thus excluded. In such case, this License incorporates +the limitation as if written in the body of this License. + + 9. The Free Software Foundation may publish revised and/or new versions +of the General Public 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. + +Each version is given a distinguishing version number. If the Program +specifies a version number of this License which applies to it and "any +later version", you have the option of following the terms and conditions +either of that version or of any later version published by the Free +Software Foundation. If the Program does not specify a version number of +this License, you may choose any version ever published by the Free Software +Foundation. + + 10. If you wish to incorporate parts of the Program into other free +programs whose distribution conditions are different, write to the author +to ask for permission. For software which is copyrighted by the Free +Software Foundation, write to the Free Software Foundation; we sometimes +make exceptions for this. Our decision will be guided by the two goals +of preserving the free status of all derivatives of our free software and +of promoting the sharing and reuse of software generally. + + NO WARRANTY + + 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY +FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN +OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES +PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED +OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF +MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS +TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE +PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, +REPAIR OR CORRECTION. + + 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR +REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, +INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING +OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED +TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY +YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER +PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE +POSSIBILITY OF SUCH DAMAGES. + + END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to the public, the best way to achieve this is to make it +free software which everyone can redistribute and change under these terms. + + To do so, attach the following notices to the program. It is safest +to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least +the "copyright" line and a pointer to where the full notice is found. + + + Copyright (C) + + This program is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 2 of the License, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program; if not, write to the Free Software + Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA + + +Also add information on how to contact you by electronic and paper mail. + +If the program is interactive, make it output a short notice like this +when it starts in an interactive mode: + + Gnomovision version 69, Copyright (C) year name of author + Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + +The hypothetical commands `show w' and `show c' should show the appropriate +parts of the General Public License. Of course, the commands you use may +be called something other than `show w' and `show c'; they could even be +mouse-clicks or menu items--whatever suits your program. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the program, if +necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the program + `Gnomovision' (which makes passes at compilers) written by James Hacker. + + , 1 April 1989 + Ty Coon, President of Vice + +This General Public License does not permit incorporating your program into +proprietary programs. If your program is a subroutine library, you may +consider it more useful to permit linking proprietary applications with the +library. If this is what you want to do, use the GNU Lesser General +Public License instead of this License. + +=========================================== diff --git a/docs/home-page/es/donations.txt b/docs/home-page/es/donations.txt new file mode 100644 index 00000000..2c038c87 --- /dev/null +++ b/docs/home-page/es/donations.txt @@ -0,0 +1,18 @@ +Kern;;;2006/08/04;;;12:30 +Donations Received + +The following people or organizations have made +donations or supplied finacial development support +to the Bacula project and have specifically requested +that their names appear here: + + + +Many thanks to the many Bacula listed and non-listed +supporters have provided support or made donations. +Names listed here are by specific request. If you have +made a donation or provided financial support and wish +to appear in this list, please send an email to +kern at sibbald dot com. + +;;; diff --git a/docs/home-page/es/inc/footer.php b/docs/home-page/es/inc/footer.php new file mode 100644 index 00000000..7ccbd8e0 --- /dev/null +++ b/docs/home-page/es/inc/footer.php @@ -0,0 +1,10 @@ +
+ spacer
+ +
+ + + diff --git a/docs/home-page/es/inc/header.php b/docs/home-page/es/inc/header.php new file mode 100644 index 00000000..ffef3fef --- /dev/null +++ b/docs/home-page/es/inc/header.php @@ -0,0 +1,204 @@ + + + + + + Bacula, the Open Source, Enterprise ready, Network Backup Tool for Linux, Unix, and Windows + + + + + + + + + + +
+ + + + + + + + +
+ Bacula, the Open Source, Enterprise ready, Network Backup Tool for Linux, Unix, Mac and Windows. + + Español +     + + English +     + + Français +     + + Deutsch + + + + + + + +
+
+ + + + + + '); + printf('Welcome %s, logout here.', $_SESSION['user']); + printf(''); + } + ?> + + +
+ + +
General
+
+ +
+ + + +
Documentation
+
+ +
+ + +
Downloads
+
+ +
+ + +
Support
+
+ +
+ + +
Projects
+
+ +
+ +
Donations
+
+ +
+
+
+ www.ukfast.net +
+ +
+ +
+ It comes by night and sucks the vital essence from your computers. +
+ +
diff --git a/docs/home-page/es/index.php b/docs/home-page/es/index.php new file mode 100644 index 00000000..804203d8 --- /dev/null +++ b/docs/home-page/es/index.php @@ -0,0 +1,32 @@ +ERROR occurred:
+

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

', $page); +} + + +/** + * load footer + * + */ +require_once("inc/footer.php"); + +?> diff --git a/docs/home-page/es/news.txt b/docs/home-page/es/news.txt new file mode 100644 index 00000000..ab735e68 --- /dev/null +++ b/docs/home-page/es/news.txt @@ -0,0 +1,1741 @@ +Kern;;;30 April 2009 at 17:49 +Bacula Version 3.0.1 has been released to Source Forge. + +Note, if you are not already running 3.0.0, please read the 3.0.0 release notes. Important!!! + +Version 3.0.1 is primarily a minor bug fix update to version 3.0.0 with +one enhancement (see below). + +Changes since 3.0.0: +Bug fixes: + 1276, 1274, 1275, 1272 1246, 1268, 1281, 1282. + +Fixed: +- Check for job_canceled() in fd_plugin code. +- Update Win32 table creation to have new DB version 11 format +- Remove illegal Options in Exclude of default Win32/64 bacula-dir.conf +- Remove 'Reposition' messages when restoring +- Updated projects file +- Tweak version string to display versionid field at the end + and keep fields order. + - Add additional mysql connection debug code submitted by: + Chandranshu + +Enhancement: +- Modify insertion of read Volumes in SD to be done *before* the + drive reservation. This ensures that a Volume to be read will not + be reserved for writing. Significant improvement in eliminating + tape deadlock situations. + +Note, both the Director and Storage daemons must be upgraded at the +same time. The 3.0.1 File daemons are compatible with 3.0.0 file +daemons and as noted below in the 3.0.0 release notes the Director +and Storage daemon should be compatible with 2.4.x File daemons. +In general, we do not expect any of the 3.0.x File daemons to work with older +Directors and Storage daemons (as has always been the case for Bacula +releases). + +============ Documentation improvements needed ================== + +Note!!!!! The 3.0.0+ documentation needs rather extensive modifications in the +following areas: + +1. Missing documentation. +2. Correction of links within various manuals -- most fail. +3. Integration of the new features into the main documents. +4. Much more. + +The documentation will not be completed in the near future due to lack +manpower. If you are unhappy with this situation as we are, we suggest +you help by submitting patches to the documentation. Thanks. +===== +;;; + +Kern;;;09 April 2009 at 22:30 +Bacula Version 3.0.0 has been released to Source Forge. + +This is to inform you that we have uploaded the Bacula version 3.0.0 source +tar files and the Win32/64 installer files to the Bacula Source Forge +download location. + +There are quite a number of new features in this release, and upgrading to it +requires a database upgrade, so please read the release notes carefully +(included below) and the documentation for the new features at: + +http://www.bacula.org/manuals/es/concepts/concepts/New_Features.html + +There is still a good deal of work to do to finish the release process (mainly +reorganizing the web site manuals ...), but at least the source files are +released. The rpms should follow shortly (probably this weekend). + +If you are currently using 2.4.4, please note that within a few months that +version will no longer be supported, so please consider the possibility of +upgrading. + +This release probably has the most new features that we have ever released, +and it has taken a long time to produce it. The basic code is very well +tested, and if you stick to 2.4.4 features, you are unlikely to experience +problems. However, many of the new features have not been well tested, so +your help will be appreciated. + +The following issues with 3.0.0 are known and we are working on them: + +1. The documentation is not 100% complete (there are so many new features that +we missed documenting some). + +2. All the new documentation is in the New Features chapter, but not all of it +has yet been integrated back into the appropriate chapters. + +3. James has reported that the Exchange plugin may crash if you cancel a job +while it is running. He is working on this. + +4. The SD has many new features that will make it more stable. One in +particular is that it knows what Volumes will be read during a migration, +copy, or Virtual backup job, and will ensure that they are not selected for +writing (something easy to do if you are using disk files and the same pool +for reading an writing). However, the day after the release was cut, I found +a problem with this code that prevents it from working properly during +certain pre-allocations of the write tape. + +5. There is still an outstanding bug report on VSS failing (it seems to be a +bit of a rare case). + +As I previously announced, we will now make 3.0.0 our main release source code +stream, and we hope to release new version every six months and bug fix +updates even sooner. To be able to do this, we will support version 2.4.4 +only for a few more months. There after the project will only support the +most current release ... + +This release comprises a lot of work by a lot of different people and many +contributions. Normally I hesitate to mention particular people or +contributions because I always forget someone, but since this was such a big +release, I would like to mention at least the big contributions: + +Sponsor Company(s) - Programmer - Project +Bacula Systems - Eric Bollengier - Accurate Backup +Bacula Systems - Eric Bollengier - Catalog format enhancements +Bacula Systems - Eric Bollengier - bextract non-portable Win32 data +Bacula Systems - Eric Bollengier - Win64 File daemon +Bacula Systems - Eric Bollengier - SD deadlock detection + postmortum dump +Bacula Systems - Eric Bollengier - Faster Attribute despooling if DIR & FD on + same machine +Bacula Systems - Eric Bollengier - Virtual tape emulation +Bacula Systems - Kern Sibbald - USB rescue key +Equiinet funded development - James Harper - MS Exchange plugin + +Personal contributions: +Kjetil Torgrim Homme - Regex expressions for restore in bootstrap file +Marco van Wieringen - ACL code overhaul +Marco van Wieringen - Solaris ZFS/NFSv4 ACL support +Marco van Wieringen - Extended Attribute support +Marco van Wieringen - Shared Objects +Dirk Bartley - Bat speedup + stability improvement + many enhancements +Joao Henrique Freitas - libdbi catalog driver +Scott Barninger - rpm packaging +Kern Sibbald - many big and little projects ... +Many people -- see the AUTHORS file. + +Many thanks to everyone for making Bacula what it is today. + +=== List of new features === +- Accurate Backup +- Copy Jobs +- ACL code overhaul +- Solaris ZFS/NFSv4 ACL support +- Extended Attribute support + --disable-xattr (default=auto) +- Shared Objects + --enable-libtool (default) + --disable-libtool +- Virtual Backup +- Catalog Format Enhancements + - Support for more than 4 Billion file entries + - New stats tables +- Duplicate Job Control +- TLS Authentication +- bextract non-portable Win32 data +- State File updated at Job Termination +- Bacula Plugins + - FD bpipe plugin + - FD Exchange plugin +- libdbi DB driver +- Console Enhancements + - status slots + - list joblog + - command separator +- Bootstrap regex +- Restore seek optimization +- Virtual Tape Emulation +- Bat Enhancements +- RunScript Enhancements +- Status enhancements +- FD connect timeout default to 3 minutes +- ftruncate implemented for NFS Volumes +- FD Version compatibily flag +- Statistics Enhancements +- Faster Attribute despooling +- Document split into 6 manuals +- GPLv2 license now compatible with OpenSSL +- Win64 File daemon +- Postmortum dump improvements in SD +- Deadlock mutex detection in SD +- Improved Volume management in SD to avoid deadlocks. +- New configure install options + --docdir= (default=/usr/share/doc/bacula-VERSION) + --htmldir= (default=/usr/share/doc/bacula-VERSION/html -- bat help files) + --plugindir= (default=sysconfdir, where plugins will be installed) +- New Bare Metal Recovery with USB key. See rescue/linux/usb + New Directives: +- Max Full Interval +- Max Diff Interval +- Honor No Dump Flag +- Exclude Dirs Containing +- Recycle Pool +- Max Run Sched Time +- Max Wait Time +- Full/Diff/Incr Max Run Time +- Scratch Pool +- Max Console Connections +- Spool Size (in Job resource) +- Allow Mixed Priorities +- Allow Duplicate Jobs +- Allow Higher Duplicates +- Cancel Queued Duplicates +- Cancel Running Duplicates +- TLS Authenticate +- Console (in RunScript) + +New features from Project Items Completed for version 3.0.0 + also listed above: +Item 1: Accurate restoration of renamed/deleted files +Item 3: Merge multiple backups (Synthetic Backup or Consolidation) +Item 4: Implement Catalog directive for Pool resource in Director +Item 5: Add an item to the restore option where you can select a Pool +Item 8: Implement Copy pools +Item 12: Add Plug-ins to the FileSet Include statements. +Item 13: Restore only file attributes (permissions, ACL, owner, group...) +Item 18: Better control over Job execution +Item 26: Store and restore extended attributes, especially selinux file +contexts +Item 27: make changing "spooldata=yes|no" possible for +Item 28: Implement an option to modify the last written date for volumes +Item n: Split documentation into several books +================================ + + + Release Notes for Bacula 3.0.0 + + Bacula code: Total files = 520 Total lines = 205,459 (*.h *.c *.in) + +The diff between 2.4.4 and 2.5.x is 208,340 lines, so this release +represents an enormous effort. + +This Director and Storage daemon must be upgraded at the same time, +but they should be compatible with all 2.4.x File daemons, unless you +use some of the new features that affect the FD. In other words, you should +not have to upgrade all your File daemons when you upgrade. However, any +release of version 2.5.40 or greater requires a database upgrade. + +================== Warning !!!!!! ========================== + +New Catalog format in version 3.0.0 (2.5.40 or later) +----------------------------------------------------- + +This release of Bacula uses a new catalog format. We provide a set of +scripts that permit to convert a 2.4.x (version 10) catalog to 3.0.0 (version +11). The Bacula project rpms distributed on Source Forge will automatically +detect the database change and do the upgrade for you. We strongly +recommend that you save a copy of your existing database before upgrading +using rpms. + +The simplest way to upgrad the database assuming you are building from +source: +1. Stop any current version of Bacula from running. +2. Save a copy of your existing database. +3. Configure, build, and install the 3.0.0 version of Bacula + Note the new ./configure options in the manuals see the link + at the bottom of this file. +4. cd +5. ./update_bacula_tables +6. If you have multiple catalogs, edit the update_bacula_tables + script and put the name of another database, and then + execute the script again. Repeat this until all Bacula + catalogs have been updated. +7. Start the new Bacula. If everything worked, it should + not print any error messages. + +The upgrade operation will convert the FileId index field of the File table +from 32 bits to 64 bits. This operation will take TIME and will *temporarily* +DOUBLE THE SIZE of your catalog. Bacula must be shutdown during this update, +so, won't be able to run jobs during this period. For example, a 3 million +files +catalog will take 2 mins to upgrade on a normal machine. Don't forget to +backup it before executing the script. + +If you start from scratch, you don't need to run the update_bacula_tables +script because the create_bacula_tables script automatically creates the new +table format. However, if you are using a version of Bacula older than 2.5.40 +(e.g. 2.4.4) then you need to run the update_bacula_tables script that will +be found in the /src/cats directory after you run the ./configure +command. As mentioned above, before running this script, please backup your +catalog database, and when you do running it, be sure shutdown Bacula and be +aware that running the script can take some time depending on your database +size. + + +Important New configure options : +---------------------- + +This release of Bacula 3.0.0 uses libtool by default +to generate the Bacula libraries as shared objects rather than +being directly linked in as in prior versions. This means that +the Bacula shared objects, must either be in a shared object +directory known to the loader or they must be in the directory +where the Bacula binaries are installed. It is also possible +to explicitly specify the libraries directory on the ./configure +line (--libdir=/full-path/dir), but this should not be necessary. + + ./configure --libdir= + +If you have problems with libtool or you wish to use the old +way of building libraries and linking them into Bacula, you +can do so by disabling libtool on the configure command line with: + + ./configure --disable-libtool + +During the installation of Bacula 3.0.0, it will now install +bat help files (if you have configured bat). These files +are placed in /usr/share/doc/bacula/html by default. If you +want to put them elsewhere use: + + ./configure --htmldir= + +During the installation of Bacula, it will now install the +ReleaseNotes, License, technotes, ChangeLog, and similar +files in /usr/share/doc/bacula by default. If you +want to put them elsewhere use: + + ./configure --docdir= + +During the installation of Bacula, any plugins will be +installed in the plugindir, which is by default the +same as libdir (/usr/lib). You can specify an alternate +location with: + + ./configure --with-plugindir= + +============================================================== + +This release includes large number of new features and changes. +It should be more or less compatible with previous xx.conf files +and File daemons providing that you are not using any of the new +features. + +Please see the New Features chapter of the new manual, which documents +some but not all the new features (we are still working on it): + +http://www.bacula.org/manuals/es/concepts/concepts/New_Features.html + +The ChangeLog has more details. + +;;; +Kern;;;03 Nobember 2008 at 17:35 +Critical 2.4.3-orphaned-jobs.patch released +We recently found and corrected a serious bug in Bacula that causes jobs to be +orphaned or "stuck" in the director during the pruning process. Depending on +what jobs get stuck and how many there are, it could prevent additional jobs +from running. As best we can tell, this problem occurs only during what could +be called extreme pruning conditions -- i.e. there are insufficient Volumes +available for normal operations. + +In any case, we recommend that everyone apply the 2.4.3-orphaned-jobs.patch, +which you can find in the bacula-patches section of the Source Forge download +area as well as in the directory patches of both the trunk and Branch-2.4 SVN. +;;; + +Kern;;;12 October 2008 at 10:30am +Creation of Bacula Systems SA +Dear Members of the Bacula Community, + +I'm pleased to announce the creation of Bacula Systems S.A., a new company to +provide professional support and service for Bacula. I believe you will be +pleased to see how we have married a strong commitment to the ethos of honest +open source software with the availability of services desired by a wide +range of Bacula users. + +As many of you know, I began work on Bacula in 2000 and released the first +public version in April 2002 to Source Forge. Although I have personally +written a very substantial part of the code, I offer sincere thanks to the +many members of the community who have provided ideas, fixes, testing, and +contributions of code, without which Bacula would not be what it is today. +It has been a labor of love and I am pleased that so many people have found +Bacula useful. + +Before telling you more about Bacula Systems, let me reiterate my unfaltering, +ongoing commitment to open source software and the Bacula open source +project. The code for Bacula and all future releases will remain available as +free open source software under the GPL license that I transferred to the +protection of the Free Software Foundation of Europe. Unlike some other open +source projects, there will be no separate "enterprise" or proprietary +version of the Bacula source code. www.bacula.org will continue to be the +home for Bacula project development. + +So, why create Bacula Systems? The company was created to respond to requests +from users who want professional support with guaranteed levels of service +and response times. To ensure continuity and the highest level of knowledge +transfer, I will take the position of Chairman of the Board and Chief +Technical Officer of Bacula Systems S.A.. + +Several members of the Bacula community have joined me to start the company. +The other team members are also strongly dedicated to the spirit of keeping +Bacula open and free while simultaneously offering commercial services to +those for whom it is essential in making the decision to deploy Bacula. +Bacula Systems is self-financed -- the initial capital comes from the +founders; no outside venture capital was sought or accepted. This means we +have the power to establish the company's priorities and we can remain +dedicated to "honest open source". Bacula Systems S.A. is a Swiss company +with offices in Yverdon-les-Bains, and with branches in France and Germany +initially. We will open additional branches as business requires. + +I will continue to support development of Bacula via bacula.org and the Bacula +community. Future developments will be in the "community" code base which +will remain free. Bacula Systems will offer "funded development" to +customers who wish to accelerate the addition of certain features to Bacula. +Code developed this way will be contributed to the free distribution and will +be available to the entire community at no charge. Bacula Systems will +provide additional fee-based services, including high quality consulting, +training, documentation and certified binaries. + +Our goal in establishing Bacula Systems is to be inclusive of the community, +and expand it by creating opportunities for members of the Bacula community +through a well-defined Partner Program. If you provide IT services or +consulting, the Bacula Systems Partner Program can provide you with the +additional back-up (pardon the pun) support you need to serve your customers +more effectively. + +Our plan is to develop an international network of partners who offer high +value added services to Bacula users -- installing, configuring and optimizing +Bacula for their customers, as well as Level 3 and 4 support, with guaranteed +service levels. We will also provide training and tools to our partners. + +The Bacula project website, www.bacula.org, and Source Forge will be unchanged +in the mission and ideals of being free sources of information, mail lists +and forum-based support for and by the community. Both Bacula source code and +Bacula binaries will continue to be available for free, as in the past, and +new releases will also be available for free. The new commercial website, +www.baculasystems.com will provide information on commercial subscriptions +for those users who want guaranteed levels of service, support, documentation +and certified binaries. + +All members of the Bacula community are encouraged to register for free at +www.baculasystems.com, so that you will receive announcements and news about +our commercial activities, and so that you can send feedback to our new +company, Bacula Systems. + +Thank you for your interest and participation in the Bacula community. + +Sincerely, + +Kern Sibbald +;;; + +Kern;;;11 October 2008 at 11:30am +Bacula version 2.4.3 Released +This is to let you know that the source tar files and the Win32 binaries for +Bacula version 2.4.3 have been released to the Bacula Source Forge download +area. + +Release 2.4.3 + This is a bug fix to version 2.4.2. All daemons are compatible + with other 2.4.x versions. + +Bugs Fixed: + 1159, 1162. 1149, 1128, 1143, 1140, 1129 + +Change Summary: +- Apply 2.4.2-cancel-non-running-jobs.patch to be able to cancel + a non created job faster. +- This should correct bug #1159 where Migration does not properly + respect the Migration Low Bytes directive. +- Fix typo in configure.in that breaks --with-db-password option +- This code should fix the race condition that leads to a Director + crash at job end time when the job list is updated. This was reported + in bug #1162. +- Remove all double quotes from SQLite creating script and + replace by single quotes as suggested by John Huttley. +- Fix SQL case problem that may cause the failure of DiskToCatalog + in bug #1149. +- Copy missing storage name into edit buffer. As far as I can tell + this never caused a bug. +- Remove catalog dependency for bcopy +- Modify catalog scripts to have an easier packaging integration, + using default variables. + Make difference between SQLite3 and SQLite in db_get_type() +- Attempt to fix bug #1128 InChanger flag cleared during Migration + job when reading from one autochanger and writing to another. +- Add more information to SD acquire.c INFO messages. +- Fix NULL Volume name error when reading and the drive must + be switched. +- Fix a Verify InitCatalog problem where in certain cases + a garbage filename may be entered in the verification database. This + fixes bug #1143. +- Add space after version before date in bat about dialog. +- Fix seg fault in Dir during estimate command with no level value + given. This fixes bug #1140. +- Add message to migration job when the target job is already migrated. + This closes bug #1129. + +Unless some really serious new bug shows up, this will be the last release +until the next major version (3.0.0), which we hope will be ready around the +end of the year. +;;; + +Kern;;;26 July 2008 at 10:30am +Bacula version 2.4.2 Released +This is to inform you that we have released the source and Win32 binaries of +Bacula version 2.4.2 to the Bacula Source Forge download area. + + This is an important bug fix release since version 2.4.1. + +Bugs Fixed: + 1034, 1125, 1118, 1124, 1107, 1129, 1126 + +Change Summary: +26Jul08 +- When a migration job actually runs, re-check the Job record + and skip if the job is already migrated. This should + significantly reduce the problems with bug #1129. +- Break the do_swapping into do_unload, do_swapping, and + do_load. It is much more logical that way. +- Implement a set_dcr_from_vol subroutine in acquire.c for + reading volumes. This allows the dcr to be refreshed after being + zapped when the wrong volume is mounted. This should fix bug #1126 - +- During multiple tape restore, bacula + does not ask for physical tape change, but rereads same tape +- Apply patch submitted for bug #1107 with a small modification. + This fixes a bug where bcopy copied too many records. +- Make some tweaks to bsmtp based on patch submitted in bug #1124. + This fixes bug #1124. +- Make the default bat restore Pool be Any. This fixes bug #1118. +- Fix bug #1125 which reports a SD crash at the end of a tape + during restore. It was a debug statement that should not be + in a release. +- Fix #1034 by setting big timeout on mysql connections +- Do partial integration of the Win32 bat build created by Eric. +- Ensure that SD tried to mount a volume not in an autochanger + at least once before asking for operator intervention. +- Fix a pthreads bug in the Win32 pthreads emulation code affects only + version 2.5.x and above. +;;; + +Kern;;;7 July 2008 at 10:30am +Bacula version 2.4.1 Released +This is to inform you that we have released the source and Win32 binaries of +Bacula version 2.4.1 to the Bacula Source Forge download area. + +Bugs Fixed: + 1103, 1100, 1105, 1094, 1109, 1106, 1101, 1102, 1112 + 1117, 1116, 1097. + +Change summary: +- Clear in-use bit on vol when unused while swapping. +- Remove sleep at end of ./bacula +- Clear hash packet for hardlinked files correctly. This corrects + a long standing bug where hardlinked files selected individually + would occasionally not be restored. +- Apply Eric's patch to ensure that autoprune does not return + a Volume not in the autochanger unless requested to do so. +- Correct bat restore display of multiple drives. This fixes + bug #1117. +- Do find_a_volume() each time an unload is done. This + fixes the failure of maxvol2-test. +- Use Qmsg() in job.c watchdog callback. +- Release main control rwlock if ABORTing. +- Make watchdog connect timeout queue messages rather than sending + directly to avoid lock conflicts with the real thread. +- Remove const char that causes problems with Python, which has + older 'incorrect' headers. +- Add const char in dbd.c to avoid compiler warnings. +- Fix mtx-changer to detect both versions of Ubuntu (Debian) + mt. This fixes bug #1116. +- Fix failure of 2drive-concurrent-test. Always read label; + clear_unload() only after drive is defined in acquire_for_read(). +- Generally clean up the manual tape loading code. The main + conceptial change is that when a volume is marked to be unloaded, + its volume name is retained, and it is only marked as unloaded + when either the autoloader says it is unloaded or another tape + is read on that drive. +- Fix a recycling problem with two autochangers reported in bug + #1106. This may also (unlikely) fix a second recycling bug as + reported in #1103. +- Fix a SD lock volumes deadlock problem reported in bug #1100. +- Fix format problem in bscan output reported in bug #1105. +- Copy more data when restarting a job so that run + overrides are kept. This should fix bug #1094. +- Backport updates to jobq.c where possible. +- Fix bug where SD did not ask operator if the device could not + be opened. Reported by Eric. +- Add dbuser to DIR conf file (replaces user). +- Add --with-db-password to ./configure +- Fix regress to handle db_password. +- Fix a couple of pedantic compiler warnings. +- Fix bug when starting a restore on a storage that doesn't + have the requested MediaType. +- More work on word alignments -- eliminate all ints from + the configuration routines. +- Fix bug reported by Scott Barninger where the bacula script + refers to scripts in the wrong directory. Needed to meet the + requirements of recent FHS location changes. +- Fix word alignment problem on non-Intel 64 bit machines + such as Solaris. This should fix bug #1097 -- bus error in SD. +- Add missing win32/patches/wxWidgets.patch to 2.4 repository. +;;; + + +Kern;;;4 Jun 2008 at 10:30am +Bacula version 2.4.0 Released +This is to inform you that we have released the source and Win32 binaries of +Bacula version 2.4.0 to the Bacula Source Forge download area. + +This release consists mainly of a number of bug fixes since 2.2.x +but most importantly, a rewrite of significant portions of the +Storage daemon reservation and autochanger code. This rewritten +code is simpler, more stable, and works much better, particularly +with multiple drive autochangers than the prior code did. That +said, there are still a number of issues to be resolved. Note, +the new code has not been tested in manual volume mount situations. + +As usual, we strongly recommend when installing to keep the Director and the +Storage daemon on the same version. However, since this release only +contains refactored code and bug fixes rather than new features, the clients +(File daemons) should function perfectly with any 2.2.x version, and there is +no database upgrade needed. + +===================================================== + + Release Notes for Bacula 2.4.0 + + Bacula code: Total files = 500 Total lines = 188,654 (*.h *.c *.in) + +This Director and Storage daemon must be upgraded at the same time, +but they should be compatible with all 2.0.x File daemons, unless you +use some of the new features that affect the FD. In other words, you should +not have to upgrade all your File daemons when you upgrade. There is +no database upgrade needed from version 2.0.x to 2.2.0 nor from version +2.2.x to version 2.4.0 + +================== Warning !!!!!! ========================== +As of Version 2.4.0, the Win32 FD should not descend into +any reparse point directory or reparse mount points unless the +specified directory is explicitly mentioned at the top level of +FileSet (as with Unix). A file that is linked to another file will +be backed up, much like Unix hardlinked files. If you want +reparse directories backed up, you must explicitly include them +in your FileSet. +====================================================== + +This release consists mainly of a number of bug fixes since 2.2.x +but most importantly, a rewrite of significant portions of the +Storage daemon reservation and autochanger code. This rewritten +code is simpler, more stable, and works much better, particularly +with multiple drive autochangers than the prior code did. That +said, there are still a number of issues to be resolved. Note, +the new code has not been tested in manual volume mount situations. + +Bugs fixed: + 1095, 1086, 1091, 1070, 1041, 1083, 1078, 1066, 1068, 1038 + 1062, 1065, 1046, 1047, 1031 + +New features: +- You can now build bat without the QWT libraries. Use + --without-qwt as a ./configure option. + +Release Version 2.4.0 +- Update version to 2.4.0 to reflect the magnitude of the SD changes. +- Make sure to clear JS_WaitMedia when operator mounts a Volume. + This fixes bug #1095. +- Add create_postgresql_database.sql to Win32 installer. Should + fix problem reported by Juilio Monteiro. +- Get correct slot when auto unloading a device. This fixes bug + #1086. +- Fix possible seg fault if SQL error. +- Fix renaming a Volume, which used the wrong Volume name. +- If operator has rewind tape, print warning, release tape and + try once more. If tape is positioned somewhere, something went + wrong, so mark the tape in error and try once more. Previously + this error was fatal, now it produces an error message. +- Ensure correct volume name displayed during restore +- Fix a few more Coverity reported problems. +- Fix #1091 about bad output in estimate command. +- Modify autochanger locking to attempt to avoid race + conditions. +- Make sure device not busy before doing label command. +- Display open() errors except when polling. Previously too + many were suppressed. This should fix bug #1070. +- Fix Win32 reparse points. Bacula will not recurse into any + reparse point directory, including mount points, unless the + directory is explicitly mentioned at the top level (same as + with Unix). A file that is linked to another file will be + backed up -- much as Unix does for hardlinked files. + This fixes bug #1041. +- Remove StorageId test when pruning and recycling (Eric's changes). +- Fix buffer overruns detected by Coverity. +- Implement --without-qwt +- Fix layout of restore tree dialog +- Add configure bat QWT libraries, so that bat can be built + with or without the QWT libaries. +- Implement regression that explicitly tests swapping a Volume + from one drive to another. +- Enhance disk-changer to detect most error conditions. +- Fix SD code so that it properly swaps a Volume between drives. + This fixes bug #1083. +- Prevent a Volume that is being swapped from being freed from + the volume list. This will most likely fix, at least partially, + bug #1083. +- Fix strippath so that it does not get a buffer overrun and crash FD. + This fixes bug #1078. +- Make inability to change owner/group when creating a dir only a + warning rather than an error. +- Fix SQL query in migration code +- Fix bat seg fault at termination. +- Add Bacula generated version to bat about box. +- Backport development stream SD reservation system changes. +- When wrong volume is mounted during read, unload_autochanger. +- Stop searching for Volumes in SD askdir if DIR returns the + same volume name twice in a row. +- Rework class structures for VOLRES, DCR, and DEVICE to make + the method names a bit more logical, and for more logically + handling the responsibilities. +- Remove redundant code in terminating the scheduler that just + causes a seg fault in many cases. +- Improve algorithm for detecting pre-reserved volume and + swapping volumes. +- Prevent volume from being released while being swapped. +- Refactor parts of stored/mount.c +- Add sanity checks for VolWriteTime and VolReadTime +- Take care of bad clock changes while computing VolWriteTime + and VolReadTime. This should fix or limit #1066 +- Correct error string numbers in dird/catreq.c +- Restructure reserving, acquiring, and mounting volumes. Calls to + autochanger are deferred for mount.c -- simplifes the code. +- Do not prune any running job. It just fails the job. +- Lock the volumes when changing dev->reserved_device and marking + the volume unused otherwise the device can get reserved by + another job before the volume is released, thus blocking it. +- Correct some SD catalog request error messages. +- Turn off code in read_record that causes a seg fault in the SD + when reading past an EOS_LABEL. +- Turn off unloading the autochanger in reserve.c as it just + causes problems. +- Lock volumes when unreserving a device. +- Do not mark volume unused when recycling. +- Fix bug #1068 fixes a SD crash when using Virtual autochanger. +- Generate correct JobMedia records during spooling/despooling when + running concurrent jobs. Thanks to Tom Ivar Helbekkmo + for excellent analysis and testing. +- *Massive* commit of all fixes and back ports to create 2.2.9 + Mostly SD reservations enhancements. +- Fix Win32 FD backup/restore memory leak due to improper termination + of BackupRead/Write. This fixes bug# 1038. +- Fixes a StorageId problem with volumes after migration. +- Implements autostart scripts for Debian +- Fix mtx-changer.in for broken Debian mt program. +- Apply doc fix from bug #1062. +- Resolve crash and improper restore wx-console Win32 restore + GUI. Fixes bug #1065. +- Update Win32 wxWidgets to latest version. +- Attempt to do correct handling of Win32 mount points. Should + fix bug #1046. +- Add const to AIX prototype for initgroups() +- Fix to the JobMedia patch, which introduced a new problem. +- Fix creating first JobMedia record during Migration to include + proper index. This caused slow restores of migrated jobs. +- Fix bug #1047, do not strip paths on symbolic links. +- Set catalog backup database and user name from values specified on + the ./configure line. +- Apply patch to correct bug #1031, about wrong pool source information + in job report. +;;;; + +Kern;;;27 Jan 2008 at 10:30am +Bacula version 2.2.8 Released +Bacula version 2.2.8 source tar files as well as the Win32 +binaries are available in the bacula and Win32 release areas +of Source Forge. I have hidden the previous BETA release + +Version 2.2.8 is a bug fix to version 2.2.7 and has a few + additional bugs fixed than the BETA 2.2.8 version previously + released: +- It fixes bugs: 1036, 1033(doc), 1028, 1040, 1045(doc), 1030, + 1042(partially), and possibly bugs 1018 and 1032. + Bugs 1018 and 1032 involve problems with multiple-drive autochangers, + and are difficult to reproduce. + See the ChangeLog for more details. + Note, if you previously loaded version 2.2.8 BETA, you will probably + want to upgrade, but it is not urgent ... +;;; + + +Kern;;;9 Jan 2008 at 20:30 +Bacula version BETA 2.2.8 Released +Bacula version 2.2.8 source tar files as well as the Win32 +binaries are available in the bacula-beta and +Win32-beta release areas of Source Forge + +Version BETA 2.2.8 is a bug fix to version 2.2.7: +- It fixes bugs: 1036, 1033(doc), 1028, and possibly 1018 and 1032. + Bugs 1018 and 1032 involve problems with multiple-drive autochangers. +;;; + +Kern;;;24 Dec 2007;;20:30 +Bacula version 2.2.7 Released +Bacula version 2.2.7 source tar files as well as the Win32 +binaries are available in the Bacula release area of Source Forge + +Version 2.2.7 has several new features and several important bug fixes + since version 2.2.6: +- It fixes bugs: 1009, 1022, 1024, 1019, 1012, 1021, 1020 + 1007, 1008. For more details, please see the technotes-2.1 file. +- Fixed a seg fault reported by Frank Sweetser that depended on + exact path lengths, but the problem was in bsnprintf.c +- Double quoting include filenames (@xxx) in Bacula conf files is now + possible, thanks to a patch by Michael Stapelberg. +- You can pipe input to include filenames (@|prog) by using a vertical + bar, thanks to the above patch. +- A daylight savings time bug in the Win32 bsmpt was fixed by a patch from + Nerijus Baliunas. +- Marc Cousins submitted a patch that permits building the PostgreSQL + driver with version 8.3. +- The configure option --archivedir has been changed to --with-archivedir +;;; +Kern;;;9 Nov 2007;;15:25 +Bacula version 2.2.6 Released +Bacula version 2.2.6 source tar files as well as the Win32 +binaries are available in the Bacula release area of Source Forge. + +This release is a minor fix upgrade to version 2.2.5, +and we recommend that all users upgrade when they can. + +Version 2.2.6 is a minor bug fix realease to version 2.2.5 +- It fixes bugs: #1003, 942, 982, 990(response only), 991, + 993, 986, 976. + - Fix bat crash wen it cannot connect to Director. + - Fix joblist failure bug in bat. +;;; +Kern;;;9 Oct 2007;;15:25 +Bacula version 2.2.5 Released +Despite the fact that the Release Notes are rather short, the bug +fixes represent quite a lot of work: + +Version 2.2.5 is a major bug fix release to version 2.2.4 +- It fixes the following bugs: #961, 962, 963, 969, 968, 960, + 964, (possibly 935 and 903), 953, 953, 967, 966, 965, 954, + 957, 908, 958, and 955. +- It also improves listing performance problems in bat pointed + out by Chris Howells. +;;; +Kern;;;29 Sept 2007;;20:30 +A serious data loss bug in Bacula version 2.2.4 found and fixed + +This bug was very elusive and time consuming to track down. It +turned out to be a race condition that can lose the last one or +two blocks of a Job, which can happen in rare cases only when +running multiple simultaneous jobs when a volume fills and one +Job finishes receiving the last data from the FD and at the same +time a second job detects the end of the Volume. The bug was +introduced in version 2.0.0 and did not exist in version 1.38.x. +If the bug is triggered, the data is lost (not written to the +Volume), and it can occur for any backup job of any level under +the conditions noted above. + +The bug is reported in the bugs database as bug #964, and just +this morning I found and tested a fix, which is attached as a patch +to the bug report. The patch (2.2.4-lost-block.patch) is also +uploaded to the bacula-patches 2.2.x release area. This bug may +also be part of the problems reported in bug #935 and possibly +#903. + +Also in the bacula-patches 2.2.x area, you will find other +patches that fixes bugs #953, 966, 967, 965, 958, 908, and +955. Please refer to bugs.bacula.org for the details. + +Though this bug quite serious (data loss), it should be rare. +However, we recommend everyone to apply the patch. +;;; +Kern;;;2007/9/14;;;14:30 +Bacula version 2.2.4 Released + +This version of Bacula is a minor bug release to version 2.2.3. +It contains the following fixes: + +- Possible fix for authorization problems bug #953. +- Possible fix for bug #908. +- Add waits to multiple exit detection code to try to force pid + file to always be deleted. +- Restore good dev.tar.gz to rescue set appropriate binary property. + This fixes bug #950. +- Fix seg fault in error exit of acquire_for_read after unsuccessfully + trying to switch drives by checking for blocking before unblocking. + Fixes bug #906. +- Cancel storage daemon in all cases where FD reports error. This + should fix virtually all cases of bug #920 and will ensure that Devices + are released as soon as possible. +- Fix error message that was clobbered when Dir tells SD it does not + have write permission on Volume. This should fix a minor point + in bug #942, but not the main problem. +- Fix migration code to get correct Volume name with multiple volumes + by skipping |. Fixes bug #936. +- Implement patch supplied by Landon to fix bug #944 where using + TLS with bconsole uses 99+% of the CPU. +- Fix bug #946 about "bacula-dir -t" which doesn't works + as expected. +- Using "m" in bconsole will show messages as in prior versions + and not memory usage. + +- Note, you need GTK >= 2.10 to be able to link the Tray Monitor + program. +;;; +Kern;;;2007/9/9;;;14:30 +I regret to announce that there is a rather serious bug in Bacula. + +Bacula bug #935 reports that during a restore, a large number of files are +missing and thus not restored. This is really quite surprising because we +have a fairly extensive regression test suite that explicitly tests for this +kind of problem many times. + +Despite our testing, there is indeed a bug in Bacula that has the following +characteristics: + +1. It happens only when multiple simultaneous Jobs are run (regardless of +whether or not data spooling is enabled), and happens only when the +Storage daemon is changing from one Volume to another -- i.e. the +backups span multiple volumes, and it only happens for Jobs writing +to the same volume. + +2. It has only been observed on disk based backup, but not on tape. + +3. Under the right circumstances (timing), it could and probably does happen +on tape backups. + +4. It seems to be timing dependent, and requires multiple clients to +reproduce, although under the right circumstances, it should be reproducible +with a single client doing multiple simultaneous backups. + +5. Analysis indicates that it happens most often when the clients are slow +(e.g. doing Incremental backups). + +6. It has been verified to exist in versions 2.0.x and 2.2.x. + +7. It should also be in version 1.38, but could not be reproduced in testing, +perhaps due to timing considerations or the fact that the test FD daemons +were version 2.2.2. + +8. The data is correctly stored on the Volume, but incorrect index (JobMedia) +records are stored in the database. (the JobMedia record generated during +the Volume change contains the index of the new Volume rather than the +previous Volume). This will be described in more detail below. + +9. You can prevent the problem from occurring by either turning off multiple +simultaneous Jobs or by ensuring that while running multiple simultaneous +Jobs that those Jobs do not span Volumes. E.g. you could manually mark +Volumes as full when they are sufficiently large. + +10. If you are not running multiple simultaneous Jobs, you will not be +affected by this bug. + +11. If you are running multiple simultaneous Jobs to tapes, I believe there is +a reasonable probability that this problem could show up when Jobs are split +across tapes. + +12. If you are running multiple simultaneous Jobs to disks, I believe there is +a high probability that this problem will show up when Jobs are split across +disks Volumes. + +13. The bug concerns only the Storage daemon so there is no need to update +the clients, though I do recommend updating the Director when installing +an updated Storage daemon. + +I have uploaded patches to bug #935 (bugs.bacula.org) that will correct +version 2.2.0, 2.2.1, and 2.2.2. The patch has been tested only on version +2.2.2 and passes all regression tests as well as the specific test that +reproduced the problem. + +The patch has now been confirmed to fix the problem reported, and Bacula +version 2.2.3 has been released to Source Forge. + +For the technical details of the bug, please see: + + http://www.bacula.org/downloads/bug-935.txt + +;;; + +Kern;;;2007/8/11;;;14:30 + +Bacula Version 2.2.0 has been released to Source Forge. + + Release Notes for Bacula 2.2.0 + + Bacula code: Total files = 520 Total lines = 195,550 (*.h *.c *.in) + 82 new files, 41,221 new lines of code, 208,380 lines of change from 2.0.3 + +This Director and Storage daemon must be upgraded at the same time, +but they should be compatible with all 2.0.x File daemons, unless you +use some of the new features that affect the FD. In other words, you should +not have to upgrade all your File daemons when you upgrade. There is +no database upgrade needed from version 2.0.x to 2.2.0. + +Areas requiring caution or testing: +- You must have the thread safe version of MySQL client libraries loaded + to build with MySQL enabled. +- Volumes are pruned only when absolutely necessary -- this may cause + your database to grow compared to prior Bacula versions. +- Solaris door and even port files are no longer restored (equivalent + to what we do with sockets). +- SQLite is no longer supported for Solaris -- it fails too often with + bus errors. SQLite3 should work on Solaris. +- The default setting for SQLite3 is now 'PRAGMA synchronous=OFF'. + This makes it run 30 times faster, but increases the possiblity + of a corrupted database if your server shuts down unexpectedly. + The default behavior can be changed in src/version.h +- Restore on Win32, and in particular on Vista is untested. Please + test before relying on it. It should backup and restore reparse + points. +- Win32 servers are untested, and very likely not to work. + +The major new features are: +- Much faster insertion of attributes (somewhere around 10 times), + many thanks to Eric Bollengier and Marc Cousin. +- First release of bat (Bacula Administration Tool). Note to build + bat you must explicitly enable it on the ./configure line, you + must have the Qt4 version 4.2 or later libraries loaded, the qwt + (Qt Graphics) package loaded, and qmake and the other Qt4 tools + must be available. Most of the implementation was done by Dirk Bartley. +- Red/Black restore in memory tree (500 times faster loading). +- The Regex Where code to allow easier relocation of restored files + thanks to Eric. +- Socket level heartbeat for all connections (untested). +- posix_fadvise() use in the FD to improve performance reduces + swapping due to opening/reading lots of files. Win32 equivalent + implemented. +- Much improved Volume reservation code that should eliminate most + conflicts experienced in multiple drive autochangers. +- Simpler locking in the SD in the reservation system. +- Detection of file size/date change during backup if enabled. +- New Recycle Pool feature -- thanks to Eric. +- Efficient implementation of very large include/exclude lists. +- Volumes are no longer pruned during 'status dir' +- Pruning is now more efficient, and if a Volume is purged, + during pruning, it is immediately discovered. +- License is now GPL v2 without modifications, fix a few copyright + mistakes made when adding FSFE copyright notice. + +New ./configure options: +- --enable-bwx-console +- --enable-bat +- --with-qwt= +- --with-db-name= +- --with-db-user= +- --enable-batch-insert + +New bconsole commands: +- exec +- memory +- update recyclepool +- .sql +- .api +- .pwd (in restore tree) +- restoreclient (keyword) +- backupclient (keyword) +- regexwhere (keyword) +- update jobid (new command) +- recyclepool (keyword) + +New directives: +- Heartbeat Interval (bconsole.conf) +- Heartbeat Interval (bacula-dir.conf in Director, Client, Storage) +- TLS Allowed CN (bacula-dir.conf in Client) +- Regex Where (bacula-dir.conf in Job) +- Strip Prefix (bacula-dir.conf in Job) +- Add Prefix (bacula-dir.conf in Job) +- Add Suffex (bacula-dir.conf in Job) +- Recycle Pool (bacula-dir.conf in Pool) +- FailJobOnError (bacula-dir.conf in RunScript) +- CheckFileChanges (bacula-dir.conf in FileSet) +- StripPath (bacula-dir.conf in FileSet) + +Other features or bug fixes: +- Fixed bugs: 916, 910, 917, 914, 906, 907, + 842, 830, 893, 861, 888, 886, 807, 877, 872 + 885, 887, 864, 874, 882, 881, 863, 859, + 856, 854, 845, 847, 846, 809, 772, + 822, 825, 824, 808, 802, 797, 798, 795, 789, 791, + 788, 780, 763, 782, 612, 767, 775, 621, 772, 764, + 766, 621, 761, 755, 750, 741, 747, 742, 744, and 743. +- Configure bat with --enable-bat. Define qwt libraries with + --with-qwt=. See Installation chapter of manual for details. +- Create a depkgs-qt package that has both Qt4 and qwt, which are + needed to build bat. Most modern Linux systems will have both + these packages in the distro. +- Storage overrides delete all previous storage definitions instead + of prepending. +- One should be able to mount and unmount removable devices if the + Device resource has Removeable Media set and the mount and unmount + directives are defined. +- ./configure will do a better job of searching for qwt libraries. +- The Win32 version can no longer be shutdown from the tray monitor. + Use the command line or the Services panne. +- Keep prune_volumes() from pruning the whole Scratch pool. +- More debug output in status storage. +- Correct moving a Scratch volume from pool to pool (some + critical columns were lost). +- Different locking in reservations and despooling systems, + which means more micro-locking and less macro-locking, which + should give a lot more concurrency at the expense of slightly + (<0.1%) more overhead due to more locking/unlocking, but + concurrent jobs should run much faster. +- Additional drive reservation algorithm that should solve a lot of + the problems experienced with multiple drive autochangers. +- Storage daemon status command enhanced to more clearly show Volume, + pool and media type when a job is waiting. +- Made bsmtp work with more strict SMTP servers. +- Detect doubly freed buffers in smartall.c +- wx-console renamed to bwx-console (Fedora request) +- gnome-console renamed to bgnome-console (Fedora request) +- Migration preserves original job's FileSetId +- Spooling implemented for migration jobs. +- Config files can be read through a pipe, by specifying a leading | + in front of the configuration path/filename. +- New memory command (bconsole) that will print the current Director's + memory usage, and an in use buffer dump. +- Console name changed from *Console* to -Console- to accomodate Win32 + filename restrictions. +- Corrected the Win32 ftruncate bug. +- Additional version information added to Job reports. +- New -8 option for bsmtp to specify UTF-8 encoding type. +- bsmtp will no longer add < > to target (from, to, cc) if there + is already a < in the target. +- Prefer Mounted Volumes extended to mean a volume that is being + mounted by another job. +- Runscript timing set to same as version 1.38.11 +- New TLS Allowed CN directive(s) permitted. +- New bconsole 'exec' command to run external script/command. +- Turn on FreeBSD/OpenBSD code to set EOT model on tape. +- Drop from root done before database is opened. +- Database user and name can be configured with: + --with-db-name=name --with-db-user=user +- Turn on wait_for_drive in mtx-changer script. +- Rework how bar codes are handled in mtx-changer script. + This appears to have been an unreported bug. +- Updated nagios plugin supplied by Christian Masopust +- Better restricted console ACL checking. +- New Client Connect Wait directive in Storage daemon so that + users can configure how long SD waits for FD connection. +- Bacula will no longer permit pruning of the currently running + job (note, if other jobs are running, they may be pruned). +- Sockets are no longer restored. +- dbcheck works in 300K chunks so will typically run faster. +- Include/Exclude lists can now be efficiently handled for quite + large sizes -- tens of thousands of entries. +- Several memory leaks in migration and database usage were fixed. +- New console keyword restoreclient, which specifies the client to + which the restore will be sent. The client keyword specifies + the backup client. The restoreclient keyword is optional if it is + not specified, the backup client will also be the restore client. +- The disk file size is now checked to ensure that it agrees with the + catalog value before Bacula will append to the disk (same as tape + and DVD). + +;;; + +Kern;;;2007/3/6;;;14:30 + +Bacula Version 2.0.3 has been released to Source Forge. +This is a bug fix release to version 2.0.2. If you are upgrading from +a version older than 2.0.0, please be sure to read the important notes +below. + +Also, please check the patches directory in the current SVN or the +patches release section on Source Forge for important bug fixes to +this version. + +5Mar07 +kes File migrate bug with Pool Occupancy using mediaid instead + of jobids. Fixes bug #795. +kes Fix orphaned buffers in filed backup and verify due to + crypto buffers not freed during errors. Fixes bug #789. +04Mar07 +kes Add smartctl call to bacula-sd.conf as an example of getting + tape alert info. +02Mar07 +kes Add Client Connect Wait to Storage daemon to permit users to + modify the time the SD waits for a FD connection. +28Feb07 +kes Apply Command ACL filter to JobId list in restore command. +kes Correct typeo in var.c patch. +27Feb07 +kes Don't let Bacula prune File or Job records for the current Job. +kes Fix variable substitution pad + inc bug reported (with patch) + in bug #791. +26Feb07 +kes Correct SQLite log table index as reported by Luca Berra. +24Feb07 +ebl Fix FIFO stuff, bacula tries to rewind the FIFO... Thanks to Andreas +22Feb07 +kes Fix a few places in lib/message.c where the open fd may + not be zeroed. +21Feb07 +kes Add LANG=C to autoconf/randpass so it works with languages other + than English. Fixes bug #788. +20Feb07 +ebl Revert ClientRunBeforeJob as it was in 1.38.x + This fixes bug #780 + You will not be able to generate Include/Exclude list any more. + If you want to use this, you can apply + trunk/bacula/patches/testing/clientrunbeforejob_can_generate_include_exclude_list.patch +19Feb07 +kes Restore of sockets created false error messages because Bacula + no longer restores sockets, but the code was still trying to + set the attributes on a non-existent file. Reported by a user. +16Feb07 +kes Fix encryption deblocking bug, which caused some restored files + to be truncated. This fixes bug #763. This is a CRITICAL bug fix. +kes Add FD event sequence order prepared by Eric -- for RunScripts. +kes Fix 12am/pm bug as reported in bug #782. +15Feb07 +kes Add quick disconnect FD code from 2.1.4 to 2.0.3. This code + causes the SD to release the FD as soon as the FD has sent + all the data to the SD. After that the SD will do any final + despooling (data and attributes) that are necessary. This + allows laptops to disconnect much quicker from the network + after a backup. +13Feb07 +kes Apply Eric's ClientRunScriptAfter patch to 2.0 and 2.1. +11Feb07 +kes Optimize the use of the database a bit in the Status dir command. + Only open it when needed, ensure that if any previous database + was opened, it is closed. +10Feb07 +kes Modify dbcheck to handle orphaned JobMedia, Path, Filename, + and File records in 300K chunks to be more efficient. This + idea came from Juan Luis Frances (if I remember right). +09Feb07 +kes Update projects list. +08Feb07 +kes Fix dird/ua_cmds.c so that a cancel command checks if the + console is authorized to cancel the job. This fixes bug + #767. +kes Modify SD so that the VolCatJobs medium record is updated + at the beginning of a Job rather than the end. This + fixes bug #775 where exceeding MaxVolJobs caused jobs + to fail. +kes Added a mutex around getting and setting Volume information + so that multiple simultaneous jobs will single thread. +07Feb07 + Switch to using Subversion +kes Remove src/pygtk-console/ from configure +06Feb07 +kes Delete src/lib/btree.c from win32 build, then add rblist.c + plus the entrypoints. +kes Apply patch supplied that corrects debug print + in canceling jobs for max run time. Supplied as + part of bug #621, which was previously fixed. +05Feb07 +kes Test on job_canceled() and sd_msg_thread_done inside + loop starting the message thread to avoid a race condition. + Fixes bug #771. +kes Remove rl_catch_signal from console.c as it conflicted + with the header definition. Fixes bug #765. +ebl Fixes bug #766 about RunsOnClient = Yes (case sensitive) +04Feb07 +kes Clarify some stored/acquire messages to indicate if the + problem is with read or append. +02Feb07 +kes Fix memory leak with storage ids in cats/sql_get.c +kes Terminate watchdog earlier to avoid reference to released + memory -- reported by Jason Austin. +kes Move closing the database from jobq.c to the director daemon + termination routine. This fixes memory leaks for shadow jobs + (i.e. migration jobs). +kes Free up the unique jobid chain items in migrate.c. This fixes + a memory leak problem. +kes Convert some ugly looking for statements to use foreach_alist + in findlib/find.c. This will facilitate converting the structures + to use dlist (for large include/exclude lists). +kes Fix a bug in the btree.c and btree.h routines, then rename them + rblist and add them to be built in src/lib. Include some new + methods written by Rudolf Cejka that make the code more readable + (hides some of the ugly casting). +26Jan07 (back port) +kes Implement item #12 on project list -- quick release of FD by + the SD. This is noted in more detail above. + +;;; + +Kern;;;2007/1/28;;;14:30 + +Bacula Version 2.0.2 released: +28Jan08 +kes Fix maxruntime bug #621. +27Jan07 +kes Get current main CVS .specs for RedHat, SuSE, Mandrake. +26Jan07 +ebl Implement the include JobID in spool file name project. +kes Reorder projects file in order determined by Jan 2007 vote. +kes Fix open of SQLite3 db where user does not have write permission + so that DIR does not crash. Fixes bug #761. +25Jan07 +kes Change 'Device not configured to autolabel' from INFO + to WARNING. +kes Fix jobq.c to restart failed jobs when Reschedule Times = 0 + which should restart an indefinite # of times. +kes Fix configure --help to print --with-mysql[=DIR]. Same for + other DIR specifications. +23Jan07 +rn Fix msvc build problems. Fix bacula.dll exports for msvc build. + Fix path quoting in SQLite scripts. + Fix problems with SHGetFolderPath. +19Jan07 +kes Create patches/2.0.1-restart.patch. Fixes bug #755. +18Jan07 +kes Fix Job restart on error bug that promotes an Inc to a Full + backup. This should fix bug #755. +kes Add qt-console and first cut of code. + +;;; + +Kern;;;2007/1/13;;;14:30 + +Bacula Version 2.0.1 has been released to Source Forge. +This is bug fix update to version 2.0.0 and contains +the following fixes: + +- Fix Bacula->Documentation link on Win32 to point to index.html + instead of bacula.html. Fixed bug #750. +- Return JobId in db_get_job_record() when JobId==0. This should + fix bug #741. +- Do not release source pointers when restarting a failed job. +- Add dynamic dll entry point for SHGetFolderPath to Win32 code. + This *should* fix bug #747. +- Modify winbacula.nsi to substitute with g bin_dir_cmd. Should fix + bug #742. +- Modify USTORE constructor to set an empty store_source string, + and don't copy the store_source string in a cancel. Hopefully + this will fix Arno's seg fault, bug #744. +- Add back code to disable conio in configure. Fixes bug #743. +- Correct the Options scanner in the FD to correctly handle + SHA1 option, which was eating the next option. Reported by + Sebastien Guilbaud. +- Add code to indicate when the SD is spooling, spool wait, and + despooling as requested by Alan Brown. + +;;; + +Kern;;;2007/1/4;;;14:30 + +Bacula Version 2.0.0 has been released to Source Forge. + +There is an English Press Kit, written by Dan Langille at: + + http://www.bacula.org/about/press/presskit200.html.en + +and a German version, translated by Arno Lehmann at: + + http://www.bacula.org/about/press/presskit200.html.de + +;;; + +Kern;;;2007/1/4;;;14:31 + + Release Notes for Bacula 2.0.0 + + Bacula code: Total files = 438 Total lines = 154,329 (*.h *.c *.in) + +==== IMPORTANT Catalog update required ===== +- The database format has been updated from what was used in + Bacula 1.38.x. You must manually update your database before + running Bacula 1.39.x or higher. If you are using Bacula supplied + RPMs this is not necessary as the RPM does it automatically. + Please backup your previous version of the database before + running the update. The update script will be automatically + installed in your scripts directory, or can also be found in + /src/cats. It is called: + + ./update_bacula_tables + + It is necessary to run it only once the first time you move to + a 2.0.0. Upgrading the Bacula version thereafter does not + require updating the database again. Depending on the size of + your database the script make take a bit of time, to run, but + in general, it should be very fast. + +==== IMPORTANT new Win32 install procedure ===== + For Win32 migrations from versions prior to 1.39.0 nothing special + needs to be done to upgrade. Everything should be taken care of + automatically. The only thing not done is to delete the old C:\bacula + directory mostly out of paranoia. + +==== IMPORTANT miscellaneous ==== +- The Gnome console program (gconsole) no longer functions as it + should.More importantly, in restore mode, the restore tree is + no longer shown in the left pane. I suspect this is due to + incompatible changes in the GTK+ API, and hence have given up + on gnome and gtk+, as this has already happened several times + previously. At some point there will be a new GUI console. +- The bacula-dir.conf directive Accept Any Volume has been + removed because it was never implemented. You must delete all + occurrence of this directive for the Director to run. The Storage + daemon will automatically accept any valid Volume that you mount. +- The --mandir ./configure option now points to the top level man + directory. The man files will be installed under mandir/man8 and + mandir/man1 as appropriate. +- You *should* be able to use 1.38.x FDs with version 2.0.0 Director + and SD providing you do not use any of the new features (runscript, + data encryption). It seems to work here, but we do not guarantee it. +- Your Director and SD must be simultaneously upgraded. +- The restore command no longer uses the MediaType as the primary method + of finding a suitable Storage device. Normally it will select the last + device used to write a Volume. If no storage device is defined, it + will use the old algorithm which selects the first Storage resource + with the correct MediaType. +- The MD5/SHA1 hash codes kept in the database are now kept in a binary + format compatible with the rest of the world. If you are running verify + jobs, you *must* do an InitCatalog or all files will show an MD5 + difference. Also, authentication uses the new algorithm by + default, but *should* accept connections from older components (FD) using + the old non-compatible algorithm. This has been tested, but more + more testing is still needed. +- A stock SuSE 10.1 kernel may crash when Bacula runs and accesses + the tape drive. Workaround, load the SuSE 10.1 version 2.6.16.21-0.25 + kernel or later. The SuSE 10.2 Alpha 5 or later kernel also works. + This problem may also be present in certain Fedora FC5 kernels. +- If you have been using the data encryption feature of 1.39.x, please + be aware that certain combinations of encryption and other options + with version 1.39.0 through 1.39.26 created Volume data that cannot + be restored. We strongly recommend that anyone using encryption + carefully review his/her backups and at a minium do a Full backup + with 1.39.28 of all encrypted data. Robert Nelson has identified + and fixed it as follows: + As of 1.39.27: + No filters = Works fine + Sparse = Works fine + Compression = Works fine + Encryption = Works fine + Sparse + Compression = Works fine + + Sparse + Encryption = Restore broken + Sparse + Compression + Encryption = Restore broken + Compression + Encryption = Restore broken + + As of 1.39.28: + Most combinations work, but some encrypted files are + not properly restored. + + As of 1.39.30: + All combinations work fine except Sparse+Encryption. + + Bottom line, if you are using data encryption, please test restoring + data to be sure it all works correctly. +- The current Volume format written by 1.39.22 is different from + the format written by previous versions. The two formats + are not compatible. Thus any DVDs written prior to 1.39.22 will + be unreadable by version 1.39.22. +- If you previously run a Bacula version prior to 1.39.30, the JobMedia + data may not be correct for disk Volumes. This can cause incorrect + seeking in versions after 1.39.30. If you experience what appears to + be data I/O or integrity errors during restores, please add the + following directive to your disk DEVICE resource in the Storage + daemon conf file: + + Block Positioning = no + + This will turn off all seek requests during restores and avoid + this problem. +- VSS for Windows clients is now enabled by default. +- Do not unload autochanger when doing "update slots" +- Implement mount command for autochanger, see manual. + +New Features in 2.0.0: +- Turn on disk seek code for restores. +- There is a partial but reasonable translation of the Bacula + messages for French. To install it, first configure and build + Bacula, then as root run: + + cd /po + make install + + If you have your locale set properly you will get the translated + messages. +- Bacula now support Migration jobs that are documented in a new + Migration chapter in the manual + http://www.bacula.org/dev-manual/Migration.html +- Data encryption is now implemented and is documented in + a new chapter of the manual at: + http://www.bacula.org/dev-manual/Bacula_Data_Encryption.html +- Additional support for removable devices. See the + Requires Mount, Mount Point, Mount Command, and Unmount + Commands in the Storage daemon configuration chapter: + http://www.bacula.org/dev-manual/Storage_Daemon_Configuratio.html + Also see the Edit Codes for Mount and Unmount Directives in the + same chapter. +- Switch the Win32 build from using Microsoft C++ to using mingw32 + cross-compiling. The initial work was done by Howard Thomson, + then tweaked by me. Robert Nelson then totally reworked the + cross-compiling code so that it not only cross-compiles, but + also compiles on Visual Studio, and at the same time, he added + all the current Unix features to the FD, such as selection on + drives, encryption support, building *all* the tools, ... +- The Director and Storage daemon have now been ported to Win32. + This code is working but should still be tested carefully + before putting into production. +- Bacula restore and bextract can now extract non-portable Win32 data to + any client (including Unix/Linux clients). Of course, in doing so, + the Microsoft specific permissions and ACLs will be lost. Thanks + to Thorsten Engel for this code. +- The 260 character limitation for Win32 paths name lengths is now + eliminated thanks to Thorsten Engel. However, if you are using + Volume Shadow Copy, please be careful to specify all the paths + in the bacula-fd.conf file using a full path notation including + the drive letter. +- Eric Bollengier wrote new RunScript directives that includes + the old RunBefore/AfterJob and ClientRunBefore/AfterJob features + plus a *lot* more, allowing you to control just about every aspect + of running scripts. See the manual for detailed documentation. + http://www.bacula.org/dev-manual/Configuring_Director.html#5227 +- SunOS ACLs should now work thanks to a patch from David Duchscher. +- 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" + This can be used to preview the next scheduled job (and the + next tape to be used) on Fridays if there are no scheduled jobs during + the weekend. +- From Eric Bollengier. One can now using the bconsole wait command do: + wait (wait for all jobs to stop) + wait jobid=nn + wait jobuid=unique id + wait job=job-name +- Volumes can now be set to Enable, Disable, or Archive. If they + are not enabled, Volumes will not be mounted. + Implement update volume enable=(on|off|true|false|archived|0|1|2) +- Add Catalog message destination in Messages resource that puts the + job report in the Log database table. +- Writing/reading DVD Volumes is much more stable -- to the point + of being useful. Thanks to Richard Mortimer. +- Add enable/disable job=. This command prevents + the specified job from being scheduled. Even when disabled, + the job can be manually started from the console. +- The database Id records should be 32/64 bit independent now. 64 bits + can be enabled by changing one define and changing the appropriate + table variable. Normally, you need 64 bits only for FileId. +- Relative path specifications (i.e. ../xxx) are now permitted in + the restore cd command. +- When running multiple simultaneous jobs, most jobs that use spooling + will now finish faster due to a mutex optimization made by Eric + Bollengier. +- Conf files containing UTF-8 marker at the head of the file as well as + conf files containing Window cr/lf and Mac cr line termination characters + are now accepted thanks to Robert Nelson. +- Windows tray status windows are scrollable and resizable. +- Win32 external script execution is much more flexible -- handles + spaces in names better, ... +- Lots of DVD fixes -- writing DVDs is now reported to work. +- Fix opening of database in a restricted console to respect + any Catalog ACL. +- Much better automatic handling of multiple database catalogs in + the restore command. +- Permit multiple console/director resources in bconsole.conf. + patch from Carsten Paeth calle@calle.in-berlin.de +- Character substitution in Job/JobDefs WriteBootStrap. + from Eric Bollengier. +- Apply patch supplied in bug #656 to pass priority field + in the run dialog to the Director in gnome console. +- Add support of encrypted data stream to bscan from Eric. + display data_len instead of data content (may be binary). +- Add Enabled=xxx on update slots command. +- Add host:port to connect failure messages to FD and SD from Dir/ +- Add WhereACL to console ACL list. If nothing is specified, only + the default is permitted for restore. Otherwise, *all* allows any + path, or you can specify permitted paths. This should allow control + over where users can restore files. This is untested. +- Install man pages with 'make install'. +- Add Media.Enabled flag to client backups for dotcmds.c +- Enforce Media.Enabled=1 for a current restore to work +- Require restore case 3 to have sqlquery permission to work. +- Add -n option to bconsole to turn off conio -- used in bweb. +- The bytes field in the terminated jobs part of the status + command now reports in KB, MB, ... units. +- When not descending into a directory, print the File= name that + triggered it -- makes why not descending a bit clearer +- Do not unload autochanger when doing "update slots" +- Implement mount command for autochanger +- Fix bug #462 incorrect error message printed when client script called + from File= was not found. +- Fix bug #558 (waiting for feedback) where Bacula needs too much time to + do a rewind on Solaris when no tape is in the drive (Solaris does not + have the detailed errno found on Linux). Added Solaris specific code. + Note, this may apply to other OSes as well. +- The examples directory has a new bacula_mail_summary.sh file that + creates a single email summary of any number of jobs. Submitted by + Andrew J. Millar. +- Add nagios plugin to the examples directory. Submitted by + Christian Masopust. +- Modify most restore error messages to be queued so that they + appear at the end of the job rather than mixed with the restore + listing where they could be "lost". +- Apply patch supplied by user (slightly modified) to fix + correct detection of holes in block devices and FIFOs. + Bug # 506. +- Added a report.pl program to the examples directory from Jonas Bjorklund. +- 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, ...). +- Implement new code for changing userid and group at startup. This + should get Bacula into the correct groups. +- Implement support for removable filesystems -- device type directive + and mount, unmount directives. +- Transfer rates are now presented in a more readable format thanks + to a user submission. +- SD is now aware of what volumes are mounted. More information is printed + in the Status report. You must take much more care now to unmount + devices prior to removing tapes that Bacula has open or prior to + changing a magazine. Don't forget to do a mount afterwards or the + device will be blocked. +- The Pool Maximum Volumes directive is now respected in all places. +- A Storage device can now be specified in a Pool resource. It will override + all other Storage specifications. +- Most but not all directives accept true/false in place of yes/no. +- A patch from Karl Hakimian that reads JobIds, FileIndexes + from a database table for restore. +- There are a number of new tables. Some such as the Location table are + designed for user use in doing Volume Management software. +- Maximum Changer Wait, Maximum Open Wait, Maximum Rewind Wait to + accept time qualifiers. +- Implement jobuid to replace old usage of job in keywords as + suggested by Eric Bollengier. +- Implement write variables for Python to set Priority (anytime), and + Job Level, only during JobInit event. +- 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 the SD to use multiple drives during a backup/restore (only + one at a time). +- Integrate addition of line count limitation to bsmtp -l from + Sebastian Stark +- 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 +- Remove automatic case folding on Windows FDs. You must + explicitly use the 'Ignore Case = yes' option. +- Implement wild program in tools directory for testing + wild-cards. Almost identical to the regex program. +- Use the new bregex.c to implement Regex expressions on Win32. +- Apply patch from Christopher Hull + - Allow multiple connections to database with different + parameters. + - Invalidate the scheduler when doing a reload. Fixes seg + fault, but still 60 second window. + - Additional info in Reschedule message. + - Use set_jcr_job_status() everywhere to prevent loss of + cancel, error. + - Display peer IP in FD if error from connecting DIR. + - Don't increment file count for DIRBEGIN. + - Replace illegal characters in Win32 filename by _. + - Add SE_CREATE_PERMANENT_NAME privilege in Win32. + - Hash hard link filenames rather than linked list (performance). + - Fix for security failure in chdir on Win32. + - Add CreateDirectoryA/W win32 API entry points. +- programs to duplicate Bacula's base64 algorithm using standard + routines. This fixes bugs #296, and 565. Patch submitted by + author of bug #565. +- Fixes to reloading the Dir conf file from Eric Bollengier and Christopher + Hull. +- Modify LICENSE to correct some problems pointed out by Debian. +- Apply a patch submitted by cesarb in bug #606 to implement O_NOATIME support. + O_NOATIME is a open() flag which makes it possible to read a file without + updating the inode atime (and also without the inode ctime update which + happens if you try to set the atime back to its previous value). It also + prevents a race condition when two programs are reading the same file, but + only one does not want to change the atime. It's most useful for backup + programs and file integrity checkers (and bacula can fit on both + categories). + You enable it in the Bacula FileSet Options resource by setting: + noatime = yes + The effect of this option is similar to the keepatime option except + it is more efficient and avoids modifying ctime. +- Implement a pile of new man pages contributed by Jose Tallon. +- Modify the database format for handling Migration jobs: + Add PriorJobId, RealEndTime to Job table + Delete MAC table + Remove Stripe from JobMedia record (not used, wasting space) + Add ScratchPoolId, RecyclePoolId, Enabled to Media record + Add Cost to Location table. + Enabled to Media table and Location table. +- Security: harden authentication failure in FD by single threading errors + and forcing a 6 second wait. +- If using GCC (actually g++) add the following compiler flags + -fno-strict-aliasing -fno-exceptions -fno-rtti +- Turn on new bsnprintf() code. The reason for this code is to + eliminate the security problems associated with using the + system libraries print routines. +- Implement job report that indicates where Storage and Pool + came from -- with overrides and Pool storage and NextPool, + it is all very complicated. +- Add more detail (Storage, Device) to list of volumes printed + for restore. +- Add new VOLMGMT message class. No messages are yet sent with this + class. +- Improved Bacula rescue procedures -- see the Disaster Recovery + chapter of the manual +- Add spooling/despooling info in status output of SD. +- Add Comment field to llist of a volume. +- Allow true/false in many but not all yes/no directives. +- The Bacula source code is now copyrighted by the Free Software + Foundation Europe. The Developer's Guide documents the new procedures, + and the LICENSE file has been updated. +- Apply Jaime Ventura's patch that implements the Messages resource + Mail On Success directive. +- The Client returns its Version string, which is printed in the Job + report. +- The Client returns whether or not VSS and Encryption are used, which + are printed in the Job report. + +Additional Features Added for Win32: +- Added DriveType directive to the Director's Include Option FileSet + resource. Allowed values are: fixed, removable, cdrom, and remote. There + is only an implementation for Windows because it is the only platform that + has the concept of drives. + +- Adds EnhancedWild directive to the Director's Include Option FileSet + resource. Allowed values are: yes and no. + + When EnhancedWild is enabled then the processing of the + Wild, WildDir and WildFile is changed in the following ways. + + Patterns conform to Posix + \ is not a special character in character classification [] + To match a - it must be the first or last character + To match a ] it must be the first character + + fnmatch option FNM_FILE_NAME is specified * doesn't match a / + so it won't match multiple directory levels in a path + +- Relative WildFile patterns (ones without a leading /) match + against the filename portion. This in combination with the + FNM_FILE_NAME fnmatch() flag makes directives such as WildFile = + abc*.def work as expected. + +- Adds support for the shell's feature of brace expansion. + + Here is an example where braces allow 24 lines to be expressed in 5. + + # Exclude directories full of lots and lots of useless little files + WildDir = "[A-Z]:/{Documents and Settings,{WINNT,Windows}/Profiles}/*/Cookies" + WildDir = "[A-Z]:/{Documents and Settings,{WINNT,Windows}/Profiles}/*/Recent" + WildDir = "[A-Z]:/{Documents and Settings,{WINNT,Windows}/Profiles}/*/{Local Settings,LOCALS~1}/History" + WildDir = "[A-Z]:/{Documents and Settings,{WINNT,Windows}/Profiles}/*/{Local Settings,LOCALS~1}/Temp" + WildDir = "[A-Z]:/{Documents and Settings,{WINNT,Windows}/Profiles}/*/{Local Settings,LOCALS~1}/Temporary Internet Files" + +;;; diff --git a/docs/home-page/es/pages/articles.php b/docs/home-page/es/pages/articles.php new file mode 100644 index 00000000..a6bf9811 --- /dev/null +++ b/docs/home-page/es/pages/articles.php @@ -0,0 +1,31 @@ + + + + + + + + + + + +
+ Bacula Articles on the Web +
+ + +
+

+ diff --git a/docs/home-page/es/pages/bugs.php b/docs/home-page/es/pages/bugs.php new file mode 100644 index 00000000..e9c80915 --- /dev/null +++ b/docs/home-page/es/pages/bugs.php @@ -0,0 +1,97 @@ + + + + + + + + + + + + + +
+ Bug Reporting +
+Before reporting a bug, please be sure it is a bug and +not a request for support or a feature request (see the menu +bar at the left of this page). + +

Bugs are resolved by volunteer Bacula developers (and the +community at large). If you have a high priority for your bug or +need professional help, please see the + +Professional Services page of this website. + +

Bacula now has a Mantis bug reporting system +implemented by Dan Langille and hosted on his computer. It is web based, +easy to use, and we recommend you give it a try. However, before +visiting our bugs database, please carefully read the following: + + +To view the bug reports, you can login as user anonymous and +password anonymous. The advantage of actually being subscribed +is that you will be notified by email of any serious bugs and their +resolution. + +To submit bug reports, you must create an account. You must also use a +browser running a US ASCII code page or UTF-8. Some users running Win32 +IE with Windows Eastern European code pages have experienced problems +interfacing with the system. + +

+Most Bacula problems are questions of support, so if you are not +sure if a problem you are having is a bug, see the support page +on this site for links to the email lists. However, once you have +determined that a problem is a bug, you must either submit a bug +report to the bugs database or send an email to the bacula-devel +list, otherwise it is possible that the developers will never know +about your bug and thus it will not get fixed. + +You should expect two things to be slightly different in our Bugs +handling than many other Open Source projects. First, we unfortunately +cannot give support or handle feature requests via the bugs database, +and second, we close bugs very quickly to avoid being overwhelmed. +Please don't take this personally. If you want to add a note to the bug +report after it is closed, you can do so by reopening the bug, adding a +bug note, then closing the bug report again, or for really simple +matters, you can send an email to the bacula-devel email list. If a +developer closes a bug report and after everything considered, you are +convinced there really *is* a bug and you have new information, you can +always reopen the bug report. + +

Information Needed in a Bug Report

+For us to respond to a bug report, we normally need the following +as the minimum information, which you should enter into the appropriate +fields of the bug reporting system: +
    +
  • Your operating system
    • +
  • The version of Bacula you are using
    • +
  • A clear and concise description of the problem
    • +
  • If you say "it crashes", "it doesn't work" or something + similar, you should include some output from Bacula that shows this.
    • +
+If you are having tape problems, please include: +
    +
  • The kind of tape drive you have
    • +
  • Have you run the btape "test" command?
    • + +
+The first two of these items can be fulfilled by sending us a copy of +your config.out file, which is in the main Bacula source +directory after you have done your ./configure. + +

In addition, we will sometimes need a copy of your Bacula +configuration files (especially bacula-dir.conf). If you think it is a +configuration problem, please don't hesitate to send them if +necessary.

+ Please read that little Bug-Report-HowTo as well. +
+You can submit a bug or review the list of open or closed bugs by going to: + +

+ http://bugs.bacula.org +

+
+ diff --git a/docs/home-page/es/pages/documentation.php b/docs/home-page/es/pages/documentation.php new file mode 100644 index 00000000..d93b128e --- /dev/null +++ b/docs/home-page/es/pages/documentation.php @@ -0,0 +1,85 @@ + + + + + + + + + + + + + + + + + + + + +
+ Manuals for Version 3.0.x +
+
    +
  • News about Bacula + HTML +
    • +
  • New Features in 3.0.0 + HTML +

    • +
  • Concepts and Overview Guide + PDF + /HTML +
    • +
  • Installation and Configuration Guide + PDF + /HTML +
    • +
  • Console and Operators Guide + PDF + /HTML +
    • +
  • Problem Resolution Guide + PDF + /HTML +
    • +
  • Catalog Database Guide + PDF + /HTML +
    • +
  • Utility Programs + PDF + /HTML +
    • +
  • Developers' Guide + PDF + /HTML +

    • +
  • Free Software Foundation Europe FLA + PDF + -- (Developer's Fiduciary License Agreement)
    • +
+
+ Bacula Documentation for Prior Version 2.4.x +
+
    +
  • User's Manual + PDF + /HTML + -- (Version 2.4.4 of the User's Manual)
    • +
    +
  • Tutorial + HTML + -- (start here after installing Bacula)
    • +
  • Bacula-web Guide + HTML + -- (Guide for the Bacula-web GUI application)
    • +
  • Developer's Guide + PDF + /HTML + -- (Guide for Bacula developers)
    • +
+
+

+ diff --git a/docs/home-page/es/pages/donations.php b/docs/home-page/es/pages/donations.php new file mode 100644 index 00000000..f03c6ec4 --- /dev/null +++ b/docs/home-page/es/pages/donations.php @@ -0,0 +1,64 @@ + + + + + + +
+ Donations Received +
+ + + + +
+ + 0 && $news_counter < $max_news) { + // next line + $line = array_pop($lines); + + // start of news + if(eregi("^[a-z0-9]+;;;", $line)) { + // news header + list($author,$date,$time) = explode(";;;",$line); + + // news subject + $subject = array_pop($lines); + printf('', $subject); + printf(''); + printf(''); + printf('', $date, $time, $author); + printf(''); + printf(''); + $news_counter++; + continue; + } + + // news content + printf('%s', $line); +} +?> +
%s
');
+
+                continue;
+        }
+
+        // end of news
+        if(eregi("^;;;", $line)) {
+                printf('
%s - %s, %s
+
+ diff --git a/docs/home-page/es/pages/feature-request.php b/docs/home-page/es/pages/feature-request.php new file mode 100644 index 00000000..d3cc196f --- /dev/null +++ b/docs/home-page/es/pages/feature-request.php @@ -0,0 +1,108 @@ + + + + + + + + + +
Feature Requests
+ +

Funded Development

+Now that Bacula Systems SA exists, +it is possible to sponsor funded development projects. This is a contractual +relationship where the Bacula Systems developers agree to implement +a specific project within a specific time frame. All code that is developed +by Bacula Systems developers, goes into the Bacula community source +repository, so is available for everyone to use. + +

Community Development

+If you are not interested in sponsoring a development project, you can +nevertheless submit a feature request to have a favorite feature +implemented (and even submit your own patch for it). + +

In the past, users informally submitted feature requests by email, and +we collected them, then once a version was released, we would publish the +list for users to vote on. +

+Now that Bacula has become a bigger project, this process has been +formalized a bit more. The main change is for users +to carefully think about their feature, and submit it on a feature +request form. A mostly empty form is shown below along with an +example of an actual filled in form. A text copy of the form can +be found in the projects file in the main source directory +of the Bacula release. That file also contains a list of all the +currently approved projects and their status. +

+The best time to submit a Feature Request is just after a release when +we officially request feature requests for the next version. The worst +time to submit a feature request is just prior to a new release (we are +very busy at that time). To actually submit the Feature request, +fill out the form, and submit it to both the bacula-users and +the bacula-devel email lists. It will then be openly discussed. +

+Once the Feature Request has beeen adequately discussed, Bacula Project +Manager (Kern) will either reject it, approve it, or possibly request some +modifications. If you plan to implement the feature or donate +funds to have it implemented, this is important to note, +otherwise, the feature, even if approved, may wait a long time +for someone to implement it. +

+Once the Feature request is approved, we will add it to the projects +file, which contains a list of all open Feature Requests. The projects +file is updated from time to time +

+The current (though possibly somewhat old) list of projects can also +be found on the Web site by clicking on the Projects menu item to the +left of this window. + + +

Feature Request Form

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

An Example Feature Request

+
+Item 1:   Implement a Migration job type that will move the job
+          data from one device to another.
+  Date:   28 October 2005
+  Origin: Sponsored by Riege Sofware International GmbH. Contact:
+          Daniel Holtkamp 
+  Status: Partially coded in 1.37 -- much more to do. Assigned to
+          Kern.
+
+  What:   The ability to copy, move, or archive data that is on a
+          device to another device is very important.
+
+  Why:    An ISP might want to backup to disk, but after 30 days
+          migrate the data to tape backup and delete it from
+          disk.  Bacula should be able to handle this
+          automatically.  It needs to know what was put where,
+          and when, and what to migrate -- it is a bit like
+          retention periods.  Doing so would allow space to be
+          freed up for current backups while maintaining older
+          data on tape drives.
+
+  Notes:  Migration could be triggered by:
+           Number of Jobs
+           Number of Volumes
+           Age of Jobs
+           Highwater size (keep total size)
+           Lowwater mark
+
+
+ +
+ diff --git a/docs/home-page/es/pages/fsfe.php b/docs/home-page/es/pages/fsfe.php new file mode 100644 index 00000000..dc8daa62 --- /dev/null +++ b/docs/home-page/es/pages/fsfe.php @@ -0,0 +1,65 @@ + + + + + + + + + + + + +
+ The Free Software Foundation Europe License +
+ + The Bacula project has assigned its copyright to the Free Software Foundation + Europe e.V. in a fiduciary relationship that permits the FSFE to + safeguard the Bacula software against abuse while allowing the project + to continue without the administrative burden of maintaining the + copyright paper work. +

+ If you contribute more than a few lines of code or documentation to the + Bacula project, we ask you to complete the copyright Fiduciary License + Agreement (link provided below). This is the same agreement that I (Kern) + and the other developers have signed to transfer our copyrights to the + FSFE. +

+ Filling it out is really quite simple. Please make two copies, + then put your name and mailing address on the first page and + date it. +

+ On the third page after "the author" put your name and the + other information requested. This is simply to uniquely identify + you. +

+ If you are employed and you do Bacula work while at work + or your employer has the rights to your work (often the case), + please put your employer's information here. +

+ On the fourth page, you can simply put "All code and documentation + contributed to the Bacula.org project" or if you wish to be more + specific please do so. +

+ Finally, send the two filled out, signed copies to me at:

+ Kern Sibbald
+ Cotes-de-Montmoiret 9
+ 1012 Lausanne
+ Switzerland
+

+ and I will take note that you have filled it out, then I will send + them on to the Free Software Foundation. +

+ Thanks for taking the time to complete and send the FLA in. +

+

+ 		+
    +
+
+

+ diff --git a/docs/home-page/es/pages/home.php b/docs/home-page/es/pages/home.php new file mode 100644 index 00000000..f86966e6 --- /dev/null +++ b/docs/home-page/es/pages/home.php @@ -0,0 +1,167 @@ + + + + + + + + +
+ Bacula® - The Open Source Network Backup Solution +
+ Bacula is a set of Open Source, enterprise ready, + 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. + 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. + In technical terms, it is an Open Source, enterprise + ready, network based backup program. +
+
+ According to Source Forge statistics (rank and downloads), + Bacula is by far the most popular Enterprise grade Open + Source program. +
+
+ + + + + + + + + +
Bacula.org and Bacula Systems: + How to find what you need.
+ +

+ + + + + + + + + + +
+ + + + + + + + + + +
+ + + + +
+ + + + + +
+

Bacula.org is the community home of the Bacula project, for developers and contributors. You can find the latest release of Bacula here, along with full documentation.

+
+
+
+

30 April 2009: Bacula 3.0.1 has been released.

+

+

See: News

+
+ 		+ + + + +
+ 		+ + + + + + + + + + +
+ + + + +
+ + + + + +
+

Bacula Systems is the commercial support, services and + training organization for Enterprises using Bacula. The Bacula Systems + website is found at www.baculasystems.com

+
+
+
+

3 May 2009: Bacula Enterprise Edition 1.0 will be released shortly.

+

See: Bacula Systems News + +

+
+ + + + +
+ 		+ + + + +
+
+

+ + + Most of the Bacula source code is released under the + GPL version 2 license. If you wish additional + details, please follow the License link to your left.
+ +
The Documentation link takes you to a page where you + can access all the available Bacula documentation (HTML, + PDF, and TGZ) both for the officially released version + and for the current code under development in the Source + Forge SVN. The development version of the manual typically has + more documentation, but may also document new features that are + not in the released version. The Developer's Guide + presents important information for users who want to + contribute to the Bacula project.
+ +
Bacula is released on + SourceForge at + http://sourceforge.net/projects/bacula where you can + download the software.

You may also use + the links on the left side of this page for more + information. In particular, Current Files link takes + you to the currently available downloads, and the All + Downloads link takes you to a list of all files ever + released to SourceForge. +
+ + diff --git a/docs/home-page/es/pages/license.php b/docs/home-page/es/pages/license.php new file mode 100644 index 00000000..d46c52a2 --- /dev/null +++ b/docs/home-page/es/pages/license.php @@ -0,0 +1,41 @@ + + + + + + + + +
+ Bacula Copyright, Trademark, and Licenses +
+ There are a number of different licenses that are used in + Bacula. +

GPL

+ The vast bulk of the code is released under the + + GNU General Public License version 2. + Most of this code is copyrighted: + Copyright (C) 2000-2009 Free Software Foundation Europe, e.V. +

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

LGPL

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

Public Domain

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

Trademark

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

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

+
+ + diff --git a/docs/home-page/es/pages/listlic.php b/docs/home-page/es/pages/listlic.php new file mode 100644 index 00000000..651590ad --- /dev/null +++ b/docs/home-page/es/pages/listlic.php @@ -0,0 +1,40 @@ + + + + + + + + +
+ Professional Support for Bacula +
+ The people listed are independent contractors.
+ We can't take responsibility for their actions when you hire them, + but we would appreciate feedback positive or negative.
+
+ Listing on the Bacula Professional page is offered as a + service, without any guarantees.
+
+ We reserve the right to decide with reason who is + added/removed from the web page.
+ To be listed: +
    +
  • You must have some tangible connection with and + knowledge of Bacula (i.e. developer, contributed + code/patches, Bacula user and subscribed to bacula-users, or + bacula-devel, and preferably a Web site ...).
    • +
  • You must have a web site that explicitly mentions that you support + backup.
    • +
  • You must mention Bacula on your web site.
    • +
  • You must provide a link to www.bacula.org on your web site.
    • +
+ +
+ People listed agree to update their contact information + on a regular basis.
Anyone listed with incorrect + information is subject to removal.

If you want to be + listed on the page, please get in contact with Kern + Sibbald.
+
+ diff --git a/docs/home-page/es/pages/login.php b/docs/home-page/es/pages/login.php new file mode 100644 index 00000000..31690ee3 --- /dev/null +++ b/docs/home-page/es/pages/login.php @@ -0,0 +1,24 @@ + + + + +

+ + diff --git a/docs/home-page/es/pages/logout.php b/docs/home-page/es/pages/logout.php new file mode 100644 index 00000000..63bd3f85 --- /dev/null +++ b/docs/home-page/es/pages/logout.php @@ -0,0 +1,12 @@ + + + + + + + diff --git a/docs/home-page/es/pages/maillists.php b/docs/home-page/es/pages/maillists.php new file mode 100644 index 00000000..1e36ed39 --- /dev/null +++ b/docs/home-page/es/pages/maillists.php @@ -0,0 +1,198 @@ + + + + + + + + +
+ Email Lists +
+ +Bacula has a number of email lists which are described below with +links to subscribe, unsubscribe, or modify your account. +For general information subscribing to or unsubscribing from these lists, please see +Bacula Mailing Lists at SourceForge. +

For email archives see the bottom of this page.

+ +Source Forge has rather strict email requirements in order to +try to minimize the large quantity of spam that the lists receive every day. +These are mesures that they have implemented, and over which we have no +control. +

+If you are having problems subscribing or sending email to a Bacula list, +please, read the following: +SourceForge.net: Email Problems: Spam, Bounces, Unreceived Messages, then +if you are still having problems send a support request to Source Forge. +Source Forge requires the person affected submit his/her own support request; +the Bacula project is not permitted to do so on your behalf. +

+One item they do not mention in the above referenced document is grey listing. +If you are using grey listing, you are likely to have problems with the Source +Forge email lists. The solution is to whitelist their sending IPs. You might +want to whitelist their whole zone (66.35.250.0/24) as I (Kern) have done, but +if you are more conservative, I found only two of their IPs were sending email +(66.35.250.225 and 66.35.250.206). If you grey list individual Source Forge +IP addresses, please be sure to check your logs to verify the addresses they +use for you. + +

bacula-announce

+The bacula-announce list is a read only low volume list for those +users who wish to be notified when there are important events +(important bugs, new releases, ...). We recommend that all +users subscribe to this list. Do so by following the instructions at: + +Bacula Announce List Subscription/Unsubscription/Modification. +Please do not send email directly to this list. + +

It is also possible to get email notification whenever a new package +is released on SourceForge. This is accomplished by going to +the Bacula SourceForge +Project page and clicking on the little letter or mail icon + under the heading Monitor in the +row corresponding to the package you want to monitor. +

+ +

bacula-users

+The bacula-users list is the general forum to +ask questions about Bacula or respond to questions +from other users. The volume on this list is generally +moderate, but can vary. All users are encouraged to subscribe +and to participate. +Due to the increasing volume of spam, you must be subscribed +before you can send email to this list. + +To subscribe follow the instructions at: +Bacula Users List Subscription/Unsubscription/Modification. +

+To send an email to the Bacula Users List, use the following +address: bacula-users at lists.sourceforge.net. +The previous address was modified to prevent easy use by spammers. To use it, +you must replace the at with an @ symbol. +

+ + +

bacula-users-es

+The bacula-users-es list is the general Spanish language forum to +ask questions about Bacula or respond to questions +from other users. The volume on this list is generally +moderate, but can vary. All Spanish speaking users are encouraged to subscribe +and to participate. +Due to the increasing volume of spam, you must be subscribed +before you can send email to this list. + +To subscribe follow the instructions at: +Bacula Spanish Users List Subscription/Unsubscription/Modification. +

+To send an email to the Bacula Spanish Users List, use the following +address: bacula-users-es at lists.sourceforge.net. +The previous address was modified to prevent easy use by spammers. To use it, +you must replace the at with an @ symbol. +

+ +

bacula-users-fr

+The bacula-users-fr list is the general French language forum to +ask questions about Bacula or respond to questions +from other users. The volume on this list is generally +moderate, but can vary. All French speaking users are encouraged to subscribe +and to participate. +Due to the increasing volume of spam, you must be subscribed +before you can send email to this list. + +To subscribe follow the instructions at: +Bacula French Users List Subscription/Unsubscription/Modification. +

+To send an email to the Bacula French Users List, use the following +address: bacula-users-fr at lists.sourceforge.net. +The previous address was modified to prevent easy use by spammers. To use it, +you must replace the at with an @ symbol. +

+ + +

bacula-devel

+The bacula-devel list is for those users who wish to +communicate directly with the developers. The email volume +is usually quite low (several emails per day), but can vary. +Due to the increasing volume of spam, you must be subscribed +before you can send email to this list. + +To subscribe, please follow this link: + +Bacula Developers List Subscription/Unsubscription/Modification. +

+To send an email to the Bacula Developers List, use the following +address: bacula-devel at lists.sourceforge.net. +The previous +address was modified to prevent easy use by spammers. To use it, +you must replace the at with an @ symbol. +

+ +

bacula-docs

+The bacula-docs list is the general forum to +help with the Bacula documentation. The volume on this list +low volume. +Due to the increasing volume of spam, you must be subscribed +before you can send email to this list. + +To subscribe follow the instructions at: +Bacula Docs Subscription/Unsubscription/Modification. + +

bacula-bugs

+The bacula-bugs list is a read only +list for those users who wish to be notified about new bugs +registered at: +http://bugs.bacula.org. Please do not send email directly +to this list bug file a bug report in the bugs database mentioned +above. All email to this list other than from the bugs system itself +is automatically discarded. + +To subscribe, follow follow the instructions at: + +http://lists.sourceforge.net/lists/listinfo/bacula-bugs. + +

bacula-beta

+The bacula-beta list is a read only +list for those packagers or users who wish to be notified +when a new release is in preparation or is ready. +This list is also used for discussions on running regression +scripts. +Due to the increasing volume of spam, you must be subscribed +before you can send email to this list. + +To subscribe, follow follow the instructions at: + +http://lists.sourceforge.net/lists/listinfo/bacula-beta. + + +

bacula-commits

+The bacula-commits list is a read only +list for those users who wish to be receive a diff of each +commit to the SVN. Please do not email directly to this list. +If you do commits, please subscribe your Source Forge name to this +list. Any mail from non-subscribed users is automatically discarded. + +You may subscribe by following the instructions at: + +http://lists.sourceforge.net/lists/listinfo/bacula-commits. + + +

Archives

+Most of the above email lists are archived on Source Forge, but they are +also archived on Gmane, which has better search facilities. The +Gmane archives are at: +http://news.gmane.org/search.php?match=bacula. + +

+The lists are also archived at +Mailing list ARChives (MARC). +

+
+ diff --git a/docs/home-page/es/pages/makedonation.php b/docs/home-page/es/pages/makedonation.php new file mode 100644 index 00000000..58025911 --- /dev/null +++ b/docs/home-page/es/pages/makedonation.php @@ -0,0 +1,102 @@ + + + +
+ + + + + + +
+ + + + + + + + +
+ Contributing to the Bacula Project +
+ Although one talks about Free Software, in fact, Open Software such + as Bacula was not developed without some cost. The software + may be free for the user, but it wasn't free for the developer + or developers, either in terms of time or in terms of financial + cost. + + For example, since beginning work on the Bacula project in + January 2000 until now (August 2006), I (Kern) have spent + approximately $8000 per year for computers, tape drives, + communications expenses, electricity, software licenses, and + other expenses. I am not complaining and am pleased to have + been able to afford these expenditures. In addition, have no + desire to have my past expenses reimbursed. + + Bacula is now a fairly mature product, and to ensure its long + term survival, I believe it is time that Bacula begins to + stand on its own, both financially and for the development, + which is why we began accepting donations or project support + in November 2005. +

+ There are ways you can contribute to the Bacula + project, some of which are: ideas, user support, + documentation review, translation, programming and + contributing code, testing the new releases, hosting + services, testing machines, donating needed equipment, and + financial support. + + Previously all but the last one (financial support) were possible. + It is now possible for you to contribute financial aid + the Bacula project. All funds collected will be used to help + further the Bacula project by covering out of pocket expenses + incurred by the project (no salaries). Examples are, administrative + fees, hardware, software licenses (yes Micro$oft), and possibly a + portion of travel/conference expenses. + +

+ Contributions may not be US tax deductible as Bacula is + based in Switzerland. +

+ If you are a government or for-profit corporation and cannot + make "donations", please consider paying a (non-obligatory) + binary license fee for any Bacula built binaries that you download. + By making these pre-built, pre-tested binaries available, we are + providing users who download them with an extra service, which merits + careful consideration for making a contribution or paying a + "license fee". +

+ If you are a corporation and cannot make donations and don't want + to pay a binary license fee, you can request an invoice for + Bacula Project development. Please see below for how to do this. + +

+ To make a contribution, please click on the donate button at + the top of the screen, and your transaction will be secured + and confirmed directly by PayPal. If you contribute, or have + any questions, please send me an email directly: kern at + sibbald dot com. + +

+ If you need an invoice, I can send you one, but in order to limit my + administrative work, I kindly request you to make a donation of at least + $200 before requesting an invoice. To obtain one, simply email me the exact + name to appear on the invoice as well as the mailing address, the amount + you want to contribute, and the project you are supporting (or simply + Bacula development). + +

+ The Bacula web site has a "Donations Received" page where + you can have your company name, your name, and the amount (or any + combination of those) listed. You must explicitly request to be listed. + Do so by sending an email to: kern at sibbald dot com after you have + made the payment. + +

Although there is one link to our ISP, who we thank for providing the + hosting service, we do not provide any links to other sites other than + on the Professional page. + +

+

+ diff --git a/docs/home-page/es/pages/news.php b/docs/home-page/es/pages/news.php new file mode 100644 index 00000000..3c0ac237 --- /dev/null +++ b/docs/home-page/es/pages/news.php @@ -0,0 +1,64 @@ + + + + + + +
+ News +
+ + + + +
+ + 0 && $news_counter < $max_news) { + // next line + $line = array_pop($lines); + + // start of news + if(eregi("^[a-z0-9]+;;;", $line)) { + // news header + list($author,$date,$time) = explode(";;;",$line); + + // news subject + $subject = array_pop($lines); + printf('', $subject); + printf(''); + printf(''); + printf('', $date, $time, $author); + printf(''); + printf(''); + $news_counter++; + continue; + } + + // news content + printf('%s', $line); +} +?> +
%s
');
+
+                continue;
+        }
+
+        // end of news
+        if(eregi("^;;;", $line)) {
+                printf('
%s - %s, %s
+
+ diff --git a/docs/home-page/es/pages/old-professional.txt b/docs/home-page/es/pages/old-professional.txt new file mode 100644 index 00000000..ab69dd62 --- /dev/null +++ b/docs/home-page/es/pages/old-professional.txt @@ -0,0 +1,188 @@ + + + + + + + + + + + + + + + diff --git a/docs/home-page/es/pages/presentations.php b/docs/home-page/es/pages/presentations.php new file mode 100644 index 00000000..c3d5ed4d --- /dev/null +++ b/docs/home-page/es/pages/presentations.php @@ -0,0 +1,40 @@ + + + + + + + + + + + + + + + +
+ Bacula Presentations +
+ + + + + + + +
+

+ diff --git a/docs/home-page/es/pages/presskits.php b/docs/home-page/es/pages/presskits.php new file mode 100644 index 00000000..cc1b3c3e --- /dev/null +++ b/docs/home-page/es/pages/presskits.php @@ -0,0 +1,31 @@ + + + + + + + + + + +
+ Bacula 2.2.0 Press Information +
+ +

Bacula 2.2.0 Press Information

+ + +

Press Kit in Other Languages

+ + +
+

+ diff --git a/docs/home-page/es/pages/professional.php b/docs/home-page/es/pages/professional.php new file mode 100644 index 00000000..c695e3b3 --- /dev/null +++ b/docs/home-page/es/pages/professional.php @@ -0,0 +1,423 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Professional Support for Bacula +
+ In October 2008, Bacula Systems SA, + the professional support organization specifically for Bacula + was announced. You can access the official press release + + here.

+ + I (Kern) am the chairman and CTO of Bacula Systems, so I can personally + vouch for the quality of support it provides. For those who are interested + in why there is a need for Bacula Systems along side the Bacula Open Source + community, please read my + + Letter to the community.

+ + Bacula Systems' goal is to offer subscriptions, training, and consulting + services for all levels of Bacula users by working with and through + qualified Bacula Systems Partners who are knowledgeable and close + to the customer. If you are interested in support, please see the + Bacula Systems web site as follows: +
+ + + + + + + + +
+ Bacula Systems SA + + Bacula Systems SA
+ Rue Galilée 15
+ CH-1400 Yverdon-les-Bains, Switzerland
+ +41 24 420 7890
+
+ http://www.baculasystems.com +
+
+ The following companies are Bacula Systems Partners, and as such, + we know them well and Bacula Systems stands behind them and supports + them.
+
+ All email-addresses are extended with a 'NOSPAM'-tag, please remove it before sending an email.
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ dass IT GmbH + + dass IT GmbH -- a Bacula Systems Partner
+ Händelstraße 25-29
+ 50674 Köln
+ Germany
+ Tel: +49 221 35 65 666 - 0
+ Fax: +49 221 35 65 666 - 10
+
+ dass IT provides professional services and + support using mainly open source tools. Our + focus lies on system management for a large + number of systems (servers and desktops). We + provide services and solutions mainly for Linux + based IT infrastructures. +
+ http://www.dass-it.de/ +
+ IT-Service Lehmann + + Arno Lehmann -- a Bacula Systems Partner
+ Sandstr. 6
+ 49080 Osnabrück
+ Germany
+ +49 (0) 541 5803396
+ +49 (0) 160 92008971 (mobile)
+
+ Storage, Communication, Backup and Monitoring using + Open-Source solutions. Services from + network design to system administration and + user education, with a focus on Small + Businesses looking for cost-effective solutions. +
+ http://www.its-lehmann.de +
+ MigraTech + + MigraTech -- A Bacula Systems Partner
+ Philippe Chauvat
+ 7 rue Alfred Kastler
+ Immeuble Emergence
+ 14000 Caen
+ France
+ + +33 (0) 231 75 14 91
+
+ Migratech is a company that provides services for Free Software. + We propose a broad range of services that go from consulting + to installation of complete systems: sercurity (access, contents, + antivirus, antispam), data sharing, messaging, backup, and + large WiFi networks. For Backup, MigraTech has become a specialist + in Bacula. Please visit our site (in French) for additional + information.
+
+ http://www.migratech.fr
+
+
+ Independent Contractors +
+ The following people are independent contractors. Each has worked + with Bacula, and we are pleased to list their names here as a service, but + without any guarantees.
+
+ If you wish to be listed here, please read the 'Listing license' for further details: + Listing license
+
+ All email-addresses are extended with a 'NOSPAM'-tag, please + remove it before sending an email.
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Alixen + + Gilles Polart-Donat
+ 20 rue Jean Rostand
+ 91400 Orsay, France
+ +33 01 60 19 72 31
+
+ http://www.alixen.fr +
+ Arden Group Inc + + Roger Berry
+ 5026 NE Clackamas
+ Portland, OR 97213 USA
+ +1(971)223-3987
+
+ http://www.ardengrp.com
+
+ BSDCan + + Dan Langille
+ Suite 474
+ 900 Greenbank Road
+ Ottawa, ON K2J 4P6
+ +1 215 882 0565
+
+ Dan has been a Bacula developer since early 2004 when he wrote + the PostgreSQL plugin. He is also the Bacula maintainer for + FreeBSD and has been writing and speaking about Bacula for + several years. As a consultant, his Bacula speciality is + design, installation, and configuration of new systems. He is + available for consulting on any project. + +
+ Reference available upon request. + +
+ http://www.langille.org/ +
+ Heitor Faria + + Heitor Faria
+ Consultoria, treinamento e suporte
+
+ Telephone +55 71 9983-3833
+
+
+ Consultancy, training and support. +
+ http://bacula.wordpress.com +
+ KDB Konsult AB + + Mats Vilhelmsson
+ Tel: +46 708 901042
+
+ Backup hosting - Internet backups, Bacula training, installations and support.
+
+ http://www.kdb.se
+
+ L. Strappazon + + Ludovic Strappazon
+ Strasbourg, France
+ +33 685 27 93 39
+
+ I offer engineering services and training around storage and Backup. + Planning and scaling of your hardware installation, Bacula implementation. +
+ MATRIX-Computer + + MATRIX-Computer GmbH
+ Dachauer Str. 44
+ 80335 München
+ Germany
+ + +49-89-922 996 80
+
+ We are a team of software developers with experience in C++, Windows, PHP, + Linux and more. We have done lots of the Think Tools software.
+
+ http://www.matrix-computer.com
+
+ NETWAYS GmbH + + NETWAYS GmbH
+ Deutschherrnstrasse 47a
+ 90429 Nürnberg
+ Germany
+
+ Telephone +49 911 92885-0
+ Fax +49 911 92885-77
+
+
+ We support our customers managing complex and + heterogeneous networks. Our services and + solutions, based on Open Source software, help + you run your servers and applications + failure-free. Special focus on Nagios, Bacula, + Request Tracker, and cluster solutions.
+
+ http://www.netways.de
+
+ müller it gmbh + + müller it gmbh
+ Hagenholzstrasse 76
+ 8050 Zürich + Schweiz +
+ Telephone +41 (0)43 536 49 75
+ Skype mueller.it.gmbh +
+
+ IT Lösungen & Services für KMU's. +
+ http://www.muellerit.ch
+
+ Sine Nomine Associates + + Services Sales Dept.
+ US:
+   43596 Blacksmith Square
+   Ashburn, VA 20147 USA
+   +1 703 723 6673
+
+ EMEA:
+   Na Dvorcich 17/Na Vrasni 18
+   CZ - Praha 4, 14000
+   Czech Republic
+
+ Design and implementation of system management tools and infrastructure,
+ from small systems to enterprise-wide implementations on global scale.
+ Special focus on Bacula for enterprise-class systems and mainframe.
+
+ http://www.sinenomine.net
+
+
+ diff --git a/docs/home-page/es/pages/projects.php b/docs/home-page/es/pages/projects.php new file mode 100644 index 00000000..dd818cdc --- /dev/null +++ b/docs/home-page/es/pages/projects.php @@ -0,0 +1,1292 @@ + + + + + + +
+ +
+                
+                
+                
+Projects:
+                     Bacula Projects Roadmap 
+                    Status updated 7 July 2007
+                   After re-ordering in vote priority
+
+Items Completed:
+Item:   2   Implement a Bacula GUI/management tool.
+Item:  18   Quick release of FD-SD connection after backup.
+Item:  23   Implement from-client and to-client on restore command line.
+Item:  25   Implement huge exclude list support using dlist   
+Item:  41   Enable to relocate files and directories when restoring
+Item:  42   Batch attribute inserts (ten times faster)
+Item:  43   More concurrency in SD using micro-locking
+Item:  44   Performance enhancements (POSIX/Win32 OS file access hints).
+Item:  40   Include JobID in spool file name
+
+Summary:
+Item:   1   Accurate restoration of renamed/deleted files
+Item:   2*  Implement a Bacula GUI/management tool.
+Item:   3   Allow FD to initiate a backup
+Item:   4   Merge multiple backups (Synthetic Backup or Consolidation).
+Item:   5   Deletion of Disk-Based Bacula Volumes
+Item:   6   Implement Base jobs.
+Item:   7   Implement creation and maintenance of copy pools
+Item:   8   Directive/mode to backup only file changes, not entire file
+Item:   9   Implement a server-side compression feature
+Item:  10   Improve Bacula's tape and drive usage and cleaning management.
+Item:  11   Allow skipping execution of Jobs
+Item:  12   Add a scheduling syntax that permits weekly rotations
+Item:  13   Archival (removal) of User Files to Tape
+Item:  14   Cause daemons to use a specific IP address to source communications
+Item:  15   Multiple threads in file daemon for the same job
+Item:  16   Add Plug-ins to the FileSet Include statements.
+Item:  17   Restore only file attributes (permissions, ACL, owner, group...)
+Item:  18*  Quick release of FD-SD connection after backup.
+Item:  19   Implement a Python interface to the Bacula catalog.
+Item:  20   Archive data
+Item:  21   Split documentation
+Item:  22   Implement support for stacking arbitrary stream filters, sinks.
+Item:  23*  Implement from-client and to-client on restore command line.
+Item:  24   Add an override in Schedule for Pools based on backup types.
+Item:  25*  Implement huge exclude list support using hashing.
+Item:  26   Implement more Python events in Bacula.
+Item:  27   Incorporation of XACML2/SAML2 parsing
+Item:  28   Filesystem watch triggered backup.
+Item:  29   Allow inclusion/exclusion of files in a fileset by creation/mod times
+Item:  30   Tray monitor window cleanups
+Item:  31   Implement multiple numeric backup levels as supported by dump
+Item:  32   Automatic promotion of backup levels
+Item:  33   Clustered file-daemons
+Item:  34   Commercial database support
+Item:  35   Automatic disabling of devices
+Item:  36   An option to operate on all pools with update vol parameters
+Item:  37   Add an item to the restore option where you can select a pool
+Item:  38   Include timestamp of job launch in "stat clients" output
+Item:  39   Message mailing based on backup types
+Item:  40*  Include JobID in spool file name
+Item:  41*  Enable to relocate files and directories when restoring
+Item:  42*  Batch attribute inserts (ten times faster)
+Item:  43*  More concurrency in SD using micro-locking
+Item:  44*  Performance enhancements (POSIX/Win32 OS file access hints).
+
+Item  1:  Accurate restoration of renamed/deleted files
+  Date:   28 November 2005
+  Origin: Martin Simmons (martin at lispworks dot com)
+  Status: Robert Nelson will implement this
+
+  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:  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  2:  Implement a Bacula GUI/management tool.
+  Origin: Kern
+  Date:   28 October 2005
+  Status: In progress
+
+  What:   Implement a Bacula console, and management tools
+          probably using Qt3 and C++.
+
+  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:   There is a partial Python-GTK implementation
+          Lucas Di Pentima  but
+          it is no longer being developed.
+
+Item  3:  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  4:  Merge multiple backups (Synthetic Backup or Consolidation).
+  Origin: Marc Cousin and Eric Bollengier 
+  Date:   15 November 2005
+  Status: Waiting implementation. Depends on first implementing 
+          project Item 2 (Migration) which is now done.
+
+  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  5:  Deletion of Disk-Based Bacula Volumes
+  Date:   Nov 25, 2005
+  Origin: Ross Boylan  (edited
+          by Kern)
+  Status:         
+
+   What:  Provide a way for Bacula to automatically remove Volumes
+          from the filesystem, or optionally to truncate them.
+          Obviously, the Volume must be pruned prior removal.
+
+  Why:    This would allow users more control over their Volumes and
+          prevent disk based volumes from consuming too much space.
+
+  Notes:  The following two directives might do the trick:
+
+          Volume Data Retention =
+ +
+ + diff --git a/docs/home-page/es/pages/requirements.php b/docs/home-page/es/pages/requirements.php new file mode 100644 index 00000000..5bd53320 --- /dev/null +++ b/docs/home-page/es/pages/requirements.php @@ -0,0 +1,57 @@ + + + + + + + + +
+ System Requirements +
+ +
    +
  • Bacula has been compiled and run on Linux, FreeBSD, + and Solaris systems.
    • +
  • It requires GNU C++ version 2.95 or higher to compile. You can try + with other compilers and older versions, but you are on your + own. We have successfully compiled and used Bacula on + RH8.0/RH9/RHEL 3.0 with GCC 3.2. Note, in general GNU C++ is a + separate package (e.g. RPM) from GNU C, so you need them both + loaded. On RedHat systems, the C++ compiler is part of the + gcc-c++ rpm package.
    • +
  • There are certain third party packages that Bacula needs. + Except for MySQL and PostgreSQL, they can all be found in the + depkgs and depkgs1 releases.
    • +
  • If you want to build the Win32 binaries, you should know + that they are cross-compiled on a Linux machine. For + more information, please see the src/win32/README.mingw32 + file in the source distribution. + Although we document it, we do not support building the + Win32 binaries. Only the Win32 File daemon is officially + supported, though the other daemons are available in the + binary release.
    • +
  • Bacula requires a good implementation of pthreads to work. + This is not the case on some of the BSD systems.
    • +
  • The source code has been written with portability in mind and is + mostly POSIX compatible. Thus porting to any POSIX compatible + operating system should be relatively easy.
    • +
  • The GNOME Console program is developed and tested under GNOME 2.x. +
    • +
  • The wxWidgets Console program is developed and tested with the + latest stable version of wxWidgets (2.6). It + works fine with the Windows and GTK+-2.x version of wxWidgets, + and should also works on other platforms supported by + wxWidgets.
    • +
  • The Tray Monitor program is developed for GTK+-2.x. It needs + Gnome >=2.2, KDE >=3.1 or any window manager supporting the + + FreeDesktop system tray standard.
    • +
  • If you want to enable command line editing and history, you will + need to have /usr/include/termcap.h and either the termcap or the + ncurses library loaded (libtermcap-devel or ncurses-devel).
    • +
+ +
+ diff --git a/docs/home-page/es/pages/screenshot.php b/docs/home-page/es/pages/screenshot.php new file mode 100644 index 00000000..68d4418d --- /dev/null +++ b/docs/home-page/es/pages/screenshot.php @@ -0,0 +1,49 @@ + + + + + + + + +
+ Bacula Screenshots +
+ + Even though Bacula himself is mostly a console based program, + many GUIs are available on a top of it. + +
    +
  • BAT (Bacula Admin Tool)
    + + + + + + + + + + + + +
    + +
  • Bweb (Bacula Web interface)
    + + + + + + + + + + + +
    +
+ + +
+ diff --git a/docs/home-page/es/pages/support.php b/docs/home-page/es/pages/support.php new file mode 100644 index 00000000..8cb29254 --- /dev/null +++ b/docs/home-page/es/pages/support.php @@ -0,0 +1,131 @@ + + + + + + + + + + + + +
Support for Bacula
+ + +

Professional Support

+ If you need professional support, please see the + + professional support page of this website.
+ +

Community Support

+ Please keep in mind that no one is getting paid for this. + Nevertheless, our desire is to see as many people using + Bacula as possible. A number of very knowledgeable volunteers are + willing to provide a reasonable level of email support. + +

Before asking for help, please read the Information Needed + listed below, and it could be useful to check against the + email archive as often solution to your problem has been discussed + or a patch has been released. Please see: + + http://news.gmane.org/search.php?match=bacula. + +

Also, if you are using Bacula in production, we highly recommend + subscribing to the bugs database at: + http://bugs.bacula.org to keep informed of problems and + patches. You might also want to look for professional support at: + + http://www.bacula.org/es/?page=professional.
+ + +

Please do not submit support requests to the bugs database. + For more information on bugs, please see the Bugs page on this + web site. + +

For community support, send an email to + bacula-users at lists.sourceforge.net, and if you are + specific enough, some kind Bacula user will help you. Please + note that if you don't at least specify what version of Bacula + and what platform you are using, it will not be easy to get a + valid answer. The email address noted above + was modified to prevent easy use by spammers. + To use it, you must replace the at with an @ symbol. Due + to the increasing volumes of spam on the list, you must + be subscribed to it to be able to send and email to it. The + link to your left entitled Email Lists provides links + to where you can subscribe to each of the Bacula email lists. + + The users constantly monitor this list and will generally provide + support. Please see Information Needed below for what to + include in your support request. If you don't supply the necessary + information, it will take longer to respond to your request, and + users may be afraid to try to respond, + if your request is too complicated or not well formulated. + + +

I (Kern) get a number of "off-list" emails sent + directly to me. Unfortunately, I am no longer able to provide + direct user support. However, I do read all the email sent and + occasionally provide a tip or two. If you do send email to me, + please always copy the appropriate list, if you + do not copy the list, I may not answer you, or I will answer by copying + the list. If you really have something confidential, + please clearly indicate it.

+ +

Please do not send general support requests to the bacula-devel list. + You may send a preliminary bug question, a development question, + or minor enhancement request to the bacula-devel list. If + you do not provide the information + requested below, particularly the Bacula version, it is very + frustrating for us, because it is quite often the case that your problem is + version dependent, and possibly already fixed. In such case, we will note + the problem, but you will be unlikely to get a response, especially if we + are busy, because it forces us to first ask you what version you are using + (or other information), then deal with your response, thus doubling the + time for us. If we do ask you for information, please include all + the previous correspondence in each email, to avoid us having to search + the archives to find what you previously wrote. In short, if you want a + response, please see "Information Needed" below. + +

If you are looking for live-support you might check out our irc-channel + in the Freenode net, called #bacula. + +

Information Needed

+For us to respond to a bug report, we normally need the following +as the minimum information, which you can enter into the appropriate +fields of the bug reporting system: +
    +
  • Your operating system
    • +
  • The version of Bacula you are using
    • +
  • A clear and concise description of the problem
    • +
  • If you say "it crashes", "it doesn't work" or something + similar, you should include some output from Bacula that shows this.
    • +
  • If we respond to your email, and you answer, possibly supplying more + information, please be sure to include the full text of previous + emails so that we have all the information in one place.
    • +
+If you are having tape problems, please include: +
    +
  • The kind of tape drive you have
    • +
  • Have you run the btape "test" command?
    • +
+ +If you are having database problems, please include: +
    +
  • The database you are using: MySQL, PostgreSQL, SQLite, SQLite3
    • +
  • The version of the database you are using
    • +
+ +The first two of these items can be fulfilled by sending +us a copy of your config.out file, which is in the +main Bacula source directory after you have done +your ./configure. +

In addition, we will sometimes need a copy of your Bacula +configuration files (especially bacula-dir.conf). If you +think it is a configuration problem, please don't hesitate +to send them if necessary.

+ Please read that little Bug-Report-HowTo as well. +
+ diff --git a/docs/home-page/es/pages/testimonial.php b/docs/home-page/es/pages/testimonial.php new file mode 100644 index 00000000..56649743 --- /dev/null +++ b/docs/home-page/es/pages/testimonial.php @@ -0,0 +1,1208 @@ + "SELECT ONE", + '100' => "Church / Religious Organization", + '101' => "Corporation", + '102' => "Educational Institution", + '103' => "Government", + '104' => "Military", + '105' => "Non-Profit Organization", + '107' => "Small Business", + '106' => "Other" +); + +$version_lst = array( + 'empty' => "SELECT ONE", + '200' => "1.36.x", + '201' => "1.38.x", + '202' => "2.0.x", + '203' => "2.2.x", + '206' => "2.4.x", + '204' => "SVN version" +); + +$catalog_lst = array( + 'empty' => "SELECT ONE", + '300' => "MySQL", + '301' => "PostgreSQL", + '303' => "SqLite" +); + +$org_industry_lst = array( + 'empty' => 'SELECT ONE', '400' => 'Aerospace / Aeronautical', + '401' => 'Agriculture / Farming', '402' => 'Architecture / Design', + '403' => 'Arts', '404' => 'ASP', + '405' => 'Banking', + '406' => 'Church / Religious Organization', '407' => 'Coaching', + '408' => 'Construction', '409' => 'Consulting (General)', + '410' => 'Consulting (Information Technology)','411' => 'Defense Industry', + '412' => 'Education / Training', '413' => 'Energy Industry', + '414' => 'Engineering', '415' => 'Entertainment (Film)', + '416' => 'Entertainment (Music)', '417' => 'Entertainment (Other)', + '418' => 'Event Management / Conferences', '419' => 'Finance / Banking / Accounting', + '420' => 'Food Service Industry', '421' => 'Government', + '422' => 'Healthcare / Medicine', '423' => 'Higher Education', + '424' => 'Insurance', '425' => 'Internet Service Provider', + '426' => 'K-12 Education', '427' => 'Law Enforcement / Emergency Management', + '428' => 'Legal', '429' => 'Manufacturing (Computer Equipment)', + '430' => 'Manufacturing (General)', '431' => 'Media (Publishing, Broadcasting, etc)', + '432' => 'Military', '433' => 'Mining', + '434' => 'Natural Resources / Environment', '435' => 'Pharmaceuticals', + '436' => 'Public Relations / Advertising', '437' => 'Real Estate', + '438' => 'Retail / Consumer Goods', '439' => 'Sales / Marketing', + '440' => 'Scientific Research', '441' => 'Sports / Recreation', + '442' => 'Technical College / Trade School', '443' => 'Telecommunications', + '444' => 'Transportation Industry (Air)', '445' => 'Transportation Industry (General)', + '446' => 'Transportation Industry (Marine)', '447' => 'Travel / Tourism / Lodging', + '448' => 'Travel Industry', '449' => 'Utilities / Public Works', + '450' => 'Other' +); + +$os_lst = array( + 'empty' => 'SELECT ONE', '500' => 'AIX', + '501' => 'FreeBSD', '502' => 'HP-UX', + '503' => 'Linux (Debian)', '504' => 'Linux (Fedora)', + '505' => 'Linux (Gentoo)', '506' => 'Linux (Mandriva)', + '507' => 'Linux (Other)', '508' => 'Linux (RedHat)', + '509' => 'Linux (Slackware)', '510' => 'Linux (Suse)', + '511' => 'Mac OS X', '512' => 'NetBSD', + '513' => 'OpenBSD', '514' => 'Other', + '515' => 'Solaris', '516' => 'Windows 2000', + '517' => 'Windows 2003', '518' => 'Windows XP', + '519' => 'Windows Vista' +); + +$country_lst = array( + 'empty' => 'SELECT ONE', '1001' => 'Afghanistan', + '1002' => 'Albania', '1003' => 'Algeria', + '1004' => 'American Samoa', '1005' => 'Andorra', + '1006' => 'Angola', '1007' => 'Anguilla', + '1008' => 'Antarctica', '1009' => 'Antigua and Barbuda', + '1010' => 'Argentina', '1011' => 'Armenia', + '1012' => 'Aruba', '1013' => 'Australia', + '1014' => 'Austria', '1015' => 'Azerbaijan', + '1016' => 'Bahamas', '1017' => 'Bahrain', + '1018' => 'Bangladesh', '1019' => 'Barbados', + '1020' => 'Belarus', '1021' => 'Belgium', + '1022' => 'Belize', '1023' => 'Benin', + '1024' => 'Bermuda', '1025' => 'Bhutan', + '1026' => 'Bolivia', '1027' => 'Bosnia and Herzegovina', + '1028' => 'Botswana', '1029' => 'Bouvet Island', + '1030' => 'Brazil', '1031' => 'Brunei Darussalam', + '1032' => 'Bulgaria', '1033' => 'Burkina Faso', + '1034' => 'Burundi', '1035' => 'Cambodia', + '1036' => 'Cameroon', '1037' => 'Canada', + '1038' => 'Cape Verde', '1039' => 'Cayman Islands', + '1040' => 'Central African Republic','1041' => 'Chad', + '1042' => 'Chile', '1043' => 'China', + '1044' => 'Christmas Island', '1045' => 'Colombia', + '1046' => 'Comoros', '1047' => 'Congo', + '1048' => 'Cook Islands', '1049' => 'Costa Rica', + '1054' => "Ivory Coast", '1050' => 'Croatia', + '1051' => 'Cuba', '1052' => 'Cyprus', + '1053' => 'Czech Republic', '1055' => 'Denmark', + '1056' => 'Djibouti', '1057' => 'Dominica', + '1058' => 'Dominican Republic', '1059' => 'East Timor', + '1060' => 'Ecuador', '1061' => 'Egypt', + '1062' => 'El Salvador', '1063' => 'Equatorial Guinea', + '1064' => 'Eritrea', '1065' => 'Estonia', + '1066' => 'Ethiopia', '1067' => 'Falkland Islands', + '1068' => 'Faroe Islands', '1069' => 'Fiji', + '1070' => 'Finland', '1071' => 'France', + '1072' => 'French Guiana', '1073' => 'French Polynesia', + '1074' => 'Gabon', '1075' => 'Gambia', + '1076' => 'Georgia', '1077' => 'Germany', + '1078' => 'Ghana', '1079' => 'Gibraltar', + '1080' => 'Greece', '1081' => 'Greenland', + '1082' => 'Grenada', '1083' => 'Guadeloupe', + '1084' => 'Guam', '1085' => 'Guatemala', + '1086' => 'Guinea', '1087' => 'Guinea-Bissau', + '1088' => 'Guyana', '1089' => 'Haiti', + '1090' => 'Honduras', '1091' => 'Hong Kong', + '1092' => 'Hungary', '1093' => 'Iceland', + '1094' => 'India', '1095' => 'Indonesia', + '1096' => 'Iran', '1097' => 'Iraq', + '1098' => 'Ireland', '1099' => 'Israel', + '1100' => 'Italy', '1101' => 'Jamaica', + '1102' => 'Japan', '1103' => 'Jordan', + '1104' => 'Kazakstan', '1105' => 'Kenya', + '1106' => 'Kiribati', '1107' => 'Kuwait', + '1108' => 'Kyrgystan', '1109' => 'Lao', + '1110' => 'Latvia', '1111' => 'Lebanon', + '1112' => 'Lesotho', '1113' => 'Liberia', + '1232' => 'Libya', '1114' => 'Liechtenstein', + '1115' => 'Lithuania', '1116' => 'Luxembourg', + '1117' => 'Macau', '1118' => 'Macedonia (FYR)', + '1119' => 'Madagascar', '1120' => 'Malawi', + '1121' => 'Malaysia', '1122' => 'Maldives', + '1123' => 'Mali', '1124' => 'Malta', + '1125' => 'Marshall Islands', '1126' => 'Martinique', + '1127' => 'Mauritania', '1128' => 'Mauritius', + '1129' => 'Mayotte', '1130' => 'Mexico', + '1131' => 'Micronesia', '1132' => 'Moldova', + '1133' => 'Monaco', '1134' => 'Mongolia', + '1135' => 'Montserrat', '1136' => 'Morocco', + '1137' => 'Mozambique', '1138' => 'Myanmar', + '1139' => 'Namibia', '1140' => 'Nauru', + '1141' => 'Nepal', '1142' => 'Netherlands', + '1143' => 'Netherlands Antilles', '1144' => 'Neutral Zone', + '1145' => 'New Caledonia', '1146' => 'New Zealand', + '1147' => 'Nicaragua', '1148' => 'Niger', + '1149' => 'Nigeria', '1150' => 'Niue', + '1151' => 'Norfolk Island', '1152' => 'North Korea', + '1153' => 'Northern Mariana Islands', '1154' => 'Norway', + '1155' => 'Oman', '1156' => 'Pakistan', + '1157' => 'Palau', '1158' => 'Panama', + '1159' => 'Papua New Guinea', '1160' => 'Paraguay', + '1161' => 'Peru', '1162' => 'Philippines', + '1163' => 'Pitcairn', '1164' => 'Poland', + '1165' => 'Portugal', '1166' => 'Puerto Rico', + '1167' => 'Qatar', '1168' => 'Reunion', + '1169' => 'Romania', '1170' => 'Russian Federation', + '1171' => 'Rwanda', '1172' => 'Saint Helena', + '1173' => 'Saint Kitts and Nevis', '1174' => 'Saint Lucia', + '1175' => 'Saint Pierre and Miquelon','1231' => 'Saint Vincent and the Grenadines', + '1176' => 'Samoa', '1177' => 'San Marino', + '1178' => 'Sao Tome and Principe', '1179' => 'Saudi Arabia', + '1180' => 'Senegal', '1227' => 'Serbia and Montenegro', + '1181' => 'Seychelles', '1182' => 'Sierra Leone', + '1183' => 'Singapore', '1184' => 'Slovakia', + '1185' => 'Slovenia', '1186' => 'Solomon Islands', + '1187' => 'Somalia', '1188' => 'South Africa', + '1189' => 'South Georgia', '1190' => 'South Korea', + '1191' => 'Spain', '1192' => 'Sri Lanka', + '1193' => 'Sudan', '1194' => 'Suriname', + '1195' => 'Swaziland', '1196' => 'Sweden', + '1197' => 'Switzerland', '1198' => 'Syria', + '1199' => 'Taiwan', '1200' => 'Tajikistan', + '1201' => 'Tanzania', '1202' => 'Thailand', + '1203' => 'Togo', '1204' => 'Tokelau', + '1205' => 'Tonga', '1206' => 'Trinidad and Tobago', + '1207' => 'Tunisia', '1208' => 'Turkey', + '1209' => 'Turkmenistan', '1210' => 'Turks and Caicos Islands', + '1211' => 'Tuvalu', '1212' => 'Uganda', + '1213' => 'Ukraine', '1214' => 'United Arab Emirates', + '1215' => 'United Kingdom', '1216' => 'United States of America', + '1217' => 'Uruguay', '1218' => 'Uzbekistan', + '1219' => 'Vanuatu', '1233' => 'Vatican City', + '1220' => 'Venezuela', '1221' => 'Vietnam', + '1222' => 'Virgin Islands (British)', '1223' => 'Virgin Islands (U.S.)', + '1224' => 'Wallis and Futuna Islands','1225' => 'Western Sahara', + '1226' => 'Yemen', '1228' => 'Zaire', + '1229' => 'Zambia', '1230' => 'Zimbabwe' +); + +admin_link(); + +if ($_REQUEST['action'] == 'Add' or $_REQUEST['action'] == 'Modify') +{ + +?> + + + + + + + + + + + + + + + + + + + + + + +
+ Testimonial +
+ +Want to let others know you're using Bacula? Submit a user profile! Your +submission will be reviewed before being made publicly available. We reserve +the right to edit your submission for spelling, grammar, etc. You will receive +an email when your profile has been approved for public viewing. Note that +while your contact name and email address are required (to verify +information if necessary), you can choose to have them not be published along +with your profile information. +

+Fields marked with a * are required. Read the privacy notice below for +information about how this data will be used. + +
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+*Contact Name:Publish Contact Name?
*Email Address:Publish Email Address? +
Job Description/Title: +

*Organization Name: + +Publish Org Name? +
*Organization Type: + +
*Organization Industry/Function: + +
+*Approx. Organization Size (# of Users): +Publish Org Size?
Website URL: +Publish Website? +
Organization Logo : + +max width 150px. png, gif or jpeg only
*Country: + +

*Bacula version: + +
*Director OS: + +
*Catalog DB: + +
*Redundant/Failover Backup Setup?
*Number of Director (Running bacula-dir): +
*Number of Clients (Running bacula-fd): +
+*Number of Storage Daemons (Running bacula-sd): +
*Total # of GB saved every month:
*Number # of Files:
Need professional support: +

Applicable Hardware and Network Information: + +
General Comments: +
+"; + echo ""; + echo "
"; + echo "
"; + +} else { + echo ""; +} +?> + +
+
+ +
+

Getting backup information

+To get Total # of GB saved every month, you can run this query on you catalog (just adapt the starttime condition and round the result) +
+bacula@yourdir:~$ bconsole
+*sql
+SELECT sum(JobBytes)/1073741824 FROM Job WHERE StartTime > '2008-02-07' AND Type = 'B'
+
+ +To know how many files are in your catalog, you can run this: +
+bacula@yourdir:~$ bconsole
+*sql
+SELECT sum(JobFiles) FROM Job WHERE Type = 'B'
+
+
+

Privacy Notice

+ +The following information is required, but you may choose to not have it +published for public viewing if you wish: contact name, email address, +organization name. We may use this information to verify the data you submit if +we find the need. +
+\n"; + $attribs = array('contact_name','email_address', 'org_name','title','website', + 'month_gb','number_files', 'number_dir','number_fd','number_sd', + 'org_size','id'); + foreach ($attribs as $arr) { + form_set_value($formul, $arr); + } + + $attribs = array('publish_contact','publish_email', 'publish_orgname', 'orgtype_id', + 'orgindustry_id', 'publish_orgsize','publish_website', 'bacula_version', + 'country_id','ostype_id', 'redundant_setup', 'catalog_id', 'support'); + foreach ($attribs as $arr) { + form_set_selection($formul, $arr); + } + + $attribs = array('comments', 'hardware_comments'); + foreach ($attribs as $arr) { + form_set_text($formul, $arr); + } + + + echo "\n"; + +} elseif ($_REQUEST['action'] == 'Review Profile Submission') { + + $form = get_formul(); + if (!$form) { + echo "Sorry, something is missing, I can't accept your submission"; + } else { + $token = uniqid(md5(rand()), true); + $filename = "$dat_dir/profile.$token"; + + $form['filename'] = $filename; + $form['id'] = $token; + $form['visible']=0; + save_formul($form); + + send_email($form['id'], $form['contact_name'], $form['email_address']); + echo "You can modify your profile here (keep this link as bookmark)

"; + print_formul($form); + } + +} elseif ($_REQUEST['action'] == 'View') { + + $file = get_file_from_id(); + + if ($file) { + print_formul_file($filename,true); + } + +} elseif ($_REQUEST['action'] == 'Delete') { + + $filename = get_file_from_id(); + + if (!$filename) { + return (0); + } + + $form = load_formul($filename); + + if ($form['org_logo'] && file_exists($form['org_logo'])) { + rename($upload_dir + $form['org_logo'], 'removed.' + $upload_dir + $form['org_logo']); + } + if (file_exists($filename)) { + rename($filename, "$filename-removed"); + echo "Profile deleted"; + } + +} elseif ($_REQUEST['action'] == 'Accept' && is_admin()) { + + $filename = get_file_from_id(); + + if (!$filename) { + return (0); + } + + $form = load_formul($filename); + + $hide = $_REQUEST['hide']; + + if ($hide) { + $form['visible']=0; + } else { + $form['visible']=1; + } + save_formul($form); + echo $form['id'] . " is now " . ($hide?"un":"") . "visible"; + print_formul($form); + +} elseif ($_REQUEST['action'] == 'Save') { + + $filename = get_file_from_id(); + + if (!$filename) { + return (0); + } + + $form = get_formul(); + + $form['filename'] = $filename; + $form['id'] = $_REQUEST['id']; // id is clean +// $form['visible'] = false; + + if (!$form['org_logo']) { + $form_old = load_formul($filename); + $form['org_logo'] = $form_old['org_logo']; + } + + save_formul($form); + + echo "Your profile has been modified.
"; + print_formul($form); + +} elseif ($_REQUEST['action'] == 'Admin' && is_admin()) { + + view_all(); + +} elseif (!$_REQUEST['action'] || $_REQUEST['action'] == 'ViewAll') { + + echo "Add your testimonial

"; + view_all(); + +} elseif ($_REQUEST['action'] == 'AdminExport' && is_admin()) { + + $file = get_file_from_id(); + if (!$file) { + return 0; + } + $form = load_formul($file); + if ($form) { + export_form($form); + } +} elseif ($_REQUEST['action'] == 'sql') { + print "

";
+   dump_sql();
+   print "
"; +} + +function view_all() +{ + global $dat_dir; + global $password; + + $limit = $_REQUEST['limit']; + $offset = $_REQUEST['offset']; + + $limit = is_numeric($limit)?$limit:5; + $offset = is_numeric($offset)?$offset:0; + $max = $offset + $limit; + + $admin = is_admin(); + if ($limit > 20) { $limit = 20 ;} + + if ($handle = opendir($dat_dir)) { + /* Ceci est la facon correcte de traverser un dossier. */ + $i = 0 ; + while (false !== ($file = readdir($handle))) { + if (preg_match("/^profile.[a-z0-9\.]+$/", $file)) { + if (($i >= $offset) && ($i < $max)) { + $i += print_formul_file("$dat_dir/$file",$admin); + } else { + $i++; + } + if ($i > $max) { + break; + } + } + } + closedir($handle); + } + if ($offset > 0) { + $offset = $offset - $limit; + if ($offset < 0) { + $offset=0; + } + echo "Prev "; + } + if ($i >= $max) { + $offset = $offset + $limit; + echo " Next
"; + } +} + +function export_form($formul) +{ + global $country_lst, $org_type_lst, $org_industry_lst, $os_lst, $catalog_lst, $version_lst; + + $attribs = array('contact_name','email_address', 'org_name','title','website', + 'hardware_comments','comments', + 'publish_contact','publish_email', 'publish_orgname','org_size','redundant_setup', + 'date','visible', 'support','number_dir', + 'number_fd','number_sd','month_gb','number_files','publish_orgsize','publish_website'); + print "
\n";
+        foreach ($attribs as $arr) {
+                print "$arr = " . $formul[$arr] . "\n";
+        }
+
+        print "orgtype = " . $org_type_lst[$formul['orgtype_id']] . "\n";
+        print "orgindustry = " . $org_industry_lst[$formul['orgindustry_id']] . "\n";
+        print "bacula_version = " . $version_lst[$formul['bacula_version']] . "\n";
+        print "country = " . $country_lst[$formul['country_id']] . "\n";
+        print "ostype = " . $os_lst[$formul['ostype_id']] . "\n";
+        print "catalog = " . $catalog_lst[$formul['catalog_id']] . "\n";
+
+        print "
\n";
+}
+
+function get_file_from_id()
+{
+    global $dat_dir;
+    $id = $_REQUEST['id'];
+
+    if (!ereg('^[a-zA-Z0-9\.]+$',$id)) {
+         return(0) ;
+    }
+
+    $filename="$dat_dir/profile.$id";
+
+    if (!file_exists($filename)) {
+         echo "Can't verify your id";
+         return (0);
+    }       
+
+    return $filename;
+}
+
+function send_email($id, $name, $email)
+{
+        // Your email address
+//        $from = 'kern@sibbald.com';
+        $from = 'eric@eb.homelinux.org';
+
+        // The subject
+        $subject = "[BACULA] New testimonial";
+
+        // The message
+        $message = "Hello, 
+You can modify your new testimonial at http://www.bacula.org/es/?page=testimonial&action=Modify&id=$id
+
+Best regards.
+";
+
+        mail($email, $subject, $message, "From: Bacula WebMaster <$from>");
+
+        $message = "Hello, 
+You can review this testimonial at http://www.bacula.org/es/?page=testimonial&action=Modify&id=$id
+
+Best regards.
+";
+
+        
+        mail('testimonial@rt.baculasystems.com', $subject, $message, "From: $name <$email>");
+
+        echo "The email has been sent for approval.
";
+}
+
+function save_formul($form)
+{
+        $fp = fopen($form['filename'], 'w'); 
+        fwrite($fp, serialize($form));
+        fclose($fp);
+}
+
+function get_formul()
+{
+        global $upload_dir;
+        global $dat_dir;
+        $formul = array();
+        $attribs = array('contact_name','email_address', 'org_name');
+        foreach ($attribs as $arr) {
+                if (!$_REQUEST[$arr]) {
+                        echo "Can't get $arr
";
+                        return '';
+                }
+                $formul[$arr] = preg_replace('/[^a-zA-Z0-9!\.?\:\/,;_()@\n -]/', " ", $_REQUEST[$arr]);
+        }
+
+        $attribs = array('title','website','hardware_comments','comments')              ;
+        foreach ($attribs as $arr) {
+                $formul[$arr] = preg_replace('/[^a-zA-Z0-9!\.?\:\/,;_()@\n -]/', " ", $_REQUEST[$arr]);
+        }
+
+        $attribs = array('publish_contact','publish_email', 'publish_orgname', 'orgtype_id', 
+                         'orgindustry_id','org_size', 'publish_orgsize','publish_website', 'bacula_version',
+                         'country_id','ostype_id', 'redundant_setup','number_fd','number_sd','support',
+                         'month_gb','number_files','catalog_id','number_dir');
+        foreach ($attribs as $arr) {
+                $tmp = $_REQUEST[$arr];
+                $tmp = preg_replace("/[,\.]/", "", $tmp);
+                if (preg_match("/^[0-9]+$/", $tmp)) {
+                        $formul[$arr] = $_REQUEST[$arr];
+                }
+        }
+
+        $attribs = array('orgtype_id', 'orgindustry_id', 'org_size', 'country_id','bacula_version',
+                         'catalog_id', 'ostype_id','number_fd','number_sd', 'number_dir', 'month_gb','number_files');
+        foreach ($attribs as $arr) {
+                if (!$formul[$arr]) {
+                        echo "Can't get $arr
";
+                        return '';
+                }
+        }
+
+        if ($_FILES['org_logo']) {
+                $token = uniqid(md5(rand()), true);
+                $image = "/upload/$token";
+
+                if (preg_match("/(jpg|jpeg)$/i", $_FILES['org_logo']['name'])) {
+                        $image = "$image.jpg";
+                } elseif (preg_match("/png$/i", $_FILES['org_logo']['name'])) {
+                        $image = "$image.png";
+                } elseif (preg_match("/gif$/i", $_FILES['org_logo']['name'])) {
+                        $image = "$image.gif";
+                } else {
+                        $image = '';
+                }
+                if ($image) {
+                        $ret=move_uploaded_file($_FILES['org_logo']['tmp_name'], "$upload_dir/$image");
+                        $formul['org_logo'] = $image;
+                }
+        }
+        $formul['date'] = time();
+        $formul['visible'] = false;
+
+        return $formul;
+}
+
+function form_set_value($formul,$val)
+{
+ echo "document.getElementById('$val').value = '" . $formul[$val] . "';\n";
+}
+
+function form_set_selection($formul,$val)
+{
+ echo "document.getElementById('${val}_" . $formul[$val] . "').selected =true;\n";
+}
+
+function form_set_text($formul,$val)
+{
+ $temp = $formul[$val];
+ $temp = str_replace(array("\n", "\r"), array("\\n",""), $temp);
+ echo "document.getElementById('$val').value='" . $temp . "';\n";
+}
+
+// passwd file must exist in dat directory
+function is_admin()
+{
+   global $dat_dir;
+   $id = $_REQUEST['p'];
+
+   if (!$id) {
+       return(false);
+   }
+
+   if (!ereg('^[a-zA-Z]+$',$id)) {
+       return(false) ;
+   }
+   
+   if (file_exists("$dat_dir/$id")) {
+       return true;
+   } else {
+       return false;
+   }
+}
+
+function admin_link()
+{
+   global $password;
+   if (is_admin()) {
+      $pass = $_REQUEST['p'];
+      $waiting = $_REQUEST['waiting'];    
+      $password = "&p=$pass";
+      print "Admin: ";
+      if ($waiting) {
+         print " View all
";
+      } else {
+         print " View all | ";
+         print " View Waiting
";
+      }
+           print "
";
+   }
+}
+
+function load_formul($filename)
+{
+   if (!file_exists($filename)) {
+           return array();
+   }
+
+   if (!filesize($filename) || filesize($filename) > 10*1024*1024) {
+       return undef;
+   }
+   $fp = fopen($filename, 'r');
+   $contents = fread ($fp, filesize ($filename));
+   fclose ($fp);
+
+   $formul = unserialize($contents);
+   if (!is_array($formul)) {
+       return undef;
+   }
+
+   return $formul;
+}
+
+function print_formul_file($filename, $admin) {
+    global $password;
+    $form = load_formul($filename);
+    if (!$form) {
+       return 0;
+    }
+    
+    if (!$admin) {
+       if (!$form['visible']) {
+          return 0;
+       }
+    } 
+    $waiting = $_REQUEST['waiting'];
+    if ($admin && $waiting && $form['visible']) {
+       return 0;
+    }
+
+    $ret = print_formul($form);
+    if ($admin) {
+       if ($form['visible']) {
+          print " Hide  | \n";
+       } else {
+          print " Accept  | \n";
+       }
+       print " Modify  | \n";
+       print " Export 

\n";
+   }
+   return $ret;
+}
+
+function dump_sql()
+{
+   global $dat_dir, $country_lst, $org_type_lst, $org_industry_lst, $os_lst,$catalog_lst, $version_lst;
+   if (!is_admin()) {
+     return;
+   }
+?>
+   CREATE TABLE dict (lang text, id int, name text, primary key (lang, id));
+   CREATE TABLE testimonials (
+    contact_name        text,
+    email_address       text,
+    org_name            text,
+    title               text  DEFAULT '',
+    website             text  DEFAULT '',
+    filename            text  DEFAULT '',
+    month_gb            int   DEFAULT 0,
+    number_files        bigint DEFAULT 0,
+    number_dir          int   DEFAULT 0,
+    number_fd           int   DEFAULT 0,
+    number_sd           int   DEFAULT 0,
+    org_size            int   DEFAULT 0,
+
+    country_id          int,
+    ostype_id           int,
+    bacula_version      int,
+    contry_id           int,
+    orgindustry_id      int,
+    orgtype_id          int,
+    catalog_id          int,
+
+    id                  text,
+    publish_contact     int    DEFAULT 0,
+    publish_email       int    DEFAULT 0,
+    publish_website     int    DEFAULT 0,
+    publish_orgname     int    DEFAULT 0,
+    publish_orgsize     int    DEFAULT 0,
+    redundant_setup     int    DEFAULT 0,
+    support             int    DEFAULT 0,
+    comments            text   DEFAULT '',
+    hardware_comments   text   DEFAULT '', 
+    visible             int    DEFAULT 0,
+    org_logo            text   DEFAULT '',
+    date                int    DEFAULT 0,
+    lastmodifed         int    DEFAULT 0
+   );
+
+   CREATE VIEW reference AS SELECT contact_name,email_address,org_name,title,website,hardware_comments,comments,
+          publish_contact,publish_email,publish_orgname,org_size,publish_orgsize,publish_website,
+          redundant_setup,number_fd,number_sd,support,month_gb,number_files,number_dir,date,visible,filename,t.id,
+          orgtype.name AS orgtype, 
+          orgindustry.name AS orgindustry,
+          version.name AS bacula_version,
+          country.name AS country,
+          ostype.name AS ostype,
+          catalog.name AS catalog
+   FROM testimonials AS t, dict AS  orgtype, dict AS orgindustry, dict AS version, dict AS country, dict AS ostype,
+        dict AS catalog
+
+   WHERE t.orgtype_id = orgtype.id            AND orgtype.lang     = 'en'
+     AND t.orgindustry_id = orgindustry.id    AND orgindustry.lang = 'en'
+     AND t.bacula_version = version.id AND version.lang = 'en'
+     AND t.country_id = country.id            AND country.lang = 'en'
+     AND t.ostype_id  = ostype.id             AND ostype.lang = 'en'
+     AND t.catalog_id = catalog.id            AND catalog.lang = 'en';
+
+
+   INSERT INTO dict (lang, id, name) VALUES ('en', 0, 'no');
+   INSERT INTO dict (lang, id, name) VALUES ('en', 1, 'yes');
+
+   
+   
-- 
2.39.2



+   

+   
+   
+   
+   
+   
+
+   
+        
+   
+
+   
+        
+   
+
+    1) { ?>
+        
+   
+
+    1) { ?>
+        
+   
+
+   
+   
+        
+   
+
+   
+   
+   
+   
 Date:  
 Location:  
 Organization Type:  
 Industry/Function:  
 Organisation Size:  
 Website: 
 Number of fd:  
 GB/Month:  
 Comments:  
 

+   
+        
+   
+   
 

+
+
diff --git a/docs/home-page/es/pages/testimonials.php b/docs/home-page/es/pages/testimonials.php
new file mode 100644
index 00000000..c92e21d0
--- /dev/null
+++ b/docs/home-page/es/pages/testimonials.php
@@ -0,0 +1,123 @@
+
+
+
+        
+
+
+        
+
+
+
+        
+
+
+
+        
+
+
+        
+
+
+
+  
+
+
+

+                Testimonials
+        

+        Below, you will find excerpts from email that users have sent us.
+        The purpose is to give you some idea of what kinds of
+        sites are running Bacula and how they are using it.
+        These testimonials are used with permission of the author.
+        

+        
 Norm Dressler - 2004/06/15 

+        Bacula has been awesome for us. We used to use Ar**** but I
+        have always hated the interface. And the cost was outrageous.
+        Then I found bacula and wow! Everything in Ar**** and then
+        some! The console is easy to use, easy to understand once you
+        get the hang of it, and I usually don't have any problems
+        restoring files! :)
+        

+        I have 15+ machines I backup with Bacula
+        with an autoloader, and I'm extremely happy with the product.
+        Whenever someone asks me about what to use, I point them at
+        Bacula.
+        
 Norm Dressler, Senior Network Architect

+        

+        
 Michael Scherer - 2005/02/09 

+        Our former backup-system was ARGHserve running on NT4.
+        Due to the fact that we replaced most of our servers with
+        Linux machines we had to find some other solution.
 At
+        first we tried ARGHserve on Linux, without much comfort.
+        Database updates took days to complete, the database
+        itself grew enormously large, ...  not really something
+        you except from such an expensive piece of software.

+        I began the quest for a new backup-solution, testing
+        almost anything I could find on Sourceforge and Freshmeat
+        and finally decided to go with Bacula.
 It's perfectly
+        maintained by Kern and many others, is an (very) active
+        project with good support through maillists and an
+        irc-channel, which can be found on Freenode.

+        

+        Today we run Bacula on a SuSE based x86 machine with a
+        2.6 kernel, some RAID5-Systems and IBM Ultrium
+        Tapelibrary.  Without any issues and without more work
+        than changing two tapes in the morning.

+        

+        Recoveries aren't complicated as well, you either choose
+        a jobid to restore from or let Bacula find the correct
+        jobid for a file or directory you need to recover.  You
+        mark everything you need, Bacula tells you which tapes it
+        needs, done.

+        You don't even have to wait for any daemon to finish
+        database updates for backuped files, you can start with
+        the recovery right after the backup-job is done.
+        Perfect.  

+
+        

+        
 Michael Scherer, some admin 

+        

+        
 Ludovicz Strappazon - 2005/03/05

+                I had previously used Veritas Netbackup, but it was really too expensive
+                for our University. Bacula permitted us to buy a library. Now, we use
+                Bacula since 10/2002 with an ADIC Scalar 24 library and LTO ultrium,
+                without any problems. I think it can do anything Netbackup could do with our
+                configuration. We backup seven Linux servers, one NT server, four
+                Windows 2003 servers and a few XP workstations. Some of these servers
+                are backed up across a firewall using ssh; some others are on a private
+                network. We tried succesfully the disaster recovery procedure on Linux
+                and had some good results in restoring Windows "from bare metal". What do I
+                like in Bacula ?  It is very flexible and reliable. With its light
+                interface console, I can manage the backups from everywhere. A few words
+                about the support : it is free but efficient. I don't have to cross a
+                level 1, level 2 helpdesk to have some help, I never felt alone, and the
+                bacula-users mailing list is a mix of courtesy and honest speech. At
+                last, you don't need to be a big company to have your features requests
+                heard.

+                Thanks to Kern Sibbald and the others who give so much work and time
+                for this project.

+                

+                Ludovic Strappazon

+                University Marc Bloch de Strasbourg.

+        

+  
 Jeff Richards - 2006/08/26

+      I used Bacula at my previous employer to backup:  Linux, OpenBSD, Windows 2000,XP,2003, and AIX 5.1 
+      
  

+      Bacula provided a solution when I had no budget for backup
+      software.  The Linux systems (about 30) acted as Tivoli (TMF)
+      gateways.  The Linux systems were commodity PCs, so when the IDE
+      HDs failed it took hours (usually at least 4) to clean up the
+      Tivoli environment and rebuild the failed gateway.  Using Bacula
+      and mkCDrec I cut that time down to under an hour, and most of
+      that time was not spent doing anything except waiting for the
+      restore to finish.  I recovered 2 failed Linux systems with
+      Bacula.
+      
     
+      I would like to thank you and the entire Bacula team for an
+      excellent piece of software.
+         
 

+         Jeff Richards

+         Consultant

+  

+
+
diff --git a/docs/home-page/es/pages/vote.php b/docs/home-page/es/pages/vote.php
new file mode 100644
index 00000000..df30bbe0
--- /dev/null
+++ b/docs/home-page/es/pages/vote.php
@@ -0,0 +1,12 @@
+
+
+
+
+        
+
+

+        

+        
+        

+
+
diff --git a/docs/home-page/es/pages/what.php b/docs/home-page/es/pages/what.php
new file mode 100644
index 00000000..2924cab8
--- /dev/null
+++ b/docs/home-page/es/pages/what.php
@@ -0,0 +1,453 @@
+
+
+
+        
+
+
+        
+
+

+                What is Bacula?
+        

+
+Bacula is a set of computer programs that permit you (or the
+system administrator) to manage backup, recovery, and verification of
+computer data across a network of computers of different kinds. In
+technical terms, it is a network Client/Server based backup program.
+Bacula is relatively easy to use and efficient, while offering many
+advanced storage management features that make it easy to find and
+recover lost or damaged files. Due to its modular design, Bacula is
+scalable from small single computer systems to systems consisting of
+hundreds of computers located over a large network.
+
Who Needs Bacula?

+If you are currently using a program such as tar, dump, or
+bru to backup your computer data, and you would like a network
+solution, more flexibility, or catalog services, Bacula will most
+likely provide the additional features you want. However, if you are
+new to Unix systems or do not have offsetting experience with a sophisticated
+backup package, we do not recommend using Bacula as it is
+much more difficult to setup and use than tar or dump.
+
If you are running Amanda and would like a backup program that
+can write to multiple volumes (i.e. is not limited by your tape drive
+capacity), Bacula can most likely fill your needs. In addition,
+quite a number of our users report that Bacula is simpler to
+setup and use than other equivalent programs.
+
If you are
+currently using a sophisticated commercial package such as Legato
+Networker. ARCserveIT, Arkeia, or PerfectBackup+, you may be interested
+in Bacula, which provides many of the same features, and is free
+software available under the GNU Version 2 software license.
+
+
Bacula Components or Services

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

+        

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

+

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

+To perform a successful save or restore, the following four daemons
+must be configured and running: the Director daemon, the File daemon,
+the Storage daemon, and MySQL, PostgreSQL or SQLite.
+
+
Bacula Configuration

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

+        
+

+
+
Conventions Used in this Document

+Bacula is in a state of evolution, and as a consequence,
+this manual will not always agree with the code. If an
+item in this manual is preceded by an asterisk (*), it indicates
+that the particular feature is not implemented. If it is preceded
+by a plus sign (+), it indicates that the feature may be partially
+implemented.
+
If you are reading this manual as supplied in a released version
+of the software, the above paragraph holds true. If you are reading
+the online version of the manual, 
+http://www.bacula.org/rel-manual, please bear in mind that this version
+describes the current version in development (in the SVN) that may
+contain features not in the released version. Just the same,
+it generally lags behind the code a bit.
+
Quick Start

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

+To facilitate communication about this project, we provide here
+the definitions of the terminology that we use.
+

+        
Administrator

+        
The person or persons responsible for administrating the Bacula system.

+
+        
Backup

+        
We use the term Backup to refer to a Bacula Job that saves files. 

+
+        
Bootstrap File

+        
The bootstrap file is an ASCII file
+    containing a compact form of commands that allow Bacula or
+    the stand-alone file extraction utility (bextract) to
+    restore the contents of one or more Volumes, for example, the
+    current state of a system just backed up. With a bootstrap file,
+    Bacula can restore your system without a Catalog. You can
+    create a bootstrap file from a Catalog to extract any file or
+    files you wish.

+
+        
Catalog

+        
The Catalog is used to store summary information
+    about the Jobs, Clients, and Files that were backed up and on
+    what Volume or Volumes. The information saved in the Catalog
+    permits the administrator or user to determine what jobs were
+    run, their status as well as the important characteristics
+    of each file that was backed up. The Catalog is an online resource,
+    but does not contain the data for the files backed up. Most of
+    the information stored in the catalog is also stored on the
+    backup volumes (i.e. tapes). Of course, the tapes will also have
+    a copy of the file in addition to the File Attributes (see below).
+    
The catalog feature is one part of Bacula that distinguishes
+    it from simple backup and archive programs such as dump
+    and tar.
+    

+        
+        
Client

+        
In Bacula's terminology, the word Client
+    refers to the machine being backed up, and it is synonymous
+    with the File services or File daemon, and quite often, we
+    refer to it as the FD. A Client is defined in a configuration
+    file resource. 

+        
+        
Console

+        
The program that interfaces to the Director allowing
+    the user or system administrator to control Bacula.

+        
+        
Daemon

+        
Unix terminology for a program that is always present in
+    the background to carry out a designated task. On Windows systems, as
+    well as some Linux systems, daemons are called Services.

+        
+        
Directive

+        
The term directive is used to refer to a statement
+    or a record within a Resource in a configuration file that
+    defines one specific thing. For example, the Name directive
+    defines the name of the Resource.

+        
+        
Director

+        
The main Bacula server daemon that schedules and directs all
+    Bacula operations. Occassionally, we refer to the Director as DIR.

+        
+        
Differential

+        
A backup that includes all files changed since the last
+    Full save started. Note, other backup programs may define this differently.

+
+        
File Attributes

+        
The File Attributes are all the information
+    necessary about a file to identify it and all its properties such as
+    size, creation date, modification date, permissions, etc. Normally, the
+    attributes are handled entirely by Bacula so that the user never
+    needs to be concerned about them. The attributes do not include the
+    file's data.
+
+        
File Daemon

+        
The daemon running on the client
+    computer to be backed up. This is also referred to as the File
+    services, and sometimes as the Client services or the FD.
+        
+        
 FileSet

+        
A FileSet is a Resource contained in a configuration
+    file that defines the files to be backed up. It consists
+    of a list of included files or directories, a list of excluded files, and
+    how the file is to be stored (compression, encryption, signatures).
+    For more details, see the
+        FileSet Resource definition
+    in the Director chapter of this document.

+
+        
Incremental

+        
A backup that includes all files changed since the
+    last Full, Differential, or Incremental backup started. It is normally
+    specified on the Level directive within the Job resource
+    definition, or in a Schedule resourc. 

+        
+        
Job

+        
A Bacula Job is a configuration resource that defines
+    the work that Bacula must perform to backup or restore a particular
+    Client. It consists of the Type (backup, restore, verify,
+    etc), the Level (full, incremental,...), the FileSet,
+    and Storage the files are to be backed up (Storage device,
+    Media Pool). For more details, see the 
+        Job Resource definition
+        in the Director chapter of this document. 

+
+        
Monitor

+        
The program that interfaces to the all the daemons
+    allowing the user or system administrator to monitor Bacula status.

+        
+        
Resource

+        
A resource is a part of a configuration file that
+    defines a specific unit of information that is available to Bacula.
+    For example, the Job resource defines all the properties of
+    a specific Job: name, schedule, Volume pool, backup type, backup
+    level, ...

+        
+        
Restore

+        
A restore is a configuration resource that
+    describes the operation of recovering a file (lost or damaged) from
+    backup media. It is the inverse of a save, except that in most
+    cases, a restore will normally have a small set of files to restore,
+    while normally a Save backs up all the files on the system. Of
+    course, after a disk crash, Bacula can be called upon to do
+    a full Restore of all files that were on the system. 

+        
+        
Schedule

+        
A Schedule is a configuration resource that
+     defines when the Bacula Job will be scheduled for
+     execution. To use the Schedule, the Job resource will refer to
+     the name of the Schedule. For more details, see the Schedule Resource
+     definition in the Director chapter of this document. 

+         
+        
Service

+        
This is Windows terminology for a daemon -- see
+    above. It is now frequently used in Unix environments as well.

+        
+        
Storage Coordinates

+        
The information returned from the
+    Storage Services that uniquely locates a file on a backup medium. It
+    consists of two parts: one part pertains to each file saved, and the
+    other part pertains to the whole Job. Normally, this information is
+    saved in the Catalog so that the user doesn't need specific knowledge
+    of the Storage Coordinates. The Storage Coordinates include the
+    File Attributes (see above) plus the unique location of the information on
+    the backup Volume. 

+        
+        
Storage Daemon

+        
The Storage daemon, sometimes referred to as
+    the SD, is the code that writes the attributes and data to a storage
+    Volume (usually a tape or disk).

+        
+        
Session

+        
Normally refers to the internal conversation between
+    the File daemon and the Storage daemon. The File daemon opens a
+    session with the Storage daemon to save a FileSet, or to restore
+    it. A session has a one to one correspondence to a Bacula Job (see
+    above). 

+        
+        
Verify

+        
A verify is a job that compares the current file
+    attributes to the attributes that have previously been stored in the
+    Bacula Catalog. This feature can be used for detecting changes to
+    critical system files similar to what Tripwire does. One
+    of the major advantages of using Bacula to do this is that
+    on the machine you want protected such as a server, you can run
+    just the File daemon, and the Director, Storage daemon, and Catalog
+    reside on a different machine. As a consequence, if your server is
+    ever compromised, it is unlikely that your verification database
+    will be tampered with.
+    
Verify can also be used to check that the most recent Job
+    data written to a Volume agrees with what is stored in the Catalog
+    (i.e. it compares the file attributes), *or it can check the
+    Volume contents against the original files on disk. 

+        
+        
*Archive

+        
An Archive operation is done after a Save, and it
+    consists of removing the Volumes on which data is saved from active
+    use. These Volumes are marked as Archived, and many no longer be
+    used to save files. All the files contained on an Archived Volume
+    are removed from the Catalog. NOT YET IMPLEMENTED. 

+        
+        
*Update

+        
An Update operation causes the files on the remote
+    system to be updated to be the same as the host system. This is
+    equivalent to an rdist capability. NOT YET IMPLEMENTED.
+    

+
+        
Retention Period

+        
There are various kinds of retention
+    periods that Bacula recognizes. The most important are the
+    File Retention Period, Job Retention Period, and the
+    Volume Retention Period. Each of these retention periods
+    applies to the time that specific records will be kept in the
+    Catalog database. This should not be confused with the time that
+    the data saved to a Volume is valid. 
The File Retention Period
+    determines the time that File records are kept in the catalog
+    database. This period is important because the volume of the
+    database File records by far use the most storage space in the
+    database. As a consequence, you must ensure that regular
+    "pruning" of the database file records is done. (See
+    the Console retention command for more details on this
+    subject). 
The Job Retention Period is the length of time that
+    Job records will be kept in the database. Note, all the File
+    records are tied to the Job that saved those files. The File
+    records can be purged leaving the Job records. In this case,
+    information will be available about the jobs that ran, but not the
+    details of the files that were backed up. Normally, when a Job
+    record is purged, all its File records will also be purged. 
The
+    Volume Retention Period is the minimum of time that a Volume will be
+    kept before it is reused. Bacula will normally never
+    overwrite a Volume that contains the only backup copy of a file.
+    Under ideal conditions, the Catalog would retain entries for all
+    files backed up for all current Volumes. Once a Volume is
+    overwritten, the files that were backed up on that Volume are
+    automatically removed from the Catalog. However, if there is a very
+    large pool of Volumes or a Volume is never overwritten, the Catalog
+    database may become enormous. To keep the Catalog to a manageable
+    size, the backup information should removed from the Catalog after
+    the defined File Retention Period. Bacula provides the
+    mechanisms for the catalog to be automatically pruned according to
+    the retention periods defined. 

+
+        
Scan

+        
A Scan operation causes the contents of a Volume or a
+    series of Volumes to be scanned. These Volumes with the information
+    on which files they contain are restored to the Bacula Catalog.
+    Once the information is restored to the Catalog, the files contained
+    on those Volumes may be easily restored. This function is
+    particularly useful if certain Volumes or Jobs have exceeded
+    their retention period and have been pruned or purged from the
+    Catalog. Scanning data from Volumes into the Catalog is done
+    by using the bscan program. See the 
+    bscan section of the Bacula Utilities Chapter of this manual
+    for more details.

+
+        
Volume

+        
A Volume is an archive unit, normally a tape or
+    a named disk file where Bacula stores the data from one or more
+    backup jobs. All Bacula Volumes have a software label written to
+    the Volume by Bacula so that it identify what Volume it is really
+    reading. (Normally there should be no confusion with disk files,
+    but with tapes, it is easy to mount the wrong one).

+

+
+
What Bacula is Not

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

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

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

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

+        Interactions between Bacula Services
+

+        

+
+
diff --git a/docs/home-page/es/pages/wxconsole.php b/docs/home-page/es/pages/wxconsole.php
new file mode 100644
index 00000000..b544c956
--- /dev/null
+++ b/docs/home-page/es/pages/wxconsole.php
@@ -0,0 +1,3 @@
+
+TODO!
+
diff --git a/docs/home-page/fr/inc/header.php b/docs/home-page/fr/inc/header.php
index e6cc68af..c56ae6d6 100644
--- a/docs/home-page/fr/inc/header.php
+++ b/docs/home-page/fr/inc/header.php
@@ -75,6 +75,9 @@
                
             
               Deutsch
+                 
+            
+              Español