Backing Up and Restoring Your OpenVPMS data

openVPMS: Backing Up and Restoring Your openVPMS Data

 

Home Page

 


CONTENTS

1. Introduction

Why do I need to backup my computer? I've never had a problem before.  ("Famous last words"!)
It's often been said of hard drive failure: " it's not a matter of if, it's a matter of when."

If you haven't lost data yet, count yourself lucky! It WILL happen. It happens if you lose data due to power surges or loss of power whilst writing data (and yes, you're probably thinking your UPS on the server protects you from that eventuality), equipment failure, a computer virus attack, or some other catastrophic event like a fire. Whilst hardware is cheap and easy to replace, consider how much it would cost to restore lost data (do you even have hard copy of your clinical records any more?).

Backing up your data and keeping that information somewhere "safe-and separate" means you will always have a copy of your data, just in case something tragic happens to your server.

2. Backing Up Your Data

Go to

https://openvpms.org/documentation/csh/2.3/topics/how/backup

for the current recommendations on backing up and restoring OpenVPMS.

3. Creating a system image

More extensive than a database back up, creating a system image enables the user to take a complete image of their hard drive and restore it in the event of a hard- or soft-ware failure.

Creating a System Image (Windows 7-10)


Updated 25 Nov 2021 (compiled by Yuri Sos)

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Im going to add a caveat here.  MYSQL ADMIN is no longer updated or supported by the Oracle team.  The version of mysqldump it arrives with is most likely outdated for the version of mysql you are running. This presents 2 possible issues    1. It may backup fine, but it may NOT restore to a new instance of mysql later.    2. The backup options you set may result in different sql formatting that may not apply... this is particularly relavent as oracle moves beyond mysql 5.6.   I advise that people use the mysqldump utility that is provided with the installation of msyql they are using.  There is NO GUI for mysqldump in the free community mysql version. When restoring after a critical failure. Reinstall using the same mysql version to ensure data consistency.   I have seen big changes when moving  from Mysql 5.1 to Mysql 5.6(developer version - not stable)      
Syndicate content