Production and Testing Database Merge

[scottgutman]

I was wondering if there is a good method for combining a test database and a production database.

I have a vicidial 2.0.4 server that I am replacing with 2.0.5 server. For testing purposes, I have made a copy of the 2.0.4 database, upgraded it to 2.0.5 and am using it to test the new server.

I have made alot of technical changes. And, I worry that if I miss one setting, that the center will be down until I figure out that I forgot an 'o' or some other nuance.

Is it possible replace tables (after upgrading) from the production server to the new server and have it run correctly? If so which tables? Does anyone have a procedure for this? Or am I crazy?

[lerroux]

I was wondering if there is a good method for combining a test database and a production database.

I have a vicidial 2.0.4 server that I am replacing with 2.0.5 server. For testing purposes, I have made a copy of the 2.0.4 database, upgraded it to 2.0.5 and am using it to test the new server.

I have made alot of technical changes. And, I worry that if I miss one setting, that the center will be down until I figure out that I forgot an 'o' or some other nuance.

Is it possible replace tables (after upgrading) from the production server to the new server and have it run correctly? If so which tables? Does anyone have a procedure for this? Or am I crazy?

i suggest that before you merge the databases, you keep a running and ready copy of every little bit of configuration in your system. not just the database but, the dialplan, scripts and everything. so that when you do the merge and something goes wrong, you can switch readily to your backup and have the center running with lesser downtime. i dont think you'll have problems if your just planning to merge the database since the other one is a copy of the old one. just with some mods maybe. and also, try to schedule the merge when the center is not running to prevent any unforseen actions being made by the users. give it a whole weekend or holiday perhaps. so that you'll have time to prepare. DONT FORGET TO DOCUMENT EVERYTHING, for your own reference later on. sometimes, big troubles can be resolved with just a simple documentation of everything you have, every action you do.

cheers,

[scottgutman]

ok, got it. Make copies of all files and document all settings.

Now, How do I do the merge?

Should I drop some tables from one, and then load those table from the other database? Which tables would I need?

Is there another way?

[lerroux]

i'd suggest you look at the difference in between the two servers. and then try the mysql backup and restore function.

im sure, you'll find it easy to do. plus support is always available at the mysql forums.