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:36]
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 99: Line 99:
 ===== Current Implementation Restrictions ===== ===== Current Implementation Restrictions =====
  
-  * <strike>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.</strike> 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. 
-  * <strike>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).</strike> FIXME When did this get fixed? ​ 3.0.3?+  * <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). ​ 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.   * 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.
-  * <strike>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.</​strike> 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).
-E 
  
 ===== Design Limitations or Restrictions ===== ===== Design Limitations or Restrictions =====
bacula_manual/the_current_state_of_bacula.1265330192.txt.gz · Last modified: 2010/02/05 00:36 by baylink