Recover corrupted family tree - Revision history

Bmcage: /* I have backup gbkg files */

2013-05-14T13:31:26Z

‎I have backup gbkg files

Bmcage: /* I have backup gpkg files */

2013-05-13T19:43:24Z

‎I have backup gpkg files

Romjerome: /* What to do now? */

2013-01-06T10:14:46Z

‎What to do now?

Romjerome: /* What to do now? */

2013-01-06T10:11:07Z

‎What to do now?

Patsyblefebre: # ...TO_COMPLETE...

2013-01-06T10:09:03Z

# ...TO_COMPLETE...

Romjerome at 09:40, 6 January 2013

2013-01-06T09:40:42Z

Romjerome: /* What to do now? */

2013-01-06T09:31:32Z

‎What to do now?

Erikdr at 21:51, 25 November 2012

2012-11-25T21:51:04Z

Romjerome: /* Implement more security */

2012-11-23T21:52:23Z

‎Implement more security

Romjerome: /* I have backup gpkg files */

2012-11-23T21:48:56Z

‎I have backup gpkg files

@@ Line 49: / Line 49: @@
 # ...TO_COMPLETE...
-=== I have backup gbkg files ===
+=== I have backup gbkp files ===
-If you have a backup, you can try to recover the backup gbkg files. Do the following steps:
+If you have a backup, you can try to recover the backup gbkp files. Do the following steps:
 The procedure to recover your data from gbkp files is:
 # Copy the gbkp files to a new directory in your database directory, eg directory ''a1111''

@@ Line 49: / Line 49: @@
 # ...TO_COMPLETE...
-=== I have backup gpkg files ===
+=== I have backup gbkg files ===
-If you have a backup, you can try to recover the backup gpkg files. Do the following steps:
+If you have a backup, you can try to recover the backup gbkg files. Do the following steps:
 The procedure to recover your data from gbkp files is:
 # Copy the gbkp files to a new directory in your database directory, eg directory ''a1111''

@@ Line 29: / Line 29: @@
   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. Look at your [[Gramps_4.0_Wiki_Manual_-_User_Directory|home directory]]. Copy the directory of the tree with problems so as to have a backup:
+This will give you a list with all family trees and the directory where they are stored, normally somewhere in the directory  ~/.gramps/grampsdb. Look at your [[Gramps_4.0_Wiki_Manual_-_User_Directory|user directory]]. Copy the directory of the tree with problems so as to have a backup:
   cp -a <target directory> <backup directory>

@@ Line 29: / Line 29: @@
   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:
+This will give you a list with all family trees and the directory where they are stored, normally somewhere in the directory  ~/.gramps/grampsdb. Look at your [[Gramps_4.0_Wiki_Manual_-_User_Directory|home directory]]. Copy the directory of the tree with problems so as to have a backup:
   cp -a <target directory> <backup directory>

← Older revision		Revision as of 10:09, 6 January 2013
Line 44:		Line 44:

	====Windows OS====		====Windows OS====
		+	{{out of date\|says # ...TO_COMPLETE...}}

	# download Oracle tools on: http://www.oracle.com/technetwork/products/berkeleydb/downloads/index-082944.html		# download Oracle tools on: http://www.oracle.com/technetwork/products/berkeleydb/downloads/index-082944.html

← Older revision		Revision as of 09:40, 6 January 2013
Line 42:		Line 42:

	That should do the trick, and allow GRAMPS to load the family tree. If not, then start a ticket on the gramps bug tracker.		That should do the trick, and allow GRAMPS to load the family tree. If not, then start a ticket on the gramps bug tracker.
		+
		+	====Windows OS====
		+
		+	# download Oracle tools on: http://www.oracle.com/technetwork/products/berkeleydb/downloads/index-082944.html
		+	# ...TO_COMPLETE...

	=== I have backup gpkg files ===		=== I have backup gpkg files ===

@@ Line 34: / Line 34: @@
 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.8_recover, where 4.8 might be an older or newer version number.
+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.8_recover, where 4.8 might be an older or newer version number. See your BSDDB version into {{man menu|Help -> About}} dialog or with <code> gramps -v</code> command.
 Run this tool as follows:

@@ Line 1: / Line 1: @@
-{{languages}}
+{{grampsmanualcopyright}}
 Explanation of '''family tree''' and '''GRDB corruption''', how to recover from it, and how to avoid it in the future.
@@ Line 10: / Line 13: @@
 Gramps might give you on startup that recovery is needed via a dialog box:
-  GRAMPS has detected a problem in the underlying Berkeley database.
+  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
@@ Line 30: / Line 33: @@
   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 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.
+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.8_recover, where 4.8 might be an older or newer version number.
 Run this tool as follows:
   cd /home/<user>/.gramps/grampsdb/<target directory>
-  db4.6_recover -c
+  db4.8_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.
@@ Line 51: / Line 54: @@
 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 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 [[How_to_make_a_backup|backup]] in XML format (the .gramps format). Do not forget to disable privacy filters...
@@ Line 93: / Line 96: @@
 ====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 <code>db_dump</code> and <code>db_load</code>, <code>db41_dump</code> and <code>db41_load</code>, <code>db4.4_dump</code> and <code>db4.4_load</code>, ... In Ubuntu you find them in the package <code>db4.4-util</code>. 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 <code>db4.6-util</code>. Whatever they are called, there should be a dump tool and a load tool, and they should be version 4 or later.
+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 <code>db_dump</code> and <code>db_load</code>, <code>db41_dump</code> and <code>db41_load</code>, <code>db4.4_dump</code> and <code>db4.4_load</code>, ... In Ubuntu you find them in the package <code>db4.8-util</code>. 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 <code>db4.8-util</code>. Whatever they are called, there should be a dump tool and a load tool, and they should be version 4 or later. For Fedora 17 this is 'db4-utils-4.8.30-10.fc17'.
 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.8dump BackupData.grdb > somefile.txt
-     $ db4.4_load newfile.grdb < somefile.txt
+     $ db4.8_load newfile.grdb < somefile.txt
-and then cross your heart and hope that <code>newfile.grdb</code> will open in GRAMPS.
+and then cross your heart and hope that <code>newfile.grdb</code> 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:
+this is an indication you need a more recent version. So use db4.8 tools:
-     $ db4.6_dump BackupData.grdb > somefile.txt
+     $ db4.8_dump BackupData.grdb > somefile.txt
-     $ db4.6_load newfile.grdb < somefile.txt
+     $ db4.8_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.
@@ Line 121: / Line 123: @@
 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.
 [[Category:How do I...]]

@@ Line 54: / Line 54: @@
 If you know you work on GRAMPS sporadically only, or have no space to backup your trees regularly, then do [[How_to_make_a_backup|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:
+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 [[How_to_make_a_backup|backups]] :
 . Export to XML from time to time, especially after large edits.

@@ Line 41: / Line 41: @@
 === I have backup gpkg files ===
-If you have a [[How_to_make_a_backup|backup]], you can try to recover the backup gpkg files. Do the following steps:
+If you have a backup, you can try to recover the backup gpkg files. Do the following steps:
 The procedure to recover your data from gbkp files is:
 # Copy the gbkp files to a new directory in your database directory, eg directory ''a1111''
 # Copy name.txt, open it in the new directory and set the content to a unique name.
 # Create a file with name '''need_recover'''. Mind the underscore and the lack of an extension. The content of that file is unimportant.
 # Start Gramps, click on the family tree with the name you adjusted in step 2. There should be a red stop sign with that filename. Click on the Recover button. The red stop sign should disappear and you should be able to load that family tree.
 === Implement more security ===