Re: [mbackup-devel] development schedule

[Known H. N. R. <ni...@in...>]

>
>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.

I would hightly suggest a tar output. Tar is an industry standard, and blah
blah blah. You know all the good reasons -- one above that being the ability
to restore (reasonably) /without/ mbackup.

Seems like tar would be a good intermediate format before the final output
filter, like writing a tar file to cdr or tape.

as always,
nick

       ni...@gr... * http://www.fargus.net/nick
Developer - Systems Engineer - Mad System Guru - MOO Sales
                      Keep on GRAWK'n!