rootdbs mirror

Hello, We are running Informix 11.50.FC4 on HPUX 11.23. The instance was initialized without the rootdbs mirrored. Can I use onspaces -m to add a mirror chunk for rootdbs and other critical dbspaces after instance initialization? I seem to remember in older releases you needed to add mirroring at initialization or you were out of luck. Thanks for your help! Mike

If you have MIRROR set to '1' you are all set. Otherwise change it in the ONCONFIG file and bounce the instance. Then you will be able to add a mirror to any dbspace. If you have to option of using hardware mirrored storage instead, that is better as it is easier to manage and faster, but Informix level mirroring is fine if you do not. Art Art S. Kagel Advanced DataTools (www.advancedatatools.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 my employer, Advanced DataTools, 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. On Wed, May 25, 2011 at 1:21 PM, MICHAEL FAVOLE <mike.favole@ngc.com> wrote: > Hello, > > We are running Informix 11.50.FC4 on HPUX 11.23. The instance was > initialized > without the rootdbs mirrored. Can I use onspaces -m to add a mirror chunk > for > rootdbs and other critical dbspaces after instance initialization? I seem > to > remember in older releases you needed to add mirroring at initialization or > you were out of luck. > > Thanks for your help! > Mike > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --bcaec51a7d4c12dab304a41d2424

Thanks Art, that answers my question. We are looking to migrate our data from an older NetApp appliance to a newer larger one and one idea was to mirror all the dbspaces to the new appliance then bring down the primary chunks on the old appliance, recreate the primary spaces on the new appliance, bring the spaces online so the primary chunks are recovered, then drop the mirror. The end result should be a migrated database with Informix doing the heavy lifting. Any thoughts on this scenario? Thanks again. Mike

That would work. Other ideas: You could also take an external archive (ie onmode -c block) to copy the chunks (using dd, rcp, or a SAN level copy if the storage units are compatible at that level) if you can keep the checkpoint block long enough without disrupting operations. Then you will just have to do a logical log restore when you bring down the original server, relink the chunks to the new storage, and bring up the new one. Hmm, you could also use the same mirror trick using NetApp facilities or your storage manager, no? That would be more tan a little faster than Informix mirror. Art Art S. Kagel Advanced DataTools (www.advancedatatools.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 my employer, Advanced DataTools, 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. On Wed, May 25, 2011 at 1:52 PM, MICHAEL FAVOLE <mike.favole@ngc.com> wrote: > Thanks Art, that answers my question. > > We are looking to migrate our data from an older NetApp appliance to a > newer > larger one and one idea was to mirror all the dbspaces to the new appliance > then bring down the primary chunks on the old appliance, recreate the > primary > spaces on the new appliance, bring the spaces online so the primary chunks > are > recovered, then drop the mirror. The end result should be a migrated > database > with Informix doing the heavy lifting. Any thoughts on this scenario? > > Thanks again. > Mike > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --bcaec548a6db4d446904a41f11f8