...
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 (dbdatabase, 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 depending on whether proxy server can used for redirect inbound traffic back to the old PROD server
Backup and Restored
For any mirgration / upgrade, it is always recommended to plan for 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 Folder: contains translator sample data
Logs
Delete the meta and index folder within the logs folder
For Enterprise customers ensure to Note: For Enterprise and Professional Iguana License, backup .locker and .autounlocker filesautounlocker files to decode the Iguana logs
Folder: contains message logs and channel queued messages
Env.txt: Iguana environment files
Legacy VMD files: backup VMD files for your legacy VMD channels