> For special data we have a backup scheme that does not
> really fit bacula's idea of incremental backups:
> 
> There is a directory, say /archive, that is empty by
> default. If something needs to be backed up by bacula, it
> is copied (or moved) into this directory. Then the backup
> job is started and eventually (see below) the data are
> deleted from the /archive directory. 
> 
> Since the data are very likely to have an older timestamp
> than the last bacula backup run, incremental backups do
> not work for this. So far we handle this by doing a full
> backup every time and deleting the data from /archive.
> But what we would like is to keep the data within /
> archive as long as possible. 
> 
> Is there any way to tell bacula it should backup all new
> files (new meaning "not already backed up") within this
> directory, regardless of the timestamp, without doing a
> full backup? 
> 
> touch(1) is not an option because the timestamps are
> important information we must not loose.
> 

Exclude the /archive from your normal backup job filelist.

Create a new additional job, and schedule a daily full job for it. Include  
only /archive.



------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users