De:Defekten Stammbaum wiederherstellen

From Gramps
Revision as of 18:11, 7 July 2012 by Leonhaeuser (Talk | contribs) (Ich habe gesicherte gpkg Dateien)

Jump to: navigation, search

(wird aktuell übersetzt kann ein paar Tage dauern 08.7.2012)

Explanation of family tree and GRDB corruption, how to recover from it, and how to avoid it in the future.

Stammbaum Beschädigung

Was verursacht diese Beschädigungen?

Not really known. Database corruption with family trees is however far less likely than with the previous format of storing your family tree Gramps version 2.2.x uses

Wie erfährst du davon?

Gramps might give you on startup that recovery is needed via a dialog box:

GRAMPS has detected a problem in the underlying Berkeley database.
This can be repaired by from the Family Tree Manager.
Select the database and click on the Repair button

But it might happen no Repair button is present, or you obtain the error (visible in terminal)

(-30975, 'DB_RUNRECOVERY: Fatal error, run database recovery -- PANIC: Invalid argument'). 

Was ist jetzt zu tun?

It is advisable not to click the repair button right away. It should work, but GRAMPS might believe an error is present while this is in reality not true. Repairing your tree then will lead to loss of the last typed changes.

Instead, take a backup of the family tree that is given problems. In a terminal do:

gramps -l 

This will give you a list with all family trees and the directory where they are stored, normally somewhere in the directory ~/.gramps/grampsdb. Copy the directory of the tree with problems so as to have a backup:

cp -a <target directory> <backup directory>

If the recover button was present on the GRAMPS family tree, click it. All should work again. If you notice you lost information, or the repair button does not work, then do the following. If recovery worked, but you do not like the result, backup this data and place your backup taken above back in its original position. You now have again the bad family tree to work on. Next, obtain the bsddb recovery tools, see your distributions package search page. The program is called db4.6_recover, where 4.6 might be an older or newer version number.

Starte diese Werkzeug wie folgt:

cd /home/<Benutzer>/.gramps/grampsdb/<Zielverzeichnis>
db4.6_recover -c

That should do the trick, and allow GRAMPS to load the family tree. If not, then start a ticket on the gramps bug tracker.

Ich habe gesicherte gpkg Dateien

Wenn du eine Sicherung besitzt, kannst du versuchen die gesicherten gpkg Dateien wiederherzustellen. Führe folgende Schritte durch: Die Prozedur um deine Daten aus gbkp Dateien wiederherzustellen ist:

  1. Kopiere die gbkp Dateien in ein neues Verzeichnis in deinem Datenbankverzeichnis, z.B. Verzeichnis a1111
  2. Erstelle eine Datei name.txt in dem neuen Verzeichnis als Inhalt der Datei wähle einen eindeutigen Namen (dies ist der Name, mit dem der Stammbaum in deiner Stammbaumliste auftaucht).
  3. Erstelle eine Datei mit dem Namen need_recover. Beachte den Unterstrich und das Fehlen einer Dateierweiterung. Der Inhalt der Datei ist unwichtig.
  4. Starte Gramps, klicke auf den Stammbaum mit dem Namen, den du in Schritt zwei festgelegt hast. Als Status sollte der Stammbaum ein rotes Stoppschild besitzen. Klicke auf die Wiederherstellen Schaltfläche. Das Stoppschild sollte verschwinden und du solltest den Stammbaum laden können.

Mehr Sicherheit einführen

Your genealogy data contains a lot of work and man hours. So work out a backup scheme

If you work on GRAMPS regularly: backup the directory holding the family tree databases. These are very large files however.

If you know you work on GRAMPS sporadically only, or have no space to backup your trees regularly, then do backup in XML format (the .gramps format). Do not forget to disable privacy filters... The XML format will open up just fine over 5 years on another computer with another OS. This will probably not be the case for the databases a family tree is stored in. XML is machine- and human-readable. It is completely self-sufficient. It is also small. The following are good practices of backups:

  1. Export to XML from time to time, especially after large edits.
  2. Export to XML before making big changes, such as importing new data into an existing database from e.g. GEDCOM, merging records, running tools that may heavily modify the data, etc.
  3. Export to XML before upgrading GRAMPS to a newer version. Apparently, export to XML with old version before you install the new one!
  4. Export to XML before upgrading your OS. 

Also, use XML format for any data migration. Moving to another machine, sending data to grandma, copying to another user on the same machine -- all of these cases should use XML, as there is no binary specific data.

