Important Update: Cohesity Products Documentation
All Cohesity product documentation are now managed via the Cohesity Docs Portal: https://docs.cohesity.com/HomePage/Content/home.htm. Some documentation available here may not reflect the latest information or may no longer be accessible.
NetBackup™ Appliance Release Notes
- About NetBackup appliance 6.1
- NetBackup appliance 6.1 features, enhancements, and changes
- NetBackup Appliance Hardware features
- NetBackup Appliance compatibility
- Operational notes
- About operational notes for NetBackup appliance 6.1
- New operational notes for NetBackup appliance 6.1
- Upgrade and rollback notes
- General NetBackup Appliance notes
- NetBackup Appliance user interface notes
- Installation and configuration notes
- High availability notes
- About NetBackup support utilities
- About NetBackup appliance log files
- Appendix A. Related documents
New operational notes for NetBackup appliance 6.1
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.
If you configure SNMP V3 on the appliance, the documentation states that the password does not allow spaces, commas, and special characters. However, that information is incorrect. Spaces, commas, and special characters are allowed for SNMP V3 passwords.
If you restart a NetBackup appliance primary server when a large number of LUNs are attached, users may not be able to sign in to the NetBackup web UI. If you experience this issue, see the article 100073166 on the Cohesity Support website:
After you upgrade to NetBackup appliance 6.1, if you use VxLogView against a module under the Main > Support > Logs command, it fails. For example:
Logs > VxLogView Module CallHome V-1-26 Configuration setting not found for given product/originator id.
If you need to view the unified log files, contact Technical Support for assistance. Ask your representative to reference article 100073323.
The NetBackup appliance 6.1 PasswordAge expiry settings are not preserved after an upgrade. The value of PasswordAge, even when manually set before the upgrade through CLISH (Settings > Security > PasswordAge Set <Min Age> <Max Age>), is reset to the default values (Min Age: 1 day, Max Age: 60 days) after the upgrade.
During the reboot following the upgrade, VxOS performs STIG hardening, which deletes and recreates the
/etc/login.defsfile. This file contains the PasswordAge configuration.To fix this issue, manually set the password expiry age again:
Settings > Security
PasswordAge Set < Min Days> <Max Days>
You can verify the change using the Security PasswordAge Show command.
If you install NetBackup appliance 6.1 and configure MFA, and create a local user, the system prompts for a password reset. But after resetting the password, no confirmation message is displayed indicating that the password has been successfully changed.
You can login with the new password even if the message is not displayed.
When attempting to perform Password Expiry Age/Now, the system does not allow the operation for local users.
This issue can be ignored as there is no impact on functionality.
After a node reboot or restart, the NetBackup processes do not start automatically. You must manually start them using the NetBackup Start command.
When attempting to access the LUServer, a message appears stating that the server has been migrated from symantec.com to broadcom.com. This prevents access to the default LUServer on NetBackup appliance 6.1.
If Broadcom provides a new URL, update it using the option.
The Swagger document link for the NetBackup appliance API does not open because the hostname used is a short name, which is not network-resolvable. This occurs when the short name is configured as the primary server name during NetBackup appliance setup.
If the short name is intended to be the primary name, ensure it is resolvable in the network. After opening the link, replace the short hostname with the fully qualified domain name (FQDN) in the URL and reload the page.