Azure Icinga 2.8 Migration Guide

Download PDF here.


Version 2.3

January 9, 2018

This guide instructs on how to move the configuration and data from one Azure Icinga machine to another with the same hostname. The following is only supported for Icinga version 2.8.


  • Both machines need have the same MySQL version installed
  • /etc/icinga2/cloud/system_passwords needs to reflect the correct passwords being used (Nothing to do if passwords weren’t altered)
  • Confirm that both machines have the same hostname
  • Confirm the new machines hostname resolves to localhost before running migration-new.  Utilize nslookup and ping to confirm the resolution.  If there are issues add the host name to /etc/hosts

NOTE: Using scp is a quick and easy way to transfer files from one machine to another. For example:

scp /tmp/icinga.sql root@<migratingIP>:/tmp/

Migration Steps

  1. Run /usr/lib/icinga2/migration-original on the machine that is being migrated from
  2. Send the following files over to the new master in the /tmp directory:
    • icingaconfig.tgz
    • icinga.sql
  3. Replace the/etc/icingaweb2/resources.ini file on the new machine with the original

    scp /etc/icingaweb2/resources.ini root@<migratingIP>:/etc/icingaweb2/resources.ini
  4. Replace the/etc/icingaweb2/modules/director/kickstart.ini file on the new machine with the original
  5. On the original machine, rename /etc/icinga2/cloud/system_passwords to /etc/icinga2/cloud/system_passwords.orig and copy it over to the new machine’s /etc/icinga2/cloud directory
  6. Copy the ca.crt and ca.key from /var/lib/icinga2/ca to the new machine in the same location
  7. Copy ca.crt<hostname>.crt and <hostname>.key found in /var/lib/icinga2/certs to the same location
  8. Run /usr/lib/icinga2/migration-new on the machine that is being migrated to
  9. On all clients, edit zones.conf files to point to the new master and restart the Icinga process
  10. In the new machine’s web portal, redeploy Director configuration if using director
  11. In the new machine’s web portal, navigate to the  Configuration tab on the left side, then ApplicationResources, and make sure all resources have the correct password