'''Upgrading from GRAMPS 2.2.x to 3.0.x''' can be a pain-free process. The first step is to backup your database using GRAMPS' Export function. (Your version of GRAMPS may already automatically save copies of the .grdb and GRAMPS XML files.) The second step is to upgrade the application (discussed elsewhere). For the final step, this How-To article discusses some of the finer details in migrating your database.

+

{{languages}}

+

'''Upgrading from GRAMPS 2.2.x to 3.0.x''' can be a pain-free process.

−

==Oops==

+

# The first step is to backup your GRAMPS 2.2.x database using GRAMPS Export function. (Your version of GRAMPS may already automatically save copies of the .grdb and GRAMPS XML files.)

+

# The second step is to upgrade the application (discussed elsewhere).

+

# For the final step, this How-To article discusses some of the finer details in migrating your database.

−

The internal database format has changed between GRAMPS 2.2.x and 3.0.x. When you first start GRAMPS 3.0.x, your existing family tree(s) won't appear in the "Family Trees" window. '''Don't panic.''' You have not lost any data. Yet. ;)

+

==New GRAMPS 3.x database format==

−

If you didn't manually backup your database, look in <tt>~/.gramps/env</tt> to see where your automatic backups are stored.

+

GRAMPS 3.x uses a newer database format than GRAMPS 2.2.x. When you first start GRAMPS 3.0.x, your existing family tree(s) won't appear in the "Family Trees" window. '''Don't panic.''' Your GRAMPS 2.2.x family database is safe and you have not lost any data.

+

+

If you did not manually backup your database, look in <tt>~/.gramps/env</tt> to see where your automatic backups are stored.

find ~/.gramps/env -name '*.grdb'

find ~/.gramps/env -name '*.grdb'

−

A path like <tt>/home/jdoe/.gramps/env/home/jdoe/subpath/<i>data</i>.grdb</tt> would suggest we look in the folder, <tt>/home/jdoe/subpath</tt> where we'll hopefully find files, <tt><i>data</i>.backup.gramps</tt> (your family tree in GRAMPS XML format) and <tt><i>data</i>.grdb</tt>.

+

A path like <tt>/home/jdoe/.gramps/env/home/jdoe/subpath/<i>data</i>.grdb</tt> would suggest we look in the folder, <tt>/home/jdoe/subpath</tt> where we'll hopefully find files, <tt><i>data</i>.backup.gramps</tt> (your family tree in GRAMPS XML format) and <tt><i>data</i>.grdb</tt> (your family tree in GRAMPS .grdb format) .

−

Now would be a good time to make a copy of these files ... just in case.

+

Now would be a good time to make a backup copy of these files ... just in case.

If you don't have any backup files, you should revert the application back to GRAMPS 2.2.x and then make a backup.

If you don't have any backup files, you should revert the application back to GRAMPS 2.2.x and then make a backup.

Line 24:

Line 29:

# If you imported from a .grdb file, you will have to select an Individual before some functions work correctly (e.g., Pedigree).

# If you imported from a .grdb file, you will have to select an Individual before some functions work correctly (e.g., Pedigree).

Latest revision as of 19:34, 27 October 2011

The first step is to backup your GRAMPS 2.2.x database using GRAMPS Export function. (Your version of GRAMPS may already automatically save copies of the .grdb and GRAMPS XML files.)

The second step is to upgrade the application (discussed elsewhere).

For the final step, this How-To article discusses some of the finer details in migrating your database.

New GRAMPS 3.x database format

GRAMPS 3.x uses a newer database format than GRAMPS 2.2.x. When you first start GRAMPS 3.0.x, your existing family tree(s) won't appear in the "Family Trees" window. Don't panic. Your GRAMPS 2.2.x family database is safe and you have not lost any data.

If you did not manually backup your database, look in ~/.gramps/env to see where your automatic backups are stored.

find ~/.gramps/env -name '*.grdb'

A path like /home/jdoe/.gramps/env/home/jdoe/subpath/data.grdb would suggest we look in the folder, /home/jdoe/subpath where we'll hopefully find files, data.backup.gramps (your family tree in GRAMPS XML format) and data.grdb (your family tree in GRAMPS .grdb format) .

Now would be a good time to make a backup copy of these files ... just in case.

If you don't have any backup files, you should revert the application back to GRAMPS 2.2.x and then make a backup.

Database Migration

Launch GRAMPS 3.0.x.

In the (Manage) "Family Trees" window, select "New" to create a new family tree database.

Enter an appropriate name for your family tree. You can safely use the same name because your new family tree is stored in a different directory, ~/.gramps/grampsdb.

Next, Import from your backup file, e.g., data.backup.gramps.

Go to Media and check for broken links to be fixed. Broken links occur if you used Relative Paths.

If you imported from a .grdb file, you will have to select an Individual before some functions work correctly (e.g., Pedigree).