Quick Recovery
Shahzad Salam Kasi (IDS 11.50.FC6/FC7, Solaris) asked how to ensure quick recovery and how to keep an HDR/RSS secondary 10-20 minutes behind the primary. Madison Pruet said RSS has delayed apply and stop apply, with logs staged on the RSS and applied once the delay ends. Art Kagel said to set the DELAY_APPLY parameter in the secondary's ONCONFIG. Quick-recovery question not specifically answered.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
HI, How can we ensure quick recovery using Level-0 (or using snapshot backup) for any Instance. Also, how the performance of HDR/RSS improved if we have a huge transaction volume at Primary Instance ? Means, Is there any way to keep RSS / HDR behind Primary Instance (say for 10-20 min's) ? We are using IDS 11.50.FC6 & IDS 11.50.FC7 for Solaris Sparc. Thanks.
RSS has 'delayed apply' and 'stop apply'. This would prevent the RSS node from apply log records from the primary. M.Pruet From: "SHAHZAD SALAM KASI" <skasi@i2cinc.com> To: ids@iiug.org Date: 04/26/2011 03:54 PM Subject: Quick Recovery [23497] Sent by: ids-bounces@iiug.org HI, How can we ensure quick recovery using Level-0 (or using snapshot backup) for any Instance. Also, how the performance of HDR/RSS improved if we have a huge transaction volume at Primary Instance ? Means, Is there any way to keep RSS / HDR behind Primary Instance (say for 10-20 min's) ? We are using IDS 11.50.FC6 & IDS 11.50.FC7 for Solaris Sparc. Thanks. ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.
Thanks for the info. If we enable STOP_APPLY, then how we need to keep RSS active (even behind primary) ? Do we need to apply logs (manually) ? Thanks.
When using either STOP APPLY or DELAY APPLY, we save the logs on the RSS in a log staging directory. If using delayed apply, we will continue to apply the logs, but only after the delay. When you turn off stop apply or delayed apply, then the RSS node catches up by applying the logs from the staging directory. Once it has caught up, it switches back to normal processing. From: "SHAHZAD SALAM KASI" <skasi@i2cinc.com> To: ids@iiug.org Date: 04/26/2011 04:52 PM Subject: Re: Quick Recovery [23500] Sent by: ids-bounces@iiug.org Thanks for the info. If we enable STOP_APPLY, then how we need to keep RSS active (even behind primary) ? Do we need to apply logs (manually) ? Thanks. ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.
RSS Secondaries can be programmed to stay N days, hours, minutes, or seconds behind the primary, yes. Set the DELAY_APPLY environment variable in the secondary's ONCONFIG file. 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 Tue, Apr 26, 2011 at 4:53 PM, SHAHZAD SALAM KASI <skasi@i2cinc.com>wrote: > HI, > How can we ensure quick recovery using Level-0 (or using snapshot backup) > for > any Instance. > > Also, how the performance of HDR/RSS improved if we have a huge transaction > volume at Primary Instance ? Means, > > Is there any way to keep RSS / HDR behind Primary Instance (say for 10-20 > min's) ? > > We are using IDS 11.50.FC6 & IDS 11.50.FC7 for Solaris Sparc. > > Thanks. > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --002354188810edf56304a1e89c76