Please enter search query.
Search <book_title>...
Veritas NetBackup™ Flex Scale Release Notes
Last Published:
2024-07-25
Product(s):
Appliances (3.2)
Platform: NetBackup Flex Scale OS
- Getting help
- Features, enhancements, and changes
- What's new in this release
- Simplifying cluster deployment with an integrated precheck
- Configuring multifactor authentication
- Configuring single sign-on (SSO)
- Bonding management interfaces during initial configuration
- Bonding operations on management network
- Connecting eth7 network interface optional during initial configuration
- Support for VMware and Tape out backups over Fibre Channel
- Support for Data Domain storage
- Collecting time-based logs
- Forwarding logs to an external server
- Changes to the licensing model
- Support for parallel installation of EEBs
- Support for only parallel upgrades
- Including vendor packages on appliance nodes
- Configuring the console FQDN
- Configuring MTU on public interfaces
- 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
- During cluster configuration, sysadmin user is not detected on some of the nodes
- 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
- 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
- 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
- Incorrect information is displayed for the support health check command in an IPv6 environment
- Change in host time zone is not reflected within containers
- Failed to sync certificate from NetBackup primary server
- Password change for sysadmin user is partially successful
- Frequent alerts related to sysadmin users are generated and resolved automatically
- Universal Share backup does not happen when NetBackup Flex Scale is configured with IPv6
- Unable to generate kernel crash
- NetBackup issues
- The NetBackup web GUI does not list media or storage hosts in Security > Host mappings 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
- User login fails from the NetBackup GUI with authentication failed error
- MSDP engine and media server fail to come up
- Oracle Snapshot backup for Oracle workload fails with an error
- MSDP storage server may go down in a multi-domain scenario if the same user is used by two or more NetBackup domain
- Backup for Nutanix fails with status code 6
- Operation to start NetBackup services fails on a NetBackup Flex Scale cluster with media only deployment
- Sometimes the NetBackup media services in a container cannot start
- All the added media servers are not reflected in the Data Domain OST STU
- 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
- Data network details are not visible on NetBackup Flex Scale UI after console IP change
- Adding secondary data network at the secondary site using automatic mode fails
- Adding secondary data network to the secondary site fails if ECA is configured on the cluster
- If IP address is assigned to a VLAN over a bond on a node using the set network bond command, SSH using admin user does not work
- Create/remove bond operations are possible on both data and management networks from the GUI when secondary data/management network is present
- Add secondary data network operation does not fail on the secondary site if the same NetBackup primary IP/FQDN is used to add the secondary data network in both the primary and secondary site
- 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
- 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
- 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
- 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
- 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
- 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
- Proxy and etcd services do not come online when node shutdown fails
- After the management console node reboots, rollback of any running operations doesn't happen automatically
- No value is displayed in the Used for column for faulted or excluded data disks
- ECA deployment fails for a newly added node on a cluster on which both primary and media servers are configured
- Sysadmin user password is not synced to a newly added node
- Add node operation fails while rebalancing data
- After upgrade from a prior release to 3.2, add node fails if MSDP has at least one Cloud LSU configured
- Replace node fails with error "Failed to check connectivity with the gateway"
- 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
- 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
- During IPMI restriction enable/disable operation, some of the nodes operations may fail
- After switching to FIPS security mode, all the users are deleted including the sysadmin user and the Administrator password is reset to default pull tag password
- 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.2 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
- 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
- Pre-upgrade check fails intermittently on the primary cluster
- Incorrect status is shown for the appliance firmware components after a firmware upgrade
- Failed to replace a node after upgrading from 3.0 to 3.2
- While upgrading and post upgrade to 3.2 on an ECA configured cluster, you may see '502 Bad Gateway' error while accessing the NetBackup Flex Scale UI using management gateway FQDN or IP
- Upgrade progress continues to remain in the same state at 51% after all the node are rebooted
- 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
- Upgrade progress is not updated on the View details page of the GUI
- Only three IPMI IP addresses are shown in the GUI post configuration for a four node iLO-FIPS enabled cluster
- Cluster configuration issues
- Fixed issues
Node panics when eth4 and eth6 network interfaces are disconnected
When the network interfaces corresponding to eth4 and eth6 go offline or manually made offline using commands such as, ifconfig ethx down, the node panics, and restarts. This is because when the private network links used for LLT heartbeat messaging are disconnected, the node gets isolated from the other nodes in the cluster and to avoid network split brain, the vxfencing module performs node membership arbitration and deliberately panics the node to avoid data corruption.
Network interfaces corresponding to eth4 and eth6 should never be disconnected as they are used as private heartbeat links among cluster nodes. (IA-26984)
The following are sample messages in the crash dump of the node that panics:
[19737.900357] LLT INFO V-14-1-10032 link 0 (eth4) node 2 inactive 15 sec (16250505) [19737.950354] LLT INFO V-14-1-10509 link 0 (eth4) node 2 expired [19738.050361] LLT INFO V-14-1-10032 link 0 (eth4) node 3 inactive 15 sec (16250505) [19738.100361] LLT INFO V-14-1-10509 link 0 (eth4) node 3 expired [19742.720979] VXFEN INFO V-11-1-80 RACER Node is: 0 [19742.720998] VXFEN INFO V-11-1-87 Initiating VxFen Race [19742.720999] VXFEN INFO V-11-1-111 VxFen Pre-Race Delay: 0 [19742.721012] VXFEN INFO V-11-1-119 LEADER Node : 0 is in current sub-cluster [19742.721018] VXFEN CRITICAL V-11-1-89 RACER Node lost the VxFen race [19742.721019] VXFEN INFO V-11-1-112 VxFen Post-Race Delay: 0 [19742.721023] VXFEN NOTICE V-11-1-92 Sending LOST_RACE [19742.721075] Kernel panic - not syncing: VXFEN CRITICAL V-11-1-20 Local cluster node ejected from cluster to prevent potential data corruption. [19742.722157] CPU: 0 PID: 8953 Comm: vxfen Kdump: loaded Tainted: P OE ------------ T 3.10.0-1062.9.1.el7.x86_64 #1 [19742.722486] Hardware name: Veritas NetBackup Archive 3420/X11DPU, BIOS 3.0c 03/27/2019 [19742.722808] Call Trace: [19742.722965] [<ffffffffa757ac23>] dump_stack+0x19/0x1b [19742.723129] [<ffffffffa7574967>] panic+0xe8/0x21f [19742.723300] [<ffffffffc10668f2>] vxfen_plat_panic+0xc2/0xd0 [vxfen] [19742.723467] [<ffffffffc1054d61>] vxfen_process_client_msg+0x6d1/0xb30 [vxfen] [19742.723779] [<ffffffffc1055d23>] vxfen_vrfsm_cback+0x323/0x1750 [vxfen] [19742.723947] [<ffffffffc1055a00>] ? vxfen_reconfig_msg+0x840/0x840 [vxfen] [19742.724117] [<ffffffffc1073be8>] vrfsm_step+0x1c8/0x3a0 [vxfen] [19742.724280] [<ffffffffc1055a00>] ? vxfen_reconfig_msg+0x840/0x840 [vxfen] [19742.724448] [<ffffffffc1075521>] vrfsm_recv_thread+0x401/0x9b0 [vxfen] [19742.724613] [<ffffffffc1075120>] ? vrfsm_defer_message+0x140/0x140 [vxfen] [19742.724782] [<ffffffffc10761ee>] vxplat_lx_thread_base+0x9e/0xf0 [vxfen] [19742.724947] [<ffffffffc1076150>] ? vxplat_assert+0x20/0x20 [vxfen] [19742.725123] [<ffffffffa6ec61f1>] kthread+0xd1/0xe0 [19742.725282] [<ffffffffa6ec6120>] ? insert_kthread_work+0x40/0x40 [19742.725449] [<ffffffffa758dd1d>] ret_from_fork_nospec_begin+0x7/0x21 [19742.725611] [<ffffffffa6ec6120>] ? insert_kthread_work+0x40/0x40
Workaround:
Bring eth4 and eth6 online to allow the node to join the cluster properly.