Skip to main content

Adding a node

Summary

To replace an application node that has failed, or add a net-new application node:

  1. Install the hardware (physical or virtual), operating system, and database software on the new node. Apply whatever patches are available from the OS and database vendors, as noted in Preparation for setting up replication environment.

    Note that everything must be the same on the replicated nodes, including: OS version and bitsize, application locations, database versions, instance name (spelled the same, case sensitive), software required to communicate with target systems, and other integration requirements.

  2. Verify that there is connectivity on the Bravura Security Fabric ports, bidirectionally, from all other node servers to the new server (usually, this involves opening firewall ports and/or setting up VPN connections between sites/data-centers to allow network routing between the servers on those ports).

  3. Install the Bravura Security Fabric software on the new application node, as described in Installing Bravura Security Fabric using idmsetup.inf

  4. On the application node that contains the most data (usually the primary node):

    1. Add the new node to the replication configuration .

    2. Propagate the replication configuration to cause the current instance to synchronize its database with the new instance. This is described in the steps below.

    3. Optional: Synchronize data (sending the relevant data from the database node where the operation is performed, to the database node being added). This is not required, for example, when adding a node in shared schema, or when the database is very large, and it is more efficient to migrate the database, sending the data.

More detail is provided below. You should also refer to native database administration tools and their related documentation for the process to generate and load snapshots.

After finishing any changes, remember to verify the replication configuration .