urn:lsid:ibm.com:blogs:entries-4f2129a4-7efa-423f-9d93-550cb9483a64DB2 for Linux, UNIX and Windows Availability TopicsBlog to discuss the availability aspects of DB2 for LUW, as well as share some tips and tricks030222018-01-10T09:49:55-05:00IBM Connections - Blogsurn:lsid:ibm.com:blogs:entry-891679a1-7752-4a33-af84-ef10d4b03be4HADR Automation with dual NIC cardsDale_McInnis060000PV6CactivefalseComment Entriesapplication/atom+xml;type=entryLikestrue2018-01-10T09:49:55-05:002018-01-10T09:49:55-05:00<p dir="ltr">It has been quite a while since I posted, going forward you will see this blob becoming much more active.</p>
<p dir="ltr">I am now in a new role in the Tech Sales organization for IBM Analytics, supporting all North American sales teams.&nbsp; I continue to focus primarily on DB2, in all of its new forms - on-prem, in the cloud, or in an appliance form factor.&nbsp;</p>
<p dir="ltr">I will now use this blog to document solutions to issues I encounter while deploying systems at customer sites or deploying in the cloud.</p>
<p dir="ltr">The first such entry involves enabling automation of HADR Takeovers, yes I still focus on resiliency.</p>
<p dir="ltr">&nbsp;</p>
<p dir="ltr">While setting up a system for one of my clients I came across an interesting limitation that appears to be poorly documented.</p>
<p dir="ltr">If you are setting up TSA to automate HADR takeovers on an environment that is using dual NICs, one for public access and one for private HADR log transmission, you can not use a HOSTNAME for the private network.&nbsp; You must use the actually IP address, which should not be an issue as your apps will never use this IP address to connect to the DB.</p>
<p dir="ltr">If you are having challenges setting up HADR automation please let me know, I am working on an updated DB2HAICU white paper.&nbsp; We also have an excellent HADR PoT that focuses on TSA automation that can be provided at your site.</p>
<p dir="ltr">&nbsp;</p>
<p dir="ltr">Thanks</p>
<p dir="ltr">Dale</p>It has been quite a while since I posted, going forward you will see this blob becoming much more active. I am now in a new role in the Tech Sales organization for IBM Analytics, supporting all North American sales teams.&nbsp; I continue to focus primarily on...00578urn:lsid:ibm.com:blogs:entries-4f2129a4-7efa-423f-9d93-550cb9483a64DB2 for Linux, UNIX and Windows Availability Topics2018-01-10T09:49:55-05:00urn:lsid:ibm.com:blogs:entry-29f70f68-b015-4ce0-8524-9e73e869b483HADR Monitoring tipsDale_McInnis060000PV6CactivefalseDale_McInnis060000PV6CactivefalseComment Entriesapplication/atom+xml;type=entryLikestrue2015-10-22T21:46:09-04:002015-10-22T21:53:34-04:00<p dir="ltr">When monitoring a HADR system I would recommend you start with the following as a minimum set.</p>
<ul dir="ltr">
<li style="margin-bottom:8.0pt;line-height:107%;">HADR_PEER_STATE
<ul>
<li style="margin-bottom:8.0pt;line-height:107%;">Anything but PEER = Sev 1</li>
</ul>
</li>
<li style="margin-bottom:8.0pt;line-height:107%;">HADR_LOG_GAP
<ul style="list-style-type:circle;">
<li>current_value / MAX log gap x 90% = 90,000,000</li>
<li>(Max Log Gap: 5min recover, 20M/Min )</li>
</ul>
</li>
<li style="margin-bottom:8.0pt;line-height:107%;">HADR_CONNECT_STATUS
<ul>
<li style="margin-bottom:8.0pt;line-height:107%;">Anything but CONNECTED = Sev 1</li>
</ul>
</li>
<li style="margin-bottom:8.0pt;line-height:107%;">STANDBY_RECV_BUF_PERCENT
<ul>
<li style="margin-bottom:8.0pt;line-height:107%;">&gt; 90% = Sev1</li>
</ul>
</li>
<li style="margin-bottom:8.0pt;line-height:107%;">STANDBY_SPOOL_PERCENT
<ul>
<li style="margin-bottom:8.0pt;line-height:107%;">&gt; 10% = Sev 3</li>
<li style="margin-bottom:8.0pt;line-height:107%;">&gt; 50% = Sev 2</li>
<li style="margin-bottom:8.0pt;line-height:107%;">&gt; 90% = Sev 1</li>
</ul>
</li>
</ul>When monitoring a HADR system I would recommend you start with the following as a minimum set. HADR_PEER_STATE
Anything but PEER = Sev 1 HADR_LOG_GAP
current_value / MAX log gap x 90% = 90,000,000 (Max Log Gap: 5min recover, 20M/Min )...001976urn:lsid:ibm.com:blogs:entries-4f2129a4-7efa-423f-9d93-550cb9483a64DB2 for Linux, UNIX and Windows Availability Topics2018-01-10T09:49:55-05:00urn:lsid:ibm.com:blogs:entry-ad3816a1-5428-4561-93ea-215f2ad7abf0Data Deduplication and EncryptionDale_McInnis060000PV6CactivefalseComment Entriesapplication/atom+xml;type=entryLikestrue2015-04-09T11:22:09-04:002015-04-09T11:22:09-04:00<p dir="ltr">
It has been determined that the release of DB2&#39;s native encryption feature on the backup utility is incompatible with the data deduplication option on backup utility.</p>
<p dir="ltr">
The reason for this is that when encryption is enabled on the backup, the utility will read the data from disk, un-encrypt the data, re-encrypt the data utilizing a random key as part of the algorithm and then send the data to the backup target device.&nbsp; The result is that each backup of the same data will not be binary identical, which is what the data deduplication device requires to indentify data that is had already processed.</p>
It has been determined that the release of DB2&#39;s native encryption feature on the backup utility is incompatible with the data deduplication option on backup utility. The reason for this is that when encryption is enabled on the backup, the utility will...022427urn:lsid:ibm.com:blogs:entries-4f2129a4-7efa-423f-9d93-550cb9483a64DB2 for Linux, UNIX and Windows Availability Topics2018-01-10T09:49:55-05:00urn:lsid:ibm.com:blogs:entry-4a33ac9a-2a76-45cd-83dd-4e8b8235cbb4Backup and Restore StatisticsDale_McInnis060000PV6CactivefalseComment Entriesapplication/atom+xml;type=entryLikestrue2014-02-04T10:46:16-05:002014-02-04T10:46:16-05:00<p class="title topictitle1" dir="ltr" tabindex="5">
Want to determine why your backup is running slowly - Check out the backup and restore statistics what is now on be default as of V 10.2 FP2.&nbsp; This feature was available as of V 9.7 by using the DB2_BAR_STATS registry variable</p>
<h1 class="title topictitle1" dir="ltr" id="vcc_sp_h1_33" tabindex="5">
Backup and restore statistics</h1>
<div class="body conbody" dir="ltr" id="vcc_sp_div_34" tabindex="6">
<p class="shortdesc" id="vcc_sp_p_35" tabindex="7">
Each successful backup and restore operation generates a single record in the <span class="ph filepath" id="vcc_sp_span_36" tabindex="8">db2diag.log</span> file, which provides information on the performance of that operation. The log record is informational and is dumped at diaglevel 3 (the default) and 4.</p>
<div class="example" id="vcc_sp_div_37" tabindex="9">
<h2 class="title sectiontitle" id="vcc_sp_h2_38" tabindex="10">
Example</h2>
<p class="p" id="vcc_sp_p_39" tabindex="11">
The log records for backup and restore statistics consist of a row for each backup and restore buffer manipulator (db2bm) EDU and a row for each backup and restore media controller (db2med) EDU:</p>
<pre class="pre codeblock" id="vcc_sp_pre_40" tabindex="12">
<code id="vcc_sp_code_41">2012-07-30-15.41.30.012922-240 E15775E1464 LEVEL: Info
PID : 15882 TID : 46913126656320 KTID : 16001
PROC : db2sysc
INSTANCE: krodger NODE : 000 DB : SAMPLE
APPHDL : 0-18 APPID: *LOCAL.krodger.120730194119
AUTHID : KRODGER HOSTNAME: hotel74
EDUID : 49 EDUNAME: db2agent (SAMPLE)
FUNCTION: DB2 UDB, database utilities, sqluxLogDataStats, probe:377
MESSAGE : Performance statistics
DATA #1 : String, 951 bytes
Number of buffers = 4
Buffer size = 16781312 (4097 4kB pages)
BM# Total I/O MsgQ WaitQ Buffers kBytes
--- -------- -------- -------- -------- -------- --------
000 6.30 0.02 0.00 6.18 4 640
001 5.88 4.48 0.00 1.33 9 139536
--- -------- -------- -------- -------- -------- --------
TOT 12.18 4.51 0.00 7.51 13 140176
MC# Total I/O MsgQ WaitQ Buffers kBytes
--- -------- -------- -------- -------- -------- --------
000 6.36 0.34 5.94 0.00 9 114748
001 6.29 0.18 5.60 0.10 6 81944
--- -------- -------- -------- -------- -------- --------
TOT 12.66 0.53 11.55 0.10 15 196692</code></pre>
The meanings of the various columns are as follows:
<dl class="dl parml" id="vcc_sp_dl_42" tabindex="13">
<dt class="dt pt dlterm" id="vcc_sp_dt_43" tabindex="14">
BM</dt>
<dd class="dd pd" id="vcc_sp_dd_44" tabindex="15">
The db2bm EDU ID</dd>
<dt class="dt pt dlterm" id="vcc_sp_dt_45" tabindex="16">
Total</dt>
<dd class="dd pd" id="vcc_sp_dd_46" tabindex="17">
Length of time that each EDU existed</dd>
<dt class="dt pt dlterm" id="vcc_sp_dt_47" tabindex="18">
I/O</dt>
<dd class="dd pd" id="vcc_sp_dd_48" tabindex="19">
Time that was spent performing read or write I/O, to or from stable storage</dd>
<dt class="dt pt dlterm" id="vcc_sp_dt_49" tabindex="20">
MsgQ</dt>
<dd class="dd pd" id="vcc_sp_dd_50" tabindex="21">
Time that was spent waiting for an I/O buffer</dd>
<dt class="dt pt dlterm" id="vcc_sp_dt_51" tabindex="22">
WaitQ</dt>
<dd class="dd pd" id="vcc_sp_dd_52" tabindex="23">
Time that was spent waiting for a state machine control message.</dd>
<dt class="dt pt dlterm" id="vcc_sp_dt_53" tabindex="24">
Buffers</dt>
<dd class="dd pd" id="vcc_sp_dd_54" tabindex="25">
Number of I/O buffers that were processed</dd>
<dt class="dt pt dlterm" id="vcc_sp_dt_55" tabindex="26">
KBytes</dt>
<dd class="dd pd" id="vcc_sp_dd_56" tabindex="27">
Quantity of data that was processed</dd>
<dt class="dt pt dlterm" id="vcc_sp_dt_57" tabindex="28">
MC</dt>
<dd class="dd pd" id="vcc_sp_dd_58" tabindex="29">
the db2med EDU ID</dd>
</dl>
</div>
<div class="example" id="vcc_sp_div_59" tabindex="30">
<h2 class="title sectiontitle" id="vcc_sp_h2_60" tabindex="31">
Example</h2>
<p class="p" id="vcc_sp_p_61" tabindex="32">
For compressed backups, the log record contains two additional columns for performance information about the compression operation:</p>
<pre class="pre codeblock" id="vcc_sp_pre_62" tabindex="33">
<code id="vcc_sp_code_63">2012-07-30-15.41.47.228766-240 E38419E1913 LEVEL: Info
PID : 15882 TID : 46913126656320 KTID : 16081
PROC : db2sysc
INSTANCE: krodger NODE : 000 DB : SAMPLE
APPHDL : 0-29 APPID: *LOCAL.krodger.120730194132
AUTHID : KRODGER HOSTNAME: hotel74
EDUID : 80 EDUNAME: db2agent (SAMPLE)
FUNCTION: DB2 UDB, database utilities, sqluxLogDataStats, probe:377
MESSAGE : Performance statistics
DATA #1 : String, 1399 bytes
Number of buffers = 4
Buffer size = 16781312 (4097 4K pages)
<strong class="ph b" id="vcc_sp_strong_64" tabindex="34">Compr</strong>
BM# Total I/O <strong class="ph b" id="vcc_sp_strong_65" tabindex="35">Compr</strong> MsgQ WaitQ Buffers kBytes <strong class="ph b" id="vcc_sp_strong_66" tabindex="36">kBytes</strong>
--- ------- ------ ------ ------- -------- -------- -------- --------
000 12.08 4.36 7.18 0.00 0.37 5 139536 144941
001 11.87 0.01 0.01 0.00 11.79 1 640 640
--- ------- ------ ------ ------- -------- -------- -------- --------
TOT 23.96 4.38 7.19 0.00 12.17 6 140176 145581
MC# Total I/O MsgQ WaitQ Buffers kBytes
--- ------- ------ ------ ------- -------- -------- -------- --------
000 12.07 0.11 11.76 0.00 4 49168
001 12.10 0.07 11.84 0.15 4 32808
--- ------- ------ ------- -------- -------- --------
TOT 24.18 0.19 23.61 0.15 8 81976</code></pre>
<dl class="dl parml" id="vcc_sp_dl_67" tabindex="37">
<dt class="dt pt dlterm" id="vcc_sp_dt_68" tabindex="38">
Compr</dt>
<dd class="dd pd" id="vcc_sp_dd_69" tabindex="39">
Time that was spent performing the compression operation</dd>
<dt class="dt pt dlterm" id="vcc_sp_dt_70" tabindex="40">
Compr Bytes</dt>
<dd class="dd pd" id="vcc_sp_dd_71" tabindex="41">
Quantity of uncompressed data that was compressed</dd>
</dl>
</div>
</div>
<p dir="ltr">
&nbsp;</p>
Want to determine why your backup is running slowly - Check out the backup and restore statistics what is now on be default as of V 10.2 FP2.&nbsp; This feature was available as of V 9.7 by using the DB2_BAR_STATS registry variable Backup and restore...115726urn:lsid:ibm.com:blogs:entries-4f2129a4-7efa-423f-9d93-550cb9483a64DB2 for Linux, UNIX and Windows Availability Topics2018-01-10T09:49:55-05:00urn:lsid:ibm.com:blogs:entry-17146cd4-192e-419f-9949-5aaac595776fDB2 Dedup paper published on developerworksDale_McInnis060000PV6CactivefalseComment Entriesapplication/atom+xml;type=entryLikestrue2013-02-21T13:48:52-05:002013-02-21T13:48:52-05:00I'm proud to announce the publication of my article on developerWorks: &quot;Integrated support for data deduplication devices in DB2 for Linux, UNIX, and Windows&quot;.<br /><br />Summary: Learn how data deduplication offers benefits such as reducing storage requirements, improving backup performance, and reducing traffic across your network. This article explains the basic technology of deduplication, discusses the various methodology's that you can use, and shows how DB2® for Linux®, UNIX®, and Windows® has been changed to support various deduplication devices. Finally, the article includes the results of benchmark testing to illustrate how effective the Tivoli® Storage Manager server data deduplication feature can be with DB2. http://www.ibm.com/developerworks/data/library/techarticle/dm-1302db2deduplication/index.html<br /><br />I hope you like it and find it useful. If you have feedback, I'd love to hear it.<br /><br />
I'm proud to announce the publication of my article on developerWorks: &quot;Integrated support for data deduplication devices in DB2 for Linux, UNIX, and Windows&quot;. Summary: Learn how data deduplication offers benefits such as reducing storage...002792urn:lsid:ibm.com:blogs:entries-4f2129a4-7efa-423f-9d93-550cb9483a64DB2 for Linux, UNIX and Windows Availability Topics2018-01-10T09:49:55-05:00urn:lsid:ibm.com:blogs:entry-62f03652-b621-49f9-a089-e1de28df7bfdTSM deduplication test resultsDale_McInnis060000PV6CactivefalseComment Entriesapplication/atom+xml;type=entryLikestrue2012-12-06T10:57:20-05:002012-12-10T20:35:16-05:00
<div> </div><div>I have been running some experiments with TSM 6.2's native deduplication capabilities. Here are some results from my first run, they are quite impressive.<br />
<table border="0" cellpadding="0" cellspacing="0" width="818"><colgroup><col style="mso-width-source:userset;mso-width-alt:3657;width:75pt" width="100" />
<col style="mso-width-source:userset;mso-width-alt:3584;width:74pt" width="98" />
<col style="mso-width-source:userset;mso-width-alt:3401;width:70pt" width="93" />
<col style="mso-width-source:userset;mso-width-alt:5705;width:117pt" width="156" />
<col style="mso-width-source:userset;mso-width-alt:8082;width:166pt" width="221" />
<col style="mso-width-source:userset;mso-width-alt:5485;width:113pt" width="150" />
</colgroup><tbody><tr height="20" style="height:15.0pt">
<td class="xl63" colspan="2" height="20" style="height:15.0pt;mso-ignore:
colspan;width:149pt" width="198">Dedup test results</td>
<td class="xl66" style="width:70pt" width="93"><br /></td>
<td style="width:117pt" width="156"><br /></td>
<td style="width:166pt" width="221"><br /></td>
<td class="xl65" style="width:113pt" width="150"><br /></td>
</tr>
<tr height="20" style="height:15.0pt">
<td class="xl63" height="20" style="height:15.0pt"><br /></td>
<td class="xl63"><br /></td>
<td class="xl66"><span style="mso-spacerun:yes"> </span></td>
<td align="right" class="xl64">6-Dec-12</td>
<td><br /></td>
<td class="xl65"><br /></td>
</tr>
<tr height="20" style="height:15.0pt">
<td class="xl63" colspan="4" height="20" style="height:15.0pt;mso-ignore:colspan">DB2
BACKUP DB PERF USE TSM OPEN 8 SESSION DEDUP_DEVICE</td>
<td colspan="2" style="mso-ignore:colspan">Utilizing both CLIENT and SERVER
side deduplication</td>
</tr>
<tr height="20" style="height:15.0pt">
<td class="xl63" height="20" style="height:15.0pt">Start</td>
<td class="xl63">End</td>
<td class="xl66">Elapsed Time</td>
<td>Actual DB Size in bytes</td>
<td>Dedup Size sent to server in bytes</td>
<td class="xl65">% Savings in bandwidth</td>
</tr>
<tr height="20" style="height:15.0pt">
<td align="right" class="xl63" height="20" style="height:15.0pt">12:22:57 AM</td>
<td align="right" class="xl63">2:32:54 AM</td>
<td align="right" class="xl66">2:09</td>
<td align="right">1.35891E+11</td>
<td align="right">1.3574E+11</td>
<td align="right" class="xl65">0.11%</td>
</tr>
<tr height="20" style="height:15.0pt">
<td align="right" class="xl63" height="20" style="height:15.0pt">2:33:02 AM</td>
<td align="right" class="xl63">3:04:13 AM</td>
<td align="right" class="xl66">0:31</td>
<td align="right">1.35891E+11</td>
<td align="right">3501526595</td>
<td align="right" class="xl65">97.42%</td>
</tr>
<tr height="20" style="height:15.0pt">
<td align="right" class="xl63" height="20" style="height:15.0pt">3:04:19 AM</td>
<td align="right" class="xl63">3:34:07 AM</td>
<td align="right" class="xl66">0:29</td>
<td align="right">1.35891E+11</td>
<td align="right">1439490051</td>
<td align="right" class="xl65">98.94%</td>
</tr>
<tr height="20" style="height:15.0pt">
<td align="right" class="xl63" height="20" style="height:15.0pt">3:34:13 AM</td>
<td align="right" class="xl63">4:03:14 AM</td>
<td align="right" class="xl66">0:29</td>
<td align="right">1.35891E+11</td>
<td align="right">875452538</td>
<td align="right" class="xl65">99.36%</td>
</tr>
<tr height="20" style="height:15.0pt">
<td align="right" class="xl63" height="20" style="height:15.0pt">4:03:20 AM</td>
<td align="right" class="xl63">4:32:45 AM</td>
<td align="right" class="xl66">0:29</td>
<td align="right">1.35891E+11</td>
<td align="right">1015678830</td>
<td align="right" class="xl65">99.25%</td>
</tr>
<tr height="20" style="height:15.0pt">
<td class="xl63" height="20" style="height:15.0pt"><br /></td>
<td class="xl63"><br /></td>
<td class="xl66"><br /></td>
<td><span style="mso-spacerun:yes"> </span></td>
<td><span style="mso-spacerun:yes"> </span></td>
<td class="xl65"><span style="mso-spacerun:yes"> </span></td>
</tr>
<tr height="20" style="height:15.0pt">
<td class="xl63" colspan="4" height="20" style="height:15.0pt;mso-ignore:colspan">DB2
BACKUP DB PERF USE TSM OPEN 8 SESSION DEDUP_DEVICE</td>
<td colspan="2" style="mso-ignore:colspan">Utilizing both CLIENT and SERVER
side deduplication</td>
</tr>
<tr height="20" style="height:15.0pt">
<td class="xl63" height="20" style="height:15.0pt">Start</td>
<td class="xl63">End</td>
<td class="xl66">Elapsed Time</td>
<td>Actual DB Size in bytes</td>
<td>Dedup Size sent to server in bytes</td>
<td class="xl65">% Savings in bandwidth</td>
</tr>
<tr height="20" style="height:15.0pt">
<td align="right" class="xl63" height="20" style="height:15.0pt">10:29:22 PM</td>
<td align="right" class="xl63">2:05:51 AM</td>
<td align="right" class="xl66">3:36</td>
<td align="right">1.35891E+11</td>
<td align="right">1.3574E+11</td>
<td align="right" class="xl65">0.11%</td>
</tr>
<tr height="20" style="height:15.0pt">
<td align="right" class="xl63" height="20" style="height:15.0pt">2:05:59 AM</td>
<td align="right" class="xl63">2:37:17 AM</td>
<td align="right" class="xl66">0:31</td>
<td align="right">1.35891E+11</td>
<td align="right">3258729375</td>
<td align="right" class="xl65">97.60%</td>
</tr>
<tr height="20" style="height:15.0pt">
<td align="right" class="xl63" height="20" style="height:15.0pt">2:37:23 AM</td>
<td align="right" class="xl63">3:05:53 AM</td>
<td align="right" class="xl66">0:28</td>
<td align="right">1.35891E+11</td>
<td align="right">1602671422</td>
<td align="right" class="xl65">98.82%</td>
</tr>
<tr height="20" style="height:15.0pt">
<td align="right" class="xl63" height="20" style="height:15.0pt">3:06:00 AM</td>
<td align="right" class="xl63">3:35:27 AM</td>
<td align="right" class="xl66">0:29</td>
<td align="right">1.35891E+11</td>
<td align="right">1337909163</td>
<td align="right" class="xl65">99.02%</td>
</tr>
<tr height="20" style="height:15.0pt">
<td align="right" class="xl63" height="20" style="height:15.0pt">3:35:33 AM</td>
<td align="right" class="xl63">4:04:32 AM</td>
<td align="right" class="xl66">0:28</td>
<td align="right">1.35891E+11</td>
<td align="right">967988939</td>
<td align="right" class="xl65">99.29%</td>
</tr>
<tr height="20" style="height:15.0pt">
<td class="xl63" height="20" style="height:15.0pt"><br /></td>
<td class="xl63"><br /></td>
<td class="xl66"><br /></td>
<td><br /></td>
<td><br /></td>
<td class="xl65"><br /></td>
</tr>
<tr height="20" style="height:15.0pt">
<td class="xl63" colspan="4" height="20" style="height:15.0pt;mso-ignore:colspan">DB2
BACKUP DB PERF USE TSM OPEN 8 SESSION</td>
<td colspan="2" style="mso-ignore:colspan">Utilizing both CLIENT and SERVER
side deduplication</td>
</tr>
<tr height="20" style="height:15.0pt">
<td class="xl63" height="20" style="height:15.0pt">Start</td>
<td class="xl63">End</td>
<td class="xl66">Elapsed Time</td>
<td>Actual DB Size in bytes</td>
<td>Dedup Size sent to server in bytes</td>
<td class="xl65">% Savings in bandwidth</td>
</tr>
<tr height="20" style="height:15.0pt">
<td align="right" class="xl63" height="20" style="height:15.0pt">11:27:16 AM</td>
<td align="right" class="xl63">4:40:14 PM</td>
<td align="right" class="xl66">5:12</td>
<td align="right">1.35901E+11</td>
<td align="right">1.35762E+11</td>
<td align="right" class="xl65">0.10%</td>
</tr>
<tr height="20" style="height:15.0pt">
<td align="right" class="xl63" height="20" style="height:15.0pt">4:40:14 PM</td>
<td align="right" class="xl63">5:10:12 PM</td>
<td align="right" class="xl66">0:29</td>
<td align="right">1.35901E+11</td>
<td align="right">5735212149</td>
<td align="right" class="xl65">95.78%</td>
</tr>
<tr height="20" style="height:15.0pt">
<td align="right" class="xl63" height="20" style="height:15.0pt">5:10:12 PM</td>
<td align="right" class="xl63">5:39:45 PM</td>
<td align="right" class="xl66">0:29</td>
<td align="right">1.35901E+11</td>
<td align="right">4192184764</td>
<td align="right" class="xl65">96.92%</td>
</tr>
<tr height="20" style="height:15.0pt">
<td align="right" class="xl63" height="20" style="height:15.0pt">5:39:45 PM</td>
<td align="right" class="xl63">6:08:26 PM</td>
<td align="right" class="xl66">0:28</td>
<td align="right">1.35901E+11</td>
<td align="right">3486134412</td>
<td align="right" class="xl65">97.43%</td>
</tr>
<tr height="20" style="height:15.0pt">
<td align="right" class="xl63" height="20" style="height:15.0pt">6:08:26 PM</td>
<td align="right" class="xl63">6:37:29 PM</td>
<td align="right" class="xl66">0:29</td>
<td align="right">1.35901E+11</td>
<td align="right">3136679820</td>
<td align="right" class="xl65">97.69%</td>
</tr>
<tr height="20" style="height:15.0pt">
<td class="xl63" height="20" style="height:15.0pt"><br /></td>
<td class="xl63"><br /></td>
<td class="xl66"><br /></td>
<td><br /></td>
<td><br /></td>
<td class="xl65"><br /></td>
</tr>
</tbody></table>Using the DEDUP_DEVICE option on the backup invocation will make a difference, particularly when setting a new baseline backup. <br />
<table border="0" cellpadding="0" cellspacing="0" width="766"><colgroup><col style="mso-width-source:userset;mso-width-alt:3657;width:75pt" width="100" />
<col style="mso-width-source:userset;mso-width-alt:3584;width:74pt" width="98" />
<col style="mso-width-source:userset;mso-width-alt:3401;width:70pt" width="93" />
<col style="mso-width-source:userset;mso-width-alt:5705;width:117pt" width="156" />
<col style="mso-width-source:userset;mso-width-alt:7972;width:164pt" width="218" />
<col style="mso-width-source:userset;mso-width-alt:3693;width:76pt" width="101" />
</colgroup><tbody><tr height="20" style="height:15.0pt">
<td class="xl63" colspan="4" height="20" style="height:15.0pt;mso-ignore:
colspan;width:336pt" width="447"><br /></td><td colspan="2" style="mso-ignore:colspan;width:240pt" width="319"><br /></td></tr><tr height="20" style="height:15.0pt"><td class="xl63" height="20" style="height:15.0pt"><br /></td><td class="xl63"><br /></td><td class="xl65"><br /></td><td><br /></td><td><br /></td><td class="xl64"><br /></td></tr><tr height="20" style="height:15.0pt"><td align="right" class="xl63" height="20" style="height:15.0pt"><br /></td><td align="right" class="xl63"><br /></td><td align="right" class="xl65"><br /></td><td align="right"><br /></td><td align="right"><br /></td><td align="right" class="xl64"><br /></td></tr><tr height="20" style="height:15.0pt"><td align="right" class="xl63" height="20" style="height:15.0pt"><br /></td><td align="right" class="xl63"><br /></td><td align="right" class="xl65"><br /></td><td align="right"><br /></td><td align="right"><br /></td><td align="right" class="xl64"><br /></td></tr><tr height="20" style="height:15.0pt"><td align="right" class="xl63" height="20" style="height:15.0pt"><br /></td><td align="right" class="xl63"><br /></td><td align="right" class="xl65"><br /></td><td align="right"><br /></td><td align="right"><br /></td><td align="right" class="xl64"><br /></td></tr><tr height="20" style="height:15.0pt"><td align="right" class="xl63" height="20" style="height:15.0pt"><br /></td><td align="right" class="xl63"><br /></td><td align="right" class="xl65"><br /></td><td align="right"><br /></td><td align="right"><br /></td><td align="right" class="xl64"><br /></td></tr><tr height="20" style="height:15.0pt"><td align="right" class="xl63" height="20" style="height:15.0pt"><br /></td><td align="right" class="xl63"><br /></td><td align="right" class="xl65"><br /></td><td align="right"><br /></td><td align="right"><br /></td><td align="right" class="xl64"><br /></td></tr></tbody></table></div> I have been running some experiments with TSM 6.2's native deduplication capabilities. Here are some results from my first run, they are quite impressive. Dedup test results 6-Dec-12 DB2
BACKUP DB PERF USE TSM OPEN 8 SESSION DEDUP_DEVICE Utilizing both...045912urn:lsid:ibm.com:blogs:entries-4f2129a4-7efa-423f-9d93-550cb9483a64DB2 for Linux, UNIX and Windows Availability Topics2018-01-10T09:49:55-05:00urn:lsid:ibm.com:blogs:entry-f8319e47-810c-4306-8833-b02e4ca498d8Multiple Standby White PaperDale_McInnis060000PV6CactivefalseComment Entriesapplication/atom+xml;type=entryLikestrue2012-06-24T09:09:11-04:002012-06-24T09:09:11-04:00<div>Here is a recently published white paper on HADR Multiple Standby supported added to db2 v10</div><div> </div><div>http://www.ibm.com/developerworks/data/library/long/dm-1206hadrmultiplestandby/index.html<br /><br />Enjoy<br /></div>
Here is a recently published white paper on HADR Multiple Standby supported added to db2 v10 http://www.ibm.com/developerworks/data/library/long/dm-1206hadrmultiplestandby/index.html Enjoy015433urn:lsid:ibm.com:blogs:entries-4f2129a4-7efa-423f-9d93-550cb9483a64DB2 for Linux, UNIX and Windows Availability Topics2018-01-10T09:49:55-05:00urn:lsid:ibm.com:blogs:entry-14329bf4-c397-471e-a151-1eff732161edQuick Business Continuity SurveyDale_McInnis060000PV6CactivefalseComment Entriesapplication/atom+xml;type=entryLikestrue2012-05-31T14:18:37-04:002012-05-31T14:18:37-04:00DB2 Business Continuity Survey<br /><br />We would ask that you consider participating in a very quick survey which will provide you the ability to directly influence our future product feature list. This survey will focus on two main areas which affect your systems’ availability, planned and unplanned outages. Please provide sufficient detail so that we can understand the business scenario.<br />Please list your top 5 most disruptive planned outages – in priority order<br />1. <br />2. <br />3. <br />4. <br />5. <br />Please list your top 5 most disruptive unplanned outages - in priority order<br />1. <br />2. <br />3. <br />4. <br />5. <br />Please provide the top 3 disruptive planned or unplanned outages (from above) in priority order<br />1. <br />2. <br />3. <br />Please list the most recent 5 issues that caused an interruption to the business you support<br />1. <br />2. <br />3. <br />4. <br />5. <br />What availability features would you like to see in the product that could help expand the use of DB2 in your company?<br />1. <br />2. <br />3. <br />4. <br />5. <br />Please send your completed survey to dmcinnis@ca.ibm.com. This information will not be shared with other customers; it is solely for the purpose of product planning. All company specific information will be removed when the results are rolled up.
DB2 Business Continuity Survey We would ask that you consider participating in a very quick survey which will provide you the ability to directly influence our future product feature list. This survey will focus on two main areas which affect your systems’...002444urn:lsid:ibm.com:blogs:entries-4f2129a4-7efa-423f-9d93-550cb9483a64DB2 for Linux, UNIX and Windows Availability Topics2018-01-10T09:49:55-05:00urn:lsid:ibm.com:blogs:entry-3f63033c-ddbd-484f-be1d-2cb077969eacHADR and TSA information pointersDale_McInnis060000PV6CactivefalseComment Entriesapplication/atom+xml;type=entryLikestrue2012-05-18T00:15:25-04:002012-05-18T00:16:45-04:00
<div> </div><div>Here is a collection of TSA and HADR white papers <br /></div><div> </div><div>1) Here is a white paper that discusses cross site HADR automation:<br />https://www.ibm.com/developerworks/data/library/long/dm-1002automateddb2hadr/<br /><br /><br />2) Here is a white paper that discusses TSA shared disk automation<br />http://www.ibm.com/developerworks/data/library/long/dm-0909hasharedstorage/index.html<br /><br />3) HADR Best Practices White paper: <br />http://public.dhe.ibm.com/software/dw/dm/db2/bestpractices/DB2BP_HADR_0911.pdf </div><div> </div><div>4)Using DB2HAICU<br />http://public.dhe.ibm.com/software/dw/data/dm-0908hadrdb2haicu/HADR_db2haicu.pdf<br />https://www.ibm.com/developerworks/mydeveloperworks/blogs/nsharma/resource/HADR-db2haicu_v5.pdf?lang=en<br /> <br /></div>
Here is a collection of TSA and HADR white papers 1) Here is a white paper that discusses cross site HADR automation: https://www.ibm.com/developerworks/data/library/long/dm-1002automateddb2hadr/ 2) Here is a white paper that discusses TSA shared disk...005828urn:lsid:ibm.com:blogs:entries-4f2129a4-7efa-423f-9d93-550cb9483a64DB2 for Linux, UNIX and Windows Availability Topics2018-01-10T09:49:55-05:00urn:lsid:ibm.com:blogs:entry-ec40ef59-a834-442c-9dd8-d2aab84ba633IDUG NA - HADR configuration change propogationDale_McInnis060000PV6CactivefalseComment Entriesapplication/atom+xml;type=entryLikestrue2012-05-17T11:12:59-04:002012-05-17T11:12:59-04:00<div>Question:</div><div>Does HADR propagate the database configuration changes made on the primary to the standby(s)<br /><br />Response:</div>
<div> </div><div>HADR will propagate any operation that is logged. Unfortunately changes to both the database manager and database configuration parameters are not logged, thus they are not propagated from the primary to the standby<br /></div>
Question: Does HADR propagate the database configuration changes made on the primary to the standby(s) Response: HADR will propagate any operation that is logged. Unfortunately changes to both the database manager and database configuration parameters are...003112urn:lsid:ibm.com:blogs:entries-4f2129a4-7efa-423f-9d93-550cb9483a64DB2 for Linux, UNIX and Windows Availability Topics2018-01-10T09:49:55-05:00urn:lsid:ibm.com:blogs:entry-ccbedb76-3ed0-4e59-90a3-bec9a01a25beQuestion from IDUG NA - HADR Load SupportDale_McInnis060000PV6CactivefalseComment Entriesapplication/atom+xml;type=entryLikestrue2012-05-17T10:59:43-04:002012-05-17T11:01:24-04:00<div>question:</div><div>how does load work in an HADR environment<br /><br />Response:</div><div>there are 3 types of load <br />1) load non recoverable - in this case the table on the standby will be taken offline<br />2) load copy no - also in this case the table on the standby will be taken offline</div><div>3) load copy yes - when the load commit log record gets processed on the standby the load copy image MUST be accessible on the standby. this can be done by using a shared device - e.g NFS mount or TSM.<br /><br />Our recommendation is to the new V10 INGEST option rather than load - INGEST is a fully logged operation and as such is completely compatible with HADR. Ingest does not require a V 10 server, only a V 10 client.<br /></div>
question: how does load work in an HADR environment Response: there are 3 types of load 1) load non recoverable - in this case the table on the standby will be taken offline 2) load copy no - also in this case the table on the standby will be taken offline 3)...003651urn:lsid:ibm.com:blogs:entries-4f2129a4-7efa-423f-9d93-550cb9483a64DB2 for Linux, UNIX and Windows Availability Topics2018-01-10T09:49:55-05:00urn:lsid:ibm.com:blogs:entry-930c894c-a5b9-45a1-9a10-8d506389ee2aQuestions from IDUG NADale_McInnis060000PV6CactivefalseComment Entriesapplication/atom+xml;type=entryLikestrue2012-05-15T13:31:12-04:002012-05-15T13:31:12-04:00<div> </div><div>This week is the IDUG North American 2012 conference in Denver CO. </div><div> </div><div>Over the next week I will be posting questions and the associate answers from questions from customers that occur either during my sessions or from hallway conversations.<br /></div><div> </div><div>Question:<br />Has an change been made to HADR RoS for access the LOB data<br /></div><div> </div><div>Response:</div><div>As of DB2 v 9.7 FP5 we now supporting returning any INLINE LOB on queries run on the standby. This feature also applies to INLINE XML data as well.<br /></div><div>This is also available in DB2 10 <br /></div>
This week is the IDUG North American 2012 conference in Denver CO. Over the next week I will be posting questions and the associate answers from questions from customers that occur either during my sessions or from hallway conversations. Question: Has...002854urn:lsid:ibm.com:blogs:entries-4f2129a4-7efa-423f-9d93-550cb9483a64DB2 for Linux, UNIX and Windows Availability Topics2018-01-10T09:49:55-05:00urn:lsid:ibm.com:blogs:entry-c6f2c117-8aac-4bd7-bec2-09b04e0176d2Pointers to DB2 HADR V 10 documentationDale_McInnis060000PV6CactivefalseComment Entriesapplication/atom+xml;type=entryLikestrue2012-05-08T14:47:34-04:002012-05-08T14:48:35-04:00
<div class="wiki-content"><h3><a name="HADR_NEW-Multiplestandby">Multiple standby</a></h3><a name="HADR_NEW-Multiplestandby">
</a><p><a name="HADR_NEW-Multiplestandby">Up to 3 standbys are supported. Now you can provide HA and DR protection to
your database with a single technology. See <span class="nobr" /></a><a href="http://publib.boulder.ibm.com/infocenter/db2luw/v10r1/topic/com.ibm.db2.luw.admin.ha.doc/doc/c0059994.html" rel="nofollow">http://publib.boulder.ibm.com/infocenter/db2luw/v10r1/topic/com.ibm.db2.luw.admin.ha.doc/doc/c0059994.html<sup><img align="absMiddle" alt="" border="0" class="rendericon" height="7" src="/developerworks/wikis/images/icons/linkext7.gif" width="7" /></sup></a></p>
<div> </div><div> </div><h3><a name="HADR_NEW-Spooling">Spooling</a></h3><p><a name="HADR_NEW-Spooling">Spooling allows you to specify additional space where logs can be spooled on
the standby. This helps avoid back-pressure on the primary caused by sudden
spikes in logging activity. See <span class="nobr" /></a><a href="http://publib.boulder.ibm.com/infocenter/db2luw/v10r1/topic/com.ibm.db2.luw.wn.doc/doc/c0060144.html" rel="nofollow">http://publib.boulder.ibm.com/infocenter/db2luw/v10r1/topic/com.ibm.db2.luw.wn.doc/doc/c0060144.html<sup><img align="absMiddle" alt="" border="0" class="rendericon" height="7" src="/developerworks/wikis/images/icons/linkext7.gif" width="7" /></sup></a></p>
<div> </div><div> </div><h3><a name="HADR_NEW-DelayedReplay">Delayed Replay</a></h3><p><a name="HADR_NEW-DelayedReplay">Delayed replay helps prevent data loss due to errant transactions. See <span class="nobr" /></a><a href="http://publib.boulder.ibm.com/infocenter/db2luw/v10r1/topic/com.ibm.db2.luw.admin.ha.doc/doc/c0060000.html" rel="nofollow">http://publib.boulder.ibm.com/infocenter/db2luw/v10r1/topic/com.ibm.db2.luw.admin.ha.doc/doc/c0060000.html<sup><img align="absMiddle" alt="" border="0" class="rendericon" height="7" src="/developerworks/wikis/images/icons/linkext7.gif" width="7" /></sup></a></p></div>
Multiple standby Up to 3 standbys are supported. Now you can provide HA and DR protection to
your database with a single technology. See http://publib.boulder.ibm.com/infocenter/db2luw/v10r1/topic/com.ibm.db2.luw.admin.ha.doc/doc/c0059994.html Spooling...002623urn:lsid:ibm.com:blogs:entries-4f2129a4-7efa-423f-9d93-550cb9483a64DB2 for Linux, UNIX and Windows Availability Topics2018-01-10T09:49:55-05:00urn:lsid:ibm.com:blogs:entry-931b6dee-1fd0-4507-8aa5-ba8509f1f179Log Archiving in an HADR environmentDale_McInnis060000PV6CactivefalseComment Entriesapplication/atom+xml;type=entryLikestrue2012-04-09T10:58:03-04:002012-04-13T08:50:19-04:00
<div><b>Log archiving in an HADR environment</b><span style="mso-bidi-font-size:12.0pt"><br />It is recommended that both the
primary database and the standby databases be configured for log archiving, as
any of these systems could be promoted to become the primary at which point it
will be required to archive its log files.</span><span style="mso-bidi-font-size:12.0pt"><span style="mso-tab-count:1"><span style="mso-bidi-font-size:12.0pt"><br /><br />Only the current primary
database can perform log archiving. If the primary and standby databases are
set up with separate archiving locations, logs are archived only to the primary
database's archiving location. In the event of a takeover, the standby database
becomes the new primary database and any logs archived from that point on are
saved to the original standby database's archiving location. In such a
configuration, logs are archived to one location or the other, but not both;
with the exception that following a takeover, the new primary database might
archive a few logs that the original primary database had already archived. In
a multiple standby system, the archived log files can be scattered among all
databases' (primary and standbys) archive devices. A shared archive is
preferred because all files are stored in a single location.</span><span style="mso-bidi-font-size:12.0pt"><span style="mso-bidi-font-size:12.0pt"><br /><br />Many operations need to
retrieve archived log files. These operations include: database roll forward,
the HADR primary database retrieving log files to send to the standby database
in remote catch up, and replication programs (such as Q Replication) reading
logs. As a result, a shared archive for an HADR system is preferred, otherwise,
the needed files can be distributed on multiple archive devices, and user
intervention is needed to locate the needed files and copy them to the
requesting database. The recommended copy destination is an archive device. If
copying into an archive is not feasible, copy the logs into the overflow log
path. As a last resort, copy them into the log path (but one should be aware
that there is a risk of damaging the active log files). DB2® does not auto
delete user copied files in the overflow and active log path, so one should
manually remove the files when they are no longer needed by any HADR standby or
any application.</span><span style="mso-bidi-font-size:12.0pt"><br /><b><br />Log file management on standby</b><span style="mso-bidi-font-size:12.0pt;
line-height:150%"><span style="mso-bidi-font-size:12.0pt"><br />The standby
database automatically manages log files in its log path. The standby database
does not delete a log file from its local log path unless it has been notified
by the primary database that the primary database has archived it. This
behavior provides added protection against the loss of log files. If the
primary database fails before the log file is safely stored in the archive, the
standby database would ensure the log file is archived. If both the
logarchmeth1 and logarchmeth2 configuration parameters are in use, the standby
database does not recycle a log file until the primary database has archived it
using both methods.</span></span></span></span></span></span></div><div> </div><div>Dale McInnis <br /></div>
Log archiving in an HADR environment It is recommended that both the
primary database and the standby databases be configured for log archiving, as
any of these systems could be promoted to become the primary at which point it
will be required to archive...019862urn:lsid:ibm.com:blogs:entries-4f2129a4-7efa-423f-9d93-550cb9483a64DB2 for Linux, UNIX and Windows Availability Topics2018-01-10T09:49:55-05:00urn:lsid:ibm.com:blogs:entry-1bbf5339-ca3d-42cf-a95c-b130d344139eDB2 V 10 HADR Time Delayed Apply on StandbyDale_McInnis060000PV6CactivefalseComment Entriesapplication/atom+xml;type=entryLikestrue2012-04-09T10:53:38-04:002012-04-09T17:28:36-04:00
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal"><span style="mso-bidi-font-size:12.0pt">HADR delayed replay
helps prevent data loss due to errant transactions. To implement HADR delayed
replay, set the <i style="mso-bidi-font-style:normal">hadr_replay_delay </i>database
configuration parameter on the HADR standby database.</span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal"><span style="mso-bidi-font-size:12.0pt">Delayed replay
intentionally keeps the standby database at a point in time that is earlier
than that of the primary database by delaying replay of logs on that standby.
If an errant transaction is executed on the primary, one has until the
configured time delay has elapsed to take action to prevent the errant transaction
from being replayed on the standby. To recover the lost data, one can either
copy this data back to the primary, or one can have the standby take over as
the new primary database.</span></p>
<p class="MsoNormal" style="margin-bottom:0in;margin-bottom:.0001pt;line-height:
normal"><span style="mso-bidi-font-size:12.0pt">Delayed replay works by
comparing timestamps in the log stream, which is generated on the primary, and
the current time of the standby. As a result, it is important to synchronize
the clocks of the primary and standby databases. Transaction commit is replayed
on the standby according to the following equation: </span></p>
<p class="MsoNormal" style="margin-bottom:0in;margin-bottom:.0001pt;line-height:
normal;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt"><span style="font-size:10.0pt;font-family:&quot;Courier New&quot;">(<i>current time on the
standby</i> - <i>value of the hadr_replay_delay configuration parameter</i>)
&gt;= </span></p>
<p class="MsoNormal" style="margin-bottom:0in;margin-bottom:.0001pt;line-height:
normal;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt"><span style="font-size:10.0pt;font-family:&quot;Courier New&quot;"><span style="mso-tab-count:
1"> </span><i>timestamp of the committed log record</i></span></p>
<p class="MsoNormal" style="margin-bottom:0in;margin-bottom:.0001pt;line-height:
normal"><span style="mso-bidi-font-size:12.0pt">One should set the
hadr_replay_delay database configuration parameter to a large enough value to
allow time to detect and react to errant transactions on the primary.</span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal"><span style="mso-bidi-font-size:12.0pt">One can use this
feature in either single standby mode or multiple standby mode. In multiple
standby mode, typically one or more standbys stays current with the primary for
high availability or disaster recovery purposes, and one standby is configured
with delayed replay for protection against errant transactions. </span></p>
<p class="MsoNormal" style="margin-bottom:0in;margin-bottom:.0001pt;line-height:
normal"><span style="mso-bidi-font-size:12.0pt">There are several important
restrictions for delayed replay:</span></p>
<ul type="disc"><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal;mso-list:l0 level1 lfo1;tab-stops:list .5in"><span style="mso-bidi-font-size:12.0pt">One can set the <i style="mso-bidi-font-style:
normal">hadr_replay_delay</i> configuration parameter only on a standby
database. </span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal;mso-list:l0 level1 lfo1;tab-stops:list .5in"><span style="mso-bidi-font-size:12.0pt">A TAKEOVER command on a standby with
replay delay enabled will fail. One must first set the <i style="mso-bidi-font-style:normal">hadr_replay_delay</i> configuration
parameter to 0 and then deactivate and reactivate the standby to pick up
the new value, and then issue the TAKEOVER command. </span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
line-height:normal;mso-list:l0 level1 lfo1;tab-stops:list .5in"><span style="mso-bidi-font-size:12.0pt">The delayed replay feature is supported
only in SUPERASYNC mode. Because log replay is delayed, a lot of
unreplayed log data might accumulate on the standby, filling up receive
buffer and spool (if configured). In other synchronization modes, this
would cause the primary to be blocked. </span></li></ul>
<p class="MsoNormal" style="line-height:normal">If one enables delayed replay, it
is recommended that log spooling is also enabled by setting the <i style="mso-bidi-font-style:normal">hadr_spool_limit</i> database configuration
parameter. Because of the intentional delay, replay position can be far behind
log receive position on standby. Without spooling, log receive can only go
beyond replay by the amount of the receive buffer. With spooling enabled the standby
can receive much more logs beyond the replay position, providing greater
protection against data loss in case of primary failure. Note that in either
case, because of the mandatory SUPERASYNC mode, the primary will not be blocked
by enabling delayed replay.</p>HADR delayed replay
helps prevent data loss due to errant transactions. To implement HADR delayed
replay, set the hadr_replay_delay database
configuration parameter on the HADR standby database. Delayed replay
intentionally keeps the standby database at a...005541urn:lsid:ibm.com:blogs:entries-4f2129a4-7efa-423f-9d93-550cb9483a64DB2 for Linux, UNIX and Windows Availability Topics2018-01-10T09:49:55-05:00urn:lsid:ibm.com:blogs:entry-fa1f966f-0874-4eda-b340-166a8ae96e4aHADR V10 Log SpoolingDale_McInnis060000PV6CactivefalseComment Entriesapplication/atom+xml;type=entryLikestrue2012-04-08T12:55:00-04:002012-04-09T17:27:37-04:00
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:0in;margin-bottom:
.0001pt;line-height:normal"><span style="mso-bidi-font-size:12.0pt">HADR
standby log spooling is a new feature in DB2® V10. This feature allows
transactions on the primary to make progress without having to wait for the log
replay on the standby. Log data that is sent by the primary is written, or
spooled, to disk on the standby if it falls behind in log replay. The standby
database can later read the log data from disk. This allows the system to
better tolerate either a spike in transaction volume on the primary, or a slowdown
of log replay on the standby. This feature can be used in both single and
multiple standby environments.</span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:0in;margin-bottom:
.0001pt;line-height:normal"><span style="mso-bidi-font-size:12.0pt">When making
use of log spooling, ensure that adequate disk space is provided to the active
log path of the standby database in order for it to hold the spooled log data,
in addition to the disk space required for active logs. Log space is determined
by the <i style="mso-bidi-font-style:normal">logprimary</i>, <i style="mso-bidi-font-style:normal">logsecond</i> and <i style="mso-bidi-font-style:
normal">logfilsiz</i> configuration parameters.</span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:0in;margin-bottom:
.0001pt;line-height:normal"><span style="mso-bidi-font-size:12.0pt">Log
spooling can be enabled by setting the <i style="mso-bidi-font-style:normal">hadr_spool_limit</i>
database configuration parameter. It specifies an upper limit on how much data
is written, or spooled, to disk if the log receive buffer fills up. The default
value of 0 means no spooling. The special value of -1 means unlimited spooling,
as much as supported by the disk space available in the active log path on the
standby.</span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:0in;margin-bottom:
.0001pt;line-height:normal"><span style="mso-bidi-font-size:12.0pt">When
configuring for log spooling, in addition to the extra disk space requirement
on standby, another consideration is that there could be a larger gap between
the log position of the primary and log replay on the standby, which might lead
to a longer takeover time because the standby cannot assume the role of the new
standby until the replay of the spooled logs finishes.</span></p>
<span style="mso-bidi-font-size:12.0pt">Note that
making use of log spooling does not compromise the HADR protection provided by
the HADR feature. Data from the primary is still replicated in log form to the
standby using the specified sync mode; it just takes time to apply (through log
replay) the data to the table spaces.</span><span style="mso-bidi-font-size:12.0pt"></span>
HADR
standby log spooling is a new feature in DB2® V10. This feature allows
transactions on the primary to make progress without having to wait for the log
replay on the standby. Log data that is sent by the primary is written, or
spooled, to disk on the...004883urn:lsid:ibm.com:blogs:entries-4f2129a4-7efa-423f-9d93-550cb9483a64DB2 for Linux, UNIX and Windows Availability Topics2018-01-10T09:49:55-05:00urn:lsid:ibm.com:blogs:entry-b1f5c1a6-202c-4b0e-b5c6-3fd282da3ae2HADR Synchronization mode reviewDale_McInnis060000PV6CactivefalseComment Entriesapplication/atom+xml;type=entryLikestrue2012-04-07T07:21:06-04:002012-04-09T17:26:48-04:00
<p class="MsoNormal"><span class="keyword"><b style="mso-bidi-font-weight:normal">SYNC</b></span><b style="mso-bidi-font-weight:normal"> (synchronous)</b></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:normal">This mode
provides the greatest protection against transaction loss. However using it may
result in the longest transaction response time among the four modes. </p>
<p class="MsoNormal" style="margin-left:.5in;line-height:normal">In this mode,
log writes are considered successful only when logs have been written to log
files on the primary database and when the primary database has received
acknowledgement from the standby database that the logs have also been written
to log files on the standby database. The log data is guaranteed to be stored
at both sites.</p>
<p class="MsoNormal"><span class="keyword"><b style="mso-bidi-font-weight:normal">NEARSYNC</b></span><b style="mso-bidi-font-weight:normal"> (near synchronous)</b></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:normal">While this mode
has a shorter transaction response time than synchronous mode, it also provides
slightly less protection against transaction loss. </p>
<p class="MsoNormal" style="margin-left:.5in;line-height:normal">In this mode,
log writes are considered successful only when the log records have been
written to the log files on the primary database and when the primary database
has received acknowledgement from the standby system that the logs have also
been written to main memory on the standby system. Loss of data occurs only if
both sites fail simultaneously and if the target site has not transferred to
nonvolatile storage all of the log data that it has received.</p>
<p class="MsoNormal"><span class="keyword"><b style="mso-bidi-font-weight:normal">ASYNC</b></span><b style="mso-bidi-font-weight:normal"> (asynchronous)</b></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:normal">Compared with
the <span class="keyword">SYNC</span> and <span class="keyword">NEARSYNC</span>
modes, the <span class="keyword">ASYNC</span> mode results in shorter transaction
response times but may cause greater transaction losses if the primary database
fails</p>
<p class="p" style="margin-left:.5in">In <span class="keyword">ASYNC</span> mode,
log writes are considered successful only when the log records have been
written to the log files on the primary database and have been delivered to the
TCP layer of the primary system's host machine. Because the primary system does
not wait for an acknowledgement from the standby system, transactions may be
considered committed when they are still on their way to the standby database.</p>
<p class="MsoNormal"><span class="keyword"><b style="mso-bidi-font-weight:normal">SUPERASYNC</b></span><b style="mso-bidi-font-weight:normal"> (super asynchronous)</b></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:normal">This mode has
the shortest transaction response time but also has the highest probability of
transaction losses if the primary system fails. This mode is useful when one does
not want transactions to be blocked or experience elongated response times due
to network interruptions or congestion.</p><p class="p" style="margin-left:.5in">In this mode, the HADR pair will never be
in peer state or disconnected peer state. The log writes are considered
successful as soon as the log records have been written to the log files on the
primary database. Because the primary database does not wait for
acknowledgement from the standby database, transactions are considered
committed irrespective of the state of the replication of that transaction.</p>
<p class="p" style="margin-left:.5in">Since the transaction commit operations on
the primary database are not affected by the relative slowness of the HADR
network or the standby HADR server, the log gap between the primary database
and the standby database may continue to increase. It is important to monitor
the log gap as it is an indirect measure of the potential number of
transactions that could be lost should a true disaster occur on the primary
system. </p>
<p class="p" style="margin-left:.5in">In disaster recovery scenarios, any
transactions committed during the log gap would not be available to the standby
database. Therefore, monitor the log gap by using the <span class="keyword"><i style="mso-bidi-font-style:normal">hadr_log_gap</i></span> monitor element. If
it occurs that the log gap is not acceptable, investigate the network
interruptions or the relative speed of the standby database node and take
corrective measures to reduce the log gap.</p>
SYNC (synchronous) This mode
provides the greatest protection against transaction loss. However using it may
result in the longest transaction response time among the four modes. In this mode,
log writes are considered successful only when logs have been...1010815urn:lsid:ibm.com:blogs:entries-4f2129a4-7efa-423f-9d93-550cb9483a64DB2 for Linux, UNIX and Windows Availability Topics2018-01-10T09:49:55-05:00urn:lsid:ibm.com:blogs:entry-cadf50fc-ffe3-4bab-9616-63f5a73590d7HADR - not a 1 trick ponyDale_McInnis060000PV6CactivefalseComment Entriesapplication/atom+xml;type=entryLikestrue2012-04-07T07:19:40-04:002012-04-09T17:25:47-04:00
<p class="MsoNormal" style="line-height:normal">There are a number of ways that the
HADR standby or standbys can be used beyond their HA or DR purpose. </p>
<p class="MsoNormal"><b style="mso-bidi-font-weight:normal">Reads on standby</b></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:normal">The reads on
standby feature can be used to direct read-only workload to one or more standby
databases without affecting the HA or DR responsibility of the standby. This
feature can help reduce the workload on the primary without affecting the main
responsibility of the standby. </p>
<p class="MsoNormal" style="margin-left:.5in;line-height:normal">Only the primary
database is accessible unless the reads on standby feature is enabled on one or
more of the standbys. Applications connecting to the standby database do not
affect the <span class="resultoftext">availability</span> of the standby in the
case of a failover. </p>
<p class="MsoNormal"><b style="mso-bidi-font-weight:normal">Delayed replay</b></p>
<p class="MsoNormal" style="margin-left:.5in;line-height:normal">Delayed replay can
be used to specify that a standby database is to remain at an earlier point in
time than the primary, in terms of log replay. If data is lost or corrupted on
the primary, it can be recovered on the time delayed standby. </p>
<p class="MsoNormal"><b style="mso-bidi-font-weight:normal">Rolling updates and
upgrades</b></p>
Using an HADR
setup, one can make various types of upgrades and DB2® fix pack updates to your
databases without an outage. With multiple standby mode enabled, an upgrade can
be performed while maintaining the protection provided by HADR
There are a number of ways that the
HADR standby or standbys can be used beyond their HA or DR purpose. Reads on standby The reads on
standby feature can be used to direct read-only workload to one or more standby
databases without affecting the HA or DR...003435urn:lsid:ibm.com:blogs:entries-4f2129a4-7efa-423f-9d93-550cb9483a64DB2 for Linux, UNIX and Windows Availability Topics2018-01-10T09:49:55-05:00urn:lsid:ibm.com:blogs:entry-a52e7f8d-fee3-4749-bf00-0cea4bd6d4deHADR - what do I need to consider?Dale_McInnis060000PV6CactivefalseComment Entriesapplication/atom+xml;type=entryLikestrue2012-04-07T07:18:29-04:002012-04-09T17:24:49-04:00
<p class="MsoNormal" style="line-height: normal;">The high <span class="resultoftext">availability</span> disaster recovery (HADR) feature
provides a high <span class="resultoftext">availability</span> solution for both
partial and complete site failures. HADR protects against data loss by
replicating data changes from the primary database (source), to one or more standby
databases (targets).</p><p class="MsoNormal" style="line-height: normal;">A partial site failure can be
caused by a hardware, network, or software failure. Without HADR, a partial
site failure requires restarting the database management system (DBMS) server
that contains the database. The length of time that it takes to restart the
database and the server where it is located is unpredictable. It may take
several minutes before the database is brought back to a consistent state and
made <span class="resultoftext">avail</span>able. With HADR, a standby database will
assume control in seconds. In addition, the system can redirect the clients
that used the original primary database to the new primary database by using
automatic client reroute or retry logic in the application.</p><p class="MsoNormal" style="line-height: normal;">A complete site failure will
occur when a disaster, such as fire, causes the entire site to be destroyed.
For example, the primary database may be located at your primary data center in
one city, and a standby database might be located at your second data center in
another city. If a disaster occurs at the primary site, data <span class="resultoftext">availability</span> is maintained by having the remote
standby database take over as the primary database with full DB2® functionality.
After a takeover operation occurs, one can bring the original primary database
back up and return it to its primary database status; this is known as<i style="mso-bidi-font-style:normal"> <i>failback</i></i>. One can initiate a
failback if one can make the old primary database consistent with the new
primary database. After reintegration of the old primary database into the HADR
setup as a standby database, one can switch the roles of the databases to
enable the original primary database to once again be the primary database. </p><p class="MsoNormal">With HADR, the level of
protection from potential loss of data is based on configuration and topology
choices. Some of the key choices will now be detailed: </p><p class="MsoNormal"><b style="mso-bidi-font-weight:normal">What level of
synchronization will one use?</b></p>
<p class="MsoNormal" style="line-height:normal">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. One can choose from four different synchronization modes. In order
of most to least protection, these modes are SYNC, NEARSYNC, ASYNC, and
SUPERASYNC. </p>
<p class="MsoNormal"><b style="mso-bidi-font-weight:normal">Will one use a peer
window?</b></p>
<p class="MsoNormal" style="line-height:normal">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 &quot;disconnected
peer&quot; state, the failover to standby will have zero data loss. This
feature provides the greatest protection. </p>
<p class="MsoNormal"><b style="mso-bidi-font-weight:normal">How many standbys
will one deploy?</b></p>
<p class="MsoNormal" style="line-height:normal">With HADR, one can use either
single standby mode or multiple standby mode. With multiple standbys, a user can
achieve both high <span class="resultoftext">availability</span> and disaster
recovery objectives with a single technology </p>The high availability disaster recovery (HADR) feature
provides a high availability solution for both
partial and complete site failures. HADR protects against data loss by
replicating data changes from the primary database (source), to one or more...003529urn:lsid:ibm.com:blogs:entries-4f2129a4-7efa-423f-9d93-550cb9483a64DB2 for Linux, UNIX and Windows Availability Topics2018-01-10T09:49:55-05:00urn:lsid:ibm.com:blogs:entry-b5d12f58-06f5-4366-83bd-05c8a9ae3e4cDB2 V 10 HADR Monitoring sample outputDale_McInnis060000PV6CactivefalseComment Entriesapplication/atom+xml;type=entryLikestrue2012-04-05T12:35:26-04:002012-04-09T17:22:48-04:00<div><span class="css88250a40-8f0a-1028-930f-db07163b51b2indicatortag"><b /></span><span class="cssa5774ac0-d758-102a-9710-ee322f01ca37indicatortag">The following query
is issued to a primary database with three standbys. Three </span><span class="css88250a40-8f0a-1028-930f-db07163b51b2indicatortag">rows are returned.
The HADR_ROLE column represents the role of the database to which the query is
issued. Therefore it is PRIMARY on all rows.</span></div>
<p style="margin:0in;margin-bottom:.0001pt"><span class="css88250a40-8f0a-1028-930f-db07163b51b2indicatortag"><span style="font-size:7.5pt;font-family:&quot;Courier New&quot;">db2 &quot;select HADR_ROLE,
STANDBY_ID, HADR_STATE, varchar(PRIMARY_MEMBER_HOST,20) as PRIMARY_MEMBER_HOST,
varchar(STANDBY_MEMBER_HOST,20) as STANDBY_MEMBER_HOST from table
(mon_get_hadr(NULL))&quot;</span></span><span style="font-size:7.5pt" /></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:7.5pt"> </span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span class="css88250a40-8f0a-1028-930f-db07163b51b2indicatortag"><span style="font-size:7.5pt;font-family:&quot;Courier New&quot;">HADR_ROLE
STANDBY_ID
HADR_STATE
PRIMARY_MEMBER_HOST STANDBY_MEMBER_HOST</span></span><span style="font-size:7.5pt" /></p>
<p style="margin:0in;margin-bottom:.0001pt"><span class="css88250a40-8f0a-1028-930f-db07163b51b2indicatortag"><span style="font-size:7.5pt;font-family:&quot;Courier New&quot;">------------- ----------
----------------------- -------------------- --------------------</span></span><span style="font-size:7.5pt" /></p>
<p style="margin:0in;margin-bottom:.0001pt"><span class="css88250a40-8f0a-1028-930f-db07163b51b2indicatortag"><span style="font-size:7.5pt;font-family:&quot;Courier New&quot;">PRIMARY
1
PEER
beaverton-a
beaverton-b </span></span><span style="font-size:7.5pt" /></p>
<p style="margin:0in;margin-bottom:.0001pt"><span class="css88250a40-8f0a-1028-930f-db07163b51b2indicatortag"><span style="font-size:7.5pt;font-family:&quot;Courier New&quot;">PRIMARY
2 REMOTE_CATCHUP </span></span><span class="-8f0a-1028-930f-db07163b51b2"><span style="font-size:7.5pt;
font-family:&quot;Courier New&quot;">beaverton</span></span><span class="-8f0a-1028-930f-db07163b51b2"><span style="font-size:7.5pt;font-family:
&quot;Courier New&quot;">-a</span></span><span class="css88250a40-8f0a-1028-930f-db07163b51b2indicatortag"><span style="font-size:7.5pt;font-family:&quot;Courier New&quot;">
portland</span></span><span style="font-size:7.5pt" /></p>
<p style="margin:0in;margin-bottom:.0001pt"><span class="css88250a40-8f0a-1028-930f-db07163b51b2indicatortag"><span style="font-size:7.5pt;font-family:&quot;Courier New&quot;">PRIMARY
3 REMOTE_CATCHUP </span></span><span class="-8f0a-1028-930f-db07163b51b2"><span style="font-size:7.5pt;
font-family:&quot;Courier New&quot;">beaverton</span></span><span class="-8f0a-1028-930f-db07163b51b2"><span style="font-size:7.5pt;font-family:
&quot;Courier New&quot;">-a</span></span><span class="css88250a40-8f0a-1028-930f-db07163b51b2indicatortag"><span style="font-size:7.5pt;font-family:&quot;Courier New&quot;">
toronto</span></span><span style="font-size:7.5pt" /></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:7.5pt"> </span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span class="css88250a40-8f0a-1028-930f-db07163b51b2indicatortag"><span style="font-size:7.5pt;font-family:&quot;Courier New&quot;">3 record(s) selected.</span></span><span style="font-size:7.5pt" /></p>
<p><span class="cssa5774ac0-d758-102a-9710-ee322f01ca37indicatortag">Example 2:</span></p><p><span class="cssa5774ac0-d758-102a-9710-ee322f01ca37indicatortag">The
following query is issued to a standby database (with reads on standby
enabled). The standby only knows about its own primary. Only one row is
returned even if the standby is part of a multiple standby system. STANDBY_ID
is always zero when a query is issued to a standby</span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span class="css88250a40-8f0a-1028-930f-db07163b51b2indicatortag"><span style="font-size:7.5pt;font-family:&quot;Courier New&quot;">db2 &quot;select HADR_ROLE,
STANDBY_ID, HADR_STATE, varchar(PRIMARY_MEMBER_HOST,20) as PRIMARY_MEMBER_HOST,
varchar(STANDBY_MEMBER_HOST,20) as STANDBY_MEMBER_HOST from table
(mon_get_hadr(NULL))&quot;</span></span><span style="font-size:7.5pt" /></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:7.5pt"> </span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span class="css88250a40-8f0a-1028-930f-db07163b51b2indicatortag"><span style="font-size:7.5pt;font-family:&quot;Courier New&quot;">HADR_ROLE
STANDBY_ID HADR_STATE
PRIMARY_MEMBER_HOST STANDBY_MEMBER_HOST</span></span><span style="font-size:7.5pt" /></p>
<p style="margin:0in;margin-bottom:.0001pt"><span class="css88250a40-8f0a-1028-930f-db07163b51b2indicatortag"><span style="font-size:7.5pt;font-family:&quot;Courier New&quot;">------------- ----------
----------------------- -------------------- --------------------</span></span><span style="font-size:7.5pt" /></p>
<p style="margin:0in;margin-bottom:.0001pt"><span class="css88250a40-8f0a-1028-930f-db07163b51b2indicatortag"><span style="font-size:7.5pt;font-family:&quot;Courier New&quot;">STANDBY
0
PEER
</span></span><span class="-8f0a-1028-930f-db07163b51b2"><span style="font-size:7.5pt;font-family:
&quot;Courier New&quot;">beaverton</span></span><span class="-8f0a-1028-930f-db07163b51b2"><span style="font-size:7.5pt;font-family:
&quot;Courier New&quot;">-a beaverton-b </span></span><span style="font-size:7.5pt" /></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:7.5pt"> </span></p>
<div><span class="css88250a40-8f0a-1028-930f-db07163b51b2indicatortag"><span style="font-size:7.5pt;font-family:&quot;Courier New&quot;">1 record(s) selected</span></span> <br /></div>
The following query
is issued to a primary database with three standbys. Three rows are returned.
The HADR_ROLE column represents the role of the database to which the query is
issued. Therefore it is PRIMARY on all rows. db2 &quot;select...002927urn:lsid:ibm.com:blogs:entries-4f2129a4-7efa-423f-9d93-550cb9483a64DB2 for Linux, UNIX and Windows Availability Topics2018-01-10T09:49:55-05:00urn:lsid:ibm.com:blogs:entry-04a78a97-e5cd-4a20-8736-d60c970c584cDB2 V 10 HADR MonitoringDale_McInnis060000PV6CactivefalseComment Entriesapplication/atom+xml;type=entryLikestrue2012-04-05T12:30:15-04:002012-04-09T17:18:54-04:00<div><span style="color:#222222">In DB2 Version 10.1, HADR monitoring has been enhanced to
support multiple standby databases, as well as provide better performance
monitoring for single and multiple standby systems.</span></div><div> </div><div><div class="entryContentContainer">
<span class="cssa5774ac0-d758-102a-9710-ee322f01ca37indicatortag"><wbr />A new table function,
MON_GET_HADR has been added. &quot;<wbr />db2pd -hadr&quot;<wbr /> output content and format
has been updated. The two interfaces return identical information. The table
function uses standard SQL interface, so it is very flexible. It can be queried
from any SQL client and the output can be further processed by SQL filter,
join, aggregate, etc. In comparison, db2pd can only be issued on the database
host machine. But db2pd is lightweight</span><span class="css88250a40-8f0a-1028-930f-db07163b51b2indicatortag"><wbr />, </span><span class="cssa5774ac0-d758-102a-9710-ee322f01ca37indicatortag"><wbr />works on reads on
standby disabled databases</span><span class="css88250a40-8f0a-1028-930f-db07163b51b2indicatortag"><wbr />, and can be easily
incorporated into admin scripts.</span><span class="css88250a40-8f0a-1028-930f-db07163b51b2indicatortag"><wbr />All old interfaces
such as CLP database snapshot command, SNAPHADR view, SNAP_GET_HADR table
function, snapshot monitor element API are deprecated for HADR monitoring.</span><br /><span class="css88250a40-8f0a-1028-930f-db07163b51b2indicatortag"><span style="font-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;mso-fareast-font-family:
&quot;Times New Roman&quot;;mso-ansi-language:EN-US;mso-fareast-language:AR-SA;
mso-bidi-language:AR-SA"><wbr />Note: Unless reads on standby is enabled, </span><wbr /></span><wbr /><span class="cssa5774ac0-d758-102a-9710-ee322f01ca37indicatortag"><wbr /><span style="font-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;mso-fareast-font-family:
&quot;Times New Roman&quot;;mso-ansi-language:EN-US;mso-fareast-language:AR-SA;
mso-bidi-language:AR-SA"><wbr />the </span><wbr /></span><wbr /><span class="css88250a40-8f0a-1028-930f-db07163b51b2indicatortag"><wbr /><span style="font-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;mso-fareast-font-family:
&quot;Times New Roman&quot;;mso-ansi-language:EN-US;mso-fareast-language:AR-SA;
mso-bidi-language:AR-SA"><wbr />table function cannot be issued to a standby database.
Monitoring from the primary or using db2pd on the standby is recommended. </span><wbr /></span><wbr /></div> </div>
In DB2 Version 10.1, HADR monitoring has been enhanced to
support multiple standby databases, as well as provide better performance
monitoring for single and multiple standby systems. A new table function,
MON_GET_HADR has been added. &quot; db2pd...003102urn:lsid:ibm.com:blogs:entries-4f2129a4-7efa-423f-9d93-550cb9483a64DB2 for Linux, UNIX and Windows Availability Topics2018-01-10T09:49:55-05:00urn:lsid:ibm.com:blogs:entry-69119c9f-c267-4dfa-89f6-04ac778a19c7Welcome to my blog - what's new in V10 for HADRDale_McInnis060000PV6CactivefalseComment Entriesapplication/atom+xml;type=entryLikestrue2012-04-05T10:58:57-04:002012-04-05T10:58:57-04:00<div>Welcome to my first attempt at blogging. The intent of this blog is to discuss the availability aspects of DB2 LUW as well as share some tips and tricks to help you out</div><div> </div><div>So lets start out with a quick overview of what is new in the availability area for DB2 10. The biggest area of improvement in the availability arena is around HADR, here is a laundry list of the enhancements and in my next blog entry I will describe each in detail:</div><div> </div><div><ul><li>Support for multiple standbys - up to 3</li><li>Log spooling on the standby</li><li>Time delay on the standby </li><li>SuperAsync mode</li><li>Semi-dynamic HADR configuration parameters</li><li>New MON_GET_HADR table function</li></ul><p>Some pureScale availability enhancements include:</p><div><ul><li>Table space level granularity for recovery operations</li><li>db2cluster command to support instance domain repair and automatic failback control </li></ul><p>Thanks for reading and I look forward to sharing my thoughts with you</p><div> </div><div>Dale McInnis<br />DB2 LUW Availability Architect.<br /> </div></div></div>
Welcome to my first attempt at blogging. The intent of this blog is to discuss the availability aspects of DB2 LUW as well as share some tips and tricks to help you out So lets start out with a quick overview of what is new in the availability area for DB2...029433urn:lsid:ibm.com:blogs:entries-4f2129a4-7efa-423f-9d93-550cb9483a64DB2 for Linux, UNIX and Windows Availability Topics2018-01-10T09:49:55-05:00