Adding a node to the cluster using the GUI
You can add a new node to the cluster to increase its compute resources. When the add node operation is in progress, the backup and restore jobs continue to run on the cluster nodes. The new node must have the same hardware configuration as the existing cluster node.
Considerations before adding a new node to a cluster
Verify that all the existing nodes in the cluster are in a healthy state. You cannot add a node if a cluster node is not healthy.
Private links should be modified such that private NIC (eth2) of cluster node is connected to private NIC (eth2) of new node and private NIC (eth3) of cluster node should be connected to private NIC (eth3) of the new node.
The node that you want to add must be connected to the same private and public network as that of the existing cluster. For details about the cabling information, see the Hardware installation procedures in the Veritas Access 3360 Appliance Hardware Installation Guide.
Management interface IP (eth1) should be assigned using the node-level CLI command.
If add node operation is in progress, you cannot perform any other cluster operation until the existing operation is completed.
If DNS is configured on the cluster node, IP and FQDN mapping should be done correctly.
If you have replaced a disk on an existing cluster node, check the status of the show hardware health command and wait until the replaced disk status is OK. Once the disk state is in OK state and it is associated with a volume group, you can trigger the add node operation.
The network of the new node's management interface IP should be the same as the network of the cluster node's management interface.
If you have upgraded from Access Appliance version 8.3 to 8.6 using the GUI, and if any patch, EEBs or add-ons are already installed on the cluster node, then the same patch, EEBs or add-ons are installed on the new node before adding it to the cluster. If you have upgraded from an earlier version of Access Appliance, you have to manually upgrade the new node before adding it to the cluster.
In a single-node cluster, both adding a node and upgrading the cluster must be performed through the GUI.
Add node operation upgrades the node only if the upgrade path is supported.
The upgrade path between the software version of the node being added and the version running on the existing cluster node must be supported.
The required patch must already be present on the node being added.
Once the add node operation is complete, all the configurations are copied to the new node.
Do not trigger the add node operation from both the GUI and CLISH simultaneously.
To add a new node the cluster
- Using an user account with an Appliance Administrator role, log in to the Access Appliance GUI.
- Navigate to the Infrastructure section. Under the Nodes tab, select the nodes that you want to add and click + Add.
- In the Add node window, select Continue.
- Enter the following information for the selected nodes:
Host name: Enter the host name assignments for each node to be added to the cluster. The node name should have at least 3 characters and can contain a maximum of 63 characters, excluding the domain name. It should start with a lower case character. It cannot start with a number or a special character.
Management Network: Enter the management interface assignments for each node to be added to the cluster. FQDN is an optional parameter.
Click Add.
The progress of the add node operation is displayed on the Infrastructure page.
- To monitor the status of each of the tasks, click View details on the Infrastructure page. The ongoing and completed tasks for the add node operation are also displayed in Recent activity. After the node is added, you can view the new node and its details on the Nodes tab.
Note:
If two instances of Veritas Data Deduplication are running on one node when add node operation is performed, then after the add node operation is complete, you should explicitly change the affinity of any one of the instances to the newly added node. Else, you may experience a higher utilization of CPU, and RAM. The affinity can be changed using the dedupe affinity set <node_name> <config_name> command.