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
- About Universal Shares
- Node and disk management
- Adding a node to the cluster using the NetBackup Flex Scale web interface
- License management
- Managing hardware vendor packages
- User management
- NetBackup Flex Scale network management
- Bonding operations
- Data network configurations
- Network configuration on plain device (eth5)
- Network configuration on bonded interfaces (bond0 on eth5 and eth7)
- NetBackup Flex Scale infrastructure monitoring
- Resiliency in NetBackup Flex Scale
- EMS server configuration
- Site-based disaster recovery in NetBackup Flex Scale
- Performing disaster recovery using RESTful APIs
- NetBackup Flex Scale security
- STIG overview for NetBackup Flex Scale
- FIPS overview for NetBackup Flex Scale
- Support for immutability in NetBackup Flex Scale
- Deploying external certificates on NetBackup Flex Scale
- Troubleshooting
- Collecting logs for cluster nodes
- Troubleshooting NetBackup Flex Scale issues
- Appendix A. Maintenance procedures for HPE servers
- Appendix B. Configuring NetBackup optimized duplication
- Appendix C. Disaster recovery terminologies
- Appendix D. Configuring Auto Image Replication
Validation error while adding VMware credentials to NetBackup
For protecting VMware virtual machines, you add the login credentials of the VMware vCenter Server, VMware ESXi server, or VMware vCloud Director server to the NetBackup configuration. While adding the access credentials, you may see the following credential validation error in the NetBackup Java Console UI.
VMware credential validation failed. Cannot connect on socket (Status 25)
This issue occurs when the NetBackup Flex Scale appliance cluster is configured using a pure IPv6 address configuration while the VMware system uses IPv4 addresses. NetBackup Flex Scale appliance does not support communication between a pure IPv6 and a pure IPv4 address configuration.
To resolve this issue, the VMware system must be configured to use either a pure IPv6 address or a mixed mode dual stack IP address configuration.