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
Choosing the correct input method for data network configuration
You can provide inputs for IP/FQDN either using the Automatic tab or Custom tab from the GUI for operations such as initial configuration, add data network and add node.
Automatic tab:
The Automatic tab accepts only IP address. You can specify a single IP range, multiple IP ranges separated by a comma, comma-separated individual IP addresses, a combination of individual IP addresses and IP ranges separated by a comma, or IP addresses in CIDR format. The FQDN is retrieved using nslookup depending on the DNS server and search domain entry provided for that network. For nslookup to work correctly, the DNS server provided should be valid. In case only the short host name is specified as the FQDN, the correct search domain strings should be specified for nslookup to work correctly. The IP/FQDN validation check fails in case there is no information about the IP address in the DNS server provided.
Custom tab:
The Custom tab accepts both IP address and FQDN and does validation using forward and reverse lookup of the IP address. When Custom tab is used for providing input, the IP/FQDN validation check only fails when there is a conflict between the IP address and FQDN. There can be a conflict:
If the forward lookup of an FQDN returns an IP address which is different than the input IP provided.
If the reverse lookup of an IP address returns an FQDN which is different than the input FQDN provided.
In a non-DNS environment, if the Custom tab is used, the IP/FQDN validation check is skipped.
Consideration while choosing Automatic or Custom tab for providing input for IP/FQDN.
During initial configuration, if the IP/FQDN entries exist in the DNS, use the Automatic tab for providing input IP.
During initial configuration, if the DNS server is not specified or if the IP/FQDN entries do not exist in the DNS, then Custom tab should be used to provide the inputs for both IP address and FQDN.
During data network addition, if DNS server in configured for that network, then Automatic tab is enabled by default. Automatic tab can be used if the IP/FQDN entries are already added in DNS.
During data network addition, if DNS server is not configured or if the IP/FQDN entries do not exist in the DNS server, then the Custom tab should be used for providing input for both IP/FQDN.
During node addition operation, if DNS is configured for the data network, the Automatic tab should be used for providing input for data network IPs.
During node addition operation, if DNS is not configured or if the IP/FQDN entries do not exist in the DNS server then the Custom tab should be used for providing input for both IP/FQDN.
During node addition operation, when a secondary data network exists on the management interface (eth1 or eth1.<VLANID>), the Custom tab should be used for providing input for both IP/FQDN for the secondary data network IPs.