Migration from 1.2.3 to current? Possible?
Submitted by mlewis on Thu, 04/24/2008 - 1:25pm.
The simplest answer although
Fri, 04/25/2008 - 9:09am
The simplest answer although probably not one you will be pleased with, write down or print all all of you configurations, do a fresh install with the most recent stable code and reconfigure the new box from scratch. You will spend much less time this way than trying to make any upgrade process work and trying to work out all the issues. There are just way too many differences in all the versions of primary and supplementary applications to have a clean upgrade. My two cents.
I had found this
Fri, 04/25/2008 - 10:30am
I had found this earlier,
http://www.trixbox.org/forums/trixbox-forums/open-discussion/here...
Any thoughts on going this route or reconfiguring as you're suggesting above? Can't hurt to try both I guess since it'll be a new install.
Mike
Migration between versions?
Fri, 04/25/2008 - 1:51pm
For me the difficulty of migrating between major revisions is a real drawback of trixbox. I have one office that has been running V1.1 very happily for a long time (> 18months) and my own office system is V2.0. The time has come to move both of these to a current version and I can't find any easy way.
Part of the problem is that there does not seem to be a good tool that will allow you to print the config of the whole system. There is no option to dump the config to text file. By the time you have added a number of trunks, a ring group or two, two levels of IVR with time conditions a variety of extensions etc there is quite a lot to print and the data is in various places.
That is why I got involved in the thread on trixboxgraph over the last couple of weeks. trixboxgraph prints out the structure of the system but not the configs. At least you can see how the system components link together.
The problem is that the differences in structure between versions (mysql tables, config files in /etc/asterisk, etc) are not documented. Without that info you really only have the option pointed out by James of rebuilding a new version from scratch.
If you end up in the same place, it doesn't matter how you get
Fri, 04/25/2008 - 8:09pm
there - If you have a critical production machine, the real question is what are you upgrading for? If it's just to be current, you are wasting your time (and not doing your customer any favors) - however, if you need a function that your version doesn't have, figure out if it's a FreePBX feature or a Trixbox feature - FreePBX upgrades are very simple and almost foolproof.
If it's a Trixbox feature that you need, and you have a machine that can't be down (even over a weekend or testing period) then get another machine, do a clean load, and then you can get a machine with Dual Screens (or a WIDE screeen) and basically clone the machine. Then you can test the new machine before you put it into production.
The procedure I wrote works pretty well, but is REALLY dependent on the implementer, and where you start from - if your box is already messed up, updating it will probably not make it any better...
Greg
The current box is not
Fri, 04/25/2008 - 9:13pm
The current box is not messed up, other than being old, 1.2.3. I have another thread going about the networking issues I have as well but one main reason is that TB was installed on a common PC, never expecting it to become production. It needs to be moved over to a server class machine for various reasons including faster capabilities because we will soon be putting a lot more load on it.
All these things aside, the fact is, it needs to be moved to a new server. One other issue I'll have is that I need to keep the same IP's once everything is said and done so I'll need to build it, test it then put it into production. Not sure how I'll do this part yet since the PRI lines are sitting on a MAX TNT which also needs to talk with TB. It'll be fun but I'll get on this tomorrow.
Mike
Member Since:
2006-12-18