Windows Clustering and HADR split brain issue

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • jasonscerri
    New Member
    • Apr 2015
    • 1

    Windows Clustering and HADR split brain issue

    Hello,

    I have a question regarding Db2 Windows Clustering and HADR.

    Our scenario is the following. We were planning to have to data centers with bot having a set of servers in case of a total data center disaster.

    In the first (lets call it primary) location. We were planning to have a couple of DB2 servers using windows clustering ( 1 active, 1 standby) sharing a SAN drive. This will allow us to have almost instant failover in case something happens to the VM or Db2 engine. So in this case Db2 needs to have Autorestart set to ON otherwise it wouldn't restart automatically on the standby node.

    We were planning to use HADR to ship logs to another datacenter having again a database on windows clustering as well.

    So my question is the following. If the primary datacenter site fails and we force a takeover on the secondary site ( standby HADR db becomes primary) what actions should we take once we repair the original primary servers in the first data center. Since Autorestart is set to on I assume that the database will start automatically and HADR set to primary again, which is one thing I want to avoid (split brain issue)

    Is there a way to avoid this using this scenario?

    Any answers would be greatly appreciated.
Working...