Set the Save Interval for Routes

Execute the alter route command with the save_interval parameter at the source Replication Server to set the save interval for a route.

Save Interval Example

Figure 7-1 illustrates an example of save interval in a Replication System. In this example, there is a primary and a replicate data server, as well as, three Replication Servers in different locations. The Replication Server tokyo underscore R S maintains a direct route to manila underscore R S, and manila underscore R S maintains a direct route to sydney underscore R S. tokyo underscore R S retains messages for a period of time after manila underscore R S has received them. If manila underscore R S experiences a partition failure, it requires that tokyo underscore R S to resend the backlogged messages. manila underscore R S can also retain messages to allow sydney underscore R S to recover from failures.

For example, to set Replication Server TOKYO_RS to save for one hour any messages destined for MANILA_RS, enter:

alter route to MANILA_RS
    set save_interval to '60'

By default, save_interval is set to 0 (minutes). For systems with low volume, this may be an acceptable setting for recovery, since Replication Server does not delete messages immediately after receiving acknowledgment from destination servers. Rather, messages are deleted periodically in large chunks.

However, to accommodate the volume and activity of sites that receive distributions from the Replication Server and to increase the chance of full recovery from database or partition failures, you may want to change the save_interval setting.

In case of a partition failure on the stable queues, be sure your setting allows adequate time to restore your system. Consider also the size of the partitions that are allocated for backlogged messages. Partitions must be large enough to hold the extra messages.

Refer to the Replication Server Design Guide capacity planning guidelines for help in determining queue space requirements.