Re: [Tracker] Rescue tracker db backup
- From: Philip Van Hoof <philip codeminded be>
- To: JÄnis RukÅÄns <janis ruksans gmail com>
- Cc: tracker-list gnome org
- Subject: Re: [Tracker] Rescue tracker db backup
- Date: Fri, 14 Dec 2012 08:43:36 +0100
On Fri, 2012-12-14 at 05:45 +0200, JÄnis RukÅÄns wrote:
Hi Janis,
Thanks for your answers!
Integrity check failure means that your N9 had a serious HW failure. For
that you should return your device to a Nokia service center.
I figure so (the first thing that comes to mind is NAND failing).
Still, I will need to get that data back into the phone once it's
fixed.
nod
Note that you should completely shut down Tracker's process and that
this isn't easy as your N9's other softwares will periodically
reactivate it based on their needs. So those process must be shut down
too to avoid this, while you are working with the files.
My idea is/was to do hard-reset followed by a backup. That gives a
clean db, which can be copied to a PC, updated from the real backup
and then used for restore.
Sadly that will also copy-back the corruption from your backup.db to
your then overwritten meta.db.
So far I've been able to extract the most important data I need using
plain SQL, but getting the full graph into another db calls for some
custom coding to adjust resource IDs and URIs. Having some progress on
that, too. Too bad tracker does not export it's ontology functions (at
least Fedora -devel packages don't have those headers), had to write
that part from scratch.
Sounds good.
By the way, are the :graph fields actually used anywhere? Or can I
safely use NULL or some existing graph ID?
They are actually used on the N9.
Kind regards,
Philip
--
Philip Van Hoof
Software developer
Codeminded BVBA - http://codeminded.be
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]