# Upgrade Guide

### Backup Data <a href="#id-.upgradeguidev6.0-backupdata" id="id-.upgradeguidev6.0-backupdata"></a>

Before upgrading any part, make sure to backup the following files and folders in the `EMUSEUM_HOME` directory:

* customcss/
* logos/
* profiles/
* watermarks/
* skins/
* messages/
* config.xml

If an external database is used, backup the database using the tools provided by the database management system.

### Software Prerequisites <a href="#id-.upgradeguidev6.0-softwareprerequisites" id="id-.upgradeguidev6.0-softwareprerequisites"></a>

The update of the required software, including Java, Tomcat, and Solr,  is independent of the update of eMuseum itself and should be done regularly. Update the runtime environment and the application server and re-apply all custom configuration options.

### eMuseum Home Directory <a href="#id-.upgradeguidev6.0-emuseumhomedirectory" id="id-.upgradeguidev6.0-emuseumhomedirectory"></a>

Download the new installation package and extract its content into the `EMUSEUM_HOME` directory. Ensure all files and sub-directories are still readable and writable by the user under which the application server runs.

### Database <a href="#id-.upgradeguidev6.0-database" id="id-.upgradeguidev6.0-database"></a>

Run the SQL statements from the [Release Notes](https://app.gitbook.com/s/I8MsiB7W4uuuZty0KGgg/release-notes) against the eMuseum database via any method suitable for the database system.

### Deploy Application <a href="#id-.upgradeguidev6.0-deployapplication" id="id-.upgradeguidev6.0-deployapplication"></a>

Deploy the new war file to the application server as described in the [Installation Guide](https://app.gitbook.com/s/I8MsiB7W4uuuZty0KGgg/installation). If the “auto-deployment” feature is enabled, this can be done by copying the file `EMUSEUM_HOME/bin/emuseum.war` (the filename will include the new version, e. g. `emuseum-6.2.war` ) to the directory `TOMCAT_HOME/webapps/`. Make sure to adjust the file name to match the existing one in the `webapps` folder before copying the file.

### Manual Intervention <a href="#id-.upgradeguidev6.0-manualinterventions" id="id-.upgradeguidev6.0-manualinterventions"></a>

Check the release notes for the version you're updating for any additional steps.