Best pratice to move IDS and upgrade?

Hello, i´d like to know the best pratice you can advisory for the following case: - Informix 12.10 Growth Edition Linux 64bit - Cooked files (~60) in sum 1.2TB - 90 DBs whats the best way to migrate everything to a new Server with Informix 14.10 (latest xC) and Keep all data? Option 1 - backup cooked files and Startup on new Server with 14.10 ? Further suggested Options? Thank you! ------------------------------ Marc Demhartner ------------------------------ #Informix

Cdr migrate server

I confirm, CDR migrate, sitting on the 14.10 side Eric Vercelletto Data Management Architect and Owner / Begooden IT Consulting Board of Directors, International Informix Users group IBM Champion 2013,2014,2015,2016,2017,2018,2019,2020 Tel: +33(0) 298 51 3210 Mob : +33(0)626 52 50 68 skype: begooden-it Google Hangout: eric.vercelletto@begooden-it.com Email: eric.vercelletto@begooden-it.com www : http://www.vercelletto.com www https://kandooerp.org

Hmmm, 90 databases, maybe differing codesets (DB_LOCALE), I'd be a little careful with 'cdr migrate server'. Is downtime a concern, or can this system be down for a day or night for the move? Also: can we assume Linux for the new server as well? How about upgrading to 14.10 first, then cloning the system to the new server using ifxclone (which is disk-less backup-and-restore under the hood) ? This way the original system only had to go down for the migration and then could stay on-line for the duration of the clone operation and even beyond that, with the clone being updated with all changes. (Pre-requesite: no blobspaces (or no new blob activity at least), all databases logged, ...) If the old system can be down for the move, you could even copy the chunks physically over to the new system and simply start it there with new version. Quite a few (more) choices, all with their preconditions and restrictions, so more would have to be known. ------------------------------ Andreas Legner ------------------------------

To me it depends on several factors, so here is what I discuss with my clients considering a major upgrade: Can you afford downtime? If so how much? - inline upgrade will mean a downtime of up to 10 mins (usually less, but with 90 databases...). Are there any infrastructure issues you would like to address in addition to the upgrade ie Restructuring storage (more, fewer, different dbspaces, moving databases/tables to different storage, moving logs, indexes, etc.) Defragmenting the tablespaces in your dbspaces. Defragmenting tables. Repartitioning tables/indexes. Change codeset for a database. New physical machine? If so: Same hardware or OS? Different hardware or OS? Art Art S. Kagel, President and Principal Consultant ASK Database Management www.askdbmgt.com Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves.

Source O/S and page size, target O/S and page size ? Scott Pickett IBM Informix WW Technical Sales IBM Informix WW Cloud Technical Sales IBM Informix WW Cloud Technical Sales ICIAE IBM Informix WW Informix Warehouse Accelerator Sales Boston, Massachusetts USA spickett@us.ibm.com 617-899-7549 33 Years Informix User The Informix Roadshow page is here: https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en_US#/wiki/Informix%20Roadshow%20-%20Informix%20is%20Everywhere Shortcut to the Informix Roadshow Page: http://bit.ly/ifmx_roadshow All presentations and the agenda used by the Roadshow can be found there. The current ZACS Informix Page can be found here: https://w3-connections.ibm.com/wikis/home?lang=en#!/wiki/Wf58c4c538dbf_45b4_b7a7_5003d0ceb79b/page/Informix The older Internal IMAZ CTP Informix Main Page can be found here: https://w3-connections.ibm.com/wikis/home?lang=en-us#!/wiki/Info%20Mgmt%20Client%20Technical%20Professional%20Resources%20Wiki/page/Informix Website for Internet Of Things https://www.ibm.com/internet-of-things/ Website for Informix https://www.ibm.com/analytics/us/en/technology/informix/

all DBs hase the same DB_LOCALE - we will setup the other server much earlier. Also Linux RHEL8. I was also thinking about moveing all chunks - as they need to be "SCP´ed" via network to the new server, and i noticed there can be compressed very well by pbzip2 - are there any disadavantages if we do it this way? Shutdown 12.10 old installation, compress and move all chunk files to new server and startup 14.10 with these chunks? ------------------------------ Marc Demhartner ------------------------------

RHEL 7 - 4K ->> RHEL 8 also 4K ------------------------------ Marc Demhartner ------------------------------

You can compress on the fly with scp scp -c blowfish your_file user@remote:/location cheers j.

If you can take the outage then nothing wrong with approach. But using ontape –s | ssh newserver ontape –r is probably quicker Cheers Paul

You can do this better with ifxclone. You can even have ifxclone create the new server as an ER replicant as long as every table has a primary or unique key or a unique index and every database is logged. Then the new server will be in sync with the old one until you are ready to flip to the new one. You could even reverse the replication so the older server is kept in sync with the new one for a while in case you run into any undiscovered issues on the new server and have to fall back. FWIW, Informix running on Linux on Intel has 2K pages not 4K (the OS pages are 4K, but not server pages). Art Art S. Kagel, President and Principal Consultant ASK Database Management www.askdbmgt.com Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves.