16,602
edits
Changes
m
no edit summary
=== 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:
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''
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...
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:
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 [[How_to_make_a_backup|backup ]] the data regularly. The [[How_to_make_a_backup|backups ]] should be in XML format (the <code>.gramps</code> format). XML is machine- and human-readable. It is completely self-sufficient. It is also small. The following are 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.
