From: Kern Sibbald Date: Fri, 9 Oct 2009 19:20:05 +0000 (+0200) Subject: Update bscan info X-Git-Tag: Release-3.0.3~2^2~1^2 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=8e8b9bf2b72a00cb393ac6967ea8e11cbf8c5c67;p=bacula%2Fdocs Update bscan info --- diff --git a/docs/manuals/en/utility/progs.tex b/docs/manuals/en/utility/progs.tex index 138053c6..440fd4b7 100644 --- a/docs/manuals/en/utility/progs.tex +++ b/docs/manuals/en/utility/progs.tex @@ -455,17 +455,21 @@ database is to reload the database by using the bootstrap file that was written when you saved it (default bacula-dir.conf file). The {\bf bscan} program can be used to re-create a database (catalog) -records from the backup information written to one or more Volumes. -This is normally -needed only if one or more Volumes have been pruned or purged from your -catalog so that the records on the Volume are no longer in the catalog, or -for Volumes that you have archived. - -With some care, it can also be used to synchronize your existing catalog with -a Volume. Although we have never seen a case of bscan damaging a -catalog, since bscan modifies your catalog, we recommend that -you do a simple ASCII backup of your database before running {\bf bscan} just -to be sure. See \ilink{Compacting Your Database}{CompactingMySQL} for +records from the backup information written to one or more Volumes. This +is normally needed only if one or more Volumes have been pruned or purged +from your catalog so that the records on the Volume are no longer in the +catalog, or for Volumes that you have archived. Note, if you scan in +Volumes that were previously purged, you will be able to do restores from +those Volumes. However, unless you modify the Job and File retention times +for the Jobs that were added by scanning, the next time you run any Job +with the same name, the records will be pruned again. Since it takes a +long time to scan Volumes this can be very frustrating. + +With some care, {\bf bscan} can also be used to synchronize your existing +catalog with a Volume. Although we have never seen a case of bscan +damaging a catalog, since bscan modifies your catalog, we recommend that +you do a simple ASCII backup of your database before running {\bf bscan} +just to be sure. See \ilink{Compacting Your Database}{CompactingMySQL} for the details of making a copy of your database. {\bf bscan} can also be useful in a disaster recovery situation, after the