Is there a way to configure bacula so that no matter what pruning
takes place, there is always a reference in the catalog to a file?

I may be incorrect, but the way I'm reading the retention
configuration information my problem is this:

1. I perform a FULL backup
2. I perform incremental backups
3. FULL backup files expire, requiring another full backup.

I would like to be able to configure bacula so that at any given time,
I have at least X amount of copies of the same file available in the
catalog, or a specific time-window configuration in which to purge
older copies of the same file (while keeping copes which meet the time
restraint). A combination of the two would be nice, where X amount of
copies are always kept available, and they are pushed out of the stack
(if you will) when new copies come in and the older copies no longer
meet the time window.

Sincerely,
-- 
Michael Short
Securenets
(901) 233-9926

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users