[Gramps-users] db backup

[Alex R. <sh...@gr...>]

[Sorry, I lost original messages so can't reply properly and keep
the thread.]

Gramps 3.0.1 is most definitely backing up the database on exit.
This is done if there were 2 or more edits since the beginning
of the session.

The real data is kept under $HOME/.gramps/grampsdb/ (or whatever is
set in the preferences). Each family tree is a directory, whose
name looks like "483cb266" or somesuch. Under each family
tree directory, there are DB files (one per table), and log files.

The backups are dumped into the same directory, as a set of pickled
Python objects, one table per file. These are saved into .gbkp files.
For details see  src/GrampsDbUtils/_Backup.py  and comments therein.

The family tree manager will detect corruption and offer to restore
database from the backup files. Now that each data set has its own
environment (log files and locks etc) separate from others, the
data corruption so common in 2.2.x should not happen.

If you are curious about checking how gramps now responds to data
corruption, try creating a toy database and mess it up. As long as
backup files are there, you should always be able to restore from
backup without manual intervention. All should be do-able from
within the family tree manager in gramps.

Alex

P.S. This is how things work under the hood. I would strongly advice
to not mess up with your real data under .gramps/grampsdb
and use XML/GPKG formats for exchanging data between computers and
users, unless you know exactly what you are doing and are prepared
to face the consequences :-)

-- 
Alex Roitman <sh...@gr...>