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
Configuring an external BYOS media server
You can configure an external BYOS media server (EMS) with NetBackup Flex Scale.
To configure an external BYOS media server with NetBackup Flex Scale 3.1
- Deploy mapping BYO on the external media server.
Enter the NetBackup Flex Scale primary server details.
Enter the token that you get from the primary server.
- Go to Host Properties > Primary Server > Servers > Additional server tab. Add an entry for the external media server on the primary server.
- Go to Host Properties > Media Server > Servers -> Additional server tab. Add an entry for the external media server (all media cluster nodes).
- Go to Host Properties > Clients > Servers > Additional server tab. Add an entry for the external media server on the client server.
- Run the following command:
# ./nbemmcmd -addhost -machinename ems_fqdn -machinetype media -primaryserver primary_server_fqdn -operatingsystem Linux -netbackupversion 10.0
NBEMMCMD, Version: 10.0 Command completed successfully.
where ems_fqdn is the external media server FQDN and primary_server_fqdn is the primary server FQDN.
- Restart the EMS server services.
- Add the DNSMASQ entry on the EMS server. If the EMS server is Linux, you have to add the server's IP and FQDN entry as the nameserver. If the EMS server is a Windows server, give the preferred DNS as DNSMASQ server's IP. This entry is required if you want the EMS to get connected to the secondary site primary server after disaster recovery.
- Perform a robot inventory. Go to Configure Storage devices and confirm that the external media server is detected.
To perform a robot inventory, refer to the Veritas NetBackup™ Administrator's Guide, Volume I.
If you have configured disaster recovery and want to configure an external media server, then perform the following steps:
Clear the host cache on the primary server node
bpclntcmd -clear_host_cache
Check for the correct IP resolved by EMS after disaster recovery is configured:
# bptestnetconn # bptestbpcd -M primary FQDN # bpclntcmd -hn primary FQDN
After clearing the host cache, bptestnetconn paramenter should not show the entry, Stale entry message for EMS server.