Replication Server Demonstration

The procedure below illustrates the steps required to configure and intialize a replication network for demonstration purposes. Be advised that in demonstration mode certain restrictions apply to both functionality and client access as outlined below:

1. The SUNDM replication network can only have a primary and one secondary replication server.

2. A single managed replication directory specified by the MANAGED_DIR01 is allowed.

3. A single unmanaged replication directory specified by the UNMANAGED_DIR01 is allowed.

4. All other replication directory keywords are ignored.

5. Any SUNDM data manager with the Dnnnnnn serial number has an expiration date beyond which the software will not execute. The 'sundm -e' command will display the expiration date. Also, these data managers are limited to two managed file logons at any given time

 

1. Install a data manager using the Sunbelt installation software with the serial number specified as "DEMO". You can either install the primary and secondary as DEMO or just the secondary and use your current 9.1 SUNDM as the primary for testing.

2. Define the primary and secondary IP and port numbers.

3. Define the primary and secondary directories. Only the MANAGED_DIR01 and UNMANAGED_DIR01 keywords may specified in the primary server's configuration file.

4. Add a [replication] section to the primary server's configuration file that defines keywords as follows:

 

[replication]

#

# Define the replication type

#

TYPE=Primary

#

# Define the Sunbelt serial number, TCP/IP, and Port

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

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

# primary SUNDM and one secondary SUNDM replication

# server. The Port Number is specified.

# The N123456 in this example is your

# current SUNDM license number. If both the primary

# and secondary data managers are DEMO, you

# would use D999999 for both numbers.

#

HOST00=N123456:192.168.0.3

HOST01=D999999:192.168.0.100

#

# For the demo version, only one managed and one

# unmanaged directory is allowed. These keywords must

# be changed to reflect the two directories you want to

# test.

#

MANAGED_DIR01=c:\reptest

UNMANAGED_DIR01=c:\reptest1

 

5. Add a [replication] section to the configuration file for the secondary server that defines keywords as follows:

 

[replication]

#

# Define the replication type

# Backup may be also be specified.

#

TYPE=Secondary

#

# Define the Sunbelt serial number, TCP/IP, and Port

# Number (optional) for the primary server.

# The secondary serversettings come from the control data

# received from the primary server.

#

HOST00=N123456:192.168.0.3

#

 

6. The server is running Linux, the [replication] section in the configuration file must include the LOGON_HOST keyword.

7. Start the primary data manager with the '-s' option. This creates the master replication file named 'sundmrep.DM' in the directory where sundm.exe resides. The replication control file is created using the settings in the configuration file. The log file identifies that the replication is processing in a 'demo' mode. Note that changes to the confniguration file appear in the replication control file only after a '-s' or a '-u' SUNDM command is executed.

8. Start the secondary data managers with the '-s' option. The replication master file data is transferred to secondary servers as they log on. The log file identifies that the replication is processing in a demo mode.

See Also: Introduction,