Good suggestion (.bacula with a more Bacula-styled syntax).
That way one could always write a script that converts ones .nsr files
to .bacula ones when (note: not "if" :-) one migrates from Networker to
Bacula :-)
- Peter
On Thu, 24 Nov 2005, Kern Sibbald wrote:
> Hello,
>
> Concerning the .nsr files and the CACHEDIR.TAG directories, here is an idea
> that merits discussion that seconds my comments that the Networker syntax is
> a bit hard to understand. The idea presented here gives some of the same
> features in a more Bacula like style syntax ...
>
> ---------- Forwarded Message ----------
>
> Subject: [Bacula-devel] Request for .bacula FileSet includes
> Date: Tuesday 22 March 2005 15:36
> From: "John Stoffel" <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
>
> Hi Kern,
>
> One of the things in Bacula that I miss from Legato Networker is the
> concept of directives files, which can change the behavior of how a
> backup runs without having to change the master configuration.
>
> They're called '.nsr' files in Legato and you can use them to skip or
> pre-process certain files during backups. Useful. Not that Legato
> has it done perfectly, the syntax (and man page examples) are
> baroque. But the idea is nice.
>
> It would be great if we could get .bacula files, which you could drop
> into a directory and have it either skip or ignore various files which
> you don't want backed up. Off the top of my head, a syntax like this
> might work:
>
> Directory: "." {
> Skip: *.jpeg
> Skip+: core
> Allow:
> Filter: "*.mp3" {
> Backup: /some/path/to/tool -backup
> Restore: /some/path/to/tool -restore
> }
> }
>
> The idea would be that you could specify the Skip directive to just
> skip files in the current directory. The Skip+ directive would skip
> files in the current and all descendent directories. The Allow: would
> let sub directories with .bacula files influence backups. Deny: would
> invert that obviously. The Filter: one would let you specify a tool
> which reads the various files (via STDIN probably) and writes the
> output to STDOUT so that bacula could them backup and restore the
> file(s) with a user provided script. Sorta like how the backups of
> the Catalog are done now, but more flexible.
>
> The whole idea is to allow admins/users to control what gets backed
> up. Of course, there would be a report (optional?) that would say
> what was Skipped or Filtered so you could at least get an idea of what
> wasn't going to tape.
>
> I just hate having to update the Director configuration and muck with
> the "Ignore Fileset Changes" toggle, just to make sure I don't backup
> MySQL databases in their raw format.
>
> What do people think?
>
> John
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Bacula-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/bacula-devel
>
> -------------------------------------------------------
>
>
--
Peter Eriksson <[EMAIL PROTECTED]> Phone: +46 13 28 2786
Computer Systems Manager/BOFH Cell/GSM: +46 705 18 2786
Physics Department, Linköping University Room: Building F, F203
SE-581 83 Linköping, Sweden http://www.ifm.liu.se/~peter
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
