Recover corrupted family tree
[[::Recover corrupted family tree|English]] • [[::Recover corrupted family tree/de|Deutsch]] • [[::Recover corrupted family tree/fr|français]] • [[::Recover corrupted family tree/nl|Nederlands]]
An attempt to explain GRDB corruption, how to recover from it, and how to avoid it in the future.
Why this corruption?
By far, 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 current stable gramps releases store 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
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.
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.
- You copied
/home/user/genealogy/backup/BackupData.grdband the new file is not working.
/home/user/.gramps/env/home/user/genealogy/backup/BackupData.grdband 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
db4.4_load, or some such. 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.
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 smalll. Following are the good practices of backups:
- Export to XML from time to time, especially after large edits.
- 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.
- Export to XML before upgrading gramps to a newer version. Apparently, export to XML with old version before you install the new one!
- 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.
Can you guys not solve this ?
Yes we can! In the next version (GRAMPS 3.0/4.0) this part will be completely reworked, see here.