Restoring a database using IBConsole
Go Up to Performing backups and restores using IBConsole
Use the Database Restore dialog to restore databases. To access this dialog, select a server from the list of available servers displayed in the Tree pane and continue with one of these possible methods:
- Select anything under the databases hierarchy and choose Database|Maintenance|Backup/Restore|Restore.
- Double-click any backup alias name under the Backup hierarchy.
- Right-click Backup or any backup alias name under the Backup hierarchy and choose Restore from the context menu.
- Select any backup alias name under Backup and click Restore in the Work pane.
The Database Restore dialog appears:
- Important: When restoring a database, do not replace a database that is currently in use.
To restore a database:
- Check the source Backup File(s) Server to make sure the indicated server is correct. If it is not, cancel this dialog and re-initiate the Database Restore dialog under the correct server.
- If you accessed the Database Restore dialog from a backup alias, then the Alias field is automatically assigned. If you accessed the Database Restore dialog from Backup, then you must select an alias from the list of backup aliases.
Note: The backup alias references the associated backup file names, so you need only to specify the alias name, not the actual backup file name, when indicating the backup to restore. If the backup spans multiple files, the server uses the header page of each file to locate additional files, so the entire backup can be restored based on the alias filename.
- If you choose a backup file alias, the Backup File(s) table displays the associated backup files. If you do not specify a backup file alias, then you can either enter the backup filenames manually, or browse for the file by selecting File from the Alias drop-down list. If you enter the file name manually, include the complete path. It is important that you include all filenames associated with the restore.
To insert a new row into the Backup File(s) table, move to the last row and column in the table and type
W‑Z. - Select a destination server from a list of registered servers in the Database Server drop‑down list.
- If you want to restore to an existing database, select its alias from the Database Alias drop-down list. If you want to restore to a new database, type a new alias name in the Database Alias field.
- In the Filename(s) / Pages table, enter one or more filenames for the restored database and specify the number of pages required for each file. Include the complete path unless you want to place the files in the current working directory. To insert a new row into the Database table, move to the last row and column in the table and type
W‑Z. - You might want to restore a database to multiple files to distribute it among different disks, which provides more flexibility in allocating system resources.
- If you selected an existing database alias, the Database table displays all the associated filenames and number of pages. You can edit any information within this table. You can add another file to the database file list by entering a new filename at the end of the table. You can remove a file from the list by deleting the values in the table.
Note: You cannot restore a database to a network file system (mapped drive).
- You can specify options for the restore by entering a valid value, by clicking the option value and choosing a new value from a drop‑down list of values or by double-clicking the option value to rotate its value to the next in the list of values. See Restore options below for a description of these options.
- Click OK to start the restore.
Typically, a restored database occupies less disk space than it did before being backed up, but disk space requirements could change if the ODS version changes. For information about the ODS, see Restoring the ODS.
Note: The InterBase restore utility allows you to restore a database successfully even if for some reason the restore process could not rebuild indexes for the database. For example, this can occur if there is not enough temporary disk space to perform the sorting necessary to build an index. If this occurs, the database is restored and available, but indexes are inactive. After the restore completes, use
ALTER INDEXto make the indexes active.