Migrating Urchin to another server. Moving Urchin 4x from one server to another requires three basic steps.1. Moving the entire database. 2. Moving the configuration data. 3. Re-activation of the license. Moving the Database: The entire database is contained within a child directory of the main Urchin directory; ~urchin/data This directory should be archived and moved to the new server after installing Urchin on the new server. It should be restored in the same directory location on the new server; ~urchin/data. Moving the Configuration: The configuration also must be moved. However, if the new directory structure is different from that of the older server, Urchin will not be able to process logs and write data correctly. For instance, if Profile-A on the old server has the following parameters:
Log Source: /www/site1/logs/access_log data directory: /usr/home/urchin/data
...and the new server has a slightly different directory structure: Log source: /usr/www/site1/logs/access_log data directory: /usr/home/etc/urchin/data
...then, the old Urchin configuration cannot be imported "as is" and must be either recreated or edited before or after importing. Exporting and Importing the configuration: The Urchin 4 configuration can be edited as a text file. To do this, you must first export it from the ~urchin/util directory by running this command: ./uconf-export -f config.txt This will create a file called config.txt that can be edited and imported later. In most cases, you should install and complete the basic setup of Urchin 4 on the new server first. Do not create any profiles or log sources though. Only complete the basic Administration and system setup. When that is finished and you are prompted to add new profiles, "stop." This is when you will want to import your configuration file from the old server. Because you completed the basic setup, the new Urchin configuration will already contain "Global Settings" and "Process Settings." These must not be edited. So, before you import your old configuration file, open it for editing. Remove the "Global Settings" and "Process Settings" containers from the old configuration file. Those containers will have more data, but look something like this: #--------------------- # Global Settings #--------------------- <Global Name="Access Settings"> ct_name=Access Settings cr_remoteadmin=on cr_remoteaccess=on ct_port=9999 </Global> #--------------------- # Process Settings #--------------------- <Machine Name="Process Settings"> ct_name=Process Settings </Machine> Now you are ready to import the remaining configuration settings from the old server. Move the old configuration file into the new ~urchin/util directory and run the uconf-import tool to (-o) overwrite it with the new data: uconf-import -o -f config.txt Reactivate the Urchin License: After you have completed the configuration import, you'll need to relicense Urchin on the new server. You'll need to contact Technical Support for this and provide your company name and original serial number. If you do not have it we can look it up for you. After Support resets the license, you can login and select "Activate Pre-purchased License." This will complete the migration and licensing process.