Difference between revisions of "OpenEMR Backup Tools"

From OpenEMR Project Wiki
(Created page with '== Overview == I am going to get on a little small soapbox for all the newbies using OpenEMR. Electronic Medical Records are your livelihood and exist to protect the health of…')
 
 
(31 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Overview ==
== Overview ==
 
Words of advice on backing up:
I am going to get on a little small soapbox for all the newbies using OpenEMR.
* The first most basic requirement of any database is a regular, frequent, comprehensive backup system.
* Losing data should terrify you.
Electronic Medical Records are your livelihood and exist to protect the health of your patients. If you are going to be your own IT manager you have to approach this professionally. The first most basic requirement of any database is a regular, frequent, comprehensive backup system.
* Hardware fails. Lightning strikes happen.
* A good backup strategy is drudgery but nothing will give such a warm, glowing, fuzzy, feeling like successfully recovering your system from a recent backup after a lightning strike that burns out a critical component on your server.
My system does real time back-ups to a second server. I also run a MySQL dump every 24 hours. I do this myself and I don't trust it to anyone else.
* Backup your databases on a regular basis (daily is best).  Make frequent secure backups of the MySQL data and the data in the openemr web directory.
* If you have the resources it is best to back up to an off site facility.  This can be done electronically over a secure internet connection (VPN) or you can burn CDs / DVDs and carry them off site.
Losing my data terrifies me and it should terrify you.
* Always backup before starting an upgrade.
 
I have not this happen to me, but some of our local practices have had break-ins where all the computers were stolen.  If they carry off your server you'll be in a big mess.
Hardware fails. Lightning strikes happen. I have had both occur since I started running OpenEMR. A good backup strategy is drudgery but nothing will give such a warm, glowing, fuzzy, feeling like successfully recovering your system from a recent backup after a lightning strike that burns out a critical component on your server.
Please backup your databases on a regular basis (daily is best).  Make frequent secure backups of the MySQL data and the data in the openemr / documents directory.  These are the irreplaceable parts.
 
I back up my data on a daily basis.  If you have the resources it is best to back up to an off site facility.  This can be done electronically over a secure internet connection (VPN) or you can burn CDs / DVDs and carry them off site.
 
Always backup before starting an upgrade.
 
 
Sam Bowen, MD
 


== Linux ==
== Linux ==
* [http://www.bradymd.com/appliance/manual3/#6.0.0.0.0.5.Automatic%20Backup%20Setup|outline Mandriva Backup] : This method/script will backup the complete MySQL database, the complete PostGreSQL database, the OpenEMR patient scanned documents file directories, the OpenEMR directory containing patient billing files, and the FreeB directory containing patient billing files. It will automatically backup to a secure local directory and burn the encrypted data to a multisession DVD(so, you can just leave the same DVD in the drive).
* [http://www.bradymd.com/appliance/manual9/#__RefHeading__5628_695817034 Ubuntu Backup] : This method/script will backup the complete MySQL database and the complete OpenEMR web directory. It will automatically backup encrypted data to a local directory and burn the encrypted data to a multisession DVD(so, you can just leave the same DVD in the drive). Here is a link to the raw script, if wanted: [[Media:Fullbackup4_sh.zip|fullbackup4_sh.zip]]
* [http://www.bradymd.com/appliance/manual5/#6.0.0.0.0.5.Backup%20(Automatic)%20Setup|outline Ubuntu Backup] : This method/script will backup the complete MySQL database and the complete OpenEMR web directory. It will automatically backup to a secure local directory and burn the encrypted data to a multisession DVD(so, you can just leave the same DVD in the drive).
* [[Backing Up Using the Built In Tools]] : OpenEMR has a built in 'backup' facility. this page describes how to use it, and how to manually perform the same task.
 
* [http://www.openhealthit.info/2010/06/openemr-dump-database/ Dump Database - Hourly ] : This procedure creates a database dump every hour and cleans out old backups once a day.
 
* [[Automated Backups to an Alternate Server]] : Rod's preferred method (documentation sponsored by IPPF).


== Windows ==
== Windows ==
*[[Windows OpenEMR Backup and Recovery| Windows Backup/Recovery]] a Downloadable HowTo using Windows Batch Routine Files (PDF Copy Enclosed) written by [http://www.holzerent.com Joe Holzer].
*[[Windows OpenEMR Restore using emr_backup.tar|Windows Restore from OpenEMR native backup file]] - Restore from your previously backed-up file (emr_backup.tar)
*[[Windows OpenEMR Backup and Recovery over Amazon Web Services]] A way to automate the encrypted backup of my windows server to Amazon web services (S3 cloud).
*[[Windows Backup And Restore Made Easy]]  A third way to backup.


== OS-X ==


== OS-X ==
[[Category:Backup]][[Category:Configuration Guide]]

Latest revision as of 22:00, 21 May 2016

Overview

Words of advice on backing up:

  • The first most basic requirement of any database is a regular, frequent, comprehensive backup system.
  • Losing data should terrify you.
  • Hardware fails. Lightning strikes happen.
  • A good backup strategy is drudgery but nothing will give such a warm, glowing, fuzzy, feeling like successfully recovering your system from a recent backup after a lightning strike that burns out a critical component on your server.
  • Backup your databases on a regular basis (daily is best). Make frequent secure backups of the MySQL data and the data in the openemr web directory.
  • If you have the resources it is best to back up to an off site facility. This can be done electronically over a secure internet connection (VPN) or you can burn CDs / DVDs and carry them off site.
  • Always backup before starting an upgrade.

Linux

  • Ubuntu Backup : This method/script will backup the complete MySQL database and the complete OpenEMR web directory. It will automatically backup encrypted data to a local directory and burn the encrypted data to a multisession DVD(so, you can just leave the same DVD in the drive). Here is a link to the raw script, if wanted: fullbackup4_sh.zip
  • Backing Up Using the Built In Tools : OpenEMR has a built in 'backup' facility. this page describes how to use it, and how to manually perform the same task.
  • Dump Database - Hourly  : This procedure creates a database dump every hour and cleans out old backups once a day.
  • Automated Backups to an Alternate Server : Rod's preferred method (documentation sponsored by IPPF).

Windows

OS-X