NetBackup™ Upgrade Guide
- Introduction
- About the NetBackup 10.3 Upgrade Guide
- Available NetBackup upgrade methods
- About changes in NetBackup 10.3
- License file required for upgrade
- Windows primary server upgrades are slowed if a large number of files are in the installation directory
- About NetBackup database changes
- Windows compiler and security requirements for NetBackup 9.1 and later installation and upgrade
- Java GUI and JRE installation optional for some computers
- Logging directory permissions require reset on rollback
- Upgrades from NetBackup 7.6.0.4 and earlier are not supported
- External certificate authority certificates supported in NetBackup 8.2 and later
- About Veritas Usage Insights
- Best practices for Veritas Usage Insights
- Planning for an upgrade
- General upgrade planning information
- About planning a NetBackup 10.3 upgrade
- How to plan for an upgrade to NetBackup 10.3
- Legacy logging directory security update
- Unified logging security update
- Notifications, Messages, and Resiliency configuration information are not upgraded
- Known catalog backup limitation
- About security certificates for NetBackup hosts
- About automatic file changes from an upgrade
- Reduce the job database size before upgrade
- Known SUSE Linux primary server upgrade issue
- Performance and tuning considerations
- About upgrade tools
- Upgrade operational notes and limitations
- Creating the user account to support the NetBackup web server
- About NetBackup 10.3 support for Fibre Transport Media Server with RHEL 7.5 and later
- MSDP changes in NetBackup 8.1
- Potential required changes for NetApp clusters
- Errors when Bare Metal Restore information is replicated using Auto Image Replication
- Upgrade issue with pre-8.1 clients and 8.1 or later media servers
- General upgrade planning information
- Primary server upgrade
- About primary server upgrades
- Preinstall procedure for upgrading to NetBackup 10.3
- Performing local, remote, or clustered server upgrades on Windows systems
- Performing silent upgrades on Windows systems
- Upgrading Linux server software to NetBackup 10.3
- Silently upgrading NetBackup primary server software on Linux
- Post-install procedure for upgrading to NetBackup 10.3
- About NetBackup startup and shutdown scripts
- Completing your system update after an upgrade
- Media server upgrade
- MSDP upgrade for NetBackup
- Client upgrade
- NetBackup Deployment Management with VxUpdate
- Appendix A. Reference
- NetBackup primary server web server user and group creation
- NetBackup database user
- Generate a certificate on the inactive nodes of a clustered primary server
- About the NetBackup Java Runtime Environment
- Add or Remove Java GUI and JRE after upgrade
- About the NetBackup web user interface
- About the NetBackup answer file
- Manually install or uninstall NetBackup IT Analytics Data Collector binaries
- Configure the NetBackup IT Analytics Data Collector manually for NetBackup
- Manually upgrading the NetBackup IT Analytics Data Collector
- Persistent Java Virtual Machine options
- About RBAC bootstrapping
- About NetBackup software availability
- Additional post-upgrade steps for NetApp clusters
- Using NetApp disk arrays with Replication Director
- About compatibility between NetBackup versions
- Upgrade requirements for UNIX and Linux
- Upgrade requirements for Windows and Windows clusters
- Requirements for Windows cluster upgrades
- Removing a clustered media server by migrating all data to a new media server
- Post upgrade procedures for Amazon cloud storage servers
- Upgrading clients after servers are upgraded
- Upgrade failure rollback steps
- Size guidance for the NetBackup primary server and domain
About RBAC bootstrapping
RBAC Bootstrapping lets you assign role-based access control (RBAC) permissions to a user or a user group during NetBackup installation or upgrade on Linux platforms. The Linux installer uses the bpnbaz -AddRBACPrincipal command to grant the Administrator role permissions to the user or the user group that you specify in the /tmp/NBInstallAnswer.conf file.
Note:
RBAC bootstrapping provides access to all objects for the specified user or user group, even if previously the user or the user group had restricted access to certain objects. For example, the existing user Tester1 was assigned the Default VMware Administrator role. If Tester 1 is specified for RBAC bootstrapping, Tester1 is assigned the Administrator role.
After installation or upgrade, you can run the bpnbaz -AddRBACPrincipal command standalone on both Windows and Linux platforms to assign RBAC permissions. The command is available only on the primary server. For more information about this command, see the NetBackup Commands Reference Guide.
Use the answer file template NBInstallAnswer-primary.template available in the install package to create the /tmp/NBInstallAnswer.conf file. In that file, add the following entries before you run the installation or upgrade:
RBAC_DOMAIN_TYPE = domain_type
RBAC_DOMAIN_NAME = domain_name
RBAC_PRINCIPAL_TYPE = USER | USERGROUP
RBAC_PRINCIPAL_NAME = principal_name
Be aware that RBAC_DOMAIN_TYPE supports the values shown: NT, VX, UNIXPWD, LDAP.
Note:
Additional information about the RBAC_* options is available.
RBAC bootstrapping is not performed if all the entries are empty or missing. In this case, the message Answer file did not contain any RBAC entries is posted in the install trace file. The install process always continues whether the RBAC bootstrapping is successful or not. The audit records are created under the SEC_CONFIG category.
If RBAC bootstrapping is successful, the installer displays the following message:
Successfully configured the RBAC permissions for principal_name.
The installer also displays this message if the user or the user group already exists with the Administrator RBAC role.
If one or more RBAC entries exist in the answer file, but a required answer file entry is missing, the installer displays the following message:
Warning: Unable to configure the RBAC permissions. One or more required fields are missing in /tmp/NBInstallAnswer.conf.
If there are other issues with the RBAC Bootstrapping, the installer displays the following message:
Warning: Failed to configure the RBAC permissions for principal_name. Refer to logs in /usr/openv/netbackup/logs/admin for more information.
If RBAC bootstrapping is successful but auditing fails, the install displays the following message:
Successfully configured the RBAC permissions for user_or_usergroup_name. WARNING: Auditing of this operation failed. Refer to logs in /usr/openv/netbackup/logs/admin for more information.
After the installation or upgrade completes, the specified user or user group is assigned the Administrator role with its corresponding RBAC access permissions. The user can then access APIs and the Web UI.