<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Transitional//EN">
<HTML>
<HEAD>
  <!--
    *************************************************************************************
    * Copyright (c) 2005 VERITAS Software Corporation. All rights reserved. *

      For third-party license citations, please see the bottom of this file.
    *************************************************************************************
  -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="TEMPLATEBASE" content="vx_vxhelp_2005c">
<meta name="LASTUPDATED" content="06/14/05 13:33:58">
<meta name="PRODUCTNAME" content="VERITAS Software Documentation">
<meta name="FILENAME" content="ch9tranprirole.fm">
     
<title>Failing Back to the Original Primary</title>

</HEAD>

<BODY bgcolor="#FFFFFF" link="#000066" vlink="#0000ff" marginheight="0" topmargin="0">
<basefont=1>

<a name="114209"></a>

<div align="left">
<table border="0" cellspacing="0" cellpadding="0" width="100%">
 <tr>
   <td height="2" border="0" cellspacing="0" cellpadding="0" colspan="2" bgcolor="#000000">
   </td>
 </tr>
 <tr>
   <td height="15" width="50%" border="0" cellspacing="0" cellpadding="0" bgcolor="#cccccc">
    <img src="images/vxsymbol.gif" height="20" width="31" border="0" cellspacing="0" cellpadding="0" align="left">
     
     
   </td>
   <td align="right" width="50%" bgcolor="#cccccc">

<!-- Header Breadcrumbs -->
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="-2">&lt;&nbsp;<a href="ch9tranprirole_vvr101_114096.html" title="Previous - Taking Over from an Original Primary">Previous</a>&nbsp;&nbsp;|&nbsp;&nbsp;<a href="vea_vvr103_113895.html" title="Next - Administering VVR Using VVR VEA">Next</a>
&nbsp;&gt;&nbsp;&nbsp;</font>
   </td>
 </tr>

 <tr>
  <td bgcolor="#CCCCCC" colspan="2" height="15" align="right">
  <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="1">Product:  
<a href="vvr_splashpage_docCD_vvr1_103036.vxhd" title="Volume Replicator Guides title page ">Volume Replicator Guides</a>
  &nbsp;&nbsp;
  </font>
  </td>
 </tr>
 <tr>
  <td bgcolor="#CCCCCC" colspan="2" height="15" align="right">
  <font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="1">Manual:  
<a href="vvr_ag_hpux_titlepage_docCD_vvr41_73700.vxhd" title="Volume Replicator 4.1 Administrator's Guide title page ">Volume Replicator 4.1 Administrator's Guide</a>
  &nbsp;&nbsp;
  </font>
  </td>
 </tr>


</table>
</div>

<div align="left">
 <table border="0" width="100%" bgcolor="#FFFFFF">
  <tr>
   <td width="100%" valign="top" bgcolor="#FFFFFF">

<!-- Start Main Topic Content -->
        <a name="startcontent"></a>
	
<h1><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="+1" color="#000000"><a name="114209"></a> Failing Back to the Original Primary</font>
</h1>
         
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114210"></a>After an unexpected failure, a failed Primary host might start up to find that one of its Secondaries has been promoted to a Primary by a takeover. This happens when a Secondary of this Primary has taken over the Primary role because of the unexpected outage on this Primary. The process of transferring the role of the Primary back to this original Primary is called <em>failback</em>.</font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114214"></a>VVR provides the following methods to fail back to the original Primary:</font>
</p>

<p>
<ul type="disc"><li><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114218"></a><a href="ch9tranprirole_vvr102_114209.html#114233">Failing Back Using Fast Failback Synchronization</a></font>
</li>
<li><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114222"></a><a href="ch9tranprirole_vvr102_114209.html#114282">Failing Back Using Difference-Based Synchronization</a></font>
</li>
<hr noshade size="2" width="100%" color="#000000">
<img src="images/note.gif" alt="Note " height="16" width="16">&nbsp;
<font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000">
<a name="114223"></a><b>Note  &nbsp;&nbsp;</b>
</font>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2" color="#000000">We recommend that you use the fast failback synchronization method.
</font>
<hr noshade size="2" width="100%" color="#000000">
</ul>
</p>



<h2><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="3" color="#000000"><a name="114225"></a>Fast Failback Versus Difference-Based Synchronization</font>
</h2>
 
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114226"></a>In the case of fast failback, the data blocks that changed while the original Primary was unavailable are tracked using the DCM for each volume. Difference-based synchronization computes MD5 checksums for a fixed size data block on the Primary and Secondary data volumes, compares it, and then determines whether this data block needs to be transferred from the Primary data volume to the Secondary data volume. The fast failback feature is recommended over the difference-based synchronization for the following reasons:</font>
</p>

