vicidial Migrate to a newer version

[liigi]

Hi

Pals , i need your help .I have a running vicidial in a server VERSION: 2.12-496a BUILD: 150710-1120 that a want to migrate to a new server with a new vicidial version (vicibox 7) .How are the steps to do this .

I tried to do this, but it did not work :

1 Backup de DB in old server
2 Copy the DB to the new server
3 Restore de DB
4. But in admin page i dont see the data , campaing , list ...


another info , system page:
VERSION: 2.12b0.5
Versión SVN: 2552
DB versión de esquema: 1461

I have 1 DB-WEB SERVER and 2 DIALER.

Sorry for my bad english

[mflorell]

You need to upgrade the database schema. This is detailed in the UPGRADE document.

[liigi]

Thanks you, so i need to do this upgrade database in old server or in the new server : (

[mflorell]

ideally you would upgrade the database on the old server before migrating it.

[liigi]

Thanks a lot , you are the best

[liigi]

Hi mflorell i need your help


I perform the upgrade updating the database schema

but I've had some drawbacks
I use the following process in a test environment and work very well
:
-install a new database server
-perform the upgrade the database schema
-perform the backup
-restore the backup on the new server
-install the remaining cluster nodes ( telephony servers )


but now , i take this same process in my production environment and have some problems .
I install 1 database server ,1 web server , 4 telephony server , in 2 of the telephony server i have the following problems :


dahdi problem


"There aren't any DAHDI hardware modules specified to
load Please update /etc/dahdi/modules in order to
specify the modules to load"

"the /dev/dahdi directory if missing"


i solved this by the modprobe dahdi


in the other 2 server i dont have this problem. i use the same media instaltion and process

good for now. ,



in all of the telephony server i have the following problems :

administration page problem


when I make a change in the administration page it is not reflected on servers,
for example, if I create a new trunk not reflect the changes must go directly to the server and perform restart asterisk


VERSION: 2.12b0.5
Versión SVN: 2578
DB versión de esquema: 1464