Akonadi

Introducció

El marc de treball Akonadi és el responsable de proporcionar a les aplicacions una base de dades centralitzada per a emmagatzemar, indexar i recuperar informació personal de l'usuari. Això inclou missatges de correu electrònic, contactes, calendaris, esdeveniments, diaris, alarmes, notes, etc. En SC 4.4, KAddressBook es va convertir en la primera aplicació en començar a utilitzar Akonadi. En SC 4.7, KMail, KOrganizer, KJots, etc, també s'han actualitzat per a utilitzar Akonadi. A més, els diversos ginys Plasma també utilitzen Akonadi per a emmagatzemar i recuperar els esdeveniments del calendari, notes, etc.

Currently, all KDE PIM applications with the exception of Akregator are using Akonadi to access user's PIM data.

Controlar el servidor Akonadi

Akonadi will start automatically in the background when any application using it is started.

To manually start, stop or restart Akonadi, you can use the akonadictl command from the commandline. Using this method, you can get additional useful information on the console.

Per a iniciar el servidor Akonadi,

akonadictl start

Per a aturar el servidor Akonadi,

akonadictl stop

Per a reiniciar un servidor Akonadi en execució,

akonadictl restart

Per a consultar l'estat del servidor Akonadi,

akonadictl status

Inhabilitar el subsistema Akonadi

El servidor Akonadi s'inicia per a qualsevol aplicació habilitada per Akonadi. Si no voleu que s'iniciï l'Akonadi després d'iniciar la sessió, haureu d'assegurar-vos que cap aplicació habilitada per Akonadi és llançada en iniciar la sessió o després. Recordeu revisar també els ginys Plasma -el giny de Rellotge digital en el plafó predeterminat, per exemple utilitza Akonadi (opcionalment) per a mostrar els esdeveniments del calendari i això està activat als seus ajustaments predeterminats (vegeu l'opció «Mostra els esdeveniments»)-. Haureu de treure els ginys que poden iniciar-lo, si voleu que l'Akonadi només s'iniciï quan s'iniciï el KMail o altres aplicacions.

Recordeu!

Si no voleu tenir Akonadi en execució al sistema, no podreu utilitzar cap de les aplicacions habilitades per a l'ús d'Akonadi. Aquestes aplicacions funcionaran quan Akonadi resti inhabilitat seguint els passos següents. Vegeu la llista d'aplicacions habilitades per a l'ús d'Akonadi. Cal tenir també en compte que alguns ginys Plasma, com el Rellotge digital utilitzen Akonadi.

Per a assegurar que no s'inicia l'Akonadi, comproveu que no hi ha aplicacions que el requereixen en iniciar la sessió. En particular, obriu les preferències de la miniaplicació rellotge del Plasma, aneu a Calendari i desmarqueu Mostra els esdeveniments per evitar que el Plasma sol·liciti informació a l'Akonadi i per tant permeti iniciar-lo.

Some Definitions

Real data

By real data we mean the data, like the contacts or events. These data are stored either on a groupware server or in local files. Where exactly depends on the resource you are using. E.g. the Personal Contacts resource stores its data under $XDG_DATA_HOME/contacts.

Cached data

The cached data are copies of the real data that are kept in the database for faster access and offline caching. The database also keeps the meta data which are management data needed by Akonadi to work correctly.

Configuration data

The configuration data are the data that configure the Akonadi server and the individual resources. The general configuration data for the server can be found under $XDG_CONFIG_HOME/akonadi. The configuration data for each indvidual resources are stored under $XDG_CONFIG_HOME/akonadi_xyz_resourcerc# (xyz is name of resource and # its instance number).

The Akonadi server configuration is a couple of files in $XDG_CONFIG_HOME/akonadi. It contains which data sources and helper programs are active and will be started and watched (so they can be restarted on crashes) by one of Akonadi's server processes (akonadi_control).

Each data source handler (called resources) or helper program (called agents) can have its own configuration although some agents or resources don't require configuration. The general rule is that for every entry in $XDG_CONFIG_HOME/akonadi/agentsrc there is a corresponding configuration file in $XDG_CONFIG_HOME. For example, if the [Instances] section in agentrc contains an entry for akonadi_ical_resource_2, there is also a config file called akonadi_ical_resource_2rc in the $XDG_CONFIG_HOME directory.

Depending on the type of data, such config files for resources will have filenames or directory names of where the data is stored. Common locations are KDE's legacy default files, e.g. $HOME/.kde/share/apps/korganizer/std.ics. New default locations are files and directories in $XDG_DATA_HOME, e.g. $XDG_DATA_HOME/contacts.

Backup

So now we need to decide what to back up. If you want to backup the "real data", then it depends on the resources you have configured... if you use a groupware server, then the backup should be done there. For contacts, the files under $XDG_DATA_HOME/contacts will normally be what you need.

To back up the entire Akonadi configuration, including which resources are active and their configuration, you can use the pimdataexporter' tool. This, however doesn't back up the Akonadi database containing the cached data and, unfortunately, after restoring the configuration (using the pimdataexporter again), Akonadi will have to re-fetch all data again into its cache. This can cause configuration that points to actual mail folders or calendars to get broken and accidentally point to another folder.

After restoring configuration and syncing all data, it's vital to manually check all folder configuration, especially in KMail identities and make sure the folders are configured properly.

Preguntes més freqüents

On són ara les meves dades?

Your data are safely stored outside of Akonadi control on your disk (e.g. local maildir folder or iCal calendar), or on a remote server (in case of e.g. email over IMAP or events from a CalDAV calendar). Akonadi will optionally store a copy of this data in its database to allow applications to quickly retrieve and display them. Any modifications done to data in the Akonadi database will be synced to the actual storage. The main advantage of using the database as a cache is that remote PIM data are available even when you are offline, and you can still interact with them (e.g. mark emails as read or move them, create new events, reschedule existing meetings etc.) and all the changes will get synced automatically once you connect to the internet again.

Thus, deleting the Akonadi database will not cause any data to be lost (as long as all pending changes are synced).

Com actualitzar la meva base de dades PostgreSQL?

Després d'actualitzar el servidor PostgreSQL a una nova versió major, de vegades haureu de convertir la vostra base de dades Akonadi per a utilitzar-la amb aquesta nova versió. Les instruccions es troben en aquesta pàgina.

Problemes de migració

L'entrada al glossari per a Akonadi té una breu descripció del seu propòsit i altres enllaços d'interès. En aquesta pàgina s'explica com treballen junts Akonadi i el KAddressBook.

How do I switch from MySQL/PostgreSQL to SQLite?

Since Akonadi 6 akonadi-db-migrator is included in akonadi that allows you to switch the database backend. Where for previous versions this involved deleting and recreating the database a migration is now properly supported by akonadi.

The tool needs to be called with the parameter --newengine to chose to which backend it should to: {{{

 --newengine <ENGINE>       The new DB engine to use. Possible values are 
                            "sqlite", "mysql" and "postgres"

}}}

For example: {{{ akonadi-db-migrator --newengine sqlite }}}