Note that XML does not contain your media files. The gpkg output format contains XML and your media files, with the disadvantage of this being very large. If you already have a backup scheme for your media files, there is no need to also backup gpkg files.

ACI not ACID, upgrade, downgrade

Gramps protects your data using an ACI database. This means the last commit can be lost on an error, but not more than that. You should before an upgrade make sure Gramps closed your family tree correctly however.

There should be no error in opening a family tree with a newer version. See the long research in 3975, which does indicate version 4.7.25 of Bsddb contains a bug that can give a strange error message.

Trying to open a family tree after a downgrade is not supported. You will obtain an error that the database is created with a newer version.

Version 2.2.x: GRDB corruption

What causes this corruption?

The leading cause of grdb corruption is moving the grdb file from its original location. Whether you move the file to another directory, rename it, copy into another file, transfer to another machine, or another user account -- all of those will "corrupt" the file.

What happens is that the grdb file needs its database environment -- a directory with log files, lock files, temp files, etc. The 2.2.x gramps releases uses grdb files and stores the environment for each file, under a tree in a ~/.gramps/env directory. If your grdb file is /home/user/genealogy/MyData.grdb then its environment is in the /home/user/.gramps/env/home/user/genealogy/MyData.grdb directory.

So moving, copying, or renaming the file will copy the file's bytes, but not its environment. This is why the moved file appears corrupted.

Another cause can be an upgrade or downgrade of your operating system to a bsddb database backend that does not support fully the previous form of the database (eg, changed hash versions). This will also seem like a corruption in GRAMPS, but actually means the bsddb tools must be used to convert to data to a new version.

Not being able to open a /tmp/... file in GRAMPS 3.0.x on opening grdb files indicates database corruption. This is because the grdb file you want to open is copied to the /tmp dir, and then opened. All failure results in the '/tmp/tmpxxxxx could not be opened'

What do I do now?

The answer depends on whether or not you have the environment for that database. If you just copied one file into another then the environment may still work. If you modified the original database since then, the original environment has changed and there's no good environment for the new file. If you removed your .gramps directory (why oh why?) then all environments are lost. So act depending on the situation, as explained below.

The environment still exists

If you have environment directory for that file, copy it under the above gudelines.

Example
You copied /home/user/genealogy/MyData.grdb to /home/user/genealogy/backup/BackupData.grdb and the new file is not working.
Solution
Copy /home/user/.gramps/env/home/user/genealogy/MyData.grdb directory into /home/user/.gramps/env/home/user/genealogy/backup/BackupData.grdb and this should fix the problem.

The environment is lost

If you don't have the original environment for that file, you may try dumping and loading your data using Berkeley DB tools. Depending on your system, they may be called db_dump and db_load, db41_dump and db41_load, db4.4_dump and db4.4_load, ... In Ubuntu you find them in the package db4.4-util. You might need more recent versions depending on the version your distribution uses in its python package. So for eg Ubuntu Hardy created files, you will need db4.6-util. Whatever they are called, there should be a dump tool and a load tool, and they should be version 4 or later.

Basically, you just dump the grdb into a text file, then create a new grdb from that text file:

   $ db4.4_dump BackupData.grdb > somefile.txt
   $ db4.4_load newfile.grdb < somefile.txt

and then cross your heart and hope that newfile.grdb will open in GRAMPS.

If you obtain the error:

db4.4_dump: eidtrans: unsupported hash version: 9

this is an indication you need a more recent version. So use db4.6 tools:

   $ db4.6_dump BackupData.grdb > somefile.txt
   $ db4.6_load newfile.grdb < somefile.txt

Note: If you downgrade your distribution, it might be needed to do dump with 4.6 tools, and load with 4.4 or 4.5 tools.

How to prevent corruption?

While moving the file is the leading cause of corruption, apparently there are other less frequent causes that we don't fully know. So preventing corruption is not always possible.

What is possible though is to backup the data regularly. The backups should be in XML format (the .gramps format). XML is machine- and human-readable. It is completely self-sufficient. It is also small. The following are good practices of backups:

  1. Export to XML from time to time, especially after large edits.
  2. Export to XML before making big changes, such as importing new data into an existing database from e.g. GEDCOM, merging records, running tools that may heavily modify the data, etc.
  3. Export to XML before upgrading GRAMPS to a newer version. Apparently, export to XML with old version before you install the new one!
  4. Export to XML before upgrading your OS.

Also, use XML format for any data migration. Moving to another machine, sending data to grandma, copying to another user on the same machine -- all of these cases should use XML.