Re: Rootdb

Stripping on 5 engine was not a bad idea. If you are performing regular archives not having mirror is not really all that bad, yet depends on how critical you and your managment consider the data. Also how much down time you can afford while a restore is occuring! If you are going to 7.X I suggest at least a 4CPU machine. You may want to also consider fragmentation if you have very large tables (I think 1GB or more). If you have to recreate your dbspace due to readjustment of your logical volumes then you are going to have to do an tbunload/tbload. A Level 0 restore will not work if: DBSAPCES are not same name and same size! IF PATH names are not the same for each chunk! If you are fortunate enough to have another machine to install 7 this could be easy. Yet if you only have one machine and limited time. I say GOODLUCK because you've got your work cut out for you! Which every direction you choose, I would be interested in hearing your results! ------------------------------------------------------------------------- Cheryl Kendricks Internet:cherylk@prod1.jcdc.doleta.gov OR cherylk@gwysmtp.jcdc.doleta.gov DTSI, Inc. Voice: 1-800-598-5008 Fax: 512-393-7296 Database Administrator - DOL Job Corps San Marcos, Texas ------------------------------------------------------------------------ On Mon, 3 Jun 1996, Devkant N. Kulkarni wrote: } Dear Informix Gurus!!!! } } Some time ago we had hired a HP consultant to configure our HP9000/I50 } model to run elite/computron. I have since found that he as left us a } big mess...for starters he has not mirrored rootdb, and the logical } volume was created across 16 physical volumes (Yes! that's correct). } I wanted to mirror rootdb but we cannot add anymore disk to the Volume } Group since he has also selected the default 16 Physical Volumes per } VG. I could and have reduced one of the other LV to get 400mb (that } is the size of rootdb). But when I go to mirror it I have to specify } non-strict mirroring (i.e. on the same disk since it is across all 16 } disks) I was able to mirror the rootdb across two disks by specifying } lvextend -m 1 /dev/vg02/rootdb /dev/dsk/c18d0s2 /dev/dsk/c19d0s2. } This as you know is not a good idea to mirror LV on same disks. I } would like to move and/or create a rootdb LV on a separate VG and then } link it....I understand I have to do a restore....any suggestions how } to go about doing this....I would realy appreciate it. } } Also we are currently running Informix 5.05 and would like to move on } to the 7.xx. Is there any advantage or disadvantage with a single } cpu. There is 256mb of RAM. } Ask as many questions, you may find the answer. } } e-mail: dkulkarn@ix.netcom.com } } }