Best practices for Vicidial Migration (different versions)

[mrgunston]

We have Vicidial running on a single server (Vicibox) and we are upgrading to a clustered envrionment which looks like this:

3 Diallers
1 DB
2 Webservers

I have setup the cluster and it all looks good. Now I need to figure out the plan for migration.

I understand that the admin_backup.pl script is built for this exact purpose however, I am concerned about complications of restoring from a single server into a cluster which is a newer version.

Old dialler config:

Version: 2.12b0.5
SVN Version: 2590
DB Schema Version: 1468
DB Schema Update Date: 2016-09-22 17:36:13

New dialler config:
Version: 2.14b0.5
SVN Version: 2829
DB Schema Version: 1519
DB Schema Update Date: 2018-09-25 14:12:29

Are there any considerations / best practices that I need to make? Also, it is worth noting that the new environment will have totally different IP address(s).


Current System:

Vicibox 2.12-565a from vicibox_v7x68_65.iso | Vicidial 2.12-565a Build 160827-0917 | Asterisk 11.23.1-vici | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | DELL R710 | Intel Xeon CPU X5690 @ 3.47Ghz 6 Cores


My goal is to have a all of the campaigns and data on the new system, but to continue running the latest version.

[mflorell]

I would suggest running all of the database schema upgrade files on the old server before backing the database up and moving it to the new server. Then after the database migration is complete, install the web servers and dialers.