APTARE IT Analytics System Administrator Guide
- Preparing for updates
- Backing up and restoring data
- Monitoring APTARE IT Analytics
- Accessing APTARE 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
- Automating NetBackup utilities
- Attribute management
- Importing generic backup data
- Backup job overrides
- Managing host data collection
- System configuration in the portal
- Host discovery: EMC Avamar
- Performance profile schedule customization
- Configuring AD/LDAP
- Configuring single sign-on (SSO) using security assertion markup language (SAML)
- Changing Oracle database user passwords
- Integrating with CyberArk
- Tuning APTARE 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
- Advanced configuration for NetBackup discovery
- Data retention periods for SDK database objects
- Configure multi-tenancy data purging retention periods
- Troubleshooting
Oracle database: On demand backup
This method is useful for cases where an immediate backup/export is required; for example, when Customer Support requests a copy of your database for troubleshooting.
To back up the database tables, APTARE IT Analytics provides an Oracle data pump utility, exdp. This utility exports the user portal, which contains the database tables. To create a full export file of all database objects, refer to the following section.
See Oracle database: Export backups.
For optimum performance, use this utility rather than your favorite backup solution's backup utility (for example, rman) because most backup solutions require archive logging. This setting is not enabled or exposed because archive logging can have a significant, negative impact on performance.
You will import this export in the event that you need to:
Restore the entire Reporting Database.
Retrieve a data table that's been corrupted or accidentally deleted. Simply drop the portal user then import the export.