What is the correct procedure to Migrate QueueMetrics to a new server?

Sometimes, migrating QueueMetrics to a new server is the easiest way to upgrade the software to the latest version. There are different approaches on how to migrate QueueMetrics; this guide will focus on the most basic and reliable procedure.

QueueMetrics Migration steps:

Stop the Loader service

You can check whether or not you have uniloader or qloaderd installed by running:

ps fax | grep loader   

Stop any qloaderd/uniloader service that is running, so that the current database will be in a stable state:

service qloaderd stop

or

service uniloader stop

depending on which you have installed.

1

Consider upgrading to the Uniloader service if you are still running the Qloaderd script: Qloaderd Upgrade

Backups

Make a complete backup of your existing system (configuration and database)

Configuration

Make a copy of the following files, found in

/usr/local/queuemetrics/qm-current/WEB-INF

listed below:

  • web.xml
  • configuration.properties
  • tpf.properties
  • agaw.properties

Database

Make a full backup of your database:

mysqldump -uroot -ppassword queuemetrics > queuemetrics_Backup.sql

NOTE: This will make QueueMetrics inaccessible for a short period of time, so make sure nobody is working on it at the time of the migration.

Install QueueMetrics

Install QueueMetrics using yum on your new server. It should be enough to run:

yum install queuemetrics -y

When it’s working (you are able to log in), turn it off with:

service queuemetrics stop

2

Import Database Backup

Overwrite the freshly created QueueMetrics database, on the new server, with the database backup from the old server:

mysql -uroot -ppassword queuemetrics < queuemetrics_Backup.sql

Import Configuration Files

Import the configuration files you copied previously in the new WEB-INF folder (/usr/local/queuemetrics/qm-current/WEB-INF).
If you are using the DirectAMI mode and only migrating QueueMetrics, remember to edit the callfile.dir property, from the “Edit system parameters” section, with the correct IP address of the PBX server.

Start the new QueueMetrics instance

Start the new QueueMetrics instance with:

service queuemetrics start

When you connect to the new QueueMetrics, it will realise that the database comes from an older version and will automatically update it, if needed. Follow the procedure and accept the license agreement.

3

Depending on the size of your database it might take a few minutes for the database to update.

4

NOTE: If you are updating from a version older than 17, you will need to update the database driver as well. You can find more details here:
Driver Update

Stop the old QueueMetrics instance

Stop the old QueueMetrics instance with:

service queuemetrics stop

NOTE: This will make QueueMetrics inaccessible, so make sure nobody is working on it at the time of the migration.

Sending data to the new QueueMetrics

If you are only migrating QueueMetrics, on the Asterisk machine, edit the Uniloader properties; usually stored in:

/etc/sysconfig/uniloader

Edit the URI parameter with the IP Address of the new machine.

5

If you are Migrating the PBX as well, install and configure the Uniloader service. You can find some more details here:
Uniloader installation

Final steps

Restart uniloader on the Asterisk machine with:

service uniloader start

Check if the Uniloader service in sending data to the new database:
From the new “Live DB Inspector” page, under “System Diagnostic Tools” on the QueueMetrics Homepage.
The new system should be working now!

Now, you just have to share the new QueueMetrics IP with your agent and start using the new Instance.

QueueMetrics References

QueueMetrics software is available on premise or as a cloud hosted service for FreePBX, Yeastar S PBX, Grandstream, Issabel, FusionPBX and many other Asterisk distros.

For more technical information please refer to the User Manual.

Visit www.queuemetrics.com for a free 30 days full featured trial.

Attend our Free Webinars for a live demonstration of QueueMetrics.

keyboard_arrow_left Back