Migrating workgroup to enterprise

Hi I just need a quick advise. The client running a instance using IBM INformix workgroup 12.10.FC6WE on RedHat Linux 7.5 VM. All instances are in cluster (Pri,Sec & Rss). With the new direction and new maintenance, they want to upgrade to Informix IBM Enterprise. My question, from the current Pri instance , can I used the level 0 backup and do physical restore on a new VM that will be setup Informix Enterprise 12.10.xx (latest version). By right I can do my own testing but since for enterprise it is difficult to get trial version, that is why I ask to get an input advise. It also important to plan for the mandays either to do plysical restore or doing dbexport n import. Regards ------------------------------ ABeMie ------------------------------ #Informix

Backup and esp. Restore doesn't care about edition (workgroup or enterprise), yet what it cares about is version. And there's a pretty siginificant version change between xC6 and latest 12.10 (xC15), involving a conversion of some disk structures too, so I'd assume the xC15 restore would even refuse to accept an xC6 backup. -> do the upgrade first, to xC15 (no matter what edition), then do whatever's required to move to new VM (if storage is good enough and can be moved, they might even save backup/restore). HTH, Andreas ------------------------------ Andreas Legner ------------------------------

Hi, It is important to backup and restore using the same version of Informix. Edition is not important. A backup using workgroup can be used during a restore with an enterprise. However, backup with version 12.10.xC3 for example will not work if you restore using 12.10.xc12 or 14.10.xc7 using the same edition. You need to perform a version migration first before changing editions; there can be exceptions between versions if the version change is not considered a migration (no important changes in the new version: sometimes there are only some very small corrections). In your case, you need to perform a version migration first, then an edition change. -- Cordialement, Regards, Khaled Bentebal Directeur G??n??ral - ConsultiX T??l: 33 (0) 1 39 12 18 00 Mobile: 33 (0) 6 07 78 41 97 Email: khaled.bentebal@consult-ix.fr Site Web: www.consult-ix.fr

I might consider doing your install and migration in the other order, install 12.10.FC6 Enterprise (assuming it's still available on PPA) on the new server and do your restore, then do the upgrade to 12.10.Fxx there. That way if the upgrade goes haywire, you still have your operational workgroup server. Admittedly, to risk is pretty low, but I'm pretty paranoid about creating extra down time. For what it's worth, you could even do a test run or two, assuming you did the software installs in separate directories. --EEM

Hi Andreas Thanks for your input. By the given approach , look like I have to touch the PRI production. 1. If I have to upgrade the version first, mean I have to install Informix workgroup 12.10.xC15 (or any latest) in seperate folder : a. I have to create a new folder 12.10.FC15 for example and install 12.10.FC15 informix product b. Then copy the existing onconfig, sqlhost and other critical files from 12.10.FC6 folder into 12.10.FC15 folder. c. Restart the instance under 12.10.FC15. d. Take level 0 backup 2. IN the new VM, install Informix enterprise 12.10.xC15 a. copy onconfig,sqlhosts n other critical files from workgroup 12.10.FC15 done at 1(b) . b. do physical restore using backup 1(d). d. Once complete, initiate the new VM as std (standalone) e. INitiate as new Primary f, Take level 0 3. INside new Sec & Rss server vm, do installatoon of INformix enterprise 12.10.xc15 a. Setup Secondary & Rss server vm using onconfig ,sql hosts from Primary b. Restore physical level 0 to setup new Secondary & Rss bm server 4. Is dbexport / dbimport recommended for mirating ? --- i mean dbexport from Workgroup informix 12.10.FC6 and dbimport in new instance 12.10.FC15. Regards ------------------------------ ABeMie ------------------------------

You do not perform a dbexport/dbimport to migrate unless you want to. Exporting locks the database and might be long depending ominous the size of the database. Dbexport defeats the above steps and the purpose of the subject of this thread of discussion. You either perform migration from one version to another ( takes few minutes); conversion of the header pages and can even go backwards. Remember that this can only be done if you are on the same server( in place migration). If you want to move to a different server with a different OS for example, you need to go another route( dbexport/ dbimport, external tables, copy of tables from one instance to another, ER, etc). The downtime can be substantial depending on the size of the data migrated. For what you are requesting, an in place migration is the way to go. Khaled Bentebal de mon portable