Version 5.1.4
MacOS Monterey Version 12.7.5
https://www.gramps-project.org/wiki/index.php?title=How_to_make_a_backup
The above doc gives instructions for 5.2.x and up OR up to 3.3 or later. Is my 5.1.4 version considered the 3.3 or later version? It is not mentioned.
Thanks,
See the Backing up a Family Tree section in the Gramps 5.1 User Manual.
Yes, it is that older version’s workflow. The manual backup option from the Family Trees menu is the same. And that’s what is described.
Although automation for backup and its interface existed in 5.1, the GUI changed upgraded for the 5.2 cycle. The Preferences tabs have been reorganized. So the instructions changed for the automated (backup at timed intervals and upon exit) backup.
The intervals for timed backup were added for 5.0, then changed to be not be so excessively frequent in 5.2. The interaction of backup and sleeping OSes was tuned. The backup on exit is in a different tab.
Thank you, Nick, for the URL to 5.1 instructions.
One more question. Does the latest back up only apply to GRAMPS?
So must I open each surname file and make back ups before upgrading?
This question is confusing. What else would a Gramps backup apply to than Gramps? Please restate it.
The expectation is that people do NOT maintain separate Trees for each Surname line. (That approach is too hard to keep harmonized.) So if you have multiple Trees then yes, you should make backups for each tree.
Revised the introduction for the How to make a backup article to note when the available archival were added. (When was the “Archive” feature removed from the Family Trees dialog? The 5.2 FAQ has outdated mentions of GRDB in backup options and needs correction. And the import of old Archive files needs to be added to our data recovery processes.)
Lorrie has a good question too. The workflow to process backups for a large collection of Trees is pretty onerous.
It seems like a Report to do generate a CLI batch file for a collection of Trees would be one approach. That could be used to update the set of trees and would be less error prone than doing one-by-one manually. (If it had the option to suppress updating the “last accessed” timestamp, then that information would retain more value. I don’t care when a Tree was last loaded or even when it was updated to a newer schema or database backend. I only care when records were added, deleted or had field value changes.)
I was asking about updating the empty software without opening a surname file.
Before upgrading you should backup all data that you don’t want to lose.
The chance of something going wrong and corrupting your data is very small, but it is always better to be safe. It is also a good idea to backup your data before any big change.
I think I understand. Thank you.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.