NetBackup IT Analytics System Administrator Guide
- Introduction
- Preparing for updates
- Backing up and restoring data
- Monitoring NetBackup IT Analytics
- Accessing NetBackup IT Analytics reports with the REST API
- Defining NetBackup estimated tape capacity
- Automating host group management
- Categorize host operating systems by platform and version
- Bulk load utilities
- Automate NetBackup utilities
- Scheduling utilities to run automatically
- Attribute management
- Importing generic backup data
- Backup job overrides
- Managing host data collection
- System configuration in the Portal
- Custom parameters
- Performance profile schedule customization
- LDAP and SSO authentication for Portal access
- Change Oracle database user passwords
- Integrate with CyberArk
- Tuning NetBackup IT Analytics
- Working with log files
- Portal and data collector log files - reduce logging
- Data collector log file naming conventions
- Portal log files
- Defining report metrics
- SNMP trap alerting
- SSL certificate configuration
- Configure virtual hosts for portal and / or data collection SSL
- Keystore on the portal server
- Portal properties: Format and portal customizations
- Data retention periods for SDK database objects
- Data aggregation
- Troubleshooting
- Appendix A. Kerberos based proxy user's authentication in Oracle
- Appendix B. Configure TLS-enabled Oracle database on NetBackup IT Analytics Portal and data receiver
- Appendix C. NetBackup IT Analytics for NetBackup on Kubernetes and appliances
Rename attributes before upgrading
Beginning with Release Version 10, all attributes are multi-object attributes--that is, a single attribute is defined and that attribute, with its values, can be used for multiple object types. For example, prior to Release Version 10, you could have a Location attribute for a host and a separate Location attribute for an array. During the upgrade, a system attribute named Location is added to the database and this single attribute can be used for multiple object types--in this example, it would be used for both hosts and arrays.
During the Portal upgrade, if the names of existing attributes match the name of a system attribute introduced with the upgrade, you may want to rename existing attributes so that their values do not get merged into a single attribute. Renaming of attributes, before the upgrade is completed, must be performed using SQL at the command line.
Note:
After you rename an attribute, any report templates that used these attributes must be updated via the Portal SQL Template Designer.
To rename existing attributes so that their values do not get merged into a single attribute, take the following steps.
Log in to the Portal server.
At the command line:
su - aptare
At the command line, launch sqlplus:
sqlplus <pwd>/<pwd>@//localhost:1521/scdb>
Example: sqlplus portal/portal@//localhost:1521/scdb
At the command line, execute the following at the
prompt:UPDATE apt_attribute SET attribute_name - '<NewAttributeName>' WHERE attribute_id = <ExistingAttributeID>; Commit;
Where <NewAttributeName> is the new name you supply and <ExistingAttributeID> is the ID listed during the Portal upgrade process.