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
- 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
- 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
- Troubleshooting
- Appendix A. Configure TLS-enabled Oracle database on NetBackup IT Analytics Portal and data receiver
Import the oracle database
IMPORTANT: The following process deletes your existing NetBackup IT Analytics database. Before you try to import the Oracle Database, verify you have no other recovery options and you have a valid database export. Contact Veritas Support.
Some common problems include:
Importing unsuccessful backups. Ensure that your backups were successful before you accidentally import old data.
Importing more than what you need. Do not restore the entire database or import all database tables if you only need to restore one database table. Import only what you need.
IMPORTANT: Before restoring user objects, stop the Tomcat and Portal processes.
See Starting and stopping portal server software.
To import the latest successful export of the Oracle database, the database user Aptare user must have access to the export files stored in the directory:
/opt/aptare/database/tools
Verify the Oracle user has read and execute privileges on these files before starting the database export.
Log into the Linux database server and switch to user Aptare.
Place the export file
aptare_scdb.exp
in the/tmp
directory.If you have a different preferred directory (for example,
/new_directory_path
), then placeaptare_scdb.exp
in your preferred directory (/new_directory_path
). Subsequently, change the path for the creation of directory from/tmp
to the new directory (new_directory_path
) in the/opt/aptare/database/tools/drop_users_linux.sql
file.Note:
You can also use
/opt/aptare/
or/opt/aptare/oracle/rdbms/log/
directories.Stop all Oracle and APTARE services by running from the root user:
/opt/aptare/bin/aptare stop
Start Oracle services by running from the root user:
/opt/aptare/bin/oracle start
Verify the Oracle Listener is running (/opt/aptare/bin/aptare status)
Run the following command:
chmod +x /opt/aptare/database/tools/import_database_template.sh
Run the script import_database_template.sh using the user Aptare by executing the command:
/opt/aptare/database/tools/import_database_template.sh
After successful completion, the data pump export file aptare_scdb.exp is saved on the Linux database server in the /tmp directory.
The import_database_template.sh script, unlocks Portal user, grants privileges, and validates the packages after the completion of the import, so they are not required to be run manually. The scripts also address the compilation warnings for the packages that follow.
The import log, import_scdb.log, is located in the /tmp directory.
Check the log file for compilation warnings for the packages:
view apt_v_solution_history_log
cmv_adaptor_pkg
avm_common_pkg
sdk_common_pkg
load_package
common_package
util
These compilation warnings are addressed by the script itself and no action is required from the user.
Note:
If you are importing a database from version 10.4, upgrade the portal after the import to a 10.5 build.
This step is required only if you are exporting the database from NetBackup IT Analytics version 10.5 or above. Execute the following commands to copy the file aptare.ks to datarcvrconf folder.
cp /tmp/aptare.ks /opt/aptare/datarcvrconf/ chown aptare:tomcat /opt/aptare/datarcvrconf/ chmod 664 /opt/aptare/datarcvrconf/aptare.ks
Run updateUser.sh to change the password of the application account. For example, to change the password for the admin123 application user, run: updateUser.sh admin123 <newPassword>
Restart all Oracle and APTARE services by running them from the root user:
/opt/aptare/bin/aptare restart
Log into the portal Application using the application account.
To import the latest successful export of the Oracle database, the database user Aptare user must have access to the export files stored in the directory:
c:\opt\oracle\database\tools
Verify the Oracle user has read and execute privileges on these files before starting the database export.
Log into the Windows database server as a user who is a member of the ORA_DBA group.
Place the export file aptare_scdb.exp in the directory:
C:\opt\oracle\logs
Stop all Oracle and Aptare services using stopAllServices from the Windows Services tab.
Verify the Oracle TNS Listener is running and start OracleServicescdb from the Windows Services tab.
From the command prompt, run the script import_database_template.bat by executing the command:
c:\opt\oracle\database\tools\import_database_template.bat
After successful completion of the import, run Startallservices from the Windows Services tab.
The import_database_template.bat script, unlocks Portal user, grants privileges, and validates the packages after the completion of import, so they are not required to be run manually. The scripts also address compilation warnings for the packages that follow.
The import log, import_scdb.log, is located C:\opt\aptare\oracle\logs.
Check the log file for compilation warnings for the packages:
view apt_v_solution_history_log
cmv_adaptor_pkg
avm_common_pkg
sdk_common_pkg
load_package
common_package
util
These compilation warnings are addressed by the script itself and no action is required from the user.
Note:
If you are importing a database from version 10.4, upgrade the portal after the import to a 10.5 build.
Copy the saved file c:\opt\oracle\logs\aptare.ks to c:\opt\datarcvrconf\ folder. Ensure that the file is owned by NetBackup IT Analytics user and has appropriate Read and Write access to the copied file.
Note:
This step is required only if database is exported from an NetBackup IT Analytics version of 10.5 or above.
Run startAllServices using the Windows Services tab.
Run stopAllServices using the Windows Services tab.
Run updateuser.bat to change the password of the application account. For example, to change the password for the admin123 application user, run: updateuser.bat admin123 newPassword
Log into the portal Application using the application account.
If you do not have a successful cold backup of your Oracle database, take the following steps to recover your NetBackup IT Analytics Oracle database. Refer to the Installation and Upgrade Guides for complete details about re-installing the binaries and the database schema. Contact Support for assistance.
Re-install the Oracle binaries.
Re-install the database schema.
Import the latest successful export of your Oracle database to restore the Portal user objects.