Management Console for Unix database files are located in the following locations:
- On Unix/Linux: /var/opt/quest/mcu/db
- On Windows: %SystemDrive%:\ProgramData\Quest Software\Management Console for Unix\db
The data for each database consists of multiple files located in the same directory. All the database files start with the same name as defined by the value in the jdbc.url key. For Management Console for Unix, the database consists of the following files by default:
Table 23: Database files
||This file is used to determine if the database is in use. If console.lck exists, the server is currently running. This file is deleted once the database is properly shutdown. DO NOT BACKUP THIS FILE.|
||This file contains the extra SQL statements that have modified the console database since the last checkpoint (something like the 'Redo-log' or 'Transaction-log', but just text.) For a normal shutdown this file is deleted once the database has completely shutdown. |
||This file contains general settings about the database including the console.properties entry 'modified'. If [modified=yes], the database is either running or was not closed correctly (because the close algorithm sets 'modified' to 'no' at the end).|
||This file contains the SQL statements that make up the database up to the last checkpoint.|
It is best to perform a backup when the HSQLDB is not running. use normal backup methods, such as archiving the files in a compressed bundle.
To backup a database
- Shutdown the HSQLDB server. See Start/stop/restart Management Console for Unix service for details about starting and starting the Management Console for Unix Service.
- Copy the following files to a backup location: console.properties and console.script.
- Once the HSQLDB server is stopped, replace the files in the database directory with the ones you previously backed up. See Database location and files.
- Once you have replaced the files, start the HSQLDB server.
Note: If a backup immediately follows a checkpoint, then the console.log file can also be excluded, reducing the significant files to console.properties and console.script.
You can backup the files while the HSQLDB server is running, but make sure that a shutdown or checkpoint is NOT performed during the backup. If you perform a backup while the server is running, you will need to backup the console.log file, as well. This file will be deleted once the server is shutdown.
Use the following information to determine if the database was shutdown successfully.
State after shutting down the HSQLDB server:
- The console.script file contains the information in the database, excluding data for text tables.
- The console.properties file contains the entry [modified=no].
- There is no console.log file.
Aborted database state (may happen by sudden power outage, Ctrl+C in Windows)
- The console.properties file still contains the entry [modified=yes].
- The console.script file contains a snapshot of the database at the last checkpoint and is OK.
- The console.log file contains all the information to restore all the changes since the snapshot. As a result of abnormal termination, this file may be partially corrupt.