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
- Directory services and certificate management
- Region settings management
- About NetBackup Flex Scale storage
- About Universal Shares
- Creating a Protection Point for a Universal Share
- Node and disk management
- License management
- NetBackup Flex Scale network management
- About network management
- Modifying DNS settings
- About bonding Ethernet interfaces
- 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
- About site-based disaster recovery in NetBackup Flex Scale
- Configuring disaster recovery using GUI
- Clearing the host cache
- Managing disaster recovery using GUI
- Performing disaster recovery using RESTful APIs
- Active-Active disaster recovery configuration
- NetBackup optimized duplication using Storage Lifecycle Policies
- NetBackup Flex Scale security
- Troubleshooting
- Services management
- Collecting logs for cluster nodes
- Checking and repairing storage
- Troubleshooting NetBackup Flex Scale issues
- If cluster configuration fails (for example because an IP address that was already in use is specified) and you try to reconfigure the cluster, the UI displays an error but the configuration process continues to run
- Validation error while adding VMware credentials to NetBackup
- NetBackup Web UI incorrectly displays some NetBackup Flex Scale processes as failed
- Unable to create BMR Shared Resource Tree (SRT) on NetBackup Flex Scale Appliance
- NetBackup configuration files are not persistent across operations that require restarting the system
- 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:
Using an user account with an Appliance Administrator and NetBackup Administrator role, log in to the NetBackup web interface
https://ManagementServerIPorFQDNwhere ManagementServerIPorFQDN is the public IP address that you specified for the NetBackup Flex Scale management server and API gateway during the cluster configuration, and then in the left pane click Appliance management.Using an user account with an Appliance Administrator role, log in to the NetBackup Flex Scale web interface
https://ManagementServerIPorFQDN:14161where ManagementServerIPorFQDN is the public IP address that you specified for the NetBackup Flex Scale management server and API gateway during the cluster configuration.
- In the left navigation bar, click Monitor and then click 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.
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.
The node status changes to healthy.