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
- Considerations for managing NetBackup Flex Scale users
- Adding users
- Changing user password
- Removing users
- Modifying user roles
- Considerations for configuring AD/LDAP
- Configuring AD server for Universal shares and Instant Access
- Configuring AD/LDAP servers for NetBackup services
- Configuring additional AD/LDAP servers for managing NetBackup services/Universal Shares/Instant Access
- Configuring AD/LDAP servers on clusters deployed with only media servers
- Directory services and certificate management
- Region settings management
- About NetBackup Flex Scale storage
- About Universal Shares
- Cloud bucket support for NetBackup Flex Scale
- Node and disk management
- NetBackup Flex Scale network cabling
- Adding a node to the cluster using the NetBackup Flex Scale web interface
- Adding a node using the REST APIs
- Replacing a node in a cluster
- Starting and stopping nodes
- Rebooting a node
- Adding an excluded node to the cluster
- Replacing a disk
- Adding an excluded disk to the cluster
- Viewing the disk sync status
- Viewing disk details
- Viewing node details
- Switching management console to another cluster node
- License management
- Stopping NetBackup service containers
- Starting NetBackup service containers
- Managing hardware vendor packages
- User management
- NetBackup Flex Scale network management
- About network management
- Modifying DNS settings
- About bonding Ethernet interfaces
- Bonding operations
- Configuring NetBackup Flex Scale in a non-DNS environment
- Data network configurations
- Choosing the correct input method for data network configuration
- Network configuration on plain device (eth5)
- Network configuration on VLAN (eth5)
- Network configuration on bonded interfaces (bond0 on eth5 and eth7)
- VLAN on bond of eth5 and eth7 (bond0)
- Network configuration on management interface (eth1)
- Network configurations for adding a partial data network
- Support for multiple VLAN when disaster recovery is configured
- Configuring static routes on a NetBackup Flex Scale cluster
- 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
- Automated NetBackup SLP management
- DNS key management
- 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
- STIG overview for NetBackup Flex Scale
- FIPS overview for NetBackup Flex Scale
- Managing the login banner
- Changing the password policy
- Support for immutability in NetBackup Flex Scale
- Authenticating users using digital certificates or smart cards
- About system certificates on NetBackup Flex Scale
- Deploying external certificates on NetBackup Flex Scale
- Troubleshooting
- Services management
- Audit logs
- Collecting logs for cluster nodes
- 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. Maintenance procedures for HPE servers
- Replacement procedure for a chassis fan
- Replacement procedure for power supply
- Replacement procedure for a single OS disk
- Replacement procedure for both OS disks on the management console node
- Replacement procedure for both OS disks on a non- management console node
- Replacement procedure for NVMe disks (SSDs)
- Replacement procedure for RAID controller
- Replacement procedure for an Integrated Lights-Out (iLO) port
- Replacement procedure for quad-port NIC
- Procedure for memory expansion (DIMMs)
- Replacement procedure for memory (DIMMs)
- Replacement procedure for Mellanox port
- Appendix B. Configuring NetBackup optimized duplication
- Appendix C. Disaster recovery terminologies
- Appendix D. Configuring Auto Image Replication
Monitoring hardware components
After you configure the cluster, you can monitor the hardware components using the NetBackup Flex Scale UI or the Appliance Shell Menu. If a problem is detected, the following notification mechanisms can be used to view and report the issue:
View alerts on the Dashboard or the option of the web interface.
See About the NetBackup Flex Scale infrastructure management UI.
Send email alerts.
Send SNMP alerts.
Share hardware monitoring information for analysis and troubleshooting with Veritas Support using Call Home.
Locate disks.
See Locating the disks.
Monitor deviations.
See Monitoring deviations in firmware, driver, and utilities.
The Hardware tab on the page shows the status of the hardware components for each of the nodes. If a problem occurs and Call Home is enabled, the diagnostic data is automatically sent to Veritas Support and a support case is automatically created. This option helps to provide proactive service and leads to a faster resolution of any hardware issues.
You can monitor the following hardware components in the web interface:
CPU
Fan
Hard disk
Network card
PCI
Power supply
RAID
If a hardware component fails or reports an error, an alert icon is displayed next to the component and the node it belongs to.
You can also use the Veritas Appliance shell menu to check the health and status of the hardware components. After logging in to the shell menu, you can use the following commands to monitor the status:
Command | Description |
|---|---|
show hardware-errors | View hardware component faults and errors |
show hardware-health node [component=] | View the status of a specific hardware component. The Item parameter specifies the component for which the data is queried. The following options are available. The default option is All. Note: Some of the options might vary based on the hardware platform.
|