Upgrading Urchin 6 to Newest Version

Urchin 6, as it's in constant development, often has a minor revision update. For example, from 6.5.01 to 6.6. These minor updates (any 6.* upgrade) are free for those that have purchased an Urchin 6 license. Follow the steps below to upgrade your Urchin installation without losing any data or customizations.

1. Backup Configuration
2. Backup Data
3. Backup Customizations
4. Download Upgrade Install Package
5. Upgrade Urchin
6. Recreate Customizations
7. Verify Upgrade

1. Backup Configuration

Backup your existing Urchin configuration database using one of the following methods:

MySQL
mysqldump –u {username} –p {database} > urchin_bak.sql

PostgreSQL
pg_dump -p {database port} -U {username} {database} > urchin_bak.sql

2. Backup Data

This step is Optional, as there is usually no risk to your data when upgrading Urchin 6. However, if you wish to be extra cautious, backup the entire urchin/data directory, which contains all your processed report data.

3. Backup Customizations

Traditionally, all customizations are made in urchin/lib/custom. Backup this entire directory. Also, if any changes were made to the following files, be sure to back them up and prepare to replicate them after upgrading:

• /etc/session.conf
• /etc/urchin.conf
• /var/urchinwebd.conf

4. Download Install Package

Download the latest Urchin install package from http://www.google.com/urchin/download.html. The latest version is 6.6.01.

5. Upgrade Installation

Run the installer and follow the steps to upgrading your Urchin instance. Make sure to uncheck "Delete and recreate Urchin specific database tables if they exist" during a Windows installations or answer NO to "Would you like to initialize the configuration database during install?" for Linix installations.

6. Recreate Customizations

Look in urchin/lib/custom and make sure all custom files still exist, if not, restore the backup made in step 3. Also, chances are that the following three files were changed. If so, recreate any modifications made to them:

• /etc/session.conf
• /etc/urchin.conf
• /var/urchinwebd.conf

7. Verify Upgrade

On any given page within Urchin, scroll all the way to the bottom and look in the lower left-hand corner of the screen to ensure you are using the new version. Take a look through all of your reports and configuration to ensure everything looks as it should. If you have any discrepancies, here are the most common causes and solutions:

No profiles, filters, log sources, etc.: Urchin configuration database was rebuilt. Restore backup:

MySQL
mysql –u {username} –p {database} < urchin_bak.sql

PostgreSQL
psql –h –p {port} -U {username} {database} < urchin_bak.sql

No Custom Report Sets, lookup tables, custom fields, etc.: Follow step 6 above.

No Data in Reports: If data files were in default location (urchin/data), restore the data backup to this location. If an alternate location was used to hold data files, /etc/urchin.conf has been updated. Follow step 6 above.