Re: question about mach11 capabilities
Floyd Wellershaus wrote: > Thanks Art, > I figured it had to be ER, but wasn't sure how it would work. So basically > I would have to reorg each ER server ( or er group ) separately and let it > catch back up. > > Lots of work on a weekend type reorg, but at least no downtime. :-)) > Nice thing about no down time is that you can spread the reorg across multiple weekends. :-) Art S. Kagel Oninit > Thanks. > > ----- Original Message ----- > Subject: Re: question about mach11 capabilities > Date: Wed, March 5, 2008 10:12 > From: "Art S. Kagel (Oninit)" <art@oninit.com> > Floyd Wellershaus wrote: > >>> Hi, >>> I was just reading the white paper on ids11 availability and have a >>> question. >>> The solutions seem explicitly cover every scenario except one. >>> If I need to reorg a very large table that the application needs, but >>> I don't want to take any outages. >>> >>> Can anyone tell me ( high level ) how that would work ? >>> >> Only doable using ER really. With that you would shift all users away >> from the one (or the few) machine(s) that you want to reorg, stop >> replication to that server, reorg the table, restart replication and let >> it catch up. That done you can shift users around again and reorg >> another ER node. If you are mixing ER and other MACH11 solutions, you >> can reorg a block of HDR, RSS, & SDSS servers together if you have >> multiple such machine clusters kep in synch using ER. >> >> If you want to eliminate maintenance windows and eliminate downtime >> altogether ER's the way to go, or ER in combination with other options >> to maximize data security/safety. >> >> Art S. Kagel >> Oninit >> >> >>> Thanks, >>> floyd >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Informix-list mailing list >>> Informix-list@iiug.org >>> http://www.iiug.org/mailman/listinfo/informix-list >>> >>> >> >> =========================================================================================== >> Please access the attached hyperlink for an important electronic >> > communications > >> disclaimer: >> >> http://www.oninit.com/home/disclaimer.php >> >> =========================================================================================== >> >> >> > > =========================================================================================== > Please access the attached hyperlink for an important electronic communications disclaimer: > > http://www.oninit.com/home/disclaimer.php > > =========================================================================================== > > > =========================================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.oninit.com/home/disclaimer.php ===========================================================================================