You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After checking the state of Dashboard backups, I've found only 3 are currently reliably exporting the grafana.db:
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.
The text was updated successfully, but these errors were encountered:
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.
After checking the state of Dashboard backups, I've found only 3 are currently reliably exporting the
grafana.db
: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.
The text was updated successfully, but these errors were encountered: