<div dir="ltr">Thanks guys, I should have spelunked the archive a little bit :)</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 22, 2014 at 12:01 PM, Brian Meade <span dir="ltr"><<a href="mailto:bmeade90@vt.edu" target="_blank">bmeade90@vt.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Use the formula on <a href="https://supportforums.cisco.com/document/52421/troubleshooting-cucm-database-replication-linux-appliance-model" target="_blank">https://supportforums.cisco.com/document/52421/troubleshooting-cucm-database-replication-linux-appliance-model</a> under "<span style="color:rgb(51,51,51);font-family:Arial,sans-serif;line-height:20px;outline:none">Replication Timeout Design Estimation".</span><div>
<span style="color:rgb(51,51,51);font-family:Arial,sans-serif;line-height:20px;outline:none"><br></span></div><div><span style="color:rgb(51,51,51);font-family:Arial,sans-serif;line-height:20px;outline:none">If that formula gives you more than 300 seconds, increase the repltimeout.</span></div>
<span class="HOEnZb"><font color="#888888">
<div><span style="color:rgb(51,51,51);font-family:Arial,sans-serif;line-height:20px;outline:none"><br></span></div><div><span style="color:rgb(51,51,51);font-family:Arial,sans-serif;line-height:20px;outline:none">Brian</span></div>
</font></span></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On Tue, Apr 22, 2014 at 11:26 AM, Ed Leatherman <span dir="ltr"><<a href="mailto:ealeatherman@gmail.com" target="_blank">ealeatherman@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">Reviewing some docs for upgrading my primary production cluster from 8 to 9.1. What constitutes a "large cluster" wrt to the db replication timeout?<div>
<br></div><div><ul style="line-height:14.399999618530273px;font-size:12px;font-family:Arial,Helvetica,sans-serif">
<li style="margin-top:0.5em;margin-bottom:0.5em;line-height:1.2em"><a name="1458a2bfebc75c64_1458a23be147f881_CUCM_RF_PE243493_00__li_B3B9A27A062C4E89B81204EBCD30C3DF"> </a>Use the <span><span style="font-weight:bold">utils dbreplication setrepltimeout</span></span> CLI command to increase the database replication timeout value when upgrading large clusters so that more subscriber nodes have sufficient time to request replication. When the timer expires, the first subscriber node, plus all other subscriber nodes that requested replication within that time period, begin a batch data replication with the publisher node. The default database replication timeout value is 300 (5 minutes). Restore the timeout to the default value after the entire cluster upgrades and the subscriber nodes have successfully set up replication. For more information, see the <cite>Command Line Interface Guide for Cisco Unified Communications Solutions</cite>.</li>
<span><font color="#888888">
</font></span></ul><span><font color="#888888"><div><br></div>-- <br>Ed Leatherman<br>
</font></span></div></div>
<br></div></div><div class="">_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></div></blockquote></div><br></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Ed Leatherman<br>
</div>