Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

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:

Pros

Cons

  • This is useful for channels which has fewer channels (e.g < 40 channels )

  • No or less message lost from the Iguana channel queue

  • Expected down time during the migration

  • Recommended down time during the off hours

  • If any channel not working (ex. unable to connect external systems), a full rollback is needed

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:

Pros

Cons

  • No downtime and Iguana channels can be seamlessly transfer over to the new server.

  • Can work with any size of Iguana (ex. over 100 channels)

  • Need to keep Two Prod servers running at the same time

  • May need proxy server to navigate the inbound traffic

  • Overall migration time can be very lengthy

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 (db, VPN etc.)

  • Roll back could be complicated

  • In case of Migration failure user will have to roll back to the previous server

  • This includes reverting the source and destination system pointing back to the previous server

Backup and Restored

  • For any mirgration / upgrade, it is always recommended to plan for backup and restore in case of failure

  • There are some key files and folder that need to be backup:

    • IguanaMainRepo

    • Data

    • Logs

      • Delete the meta and index folder within the logs folder

      • For Enterprise customers ensure to backup  .locker and .autounlocker files

    • Env.txt

    • VMD files

  • No labels