Raghavendra Chiyodu’s Post

View profile for Raghavendra Chiyodu, graphic

Db2 LUW Product Engineer, IBM Software Labs Bangalore

Key choices to make when DB2 HADR is setup(DB2 LUW High availability) With HADR, you base the level of protection from potential loss of data on your configuration and topology choices. Some of the key choices that you must make are as follows: What level of synchronization will you use? Standby databases are synchronized with the primary database through log data that is generated on the primary and shipped to the standbys. The standbys constantly roll forward through the logs. You can choose from four different synchronization modes. In order of most to least protection, these are SYNC, NEARSYNC, ASYNC, and SUPERASYNC. Will you use a peer window? The peer window feature specifies that the primary and standby databases are to behave as though they are still in peer state for a configured amount of time if the primary loses the HADR connection in peer state. If primary fails in peer or this "disconnected peer" state, the failover to standby occurs with zero data loss. This feature provides the greatest protection. How many standbys will you deploy? With HADR, you can use up to three standby databases. With multiple standbys, you can achieve both your high availability and disaster recovery objectives with a single technology.

  • No alternative text description for this image
Syed Abrar Ahmed Moinuddin

Immediate Joiner .DB2 LUW Database |Instance and database creation | Database Utilities Reorg, Runstats , Rebuild , Database backup and Recovery , Redirect restore |1x AWS Certified |

7mo

Nice info .

To view or add a comment, sign in

Explore topics