-Orphaned Filename records. This condition happens any time a file is
- deleted from your system and all associated Job records have been purged.
- This can happen quite frequently as there are quite a large number of files
- that are created and then deleted. In addition, if you do a system update or
- delete an entire directory, there can be a very large number of Filename
- records that remain in the catalog but are no longer used.
-
- During standard purging (or pruning) of Job records, Bacula does not check
- for orphaned Filename records. As a consequence, over a period of time, old
- unused Filename records will accumulate and use space in your database. This
- check will eliminate them. It is strongly recommended that you run this check
- at least once a year, and for large database (more than 200 Megabytes), it is
- probably better to run this once every 6 months.
+Orphaned Filename records. This condition happens any time a file is
+ deleted from your system and all associated Job records have been
+ purged. This can happen quite frequently as there are quite a large
+ number of files that are created and then deleted. In addition, if you
+ do a system update or delete an entire directory, there can be a very
+ large number of Filename records that remain in the catalog but are no
+ longer used.
+
+ During standard purging (or pruning) of Job records, Bacula does not
+ check for orphaned Filename records. As a consequence, over a period of
+ time, old unused Filename records will accumulate and use space in your
+ database. This check will eliminate them. It is strongly recommended
+ that you run this check at least once a year, and for large database
+ (more than 200 Megabytes), it is probably better to run this once every
+ 6 months.