JPH08212142A - Data backup system for data base - Google Patents

Abstract

PURPOSE: To provide the data backup system for performing the backup of data to be contributed to the speedy and sure recovery of a data base at the time of fault generation. CONSTITUTION: This system is provided with a control part 11 for controlling the various operations of the data base, external storage device 20 where a data base file 21 is stored, control file 12 for storing start conditions in order to start backup, backup executing part 13 for performing the backup of data from the data base file 21, backup medium 30 for storing the backup data, backup history possessing part 14 and history file 15 for possessing and managing backup history.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a data backup system for backing up data in a database, and more particularly to a data backup system for swiftly and reliably recovering data when a failure occurs.

[0002]

2. Description of the Related Art Generally, a database stores a large amount of data in an external storage device using a storage medium such as a magnetic disk. Therefore, if some failure occurs in the storage medium or the external storage device itself, the data may not be read. Therefore, in order to avoid the loss of the data, the data is backed up. The backed up backup data is used to restore the database when a failure of the medium or the external storage device occurs.

In a conventional data backup system for backing up data in such a database, data is backed up by input of an instruction from the outside by a user, or at a predetermined timing (for example, at regular intervals or in advance). The data was automatically backed up at a predetermined time. Then, a database administrator or the like intervenes in the operation of backup data in the recovery of a failure and the management of a backup execution history including information such as a medium and time when the backup was performed.

[0004]

The above-mentioned conventional data backup system is a database management system that manages backup data when recovering from a failure and manages a backup execution history including information such as the medium and time when the backup was performed. The restoration procedure was not unified because some people and others intervened. For this reason, the procedure is complicated, and in some cases, an unrecoverable state may occur.

In the past, when restoring a database, the backup data from the latest backup was used to restore the state immediately before the occurrence of a failure. If the backup just before the occurrence of the failure has failed, or if there is an error in individual data before the failure becomes apparent at the system level of the medium or external storage device, there is the drawback that sufficient recovery cannot be performed there were.

An object of the present invention is to provide a data backup system that solves the above-mentioned conventional drawbacks and that backs up data that can contribute to quick and reliable restoration of a database when a failure occurs.

[0007]

In order to achieve the above object, the present invention relates to an external storage device storing a database file, a control file storing a start condition for starting a backup, and the database file. The control unit controls various operations of the database including reading and writing of data, inputs a start condition of the backup and registers it in the control file, and refers to a start condition of the backup stored in the control file to determine a predetermined value. A backup execution unit that backs up data from a database file at a timing, a backup medium that stores backup data, a backup history acquisition unit that acquires an execution history of the backup when the backup execution unit makes a backup, and Backup history collection Part is configured to include the to and the historical file stores an execution history of the acquired backup.

In another aspect, the backup start condition of the data stored in the control file includes at least a backup medium name for specifying the backup medium storing the backup data and a backup timing. I am trying.

In another aspect, the timing of performing backup included in the backup start condition is
At the very least, you can select a date and time to perform backup, a setting to perform a backup at regular intervals, and a setting to perform a backup at the end of a specific process. The setting is performed by associating each setting with a logical operator of AND or OR.

In another aspect, the backup execution history stored in the history file is at least the medium name of the backup medium storing the backup data, the backup start time and the backup end time, and the backup execution history. It is configured to include the success or failure of the result.

[0011]

[Operation] According to the present invention, when the data is backed up, the backup history acquisition unit acquires the backup execution history and stores it in the history file, so that the backup execution history can be managed.

Further, by managing the backup execution history, it is possible to accumulate the backup media storing the backup data and generate them, and to use the desired backup data when restoring the database.

[0013]

Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram showing the configuration of a data backup system according to an embodiment of the present invention.

As shown in the figure, the data backup system of this embodiment has a control unit 11 for controlling various operations of a database, an external storage device 20 storing a database file 21, and a start condition for starting a backup. A control file 12 to be stored, a backup execution unit 13 for backing up data from the database file 21, a backup medium 30 for storing backup data, a backup history acquisition unit 14 and history file 15 for acquiring and managing backup history. Equipped with.

The control unit 11 controls general operations of the database such as reading / writing data from / to the database file 21 of the external storage device 20 and registers the backup start condition in accordance with the input from the input device 40.

The control file 12 holds the backup start condition registered by the control unit 11. The backup start condition includes at least the backup medium name that specifies the backup medium 30 that stores the backup data and the timing of performing the backup.
By specifying the backup medium 30 and the timing of performing the backup, the backup medium 30
By sequentially storing the backup media, it is possible to achieve generations of backup media. As the timing of performing the backup, it is possible to specify the date and time of performing the backup, to perform the backup at regular intervals, or to perform the backup when a specific process ends.

FIG. 2 shows an example of the structure of data stored in the control file 12. In the illustrated example, the designated date and time and the end time of the predetermined process are the backup timing. The designated date and time and the end time of the process are related by a logical operator (AND or OR) so that the timing of backup can be defined in detail.

The backup execution unit 13 refers to the backup start conditions stored in the control file 12, acquires data from the database file 21 of the external storage device 20 at the registered backup timing, and sets the medium name. It is stored in the registered backup medium 30.

When the backup execution unit 13 backs up the data, the backup history acquisition unit 14 acquires the execution history of the backup and sends it to the history file 15.

The history file 15 stores the execution history of backup received from the backup history acquisition unit 14. The stored backup execution history is output and displayed on the display device 50 when necessary, such as when the database is restored. The backup execution history stored in the history file 15 includes at least the medium name of the backup medium 30 storing the backup data, the backup start time and the backup end time, and the success or failure of the execution result.