<p>
<ul type="disc"><li><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114227"></a>For difference-based synchronization, all the blocks on all the Primary and Secondary data volumes are read; in the case of fast failback, only the blocks that changed on the new Primary are read and hence the number of read operations required is smaller.</font>
</li>
<li><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114228"></a>For difference-based synchronization, the differences are determined by computing and comparing checksum of each of the data chunks on the Secondary and Primary; in the case of fast failback, there is no need to compute checksum because the differences are tracked as they happen, which makes fast failback faster.</font>
</li>
</ul>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114229"></a>The following sections describe each of the above methods for failing back to the original Primary.</font>
</p>




<h2><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="3" color="#000000"><a name="114233"></a>Failing Back Using Fast Failback Synchronization</font>
</h2>
 
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114234"></a>We recommend that you use the fast failback synchronization method. This procedure assumes that the fast failback feature was enabled on the new Primary when takeover was performed. Failing back to the original Primary using fast failback involves the following steps:</font>
</p>

<ol>
<li value="1">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114235"></a>Converting the original Primary to an acting Secondary, as shown in the <br><font face="Courier New, Courier, sansserif, sans serif" size="2">vxprint&nbsp;-l&nbsp;</font><font face="Courier New, Courier, sansserif, sans serif" size="2"><em>rvgname</em></font> output, and replaying the DCM or SRL of the original Primary to set bits in the DCM of the new Primary. This is performed automatically when the Primary recovers, unless fast failback was disabled during the takeover.
</font>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114236"></a>It is possible that the Primary and Secondary data volumes are not up-to-date because all updates to the original Primary might not have reached the Secondary before the takeover. The failback process takes care of these writes by replaying the SRL or DCM of the original Primary. After the original Primary detects that a takeover has occurred, the new Primary uses information in the DCM or SRL of the original Primary to set bits in its DCM for any blocks that changed on the original Primary before the takeover. You can use the vxrlink status command to monitor the progress of the DCM replay. </font>
</p>
<li value="2">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114237"></a>Converting the original Primary to Secondary and synchronizing the data volumes on the original Primary with the data volumes on the new Primary using the <font face="Courier New, Courier, sansserif, sans serif" size="2">vradmin</font>&nbsp;<font face="Courier New, Courier, sansserif, sans serif" size="2">fbsync</font> command. This command replays the failback log to synchronize the data volumes. The blocks that changed on the original Primary are resynchronized with the new Primary after the DCM of the new Primary is replayed. During the resynchronization, the data from the data volumes on the new Primary is transferred to the data volumes on the original Primary.
</font>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="150247"></a>This step is not required if the <font face="Courier New, Courier, sansserif, sans serif" size="2">-autofb</font> option was used at the time of the takeover. The data on the original Primary data volumes is inconsistent for the duration of the replay. To keep a consistent copy of the original Primary data, take a snapshot of the data volumes before starting the replay. When using the <font face="Courier New, Courier, sansserif, sans serif" size="2">vradmin&nbsp;</font><font face="Courier New, Courier, sansserif, sans serif" size="2">fbsync</font> command, you can also specify the <font face="Courier New, Courier, sansserif, sans serif" size="2">cache</font> or the <font face="Courier New, Courier, sansserif, sans serif" size="2">cachesize</font> option so that a space-optimized snapshot of the original Primary data volumes is automatically created. If the RVG on the original Primary has VxVM ISP volumes, then you cannot use the <font face="Courier New, Courier, sansserif, sans serif" size="2"><em>cachesize</em></font> attribute.</font>
</p>
<li value="3">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114238"></a>Migrating the Primary Role back to the original Primary and starting replication.
</font>
</ol>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114240"></a>In the following illustration, the original Primary <font face="Courier New, Courier, sansserif, sans serif" size="2">seattle</font> has recovered and is now the acting Secondary. The new Primary <font face="Courier New, Courier, sansserif, sans serif" size="2">london</font> uses information in the DCM or SRL of the original Primary to set bits in its DCM for any blocks that changed on the original Primary before the takeover.</font>
</p>

<a name="no_figure_caption0"> </a>  <!-- Start Image Code -->
  <!--
   CAUTION: If graphics output is truncated, change the paper size setting 
   of your WebWorks Rasterizer printer driver from "A4" to "Letter" and regenerate your project.
  -->

<p>
<a href="ch9_migration35_t.htm">
<img src="images/ch9_migration35.gif" width="110" height="82" border="0" ></a>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="1"><em>Click the thumbnail above to view full-sized image. </font></em></p>
   <!-- End Image Code -->



<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114247"></a>In the following illustration, the fast failback feature was enabled on the new Primary <font face="Courier New, Courier, sansserif, sans serif" size="2">london</font> when takeover was performed. </font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114248"></a>The original Primary <font face="Courier New, Courier, sansserif, sans serif" size="2">seattle</font> is being resynchronized using the failback log.</font>
</p>

<a name="no_figure_caption1"> </a>  <!-- Start Image Code -->
  <!--
   CAUTION: If graphics output is truncated, change the paper size setting 
   of your WebWorks Rasterizer printer driver from "A4" to "Letter" and regenerate your project.
  -->

<p>
<a href="ch9_tofailback6_t.htm">
<img src="images/ch9_tofailback6.gif" width="110" height="82" border="0" ></a>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="1"><em>Click the thumbnail above to view full-sized image. </font></em></p>
   <!-- End Image Code -->






<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="114254"></a>Example 1---Failing Back to the Original Primary Using Fast Failback</font>
</h3>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114255"></a>In this example, the Primary host <font face="Courier New, Courier, sansserif, sans serif" size="2">seattle</font> has restarted after an unexpected failure. After the failure, the original Primary <font face="Courier New, Courier, sansserif, sans serif" size="2">seattle</font> was taken over by the Secondary host <font face="Courier New, Courier, sansserif, sans serif" size="2">london</font>. Each data volume on the Secondary <font face="Courier New, Courier, sansserif, sans serif" size="2">london</font> has a Data Change Map (DCM) associated with it. As a result, fast failback is enabled on <font face="Courier New, Courier, sansserif, sans serif" size="2">london</font>. </font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114256"></a>An application is running on <font face="Courier New, Courier, sansserif, sans serif" size="2">london</font> and incoming writes are being logged to its DCM. This example shows how to fail back to the original Primary <font face="Courier New, Courier, sansserif, sans serif" size="2">seattle</font> using the fast failback feature.</font>
</p>

</ol>
<p><img src="images/stepintro.gif" height="16" width="16">
<font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="114257"></a>&nbsp;&nbsp;<b>To fail back to the original Primary seattle using fast failback</b></font>
</p>
<ol>
<li value="1">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114258"></a>Examine the original Primary and make sure you want to convert the original Primary to Secondary.
</font>
<li value="2">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114259"></a>Convert the original Primary to Secondary and synchronize the data volumes in the original Primary RVG <font face="Courier New, Courier, sansserif, sans serif" size="2">hr_rvg</font> with the data volumes on the new Primary RVG <font face="Courier New, Courier, sansserif, sans serif" size="2">hr_rvg</font> on <font face="Courier New, Courier, sansserif, sans serif" size="2">london</font> using the fast failback feature. To synchronize the Secondary using fast failback, type the following command on the new Primary <font face="Courier New, Courier, sansserif, sans serif" size="2">london</font> or the original Primary <font face="Courier New, Courier, sansserif, sans serif" size="2">seattle</font>:
</font>
<br>
<font face="Courier New, Courier, sansserif, sans serif" size="2"><a name="114264"></a>&nbsp;&nbsp;#&nbsp;<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>vradmin</b></font>&nbsp;<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>-g&nbsp;hrdg&nbsp;[-wait]&nbsp;fbsync&nbsp;hr_rvg&nbsp;</b></font><font face="Courier New, Courier, sansserif, sans serif" size="2"><b>\</b></font>
</font>
<br>
<font face="Courier New, Courier, sansserif, sans serif" size="2"><a name="114265"></a><font face="Courier New, Courier, sansserif, sans serif" size="2"><b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[cache=</b></font><em>cacheobj</em>&nbsp;|&nbsp;<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>cachesize</b></font><em>=</em><em>size</em><font face="Courier New, Courier, sansserif, sans serif" size="2"><b>]</b></font>
</font>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114266"></a>When the synchronization completes, go to the next step. You can check the status of the synchronization using the <font face="Courier New, Courier, sansserif, sans serif" size="2">vxrlink</font> <font face="Courier New, Courier, sansserif, sans serif" size="2">status</font> command. The <font face="Courier New, Courier, sansserif, sans serif" size="2">-wait</font> option with the <font face="Courier New, Courier, sansserif, sans serif" size="2">vradmin</font> <font face="Courier New, Courier, sansserif, sans serif" size="2">fbsync</font> command can also be used to wait for the completion of the synchronization process. </font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114267"></a>The <font face="Courier New, Courier, sansserif, sans serif" size="2"><em>cache</em></font><em> </em>attribute specifies a name for the precreated cache object, on which the snapshots for the volumes in the specified RVG will be created. For more information on creating the cache object refer to the information provided in the section <a href="ch7admin_vvr89_115171.html#115365">Preparing the RVG Volumes for Snapshot Operation</a>. The <font face="Courier New, Courier, sansserif, sans serif" size="2"><em>cachesize</em></font> attribute specifies a default size for the cache object with respect to the source volume. You can specify only one of these attributes at one time with the <font face="Courier New, Courier, sansserif, sans serif" size="2">vradmin</font> <font face="Courier New, Courier, sansserif, sans serif" size="2">fbsync</font> to create one cache object for each snapshot.</font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114271"></a>The parameters <font face="Courier New, Courier, sansserif, sans serif" size="2"><em>cache</em></font> and <font face="Courier New, Courier, sansserif, sans serif" size="2"><em>cachesize</em></font> are optional. If you do not specify either of these parameters then the <font face="Courier New, Courier, sansserif, sans serif" size="2">vradmin</font> <font face="Courier New, Courier, sansserif, sans serif" size="2">fbsync</font> will convert the original Primary to a Secondary and synchronize the data volumes on the original Primary with the data volumes on the new Primary, without creating the snapshots.</font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114272"></a>This step is not required if the <font face="Courier New, Courier, sansserif, sans serif" size="2">-autofb</font> option was used at the time of takeover</font>
</p>
<li value="3">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114273"></a>At a convenient time, stop the application on the new Primary.
</font>
<li value="4">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114274"></a>Migrate the Primary role from the new Primary host <font face="Courier New, Courier, sansserif, sans serif" size="2">london</font> to the original Primary host <font face="Courier New, Courier, sansserif, sans serif" size="2">seattle</font> by typing the following command on any host in the RDS:
</font>
<br>
<font face="Courier New, Courier, sansserif, sans serif" size="2"><a name="114278"></a>&nbsp;&nbsp;#&nbsp;<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>vradmin&nbsp;-g&nbsp;hrdg&nbsp;migrate&nbsp;hr_rvg&nbsp;seattle</b></font>
</font>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114279"></a>Replication from the original Primary <font face="Courier New, Courier, sansserif, sans serif" size="2">seattle</font> to the original Secondary <font face="Courier New, Courier, sansserif, sans serif" size="2">london</font> is started by default.</font>
</p>
<li value="5">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="147799"></a>Restart the application on the original Primary <font face="Courier New, Courier, sansserif, sans serif" size="2">seattle</font>. Because the application was stopped properly before the migration, an application recovery is not required.
</font>
</ol>



