What files need backing up?

I'm trying to write a basic graphical backup tool for Linux, and I can't seem to find an up-to-date version of which files to backup. At the moment I'm:

* dumping out the database

...and backing up the following:

* /etc/mysql/my.cnf
* /var/lib/tomcat7/webapps/openvpms/WEB-INF/classes/localisation/*
* /var/lib/tomcat7/webapps/openvpms/WEB-INF/classes/style/default.stylesheet
* /usr/local/openvpms-release-1.7.1/conf/hibernate.properties
* /var/lib/tomcat7/webapps/openvpms/WEB-INF/classes/hibernate.properties

At one time I thought that document templates needed to be backed up, but I somehow found the (unreleased) v1.8 documentation on the site and it says that these are now part of the database. I can't find any info specifically for v1.7.1. Do I still need to backup these separately for v1.7.1, and if so where are they located? Is the above list complete for everything that needs to be backed up? (I realise some of these files contain info that needs to be hand-edited into new files if/when upgrading).

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: What files need backing up?

I've attached my very basic backup, restore and install scripts for OpenVPMS on Ubuntu.  They are by no means complete or even guaranteed to work correctly.  Use at your own risk (and even then only if you know what you're doing).

I'm using Zenity in the backup and restore shell scripts to give graphical feedback to the user.  Also, the restore script doesn't restore all that it probably should.

AttachmentSize
Backup_OpenVPMS.txt 1.8 KB
Restore_OpenVPMS.txt 2.32 KB
Install_OpenVPMS.txt 6.23 KB

Re: What files need backing up?

Document templates have always been stored in the database. If you customise the original versions located in <OPENVPMS_HOME>/reports, its probably a good idea to back those up.

Syndicate content