Up over 370 days Straight and going, 7.2 Billion Transactions
This is an example of what a properly configured and monitored DB2 LUW HADR implementation can provide. In this example, this two database instance running HADR in superasync mode to one standby server has been up over 370 days without an outage, with reports running against the standby databases in read only mode. Get started with DB2 today and see what you can achieve!
Database Partition 0 — Database FLW — Active — Up 375 days 01:28:32 — Date 2015-11-29-13.06.33.282000
HADR Information:
Role State SyncMode HeartBeatsMissed LogGapRunAvg (bytes)
Primary RemoteCatchup SuperAsync 0 57371
ConnectStatus ConnectTime Timeout
Connected Thu Nov 05 13:30:59 2015 (1446748259) 120
LocalHost LocalService
10.221.37.1 db2h_DB2_1
RemoteHost RemoteService RemoteInstance
10.221.37.2 db2h_DB2_2 DB2
PrimaryFile PrimaryPg PrimaryLSN
S0405097.LOG 7153 0x000052083D8E94C3
StandByFile StandByPg StandByLSN
S0405097.LOG 7022 0x000052083D8663A2
Database Partition 0 — Database LARG — Active — Up 375 days 01:04:01 — Date 2015-11-29-13.06.34.077000
HADR Information:
Role State SyncMode HeartBeatsMissed LogGapRunAvg (bytes)
Primary RemoteCatchup SuperAsync 0 279
ConnectStatus ConnectTime Timeout
Connected Wed Oct 07 09:33:41 2015 (1444224821) 120
LocalHost LocalService
10.221.37.1 db2h_DB2_3
RemoteHost RemoteService RemoteInstance
10.221.37.2 db2h_DB2_4 DB2
PrimaryFile PrimaryPg PrimaryLSN
S0015831.LOG 1663 0x00000117A25AF50F
StandByFile StandByPg StandByLSN
S0015831.LOG 1660 0x00000117A25AC092
Reblogged this on Gunning Technology Solutions, LLC. THE WORLD LEADER IN DB2 LUW CONSULTING! and commented:
Now at 420 days…..