<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="146676"></a>Example 2---Failing Back to the Original Primary Using Fast Failback in a Multiple Secondaries Setup </font>
</h3>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="147096"></a>In this example, the setup consists of two Secondaries, <font face="Courier New, Courier, sansserif, sans serif" size="2">london</font> and <font face="Courier New, Courier, sansserif, sans serif" size="2">tokyo</font>. The Primary host <font face="Courier New, Courier, sansserif, sans serif" size="2">seattle</font> has restarted after an unexpected failure. After the failure, the original Primary <font face="Courier New, Courier, sansserif, sans serif" size="2">seattle</font> was taken over by the Secondary host <font face="Courier New, Courier, sansserif, sans serif" size="2">london</font>. Each data volume on the Secondary <font face="Courier New, Courier, sansserif, sans serif" size="2">london</font> has a Data Change Map (DCM) associated with it. As a result, fast failback is enabled on <font face="Courier New, Courier, sansserif, sans serif" size="2">london</font>. </font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="147094"></a>If you had created RLINKs between the hosts <font face="Courier New, Courier, sansserif, sans serif" size="2">london</font> and <font face="Courier New, Courier, sansserif, sans serif" size="2">tokyo</font> when setting up the replication, you do not need to manually reconfigure the additional Secondary <font face="Courier New, Courier, sansserif, sans serif" size="2">tokyo&nbsp;</font>as a part of the RDS. It will automatically be added as a Secondary of the new Primary <font face="Courier New, Courier, sansserif, sans serif" size="2">london</font>. </font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="146729"></a>An application is running on <font face="Courier New, Courier, sansserif, sans serif" size="2">london</font> and incoming writes are being logged to its DCM. This example shows how to fail back to the original Primary <font face="Courier New, Courier, sansserif, sans serif" size="2">seattle</font> using the fast failback feature.</font>
</p>

