Upgrade Vicibox 7.0.2 to 7.04

[jbs0023]

Hi
I need to replace my sas drives with ssd drives on my database server, and am not sure the best route to follow.
My setup is as follows:

VERSION: 2.12-551a
BUILD: 160427-1656

4 x Telephony servers
1 x DB/Web server
All servers are running Vicibox 7.0.2.
I have a spare server which i am planning on using as the replacement db/web server, with the new ssd drives installed. i tried to install v7.0.2 onto this server but kept hitting a stumbling block after the installation when it reboots, it hangs on "Loading initial ramdisk". I then attempted to install 7.0.4 and that worked perfectly. now my problem is how do i migrate my database to the new server which is:

VERSION: 2.14-592a
BUILD: 170221-1542

i'd imagine the db structure has been changed in the newer version. i dont mind re-installing 7.0.4 onto the existing telephony servers.
Thanks in advance.

[williamconley]

Vicibox (7.0.2 / 7.0.4 in this case) is the Installer for Vicidial. The installer version is never actually relevant after installation. It merely provides a viable environment for Vicidial to run. Technically speaking, you can use Vicibox 1.0RC2 and install the latest version of ViciDIAL onto it and it'll work just fine. Keep that in mind.

Vicidial compatibility requires that the DB and the Vicidial scripts ... match. So if you have a DB that matched VERSION: 2.12-551a BUILD: 160427-1656 and your new server has VERSION: 2.14-592a BUILD: 170221-1542, you have two choices:

* Downgrade the Vicidial Version.
* Upgrade the Database Schema.

For the downgrade of the Vicidial system, you *could* copy the /usr/src/astguiclient/trunk folder from the original machine to the new one and then execute "perl install.pl" in that folder to push all the script files where they belong. You could also use the svn command to specify the version of Vicidial to force subversion to just go get the right version, and then perform that same install request.

For the upgrade of the DB, there's an "UPGRADE" document in that same folder. Essentially, there are ".sql" files for each major version of Vicidial. After each command in the file ... is a sql command that changes the "db schema" value in the database. Find all the commands that have not run ... and run them. Many just execute the whole file, but we like to copy the file, delete the commands up to and including the present db_schema, and then execute the modified copy (so only the "not yet run" commands are executed). To get the present DB schema, you check "admin->system settings", which is the value that is changed after every executed line in the file, so you can always see what the present DB schema is without checking an install log.

Of course, you could have probably swapped the SSD drives into the existing RAID one at a time without reinstalling at all.

Do note that while RAID1 is good for redundancy, it will fail under heavy stress. As will RAID5. RAID10 is the only proven reliable raid level after years of testing Vicidial (for the DB server, which responds to thousands of DB requests per second!). A six drive RAID10 is a very good idea if you can manage it. But only on the DB server. The other servers can survive with RAID1 or NO raid at all. (Just a fast HD)