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 cu
On 19.02.2009, at 14:50, Jari Fredriksson 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?
> Exclude the /archive from your normal backup job file
> 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 star
Hi,
18.02.2009 14:55, Sebastian Stark wrote:
> 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)
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
