The "4 consecutive migrations" idea would work as follows:
cd /tmp
git clone https://github.com/OpenSIPS/opensips.gitopensips
cd opensips
git checkout 2.1
scripts/opensipsdbctl migrate opensips opensips_2_1
git checkout 2.2
scripts/opensipsdbctl migrate opensips_2_1 opensips_2_2
git checkout 2.3
scripts/opensipsdbctl migrate opensips_2_2 opensips_2_3
git checkout 2.4
scripts/opensipsdbctl migrate opensips_2_3 opensips_2_4
This should port all your data -- a method which I recommend. If you
need to edit the DB access credentials, edit the scripts/opensipsctlrc file.
Doing the migration manually is also a decent option, as I assume you
don't have that many tables which require provisioning (3 - 6 tables?).
You could view all current data in your 1.11 DB with something like:
SELECT TABLE_NAME, ENGINE, TABLE_ROWS, DATA_LENGTH, MAX_DATA_LENGTH FROM
information_schema.tables WHERE TABLE_SCHEMA="opensips_1_11" ORDER BY
TABLE_ROWS DESC;
... and go from there, building statements which resemble "INSERT INTO
new_db(x,y,z,...) SELECT a,b,c,... FROM old_db" in order to migrate
each old table which had data in it.
Best regards,
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com
On 16.10.2018 11:21, Michele Pinassi wrote:
Hi Liviu,
my plan is to use a completely separate new server where to build new
2.4 system while older is still running. After a successfull upgrade,
move the new server to production and shut down the old one. So
volatile data should not be a problem because i can start with a fresh
(empty) table.
Best regards,
Michele
On 16/10/18 10:06, Liviu Chircu wrote:
Hi Michele,
Before going deeper: what is your plan with regards to volatile DB
data (dialogs, contacts, presence, etc.) on this server? Can it be
discarded, possibly during some maintenance window?
Best regards,
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com
On 16.10.2018 10:13, Michele Pinassi wrote:
Hi all,
maybe a trivial question but i'm planning to upgrade my production
OpenSIPS server from latest 1.11 (1.11.11) to latest state and
production-ready 2.4 release.
Obviously i have to make some minor changes to dialplan. No worry about
this. But i'm quite scared about database migration. I'm still thinking
to do (after a backup, of course) a step-by-step migration, following
https://www.opensips.org/Documentation/Migration procedures, so moving
from 1.11 to 2.1, then from 2.1 to 2.2 and so on, until i reach 2.4.
That's the best way or there is another, better, way ?
Thanks for any hint :-)
Michele
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
--
Michele Pinassi
Responsabile Telefonia di Ateneo
Ufficio Esercizio e tecnologie - Università degli Studi di Siena
tel: 0577.(23)5000 [email protected]
Per trovare una soluzione rapida ai tuoi problemi tecnici consulta le FAQ di Ateneo,http://www.faq.unisi.it
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
