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
- Backing up data to Data Domain storage
- 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 the Fibre Channel ports
- Requirements
- Enabling BOM (Bill of Materials) configuration for Fibre Channel
- Assigning Fibre Channel ports
- Discovering attached devices
- Rescanning Fibre Channel cards
- Cleaning Fibre Channel ports
- Unassigning Fibre Channel ports
- Viewing details about the Fibre Channel ports
- Disabling BOM (Bill of Materials) configuration for Fibre Channel
- Managing hardware vendor packages
- Updating credentials for HPE iLO administrator users
- User management
- NetBackup Flex Scale network management
- About network management
- Modifying DNS settings
- Configuring MTU on public interfaces
- Configuring the console FQDN
- 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
- About the security meter
- 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
- Configuring isolated recovery environment (IRE)
- Configuring multifactor authentication
- About multifactor authentication
- Considerations before configuring multifactor authentication
- Configuring multifactor authentication for your user account
- Disabling multifactor authentication for your user account
- Enforcing multifactor authentication for all users
- Configuring multifactor authentication for your user account when it is enforced in the cluster
- Resetting multifactor authentication for a user
- Single Sign-On (SSO)
- 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 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
- Replacement procedure for SFP port
- Replacement procedure for chassis
- Replacement procedure for a hard disk drive
- Replacement procedure for a Fibre Channel card for a cluster node
- Replacement procedure for a Fibre Channel card for a node that is not in a cluster
- Appendix B. Configuring NetBackup optimized duplication
- Appendix C. Disaster recovery terminologies
- Appendix D. Configuring Auto Image Replication
Replacement procedure for NVMe disks (SSDs)
NVMes are solid state drives (SSDs). The 7.68 TB NVMe RI drives are in slots 3 and 4 in the mid-bay.
To view the serial number of the NVMe disks, log in to the iLO remote console and click .
The following figures show the serial number for the two NVMe disks. Note the serial number of the NVMe disks. The serial number changes after the faulted disk is replaced.
In the NetBackup Flex Scale infrastructure management UI, navigate to . The disk status is shown faulted.
SSH to the the eth1 (management) IP address of the node and in the node-level CLI, run the following command to check the status of the NVMe disks:
show hardware-health node component=SSD
If there is some problem with the NVMes disks (7.68 TB capacity), in the Status column the disk status is shown NOT-OK.
Before an HPE representative can replace the NVMe disks, you must shut down the node.
To shut down the node:
- Sign in to the NetBackup Flex Scale infrastructure management UI and navigate to Monitor > Infrastructure > Nodes.
- On the node where the failure occurred, click the Actions menu (vertical ellipsis) from the right side of the row in the UI and click Shutdown node.
- Confirm that the node is shut down successfully. In the UI, you can view the notification at the top of the page. In the iLO remote console, wait until the system shows the System halted message.
- Shut down the node. Press the Power button on the front panel of the server or from the iLO remote console use the Server Power > Press and Hold option.
The HPE representative replaces the faulted NVMe disk with another NVMe disk.
After the hardware vendor notifies you that the hardware component is replaced, verify that the issue is resolved.
To verify that the issue is resolved, complete the following steps:
- Restart the node from the iLO remote console using the Power > Momentary Press option.
- Confirm that the serial number of the NVMe disk is updated. After an NVMe disk is replaced, the serial number is different from the one that you noted earlier.
- SSH to the eth1 (management) IP address of the node and run the show hardware-health node component=SSD command in the node-level CLI. In the Status column, the NVMe disk status is shown OK.
- In the NetBackup Flex Scale infrastructure management UI, replace the faulty NVMe disk with a new NVMe disk. If both the NMVe disks are faulty, replace with new disks successively. Navigate to Monitor > Infrastructure > Disks. Click the faulty disk that you want to replace, and then click Actions menu (vertical ellipsis) from the right side of the row in the UI and click Replace disk. The replacement disk is detected and added to the node.
After the disk is replaced, data rebuild process begins and you can monitor the progress at the bottom of the screen when you click Infrastructure > Monitor > Disks. Time taken to rebuild the data depends on the amount of data.