What are iDBQuery's backup and disaster-recovery options?
iDBQuery supports regular backups of its application configuration and metadata, with restore procedures and, for self-hosted deployments, recovery that fits your own backup and DR processes. Because iDBQuery queries your data in place rather than storing full copies, your source databases remain your system of record and follow your existing DR plan.
Backup and disaster recovery for iDBQuery focus on its own configuration, since your source data stays in your systems.
- What gets backed up - iDBQuery's application state, connection settings, semantic-layer definitions, saved reports, and dashboards, so your setup can be restored after a failure.
- Your data, your DR - because iDBQuery queries sources in place, it does not become a second copy of your databases; those keep following your own backup and recovery plan.
- Self-hosted control - in a VPC or on-prem deployment, iDBQuery slots into your existing snapshot, replication, and restore tooling, so DR meets your RPO and RTO targets.
- Restore testing - we recommend periodic restore drills, and we can advise on backing up the components that carry your configuration.
For example, if a self-hosted iDBQuery host fails, you restore its configuration backup onto new infrastructure and reconnect to the same live sources - your data was never trapped inside iDBQuery to begin with. This reflects the query-in-place architecture: the tool holds the questions, models, and reports, not a warehouse of your raw records, which keeps the recovery scope small and your source-of-truth intact. Contact us for backup guidance tailored to your deployment and DR requirements.
Updated 2026-06-22