At the Rwandan MOH we have 70 remote sites to deploy to soon and we need a backup strategy that doesn't require great internet or IT capacity at the sites. People have obviously tackled this problem before so am looking for ideas. I think the general idea should be:
1. Nightly database dumps 2. Delete dumps past a certain age to avoid filling up the hard drive 3. Regular transport of latest dump to another location I've attached a bash script that I've written which will read database connection details from the OpenMRS runtime properties file, dump the database and delete dumps older than a configurable number of days. Easy to hook this up to a nightly cron job. Not sure though about getting the database dumps to a different location. Should we try to make it all automated via rsync? Should we rely on site IT staff to copy dumps onto a USB device? Should those dumps be encypted? How could we encrypt them? Ideas anyone? -- *Dr Rowan Seymour** Partners In Health, Rwanda* Tel: +250783835665 _________________________________________ To unsubscribe from OpenMRS Implementers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-implement-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-implement-l]
openmrs_backup.sh
Description: Bourne shell script
