15
Managing Replication

Replication involves periodically copying domain information from an SCN or DCN to other nodes in the system or domain so that the nodes have access to the same information. Configuration information, such as routing information, is replicated from the SCN to all other nodes in the system. Directory information is replicated from a DCN to member nodes and the nodes subscribed to it.

Replication occurs automatically. You can use the following tasks described in this chapter to monitor and manage replication:

• Checking Replicator Status

• Manually Replicating Directory Data

• Resetting Replicator Package Numbering

Checking Replicator Status

Check the status of the replicator process to monitor the transfer of directory and node information from the DCN to the nodes subscribed to it.

Steps for Checking Replicator Status

This task can be performed through either the Administration Tool GUI, or the OOMGR command-line interface.

See Also: "Troubleshooting for Checking Replicator Status" for more information about troubleshooting the performance of this task "Understanding the Replicator Process Status" for more information about how to interpret the results of the replicator process status

In the Administration Tool GUI

1. Start the Administration Tool GUI.

2. In the navigation tree, select Messaging System > Nodes > node_name > Processes.

3. In the right pane, select one of the following tabs:

   Replicator Queue	To display the number of inbound and outbound packages in the replicator queue
   Replicator Activities	To display the state of the processes involved in the replication
   Replicator Folders	To display the contents of the replication folders such as the corrupted folder.

In OOMGR

1. Start OOMGR on the DCN.

2. Enter one of the following commands at the OOMGR prompt:

   To perform this task:	Use this command:
   Check replicator state	IOFCMGR>display replicator activity;
   Check replicator folders	IOFCMGR>display replicator folders;
   Check replicator package status	IOFCMGR>display replicator;

Troubleshooting for Checking Replicator Status

• If the monitor tests show that the replicator process log table is too big, then check to see if the local replicator process is running. To check the size of the replicator process log table, check the results of the REPLOG_TOO_BIG test.

• If packages remain unacknowledged for a long time, then make sure that the replicator and postman processes on the receiving node are running. To check the number of unacknowledged packages, check the results of the REPL_UNACKED test. Also, check to make sure there are no problems with the network or the computers.

• Examine the replicator process log file for additional information about any problems that may have occurred.

  See Also: "Running the Monitor Tests and Statistics Tasks" for instructions on how to run the REPLOG_TOO_BIG and the REPL_UNACKED monitor tests Chapter 17, "Monitoring and Troubleshooting", for more information about the monitor tests "Using Server Process Logs" for more information about the log file

Understanding the Replicator Process Status

The following sections are displayed when you check the replicator process status:

• Outbound Packages

  All domains listed in the Outbound Packages status section are domains for which this eMail Server node is the DCN.

  Outbound package status can be either sent or ack(nowledged). Sent indicates that the package was sent. Ack indicates that the destination node has acknowledged receiving the package.

  The Outbound Packages status section displays:

  • Recently acknowledged packages.

  • Packages that have been sent but not yet acknowledged.

• Inbound Packages

  Domains listed in the Inbound Packages status section are domains to which the node subscribes.

  Inbound package status can be either received or executed. Received indicates this node has received the package. Executed indicates that the changes contained in the package have been implemented.

  The Inbound Packages status section displays:

  • Recently executed packages.

  • Packages received but not yet executed.

Manually Replicating Directory Data

You can manually replicate information to a node if the replicator process is not running or not accessible. For example, the network connection to a particular node could be down.

You have two choices for manual replication. You can:

• Send eMail Server information to a node in the form of a replicator package.

• Copy (replicate) eMail Server information to a file, transfer the file to the node that needs the information, then replicate the information from the file to the node's database.

Replicating by Manually Sending a Replicator Package to a Node

You can replicate information to a single node if you only want the information to go to one node.

Steps for Replicating by Manually Sending a Replicator Package to a Node

This task can only be performed through the OOMGR command-line interface.

In OOMGR

1. Start OOMGR on the DCN.

2. Enter the following command at the OOMGR prompt:

   IOFCMGR>replicate to node=<node_name> class={<class_name> | all};
   

   See Also: "Parameters for Replicating by Manually Sending a Replicator Package to a Node" for more information about the parameters available with this command

Example:

To replicate the person class to the intmsg2 node, enter the following command:

IOFCMGR>replicate to node=intmsg2 class=person;

Parameters for Replicating by Manually Sending a Replicator Package to a Node

Parameters	Description
class	Name of the specific class you want to manually replicate. For example, you could replicate the person class to copy user name information to a node.
node	Name of the node to which you want to replicate information.

Replicating by Manually Transferring a File

You can replicate node information with a file by replicating the information to a file, transferring the file to another node, and then replicating from the file you just transferred.

Steps for Replicating by Manually Transferring a File

This task can only be performed through the OOMGR command-line interface.

In OOMGR

1. Start OOMGR on the DCN.

2. Create a replication file. Enter the following command at the OOMGR prompt:

   IOFCMGR>replicate to file=<file_name> class={<class_name> | all};
   
   

3. Transfer the file to the node on which replication will occur.

4. Replicate the information from the file you transferred to the node. Enter the following command at the OOMGR prompt:

   IOFCMGR>replicate from file=<file_name>;
   

   See Also: "Parameters for Replicating by Manually Transferring a File" for more information about the parameters available with this command

Parameters for Replicating by Manually Transferring a File

Parameter	Description
class	Name of the specific class you want to manually replicate. For example, you could replicate the person class to copy user name information to a node.
file	Name of the file to which you want to replicate information. You can enter any filename.

Resetting Replicator Package Numbering

You can reset the replicator package numbering to force the replicator process to accept a package that has a number that does not match the next expected package. For example, if a package was not delivered due to network problems, you might need to reset the package numbering to skip the package that cannot be delivered.

Steps for Resetting Replicator Package Numbering

This task can only be performed through the OOMGR command-line interface.

In OOMGR

1. Start OOMGR on the DCN.

2. Enter the following command at the OOMGR prompt:

   IOFCMGR>reset replicator;
   
   

   This command causes the replicator process to accept the next package sent, regardless of number. The replicator process resets its sequencing starting with the number of the first package it receives.