Please enter search query.
Search <book_title>...
Veritas NetBackup™ Flex Scale Release Notes
Last Published:
2024-02-06
Product(s):
Appliances (3.1)
Platform: NetBackup Flex Scale OS
- Getting help
- Features, enhancements, and changes
- What's new in this release
- Enhancements to the cluster configuration workflow
- Additional settings in NetBackup Flex Scale web UI to manage appliance infrastructure and settings
- Managing vendor packages
- Authenticating users using smart card and certificates
- Support for parallel upgrade
- Monitoring deviation in firmware, driver, and utility versions
- Monitoring cluster configuration
- Locating appliance disks
- Including or replacing an excluded disk
- Monitoring disk sync status
- Including an excluded node
- Restarting a node
- Starting and stopping NetBackup containers
- Switching management console to another cluster node
- Enhancements to log package
- Configuring static routes on a NetBackup Flex Scale cluster
- Audit logs
- Enhancements to the add data network workflow
- Enhancements to DNS workflow
- Enhancements to primary service replication
- Restricting remote management access
- Universal share user role
- Cloud bucket support
- Changes to the VxOS shell
- Support for NetBackup Client
- What's new in this release
- 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
- Node discovery fails during initial configuration if the default password is changed
- When NetBackup Flex Scale is configured, the size of NetBackup logs might exceed the /log partition size
- Error message is not displayed when NTP server is added as FQDN during initial configuration in a non-DNS environment
- All the selected EEBs are not uploaded during the initial configuration
- 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
- If the replication link is down on a node, the replication IP does not fail over to another node
- Task output message for migration operation appears as 'Force migrate operation is successful'
- Disaster recovery configuration may take around 2.5 hours to complete when data-collect task runs in the backend
- After disaster recovery takeover operation, the old recovery points or checkpoints for the primary server catalog file system are not visible in the GUI on the new primary site
- SLP templates are not created post disaster recovery configuration if lockdown mode is set to compliance or enterprise
- Policies and SLPs do not revert back when the new secondary site joins after a takeover operation
- Disaster recovery configuration hangs when eth5/bond0 interface is down on the node where management console and CVM services are online on one or both sites
- Miscellaneous issues
- 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
- 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
- Call Home test fails if a proxy server is configured without specifying a user
- In a non-DNS NetBackup Flex Scale setup, performing a backup from a snapshot operation fails for NAS-Data-Protection policy
- In a non-DNS environment, the CRL check does not work if CDP URL is not accessible
- Unable to add multiple host entries against the same IP address and vice versa in a non-DNS IPv4 environment
- Multiple mkfifo-related warning messages are displayed when logging in to the Veritas Appliance Shell
- Incorrect information is displayed for the support health check command in an IPv6 environment
- Change in host time zone is not reflected within containers
- NetBackup issues
- The engines and media servers go into unhealthy state if the CRL file has expired
- NetBackup service start operation for only one service may fail
- The NetBackup web GUI does not list media or storage hosts in Security > Hosts page
- Media hosts do not appear in the search icon for Recovery host/target host during Nutanix AHV agentless files and folders restore
- On the NetBackup media server, the ECA health check shows the warning, 'hostname missing'
- 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
- NetBackup primary server services fail if an nfs share is mounted at /mnt mount path inside the primary server container
- NetBackup primary container goes into unhealthy state
- Alerts and AutoSupport case might be created for NetBackup services that are stopped intentionally
- Starting or stopping multiple NetBackup services may fail on a media-server only cluster
- User login fails from the NetBackup GUI with authentication failed error
- Monitoring of the primary, media and storage servers for high availability does not work
- MSDP engine and media server fail to come up
- Networking issues
- Cluster configuration workflow may get stuck
- Node panics when eth4 and eth6 network interfaces are disconnected
- Add node fails during precheck when a secondary data network is configured over the management interface and the Automatic tab is used for providing input IPs for the new node to be added for the secondary data network over management interface
- Static route does not get added if any node of the cluster is powered off or not up
- Add secondary data network operation fails on the management interface of the secondary site of a cluster when the management network on the secondary site is not the same as the management network on primary site and disaster recovery is configured using a single virtual IP
- Node and disk management issues
- Storage-related logs are not written to the designated log files
- 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
- Replacing an NVMe disk fails with a data movement from source disk to destination disk error
- Unable to detect a faulted disk that is brought online after some time
- Nodes may go into an irrecoverable state if shut down and reboot operations are performed using IPMI-based commands
- Replace node may fail if the new node is not reachable
- Node is displayed as unhealthy if the node on which the management console is running is stopped
- Unable to collect logs from the node if the node where the management console is running is stopped
- Log rotation does not work for files and directories in /log/VRTSnas/log
- Unable to start or stop a cluster node
- Backup jobs of the workload which uses SSL certificate fail during or post Add node operation
- During an add node operation, the error shown on the Infrastructure page is not identical to the error seen when you view the task details
- Disk size is incorrectly shown as ? when an excluded disk is added back to the cluster
- Alerts about faulted disks are not resolved after disk or node replacement
- Number of online disks shown is incorrect after an OS disk goes offline
- After a replace node operation is performed on a deployment in which ECA is enabled, the universal share is not mounted on the new node's engine
- Health of the node does not change to unhealthy when disks are physically replaced
- AutoSupport settings are not synchronized on the newly added node
- Unhealthy node count is not updated when a node is shut down or stopped
- During an add node operation, you might be prompted to enter IPv6 addresses for a cluster with IPv4 addresses
- Incorrect error message shown when a node to be added restarts or panics
- Add node operation shows NetBackup configuration failure when a newly added node restarts during rebalancing of data
- Unhealthy disk are seen on the Infrastructure page after you delete a node from the cluster
- Disk might go in a faulted state after you include the same disk
- Proxy and etcd services do not came online when node shutdown fails
- After the management console node reboots, rollback of any running operations doesn't happen automatically
- Security and authentication issues
- NetBackup certificates tab and the External certificates tab in the Certificate management page on the NetBackup UI show different hosts list
- Replicated images do not have retention lock after the lockdown mode is changed from normal to any other mode
- Unable to switch the lockdown mode from normal to enterprise or compliance for a cluster that is deployed with only media servers and with lockdown mode set to normal
- User account gets locked on a management or non-management console node
- The changed password is not synchronized across the cluster
- Certificate renewal alert is not generated automatically during deployment
- Upgrade issues
- EEB installation may fail if some of the NetBackup services are busy
- During an upgrade the NetBackup Flex Scale UI shows incorrect status for some of the components
- Unable to upgrade from version 3.0.0.1 to 3.1 when an AD/LDAP server contains a maintenance user account and you attempt to change the maintenance user password
- Server busy error is displayed during an upgrade rollback
- Storage licensing check fails during a pre-upgrade check for a cluster where disaster recovery is configured
- After upgrade, MSDP cloud operations fail on an IPv6 setup if the cluster has MSDP cloud configured with data network in a non-DNS environment
- Add data network operation fails after an upgrade
- Alert about unsupported smartpqi driver is not resolved immediately after installing the kmod-smartpqi package
- UI issues
- During the replace node operation, the UI wrongly shows that the replace operation failed because the data rebuild operation failed
- 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
- Previously generated log packages are not displayed if the infrastructure management console fails over to another node.
- Smart card authentication fails for a cluster that includes both primary and media servers with IPv6 configuration
- Multiple tasks appear to be running in parallel during an add node operation
- Incorrect search results are displayed when you search for EEBs on the Software management > Add-ons tab
- EEB installation fails with Server busy error if you attempt to install another EEB immediately after installing a previous EEB
- Include disk option is not disabled on an offline node
- Dashboard shows an unconfigured icon for the NetBackup primary server when its status is offline
- NetBackup primary server status is shown online on the dashboard after performing a stop containers operation
- Cluster configuration issues
- Fixed issues
The engines and media servers go into unhealthy state if the CRL file has expired
When the ECA certificate is renewed after CRL file expiry, the media servers can remain in unhealthy state before the ECA validation gets completed. If the renewal task fails, the media servers may come up healthy after some time since the ECA is renewed on NetBackup components. But the API gateway and NetBackup Flex Scale GUI server still use the old certificates which need to be updated. As a result, the communication between API gateway and NetBackup web server does not work.
(IA-47892)
Workaround:
Redeploy the certificates to update all the components with same certificate.