Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

grafana.db backups -- need a more robust backup system #107

Open
CarlosNZ opened this issue Jun 11, 2020 · 1 comment
Open

grafana.db backups -- need a more robust backup system #107

CarlosNZ opened this issue Jun 11, 2020 · 1 comment

Comments

@CarlosNZ
Copy link
Collaborator

After checking the state of Dashboard backups, I've found only 3 are currently reliably exporting the grafana.db:
2020-06-10 12 01 37

I suggest that we come up a backup solution that works independent of mSupply and is installed along with grafana. Something like a script that sends the grafana.db to a FTP (or Dropbox? Or Google Drive?) server and a Windows scheduled task that is enabled when Grafana is installed.

Or perhaps we just go and manually turn on bundling the grafana.db with the mSupply backups like it's being done in the three places above?

Up for discussion.

@mark-prins
Copy link
Contributor

I'm reluctant to add another script or 3rd party to run a backup when we have dropbox, arq and the 4D backup running. It's just another item to install, configure and monitor.

Would be good to have the backup running though! Perhaps also time to investigate scheduling a postgres backup? that is worth investigating if we are using pg for other apps, which is the current thinking.

Dropbox appears to only support sync of folders that are subfolders of the nominated dropbox folder. which would mean moving config and db of grafana, or copying using something external to the dropbox folder. both of which I don't like the idea of too much.

Perhaps Arq or the backup features in windows?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants