When you start database maintenance, you can choose whether to perform concurrent database archiving.
If you do not select Perform concurrent archive, the Identity Governance server is put in an idle state before starting the archive, and it remains idle while the archive runs. The server does not start the database archive until any active Identity Governance background processes complete, and does not allow new background processes to start until archiving completes. Doing so ensures the database is in a logically consistent state, and that it remains in that state during archiving. No Identity Governance processes will run during archiving, and Identity Governance is not available for use. Therefore, if your archive process takes a a long time, you may want to select Perform concurrent archive.
NOTE:Even a concurrent archive eventually must idle the Identity Governance server to finalize the archive.
If you select Perform concurrent archive, Identity Governance background processes may continue to run, and Identity Governance remains available. A concurrent archive comprises iterations, which are multiple archives. If a change occurs to the database during an archive, another iteration of the archive runs. Because each archive iteration archives only data that has changed since the last iteration, each iteration is an incremental archive that should have less data to archive than the previous iteration, and which reduces the amount of time it takes to archive. Ultimately, to achieve a logically consistent archive, the Identity Governance server must be idled for a final iteration. The final archive iteration is a non-concurrent archive, but because it was preceded by multiple incremental archives, the final archive iteration should not contain as much data to archive, which means Identity Governance is idled for only a very short period of time.
You must specify a time for the final iteration to occur. The final iteration will be produced on or after the specified time. The final archive iteration is, in effect, a non-concurrent archive. In addition to specifying a finalization time, you must specify a time interval to pause between archive iterations to control the number of archive iterations that occur between the time the concurrent archive starts and the time it is finalized.
NOTE:Perform concurrent archive is also an available option for scheduled maintenance that ensures Identity Governance processes are not idle during scheduled database maintenance periods.
If you perform a concurrent archive while an archival reader has accessed the archive, Identity Governance informs you that archiving is “Waiting on archival readers.” Click the message to view details about the maintenance you started, including the number of readers in progress. You can click the number for details about the readers and determine whether you want to continue waiting, or if you want to stop the readers and proceed with the archive.
NOTE:Proceeding with the archive while read activities are in progress can result in incomplete or canceled reports, or missing data.
Database maintenance also allows you to choose whether you want to clean up the database after you archive. For more information about database cleanup, see Section 12.6, Identifying Purgeable Data.
To archive and purge databases:
Select Data Administration > Maintenance.
(Optional) Calculate and view:
Summary of what will be archived in the next archive
Summary of items that could be purged
NOTE:If your database is large, these summaries can take a long time to calculate and can consume significant server resources to produce. Click the Refresh icon to calculate or recalculate summaries. Calculated summaries expire after an hour, and you must click the Refresh icon to calculate them again. You can cancel a running calculation at any time.
Click Start Maintenance.
To purge data without archiving, select Clean up without archive. Identity Governance cleans up only items that were previously archived in the archive database. However, if you disable archiving, all items can be purged. To preserve your data, archive before clean up. You should also make sure your archive data is backed up in your company’s archive system before you disable archive.
To archive without stopping any processes currently in progress, select Perform concurrent archive, and then select values for the following items:
Finalize On Or After to specify the date and time to finalize the archive.
NOTE:At the end of each iteration, Identity Governance checks if the current time is at or past the specified finalization time. If so, Identity Governance immediately starts the final archival iteration. If not, Identity Governance starts the next concurrent archival iteration.
Pause Between Iterations to specify the amount of time to pause after each archive iteration.
To purge data from the operations database after the archive process completes, select Perform cleanup after archive.
NOTE:Identity Governance disables all user operations during the archiving process.
Select whether to pause after any of the phases.
IMPORTANT:If you pause after a phase, the system does not automatically transition to the next phase or exit maintenance mode until a user either manually starts the next phase, or exits maintenance mode, even if the archive fails or is canceled.
Select the number of days to retain data before it is available to purge.
(Optional) Select Advanced Cleanup Configuration check box to specify retention days per entity type and select additional types of data to clean up.
NOTE:Users can access the application and perform all governance operations while cleanup is running.
Click OK.