On 18.02.2009, at 22:08, Arno Lehmann wrote:
>> 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?
>>
> Solution one: Wait for 3.0, and / or start testing the current
> development version. You want the feature called "Accurate Backup".

Sounds good, thanks.

> Solution two: Create the file list to back up by script. Let that
> script have a minimal database of the files which are already backed
> up. Read the file list, subtract the files in the database, print the
> files to back up, save the list of files *in a temporary location*,
> preferably including the current job name.
>
> As a "Client Run after Job", have a script that *on success* of the
> job copies the temporary file list to the actual database. In any
> case, delete the temporary file list.


This does not sound less complex than what I do now (mv(1) old data  
and run full backup job), but it's a good tip anyway.


Sebastian

-- 
http://www.kyb.tuebingen.mpg.de/~stark
Max Planck Institute for Biological Cybernetics


------------------------------------------------------------------------------
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