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 both OS disks on a non- management console node
This topic describes the process of replacing both the OS disks that failed or are unreachable on a non- management console node. Each node includes two OS disks.
To identify the management console node, in the NetBackup Flex Scale infrastructure management UI, navigate to . On the Infrastructure page, Console node shows the management console node and the remaining nodes are the non-management console nodes.
If both OS disks go bad or are unreachable on a non-management console node of the cluster, you receive email alerts if SMTP is configured for AutoSupport. In the NetBackup Flex Scale infrastructure management console UI, the node status is shown unhealthy for the node where the failure occurs. Navigate to to view the node status.
Note:
For NetBackup Flex Scale version 3.0, stale information is displayed for the node state. The node is shown healthy.
The HPE Integrated Lights-Out (iLO) remote console shows a failure. The health of the OS disks and the logical drive of RAID 1 is shown as Critical in the iLO remote console.
An HPE representative identifies the faulty disk, its physical location in the appliance, and replaces the OS disks. The representative can use the AHS logs to find the required details, and then replaces both the disks simultaneously so that the logical drive (RAID 1) can be created.
Note:
With NetBackup Flex Scale version 3.1, you can beacon the disk from the UI
When replacing the disks, ensure that the new disks have the same model number as the old disks. Check the model number in the iLO remote console. To create the logical drive (RAID 1 configuration), ensure that both the OS disks are replaced at the same time.
After the hardware vendor notifies you that the hardware component is replaced, verify that the issue is resolved.
After physical disk replacement, check OS disks and the logical drive status in the iLO remote console. If the logical drive status is shown as Critical, fix the failed drive; else proceed with node replacement.
To fix the failed logical drive, identify the logical drive, delete the existing failed logical drive, and create it again. After you recreate the logical drive, replace the node where both the OS disks have failed.
Identifying the OS logical drive
To identify the OS logical drive:
In the NetBackup Flex Scale UI, you get an alert with slot and physical drive ID for faulted disk. Use this information to identify the volume that has that physical drive.
The OS disks are of 2TB each. Check the volume that has those disks in the iLO remote console.
Once you identify the failed logical drive, delete the existing failed logical drive, and recreate it.
Deleting the logical drive
To delete the logical drive:
- Log in to the iLO remote console and launch the console for the node:
- In the left pane, click HPE Smart Array P816i-a SR Gen10.
- Delete the logical drive:
- The deleted logical drive is no longer listed once you delete it. Ensure that under Unassigned Drives, 2 unassigned drives is displayed.
Recreating the logical drive
To create the logical drive again:
- Log in to the iLO remote console and launch the console for the node:
- In the left pane, click HPE Smart Array P816i-a SR Gen10.
This will expand the list of Controller Devices and Tools along with available Actions as Storage Administrator.
- To create logical drive, click Unassigned Drives in the left pane, and then click Create Array.
- Select OS disks from Unassigned Drives and click Create Array.
- Click Yes to confirm.
- Click RAID 1, and then click Create Logical Drive.
- Click Yes to confirm.
- Click Finish.
The logical drive is created.
Replacing the node
To replace the node:
- Check the node status in the NetBackup Flex Scale infrastructure management UI. The node is shown unhealthy and the node status is offline.
- Prepare the node for replacement:
Deploy ISO on the failed node where the OS disks were replaced.
Perform factory reset on that node from the node CLI by using the system factory-reset command.
- From the NetBackup Flex Scale infrastructure management UI perform the replace node operation.
Scan for nodes. Click Scan for nodes to discover the nodes.
Select a node from the displayed list and replace the node. For the unhealthy node, click the Actions menu (vertical ellipsis) from the right side of the row in the UI, and click Replace node.
In the Replace node dialog box, select the node that you want to use to replace the unhealthy node and click Replace node.
- After the replace node operation completes successfully check the node status in the NetBackup Flex Scale infrastructure management UI. Navigate to Monitor > Infrastructure > Nodes. The node is online and shown healthy.
Click Dashboard and verify that all the NetBackup services are running.