This chapter explains you how to move your reporting server to another one. It can be usefull if you want to migrate your reporting server from CentOS 6 to CentOS 7.

Migration of the interface extension is linked to Sipmon central migration.

Install the new reporting server

Install your new reporting server based and the Sipmon MBI repositories using the standard documentation.

Synchronizing files & data

Stop mysqld on both Reporting servers

service mysql stop

Copy data from the old reporting server to the new one:

rsync -avz /var/lib/mysql/* root@IP_New_Reporting_Server:/var/lib/mysql/

Execute the following command to ensure database files compatibility:

mysql_upgrade

• If no error is visible, restart MariaDB and continue to the section "Move generated reports"

• If you see errors, especially on the following tables mysql innodb_index_stats, innodb_table_stats, gtid_slave_pos, it might be caused by an incompatibility between MySQL/MariaDB 5.5 and MariaDB 10.5. In that case, follow the procedure below:

  service mysql stop
  cp -a /var/lib/mysql/ /var/lib/mysql.bak
  cd /var/lib/mysql/mysql/
  rm innodb_index_stats.frm innodb_index_stats.ibd innodb_table_stats.frm innodb_table_stats.ibd gtid_slave_pos.frm gtid_slave_pos.ibd
  service mysql start
  

  Then manually recreate the tables:

  mysql mysql < repair_mysql_upgrade.sql

  Download the file here: repair_mysql_upgrade.sql

Be sure to copy the the custom report & ressources you designed to your new reporting server in the same folders.

Move generated reports

In case you also move you Sipmon central server, you need to synchronize the folders containing generated reports on your new Sipmon server to be able to have them on the interface:

rsync -avz /var/lib/Sipmon/Sipmon-bi-server/archives/ root@IP_New_Sipmon_Server:/var/lib/Sipmon/Sipmon-bi-server/archives/