<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><tt>The "4 consecutive migrations" idea would work as follows:</tt></p>
<p><tt>cd /tmp</tt><tt><br>
</tt><tt>git clone </tt><tt><a class="moz-txt-link-freetext"
href="https://github.com/OpenSIPS/opensips.git">https://github.com/OpenSIPS/opensips.git</a></tt><tt>
</tt><tt>opensips<br>
</tt><tt>cd opensips</tt><tt><br>
</tt><tt>git checkout 2.1</tt><tt><br>
</tt><tt>scripts/opensipsdbctl migrate opensips opensips_2_1</tt><br>
<tt><tt>git checkout 2.2</tt><tt><br>
</tt><tt>scripts/opensipsdbctl migrate opensips_2_1 opensips_2_2<br>
</tt></tt><tt>git checkout 2.3</tt><tt><br>
</tt><tt>scripts/opensipsdbctl migrate opensips_2_2 opensips_2_3<br>
</tt><tt>git checkout 2.4</tt><tt><br>
</tt><tt>scripts/opensipsdbctl migrate opensips_2_3 opensips_2_4</tt></p>
<p><tt>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.<br>
</tt></p>
<p><tt>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:<br>
</tt></p>
<p><tt>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;</tt></p>
<p><tt>... 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.<br>
</tt></p>
<p><tt>Best regards,<br>
</tt></p>
<pre class="moz-signature" cols="72">Liviu Chircu
OpenSIPS Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
<div class="moz-cite-prefix">On 16.10.2018 11:21, Michele Pinassi
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:086c4ed2-ba6e-f9c6-e05d-4163d812f0ae@unisi.it">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<p>Hi Liviu,</p>
<p>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.</p>
<p>Best regards,<br>
</p>
<p>Michele<br>
</p>
<div class="moz-cite-prefix">On 16/10/18 10:06, Liviu Chircu
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:5af01de0-6632-a6db-7b6a-539eefc9aa5a@opensips.org">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
<p><tt>Hi Michele,</tt></p>
<p><tt>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?</tt></p>
<p><tt>Best regards,</tt><br>
</p>
<pre class="moz-signature" cols="72">Liviu Chircu
OpenSIPS Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com" moz-do-not-send="true">http://www.opensips-solutions.com</a></pre>
<div class="moz-cite-prefix">On 16.10.2018 10:13, Michele
Pinassi wrote:<br>
</div>
<blockquote type="cite"
cite="mid:f1fa29f3-98b2-97d2-1f7e-941574847900@unisi.it">
<pre wrap="">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
<a class="moz-txt-link-freetext" href="https://www.opensips.org/Documentation/Migration" moz-do-not-send="true">https://www.opensips.org/Documentation/Migration</a> 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
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org" moz-do-not-send="true">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" moz-do-not-send="true">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org" moz-do-not-send="true">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" moz-do-not-send="true">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
Michele Pinassi
Responsabile Telefonia di Ateneo
Ufficio Esercizio e tecnologie - Università degli Studi di Siena
tel: 0577.(23)5000 - <a class="moz-txt-link-abbreviated" href="mailto:helpdesk@unisi.it" moz-do-not-send="true">helpdesk@unisi.it</a>
Per trovare una soluzione rapida ai tuoi problemi tecnici consulta le FAQ di Ateneo, <a class="moz-txt-link-freetext" href="http://www.faq.unisi.it" moz-do-not-send="true">http://www.faq.unisi.it</a> </pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</body>
</html>