You import backups of the database instance and recover the database status that they contain. To do so, you first import a complete data backup, followed by the related log backups.
If the log volumes of the database instance are available and undamaged and still contain the log from the time of the complete data backup, it suffices to start the database instance after importing the complete data backup. The system then imports the content of the log volume. If the log volumes can no longer be used, you have to recover the corresponding log backups after the data backups.
You can use an option to specify to which point in time the data of the log volume or the log backup is to be imported.
If you used another provider’s backup tool to make these backups, use that tool to recover the database instance. To do so, determine the backup ID of the requested backup first (see: backup_ext_ids_get and backup_ext_ids_list). The Database Manager uses this ID to identify the backup that is to be recovered.
During the recovery using this backup tool, the number of media in a group of parallel backup media must correspond to the number of media used to create the backup. In this case it is not possible to start with a lesser number of media and then continue importing the backup with the remaining media.
The reply to this DBM command gives you information about the import of the backup. However, this information is only displayed when the backup has been imported completely, or if the backup was interrupted. This command may therefore take a long time to execute.
If the automatic log backup was activated before the recovery was started, it is not reactivated automatically after the recovery. To reactivate the log backup function, execute DBM command autolog_on.
You do not need to reload system tables when recovering a database instance.
If a deadlock occurs during the parallel recovery of the database instance with a backup tool, you have to import the backup media of the media group one after the other in the correct order by means of the Database Manager.
· You have the server authorization Recovery.
· You have opened a database session (see: db_connect).
If you want to recover the database instances using another provider’s backup tool, the following prerequisites must also be met:
· You have configured the MaxDB software installation for the backup tool you want to use (see: Installation Manual, Integration Using Backup Tools from Other Providers).
· If you are using NetWorker, you need the exact name of the respective backup pipe for the recovery. Hence, the media group must be configured in exactly the same way it was when you backed up the data. The backup media of the media group have to be imported in the same order.
recover_start <medium_name> <backup_type> [LABEL <label>] [EBID <ebid_list>] [<nnn>] [UNTIL <date> <time>] [AUTOIGNORE]
<ebid_list> :: = <external_backup_ID> | <external_backup_ID>,<external_backup_ID>,...
Options
Option |
Description |
<medium_name> |
Medium from which the backup is to be imported. When recovering a backup made on several media at the same time, you must enter the name of the group of parallel backup media here. |
<backup_type> |
Type of backup to be imported. Possible values are: DATA: complete data backup PAGES: incremental data backup LOG: log backup |
LABEL <label> |
Backup ID of the backup medium to be imported |
<ebid_list> |
List of external backup IDs If the list contains several backup IDs, then these are to be separated by commas. If backup IDs contain spaces, the list must be enclosed in double quotation marks. |
<external_backup_ID> |
Only for recovering a backup that was created with a backup tool: name under which the backup is known to the backup tool. |
<nnn> |
Only for log backup to be imported and only for backup media of the FILE type: Version number of the log backup on the backup medium to be imported |
UNTIL <date> <time> |
Exact time (year, month, day, hour, minutes, seconds) up to which you want to recover |
AUTOIGNORE |
If you are recovering data in parallel, the process is automatically continued by the system. |
OK
Returncode <value>
Date [<value>]
Time [<value>]
Server [<value>]
Database [<value>]
Kernel Version [<value>]
Pages Transferred [<value>]
Pages Left [<value>]
Volume Count [<value>]
Mediumname [<value>]
Location [<value>]
Errortext [<value>]
Label [<value>]
Is Consistent [<value>]
First LOG Page [<value>]
Last LOG Page [<value>]
DB Stamp 1 Date [<value>]
DB Stamp 1 Time [<value>]
DB Stamp 2 Date [<value>]
DB Stamp 2 Time [<value>]
Page Count [<value>]
Devices Used [<value>]
Database ID [<value>]
Max Used Data Page [<value>]
Values for the Reply Fields
Value |
Description |
Date |
Date |
Time |
Time |
Server |
Name of database computer |
Database |
Name of database instance |
Kernel Version |
Version of database software |
Pages Transferred |
Number of pages transferred |
Pages Left |
Number of pages still to be transferred |
Volumes |
Number of backup media used |
Medianame |
Name of backup medium |
Location |
File or device name |
Errortext |
Error message text |
Label |
Backup ID |
Is Consistent |
For data backup only: backup is internally consistent |
First LOG Page |
For data backup: first page of log backup to be imported For log backup: first page saved in log |
Last LOG Page |
For log backup only: last page saved in log |
DB Stamp 1 Date |
Time stamp for first page of log backup |
DB Stamp 2 Date |
Time stamp for last page of log backup |
Page Count |
Total number of pages backed up |
Devices Used |
Number of backup devices used |
Database ID |
Database ID used to identify data and log backups that belong together |
Max Used Data Page |
Maximum number of pages used (indication of minimum database size when backup is imported) |
ERR
<err_code>, <err_description>
[<extended_description>]
Values for the Reply Fields
Value |
Description |
<err_code> |
Error message number See also: Documentation, Messages |
<err_description> |
Description of the error |
<extended_description> |
Cause of error |
The following errors may occur:
Error message number |
Error message text |
Explanation |
-24927 |
ERR_TOOLCHK: the external backup tool was not found |
The external backup tool could not be found or has been installed incorrectly. |
-24926 |
ERR_MEDIUMCHK: the medium cannot be used with an external backup tool |
The specified backup medium cannot be used with the backup tool referred to by the medium name. |
-24925 |
ERR_PREPARE: prepare of the backup operation failed |
The preparations required to use the backup tool could not be completed correctly. |
-24924 |
ERR_DBREQ: cannot start database kernel request |
The database instance was unable to start the restore/recovery operation. |
-24923 |
ERR_TOOLREQ: cannot start external backup tool correctly |
The backup tool could not be started correctly. |
-24922 |
ERR_OPCHK: cannot check state of backup operation |
Unable to check the status of database instance or backup tool. |
-24921 |
ERR_POSTOP: cannot finish backup operation correctly |
Although the recovery was successful, the post-processing steps required could not be performed. |
-24920 |
ERR_BACKUPOP: backup operation was unsuccessful |
The recovery failed due to a problem with the database of the backup tool. |
-24919 |
ERR_CLEANUP: cannot clean up correctly after backup operation |
Although the recovery was successful, the system resources used during the check could not be freed up again. |
Logging on to the Database Manager CLI as operator OLEG with password MONDAY, connecting to database instance DEMODB, recovering the database instance from the backup created with Networker on the backup medium NSRPages (complete data backup type with the external backup ID 9025):
>dbmcli –u OLEG,MONDAY –uDBS –d DEMODB recover_start NSRPages DATA ExternalBackupID 9025