new toys - new problem
we have just invested heavily in 2x E4900 boxes running solaris 9 with emc san storage. Currently we run ids7.31uc7 with solaris7 using veritas clustering, netbackup and vm. We want to migrate to 64 bit ids to take advantage of the extra allocatable memory etc. I have cobbled together a migration plan but would like to run it by all you boffins to see if i have missed anything obvious, or whether there is a better (and ultra safe) way of approaching the task. I intend to: 1. install ids7.31uc7 on new architecture - ensuring dbspaces are identical 2. configure the new box to run as a HDR secondary 3. stop all applications 4. break the hdr pair and take the current live system offline 5. change the mode of the new boxes to primary 6. upgrade the primary to version to 7.31fd? (64 bit) 7 repoint the apps 8. fire it up and pray. I would like to do this without donwtime at all but cannot afford to take ANY risks. All comments (however sarcastic:-) are gratefully received.
"mad_villan" <bryan.purkis@planetfootball.com> wrote in message news:872d93d8.0406010602.750da30@posting.google.com... > we have just invested heavily in 2x E4900 boxes running solaris 9 with > emc san storage. Currently we run ids7.31uc7 with solaris7 using > veritas clustering, netbackup and vm. > We want to migrate to 64 bit ids to take advantage of the extra > allocatable memory etc. I have cobbled together a migration plan but > would like to run it by all you > boffins to see if i have missed anything obvious, or whether there is > a better (and ultra safe) way of approaching the task. I intend to: > > 1. install ids7.31uc7 on new architecture - ensuring dbspaces are > identical > 2. configure the new box to run as a HDR secondary > 3. stop all applications > 4. break the hdr pair and take the current live system offline > 5. change the mode of the new boxes to primary > 6. upgrade the primary to version to 7.31fd? (64 bit) > 7 repoint the apps > 8. fire it up and pray. > > I would like to do this without donwtime at all but cannot afford to > take ANY risks. All comments (however sarcastic:-) are gratefully > received. I'm a bit lost as to the significance of TWO new boxes. Is one a test box: thus your question is just how to get ONE of them up-and-running as the live server? Personally, I'd use a consultancy expert in IDS, EMC and mission-critical systems who's got the medals and done it before. Like mine. :-) However, going it alone, a couple of alternatives suggest themselves: 1. Using Timefinder to take a BCV copy of your current live disks (are they on the same Symmetrix: if not go to Option 2?), making these available to the new box, doing the upgrade on the new box, when you're satisfied moving the now-live BCVs to a different Timefinder group then restoring to Primaries and running your live service off this. Benefits: Easy back-out. Drawbacks: lots of Timefinder work, plus a less-than-ideal time when you're running a live service off BCVs (but you can OS mirror them). 2. Using Informix mirroring to make duplicates of your primary chunks onto EMC disk. Shut down Informix. Make the mirrors available to the new box and point your IDS chunk links to them AS IF THEY WERE PRIMARIES. Up comes IDS but of course it bitches about the missing mirrors. Create new mirror chunks on the EMC disk, mark the chunks as "up", mirroring will be re-established. Drop the mirrors. Benefits: We've done it a million times; it's so beautifully elegant it makes me cry; downtime of a couple of minutes if you plan it properly; instant backout Drawbacks: None. I haven't commented on your plan because I rarely use HDR these days - nearly always do mirroring at the SAN or failing that OS level. It seems to be more complex and risky than option 2 above. cheers -- Neil Truby t:01932 724027 Director m:07798 811708 Ardenta Limited e:neil.truby@ardenta.com