Versions Compared

Version Old Version 2 New Version Current
Changes made by

meer.ushter

Paul Le

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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

...

  • 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 configurationMainRepo(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 (dbdatabase, VPN etc.)

  • Roll back could be complicated In case of Migration failure user will have to roll depending on whether proxy server can used for redirect inbound traffic back to the previous old PROD server

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

Backup and Restored

...

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

  • There Here are some key files and folder that need to be backupbackup files for Iguana v6 or above:

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

    • Data

      Logs

      Delete

      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

      folder within the logs folderFor Enterprise customers ensure to

      folders).

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

    • Env.txt: Iguana environment files

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