<ol>
<li value="1">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="146710"></a>Perform <a href="ch9tranprirole_vvr102_114209.html#114258">step  1</a> to <a href="ch9tranprirole_vvr102_114209.html#114274">step  4</a> described in the example <a href="ch9tranprirole_vvr102_114209.html#114254">Example 1---Failing Back to the Original Primary Using Fast Failback</a>.
</font>
<li value="2">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="146688"></a>After migration, you must synchronize the additional secondary <font face="Courier New, Courier, sansserif, sans serif" size="2">tokyo</font> with the original Primary <font face="Courier New, Courier, sansserif, sans serif" size="2">seattle</font>. 
</font>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="147125"></a>On the original Primary <font face="Courier New, Courier, sansserif, sans serif" size="2">seattle</font>:</font>
</p>
<p>
<ul type="disc"><li><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="146690"></a>Synchronize the data volumes in the Secondary RVG <font face="Courier New, Courier, sansserif, sans serif" size="2">hr_rvg</font> on <font face="Courier New, Courier, sansserif, sans serif" size="2">tokyo</font> with the data volumes in the original Primary RVG <font face="Courier New, Courier, sansserif, sans serif" size="2">hr_rvg</font> using the difference-based synchronization and checkpoint. To do this, use the following command on any host in the RDS:</font>
</li>
<br>
<font face="Courier New, Courier, sansserif, sans serif" size="2"><a name="146691"></a>&nbsp;&nbsp;&nbsp;&nbsp;<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>#&nbsp;vradmin&nbsp;-g&nbsp;hrdg&nbsp;-c&nbsp;checkpt&nbsp;syncrvg&nbsp;hr_rvg&nbsp;tokyo</b></font>
</font>
<ul><p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="147166"></a>The <font face="Courier New, Courier, sansserif, sans serif" size="2">-c</font> option when used with the vradmin syncrvg command automatically starts a checkpoint with the specified name, <font face="Courier New, Courier, sansserif, sans serif" size="2">checkpt</font>, in this example. After the data volumes are synchronized the checkpoint is ended. </font>
</p>
</ul><li><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="147167"></a>Start replication to <font face="Courier New, Courier, sansserif, sans serif" size="2">tokyo</font> using the checkpoint created above:</font>
</li>
<br>
<font face="Courier New, Courier, sansserif, sans serif" size="2"><a name="147171"></a>&nbsp;&nbsp;&nbsp;#&nbsp;<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>vradmin</b></font>&nbsp;<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>-g&nbsp;hrdg&nbsp;-c&nbsp;checkpt&nbsp;startrep&nbsp;hr_rvg&nbsp;tokyo</b></font>
</font>
</ul>
</p>
<li value="3">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="146666"></a>Restart the application on the original Primary <font face="Courier New, Courier, sansserif, sans serif" size="2">seattle</font>. Because the application was stopped properly before the migration, an application recovery is not required.
</font>
</ol>



<h2><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="3" color="#000000"><a name="114282"></a>Failing Back Using Difference-Based Synchronization</font>
</h2>
 
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114283"></a>Failing back to the original Primary using difference-based synchronization involves the following steps:</font>
</p>

<ol>
<li value="1">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114284"></a>Converting the original Primary to a Secondary of the new Primary.
</font>
<li value="2">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114285"></a>Synchronizing the data volumes on the original Primary with the data volumes on the new Primary using difference-based synchronization using checkpoint. 
</font>
<li value="3">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114286"></a>Starting replication to the Secondary (original Primary) using checkpoint.
</font>
<li value="4">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114287"></a>Migrating the Primary Role to the original Primary and starting replication by default.
</font>
</ol>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114288"></a>The examples in the following section explain how to fail back to the original Primary using VVR.</font>
</p>




<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="114292"></a>Converting an Original Primary to a Secondary</font>
</h3>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114300"></a>VVR provides the <font face="Courier New, Courier, sansserif, sans serif" size="2">vradmin</font> <font face="Courier New, Courier, sansserif, sans serif" size="2">makesec</font> command to convert the original Primary to a Secondary. This command is only needed if fast failback was not enabled when the original takeover was performed. If fast failback was enabled, the original Primary will automatically be converted to a Secondary when DCM playback begins. Note that this command can be run only from the original Primary host where one of its original Secondaries has taken over the Primary role. </font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114304"></a>You can issue the <font face="Courier New, Courier, sansserif, sans serif" size="2">vradmin</font> <font face="Courier New, Courier, sansserif, sans serif" size="2">makesec</font> command in the failback procedure only if fast failback has not been enabled when taking over from the original Primary. Run this command when the original Primary restarts. Stop the application if it restarts automatically when the Primary restarts. The <font face="Courier New, Courier, sansserif, sans serif" size="2">vradmin</font> <font face="Courier New, Courier, sansserif, sans serif" size="2">makesec</font> command converts the original Primary to a Secondary RVG.</font>
</p>

<hr noshade size="2" width="100%" color="#000000">
<img src="images/tip.gif" alt="Tip " height="16" width="16">
<font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="114311"></a>&nbsp;<b>Tip  &nbsp;&nbsp;</b></font>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2" color="#000000">Before using the <font face="Courier New, Courier, sansserif, sans serif" size="2">vradmin</font> <font face="Courier New, Courier, sansserif, sans serif" size="2">makesec</font> command make sure you close all the applications running on the original Primary's data volumes. Also ensure that none of the data volumes are open.</font>
<hr noshade size="2" width="100%" color="#000000">
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114315"></a>The <font face="Courier New, Courier, sansserif, sans serif" size="2">vradmin</font> <font face="Courier New, Courier, sansserif, sans serif" size="2">makesec</font> command fails if the Secondary data volumes are not up-to-date or if there are some applications still running on the failed Primary's data volumes. Use the <font face="Courier New, Courier, sansserif, sans serif" size="2">-f</font> option to convert a failed Primary to a Secondary even when the Secondary data volumes are not up-to-date. If any of the failed Primary data volumes are open or have applications running on them, then using the <font face="Courier New, Courier, sansserif, sans serif" size="2">vradmin</font> <font face="Courier New, Courier, sansserif, sans serif" size="2">makesec</font> command with the <font face="Courier New, Courier, sansserif, sans serif" size="2">-f</font> option will fail. To proceed with the <font face="Courier New, Courier, sansserif, sans serif" size="2">vradmin</font> <font face="Courier New, Courier, sansserif, sans serif" size="2">makesec</font> command, first close the volumes or stop the applications as required. </font>
</p>

