You are here


5 Things to Consider When Migrating Opsview to New Hardware

Migrating software to new hardware can involve a variety of different processes and requirements. Without completing the proper planning, a straightforward migration will turn into a stressful project with unnecessary complications. For this reason, when you are working to migrate Opsview Monitor to a different hardware platform, we provide specific guidance so you can achieve a successful migration. Here are five things to consider before you get started! 

What Are You Upgrading? 

One important factor to consider during the process is whether the system is upgrading the OS, Opsview or both between migrations. Depending on the goal of the migration, the installation of Opsview Monitor at the new location may include installing a newer version of the product. For instances covering migrations with an OS and Opsview upgrade, be sure to read over this documentation

Opsview Agents/NRPE

If you have set up security on your Nagios® Remote Plugin Executor (NRPE) agents by limiting the IP address of the servers permitted to interrogate them, do not forget to include the new server’s IP address. To do this, simply edit the nsc.ini file on Windows or nrpe.cfg on Linux and change the ‘allowed hosts’ directive to include the IP address of the Opsview Monitor master server. 


If you limit Simple Network Management Protocol (SNMP) communication from a specific IP address, be sure that your devices have been updated to allow the new server to receive communication. Likewise, if you send SNMP traps to the Opsview Monitor master, ensure the traps are redirected to the new server. 


By setting up a firewall for web access to the Opsview Monitor master, you will need to update it to allow access to the new Opsview Monitor master’s IP address.

Sandbox Environment 

Using a sandbox environment to test out your processes before undergoing an important task is always a wise decision. This proves to be quite true in a migration scenario, as practicing the migration will help you reduce downtime in production. 

Final Tips

Once you finish migrating, you will effectively have two different instances of Opsview Monitor, each with their own data stores. 

If you have a distributed environment, then you should disable slave devices on the old Opsview Monitor installation since there will be contention between the master servers. If you are migrating to a new architecture, you should read through our documentation as it will guide you through how you should export your data. 

You do not need the same version of Opsview Monitor on the new hardware platform; however, be sure to read these upgrade instructions carefully because you cannot downgrade your new server. 


Get unified insight into your IT operations with Opsview Monitor

webteam's picture
by Opsview Team,
Opsview is passionately focused on monitoring that enables DevOps teams to deliver smarter business services, faster.

More like this

Apr 08, 2016
By Opsview Team, Administrator

A guide on how to execute a smooth transition from Nagios to Opsview. 

Mar 27, 2017
By Duncan Ferguson, Opsview Technical Expert

A complete guide on how to set up SNMPv3 traps. 

Mar 04, 2013
By Opsview Team, Administrator

NRPE is a daemon used by Opsview to allow central monitoring of a remote host by an Opsview server.

Opsview's use of NRPE allows...