User Tools

Site Tools


german_translation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

german_translation [2007/11/06 17:34]
german_translation [2008/04/08 09:33] (current)
Line 1: Line 1:
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +====deutsches Bacula Manual ====
 +
 +eine immer (halbwegs) aktuelle Version des deutschen Handbuchs ist unter
 +
 +http://www.bacula.org/de/?page=documentation
 +
 +zu finden.
 +
 +====open questions and comments:====
 +
 +any posts are welcome :)
 +
 +
 +
 +
 +
 +====bugs.tex====
 +
 +   In addition, the file {\bf patches-version-number} in the 
 +   {\bf patches} directory contains a summary of each of the patches.
 +
 +es gibt keine Datei namens patches-version-number, in patches/ liegen Verzeichnisse <version-number> und darin patches
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +====catmaintenance.tex====
 +
 +   Over time, as noted above, your database will tend to grow. I've noticed that
 +   even though Bacula regularly prunes files, {\bf MySQL} does not effectively
 +   use the space, and instead continues growing. To avoid this, from time to
 +   time, you must compact your database. Normally, large commercial database such
 +   as Oracle have commands that will compact a database to reclaim wasted file
 +   space. MySQL has the {\bf OPTIMIZE TABLE} command that you can use, and SQLite
 +   version 2.8.4 and greater has the {\bf VACUUM} command. We leave it to you to
 +   explore the utility of the {\bf OPTIMIZE TABLE} command in MySQL. 
 +
 +wie denn nun? MySQL oder {\bf MySQL} ?
 +
 +das zieht sich durch ganze Manual: Bacula und {\bf Bacula}
 +ohne {\bf} scheint aber die neuere Version zu sein ....
 +
 +
 +   Normally, large commercial database such
 +   as Oracle have commands that will compact a database to reclaim wasted file
 +   space.
 +
 +und danach kommt: "MySQL has the {\bf OPTIMIZE TABLE} command that you can use,"
 +ersatzlos streichen. alle Datenbanken haben solche Kommandos.
 +
 +
 +
 +
 +   Recently my root partition filled and the MySQL database was corrupted.
 +   Simply running {\bf myisamchk -r} did not fix the problem. However,
 +   the following script did the trick for me:
 +   
 +   \footnotesize
 +   \begin{verbatim}
 +   #!/bin/sh
 +   for i in *.MYD ; do
 +   mv $i x${i}
 +   t=`echo $i | cut -f 1 -d '.' -`
 +   mysql bacula <<END_OF_DATA
 +   set autocommit=1;
 +   truncate table $t;
 +   quit
 +   END_OF_DATA
 +     cp x${i} ${i}
 +     chown mysql:mysql ${i}
 +     myisamchk -r ${t}
 +   done
 +   \end{verbatim}
 +   \normalsize
 +   
 +   I invoked it with the following commands:
 +   
 +   \footnotesize
 +   \begin{verbatim}
 +   cd /var/lib/mysql/bacula
 +   ./repair
 +   \end{verbatim}
 +   \normalsize
 +   
 +   Then after ensuring that the database was correctly fixed, I did:
 +   \footnotesize
 +   \begin{verbatim}
 +   cd /var/lib/mysql/bacula
 +   rm -f x*.MYD
 +   \end{verbatim}
 +   \normalsize
 +
 +eventuell kurz erklaeren was das obige macht.
 +dt. version:
 +
 +   Hier ist ein Beispiel, wie man eine korrupte Datenbank reparieren k\"{o}nnte, falls nach dem Vollaufen
 +   einer Partition die Datenbankprobleme mit {\bf myisamchk -r} nicht behoben werden k\"{o}nnen:
 +   
 +   kopieren Sie folgende Zeilen in ein Shell-Script names {\bf repair}:
 +   \footnotesize
 +   \begin{verbatim}
 +   #!/bin/sh
 +   for i in *.MYD ; do
 +     mv $i x${i}
 +     t=`echo $i | cut -f 1 -d '.' -`
 +     mysql bacula <<END_OF_DATA
 +   set autocommit=1;
 +   truncate table $t;
 +   quit
 +   END_OF_DATA
 +     cp x${i} ${i}
 +     chown mysql:mysql ${i}
 +     myisamchk -r ${t}
 +   done
 +   \end{verbatim}
 +   \normalsize
 +   
 +   dieses Shell-Script, wird dann wie folgt aufgerufen:
 +   
 +   \footnotesize
 +   \begin{verbatim}
 +   cd /var/lib/mysql/bacula
 +   ./repair
 +   \end{verbatim}
 +   \normalsize
 +   
 +   nachdem sichergestellt ist, dass die Datenbank wieder korrekt funktioniert,
 +   kann man die alten Datenbank-Dateien l\"{o}schen:
 +   \footnotesize
 +   \begin{verbatim}
 +   cd /var/lib/mysql/bacula
 +   rm -f x*.MYD
 +   \end{verbatim}
 +   \normalsize
 +
 +
 +   If you are running into the error {\bf The table 'File' is full ...}, 
 +   it is probably because on version 4.x MySQL, the table is limited by default to a maximum size of 4 GB
 +
 +laut mysql-doc-5.1 war 4gb bei version kleiner 3.23 das maximum:
 +
 +   MySQL Version 3.22 hatte eine Begrenzung auf 4 Gbyte bei der Tabellengröße.
 +   Mit der Speicher-Engine MyISAM in MySQL Version 3.23 wurde die maximale Tabellengröße auf 65.536 Terabyte (2567 – 1 Byte) erhöht. 
 +
 +und seitdem, also auch bei 5.x ist standard bei 4 gb pro Tabelle:
 +
 +   Standardmäßig erzeugt MySQL MyISAM-Tabellen mit einer internen Struktur, die eine maximale Größe von 4 Gbyte erlaubt.
 +   Sie können die maximale Tabellengröße einer MyISAM-Tabelle mit der Anweisung SHOW TABLE STATUS oder mittels
 +   myisamchk -dv tbl_name feststellen. Siehe Abschnitt 13.5.4, „SHOW“.
 +
 +beim row-format dynamic scheint es 4gb zu sein, mit row-format fixed haben wir auch groessere (mysql 4.x)
 +
 +   system_stats      | MyISAM | Dynamic   4294967295 
 +   update_timestamps | MyISAM | Fixed    433791696895
 +   watchfile_checks  | MyISAM | Dynamic   4294967295 
 +   watchfiles        | MyISAM | Fixed        1911260446719 
 +
 +
 +
 +
 +   For MySQL, what is very important is to use the examine the    
 +   my.cnf file (usually in /etc/my.cnf).
 +
 +ist das ein sinnvoller englischer satz?
 +
 +   For SQLite3, one significant factor in improving the performance is
 +   to ensure that there is a "PRAGMA synchronous = NORMAL;" statement.
 +   This reduces the number of times that the database flushes the in memory
 +   cache to disk.
 +
 +auf der Suche nach PRAGMA ... fand ich diese Thread:
 +
 +   http://www.mail-archive.com/bacula-users%40lists.sourceforge.net/msg17792.html
 +
 +was bedeutet das?
 +
 +
 +   For example, you can {\bf cd} to the location of
 +   the Bacula database (typically /usr/local/pgsql/data or possible
 +   /var/lib/pgsql/data) and check the size. 
 +
 +heutzutage liegt sowas nie nicht niemals unter /usr 
 +schon vor 10 Jahren konnte man /usr readonly mounten .. :)
 +
 +
 +
 +
 +
 +====configure.tex====
 +
 +
 +   Spaces after the equal sign and before the first character of the value are
 +   ignored. 
 +
 +hinter dem gleichheitszeichen == vor dem ersten buchstaben des wertes
 +
 +   Please note that the Address, {\bf fd-sd}, that appears in the Storage
 +   resource of the Director, preceded with and asterisk in the above example, is
 +   passed to the File daemon in symbolic form.
 +
 +kein Asterisk im Bild und weder with and noch fd-sd gibt es.
 +
 +   The following configuration files must be defined:
 +
 +   * Console -- to define the resources for the Console program (user interface to the Director). It defines which Directors are available so that you may interact with them.
 +   * Director -- to define the resources necessary for the Director. You define all the Clients and Storage daemons that you use in this configuration file.
 +   * Client -- to define the resources for each client to be backed up. That is, you will have a separate Client resource file on each machine that runs a File daemon.
 +   * Storage -- to define the resources to be used by each Storage daemon. Normally, you will have a single Storage daemon that controls your tape drive or tape drives. However, if you have tape drives on several machines, you will have at least one Storage daemon per machine.
 +
 +console, director ... sind keine Konfigurations-Dateien ... da ist der dateiname aber besser
 +
 +
 +====mysql.tex====
 +
 +   If you are using one of the new modes such as
 +   ANSI/ISO compatibility, you may experience problems.
 +
 +wieso?
 +
 +