Every attempt is made to make upgrading your Ampache installation as painless as possible. Although we do everything we can to prevent data loss during an upgrade it is never a bad idea to backup your database before performing an upgrade. Below is a simple command line way to backup your MySQL database. Whenever you upgrade Ampache it is recommend that you run a catalog Verify so that any improvements/changes to the tag reading process are applied to your local collection. The catalog verify is not forced during the upgrade due to the length of time it can take.
mysqldump -u <USERNAME> -p <AMPACHEDB> --add-drop-table --allow-keywords > mybackup.sql
mv ampache ampache.old
tar -xzf current.tar.gz
cp ampache.old/config/ampache.cfg.php ampache/config/
If Ampache reports that your config file is 'unreadable' after upgrading open your config file and remove all configuration options relating to RSS Feeds, these options should be at the bottom. This is due to a change in PHP versions which is often done at the same time as an Ampache upgrade.
Ampache 3.4 Introduces a new config format. Still follow the basic instructions however when attempting to login Ampache will redirect you to a different update page telling you that your ampache.cfg.php is out of date and must be updated. Run the command line script as instructed before continuing.
The newest release of Ampache will prompt Admins to download and install a config file if their current one is out of date. While ampache may work without the new config file, results may vary it is strongly recommended that if prompted you install the newly created config file
Updates from pre 3.3 versions of Ampache are no longer supported in the latest releases. It is recommended that you first download Ampache 3.3.5 and run any update process for that version before continuing to the newest release.