How to determine the size of a backup before creating one in RSA Identity Governance & Lifecycle
Originally Published: 2014-10-20
Article Number
Applies To
Issue
*Also known as the database backup, database dump or datapump export file.
Resolution
expdp avuser/<password> directory=Aveksa_ExportImport_Directory ESTIMATE=blocks estimate_only=y logfile=log.log
For more information,
- expdp - Oracle datapump utility which is used for the backup.
- avuser/<password> - Credentials for database access
- directory=Aveksa_ExportImport_Directory - Output directory.
This directory is specified when the database is created and points to/home/oracle/AveksaExportImportDir.
To verify the name of the backup directory, execute "select * from all_directories" as 'avuser' in SQL*Plus.
To verify the name of the backup directory, execute "select * from all_directories" as 'avuser' in SQL*Plus.
- ESTIMATE=blocks estimate_only=y
Do not do the actual backup. Just report the size that the backup will be.
- logfile=log.log - File name that contains the output that you see in the terminal window.
An example session is shown here:
Notice that no backup file is created.
Related Articles
Remote Backups not working with Authentication Manager 8.2 10Number of Views RSA Authentication Manager Restore from Microsoft Azure Snapshot or backup Failed 131Number of Views Create a Backup Using Schedule Backups 115Number of Views Failed to create a backup on Windows shared folder for RSA Authentication Manager 8.1 292Number of Views Partial failure in creating change requests with Java NPE error in RSA Governance & Lifecycle 354Number of Views
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.9 Release Notes (January 2026) Artifacts to gather in RSA Identity Governance & Lifecycle RSA Governance & Lifecycle 8.0.0 Administrators Guide RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?