Howto:Migrating an existing LAP System from IPx10(CF) to IPx11(SSD): Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 28: Line 28:


**We have Standby-Reporting application running, so when we have the new system running they will sync and the missing CDRs during the update proccess with be retrieved.
**We have Standby-Reporting application running, so when we have the new system running they will sync and the missing CDRs during the update proccess with be retrieved.
**We set the CDR0/1 Interface to a wrong IP so the CDRs are buffered on the PBX and resent when set again the right IP address of the new IPx11 Gateway (The buffer could be not enough if the amount of CDRs received are too many so the solution of using Standby-Reporting application it's more safe).
**We set the CDR0/1 Interface to a wrong IP so the CDRs are buffered on the PBX and resent when set again the right IP address of the new IPx11 Gateway (The buffer could be not enough if the amount of CDRs received are too many so the solution of using Standby-Reporting application is more safe).


*For the reasons above pointed it's strongly recommended to do this process on non-working hours and try to avoid that any other application it's processing something that could take lot of CPU load so the backup/restore goes faster.
*For the reasons above pointed is strongly recommended to do this process on non-working hours and try to avoid that any other application is processing something that could take lot of CPU load so the backup/restore goes faster.


*Additionally if you have any custom applications or modifications on your LAP system you need to take care manually the backup and restore of them afterwards (all files and settings you could need) since they will saved/restored.
*Additionally if you have any custom applications or modifications on your LAP system you need to take care manually the backup and restore of them afterwards (all files and settings you could need) since they will saved/restored.
Line 49: Line 49:
==== Restore all configuration/databases and Webdav files ====
==== Restore all configuration/databases and Webdav files ====


Even if the backup of the "Reporting Database" it's still running you can start this process and leave the restore of the Reporting Database for last.
Even if the backup of the "Reporting Database" is still running you can start this process and leave the restore of the Reporting Database for last.


* Copy manually all files and folders from your Backup/Webdav folder from PC to the new Webdav folder of the IPxx11 Linux Application Platform using WinSCP.
* Copy manually all files and folders from your Backup/Webdav folder from PC to the new Webdav folder of the IPxx11 Linux Application Platform using WinSCP.
Line 76: Line 76:
  config change LINUX /kernel Image-IPx11-4.4.0 /cmdline root%3D%2Fdev%2Fsda4 /autostart
  config change LINUX /kernel Image-IPx11-4.4.0 /cmdline root%3D%2Fdev%2Fsda4 /autostart


Also make sure there is no IP conflict, if the goal it's that IPx11 keeps the same IP then you should shutdown the IPxx10 before you restart the IPxx11 after uploading the config.
Also make sure there is no IP conflict, if the goal is that IPx11 keeps the same IP then you should shutdown the IPxx10 before you restart the IPxx11 after uploading the config.


===Known Problems===
===Known Problems===
Line 82: Line 82:
* '''After the migration the History in myPBX will mark all calls as "missed calls" '''
* '''After the migration the History in myPBX will mark all calls as "missed calls" '''


The first time the myPBX runs on the new IPxx11 the Call list retrieved from the Reporting application be list that all previous calls on the Database are marked as "missed calls". This happens because a secondary table it's not saved/restore during the process.
The first time the myPBX runs on the new IPxx11 the Call list retrieved from the Reporting application be list that all previous calls on the Database are marked as "missed calls". This happens because a secondary table is not saved/restore during the process.
To solve it we just need to click on the "Call List" on the myPBX and then the new timestamp will be written in the Database and all old calls will not marked as missed again.
To solve it we just need to click on the "Call List" on the myPBX and then the new timestamp will be written in the Database and all old calls will not marked as missed again.



Revision as of 14:53, 23 June 2016


Applies To

This information applies to

  • innovaphone Linux Application Platform v10
  • innovaphone IPx10 devices that run Linux on CF card
  • innovaphone IPx11 devices that run Linux on SSD disk

More Information

Introduction

This article explains step-by-step how could we migrate an existing innovaphone Linux Application Platform running on an IPx10 (CF Card) hardware to IPx11 (SSD disk) using the mechanism of backup/restore of the Linux Application Platform in an optimize way to be secure and fast process.

Also explains what are the concerns that we should have during this process and what information could be lost with this process and what we can do to avoid that.

Resolution

Concerns before the migration

  • With the backup/restore mechanism no LOGS of any installed application or LAP itself will be saved/restored, so if you wish to keep any Log you should download them all before to a PC but you will not be able to "upload" to the new system.
  • If we have a big database for the Innovaphone Reporting application this process will take longer time depending on the size of the Database itself since there is compressing when doing the backup and decompressing when doing the restore that uses lot of the CPU Load of Linux (75-98%). As for example one compressed Database of 250MB took around 45m to backup and more than 1h to restore.
  • All calls/CDRs received during this process will be "lost" by the reporting application unless:
    • We have Standby-Reporting application running, so when we have the new system running they will sync and the missing CDRs during the update proccess with be retrieved.
    • We set the CDR0/1 Interface to a wrong IP so the CDRs are buffered on the PBX and resent when set again the right IP address of the new IPx11 Gateway (The buffer could be not enough if the amount of CDRs received are too many so the solution of using Standby-Reporting application is more safe).
  • For the reasons above pointed is strongly recommended to do this process on non-working hours and try to avoid that any other application is processing something that could take lot of CPU load so the backup/restore goes faster.
  • Additionally if you have any custom applications or modifications on your LAP system you need to take care manually the backup and restore of them afterwards (all files and settings you could need) since they will saved/restored.

Prepare the new IPxx11 Gateway

We should start by preparing the new IPxx11 that will receive the Linux Application Platform, by installing the LAP and all applications we are running on the current system that we wish to migrate from. It's important that we install the same version of LAP/Applications that are being used, for example if our current system runs v10hf35 we will install v10hf35 on the new IPx11 so the versions match exactly.

Backup all configurations/databases and Webdav files

The next step should be starting backup the system step by step to a "backup" folder in our PC:

  • At Administration->Backup->Save configurations files/data we should save all configurations files (Linux Application Platform and installed applications).
  • Copy manually all files and folders from webdav folder to our PC "backup" folder keeping the same structure(expect folder "System Volume Information") using Webdav client like WinSCP.
  • At Administration->Backup->Save configurations files/data all database files leaving the "Reporting Database" for last since this will be the one that takes more time.
 Migrating an existing LAP System from IPx10(CF) to IPx11(SSD) 1.png

Restore all configuration/databases and Webdav files

Even if the backup of the "Reporting Database" is still running you can start this process and leave the restore of the Reporting Database for last.

  • Copy manually all files and folders from your Backup/Webdav folder from PC to the new Webdav folder of the IPxx11 Linux Application Platform using WinSCP.
  • At Administration->Backup->Restore configuration files/data we should do the restore in the following order one by one:
    • restore innovaphone_cfg_X.X.X.X.tar.gz
    • restore innovaphone_X.X.X.X.gz
    • restore innovaphone-exchange_cfg_X.X.X.X.tar.gz
    • restore innovaphone-exchange_X.X.X.X.gz
    • restore innovaphone-faxserver_cfg_X.X.X.X.tar.gz
    • restore innovaphone-faxserver_X.X.X.X.gz
    • restore innovaphone-reporting_cfg_X.X.X.X.tar.gz
    • restore innovaphone-reporting_X.X.X.X.gz
 Migrating an existing LAP System from IPx10(CF) to IPx11(SSD) 2.png

Move PBX from IPxx10 to IPxx11

In case your IPxx10 device was also your PBX the final step should download the config from the IPxx10 and upload on the IPxx11.

Before we upload we need to change the config line:

config change LINUX /kernel Image-6010-3.4.10 /cmdline root%3D%2Fdev%2Fsda4 /autostart

to:

config change LINUX /kernel Image-IPx11-4.4.0 /cmdline root%3D%2Fdev%2Fsda4 /autostart

Also make sure there is no IP conflict, if the goal is that IPx11 keeps the same IP then you should shutdown the IPxx10 before you restart the IPxx11 after uploading the config.

Known Problems

  • After the migration the History in myPBX will mark all calls as "missed calls"

The first time the myPBX runs on the new IPxx11 the Call list retrieved from the Reporting application be list that all previous calls on the Database are marked as "missed calls". This happens because a secondary table is not saved/restore during the process. To solve it we just need to click on the "Call List" on the myPBX and then the new timestamp will be written in the Database and all old calls will not marked as missed again.

Related Articles

Reference10:Concept_Linux_Application_Platform