Backup
Backing up IdentityIQ: database backups plus configuration in source control.
Back up the database on a schedule and keep IdentityIQ configuration (XML objects) exported to source control so you can restore both state and setup.
- Prerequisites for Backup
- Step-by-step install path
- Common pitfalls and fixes
- Verification after install
Backing up IdentityIQ means two complementary things: backing up the database (which holds all state) and keeping the configuration (XML objects) in source control (so the setup is reproducible). Together they let you restore both what the system knew and how it was built. Because all runtime state lives in the database, database backups are non-negotiable.
What to back up, and why
- The database, identities, accounts, roles, policies, certifications and audit history. This is the irreplaceable state.
- Configuration as XML, roles, rules, workflows, application definitions, exported and version-controlled, so the application layer can be rebuilt exactly.
- Secrets and certificates needed to reconnect to sources and targets.
Step by step
- 1. Schedule regular database backups at a frequency that meets your recovery-point objective.
- 2. Export configuration XML and commit it to source control as part of your release process.
- 3. Store backups off-site and encrypted, protecting confidentiality and surviving a site loss.
- 4. Document each backup's contents and retention.
- 5. Test restores periodically, a backup you have never restored is only a hopeful assumption.
Backup and the recovery-point objective
Backup frequency is driven by your RPO, how much data loss is acceptable. A one-hour RPO means backups (or replication) no more than an hour behind. Align the schedule with the business's agreed tolerance rather than a default.
Verify
Confirm backups complete successfully on schedule, are stored securely off-site, and, crucially, can actually be restored in a test.
Common pitfalls
- Backing up the database but not configuration/secrets, leaving you unable to fully rebuild.
- Never testing a restore.
- Backups stored only on-site, lost with the site.