This guide contains detailed information about One Identity Manager 9.1 data archiving administration
This One Identity Manager 9.1 Data Archiving Administration Guide explains how change information logged in the One Identity Manager database is regularly removed and archived in a One Identity Manager History Database. It describes the steps for setting up a History Database: installing it with the Configuration Wizard (or the Quantum.MigratorCmd.exe command line program), declaring it in the One Identity Manager database, and setting up the archiving procedure. It also covers connecting a History Database through an application server or directly, selecting an archiving procedure, and specifying data retention periods.
Further sections address change management in a History Database and how performance can be optimized by deleting log entries without archiving, plus troubleshooting and support resources. The guide notes that the share of historical data in a One Identity Manager database should not exceed 25 percent, and that several History Databases, including older formats in read-only mode, can be used for TimeTrace analysis and reports.
| Maximum share of historical data | 25 percent of the total volume of a One Identity Manager database |
|---|---|
| Configuration module for the History Database | Data archiving |
| Windows Authentication | Optional; this type of authentication is not recommended |
It should always be started on an administrative workstation.
Yes, it can alternatively be created using the Quantum.MigratorCmd.exe command line program.
The guide states that performance problems may arise.
Yes, older formats are supported in read-only mode.