Veritas NetBackup™ Flex Scale Release Notes

Last Published:
Product(s): Appliances (1.3)
Platform: NetBackup Flex Scale OS
  1. Getting help
    1.  
      About this document
    2.  
      NetBackup Flex Scale resources
  2. Features, enhancements, and changes
    1.  
      NetBackup Flex Scale features
    2.  
      Support for NetBackup Client
  3. Limitations
    1.  
      Software limitations
    2.  
      Unsupported features of NetBackup in NetBackup Flex Scale
  4. Known issues
    1. Cluster configuration issues
      1.  
        Cluster configuration fails if there is a conflict between the cluster private network and any other network
      2.  
        Cluster configuration process may hang due to an ssh connection failure
    2. Disaster recovery issues
      1.  
        Backup data present on the primary site before the time Storage Lifecycle Policies (SLP) was applied is not replicated to the secondary site
      2.  
        When disaster recovery gets configured on the secondary site, the catalog storage usage may be displayed as zero
      3.  
        Using the secondary storage unit for backup or duplication before disaster recovery configuration is complete, can result in data loss
      4.  
        Catalog backup policy may fail or use the remote media server for backup
      5.  
        The status of the master server catalog replication status appears as "needs failback synchronization" or "needs DCM resynchronization"
      6.  
        In-domain disaster recovery configuration may fail if there are more than eight nodes in each site
      7.  
        During disaster recovery, after takeover operation, replace node operation can fail on the newly formed secondary site
      8.  
        After a takeover operation, data network operations may fail on the newly formed secondary site
      9.  
        Takeover to a secondary cluster fails even after the primary cluster is completely powered off
    3. Infrastructure management issues
      1.  
        FactoryReset operation exits without any message.
      2.  
        Storage-related logs are not written to the designated log files
      3.  
        Unable to start a node that is shut down
      4.  
        Arrival or recovery of the volume does not bring the file system back into online state making the file system unusable
      5.  
        Unable to replace a stopped node
      6.  
        An NVMe disk is wrongly selected as a target disk while replacing a SAS SSD
      7.  
        Disk replacement might fail in certain situations
      8.  
        Adding a node using REST APIs fails when the new node tries to synchronize the EEBs or patch updates installed on the cluster
      9.  
        Replacing an NVMe disk fails with a data movement from source disk to destination disk error
      10.  
        When NetBackup Flex Scale is configured, the size of NetBackup logs might exceed the /log partition size
      11.  
        Nodes may go into an irrecoverable state if shut down and reboot operations are performed using IPMI-based commands
      12.  
        Replace node may fail if the new node is not reachable
    4. Miscellaneous issues
      1.  
        If NetBackup Flex Scale is configured, the storage paths are not displayed under MSDP storage
      2.  
        Failure may be observed on STU if the Only use the following media servers is selected for Media server under Storage > Storage unit
      3.  
        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
      4.  
        Primary server services fail if an nfs share is mounted at /mnt mount path inside the primary server container
      5.  
        NetBackup fails to discover VMware workloads in an IPv6 environment
    5. Networking issues
      1.  
        DNS of container does not get updated when the DNS on the network is changed
      2.  
        Cluster configuration workflow may get stuck
      3.  
        Bond modify operation fails when you modify some bond mode options such as xmit_hash_policy
      4.  
        Node panics when eth4 and eth6 network interfaces are disconnected
    6. Upgrade issues
      1.  
        After an upgrade, if checkpoint is restored, backup and restore jobs may stop working
      2.  
        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
      3.  
        During EEB installation, a hang is observed during the installation of the fourth EEB and the proxy log reports "Internal Server Error"
      4.  
        EEB installation may fail if some of the NetBackup services are busy
    7. UI issues
      1.  
        NetBackup Web UI is not accessible using the management server and API gateway IP or FQDN
      2.  
        In-progress user creation tasks disappear from the infrastructure UI if the management console node restarts abruptly
      3.  
        During the replace node operation, the UI wrongly shows that the replace operation failed because the data rebuild operation failed
      4.  
        The maintenance user account password cannot be modified from the infrastructure UI
      5.  
        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
      6.  
        Mozilla Firefox browser may display a security issue while accessing the infrastructure UI
  5.  
    Fixed issues

FactoryReset operation exits without any message.

This issue occurs if the node is partially a part of an active cluster. The node is configured in the cluster, but due to some reason, the high availability service is not healthy on this node. (APPSOL-137764)

Workaround:

Contact Veritas Technical Support and ask them to refer to article 100049211.