[Health-dev] Backup strategy

[Gerald Wiese]

Hey,

I was wondering if the way backups are managed with gnuhealth-control 
could be improved.

Currently there are three archives generated from:

- database

- home directory

- database & home directory together

First of all we could consider differentiating application and database 
as those could be on different systems. Thus we could split the option 
"backup" into "backup-database" and "backup-application".

Regarding the backup of the application I think we should not just copy 
the home directory and every python library. What I guess is necessary 
to backup is:

- Server version

- List of activated modules (how to get this?)

- Attachment folder

- Configuration file(s)

What could be useful as well:

- OS version

- pip freeze

- systemd file

What do you think about it?

Best

Gerald