FIG. 3 shows a configuration example of a backup execution history stored in the history file 15. In the illustrated example, the backup execution result is "O" when the backup is successful.
“K”, and “NG” is input in the case of failure.

The external storage device 20 is an auxiliary storage device using a storage medium such as a magnetic disk, and stores the database file 21.

The backup medium 30 is a storage medium such as a magnetic disk, and is accumulated and generated every time data is backed up. The backup medium 30 may be a removable medium (floppy disk, magneto-optical disk, etc.) that physically changes the medium once or every few backups, and stores data for several backups. It may be a large-capacity hard disk or the like.

Next, the backup operation of this embodiment will be described with reference to the flowchart of FIG. Note that the backup operation shown in the flowchart of the figure is an example of the operation when the backup start condition configured as shown in FIG. 2 is registered in the control file 12.

First, the backup execution unit 13 refers to the backup start condition stored in the control file 12 at a predetermined timing (step 401). And
Some items are determined according to the configuration of the registered start condition (steps 402 to 406) and it is determined whether or not to perform backup. The backup execution unit 13
The reference timing of the control file 12 is, for example,
It is set between processings by the control unit 11 and other general processings.

When the backup start condition is constituted by the backup execution time, the end of the related processing, and the logical operator associating them with each other as shown in FIG. 2, the backup execution unit 13 first sets the logical operator. If the presence / absence and the logical operator are set, the type is determined (steps 402 and 403). If the logical operator is not set or "OR" is set, it is sequentially determined whether the backup execution time has come and the related processing has been completed (step 40).
4, 405). If any of the conditions is satisfied, backup processing is executed (step 40).
7).

On the other hand, when "AND" is set as the logical operator, it is sequentially judged whether or not the backup execution time has come and the related processing has been completed, and when all the conditions are satisfied. , Backup processing is executed (steps 406 and 407).

When the logical operator is not set or when "OR" is set as the logical operator and neither condition of the backup execution time nor the end of the related processing is satisfied, "AND" as operator
Is set and the condition of either the backup execution time or the end of the related process is not satisfied, the backup is not executed and the process is repeated from the reference of the control file 12 at a predetermined timing. (Step 4
01-406).

When the backup execution unit 13 executes the backup, the backup history acquisition unit 14 acquires the backup history as shown in FIG. 3 and stores it in the history file 15 (step 408). The backup history obtained in this way is displayed on the display device 50 and referred to at the time of restoration or the like when a failure occurs in the database. The database administrator or the like can refer to the backup history displayed on the display device 50, obtain necessary backup data, and restore the database.

The database administrator can restore the database by using the desired backup data from the backup data accumulated and generated so far. Therefore, when the latest backup fails due to an increase in the amount of data, etc., and complete backup data cannot be obtained, the backup data can be obtained and used by going back to the previous backup. In addition, even if the latest backup data cannot be used for recovery because an error occurred in individual data before the failure became apparent at the system level of the medium or external storage device, backup data without error should be It can be selected and used.

Although the present invention has been described with reference to the preferred embodiments, the present invention is not necessarily limited to the above embodiments.

[0032]

As described above, according to the database data backup system of the present invention, when the data is backed up, the execution history of the backup is managed. There is an effect that centralization can be achieved, procedures can be simplified, and quick and reliable restoration can be performed.

Further, by accumulating backup media storing backup data into generations and using desired backup data when restoring the database,
Even if the backup just before the failure occurred due to the increase of the amount of data has failed, or if there is an error in individual data before the failure becomes apparent at the system level of the medium or external storage device. The effect is that reliable recovery can be performed.

[Brief description of drawings]

FIG. 1 is a block diagram showing a configuration of a data backup system according to an embodiment of the present invention.

FIG. 2 is a diagram showing an example of backup start conditions stored in a control file.

FIG. 3 is a diagram showing an example of a backup execution history stored in a history file.

FIG. 4 is a flowchart showing a backup operation of this embodiment.

[Explanation of symbols]

 11 Control Unit 12 Control File 13 Backup Execution Unit 14 Backup History Acquisition Unit 15 History File 20 External Storage Device 21 Database File 30 Backup Medium 40 Input Device 50 Display Device

Claims (4)

[Claims] 1. An external storage device storing a database file, a control file storing start conditions for starting a backup, controlling various operations of the database including reading and writing of data from the database file, and the backup. A control unit for inputting the start conditions of the backup file to be registered in the control file, a backup execution unit for backing up data from the database file at a predetermined timing with reference to the backup start condition stored in the control file, and a backup A backup medium that stores data, a backup history acquisition unit that acquires an execution history of the backup when the backup execution unit performs a backup, and a backup execution history that the backup history acquisition unit acquires. And a history file, a data backup system for a database. 2. The backup start condition stored in the control file includes at least a backup medium name that specifies the backup medium that stores backup data and a backup timing. Database data backup system described in. 3. The backup timing included in the backup start condition is at least the designation of the date and time of the backup, the setting of regularly backing up at regular intervals, and the point when a specific process ends. 3. The data backup system according to claim 2, wherein the data backup system is set by arbitrarily selecting from settings to be backed up and associating each setting with a logical operator of AND or OR as necessary. . 4. The backup execution history stored in the history file indicates at least the medium name of the backup medium storing backup data, the backup start time and backup end time, and the success or failure of the backup execution result. The database data backup system according to claim 1, comprising: