Translation Notice
Please note that this content includes text that has been machine-translated from English. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.
Netbackup Appliance 5.3.0.1 Maintenance Release 2
Abstract
Description
NetBackup Appliance 5.3.0.1 Maintenance Release 2 (MR2) is a full package that includes NetBackup Appliance 5.3, 5.3 SP1, 5.3 SP2, 5.3.0.1 MR1, 5.3.0.1 MR1 SP1, NetBackup 10.3.0.1 content. 5.3.0.1 MR2 obsoletes 5.3.0.1 MR1. MR2 also includes additional critical product and security fixes specific to NetBackup Appliance.
MR2 can be installed only on the following NetBackup Appliance releases:
- 5.3, 5.3 SP1, 5.3 SP2, 5.3.0.1 MR1, 5.3.0.1 MR1 SP1, 5.3.0.1 MR1 SP2
- 5.1.1, 5.1.1 SP1, 5.1.1 SP2, 5.1.1 MR1, 5.1.1 MR1 SP1, 5.1.1 MR1 SP2, 5.1.1 MR1 SP3, 5.1.1 MR2, 5.1.1 MR2 SP1, 5.1.1MR3, 5.1.1MR4
- 5.0, 5.0.0.1 MR1, 5.0.0.1 MR1 SP1, 5.0.0.1 MR1 SP2, 5.0.0.1 MR2, 5.0.0.1 MR2 SP1, 5.0.0.1 MR3, 5.0.0.1 MR4, 5.0.0.1 MR5
- 4.1, 4.1.0.1 MR1, 4.1.0.1 MR2, 4.1.0.1 MR3, 4.1.0.1 MR4, 4.1.0.1 MR5
Overview
NetBackup Appliance 5.3.0.1 Maintenance Release 2, Includes NetBackup Appliance 5.3, 5.3 SP1, 5.3 SP2, 5.3.0.1 MR1, 5.3.0.1 MR1 SP1, 5.3.0.1 MR1 SP2, NetBackup 10.3.0.1 and additional important product and security fixes.
MR Download Details
File Name | VRTS_NBAPP_update-5.3.0.1-20240704104931.x86_64.rpm |
Download Link | https://www.veritas.com/content/support/en_US/downloads/update.UPD374317 |
Download Size | 9422585971 |
sha256checksum | 88bd3628ec1b89341cf4c1c7b0dcc33d00fb0c8c2f5b6d49a821e06315830d36 |
Compatibility Details
Supported Upgrade Paths
5.3.0.1 MR2 supports upgrades from the following appliance versions |
|||||||||||
5.3 |
5.3 SP1 |
5.3 SP2 |
5.3.0.1 MR1 |
5.3.0.1 MR1 SP1 |
5.3.0.1 MR1 SP2 |
||||||
5.1.1 |
5.1.1 SP1 | 5.1.1 SP2 | 5.1.1 MR1 | 5.1.1 MR1 SP1 | 5.1.1 MR1 SP2 | 5.1.1 MR1 SP3 | 5.1.1 MR2 | 5.1.1 MR2 SP1 | 5.1.1 MR3 | 5.1.1 MR4 | |
5.0 |
5.0.0.1 MR1 |
5.0.0.1 MR1 SP1 |
5.0.0.1 MR1 SP2 |
5.0.0.1 MR2 |
5.0.0.1 MR2 SP1 |
5.0.0.1 MR3 |
5.0.0.1 MR4 |
5.0.0.1 MR5 |
|||
4.1 |
4.1.0.1 MR1 |
4.1.0.1 MR2 |
4.1.0.1 MR3 |
4.1.0.1 MR4 |
4.1.0.1 MR5 |
NetBackup Appliance 5.3.0.1 MR2 supports direct upgrade from 4.1 and later versions. Pre-4.1 versions need to upgrade twice.
Appliance Management Server (AMS) 2.2 support 5.3.0.1 MRs, including MR2.
Note: Appliances running NetBackup Appliance version 5.3 or later will be able to initiate upgrade action from the System Health Insights dashboard. The upgrade process becomes easy for the users as System Health Insights will be initiating, monitoring, and executing it with minimum user actions or external interference. For additional information, see the section Appliance Upgrade in the Veritas System Health Insights User Guide.
The following limitations are true regarding Appliance Connectivity Toolkit (ACT), upgrade automation feature support for Security Patches (SPs):
- Upgrade from 5.3 to any 5.3 SPx is not supported.
- Upgrade from any older SPx or 5.3 SPx to 5.3.0.1 MRx is not supported.
Supported Appliance Models
Appliance model name |
5240 |
5250 |
5330 |
5340 |
5330HA |
5340HA |
5350HA |
5350 |
NBVA |
5240 Cloud Catalyst appliances |
5.3.0.1 MR2 Support |
|
|
|
|
|
|
|
|
|
|
Supported NetBackup versions
- MR2 is compatible with a primary server running 10.3 or later release. 10.3 Primary server does support a media server running 5.3.0.1 MR2 or 10.3.0.1.
- NetBackup 10.3.0.1 administrative console is required for accessing NetBackup Appliances running MR2
Installation and Additional instructions
Appliance Upgrade Readiness Analyzer
The Appliance Upgrade Readiness Analyzer can be downloaded from here.
See here for more information about the Appliance Upgrade Readiness Analyzer.
Installation Time
Upgrading to 5.3.0.1 MR2 takes about two hours including rebooting.
Pre-Installation steps
- Confirm that no backup jobs are scheduled during the upgrade period.
- Deactivate all policies to ensure that no backups target the appliance you are upgrading.
- Cancel all active jobs from the NetBackup WebUI or Java Administration Console or log in to the appliance as a NetBackup CLI user and run the following command: bpdbjobs -cancel_all
- For Primary server appliances, stop data collection for Ops Center or NetBackup IT Analytics.
- For Media Server appliances, stop data collection on NetBackup IT Analytics if installed on the media server to be upgraded.
- Disable all Storage Life Cycle Policies that duplicate to/from the Media Appliances that are to be upgraded.
- The reboot that happens as part the upgrade can take a very long time if there are many LUNs. Hence, during the upgrade if the appliance can see VMWare datastores via SAN, disable the port in the SAN (on all nodes if HA appliance is involved). Once the upgrade is completed, enable the SAN port and initiate a scan of the FC.
- Veritas requires that you run the upgrade readiness analyzer on each appliance before you upgrade. Unless the Appliance is registered in NetInsights Console/System Health Insights, with Call Home enabled, and with the Health Maintenance plugin installed.
- The Health Maintenance plugin collects upgrade readiness data and displays it in System Health Insights under the Upgrade Center tab. Information about the Health Maintenance plugin is available here.
- For AMS, you must run the analyzer tool from the shell menu
- For AMS, If inventory is not collected on the System Health Insights portal after an upgrade, you can collect inventory from the Clish by navigating to Support > Collect Inventory.
- Review the 5.3 Upgrade Checklist and verify all pre-upgrade steps are completed.
Note that any references to the upgrade readiness analyzer version in the checklist are superseded by the upgrade readiness analyzer available here.
- NetBackup Appliance 5.3.0.1 MR2 Media server is compatible with Primary servers running NetBackup Appliance versions 5.3/ 5.3.0.1 MR1/5.30.1 MR2 or NetBackup versions 10.3/10.3.0.1.
- If using System Health Insights, Upgrade Center, refer to the System Health Insights Users Guide, section titled Appliance Upgrade here.
- If the MR2 installer detects the Firmware update tool EEB, it uninstalls it automatically. However, all previous firmware updates remain installed.
- It is normal for the appliance to reboot automatically about midway through the MR2 installation.
- Review the available downloads from the Clish option Manage > Software > List AvailablePatch lists GA and MR patches. Before downloading one of the listed patch, verify the information regarding patch on DC and verify if you already have the patch installed on system from Clish > Manage > Software >List Version.
Additional installation instructions for NetBackup Appliance 5340 High Availability (HA) setup
- Before installing MR2 on both nodes, ensure that the two-node HA setup is fully configured.
- Start the upgrade process on the node where the MSDP service and the virtual IP service are offline, typically, the partner node.
- After the partner node has been upgraded, run the Manage > High Availability > Switchover command to bring the Virtual IP online on the node installed with MR2.
- The HA status can be checked by using the following command: Manage > HighAvailability > Status
If the HA services status is not as described in the following table, contact Veritas Support for assistance.
HA Services |
Status on primary node |
Status on partner node |
Advance Disk |
Online |
Online |
Fingerprint calculation |
Online |
Online |
MSDP |
Online |
Offline |
Virtual IP |
Online |
Offline |
- For information on configuring a two-node HA setup, see the Veritas NetBackup Appliance High Availability Reference Guide.
- Switchover to the original node to ensure correct functionality.
Post-Installation Instructions
- The newly installed version can be checked using either of the following commands. The expected output of each command is also included.
Manage > Software > UpgradeStatus
The appliance version is 5.3.0.1 Maintenance Release 2 and not in upgrade state.
Manage > Software > List Version
Appliance Version: 5.3.0.1
NetBackup Version: 10.3.0.1
Build Date: 5.3.0.1-20231018123020
Maintenance Release Version: 2
Appliance > Status
Appliance Model is NetBackup Appliance 5xxx.
Appliance Version is 5.3.0.1 Maintenance Release 2.
Product Fixes in MR2
MR2 includes all important product fixes in 5.3 and 5.3.0.1 MR1, additional product fixes listed below.
Note: APPCPE numbers are for Veritas Support reference only.
JIRA Number |
Description |
APPCPE-17108 |
5301MR2 PCI and Expansion Shelf components will be displayed appropriately |
APPCPE-16953 |
NBA 5301 MR2 Appliance hardware info will be displayed correctly |
APPCPE-17133 |
Changed "enable" in nba repo to "enabled" |
APPCPE-17000 |
NBA 5301MR2 If the RealStor alert is active and unresolved , those alerts will not be resolved by Daily Summary |
APPCPE-16098 |
The copyright year on the Webgui's homepage is changed from 2023 to 2024. |
APPCPE-15519 |
NBA 5301MR2 [SWST]Hostname and username will be masked in the obfuscated data collect logs |
APPCPE-16227 |
NBA 5301MR2 [MFA] Print error info during administrator configure mfa failure. |
APPCPE-15967 |
During https proxy settings , the message of "Successfully set proxy username and Successfully set proxy password" will be seen only after adding username and password , |
APPCPE-15342 |
ASC data and logs are now consolidated in separate plugins. |
APPCPE-17708 |
After 5301MR2 upgrade , 2 kernels are seen under /boot for minor upgrade. |
APPCPE-16679 |
Update go testify version from 1.8.3 to 1.8.4 in 5.3.0.1MR2 as it 3 year older component |
APPCPE-16816 |
Associate UMI message with error msg- Could not find test backup images. Possible time difference between primary and media server |
APPCPE-16800 |
To add the trace event support during EEB installation and EEB uninstallation. |
APPCPE-17429 |
To investigate on the following error seen in patch_log: Could not set policy to the most recent applied policy |
APPCPE-17372 |
To add missing file imports in 5.3.0.1 MRs |
APPCPE-17225 |
Add NBA 5.3.0.1 MR2 support in AURA |
APPCPE-16217 |
To Address checksec errors and modify compiler flags if required |
APPCPE-16220 |
Remove insecure functions which may cause stack based buffer overflow |
APPCPE-16913 |
Add 100% upgrade event on cortex after minor upgrade |
APPCPE-17542 |
Old vuf states not cleaned properly, hence cleared those before VUF upgrade in MR. |
APPCPE-17656 |
Restart and enable irqbalance service after MR upgrade. |
APPCPE-16337 |
Retain NFS mount points after MR upgrade. |
APPCPE-16524 |
Not receiving multiple SNMP alerts (V-475-105-1003) for HBA ports which are not connected |
APPCPE-16287 |
Fixed When LDAP is configured able to change the passwords of admin and maintenance with previously used passwords against the STIG rule |
APPCPE-17545 |
Upgrade hangs for long time as Backing up the AD Users(258k Users) Took 5 Hours |
APPCPE-16565 |
HA upgrade fails to start incase of no dns configured |
APPCPE-17621 |
MQ Broker fails to start after upgrade from 5.0.0.1 to 5.3.x |
APPCPE-17619 |
Major Upgrade to 5.3XX fails at 18% then Rolls back due to ncsd service timeout |
Vulnerabilities Fixed in MR2
MR2 includes all vulnerabilities fixed in 5.3, 5.3 SP1, 5.3 SP2, 5.3.0.1 MR1, 5.3.0.1 MR1 SP1 and 5.3.0.1 MR1 SP2 the additional vulnerabilities listed below.
Security Risk |
Vulnerability id |
Critical |
CVE-2022-41912 |
High |
CVE-2023-28119, CVE-2017-3204, BDSA-2024-0402 (CVE-2024-22243), BDSA-2024-0647 (CVE-2024-22257), BDSA-2024-0396,[CVE-2023-28450],[CVE-2023-50387], [CVE-2023-50868],[CVE-2023-3138],[CVE-2022-48337],[CVE-2022-48339],[CVE-2021-43975],[CVE-2022-28388],[CVE-2022-3545],[CVE-2022-3594],[CVE-2022-36402], [CVE-2022-38096],[CVE-2022-38457], [CVE-2022-40133], [CVE-2022-41858],[CVE-2022-45869], [CVE-2022-45887],[CVE-2022-4744], [CVE-2023-1382], [CVE-2023-2166], [CVE-2023-2176], [CVE-2023-28772], [CVE-2023-30456], [CVE-2023-31084], [CVE-2023-33951],[CVE-2023-33952],[CVE-2023-40283],[CVE-2023-45862], [CVE-2023-4921],[CVE-2023-51042],[CVE-2023-51043],[CVE-2023-5633],[CVE-2023-6606],[CVE-2023-6610],[CVE-2023-6817],[CVE-2023-6931],[CVE-2023-6932],[CVE-2023-7192],[CVE-2024-0565],[CVE-2024-0646],[CVE-2024-1086],[CVE-2022-48337],[CVE-2022-48339],[CVE-2023-3138],[CVE-2023-4921],[CVE-2024-0646],[CVE-2023-28450], [CVE-2023-50387],[CVE-2023-50868],[CVE-2023-50387],[CVE-2023-50868] |
Medium |
BDSA-2024-0623(CVE-2024-24549), BDSA-2024-0622 (CVE-2024-23672), BDSA-2024-0367 BDSA-2024-0358, CVE-2023-35116 (BDSA-2023-1491), CVE-2024-25710 (BDSA-2024-0363), CVE-2023-45683 BDSA-2023-2813 ,[CVE-2019-14560],[CVE-2023-3446], [CVE-2023-45230], [CVE-2023-45234],[CVE-2021-43618],[CVE-2022-3094],[CVE-2022-3287],[CVE-2023-32324], [CVE-2023-34241] |
Applies to the following product releases
This update is obsolete and is superseded by
Update files
|
File name | Description | Version | Platform | Size |
---|