Re: [mbackup-devel] development schedule

[James O'K. <jo...@mi...>]

On Thu, 4 May 2000, Known Human Nick Rusnov wrote:

> Oh, another feature I would suggest would be the ability to backup the meta
> data as part of the backup in addition to keeping it locally (for future
> backups).

Since everyone else is doing this, I don't think we can get away with out
doing it. :) However, it might be done as a matter of suggestion and
policy to module writers. The way I envision things like this happening:

(Data flows from top to bottom in this list)
(non-related things deleted)

filter1 -- Data is read from some source (disk, network, etc)
filter2 -- Add a metadata entry to the local index
filter3 -- write the data to tape, with a copy of the metadata as well.

So each filter gets a chance to look at the file and the metadata and can
do with it as it pleases.

However,

This makes me think that maybe we need a facility for modules to schedule
functions to be called when certain events happen, such as the last file
has been processed. This would be where filter2 above would request that
it's index be written to tape as well.

Keep in mind that sometimes we might be writting to CDR or some other
random access media where knowing the permissions and pathnames for a file
would be needed, which is why the filter that writes the data needs the
metadata as well.

-james

Also, don't cc me and the list if you are mailing me. :)