NetBackup IT Analytics System Administrator Guide
- Introduction
- Preparing for updates
- Backing up and restoring data
- Best practices for disaster recovery
- Oracle database backups
- File system backups
- Oracle database: Cold backup
- Oracle database: Export backups
- Scheduling the oracle database export
- Oracle database: On demand backup
- Restoring the NetBackup IT Analytics system
- Import the oracle database
- Manual steps for database import / export using data pump
- Monitoring NetBackup IT Analytics
- Accessing NetBackup IT Analytics reports with the REST API
- Defining NetBackup estimated tape capacity
- Automating host group management
- About automating host group management
- Task overview: managing host groups in bulk
- Preparing to use PL/SQL utilities
- General utilities
- Categorize host operating systems by platform and version
- Identifying a host group ID
- Move or copy clients
- Organize clients by attribute
- Move host group
- Delete host group
- Move hosts and remove host groups
- Organize clients into groups by backup server
- Merge duplicate backup clients
- Bulk load utilities
- Veritas NetBackup utilities
- Automate NetBackup utilities
- Organize clients into groups by management server
- Set up an inactive clients group
- Set up a host group for clients in inactive policies
- Set up clients by policy
- Set up clients by policy type
- IBM Tivoli storage manager utilities
- Set up clients by policy domain
- Set up clients by IBM Tivoli storage manager instance
- Scheduling utilities to run automatically
- Attribute management
- Attribute bulk load utilities
- Attribute naming rules
- Rename attributes before upgrading
- Load host attributes and values
- Load attributes and values and assign to hosts
- Load array attributes and values and assign to arrays
- Overview of application attributes and values
- Load application database attributes and values
- Load MS Exchange organization attributes and values
- Load LUN attributes and values
- Load switch attributes and values
- Load port attributes and values
- Importing generic backup data
- Backup job overrides
- Managing host data collection
- System configuration in the portal
- System configuration in the portal
- System configuration: functions
- Navigation overview
- System configuration parameter descriptions: Additional info
- Anomaly detection
- Data collection: Capacity chargeback
- Database administration: database
- Host discovery: EMC Avamar
- Host discovery: Host
- Events captured for audit
- Custom parameters
- Adding/editing a custom parameter
- Portal customizations
- Configuring global default inventory object selection
- Restricting user IDs to single sessions
- Customizing date format in the report scope selector
- Customizing the maximum number of lines for exported reports
- Customizing the total label display in tabular reports
- Customizing the host management page size
- Customizing the path and directory for File Analytics database
- Configuring badge expiration
- Configuring the maximum cache size in memory
- Configuring the cache time for reports
- Performance profile schedule customization
- Configuring AD/LDAP
- Configuring single sign-on (SSO) using security assertion markup language (SAML)
- Change Oracle database user passwords
- Integrate with CyberArk
- Tuning NetBackup IT Analytics
- Working with log files
- About debugging NetBackup IT Analytics
- Turn on debugging
- Database logging
- Portal and data collector log files - reduce logging
- Database SCON logging - reduce logging
- Refreshing the database SCON log
- Logging user activity in audit.log
- Logging only what a user deletes
- Logging all user activity
- Data collector log files
- Data collector log file organization
- Data collector log file naming conventions
- General data collector log files
- Find the event / meta collector ID
- Portal log files
- Database log files
- Installation / Upgrade log files
- Defining report metrics
- SNMP trap alerting
- SSL certificate configuration
- SSL certificate configuration
- SSL implementation overview
- Obtain an SSL certificate
- Update the web server configuration to enable SSL
- Configure virtual hosts for portal and / or data collection SSL
- Enable / Disable SSL for a Data Collector
- Enable / Disable SSL for emailed reports
- Test and troubleshoot SSL configurations
- Create a self-signed SSL certificate
- Configure the Data Collector to trust the certificate
- Keystore file locations on the Data Collector server
- Import a certificate into the Data Collector Java keystore
- Keystore on the portal server
- Add a virtual interface to a Linux server
- Add a virtual / secondary IP address on Windows
- Portal properties: Format and portal customizations
- Introduction
- Configuring global default inventory object selection
- Restricting user IDs to single sessions
- Customizing date format in the report scope selector
- Customizing the maximum number of lines for exported reports
- Customizing the total label display in tabular reports
- Customizing the host management page size
- Customizing the path and directory for file analytics database
- Configuring badge expiration
- Configuring the maximum cache size in memory
- Configuring the cache time for reports
- Configuring LDAP to use active directory (AD) for user group privileges
- Data retention periods for SDK database objects
- Data retention periods for SDK database objects
- Find the domain ID and database table names
- Retention period update for SDK user-defined objects example
- SDK user-defined database objects
- Capacity: default retention for basic database tables
- Capacity: default retention for EMC Symmetrix enhanced performance
- Capacity: Default retention for EMC XtremIO
- Capacity: Default retention for Dell EMC Elastic Cloud Storage (ECS)
- Capacity: Default retention for Windows file server
- Capacity: Default retention for Pure Storage FlashArray
- Cloud: Default retention for Amazon Web Services (AWS)
- Cloud: Default retention for Microsoft Azure
- Cloud: Default retention for OpenStack Ceilometer
- Configure multi-tenancy data purging retention periods
- Troubleshooting
- Appendix A. Configure TLS-enabled Oracle database on NetBackup IT Analytics Portal and data receiver
- About Transport Layer Security (TLS)
- TLS in Oracle environment
- Configure TLS in Oracle with NetBackup IT Analytics on Linux in split architecture
- Configure TLS in Oracle with NetBackup IT Analytics on Linux in non-split architecture
- Configure TLS in Oracle with NetBackup IT Analytics on Windows in split architecture
- Configure TLS in Oracle with NetBackup IT Analytics on Windows in non-split architecture
- Configure TLS in user environment
Load application database attributes and values
Function: The Load Application Database Attributes utility provides an efficient method of assigning attributes to a large number of application databases.
Take the following steps to load application database attributes and values:
Create a CSV File of Application Database Objects and Attributes.
Execute the Load Application Database Attribute Utility.
Verify the Application Database Attributes Load.
Create a report template using the SQL Template Designer.
Once attribute values are assigned to application databases, a SQL Template Designer report can query the database to report on the application databases.
The LoadDBAttribute utility assigns application attribute values to a host's database application. This utility takes as input a comma-separated values (CSV) file.
Note:
This CSV file becomes the primary document of record for Application Database Attributes and therefore should be preserved in a working directory for future updates.
Create a spreadsheet table, in the format shown in the following example, and save it as a CSV file in a working directory. This file is specific to application databases.
In the above example:
The first 3 columns comprise the unique identifier for an Application Database--in this example, CorpServer1, FinanceDB, and FinanceDBInstance.
Subsequent columns list the attributes and values.
Columns list the objects that uniquely identify an application. For an Application Database, the required columns are: Host Name, DB Name, DB Instance.
Each additional column lists attributes and values.
First (Header) Row - Contains the fields that uniquely identify an application, followed by the attribute names. The header row is information only and is not processed as a data row.
Subsequent rows list the objects that uniquely identify an application database, followed by the attribute values that you are assigning to each application database.
Bulk Load utilities must be run in SQLPLUS as user APTARE. The load_package utility is located in:
/opt/aptare/database/stored_procedures (Linux) \opt\oracle\database\stored_procedures (Windows)
To assign attributes to application databases
- Create a table in a spreadsheet.
- Save the table as a comma-separated file (for example, DBAttributes.csv).
- 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
Execute the following at the SQL prompt:
SQL> Execute load_package.loadDBAttributeFile ('pathname_and_filename','domain_name', db_name_column_num,db_instance_column_num,host_name_column_num, 'log_path_name','log_file_name','check_valid_value');
Where:
'pathname_and_filename'
Full path + filename (enclosed in single straight quotes) of the CSV file
Windows Example: 'c:\config\DBAttributes.csv'
Linux Example: '/config/DBAttributes.csv'
'domain_name'
Name (enclosed in single straight quotes) of the domain in which the host groups and hosts reside; Example: 'DomainEMEA'
db_name_column_num
Column number in the csv file where the DB Name is listed; Example: 2
db_instance_column_num
Column number in the csv file where the DB Instance is listed; Example: 3
host_name_column_num
Column number in the csv file where the Host Name is listed; Example: 1
'log_path_name'
Full path (enclosed in single straight quotes) where the log file will be created/updated; verify that you have write access to this directory.
Optional: If a log path and filename are not specified, log records are written to scon.log and scon.err. To omit this parameter, enter: ''
Example: 'c:\configs'
'log_file_name'
Log file name enclosed in single straight quotes.
Optional: If a log path and filename are not specified, entries are written to scon.log and scon.err. To omit this parameter, enter: ''
Example: 'DBAttributes.log'
'check_valid_value'
'Y' or 'N' enclosed in single straight quotes.
Y - Checks if the attribute value exists. If the utility determines that the attribute value is not valid, it skips this row and does not assign the attribute value to the application database.
N - Updates without checking that the attribute value exists. This option is seldom chosen, but it is available for certain customer environments where attributes may have been created without values (with scripts that bypass the user interface).
Example:
SQL> Execute load_package.loadDBAttributeFile('/config/DBAttributes.csv', 'DomainEMEA', 2, 3, 1,'/config/logs','DBAttributes.log','Y'); - Check the log file for status and errors.
- Restart the Portal services so that the newly added attributes become available in the Dynamic Template Designer.
To verify that the attribute load took effect:
In the Portal, go to .
Select a blue user folder.
Select .
With the SQL Template Designer open, click the tab.
Enter the following query in the SQL Template Designer to verify Application Database attributes:
select * from aps_v_database_attribute