FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian KDE

 
 
LinkBack Thread Tools
 
Old 03-14-2010, 11:28 AM
Dominik Schulz
 
Default Akonadi-MySQL Issues

Hi,
I'm running KDE4.4 and am quite happy with it, but there are some small
issues. Maybe they'd better be discussed upstream, but I'd like to ask here
first before going that way.

1.) Akonadi startup errors
Akonadi used to show startup errors due to missing MySQL-Tables (mysql.*). I
fixed this using "akonadictl stop; mysql_install_db --
datadir=$HOME/.local/share/akonadi/db_data; akonadictl start" but I'm curisous
why this step wasn't performed when Akonadi was installed/upgraded?

2.) Akonadi backup
Another issue is also related to MySQL. Since MySQL/InnoDB is used as an
Akonadi backend, it troubles me how to properly backup user profiles in a
multi-user setup. Right now I'm just backing up the users homedirs which
covers most personal data and applicatin profiles, but with InnoDB this becomes
difficult w/o LVM Snapshots (which aren't available on all systems right now).
How is the akonadi db supposed to be backed up? Or is the information in the
db no vital to akonadi and shouldn't backed up at all? The akonadi
documentation seems to point this way, but I'm not sure.

3.) Virtusoso instead of Mysql as Akonadi backend
This question would probably better go upstream, but while I'm at asking
questions let me add this: Why isn't Akonadi using Virtuosos using an SQL-
Backend instead of MySQL? Since it's needed for nepomuk/strigi it could be
used for akonadi as well.

--
Mit freundlichen Grüßen / Best Regards
Dominik
 
Old 03-14-2010, 10:26 PM
Sune Vuorela
 
Default Akonadi-MySQL Issues

On 2010-03-14, Dominik Schulz <lkml@ds.gauner.org> wrote:
> 2.) Akonadi backup
> Another issue is also related to MySQL. Since MySQL/InnoDB is used as an=20
> Akonadi backend, it troubles me how to properly backup user profiles in a=20
> multi-user setup. Right now I'm just backing up the users homedirs which=20
> covers most personal data and applicatin profiles, but with InnoDB this bec=
> omes=20
> difficult w/o LVM Snapshots (which aren't available on all systems right no=
> w).=20
> How is the akonadi db supposed to be backed up? Or is the information in th=
> e=20
> db no vital to akonadi and shouldn't backed up at all? The akonadi=20
> documentation seems to point this way, but I'm not sure.

Akonadi is a data cache, not a data store, so by nuking the DB you are
only losing the bandwidth spent fetching it in the first place.

> 3.) Virtusoso instead of Mysql as Akonadi backend
> This question would probably better go upstream, but while I'm at asking=20
> questions let me add this: Why isn't Akonadi using Virtuosos using an SQL-
> Backend instead of MySQL? Since it's needed for nepomuk/strigi it could be=
>=20
> used for akonadi as well.

There has been someone test running it and it might end up like that one
day, but it has not (yet) been a priority.

/Sune


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: slrnhpqs5e.nfa.nospam@sshway.ssh.pusling.com">http ://lists.debian.org/slrnhpqs5e.nfa.nospam@sshway.ssh.pusling.com
 
Old 03-15-2010, 08:06 AM
Sune Vuorela
 
Default Akonadi-MySQL Issues

On 2010-03-14, Sune Vuorela <nospam@vuorela.dk> wrote:
> On 2010-03-14, Dominik Schulz <lkml@ds.gauner.org> wrote:
>> 2.) Akonadi backup
>> Another issue is also related to MySQL. Since MySQL/InnoDB is used as an=20
>> Akonadi backend, it troubles me how to properly backup user profiles in a=20
>> multi-user setup. Right now I'm just backing up the users homedirs which=20
>> covers most personal data and applicatin profiles, but with InnoDB this bec=
>> omes=20
>> difficult w/o LVM Snapshots (which aren't available on all systems right no=
>> w).=20
>> How is the akonadi db supposed to be backed up? Or is the information in th=
>> e=20
>> db no vital to akonadi and shouldn't backed up at all? The akonadi=20
>> documentation seems to point this way, but I'm not sure.
>
> Akonadi is a data cache, not a data store, so by nuking the DB you are
> only losing the bandwidth spent fetching it in the first place.

