CentraSite 10.11 | CentraSite Administrator’s Guide | Configuring CentraSite | Maintaining the CentraSite Internal Database | Setting Up Replication Instances of Registry Repository
 
Setting Up Replication Instances of Registry Repository
To replicate instances of the CentraSite Registry Repository through the CentraSite Command Line Interface, you must have the CentraSite Administrator role.
Replication instances of the CentraSite Registry Repository (CRR) can be set up on the base of a backup from the original instance, also called master instance.
To manage the replication instance of Registry Repository, CentraSite provides a set of inoadmin command tools.
To be able to replicate instances of the CentraSite Registry Repository, note the following points:
*A replication instance must be configured on a different host than the master host.
*The master server must be reachable in the same domain as the replication host.
*The master server must have enough log space data available to supply the replication instances with replication data.
The latter is important in case of a larger replication delay due to a disconnected master server. The sets of log spaces are associated with backups.
To ensure that replication instances can be supplied with replication data, the server property number of backup generations must be at least 2 or even larger. Once a replication instance is configured, the replication instance is started in the same way as the master server. During startup, the replication server connects to the master server to request replication data. When the connection to the master server is interrupted, the replication server re-connects as soon as the master server is reachable. If the replication server must be shut down for any reason, the replication processing is suspended and replication processing resumes when the replication server is started again.
To prepare a server to be set up as replication server, you must create a copy of the CentraSite Registry Repository using the command tool MoveCentraSiteRR. For details about the usage of command tool, see Moving a Database to Another Location.
You must not start the server of the created instance before it is set as replication instance using the command tool setreplication.
Note:
You must specify the host name of the computer where the CentraSite Registry Repository component is running, without specifying the domain name.
* Enabling CRR Database for Replication: To register the host name of the replication instance, at the master host, run the command allowreplication.
The syntax is of the format: inoadmin allowreplication <server> <replication_hostname>
This is required for a replication server that connects to a master server to request replication data.
CentraSite does not allow a replication server to request replication data from the master server if the host name is not already registered for replication.
* Setting Up Replication Database: To set a copy of the CentraSite Registry Repository as replication instance of the master host, at the replication host, run the command setreplication.
The syntax is of the format: inoadmin setreplication <server> <master_hostname> <master_port>
A request for replication permission is sent to the master server on the specified host using the given port number. If the response to this request is returned successfully, the host name and port number for master server access is stored. For more information about the replication properties, see Database Configuration Parameters.
Note:
If a master server was not restarted after the first replication host name was added, a restart of the master sever may be required to change some initial set up for a running server.
* Re-setting Replication Database: To reset the replication instance to a normal server instance which can be used instead of the master instance in case of a failure, at the replication host, run the command resetreplication.
The syntax is of the format: inoadmin resetreplication <server>
Other replication instances cannot use such a reset server instance as the new master because of synchronization reasons. To use such an instance as a master server, a new backup should be created as a base for re-creating other replication server instances.
* Fetching Details of Replication Database: To check whether the server is a master server or a replication serve, master host or replication host, run the command replicationinfo.
The syntax is of the format: inoadmin replicationinfo <server>
*For a master server instance, the list of permitted replication host names is displayed as an additional information, if the master server is running.
*For a replication server instance, the master server host and the port used for the master server access are displayed as an additional information. The replication time stamp shows the time of the last replicated data.
* Disabling CRR Database for Replication: To unregister the host name of the replication instance to prevent further re-replication, at the master host, run the command allowreplication.
The syntax is of the format: inoadmin denyreplication <server> <replication_hostname>