Veritas NetBackup™ Flex Scale Administrator's Guide
- Product overview
- Viewing information about the NetBackup Flex Scale cluster environment
- NetBackup Flex Scale infrastructure management
- User management
- About Universal Shares
- Node and disk management
- License management
- User management
- NetBackup Flex Scale network management
- Bonding operations
- Data network configurations
- NetBackup Flex Scale infrastructure monitoring
- Resiliency in NetBackup Flex Scale
- EMS server configuration
- Site-based disaster recovery in NetBackup Flex Scale
- Performing disaster recovery using RESTful APIs
- NetBackup Flex Scale security
- Troubleshooting
- Collecting logs for cluster nodes
- Troubleshooting NetBackup Flex Scale issues
- Appendix A. Configuring NetBackup optimized duplication
- Appendix B. Disaster recovery terminologies
- Appendix C. Configuring Auto Image Replication
Starting and stopping nodes
You might need to stop a cluster node for hardware maintenance such as replacing some of the hardware components. For a cluster with less than six nodes, only a single node can be down or you can stop only a single node at any given point in time. For a larger cluster of up to 16 nodes, a maximum of two nodes can be down or can be stopped at any given point in time. When you stop a node, the NetBackup jobs running on the node fail over to other nodes in the cluster and the cluster services running on the node are stopped. After the hardware maintenance is complete, you need to start the node. When you start a node, the cluster services are started on the node, the node joins the cluster and can start running backup jobs.
If you stop or shut down the node where the NetBackup Flex Scale infrastructure management console (UI) is running, the infrastructure management console fails over to another node. It can take a few minutes for the management console to be up on another node.
Note:
If the loss of nodes exceeds the supported fault tolerance, either due to node failures or nodes are stopped or shut down, the cluster goes in an inconsistent state.
To stop and start a node:
- Use any one of the following options to log in using the user account that you created when you configured the cluster:
Use a user account with both Appliance administrator and NetBackup administrator role, or a user account with only an Appliance administrator role to log in to the NetBackup Flex Scale web interface
https://ManagementServerIPorFQDN/webui
where ManagementServerIPorFQDN is the public IP address or the FQDN that you specified for the NetBackup Flex Scale management server and API gateway during the cluster configuration, and then in the left pane click Cluster Monitor > Infrastructure.Use a user account with an Appliance Administrator role to log in to the NetBackup Flex Scale infrastructure management console
https://ManagementServerIPorFQDN:14161
where ManagementServerIPorFQDN is the public IP address or the FQDN that you specified for the NetBackup Flex Scale management server and API gateway during the cluster configuration, and then in the left pane click Monitor > Infrastructure.
- Click the Nodes tab.
The list of cluster nodes is displayed.
- To stop the node, click the Actions menu (vertical ellipsis) from the right side of the row in the UI, and click Stop node.
If you are in the NetBackup Flex Scale UI, when prompted, click Open cluster console to open the NetBackup Flex Scale infrastructure management console in a new browser tab. In the NetBackup Flex Scale infrastructure management console, when prompted to confirm, click Stop node.
The node status changes to unhealthy.
- To start the node, click the Actions menu (vertical ellipsis) from the right side of the row in the UI, and click Start node.
If you are in the NetBackup Flex Scale UI, when prompted, click Open cluster console to open the NetBackup Flex Scale infrastructure management console in a new browser tab. In the NetBackup Flex Scale infrastructure management console, when prompted to confirm, click Start node.
The node status changes to healthy.