HDR Configuration
Posted in 2017
Topics: High Availability & Replication, Performance & Tuning
Hi Friends, After a lot of study and IIUG members help, we are ready to implement HDR in production environment. But I need your help to get move forward to successfully implement HDR without any issues. Which is the best approach to get high performance and without any data loss or miss-match in between db servers: Asynchronous or Synchronous Mode ? NEAR_SYNC or FULL_SYNC ? Buffered logging or Unbuffered logging? Little confused please anyone clear me on this. Thank you.
Id go buffered logging with NEAR_SYNC. Why/ The only thing that really needs to be flushed to disk or transmitted to the remote server is the commit log record. By going buffered logging, then you dont have to wait for a log buffer flush when a larger transaction is being run. And by going near sync, then you will cause a flush of the log buffer only with the commit and also will only complete the commit once the commit log buffer has been transmitted to the secondary server. Sent from Yahoo Mail for iPad On Saturday, November 4, 2017, 8:52 AM, MUKESH TANUKU <mukeshbt1328@gmail.com> wrote: Hi Friends, After a lot of study and IIUG members help, we are ready to implement HDR in production environment. But I need your help to get move forward to successfully implement HDR without any issues. Which is the best approach to get high performance and without any data loss or miss-match in between db servers: Asynchronous or Synchronous Mode ? NEAR_SYNC or FULL_SYNC ? Buffered logging or Unbuffered logging? Little confused please anyone clear me on this. Thank you. ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.
Thanks for prompt response. I will go with this configuratons