# Update / Upgrade the installation
URL: https://docs.valsight.ai/update-upgrade-the-installation/
Description: Follow these simple steps to keep the software up-to-date.
Follow these simple steps to keep the software up-to-date.

*Important: Always create a database backup before an application update. Updates can include database migrations, and although migrations are tested to the best of our knowledge, they always carry the risk of a failing migration that leaves the database in an inconsistent state.*

## Pre-upgrade

1. Download the installation zip file from the link provided by your Valsight support representative
2. Stop the service
3. Create a backup of the database and the application directory (See [Backup & Recovery](/backup-recovery/))

## Upgrade

1. Unzip the installation file of the new version in the same directory, overwriting existing files. Do not overwrite your runtime files:

   1. the configuration directory `conf/` (including `conf/config.yml`)
   2. the license file `license.pem`
   3. the database files `db/*.db`, if you run the integrated database
2. Windows only: adapt the version number in `<your install dir>/windowsservice/windowsservice.xml`.

## Post-upgrade

1. Start the application.

   1. On the first start of a new version, the database is upgraded & migrated automatically - it may take a little longer than a regular start.
2. Optional: Remove old rest-service-(old-version).war files from the *<your install dir>/lib/* directory.

## Troubleshooting

In case the application does not start after the upgrade double check the following:

* Windows only: Have you updated the version number in the XML File
* Does the log contain a message like the following?

  ```
  ERROR o.s.boot.SpringApplication - Application startup failed
  liquibase.exception.LockException: Could not acquire change log lock. Currently locked by ...
  ```

  In this case, a failed startup has locked the database. Double check that no application (java) process is running anymore and then run the SQL command from [Resetting the Database CHANGELOGLOCK](/resetting-the-database-changeloglock/).