Hi Kevin.
On Wednesday, 25 March 2009 20:08:01 -0700,
Kevin Keane wrote:
> If you want tapes around forever, I think your best bet is to change
> the retention time in the pool to, say, ten years (I'm not sure if you
> can do an infinite retention time off the top of my head). Usually, if
> bacula can manage something, why would you want to do it manually?
In order to maintain a historical of full volumes whose content I always
could access. But following the procedure that you said to me it could
easily recover the content of some tape that was outside jukebox, so I
suppose that having this present we could do without the necessity of
only being able to recycle tapes automatically, unless we have files
device instead of a tape for backups.
> That said, to answer your other questions: you actually can recover
> what is on a tape even after the tape has been marked as "purged" in
> the database. The data on the tape is unchanged, and the btape and
> bextract utilities allow you to recover whatever is on the tape, even
> if it is no longer in the database.
Under these circumstances, would be correct the following procedure?
* To place tapes in jukebox.
* Mark the volumes recycle=0 then mark them Full.
* Run 'update slots=n1,n2-ni scan' from bconsole.
* Run 'restore' from bconsole in order to recover the data of some of
the volumes n1,n2-ni of full pool.
> In addition to Recycle = no, you may also want to set AutoPrune = no.
> Otherwise, bacula will still delete database records about your tapes.
Good. Thanks for the tip.
> You probably should make sure that the fileset resource has a shorter
> retention time than the jobs or volumes in the pool, since the file
> information takes up a lot of space in the database. The bacula manual
> has quite a bit of information on that aspect in the database
> maintenance chapter.
I was reading the 'catalog maintenance' chapter in order to understand a
little more on the operation of File Retention and Job Retention. But
something is not to me clear still. Beyond what is due to maintain the
rule File Retention < Job Retention < Volume Retention, from the moment
at which I would be leaving AutoPrune = no, then records in the catalog
database are keeping forever with the con the volume of the database
will grow more and more.
Why it would be necessary to use 'AutoPrune = no' if I can use bscan to
get back the jobs and file records that were purged from the database?
Thanks for your reply.
Regards,
Daniel
--
Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37
Powered by Debian GNU/Linux Squeeze - Linux user #188.598
signature.asc
Description: Digital signature
------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
