Why Iguana Needs Upgrade

• Upgrade Iguana to the newer version in order to get benefits from the new Iguana features (ex. log audit/encryption)

• Upgrade Iguana Server to a newer version because the older server os is no longer supported (ex. Win Server 2008)

• Migrate local Iguana server to the cloud (ex. AWS, Azure)

• Seeking Iguana migration best practices with minimum downtime

Common Migration Strategies

Big Bang

• Migrating all channels and Iguana configuration at once

• Common approach is to migrate IguanaMainRepo (Iguana 6 or above) and Logs into the new server

• Some considerations listed as below:

By Stages

• Migrate Iguana channels by groups (ex. related channels, channels complexity, vendor dependencies..etc.)

• Common approach is to setup fresh Iguana in the new server, migrate IguanaMainRepo (Iguana 6 or above) to new server, and use proxy server to redirect traffic based on the channel groups

• Some considerations listed as below:

Iguana upgrade on the Same Server vs Server Migration

Iguana upgrade on the Same Server

• No changes on the source and destination systems

• Easy to upgrade

• Steps are very straightforward:

  • Shutdown old Iguana service

  • Download newer version of Iguana

  • Update iguana_service.hdf file and change the working directory to the old Iguana Configurations folder

  • Install and start up new iguana_service

• Fall/Revert back procedure is fairly easy as well:

  • Uninstall/shutdown new Iguana service

  • Start up old Iguana service

• See more detail, visit the following links:
  https://help.interfaceware.com/v6/upgrade-to-iguana-6
  https://help.interfaceware.com/v6/upgrade-procedure

Server Migration

• Migrating to a new server require extra planning and efforts

• Check new server system requirements and supported operating systems (ex. compatible linux systems)

• Ensure both external source and destination systems can connect with this new server, such as firewall security, proxy server for redirecting inbound traffic

• Migrate Older Iguana MainRepo(channel configurations), logs(.locker and .autounlocker files for enterprise) and Env.txt into the new Iguana

• Ensure source and destination systems all points to the new server and configure security (database, VPN etc.)

• Roll back could be complicated depending on whether proxy server can used for redirect inbound traffic back to the old PROD server

Backup and Restore

• It is important to backup Iguana configurations and logs

• It is recommended to have a roll back plan in case of failure

• Here are some key backup files for Iguana v6 or above:

  • IguanaMainRepo folder: includes all Iguana channel, translator and server configurations as a Git repository

  • Data Folder: contains translator sample data

  • Logs Folder: contains message logs and channel queued messages (backup only .log files as Iguana will rebuild the meta and index folders).

    • Note: For Enterprise and Professional Iguana License, backup  .locker and .autounlocker files to decode the Iguana logs

  • Env.txt: Iguana environment files

  • Legacy VMD files: backup VMD files for your legacy VMD channels