On Jul 2, 2008, at 3:22 AM, Gregory Orange wrote:

> Robert Wirth wrote:
>> Hi!
>>
>> I wonder if there's a way to limit the backup job size or runtime
>> for incremental jobs only.  I guess, no.
>>
>> The particular problem is, that users, from time to time, are placing
>> some needless logfiles in the work diskspace.
>> We told to our users to use symbolic links to log space etc, but they
>> don't understand (or don't remember or what else).
>> We defined lots of exclusion rules, but they ever will create  
>> filenames
>> that don't match :-(
>> Then, the daily incremental backup might be 550 GB instead of 50 GB
>> (as at the past day...)
>
> Could you put in filesystem quotas or permissions management (ACLs or
> whatever), so they can't write such large data to the wrong place?  
> To me
> this issue points to policy & practices by staff, rather than  
> technology
> - although technology can assist.

I agree.  Enforce this issue at the OS level, not with your backups.

Consider: If the job can only backup 5GB and and the user has 5GB,
the problem is now yours.  You failed to backup their data.  And which
5GB of that 10GB should be backed up?

Move this problem to the user.  You don't want it.  :)

-- 
Dan Langille -- http://www.langille.org/






-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users