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
- Directory services and certificate management
- Region settings management
- About NetBackup Flex Scale storage
- About Universal Shares
- Creating a Protection Point for a Universal Share
- Node and disk management
- License management
- NetBackup Flex Scale network management
- About network management
- Modifying DNS settings
- About bonding Ethernet interfaces
- Bonding operations
- Data network configurations
- 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
- 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
- Troubleshooting
- Services management
- Collecting logs for cluster nodes
- Checking and repairing storage
- 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. Configuring NetBackup optimized duplication
- Appendix B. Disaster recovery terminologies
- Appendix C. Configuring Auto Image Replication
About network management
You can perform network-related operations in the > Network panel. You can find the details of the network settings for the data network, management network, appliance management console, DNS, and the IPMI network for the cluster.
The data network that is created during the initial configuration is the primary network and the new data networks added by the user after the initial configuration are the secondary data networks.
> displays the data networks configured in the cluster. You can add new secondary data networks and modify or delete existing secondary data networks. You can perform interface bonding at the time of initial configuration or after cluster configuration. You can also create a bond of interfaces, modify the existing bond modes and Maximum Transmission Value (MTU), display current bond mode and remove bond(s). There may be network disruptions when you perform bonding operations.
See Data network configurations.
See Bonding operations.
> displays the details about the Domain Name Server (DNS).
Domain name
DNS servers
Search Domains
You can edit the DNS settings.
> displays about the management network.
It includes information such as:
Routing settings
This includes details such as the subnet mask and gateway of IPv4 addresses and details such as prefix length and router address of IPv6 addresses.
Management interfaces
Specifies the management interface assignment for each node in the cluster.
> displays the details about the IPMI network, if configured.
It includes information such as:
Routing settings
This includes details such as the subnet mask and gateway of IPv4 addresses and details such as prefix length and router address of IPv6 addresses.
IPMI interfaces
Specifies the IPMI interface assignment for each node in the cluster.
> specifies the network settings for the appliance management console. If you did not configure the management network earlier, these settings apply only on the data network.
The following details are displayed:
Console IP
API Gateway IP
API Gateway node
API Gateway FQDN
Note:
If you deploy a cluster with only media servers, only the console IP is displayed.