Database recovery

The -R option controls the recovery actions QDB performs when it encounters a missing or corrupt database file. The options are:

In this mode, file manipulation is fully automatic and a best-effort is always made to establish a valid database connection at startup. Files are backed up individually and restored individually.
A corrupt or missing database file is restored from the most recent, valid backup that can be located. If there's no such backup, then a blank database is recreated from the original schema definition.
In this mode, the only action performed is to create a blank database from the original schema definition if the database file is missing at startup. Databases are not restored from backups. If the file is corrupt, the server will not start. If the file is missing or corrupt at runtime, no access to that database is permitted, and it will not be restored or re-created. This mode is intended to allow the creation of a new system, or to give manual control over error recovery (for example, to preserve the corrupt database for later analysis).
In this mode, backups of attached databases are treated as a coherent set, so an error with any one of the component databases causes QDB to restore a complete and matching set of all database files. This is useful if attached databases refer to each other.

The set master is the database that attaches other databases (by using the AutoAttach option in the configuration object). The backup set contains the set master and all attached databases that have BackupAttached enabled. Note that the set master can be backed up incrementally and still belong to the set.

Note: We recommend the following actions to back up and restore your databases as a coherent set: