NAGIOSXI - migration OLE to RH

[Martin Reniec]

Hi,

we are trying to migrate our NagiosXI installation to brand new hardware
and we run into problems.
Let me explain steps we execute.

1) fullinstall of fresh, latest stable version of NagiosXI.
2) Restoring nagiosxi (php) configuration files
3) Drop databases (nagiosxi, nagiosql, nagios)
4) Load databases from dumps in following order: nagiosxi, nagiosql,
nagios.
5) Apply configuration

After these we would expect working copy of our current system.
Unfortunately in this scenario it looks like
core system is working fine, but NagiosXI does not, eg. Host and Services
Status Summary
dashlets stops refresh and active checks are disabled (ndo2db is running).

Also we already tried importing only nagiosql database and on the first
glance it is working, but after
restart of nagios core service active checks enters in disable state, host
status summary reports only critical
states (0 hosts in UP state), service status summary reports only CRITICAL
and WARNING state and so on.

We care deeply about services history, acknowledges and other things that
are stored in nagios mysql database,
hence it's important for us to make it imported from old system.

I would like to hear your comments or suggestions where can we make
mistakes or what is proper way to migrate
NagiosXI installation.

Of course more information may be provided on request.

Regards

[scottwilkerson]

I would recommend following very closely the steps outlined in our "Backing UP and Restoring Nagios XI" document:

http://assets.nagios.com/downloads/nagi ... ing_XI.pdf

Any other way of backing up and restoring Nagios XI may lead to unstable or unusable system.

Hope this helps.

[Martin Reniec]

Hi,
done according to the instructions ...
os is diffrent - migrates from Oracle Linux Enter .. to RH 5.7
you'll have to compile npre + libexec
problem lies in the display windows services and hosts
and navigation. ( services: 9000 and 1169 hosts)
XI all servicess display all 0

[scottwilkerson]

I am locking this topic as we are already handling this through a trouble ticket.