[prev in list] [next in list] [prev in thread] [next in thread] 

List:       nepomuk
Subject:    [Nepomuk] Backup service. Was: Re: ontology related advice
From:       phreedom.stdin () gmail ! com (Evgeny Egorochkin)
Date:       2009-10-23 5:47:12
Message-ID: 200910230847.12671.phreedom.stdin () gmail ! com
[Download RAW message or body]

? ????????? ?? ??????? 23 ??????? 2009 08:18:15 ????? Ben Martin ???????:
> On Wed, 2009-10-21 at 17:04 +0100, Laura Dragan wrote:
> ...
> 
> > I promised a while back that I would do a backup service
> > (NepomukService) but I never got around to do it. There are a lot of
> > things to consider, especially regarding the decision on what to
> > backup .. We should discuss this at the workshop, maybe we can
> > actually get it done :)
> 
> I've also been thinking it would be nice to make such a thing more
> readily available. Currently I just sopranocmd export to a file which is
> itself incrementally backed up by bacula.

For now it seems like the diff tool should have some presets for backup/restore 
operations. eg you want your work data backed up daily and to a different 
location than tags for your multimedia lib which is backed up weekly.

Looks like a collection of small scripts + some GUI. I wish I had time to do 
this but unf I'm totally occupied with libstreamanalyzer atm :(

> But having some sort of rdiff
> like thing build into the backup process would make sense.
> 
> For redland, a scheduled repair and lzo db_dump -p of the db files seems
> to work OK.

It's better to only backup user-generated content. This means you get to 
backup MBs instead of GBs. Imagine someone telling nepomuk to index KDE repo 
or something equally crazy(but possible) like this.

Of course indexing GBs of data doesn't apply to redland :)

-- Evgeny

[prev in list] [next in list] [prev in thread] [next in thread]