GNU Health - Tasks: task #16142, improve gnuhealth-control backup...
You are not allowed to post comments on this tracker with your current authentication level.
task #16142: improve gnuhealth-control backup & restore
Submitter: | Gerald Wiese <gerald_wiese> | ||
Submitted: | Thu 31 Mar 2022 01:12:50 PM UTC | ||
Should Start On: | Thu 31 Mar 2022 12:00:00 AM UTC | Should be Finished on: | Sun 01 May 2022 12:00:00 AM UTC |
Category: | None | Priority: | 5 - Normal |
Status: | In Progress | Privacy: | Public |
Percent Complete: | 0% | Assigned to: | None |
Open/Closed: | Open | Release: | None |
Module: | health | Component: | None |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
No changes have been made to this item
How to improve backups & restore in gnuhealth-control command?
Backup application for restore:
- attachments
- config files
- systemd service file
- .gnuhealthrc bash environment
- list of activated modules
Backup application for debugging if restore fails:
- OS version
- GH version
- Tryton version
- pip freeze
Backup PostgreSQL: A dump is saved but a backup as postgres/root could be more appropriate in order to save config files as well that are not world-readable
Any further thoughts on this?