Content Store, Configuration, and Metadata Management
What the content store holds
The content store is a relational database that holds Cognos objects: folders, reports, dashboards, schedules, jobs, packages, data source definitions, security entries, and configuration metadata. It does not hold the reporting data itself. The configuration directory holds cogstartup.xml and related files; in containers, equivalent settings come from the custom resource and secrets.
Core rules
- Use a supported database and a dedicated schema; grant the runtime user only the required privileges.
- Back up the content store with native database tools and back up the configuration directory separately; a content store backup alone does not restore encryption keys or namespace settings.
- Use deployment export/import to promote content between environments; decide deliberately whether to include access permissions and references.
- Metadata comes from Framework Manager packages, data modules, and data source definitions; keep model and package versions aligned with the content store upgrade.
- Test restore procedures, not just backups.
Worked example
After a failed upgrade, an administrator stops the application, restores the pre-upgrade content store backup, restores the configuration directory, starts the services, and verifies logon, schedules, and a sample report. The restore succeeds because both the database and configuration were captured.
Traps
Backing up only the content store; exporting content with permissions into an environment with different groups; using a database account with excessive privileges; and assuming deployment export is a backup.