Home | Previous Page | Next Page   Fault Tolerance > Using High-Availability Data Replication (Enterprise/Workgroup Editions) > Configuring a System for HDR >

Meeting Database Server Configuration Requirements

For an HDR database server pair to function, you must fully configure each of the database servers. For information on configuring a database server, refer to Installing and Configuring the Database Server. You can then use the relevant aspects of that configuration to configure the other database server in the pair. For more information on the configuration parameters, see the IBM Informix Administrator's Reference.

This section describes the following configuration considerations for HDR database server pairs:

Database Server Version

The versions of the database server on the primary and secondary database servers must be identical.

Storage Space and Chunk Configuration

The number of dbspaces, the number of chunks, their sizes, their pathnames, and their offsets must be identical on the primary and secondary database servers. In addition, the configuration contain at least one temporary dbspace. See Use of Temporary Dbspaces for Sorting and Temporary Tables.

UNIX Only

You should use symbolic links for the chunk pathnames, as explained in Allocating Raw Disk Space on UNIX.

Important:
If you do not use symbolic links for chunk pathnames, you cannot easily change the pathname of a chunk. For more information, see Renaming Chunks.
End of UNIX Only

The following ONCONFIG parameters must have the same value on each database server:

Using Non-default Page Sizes in an HDR Environment

The page size of a dbspace and the buffer pool specifications are automatically propagated from the primary to the secondary database server. While both the primary and the secondary database servers must have the same buffer pools, the number of buffers in the buffer pools do not need to match.

Mirroring

You do not have to set the MIRROR parameter to the same value on the two database servers; you can enable mirroring on one database server and disable mirroring on the other. However, if you specify a mirror chunk for the root chunk of the primary database server, you must also specify a mirror chunk for the root chunk on the secondary database server. Therefore, the following ONCONFIG parameters must be set to the same value on both database servers:

Physical-Log Configuration

The physical log should be identical on both database servers. The following ONCONFIG parameters must have the same value on each database server:

Dbspace and Logical-Log Tape Backup Devices

You can specify different tape devices for the primary and secondary database servers.

If you use ON–Bar, set the ON–Bar configuration parameters to the same value on both database servers. For information on the ON–Bar parameters, see the IBM Informix Backup and Restore Guide.

If you use ontape, the tape size and tape block size for the storage-space and logical-log backup devices should be identical. The following ONCONFIG parameters must have the same value on each database server:

To use a tape to its full physical capacity, set LTAPESIZE and TAPESIZE to 0.

Logical-Log Configuration

All log records are replicated to the secondary server. You must configure the same number of logical-log files and the same logical-log size for both database servers. The following ONCONFIG parameters must have the same value on each database server:

The database server logs the addition of logical-log files. Logical-log files added dynamically on the primary server are automatically replicated on the secondary server. Although the DYNAMIC_LOGS value on the secondary server has no effect, keep DYNAMIC_LOGS in sync with the value on the primary server, in case their roles switch.

HDR Configuration Parameters

The following HDR configuration parameters must be set to the same value on both database servers in the replication pair:

Home | [ Top of Page | Previous Page | Next Page | Contents | Index ]