Hi,
I wonder if it is possible to mark a directory to be exclude from the
backup by another mean that the bacula-dir.conf.
Here we have a centralized configuration for what is to be backup, while I
think a distributed configuration would be more efficient and easy to handle
(Ok, not in every case, but in my case I don't get why the director should
know every thing about it's clients file system)
For example, if a directory would contain an empty file
.bacula_exclude_dir own by a specific user, the file daemon would not backup
this dir even if inside a directory mention with a File=
Or a file like the robot.txt that one left for search engines so they know
what to index and what not.
If the filedaemon find a file like .bacula_directives, it would follow
that list of directives for all subdir of the current dir.
Or even a configuration file for the file daemon. It's easier to modifiy
(with scripts) a conf file on the client, that to automatically update the
director conf file from the client (quite impossible in fact).
Ok, it's a bit intrusive, but as far as I know bacula, if the only way to
exclude a directory is to write some complex config in bacula-dir.conf, it's
very cumbersome !
In my case, on the machine I add very often new websites, each one with
specific structure with some files to be backup some not.
this would lead to huge config file or huge amount of data backuped for
nothing...
What do you think about that?
Thomas.
------------------------------------------------------------------------------
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
