Architecting High-Availability and Disaster Recovery Solutions with DB2

You may also like...

6 Responses

  1. Luke Numrych says:

    Ember – great article! You are explaining the difference between HA and DR and the technologies appropriate for use to implement the solutions very clearly.

    If I may, I would like to share a thought on using HADR with Read-on-Standby. It seems like a very simple way for implementing a read-only database instance (for example to handle analytical workloads). However, one has to be aware of the effects of replay-only window (see https://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.1.0/com.ibm.db2.luw.admin.ha.doc/doc/c0056190.html?lang=en for all the events that may trigger it) on applications accessing the read-only standby. A replay-only window forces all of the applications connected to the read-on standby database, so a high-frequency of triggering events will become very disruptive to the applications that are trying to use it.

  2. Peter Prib says:

    Often wonder why there is little mention of implementing active-active db2 by using q replication.

    • Ember Crooks says:

      I have heard it is a bit difficult to deal with conflicts and to maintain. I’d love to hear others’ experiences with it if you’ve actually used it.

  1. July 15, 2015

    […] Architecting High-Availability and Disaster Recovery Solutions with DB2 […]

  2. January 12, 2016

    […] presentation from Dale McInnis on High Availability (HA) and Disaster Recovery (DR), Ember wrote an excellent article on what each means. Her article gives you a starting point to help the client define exactly what […]

Leave a Reply

Your email address will not be published. Required fields are marked *