The procedure below illustrates the steps required to configure and intialize a replication network.

1. Define primary and secondary IP and Port number requirements.

2. Define the primary and secondary directories. The MANAGED_RECURS_DIRnn, UNMANAGED_RECURS_DIRnn, MANAGED_DIRnn, and UNMANAGED_DIRnn keywords must be specified in the primary configuration file.

3. Add a [replication] section to the server configuration file (sundm.cfg) for the primary server. Define the keywords as follows:

 

[replication]

#

# Define the SUNDM replication type

#

TYPE=Primary

#

# Define the Sunbelt Serial Number, TCP/IP, and Port

# Number (optional) for the data managers used in the

# SUNDM replication network. In this case, there is a

# primary data manager and one secondary replication

# server. The Port Number is not specified.

#

HOST00=N123456:192.168.0.3

HOST01=N987654:192.168.0.100

#

# Define all of the replication directories

#

MANAGED_RECURS_DIR01=c:\reptest

MANAGED_RECURS_DIR02=c:\reptest1|d:\mydir

 

4. Add a [replication] section to the configuration file for each secondary server as follows:

 

[replication]

#

# Define the SUNDM replication type.

# Backup can be also be specified.

#

TYPE=Secondary

#

# Define the Sunbelt Serial Number, TCP/IP, and Port

# Number (optional) for the data managers used in the

# SUNDM replication network. In this case, only the

# primary data settings is needed.

#

HOST00=N123456:192.168.0.3

#

 

5. If the server is running Linux, the [replication] section must include the LOGON_HOST keyword.

6. Start the primary data manager with the '-s' option. This creates the master replication file named 'sundmrep.DM' in the directory containing sundm.exe. The replication control file is created using the settings from the cofiguration file. Note that any changes to the configuration file appear in the replication control file only after a '-s' or a '-u' command is executed.

7. Start the secondary data managers with the '-s' option. The replication master file data is transferred to secondary replication data managers as they log on to the primary.

See Also: Introduction,