User Tools

Site Tools


bacula_manual:the_current_state_of_bacula

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
bacula_manual:the_current_state_of_bacula [2010/02/05 00:21]
baylink expand, clarify, and CHECKMEs
bacula_manual:the_current_state_of_bacula [2010/02/05 00:39] (current)
baylink fix STRIKE to what docu wants
Line 74: Line 74:
  
   * Since there is a client for each machine, you can backup and restore clients of any type ensuring that all attributes of files are properly saved and restored.   * Since there is a client for each machine, you can backup and restore clients of any type ensuring that all attributes of files are properly saved and restored.
-  * It is also possible to backup clients without any client software by using NFS or Samba. However, if possible, we recommend running a Client File daemon on each machine to be backed up. +  * It is also possible to backup clients without any client software by using NFS or Samba. However, if possible, we recommend running a Client File daemon on each machine to be backed up -- accessing filesystems through shares can make it impossible to get a completely clean backup of the files
-  * Bacula handles multi-volume backups. +  * Bacula handles multi-volume backups; backup jobs which are larger than your storage volumes
-  * A full comprehensive SQL standard database of all files backed up. This permits online viewing of files saved on any particular Volume. +  * A full comprehensive SQL standard database of all files backed up. This permits online viewing of files saved on any particular Volume, and makes user extensions of the system (for custom reporting or interfacing with other systems) much easier
-  * Automatic pruning of the database (removal of old records) thus simplifying database administration. +  * Automatic pruning of the catalog ​database (removal of old records) thus simplifying database administration ​- but you will never invalidate old backup volumes; catalog records can be rebuilt by reading the optional bootstrap file in the volume, or by scanning the volume
-  * Any SQL database engine can be used making Bacula very flexible. Drivers currently exist for MySQL, ​PostgreSQL, and SQLite.+  * Any SQL database engine can be used making Bacula very flexible. Drivers currently exist for PostgreSQL, MySQL, and SQLite.
   * The modular but integrated design makes Bacula very scalable.   * The modular but integrated design makes Bacula very scalable.
-  * Since Bacula uses client file servers, any database or other application can be properly shutdown by Bacula using the native tools of the system, backed up, then restarted (all within a Bacula Job).+  * Since Bacula uses client-side file service daemons, any database or other application can be properly shutdown by Bacula using the native tools of the client ​system, backed up, then restarted (all within a Bacula Job).
   * Bacula has a built-in Job scheduler.   * Bacula has a built-in Job scheduler.
   * The Volume format is documented and there are simple C programs to read/write it.   * The Volume format is documented and there are simple C programs to read/write it.
Line 87: Line 87:
   * According to one user Bacula is as fast as the big major commercial applications.   * According to one user Bacula is as fast as the big major commercial applications.
   * According to another user Bacula is four times as fast as another commercial application,​ probably because that application stores its catalog information in a large number of individual files rather than an SQL database as Bacula does.   * According to another user Bacula is four times as fast as another commercial application,​ probably because that application stores its catalog information in a large number of individual files rather than an SQL database as Bacula does.
-  * Aside from a GUI administrative interface, Bacula has a comprehensive shell administrative interface, which allows the administrator to use tools such as ssh to administrate ​any part of Bacula from anywhere (even from home).+  * Aside from a GUI administrative interface, Bacula has a comprehensive shell administrative interface, which allows the administrator to use tools such as ssh to administer ​any part of Bacula from anywhere (even from home, or your Blackberry).
   * Bacula has a Rescue CD for Linux systems with the following features:   * Bacula has a Rescue CD for Linux systems with the following features:
-    * You build it on your own system from scratch with one simple command: make -- well, then make burn.+    * You build it on your own system from scratch with one simple command: ​'make' ​-- well, then 'make burn'.
     * It uses your kernel     * It uses your kernel
     * It captures your current disk parameters and builds scripts that allow you to automatically repartition a disk and format it to put it back to what you had before.     * It captures your current disk parameters and builds scripts that allow you to automatically repartition a disk and format it to put it back to what you had before.
Line 99: Line 99:
 ===== Current Implementation Restrictions ===== ===== Current Implementation Restrictions =====
  
-  * If you have over 4 billion file entries stored in your database, the database FileId is likely to overflow. This is a monster database, but still possible. Bacula'​s FileId fields have been modified so that they can be upgraded from 32 to 64 bits in version 1.39 or later, but you must manually do so. +  * <del>If you have over 4 billion file entries stored in your database, the database FileId is likely to overflow. This is a monster database, but still possible ​- the average WinXP workstation can easily have 250,000 files on it.</​del> ​Bacula'​s FileId fields have been modified so that they can be upgraded from 32 to 64 bits in version 1.39 or later, but you must manually do so. 
-  * Files deleted after a Full save will be included in a restoration. This is typical for most similar backup programs (we have a project to correct this). +  * <del>Files deleted after a Full save will be included in a restoration. This is typical for most similar backup programs (we have a project to correct this).</​del>​ FIXME When did this get fixed? ​ 3.0.3? 
-  * Bacula'​s Differential and Incremental backups are based on time stamps. Consequently,​ if you move files into an existing directory or move a whole directory into the backup fileset after a Full backup, those files will probably not be backed up by an Incremental save because they will have old dates. You must explicitly update the date/time stamp on all moved files (we have a project to correct this).+  * Bacula'​s Differential and Incremental backups are based on time stamps. Consequently,​ if you move files into an existing directory or move a whole directory into the backup fileset after a Full backup, those files will probably not be backed up by an Incremental save because they will have old dates. You must explicitly update the date/time stamp on all moved files (we have a project to correct this).  If you are involved in enterprise level backup, you already have lots of good reasons to be running an internal NTP time sync cluster, and having all your machines sycned to it -- while that won't in fact solve this particular problem, it will make many other things work better, and this seemed a good place to mention it.
   * File System Modules (configurable routines for saving/​restoring special files) are not yet implemented.   * File System Modules (configurable routines for saving/​restoring special files) are not yet implemented.
-  * Bacula supports doing backups and restores to multiple devices of different media type and multiple Storage daemons. However, if you have backed up a job to multiple storage devices, Bacula can do a restore from only one device, which means that you will need to manually edit the bootstrap file to split it into two restores if you split the backup across storage devices. This restriction has been removed in version 2.2.0 and later, but it is not yet fully tested.+  * <del>Bacula supports doing backups and restores to multiple devices of different media type and multiple Storage daemons. However, if you have backed up a job to multiple storage devices, Bacula can do a restore from only one device, which means that you will need to manually edit the bootstrap file to split it into two restores if you split the backup across storage devices.</​del> ​This restriction has been removed in version 2.2.0 and later, but it is not yet fully tested.
   * Bacula cannot restore two different jobs in the same restore if those jobs were run simultaneously,​ unless you had data spooling turned on and the spool file held the full contents of both jobs. In other terms, Bacula cannot restore two jobs in the same restore if the jobs' data blocks were intermixed on the backup medium. This poses no restrictions for normal backup jobs even if they are run simultaneously.   * Bacula cannot restore two different jobs in the same restore if those jobs were run simultaneously,​ unless you had data spooling turned on and the spool file held the full contents of both jobs. In other terms, Bacula cannot restore two jobs in the same restore if the jobs' data blocks were intermixed on the backup medium. This poses no restrictions for normal backup jobs even if they are run simultaneously.
   * Bacula can generally restore any backup made from a client to any other client. However, if the architecture is significantly different (i.e. 32 bit architecture to 64 bit or Win32 to Unix), some restrictions may apply (e.g. Solaris door files do not exist on other Unix/Linux machines; there are reports that Zlib compression written with 64 bit machines does not always read correctly on a 32 bit machine).   * Bacula can generally restore any backup made from a client to any other client. However, if the architecture is significantly different (i.e. 32 bit architecture to 64 bit or Win32 to Unix), some restrictions may apply (e.g. Solaris door files do not exist on other Unix/Linux machines; there are reports that Zlib compression written with 64 bit machines does not always read correctly on a 32 bit machine).
bacula_manual/the_current_state_of_bacula.1265329270.txt.gz · Last modified: 2010/02/05 00:21 (external edit)