<p>The 4.3 release removes support for logs-only replication clients. Use
of the DB_REP_LOGSONLY flag to the <ahref="../api_reference/C/repstart.html"class="olink">DB_ENV->rep_start()</a> should be replaced
with the <ahref="../api_reference/C/repmgrstart.html#repmgrstart_DB_REP_CLIENT"class="olink">DB_REP_CLIENT</a> flag.</p>
<p>The 4.3 release adds two new arguments to the <ahref="../api_reference/C/repelect.html"class="olink">DB_ENV->rep_elect()</a> method,
<spanclass="bold"><strong>nvotes</strong></span> and <spanclass="bold"><strong>flags</strong></span>. The <spanclass="bold"><strong>nvotes</strong></span> argument sets the
required number of replication group members that must participate in
an election in order for a master to be declared. For backward
compatibility, set the <spanclass="bold"><strong>nvotes</strong></span> argument to 0. The flags argument
is currently unused and should be set to 0. See <ahref="../api_reference/C/repelect.html"class="olink">DB_ENV->rep_elect()</a> method or
"Replication Elections" for more information.</p>
<p>In the 4.3 release it is no longer necessary to do a database
environment hot backup to initialize a replication client. All that is
needed now is for the client to join the replication group. Berkeley DB will
perform an internal backup from the master to the client automatically
and will run recovery on the client to bring it up to date with the