<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114323"></a>To convert an original Primary to a Secondary:</font>
</p>

<br>
<font face="Courier New, Courier, sansserif, sans serif" size="2"><a name="114327"></a>&nbsp;#&nbsp;<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>vradmin</b></font>&nbsp;<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>-g</b></font>&nbsp;<em>diskgroup</em><font face="Courier New, Courier, sansserif, sans serif" size="2"><b>&nbsp;makesec</b></font>&nbsp;<em>local_rvgname</em>&nbsp;<em>newprimary_name</em>
</font>
<blockquote>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114329"></a>The argument <font face="Courier New, Courier, sansserif, sans serif" size="2"><em>diskgroup</em></font> is the disk group on the local host.</font>
</blockquote>
<blockquote>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114330"></a>The argument <font face="Courier New, Courier, sansserif, sans serif" size="2"><em>local_rvgname</em></font> is the name of the RVG on the local host, that is, the original Primary and represents its RDS.</font>
</blockquote>
<blockquote>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114331"></a>The argument <font face="Courier New, Courier, sansserif, sans serif" size="2"><em>newprimary_name</em></font><em> </em>is the name of the new Primary host, that is, the previous Secondary host. Note that the <font face="Courier New, Courier, sansserif, sans serif" size="2"><em>newprimary_name</em></font> argument must be the same as the host name displayed with the Primary-Primary configuration error in the output of the <font face="Courier New, Courier, sansserif, sans serif" size="2">vradmin</font> <font face="Courier New, Courier, sansserif, sans serif" size="2">-l</font> <font face="Courier New, Courier, sansserif, sans serif" size="2">printrvg</font> command.</font>
</blockquote>



<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="114335"></a>Example 3---Failing Back to the Original Primary Using Difference-Based Synchronization</font>
</h3>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114336"></a>In this example, the Primary host <font face="Courier New, Courier, sansserif, sans serif" size="2">seattle</font> has restarted after an unexpected failure. After the failure, the original Primary <font face="Courier New, Courier, sansserif, sans serif" size="2">seattle</font> has been manually taken over by the Secondary host <font face="Courier New, Courier, sansserif, sans serif" size="2">london</font>. This example shows how to fail back to the original Primary <font face="Courier New, Courier, sansserif, sans serif" size="2">seattle</font> using difference-based synchronization. For more information, see <a href="ch7admin_vvr84_113910.html#114097">Synchronizing Volumes Using Difference-Based Synchronization</a>.</font>
</p>

</ol>
<p><img src="images/stepintro.gif" height="16" width="16">
<font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="114340"></a>&nbsp;&nbsp;<b>To fail back to the original Primary seattle</b></font>
</p>
<ol>
<li value="1">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114341"></a>Make the original Primary RVG <font face="Courier New, Courier, sansserif, sans serif" size="2">hr_rvg</font> on <font face="Courier New, Courier, sansserif, sans serif" size="2">seattle</font> the Secondary RVG of the new Primary <font face="Courier New, Courier, sansserif, sans serif" size="2">london</font> by typing the following command on the original Primary <font face="Courier New, Courier, sansserif, sans serif" size="2">seattle</font>:
</font>
<br>
<font face="Courier New, Courier, sansserif, sans serif" size="2"><a name="147271"></a>&nbsp;&nbsp;#&nbsp;<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>vradmin&nbsp;-g&nbsp;hrdg&nbsp;makesec&nbsp;hr_rvg&nbsp;london</b></font>
</font>
<li value="2">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="147272"></a>Synchronize the data volumes in the original Primary RVG <font face="Courier New, Courier, sansserif, sans serif" size="2">hr_rvg</font> with the data volumes in the new Primary RVG <font face="Courier New, Courier, sansserif, sans serif" size="2">hr_rvg</font> on <font face="Courier New, Courier, sansserif, sans serif" size="2">london</font> using the difference-based synchronization and checkpoint. To synchronize the Secondary based on differences using a checkpoint, type the following command on any host in the RDS:
</font>
<br>
<font face="Courier New, Courier, sansserif, sans serif" size="2"><a name="147276"></a>&nbsp;&nbsp;#&nbsp;<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>vradmin</b></font>&nbsp;<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>-g&nbsp;hrdg&nbsp;-c&nbsp;checkpt_presync&nbsp;syncrvg&nbsp;hr_rvg&nbsp;seattle</b></font>
</font>
<li value="3">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114351"></a>Stop the application on the new Primary <font face="Courier New, Courier, sansserif, sans serif" size="2">london</font>.
</font>
<li value="4">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114352"></a>Start replication to the Secondary RVG (original Primary) <font face="Courier New, Courier, sansserif, sans serif" size="2">hr_rvg</font> on <font face="Courier New, Courier, sansserif, sans serif" size="2">seattle</font> from the new Primary RVG <font face="Courier New, Courier, sansserif, sans serif" size="2">hr_rvg</font> on <font face="Courier New, Courier, sansserif, sans serif" size="2">london</font> using the checkpoint by typing the following command on any host in the RDS:
</font>
<br>
<font face="Courier New, Courier, sansserif, sans serif" size="2"><a name="114356"></a>&nbsp;&nbsp;#&nbsp;<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>vradmin</b></font>&nbsp;<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>-g&nbsp;hrdg&nbsp;-c&nbsp;checkpt_presync&nbsp;startrep&nbsp;hr_rvg&nbsp;seattle</b></font>
</font>
<li value="5">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114357"></a>Migrate the Primary role from the new Primary host <font face="Courier New, Courier, sansserif, sans serif" size="2">london</font> to the original Primary host <font face="Courier New, Courier, sansserif, sans serif" size="2">seattle</font> by typing the following command on any host in the RDS:
</font>
<br>
<font face="Courier New, Courier, sansserif, sans serif" size="2"><a name="114361"></a>&nbsp;&nbsp;#&nbsp;<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>vradmin</b></font>&nbsp;<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>-g&nbsp;hrdg&nbsp;migrate&nbsp;hr_rvg&nbsp;seattle</b></font>
</font>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="114362"></a>Replication from the original Primary <font face="Courier New, Courier, sansserif, sans serif" size="2">seattle</font> to the original Secondary <font face="Courier New, Courier, sansserif, sans serif" size="2">london</font> is started by default. </font>
</p>
<li value="6">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="147809"></a>Restart the application on the original Primary <font face="Courier New, Courier, sansserif, sans serif" size="2">seattle</font>. Because the application was stopped properly before the migration, an application recovery is not required.
</font>
</ol>



