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
 
Automate NetBackup utilities
The Veritas NetBackup utilities listed in this section can be set up to run automatically. A stored procedure can be edited to customize the list of utilities to be run as a background job on a particular schedule.
Windows: C:\opt\oracle\database\stored_procedures\nbu\setup_nbu_jobs_manual.sql
Linux: opt/aptare/database/stored_procedures/nbu/setup_nbu_jobs_manual.sql
All five are included in this file. To omit a particular utility from the scheduled job, use the following syntax before and after the block of code.
See Veritas NetBackup utilities.
- Before the block of code to be omitted, use: /* 
- After the block of code to be omitted, use: */ 
In a text editor, open the setup_nbu_jobs_manual.sql file and modify the schedule to meet your needs. The following example illustrates how to edit syntax to customize the schedule.
----------------------------------------------------------------------------------------
    -- Move clients that are in inactive policies
    -- Frequency: Every day at 02:30
    ----------------------------------------------------------------------------------------
    jobName := dba_package.getSchedulerJobName('setupInactivePolicyClients');
   
    IF (jobName IS NOT NULL AND LOWER(jobName) <> LOWER('setupInactivePolicyClients')) THEN
        DBMS_OUTPUT.PUT_LINE('setupInactivePolicyClients exists with default name '|| jobName ||
' hence will be removed and recreated.');
        DBMS_SCHEDULER.DROP_JOB(job_name => jobName);
        jobName := NULL;
    END IF;
    
    IF jobName IS NULL THEN    
        DBMS_SCHEDULER.CREATE_JOB(
            job_name         => 'setupInactivePolicyClients', 
            job_type         => 'PLSQL_BLOCK',
            job_action       => 'server_mgmt_pkg.setupInactivePolicyClients(NULL, NULL, 0, 0);',  -- What to run
            start_date       => SYSDATE + (5/48),           -- First run is 150 mins from initial installation
            repeat_interval  => 'TRUNC(SYSDATE+1,''DD'') + (5/48)',  -- Next run is 2:30 each subsequent day
            enabled          => TRUE); 
    ELSE
       DBMS_OUTPUT.PUT_LINE('setupInactivePolicyClients exists and will be altered with updated version.');
       DBMS_SCHEDULER.SET_ATTRIBUTE(
            name         => jobName,
            attribute    => 'job_type',
            value        => 'PLSQL_BLOCK'
            );
       DBMS_SCHEDULER.SET_ATTRIBUTE(
            name         => jobName,
            attribute    => 'job_action',
            value        =>  'server_mgmt_pkg.setupInactivePolicyClients(NULL, NULL, 0, 0);'
            );  
       DBMS_SCHEDULER.SET_ATTRIBUTE(
            name         => jobName,
            attribute    => 'repeat_interval',
            value        => 'TRUNC(SYSDATE+1,''DD'') + (5/48)'
            );     
    END IF;                       
    DBMS_OUTPUT.put_line('setupInactivePolicyClients set to run at 2:30 every day');