Veritas Access Appliance 8.4 Administrator's Guide
- Section I. Introducing Access Appliance
- Section II. Configuring Access Appliance
- Managing users
- Managing licenses
- Configuring the network
- Configuring authentication services
- Configuring user authentication using digital certificates or smart cards
- Section III. Managing Access Appliance storage
- Configuring storage
- Managing disks
- Access Appliance as an iSCSI target
- Configuring storage
- Section IV. Managing Access Appliance file access services
- Configuring the NFS server
- Setting up Kerberos authentication for NFS clients
- Using Access Appliance as a CIFS server
- About configuring CIFS for Active Directory (AD) domain mode
- About setting trusted domains
- About managing home directories
- About CIFS clustering modes
- About migrating CIFS shares and home directories
- Using Access Appliance as an Object Store server
- Configuring the S3 server using GUI
- Configuring the NFS server
- Section V. Managing Access Appliance security
- Managing security
- Setting up FIPS mode
- Configuring STIG
- Setting the banner
- Setting the password policy
- Immutability in Access Appliance
- Deploying certificates on Access Appliance
- Single Sign-On (SSO)
- Configuring multifactor authentication
- Section VI. Monitoring and troubleshooting
- Monitoring the appliance
- Configuring event notifications and audit logs
- About alert management
- Appliance log files
- Section VII. Provisioning and managing Access Appliance file systems
- Creating and maintaining file systems
- Considerations for creating a file system
- About managing application I/O workloads using maximum IOPS settings
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VIII. Provisioning and managing Access Appliance shares
- Creating shares for applications
- Creating and maintaining NFS shares
- About the NFS shares
- Creating and maintaining CIFS shares
- About the CIFS shares
- About managing CIFS shares for Enterprise Vault
- Integrating Access Appliance with Data Insight
- Section IX. Managing Access Appliance storage services
- Configuring continuous replication
- How Access Appliance continuous replication works
- Configuring a continuous replication job using the GUI
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Configuring continuous replication
- Section X. Reference
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.
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.4 using the GUI,if any patch, EEBs or add-ons are already installed on the cluster node, 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.
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.
Note:
If you want to perform an add node operation for a single node Access Appliance cluster using GUI, install the VRTSaccess-app-EEB-ET4196372-8.4.0.0-1.x86_64.rpm package both on the existing node within the cluster and the node that you want to add to the cluster before you trigger the add node operation..
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.