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
- 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
- Node and disk management
- License management
- 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
- 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
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.0
- 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, Version: 10.0 Command completed successfully.
where ems_fqdn is the external media server FQDN and 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 # bpclntcmd -hn
After clearing the host cache, bptestnetconn paramenter should not show the entry, Stale entry message for EMS server.