Or well. it is also containing data changed that still haven't been
replayed to the real storage. E.g. some offline imap handling.

It shouldn't be needed to backup the db.

/Sune


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: slrnhpru58.nfa.nospam@sshway.ssh.pusling.com">http ://lists.debian.org/slrnhpru58.nfa.nospam@sshway.ssh.pusling.com
 
Old 03-15-2010, 08:47 AM
George Kiagiadakis
 
Default Akonadi-MySQL Issues

On Sun, Mar 14, 2010 at 2:28 PM, Dominik Schulz <lkml@ds.gauner.org> wrote:
> 2.) Akonadi backup
> Another issue is also related to MySQL. Since MySQL/InnoDB is used as an
> Akonadi backend, it troubles me how to properly backup user profiles in a
> multi-user setup. Right now I'm just backing up the users homedirs which
> covers most personal data and applicatin profiles, but with InnoDB this becomes
> difficult w/o LVM Snapshots (which aren't available on all systems right now).
> How is the akonadi db supposed to be backed up? Or is the information in the
> db no vital to akonadi and shouldn't backed up at all? The akonadi
> documentation seems to point this way, but I'm not sure.

Well, since akonadi's database is stored in ~/.local, if you backup
the whole home dir, akonadi's db should be backed up too. The only
problem is that the database is huge; it's at least 100MB (!!!) when
it's created for the first time and keeps growing.... (On my
university's lab the admins have disabled akonadi just because of
that, to save space)


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: ba4a6e221003150247k6bd933b9i595d2f51fac12679@mail. gmail.com">http://lists.debian.org/ba4a6e221003150247k6bd933b9i595d2f51fac12679@mail. gmail.com
 
Old 03-15-2010, 11:08 AM
Michael Schuerig
 
Default Akonadi-MySQL Issues

On Monday 15 March 2010, George Kiagiadakis wrote:
> On Sun, Mar 14, 2010 at 2:28 PM, Dominik Schulz <lkml@ds.gauner.org>
wrote:
> > 2.) Akonadi backup
> > Another issue is also related to MySQL. Since MySQL/InnoDB is used
> > as an Akonadi backend, it troubles me how to properly backup user
> > profiles in a multi-user setup. Right now I'm just backing up the
> > users homedirs which covers most personal data and applicatin
> > profiles, but with InnoDB this becomes difficult w/o LVM Snapshots
> > (which aren't available on all systems right now). How is the
> > akonadi db supposed to be backed up? Or is the information in the
> > db no vital to akonadi and shouldn't backed up at all? The akonadi
> > documentation seems to point this way, but I'm not sure.
>
> Well, since akonadi's database is stored in ~/.local, if you backup
> the whole home dir, akonadi's db should be backed up too.

That, unfortunately, is a misconception. If you just copy the database
files while akonadi is running, you're in no way guaranteed to get a
consistent snapshot. The clean way to backup a database is to
transactionally dump its contents.

> The only
> problem is that the database is huge; it's at least 100MB (!!!) when
> it's created for the first time and keeps growing.... (On my
> university's lab the admins have disabled akonadi just because of
> that, to save space)

On a personal computer, I don't see the size itself as a problem.
However, regarding backups, there's no way to make small, incremental
backups. Tools such as rsnapshot (that keep hardlinks to unchanged files
in a snapshot) are thwarted, too.

BTW, it's not just akonadi that's affected by this problem, amarok has
started to use an embedded MySQL engine, too.

Michael

--
Michael Schuerig
mailto:michael@schuerig.de
http://www.schuerig.de/michael/


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201003151308.18875.michael@schuerig.de">http://lists.debian.org/201003151308.18875.michael@schuerig.de
 

Thread Tools




All times are GMT. The time now is 08:01 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org