Point a redundant interface to a secondary collective member

If you just upgraded from a single Data Archive server to a collective, restart PI ICU.

If you use PI Buffer Subsystem 4.3 or later, follow steps 1 through 4 below. If you use PI Buffer Subsystem versions 3.4.380 and earlier, follow all steps below.

1. In the PI ICU page tree, select General.

2. Under PI Host Information, set SDK Member to a secondary collective member.

   This property sets which Data Archive server in the collective sends the interface configuration information and output points. If you set each interface to a different collective member, you enable failover when the Data Archive server that sends output points becomes unavailable.

3. Set API Hostname to match.

   The interface uses this information to connect to the Data Archive server that provides configuration data.

   The drop-down list shows the host specified in various formats. You can specify the host as an IP address, a path, or a host name. However, when you configure the buffered server list, you must specify the buffered server names in the same format, otherwise buffering will not work.

4. Click Apply.

   Note: Follow the remaining steps only if you are using PI Buffer Subsystem 3.4.380 or earlier.

5. Select Tools > Buffering.

6. In the Buffering dialog box task list, select Buffered Servers.

7. Verify that the Replicate data to all collective member nodes check box is selected and that the server list contains the server and format specified in API Hostname.

8. If necessary, click the appropriate entry under Buffered Server Names to change the format.

9. Click Yes at the prompt to restart PI Buffer Subsystem and dependent interfaces.