Veritas NetBackup™ Upgrade Guide
- Introduction
- About the NetBackup 8.1.2 Upgrade Guide
- About changes in NetBackup 8.1.2
- Veritas Smart Meter introduced
- Upgrades from NetBackup 7.6.0.4 and earlier are not supported
- HP-UX and AIX support change
- Newer Red Hat Linux compilers used with NetBackup 8.1.2
- VxUpdate replaces update_clients script in NetBackup 8.1.2
- Port 443 required for NetBackup web user interface
- About MSDP
- Performance issues with upgrades to NetBackup 8.1.2 from NetBackup 8.0 and earlier
- About certificate requirements for NetBackup 8.1
- SCCM and Chef deployment tools and documentation now available
- Potential required changes for NetApp clusters
- About automatic file changes from an upgrade
- Errors when Bare Metal Restore information is replicated using Auto Image Replication
- Known catalog backup limitation
- Available NetBackup upgrade methods
- About Veritas Services and Operations Readiness Tools
- Recommended SORT procedures for new installations
- Recommended SORT procedures for upgrades
- About the NetBackup preinstall checker
- Planning for an upgrade
- About planning a NetBackup 8.1.2 upgrade
- How to plan for an upgrade to NetBackup 8.1.2
- About Veritas Smart Meter
- Best practices for Veritas Smart Meter
- Creating the user account to support the NetBackup web server
- About NetBackup 8.1.2 support for Fibre Transport Media Server with RHEL 7.5
- MSDP changes in NetBackup 8.1
- About security certificates for NetBackup hosts
- Master server upgrade
- About master server upgrades
- Preinstall procedure for upgrading to NetBackup 8.1.2
- Performing local, remote, or clustered server upgrades on Windows systems
- Performing silent upgrades on Windows systems
- Upgrading UNIX/Linux server software to NetBackup 8.1.2
- Post-install procedure for upgrading to NetBackup 8.1.2
- About NetBackup startup and shutdown scripts
- Completing your system update after an upgrade
- Media server upgrade
- MSDP upgrade for NetBackup
- NetBackup Deployment Management with VxUpdate
- Appendix A. Reference
- NetBackup master server web server user and group creation
- Generate a certificate on the inactive nodes of a clustered master server
- About the NetBackup Java Runtime Environment
- About the NetBackup web user interface
- About the NetBackup answer file
- Update cloud configuration file on the master server immediately after install or upgrade to NetBackup 8.1.2
- About NetBackup software availability
- Additional post-upgrade steps for NetApp clusters
- Using NetApp disk arrays with Replication Director
- About compatibility between NetBackup versions
- Installation and upgrade requirements for UNIX and Linux
- Installation and upgrade requirements for Windows and Windows clusters
- Requirements for Windows cluster installations and upgrades
- Upgrading clients after servers are upgraded
- Install and upgrade of the UNIX and Linux client binaries with native installers
- Removing a clustered media server by migrating all data to a new media server
- Disabling the connection between your NetBackup OpsCenter server and your NetBackup Master Server
- Post upgrade procedures for Amazon cloud storage servers
Manually initiating upgrades from the master server using VxUpdate
You can manually initiate upgrades with VxUpdate using one of two methods. You can manually initiate an upgrade based on an existing policy. You can also initiate an upgrade without an associated policy.
Manually initiate deployment policies when you are logged into the master server locally and need to force an immediate update. Or you can initiate an immediate upgrade for emergency binaries. VxUpdate also provides the ability to launch upgrades from the client with the command line. More information is available.
See Manually initiating upgrades from the client using VxUpdate.
To manually initiate an upgrade of all clients in a policy from the administration console
- In the NetBackup Administration Console, navigate to Deployment Management > Deployment Policies.
- In the middle pane, expand the master server, and select the policy you want to run.
- Right-click on the policy you want to start, and select Manual Deployment.
- Alternatively, after selecting the policy you want to run, you can select Actions > Manual Deployment.
To manually initiate an upgrade of a specific client in a policy from the administration console
- Select NetBackup Management > Host Properties > Clients in the NetBackup Administrative Console.
- Right click on the client you want to upgrade in the right pane.
- Select Upgrade Host.
- In the Upgrade Host dialog:
Select the package you want to use from the Package drop-down.
Specify the type of schedule you want to run from the Type drop-down.
Select the media server you want to use from the Media server drop-down.
Confirm that the host you want upgraded is listed under Selected hosts.
- Select OK to launch the upgrade.
Note:
You can also launch an upgrade job from the Policies section of the NetBackup Administrative Console. Select NetBackup Management > Policies in the NetBackup Administrative Console. In the middle pane, select Clients. Then right-click on the client you want to upgrade in the right pane and select Upgrade Host. Then follow the procedure shown.
To manually initiate an upgrade from the command line for all clients in a policy
Use this procedure to manually start an upgrade for all clients in a policy.
Note:
This procedure starts the upgrade for all clients in the specified policy. You can start an upgrade on selected clients. More information is available.
To manually initiate an upgrade from the command line for selected clients in a policy
- Open a command prompt and navigate to the directory shown:
Windows: install_path\netbackup\bin
UNIX or Linux: /usr/openv/netbackup/bin
- Use the nbinstallcmd command as shown to launch a policy:
nbinstallcmd -i -policy policy_name -schedule schedule [-master_server master]
Where policy_name is the name of the deployment policy, schedule is the name of the schedule, and master is the name of the master server.
Be aware that use of the -i option prevents a scheduled start of same policy and schedule. This behavior prevents duplicate jobs.
To manually initiate an upgrade from the command line for selected clients in a policy
Use this procedure to manually start an upgrade for selected clients in a policy.
Note:
This procedure starts the upgrade on selected clients in the specified policy. You can start an upgrade for all clients in a policy. More information is available.
To manually initiate an upgrade from the command line for all clients in a policy
- Open a command prompt and navigate to the directory shown:
Windows: install_path\netbackup\bin
UNIX or Linux: /usr/openv/netbackup/bin
- Use the nbinstallcmd command as shown:
nbinstallcmd -policy policy_name -schedule schedule {-hosts filename|-host_filelist client1, client2, clientN}
Where:
policy_name is the name of the deployment policy
schedule is the name of the schedule
filename is the name of a file that contains a list of clients to upgrade.
client1, client2, clientN is a list of clients to upgrade.
To manually initiate an upgrade of a single client from the command line without an associated policy
Use this procedure to manually start an upgrade for a single client without an associated policy. Be aware that an attempt to list multiple clients fails and generates an error.
- Open a command prompt and navigate to the directory shown:
Windows: install_path\netbackup\bin
UNIX or Linux: /usr/openv/netbackup/bin
- Use the nbinstallcmd command as shown:
nbinstallcmd -operation_type operation -package package -media_server name -host_filelist client1
Where:
operation is the operation type you want started.
package is the name of the package you want used for the upgrade operation.
name is the name of the media server.
client1 is the name of the client you want upgraded.
Refer to the Veritas NetBackup Commands Reference Guide for additional details about the nbinstallcmd command and available options.