Endpoint Configuration Parameters | Teradata Business Continuity Manager - ENDPOINT Configuration Parameters - Teradata Business Continuity Manager

List of IP addresses and optional ports on which the Endpoint process listens for client requests. Use commas to separate multiple IP addresses.

any[:port] | <ip>[:<port>][,<ip>
[:<port>], ...]

The keyword any indicates that the Endpoint listens on all defined IP addresses on the Teradata system. The EndpointDefaultPort parameter specifies the port value.

If the keyword any is not used, you can provide specific IP address values. The <port> value is optional. Any IP addresses given without a port value default to the value defined in the EndpointDefaultPort parameter.

Port number for an IP address that is not defined as a port in EndpointAddresses. Client applications and users connect to this port.

List of Standby IP (SIP) addresses that the Endpoint process enables if Endpoints in other Regions are not available. Use commas to separate multiple SIP addresses. The SIP address values cannot be the same as the IP address values defined in EndpointAddresses . If the EndpointAddresses value is set to any , the EndpointSIPAddresses are ignored.

<region> <ip>[:<port>][,<ip>
[:<port>], ...][;<region> <ip>[:<port>][,<ip>
[:<port>], ...]]

Because this parameter can support the failover of Endpoint processes from multiple Regions, the <region> value specifies the name of the Regions for which the following IP address is enabled if the Endpoints in that Region are not available. For example:

toronto 192.168.0.1, 192.168.0.2; sandiego
192.168.0.3, 192.168.0.4

This example shows that if all Endpoints in the Toronto Region are unavailable, then this Endpoint enables 192.168.0.1 and 192.168.0.2 for available connections from clients that were connecting to the Endpoints in Toronto. It also specifies that if all the Endpoints in San Diego Region are unavailable, then this Endpoint enables 192.168.0.3 and 192.168.0.4 for available connections from clients that were connecting to Endpoints in San Diego.

If the EndpointAddresses value is set to any, then values in the EndpointSIPAddresses are ignored.

• If a load client sends several checkpoint 0, Business Continuity Manager only counts it once.
• If the MLoad client sends several CHECKPOINT interval 0 (or several same checkpoint interval value on restart), each of them is counted as a checkpoint seen. (The checkpoint interval value of the MLoad client can be less than the Checkpoint seen.)

When the parameter is set to true, loads to managed multiple database systems are completely asynchronous. Load data are written to remote nodes asynchronously and, at a load checkpoint end or load end, when closing load data files, Business Continuity Manager does not wait for all the outstanding remote writes of load data to finish. With the True setting, if there is significant network delay or low network bandwidth between the two Business Continuity Manager regions, load clients complete the loads much faster, as loading to a single database system directly, right after completing the loads to the database system at the local region. Business Continuity Manager completes the loads to the database system at the remote region, in the background.