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
Replacement procedure for a single OS disk
This topic describes the process of replacing a single OS disk that failed or is unreachable. Each node has two OS disks.
The following section describes how to identify a single OS disk failure from NetBackup Flex Scale:
An alert is generated for an OS disk failure or for an unreachable disk. To view the alert, do one of the following from the NetBackup Flex Scale infrastructure management UI:
Click in the left pane. In the Alerts area, click to see a complete list of alerts.
At the top of any screen, click the icon.
Click . On the Alerts management page, use the filters to locate specific types of alerts.
If SMTP is configured for AutoSupport, you receive email alerts. If Call Home is configured for your setup, diagnostic information is sent to the AutoSupport server.
Navigate to and select the node on which the OS disk went bad, and then click . The UI shows the failure for the corresponding OS disk:
The following section describes how to identify an OS disk failure from third-party tools:
The HPE Integrated Lights-Out (iLO) remote console shows a failure. The Health for the OS disk is shown as Critical and Warning for the Volume of the RAID 1 in iLO.
The health of the node is shown as unhealthy for that node in the NetBackup Flex Scale UI. Navigate to to view the node health.
An HPE representative identifies the faulty disk, its physical location in the appliance, and replaces the faulty OS disk. You can use the AHS logs to find the required details, and then replace the disk.
Note:
With NetBackup Flex Scaleversion 3.1, you can beacon the disk from the UI.
After you get the physical location of the disk on the appliance, replace the OS disk with a new OS disk. Note the model number of the new disk and ensure that it matches with the older one.
To replace the disk, the HPE representative completes the following steps:
- Check the disk model number from the iLO remote console.
- Identify the corresponding location of the OS disks in the appliance. In this example, Box6 - Bay 1 and Bay 2.
- Refer to the HPE procedure to replace the disk.
- In iLO, after the OS disk is replaced, Health for the OS disk is set to OK but the Health of the Volume of the RAID 1 is set to Warning till the rebuild completes.
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, Veritas TSE completes the following steps:
- Wait till the RAID controller rebuilds the new OS disk. This operation takes approximately two hours. To check the rebuild progress, run the following command after elevating to root access:
nbfs3.1> support elevate # ssacli ctrl all show config HPE Smart Array P816i-a SR Gen10 in Slot 0 (Embedded) (sn: PWXLA0BRHDW07G) Internal Drive Cage at Port 1I, Box 2, OK Internal Drive Cage at Port 2I, Box 3, OK Internal Drive Cage at Port 3I, Box 6, OK Internal Drive Cage at Port 4I, Box 7, OK Port Name: 1I (Mixed) Port Name: 2I (Mixed) Port Name: 3I (Mixed) Port Name: 4I (Mixed) Array A (Solid State SATA, Unused Space: 0 MB) logicaldrive 1 (1.75 TB, RAID 1, Recovering, 4.13% complete) physicaldrive 3I:6:1 (port 3I:box 6:bay 1, SATA SSD, 1.9 TB, Rebuilding) physicaldrive 3I:6:2 (port 3I:box 6:bay 2, SATA SSD, 1.9 TB, OK) - After the rebuild completes successfully, verify that all the AutoSupport alerts are resolved and the node state shows healthy in the NetBackup Flex Scale UI. To verify, navigate to Monitor > Infrastructure > Nodes.
- In iLO, verify that the Health of the Volume for the RAID 1 is set to OK.