Veritas NetBackup™ Appliance Upgrade Guide
- Introduction
- Upgrade planning
- Pre-upgrade tasks
- Performing the upgrade
- Post upgrade tasks
- Troubleshooting
Pre-upgrade tasks for appliance upgrades
To prepare for an upgrade to version 3.1.2, the following tasks must be performed on each appliance that you plan to upgrade:
The preflight check verifies whether there are any active jobs. To help ensure a successful upgrade, perform the following:
Note:
For appliances (nodes) in a high availability (HA) setup, perform a switchover before you stop the jobs and run the software self-test. See Perform a switchover for appliances in an HA setup.
Log on to the NetBackup Administration Console as the administrator.
Before master server upgrades, pause all jobs and any SLPs (Storage Lifecycle Policies).
Before media server upgrades, stop all jobs that are currently running and suspend the jobs that may start during the upgrade. You must prevent jobs from attempting to start on the media server during an upgrade.
After all jobs have been stopped or suspended and all SLPs have been paused, run the following command from the NetBackup Appliance Shell Menu for a validation test:
Support > Test Software
The software self-test result must show Pass.
Note:
This command performs a backup and a restore test to the
/tmp
directory. If the/tmp
directory for the appliance you are upgrading is on the NetBackup exclude list, you must remove it from that list before you run the self-test command. Otherwise, the self-test fails.
Appliances (nodes) in an HA setup are updated one at a time. Both nodes must use the same appliance software version. Once you have upgraded one node, you must upgrade the other node immediately.
Either node can be upgraded first. However, upgrades cannot be performed on the node where MSDP services and jobs are in progress. Before you begin an upgrade on the node that is running MSDP, you must first perform a switchover to transfer the MSDP workload to the partner node. Use the following command to perform a switchover:
Main_Menu > Manage > HighAvailability > Switchover > hostname
Where hostname is the physical host name or IP address of the partner node.
When the upgrade on this node has completed, perform another switchover to transfer the MSDP workload from the partner node to the upgraded node. Immediately upgrade the partner node.
If IPSec functionality is configured on any appliance that you plan to upgrade, the IPsec certificates may not be retained after the upgrade has completed. To avoid this issue, you must export the IPsec certificates before upgrading those appliances. Use the Network > IPsec > Export command to perform this task.
The export command copies two .pfx
files (serialnumber.pfx
and .serialnumber.pfx
) to a location that you specify when you run the command.
Export the IPsec certificates before an upgrade as follows:
Log in to the NetBackup Appliance Shell Menu and navigate to the following view:
Network > IPsec
Enter the following export option details:
Export [EnterPasswd] [PathValue]
Where [EnterPasswd] is the field used to answer the question, "Do you want to enter a password?". You must enter yes or no.
Where [PathValue] is the location where you want to place the exported certificates.
After the export has completed, back up both of the
.pfx
files to a non-appliance location. After completing the upgrade, place the backed-up files from the non-appliance location to an appliance share such as/inst/patch/incoming
. Import the files from the share by using the procedure that follows.
After the upgrade has completed, re-import the IPsec certificates as follows:
Log in to the NetBackup Appliance Shell Menu and navigate to the following view:
Network > IPsec
Enter the following import option details:
Import [EnterPasswd] [PathValue]
Where [EnterPasswd] is the field used to answer the question, "Do you want to enter a password?". You must enter yes or no.
Where [PathValue] is the location where you want to place the imported certificates.
To make sure that there is enough space for the installation of the new version, all previously downloaded release updates, client packages, and client add-ons must be removed from the appliance before the upgrade.
If you do not delete the previously downloaded packages and the /inst
directory on the appliance does not contain enough space, the preflight check notifies you of the problem and prevents the upgrade. Even if enough space exists to allow the upgrade to start, the upgrade may fail if the old client add-ons are not removed.
Note:
As a best practice, always remove downloaded packages after all appliances and clients have been upgraded.
For downloaded packages on high availability (HA) nodes, you must remove the packages from both nodes.
The following table describes the package removal methods for appliances that never had version 2.6.0.1 installed.
Note:
If the appliance that you want to upgrade has ever had appliance version 2.6.0.1 installed, a different method is required for the client package removal. For details, refer to the information that appears below the table.
Table: Methods for deleting previously downloaded release updates, client packages, and client add-ons (for appliances that never had version 2.6.0.1 installed)
NetBackup Appliance Web Console | NetBackup Appliance Shell Menu |
---|---|
|
|
For appliances that once used version 2.6.0.1
If the appliance that you want to upgrade has ever had appliance version 2.6.0.1 installed, the client packages for that version remain on the appliance even if it has been upgraded to a later version. If the appliance was purchased with version 2.6.0.1 or if you ever upgraded to version 2.6.0.1, you must perform the following tasks to delete the 2.6.0.1 client packages. The only exception is if the appliance was re-imaged to a version different than 2.6.0.1.
To delete version 2.6.0.1 client packages from an appliance:
Open a web browser or an SSH session to the Veritas appliance software update release page.
Download and install any later version of the client packages onto the appliance.
Delete the newly installed client packages from the NetBackup Appliance Shell Menu. This action also deletes the 2.6.0.1 client packages.
Note:
The client packages cannot be deleted from the NetBackup Appliance Web Console.
Since all NetBackup appliances with version 2.6.1.2 and earlier use SLES version third-party plug-ins, upgrades to version 2.7.1 and later require that these plug-ins be replaced with the appropriate RHEL versions. If the preflight upgrade script identifies any required RHEL third-party plug-ins that are not found, the upgrade is not allowed to proceed.
Note:
The preflight upgrade script only identifies those plug-ins that are required for the upgrade. When version 2.7.1 was released, some third-party vendors had not yet completed development of their RHEL equivalent plug-ins. Make sure to check those vendor websites periodically for any additional plug-ins that you may need.
To install RHEL plug-ins, do the following:
Locate the appropriate RHEL plug-ins from the listed vendor websites:
http://www.datadomain.com/products
http://www.falconstor.com/en/pages/?pn=VTL
http://www.necam.com/HYDRAstor
https://www.veritas.com/product/backup-and-recovery/netbackup-appliances?themeid=nbu-appliance
If you have other third-party plug-ins that you use, those must also be replaced with the appropriate RHEL versions. See the appropriate vendor website for details.
Open the following share from the NetBackup Appliance Shell Menu:
Manage > OpenStorage > Share > Open
This command opens the
/inst/plugin/incoming
share for NFS and the\incoming_plugins
share for Windows. Copy the required plug-ins to these locations.Close the share as follows:
Manage > OpenStorage > Share > Close
Note:
For upgrades from 2.6.1 or 2.6.1.x, after the RHEL plug-in packages have been copied into the share and the share has been closed, do not run the Manage > OpenStorage > List Available command. The current 2.6.x SUSE appliance code flags the RHEL plug-in packages as invalid because the package naming conventions are different between SUSE and Red Hat environments. Since the appliance is still running on SLES, running the List Available command removes the RHEL plug-in packages from the share which prevents the upgrade.
Due to the company separation of Veritas from Symantec, some important server changes occurred that affect NetBackup appliance environments. These changes affect SORT, the NetBackup Product Improvement Program, appliance registration, and AutoSupport. Depending on your firewall settings and your proxy settings, you may need to make updates to maintain existing functionality. For specific information on these changes, refer to the following Tech Alert on the Veritas Support website:
https://www.veritas.com/support/en_US/article.INFO2803
The preflight check for the disk drive firmware version alerts you if it detects a version that is earlier than 0006 or A006. Veritas recommends that before you upgrade the appliance software, you should first update the disk drive firmware to version A006. This update addresses important disk drive performance issues.
The preflight check alerts you if it detects a disk drive firmware version that is earlier than 0006. If an earlier disk drive firmware version is detected, the preflight check blocks the upgrade. You must update the disk drive firmware to version 0006 or later before you can upgrade the appliance. This update addresses important disk drive performance issues.
The preflight check alerts you if it detects an older disk drive firmware version that can prevent the upgrade.
Caution:
The preflight check for version 3.1.2 upgrades provides the wrong disk drive firmware version of 0006. This version allows the upgrade to proceed, however the upgrade is likely to fail. Before you can upgrade to appliance release 3.1.2, you must first make sure that the disk drive firmware version on the appliance is A006.
Note:
An earlier disk drive firmware version does not prevent the software upgrade from proceeding. If you do not update the disk drive firmware before the appliance software upgrade, Veritas recommends that you do so immediately afterward.
For complete details about updating the disk drive firmware, refer to following article:
https://www.veritas.com/support/en_US/article.100033458.html