<h3><font face="Arial, Helvetica, Geneva, sansserif, sans serif, Verdana" size="2" color="#000000"><a name="146938"></a>Example 4---Failing Back to the Original Primary Using Difference-Based Synchronization in a Multiple Secondaries Setup</font>
</h3>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="146940"></a>This example shows how to fail back to the original Primary <font face="Courier New, Courier, sansserif, sans serif" size="2">seattle</font> using the difference-based synchronization feature.</font>
</p>

<ol>
<li value="1">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="146949"></a>Perform <a href="ch9tranprirole_vvr102_114209.html#114341">step  1</a> to <a href="ch9tranprirole_vvr102_114209.html#114357">step  5</a> described in the example <a href="ch9tranprirole_vvr102_114209.html#114335">Example 3---Failing Back to the Original Primary Using Difference-Based Synchronization</a>.
</font>
<li value="2">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="146951"></a>On the original Primary <font face="Courier New, Courier, sansserif, sans serif" size="2">seattle</font>:
</font>
<p>
<ul type="disc"><li><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="146952"></a>Synchronize the data volumes in the Secondary RVG <font face="Courier New, Courier, sansserif, sans serif" size="2">hr_rvg</font> on <font face="Courier New, Courier, sansserif, sans serif" size="2">tokyo</font> with the data volumes in the original Primary RVG <font face="Courier New, Courier, sansserif, sans serif" size="2">hr_rvg</font> using the difference-based synchronization and checkpoint. To do this, use the following command on any host in the RDS:</font>
</li>
<br>
<font face="Courier New, Courier, sansserif, sans serif" size="2"><a name="146953"></a>&nbsp;&nbsp;&nbsp;&nbsp;<font face="Courier New, Courier, sansserif, sans serif" size="2"><b>#&nbsp;vradmin&nbsp;-g&nbsp;hrdg&nbsp;-c&nbsp;checkpt&nbsp;syncrvg&nbsp;hr_rvg&nbsp;tokyo</b></font>
</font>
<ul><p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="147285"></a>The <font face="Courier New, Courier, sansserif, sans serif" size="2">-c</font> option when used with the vradmin syncrvg command automatically starts a checkpoint with the specified name, <font face="Courier New, Courier, sansserif, sans serif" size="2">checkpt</font>, in this example. After the data volumes are synchronized the checkpoint is ended. </font>
</p>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="146955"></a>After the data volumes are synchronized, the checkpoint is ended.</font>
</p>
</ul><li><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="146956"></a>Start replication from <font face="Courier New, Courier, sansserif, sans serif" size="2">seattle</font> to <font face="Courier New, Courier, sansserif, sans serif" size="2">tokyo</font> using the command:</font>
</li>
<br>
<font face="Courier New, Courier, sansserif, sans serif" size="2"><a name="146957"></a><font face="Courier New, Courier, sansserif, sans serif" size="2"><b>&nbsp;&nbsp;&nbsp;&nbsp;#&nbsp;vradmin&nbsp;-g&nbsp;hrdg&nbsp;-c&nbsp;checkpt&nbsp;startrep&nbsp;hr_rvg&nbsp;tokyo</b></font>
</font>
</ul>
</p>
<li value="3">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="146958"></a>Restart the application on the original Primary <font face="Courier New, Courier, sansserif, sans serif" size="2">seattle</font>. Because the application was stopped properly before the migration, an application recovery is not required.
</font>
</ol>
<p>
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="2"><a name="113811"></a></font>
</p>


