Something that could finally be related to what Kern called item 7. I'm
lazy, I qoute Kern:
Item 7: Add Plug-ins to the FileSet Include statements.
Date: 28 October 2005
Origin:
Status: Partially coded in 1.37 -- much more to do.
What: Allow users to specify wild-card and/or regular
expressions to be matched in both the Include and
Exclude directives in a FileSet. At the same time,
allow users to define plug-ins to be called (based on
regular expression/wild-card matching).
Why: This would give the users the ultimate ability to control
how files are backed up/restored. A user could write a
plug-in knows how to backup his Oracle database without
stopping/starting it, for example.
My comments:
Concerning something in-between wildcards/REs and "real" plugins, I
think that having better ways to handle volume snapshots under
unix/linux would be helpful.
Typically, a snapshot is created and mounted to some directory. If I
backup that directory, I've got the complete snapshot data, but for a
restore, the mount point of the snapshot should be purged from the paths
in the backup. Otherwise, restoring needs an additional step. (As far as
I know...)
So, I suggest to implement the option to delete leading path elements
from file names in the file set definition. See an example:
In the fileset, I have
File = /.snapshot/home
File = /.snapshot/var
File = /usr
File = /lib
but I would want to restore to /home, /var, /usr and /lib. A directive
to drop the leading /.snapshot in the FD, before sending the data to the
SD and catalog, would be good.
I can't suggest ways to implement this, but I have several ideas how to
express the necessary FileSet options.
One possible way would be to enhance the File = directive. Creating
File=xxx AS yyy is not a good idea as it might be ambiguous - nobody can
prevent me from creating a directory or file with that name.
Something like File [options] = xxx might work and be compatible. File
AS yyy = xxx or File drop 1st component = xxx or File
s/\/.snapshot\//\// = xxx could be used. The last suggestion is powerful
but unintuitive. Except for people speaking sed or PCRE.
Introducing an Option into the option blocks could be problematic
because I might end up needing an extra option block for all File=
statements included, I think.
This moment is perhaps also a good point in time to discuss the general
plug-in interface if something should evolve - defining some sort of
plugin API might make it easier to start implementing them.
Arno
(Note the reply-to to bacula-devel! Override if you think this should
rather be discussed at bacul-users.)
--
IT-Service Lehmann [EMAIL PROTECTED]
Arno Lehmann http://www.its-lehmann.de
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
