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
- How to deploy and configure a NetBackup Virtual Appliance combined primary and media server
- How to deploy and configure a NetBackup Virtual Appliance media server
- How to deploy and configure a NetBackup Virtual Appliance primary server
- How to deploy and configure a NetBackup Virtual Appliance combined primary and media server
- 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 authenticating Kerberos-NIS users
- 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.0
- 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
Installing a NetBackup Virtual Appliance software update using the NetBackup Virtual Appliance Shell Menu
Use the following procedure to start the appliance upgrade.
Note:
If you have enabled the STIG feature on an appliance and you need to upgrade it or install an EEB on it, do not plan such installations during the 4:00am - 4:30am time frame. By following this best practice, you can avoid interrupting the automatic update of the AIDE
database and any monitored files, which can cause multiple alert messages from the appliance.
To install a downloaded release update using the NetBackup Virtual Appliance Shell Menu
- Check to make sure that the following required updates and pre-upgrade tasks have already been performed:
All jobs have been stopped or suspended and all SLPs have been paused.
The Support > Test Software command has been run and it returned a Pass result.
- Log in to the NetBackup Virtual Appliance Shell Menu.
Note:
Veritas recommends that you log in using the shell menu from the virtual machine console, for example, the Virtual Machine Console in the vSphere Web Client, instead of an SSH session.
- Make sure that you have downloaded and have run the latest version of the Appliance Upgrade Readiness Analyzer tool. The analyzer tool must produce a
pass
result before you can continue to the next step. - To install the software release update, run the following command:
Main_Menu > Manage > Software > Install patch_name
Where patch_name is the name of the release update to install. Make sure that this patch name is the one that you want to install.
- Monitor the preflight check and watch for any failure and warning messages.
If no Check failed messages appear, you are prompted to continue to the next step to start the upgrade.
If any Check failed messages appear, the upgrade is not allowed. You must resolve the reported failures, then launch the upgrade script again so that the preflight check can verify that the failures have been resolved.
If any Check failed messages indicate that a RHEL version third-party plug-in was not found, you must obtain the plug-in from the appropriate vendor.
If any warning messages appear, Veritas recommends that you read the message and try to resolve the issue before you continue the upgrade. The warning message does not abort the upgrade process.
- Starting with release 5.0, a Call Home settings test will be performed. If Call Home is disabled, you will get a prompt option to enable Call Home. If Call Home is enabled, a Call Home test is performed. You can enable a proxy server if the test fails. The following warning message is displayed:
Warning:
The appliance is not able to connect to the Veritas Call Home server to upload hardware and software telemetry. Providing the Call Home information to Veritas allows for an improved support experience and recommendations through the NetInsights Console. It is recommended that you enable Call Home and ensure the system can reach the Veritas Call Home server through correct name resolution or proxy server setting.
You can ignore this warning and continue to the next step.
- After all preflight check items have passed, and before the upgrade begins, you must first select how the upgrade process should respond if any errors occur during the upgrade. The following prompt appears:
If an error occurs during the upgrade, do you want to
immediately enforce an automatic rollback? [yes, no]
Enter yes to immediately enforce an automatic rollback.
Enter no to pause the upgrade process and investigate the errors.
- After all preflight check items have passed, you may need to trust the CA certificate and the host ID-based certificate to start the upgrade process.
To trust and deploy the CA certificates, do the following:
Verify the CA certificate detail and enter yes to trust the CA certificate, as follows:
To continue with the upgrade, verify the following CA certificate detail and enter "yes" to trust the CA certificate. CA Certificate Details: Subject Name : /CN=nbatd/OU=root@abc.example.com/O=vx Start Date : Jul 14 12:59:18 2017 GMT Expiry Date : Jul 09 14:14:18 2037 GMT SHA1 Fingerprint : 31:E9:97:2E:50:11:51:7C:D6:25:7F:32:86:3D: 6B:D5:33:5C:11:E2 >> Do you want to trust the CA certificate? [yes, no](yes)
If the security level of the primary server is Very High, you must manually enter an authorization token to deploy the host ID-based certificate on the appliance, as follows:
>> Enter token:
If the security level of the primary server is High or Medium, the authentication token is not required. The host ID-based certificate is automatically deployed onto the appliance.
For more information about security certificates, refer to the chapter "Security certificates in NetBackup" in the NetBackup Security and Encryption Guide.
- Primary server upgrades from software versions 3.1.1 and earlier require you to provide a Veritas Usage Insights registration key. To obtain the registration key, follow the onscreen instructions.
- During the upgrade process, you can login using SSH and start the AIM window to check the upgrade status (except during the reboot process).
To check the upgrade status, you can:
Login using an SSH session and start the AIM window to monitor the upgrade process. Enter the following command:
Main_Menu > Manage > Software > UpgradeStatus.
Login using the IPMI console and start the AIM window. Enter the following command:
Main_Menu > Manage > Software > UpgradeStatus.
Monitor the upgrade process using the IPMI console. When all the updates have been installed successfully, a login prompt appears.
- If problems are detected during the post-upgrade self-test, the AIM window shows the upgrade status as Paused. Other SSH sessions and email notifications also indicate this status.
To clear the Paused status, perform the following tasks:
Press the V key to switch to the Verbose view to see the logs. If there are any Unique Message Identification (UMI) codes for the errors, search for them on the Veritas Support website to get more detailed information.
Try to fix the problem that the AIM window reports.
If you need to use the shell menu, log on to the NetBackup Virtual Appliance Shell Menu through an SSH session. When the AIM window appears, press the S key to close it.
Go back to the AIM window on the IPMI console.
If you tried fixing the problem, press the A key to attempt the self-test again. If you cannot fix the problem, contact Veritas Support or press the R key to roll back the appliance to the previous software version.
- After the upgrade has completed, the AIM window shows a summary of the upgrade results.
After the disk pools are back online, the appliance runs a self-diagnostic test. Refer to the following file for the test results:
/log/selftest_report_<appliance_serial>_<timedate>.txt
If SMTP is configured, an email notification that contains the self-test result is sent.