Veritas NetBackup™ Virtual Appliance Documentation
- Getting to know the NetBackup Virtual Appliance
- NetBackup Virtual Appliance product description
- Preparing to deploy the appliance
- Deploying and configuring the appliance
- Post initial configuration procedures
- Appliance common tasks
- Storage management
- About NetBackup Virtual Appliance storage configuration
- About viewing storage space information using the Show command
- About OpenStorage plugin installation
- About NetBackup Virtual Appliance storage configuration
- Deduplication pool catalog backup and recovery
- Network connection management
- Managing users
- About user name and password specifications
- About authenticating LDAP users
- About authenticating Active Directory users
- About authentication using smart cards and digital certificates
- About user authorization on the NetBackup Virtual Appliance
- Creating NetBackup administrator user accounts
- Using the appliance
- About configuring Host parameters for your appliance on the NetBackup Virtual Appliance
- About Copilot functionality and Share management
- About NetBackup Virtual Appliance as a VMware backup host
- About running NetBackup commands from the appliance
- About mounting a remote NFS
- About Auto Image Replication from a NetBackup Virtual Appliance
- Monitoring the appliance
- About SNMP
- About Call Home
- Appliance security
- About Symantec Data Center Security on the NetBackup Virtual Appliance
- About data encryption
- Setting the appliance login banner
- Upgrading the appliance
- About upgrading to NetBackup Virtual Appliance software version 5.1.1
- Requirements and best practices for upgrading NetBackup appliances
- Methods for downloading appliance software release updates
- NetBackup client upgrades with VxUpdate
- Appliance restore
- Decommissioning and Reconfiguring
- Troubleshooting
- About disaster recovery
- About NetBackup support utilities
- Appliance logging
- About forwarding logs to an external server
- Commands overview
- Appendix A. Appliance commands
- Appendix B. Manage commands
- Appendix C. Monitor commands
- Appendix D. Network commands
- Appendix E. Reports commands
- Appendix F. Settings commands
- Appendix G. Support commands
- Appendix H. Available commands for a NetBackupCLI user
Requirements and best practices for upgrading NetBackup appliances
This topic describes the requirements and best practices that you should follow anytime you plan to upgrade appliance software.
You can perform upgrades from the Appliance Management Console. After you review all upgrade guidelines and perform the required pre-upgrade tasks, refer to the Veritas Appliance Management Guide for the upgrade procedure.
Note:
The Appliance Management Console does not currently support upgrading appliances (nodes) in an HA setup. You must use the NetBackup Virtual Appliance Shell Menu to upgrade these appliances.
Always perform upgrades with the admin user account. Do not use a non-admin user account to upgrade appliances.
Always perform a full disaster recovery (DR) backup before an upgrade.
Primary servers
Make sure that you have a recent and complete NetBackup Catalog backup.
Make sure to configure your deduplication pool catalog backup policy and perform a successful backup. For details, refer to the following article:
Use the Network > Security > 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.Log in to the NetBackup Virtual Appliance Shell Menu and navigate to the following view:
Network > Security > Export
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.
Delete previously downloaded release updates, client packages, and client add-ons.
To make sure that there is enough space in the
/inst
partition during the upgrade, first delete all previously downloaded release updates, client packages, and client add-ons from the appliance. As a best practice, always remove downloaded packages after all appliances and clients have been upgraded.If you do not delete the previously downloaded packages and the
/inst
directory on the appliance does not contain enough space, the preflight check and the Appliance Upgrade Readiness Analyzer tool prevent 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. For downloaded packages on high availability (HA) nodes, you must remove the packages from both nodes.The following describes the package removal methods:
On the appliance to be upgraded, check for all downloaded release updates and client packages by entering the following command:Manage > Software > List Downloaded.
To remove each downloaded release update and client package, enter the following command:Manage > Software > Deleteupdate_name. Where
update_name
is the release update or the client package file name.To see a list of all downloaded client add-ons, enter the following command:Manage > Software > List AddOns.
To remove each downloaded client add-on, enter the following command:Manage > Software > Rollbackeeb_name. Where
eeb_name
is the client add-on file name.Note:
You must include the
.rpm
extension when you enter the client add-on file name.
Follow the same upgrade order for appliances as for traditional NetBackup upgrades. If you use NetBackup OpsCenter, upgrade it first. Then upgrade appliances starting with the primary server appliance, followed by all media server appliances.
If you have multiple media servers to upgrade, you must perform the upgrade process on each individual media server.
Appliance media servers (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.
If a traditional NetBackup primary server is used with an appliance media server, that primary server must have the same NetBackup version or later as the media server appliance. For example, before you upgrade a media server appliance to version 5.1.1, first upgrade the NetBackup primary server to version 10.1.1.
Make sure that the NetBackup primary server is active and running throughout the duration of an appliance media server upgrade. In addition, make sure that the NetBackup processes are started or running on both the primary server and the media server.
NetBackup clients must use the same or an earlier software version as the appliance. Clients cannot run at a later version than the appliance. For example, a client with NetBackup version 10.1.1 can only be used with an appliance server with version 5.1.1 or later. Client add-ons must also be the same as the client version.
Upgrades to version 3.2 and later using the NetBackup Virtual Appliance Shell Menu or the Appliance Management Console (AMS) do not support ECA deployment during the upgrade. 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
, andnginx
. For details, see the NetBackup Appliance Security Guide.Use a compatible version of the NetBackup Administration Console to manage the NetBackup services.
The NetBackup Administration Console is backward-compatible. A patch release (x.x.x.x) console is compatible with a major (x.x) or minor NetBackup release (x.x.x) that shares the same first and second digits.