CentraSite Documentation : CentraSite Administrator’s Guide : Basic Operations : Maintaining the CentraSite Internal Database : Setting Up Replication Instances of the Registry Repository
Setting Up Replication Instances of the Registry Repository
Replication instances of the CentraSite Registry Repository can be set up on the base of a backup from the original instance, also called master instance.
To be able to replicate instances of the CentraSite Registry Repository, please 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 will be 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 inoadmin setreplication.
To configure such a copy of a CentraSite Registry Repository (CRR) as replication instance, CentraSite offers a set of inoadmin commands.
Note:  
You must specify the host name of the computer where the CentraSite registry/repository component is running, without specifying the domain name.
Enabling the CRR Database for Replication
At the master host, enter the following command on the command line:
inoadmin allowreplication CentraSite <replication_hostname>
Registers the host name of the replication instance. This is required for a replication server that connects to a master server to request replication data.
CentraSite will not allow a replication server to request replication data from the master server if the host name is not already registered for replication.
Disabling the CRR Database for Replication
At the master host, enter the following command on the command line:
inoadmin denyreplication CentraSite <replication_hostname>
Unregisters the host name of the replication instance to prevent further re-replication.
Setting Up the Replication Database
At the replication host, enter the following command on the command line:
inoadmin setreplication CentraSite <master_hostname> <master_port>
Sets a copy of the CentraSite Registry Repository as replication instance of the master on the given host. 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 the Replication Database
At the replication host, enter the following command on the command line:
inoadmin resetreplication CentraSite
Resets the replication instance to a normal server instance which can be used instead of the master instance which is lost for any reason. 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 the Replication Database
At the master host or replication host, enter the following command on the command line:
inoadmin replicationinfo CentraSite
Shows whether the server is a master server or a replication 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.
Copyright © 2005-2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback