Please enter search query.
Search <book_title>...
Veritas NetBackup™ Flex Scale Release Notes
Last Published:
2022-11-25
Product(s):
Appliances (1.3.1)
Platform: NetBackup Flex Scale OS
- Getting help
- Features, enhancements, and changes
- Limitations
- Known issues
- Cluster configuration issues
- Cluster configuration fails if there is a conflict between the cluster private network and any other network
- Cluster configuration process may hang due to an ssh connection failure
- DNS servers that are added after initial configuration are not present in the /etc/resolv.conf file
- Initial configuration of the cluster fails if multiple DNS servers are specified in the YML configuration file
- Empty log directories are created in the downloaded log file
- For the private network, if you use the default IPv4 IP address but specify an IPv6 IP other than the default, the specified IPv6 IP address is ignored
- Disaster recovery issues
- Backup data present on the primary site before the time Storage Lifecycle Policies (SLP) was applied is not replicated to the secondary site
- When disaster recovery gets configured on the secondary site, the catalog storage usage may be displayed as zero
- Catalog backup policy may fail or use the remote media server for backup
- Takeover to a secondary cluster fails even after the primary cluster is completely powered off
- During disaster recovery migration phase, the new primary GUI goes into infinite loading state
- Catalog replication may fail to resume automatically after recovering from node fault that exceeds fault tolerance limit
- Infrastructure management issues
- FactoryReset operation exits without any message.
- Storage-related logs are not written to the designated log files
- Unable to start a node that is shut down
- Arrival or recovery of the volume does not bring the file system back into online state making the file system unusable
- Unable to replace a stopped node
- An NVMe disk is wrongly selected as a target disk while replacing a SAS SSD
- Disk replacement might fail in certain situations
- MEDIA_FS remain offline even though the disks are brought online
- Replacing an NVMe disk fails with a data movement from source disk to destination disk error
- Operations such as add node, replace node, and initial configuration of the cluster fail if the system clocks are not in sync
- Unable to detect a faulted disk that is brought online after some time
- Add node operation fails if the host name starts or ends with a hyphen
- Unable to view all the node details when selecting a replacement node
- When NetBackup Flex Scale is configured, the size of NetBackup logs might exceed the /log partition size
- Nodes may go into an irrecoverable state if shut down and reboot operations are performed using IPMI-based commands
- Add node fails because of memory fragmentation
- Replace node may fail if the new node is not reachable
- REST API message does not display STIG-compliant password rules if an incorrect password is specified while creating a user
- Miscellaneous issues
- If NetBackup Flex Scale is configured, the storage paths are not displayed under MSDP storage
- Failure may be observed on STU if the Only use the following media servers is selected for Media server under Storage > Storage unit
- Red Hat Virtualization (RHV) VM discovery and backup and restore jobs fail if the Media server node that is selected as the discovery host, backup host, or recovery host is replaced
- Primary server services fail if an nfs share is mounted at /mnt mount path inside the primary server container
- NetBackup fails to discover VMware workloads in an IPv6 environment
- The file systems offline operation gets stuck for more than 2hrs after a reboot all operation
- cvmvoldg agent causes resource faults because the database not updated
- SQLite, MySQL, MariaDB, PostgreSQL database backups fail in pure IPv6 network configuration
- Exchange GRT browse of Exchange-aware VMware policy backups may fail with a database error
- Networking issues
- DNS of container does not get updated when the DNS on the network is changed
- Cluster configuration workflow may get stuck
- Bond modify operation fails when you modify some bond mode options such as xmit_hash_policy
- Node panics when eth4 and eth6 network interfaces are disconnected
- LDAP configuration may fail for IPv6 addresses
- Upgrade issues
- After an upgrade, if checkpoint is restored, backup and restore jobs may stop working
- Upgrade fails during pre-flight in VCS service group checks even if the failover service group is ONLINE on a node, but FAULTED on another node
- During EEB installation, a hang is observed during the installation of the fourth EEB and the proxy log reports "Internal Server Error"
- EEB installation may fail if some of the NetBackup services are busy
- UI issues
- NetBackup Web UI is not accessible using the management server and API gateway IP or FQDN
- In-progress user creation tasks disappear from the infrastructure UI if the management console node restarts abruptly
- During the replace node operation, the UI wrongly shows that the replace operation failed because the data rebuild operation failed
- The maintenance user account password cannot be modified from the infrastructure UI
- Changes in the local user operations are not reflected correctly in the NetBackup GUI when the failover of the management console and the NetBackup primary occurs at the same time
- Mozilla Firefox browser may display a security issue while accessing the infrastructure UI
- Recent operations that were completed successfully are not reflected in the UI if the NetBackup Flex Scale management console fails over to another cluster node
- Cluster configuration issues
- Fixed issues
Software limitations
This section describes the software limitations in NetBackup Flex Scale.
The host name of any cluster node should not be the same as the FQDN of the IP that is assigned to the management interface or any publicly resolvable name.
Swagger does not support downloading of large files.
Veritas Call Home supports uploading of files with a maximum size of 2 GB. Larger file uploads may fail.