<!-- End Main Topic Content -->

   </td>
  </tr>
 </table>
</div>

<div>
<table border="0" cellspacing="0" cellpadding="0" width="100%">
 <tr>
  <td height="18" border="0" cellspacing="0" cellpadding="0" colspan="2" bgcolor="#FFFFFF">
  </td>
 </tr>
  <td align="left"><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="-2">&nbsp;&#94;&nbsp;<a href="ch9tranprirole_vvr102_114209.html" title="Failing Back to the Original Primary">Return to Top</a></font>

  </td>
  <td align="right"><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="-2">&lt;&nbsp;<a href="ch9tranprirole_vvr101_114096.html" title="Previous - Taking Over from an Original Primary">Previous</a>&nbsp;&nbsp;|&nbsp;&nbsp;<a href="vea_vvr103_113895.html" title="Next - Administering VVR Using VVR VEA">Next</a>
&nbsp;&gt;&nbsp;&nbsp;</font>
  </td>
 <tr>
   <td height="9" border="0" cellspacing="0" cellpadding="0" colspan="2" bgcolor="#FFFFFF">
   </td>
 </tr>

<!-- Footer Breadcrumbs -->
<tr>
<td bgcolor="#FFFFFF" colspan="2" height="15" align="right">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="1">Product:  
<a href="vvr_splashpage_docCD_vvr1_103036.vxhd" title="Volume Replicator Guides title page ">Volume Replicator Guides</a>&nbsp;&nbsp;</font></td>
</tr>

<tr>
<td bgcolor="#FFFFFF" colspan="2" height="15" align="right">
<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="1">Manual:  
<a href="vvr_ag_hpux_titlepage_docCD_vvr41_73700.vxhd" title="Volume Replicator 4.1 Administrator's Guide title page ">Volume Replicator 4.1 Administrator's Guide</a>&nbsp;&nbsp;</font></td>
</tr>


 <tr>
  <td colspan="2" align="left"><font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" color="#000000" align="right" size="-2">
<em>VERITAS Software Corporation
</em></font><br>

<font face="Verdana, Arial, Helvetica, Geneva, sansserif, sans serif" size="-2">www.veritas.com</font><br>
  </td>
 </tr>
</table>
</div>

</BODY>
  <!--
    *************************************************************************************
    * Copyright (c) 2005 VERITAS Software Corporation. All rights reserved. *

    VERITAS, VERITAS SOFTWARE, the VERITAS Logo, and VERITAS Software Documentation 
    are trademarks or registered trademarks of VERITAS Software Corporation 
    or its affiliates in the U.S. and other countries. Other names may be 
    trademarks of their respective owners. 

    Apache Jakarta Lucene:
    Apache Software License
    Version 1.1

    Copyright (c) 2000 The Apache Software Foundation. All rights reserved.

    Redistribution and use in source and binary forms, with or without modification, 
    are permitted provided that the following conditions are met:

    1. Redistributions of source code must retain the above copyright notice, this 
    list of conditions and the following disclaimer.

    2. Redistributions in binary form must reproduce the above copyright notice, this 
    list of conditions and the following disclaimer in the documentation and/or other 
    materials provided with the distribution.

    3. The end-user documentation included with the redistribution, if any, must include 
    the following acknowledgment: "This product includes software developed by the Apache 
    Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may 
    appear in the software itself, if and wherever such third-party acknowledgments 
    normally appear.

    4. The names "Apache" and "Apache Software Foundation" must not be used to endorse or 
    promote products derived from this software without prior written permission. For 
    written permission, please contact apache@apache.org.

    5. Products derived from this software may not be called "Apache", nor may "Apache" 
    appear in their name, without prior written permission of the Apache Software Foundation.

    THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, 
    BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A 
    PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION 
    OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, 
    OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 
    OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND 
    ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING 
    NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF 
    ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

    This software consists of voluntary contributions made by many individuals on behalf 
    of the Apache Software Foundation. For more information on the Apache Software Foundation, 
    please see <http://www.apache.org/>. Portions of this software are based upon public domain 
    software originally written at the National Center for Supercomputing Applications, University 
    of Illinois, Urbana-Champaign.
    
    This product includes WebWindow Software developed by Horst Heistermann.
    *************************************************************************************
  -->
</HTML>
