<div class="docbook"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">10.11. Reset Group Information</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Java-Broker-High-Availability-Backup.html">Prev</a> </td><th width="60%" align="center">Chapter 10. High Availability</th><td width="20%" align="right"> <a accesskey="n" href="Java-Broker-Backup-And-Recovery.html">Next</a></td></tr></table><hr /></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="Java-Broker-High-Availability-Reset-Group-Infomational"></a>10.11. Reset Group Information</h2></div></div></div><p>BDB JE internally stores details of the group within its database. There are some
      circumstances when resetting this information is useful.</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>Copying data between environments (e.g. production to UAT)</p></li><li class="listitem"><p>Some disaster recovery situations where a group must be recreated on new
            hardware</p></li></ul></div><p>This is not an normal operation and is not usually required</p><p>The following command replaces the group table contained within the JE logs files with the
      provided information. </p><div class="example"><a id="d0e10317"></a><p class="title"><strong>Example 10.1. Resetting of replication group with <code class="classname">DbResetRepGroup</code></strong></p><div class="example-contents"><div class="cmdsynopsis"><p><code class="command">java</code>   -cp je-7.4.5.jar   com.sleepycat.je.rep.util.DbResetRepGroup   -h <em class="replaceable"><code>path/to/jelogfiles</code></em> <br />  -groupName <em class="replaceable"><code>newgroupname</code></em>   -nodeName <em class="replaceable"><code>newnodename</code></em>   -nodeHostPort <em class="replaceable"><code>newhostname:5000</code></em> </p></div></div></div><br class="example-break" /><p>The modified log files can then by copied into
        <code class="literal">${QPID_WORK}/&lt;nodename&gt;/config</code> directory of a target Broker. Then
      start the Broker, and add a BDB HA Virtualhost node specify the same group name, node name and
      node address. You will then have a group with a single node, ready to start re-adding
      additional nodes as described above. </p></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Java-Broker-High-Availability-Backup.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="Java-Broker-High-Availability.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="Java-Broker-Backup-And-Recovery.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">10.10. Backups </td><td width="20%" align="center"><a accesskey="h" href="Apache-Qpid-Broker-J-Book.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 11. Backup And Recovery</td></tr></table></div></div>