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
NetBackup database user
As part of the NetBackup 10.2 upgrade, the NetBackup database is converted to a new database. That database operates under a user account with limited privileges. For Linux, this account must be a non-root user. The account must be on each primary server (or each node of a clustered primary server).
Note:
For security purposes, do not create an account with administrator or superuser privileges. Do not add the user to the sudoer list.
You can use numerous procedures to create this user. Some specific approaches are shown, but other methods may accomplish the same goal. The user must have sufficient permissions to run daemons. More information about this topic is available.
See Upgrade requirements for UNIX and Linux.
Be aware of the operating system-specific account requirements:
A separate database user account is required for Linux only if the service account is root. If the service account is non-root, you do not need to create an additional user.
In Linux clustered environments, make sure that the local accounts are defined consistently on all cluster nodes. The UID must be the same for each local account. You can use LDAP accounts on UNIX.
For Windows clustered primary servers, you must use a domain account. You can use a domain account for non-clustered environments, but it is not required.
The NetBackup primary server installation fails if these requirements are not met. On Windows, you are asked to provide the password for the user account as part of the installation process.
Note:
If the password associated with the account expires after initial configuration, NetBackup provides no notification the password has expired. This behavior is normal and expected, as the operating system manages the account and the password.
As long as the NetBackup catalog remains active, NetBackup continues to operate normally.
When you attempt to restart NetBackup, the restart fails due to the expired password. Navigate to the appropriate area in the operating system, supply the correct password, and restart the service.
To create the database user account
- Create a local user.
Linux: useradd -c 'NetBackup database user account' username
Windows: C:\>net user username strong_password /add
- (Conditional) For Windows only, grant the Log on as a service right to the user:
Go to Control Panel > Administrative Tools > Local Security Policy.
Under Security Settings, click Local Policies > User Rights Assignment.
Right-click on Log on as a service and select Properties.
Add the local user.
Save your changes and close the Properties dialog for Log on as a service.