Veritas NetBackup™ Appliance Release Notes

Last Published:
Product(s): Appliances (3.2)
Platform: NetBackup Appliance OS

New Operational Notes for NetBackup Appliance 3.2

This topic describes the known issues for this release. Some of the issues that appear here may also apply to previous releases because some issues may have been discovered after the previous release became available.

You should also refer to the Release content appendix of this document to see the issues that have been resolved for this release.

Known issues for version 3.2:

  • Upgrades to version 3.2 using the NetBackup Appliance Shell Menu or the Appliance Management Console (AMS) do not support ECA deployment. After a successful upgrade, you can enable the ECA for NetBackup. For details, see the NetBackup Appliance Commands Reference Guide. Additionally, you can configure the ECA to the appliance infrastructure services such as mongodb, tomcat, and nginx. For details, see the NetBackup Appliance Security Guide.

  • For upgrades from versions 2.7.3 and 3.0 to version 3.2, all customized tuning values that are listed in the tune.pl file are changed to version 3.2 default settings. After these upgrades are completed, you must manually reapply any affected customized tuning values.

  • High availability (HA) deployments

    To help customers deploy new NetBackup Appliance HA installations, Veritas has created a checklist with links to various documents, including those that address related issues. For complete details, see the following article:

    https://www.veritas.com/support/en_US/article.100043658.html

  • When configuring the HA setup on the compute node, if the process fails, the failure message may take up to one hour to appear.

  • To upgrade the nodes in an HA setup, MSDP configuration is required on both the compute node and the partner node. Appliance HA node upgrades are not supported if MSDP is not configured.

  • If you configure an HA setup with two appliance nodes that did not have MSDP configured during their initial configuration, MSDP configuration must be completed from the compute node using the following command sequence:

    • Manage > Storage > Resize MSDP Catalog

    • Manage > Storage > Resize MSDP

    • Manage > High Availability > Switchover <partner node>

      The last command ensures that the HA setup is functioning correctly

    Note:

    The best practice is to always configure MSDP during the initial configuration of the appliance.

  • If you create an HA setup on an appliance compute node that was upgraded to version 3.2 and then attempt to add a partner node that is a new 3.2 version appliance, the process may fail and show the following message:

    - [Error] V-409-955-2025:
    The User ID/Group ID (uid/gid) for the mongod user on the partner node is different from
    the uid/gid for the mongod user on the active node. Refer to Veritas article 100046013.

    To resolve this issue, contact Veritas Support.

  • Before adding the partner node to complete an appliance HA setup, you must first verify that all NetBackup processes are running on the master server and on both HA nodes.

    If any processes are not running on the master server or on the nodes, adding the partner node fails. To prevent this failure, you must first stop all NetBackup processes and then restart them. For complete details, see the topic "Adding the partner node to the NetBackup 53xx high availability configuration" in the NetBackup 53xx Appliance Initial Configuration Guide.

  • After an upgrade to software version 3.2, NetBackup CLI users may not be able to log in to the appliance. To resolve this issue, log in to the appliance as the administrator and run the following command:

    Support->Service Restart nbapp-nbcli.

  • Appliance Management Server (AMS) upgrades

    Upgrades to software version 3.2 also upgrade appliances that have the AMS configured to AMS version 1.3. After the upgrade has completed and you attempt to upgrade other servers from the AMS console on the upgraded appliance, the preflight check fails on those attempts. To work around this issue, unconfigure and then reconfigure the AMS on the upgraded appliance as follows:

    • On the upgraded appliance where AMS is configured, log in to the NetBackup Appliance Shell Menu.

    • Enter the following command to unconfigure the AMS:

      Appliance > Management Server Unconfigure

    • Enter the following command to reconfigure the AMS:

      Appliance > Management Server Configure

  • If you plan to upgrade appliance media servers with software versions 2.7.3 or 3.0 that are configured as an Appliance Management Agent (AMA), the preflight check can fail and prevent the upgrade if the NetBackup security level is set to Very high. The following error message appears:

    Error: Preflight check failed, could not get the path for NB_certcmdTool

    To work around this issue, log in to the NetBackup Appliance Shell Menu from the IPMI console to upgrade these appliances.

  • For appliances that use the NetBackup Auto Image Replication feature, upgrades to version 3.2 may cause these replication jobs to fail due to an issue in NetBackup version 8.2.

    To resolve this issue, contact Veritas Support and ask the representative to provide you with the following EEB:

    NBAPP_EEB_ET3091133_3.2.0.0-4/x86_64.rpm

  • The Support > Collect Inventory command fails if you attempt to run it on NetBackup Appliance 5240 models that do not include a QLogic QLE8442 card. Any model 5240 with I/O configuration H is exempt, as it is not ISCSI capable. Although the command output results with a corresponding failure message, the underlying hardware monitoring continues to work except for the EthTool plug-in that handles SFP Alerts.