KR20010004069A - Data backup and restore method in relation database and method for monitoring capacity of stroage the relation database - Google Patents

Abstract

PURPOSE: A backup/restore method of a relational database and a method for monitoring a capacity are provided to backup/restore every relational database and to backup/restore while an application program is performed. CONSTITUTION: A database archiver is outputted on a monitor by a GUI(Graphic User Interface)(204) to decide a backup/restore objective period and a storing medium and to select the backup/restoration by a user. In deciding and selecting by the user, a user configured definition file(206) defining backup/restore conditions is checked by deciding a backup/restoring data with a table unit. The database(200) and the decided storing medium are backup/restored according to the conditions about the defined table in the user configured definition file.

Description

DATA BACKUP AND RESTORE METHOD IN RELATION DATABASE AND METHOD FOR MONITORING CAPACITY OF STROAGE THE RELATION DATABASE}

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a system for accumulating data obtained in response to a passage of time in a related table of a relational database. In particular, the present invention relates to a backup / restore of data of a database that accumulates data generated over time in a related table. / restore).

In general, a relational database, that is, a system that manages data using a relational database (RDB), in a system such as a network management system (NMS), accumulates data acquired in response to the passage of time in a related table of the RDB. To manage. In such a system, there are many applications that use a database (hereinafter referred to as "DB"). Among these applications, there are programs that need to backup / restore / delete the DB at regular intervals.

In general, data backup and restoration according to a commercial DB tool or a conventional algorithm are sequentially performed based only on a date when data is stored. At this time, the unit of backup / restore is entire DB. As the unit of backup / restore is the whole DB, the DB processes cannot be used during operation. Therefore, access to data, that is, read / write, is impossible during backup / restore. And because DB processes are not available during operation, if the operation is stopped for backup / restore, data loss occurs during the operation. In addition, since the unit of backup / restore is the entire DB, it is difficult to backup / restore only the desired part and it is slow. In the case of general-purpose backup tools, there are a lot of tasks that need to be processed.

In addition, the conventional backup / restore method depends on the method provided by a particular commercial DB. As a result, when the DB is changed, the backup / restore tool cannot be recycled, and the backup / restore tool had to be modified every time the application was changed.

In addition, when the capacity of the stored data reaches the capacity of the DB, that is, the capacity of the hard disk selected as the DB area, not only the operation of the DB but also the operation of the entire software is stopped. Therefore, conventionally, the user has to check the capacity of the DB periodically or at a desired time period before such a problem occurs.

Accordingly, an object of the present invention is to provide a backup and restore method that can be used for the backup / restore of all RDB.

Another object of the present invention is to provide a backup and restore method capable of backup / restore even during execution of an application program.

Another object of the present invention is to provide a backup and restore method that can improve the speed and stability with ease of backup / restore.

Another object of the present invention is to provide a monitoring method that can automatically warn a user in advance before using all of the DB capacity.

1 is an exemplary diagram of a user defined file according to an embodiment of the present invention;

2 is a system configuration diagram according to an embodiment of the present invention;

3 is a GUI illustration of a database archiver according to an embodiment of the present invention;

4 is a diagram illustrating a GUI of a status window for monitoring a capacity of a database according to an embodiment of the present invention;

5 is a flowchart of a backup / restore process according to an embodiment of the present invention;

6 is a capacity monitoring process flow diagram according to an embodiment of the present invention.

In order to achieve the above objects, the method of backing up and restoring the present invention includes a GUI (Graphical User Interface) for selecting a DB archiver for selecting whether to perform backup / restoration together with designation of a backup / restore target period and storage medium. When the backup / restore operation is selected along with the screen output by the user and the backup / restore target period and storage medium in the DB archiver by the user, the backup / restore data for the DB can be designated in table units. The process of checking the user configured definition file that defines each condition of restoration, and saving the DB and designated data by record according to each condition of backup / restore for the table defined in the user definition file. And a process of executing backup / restore between the media.

In addition, the monitoring method of the present invention for achieving the above object is a process of periodically checking the ratio of the used capacity to the total capacity of the DB, and if the result of the ratio of the used capacity to the total capacity exceeds the predetermined threshold ratio And displaying a warning message on the screen.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. While many specific details are set forth in the following description and in the accompanying drawings, such as examples of specific user defined files, to provide a more general understanding of the invention, these specific details are illustrated for purposes of explanation of the invention, and the invention is directed to them. It is not meant to be limited. And a detailed description of known functions and configurations that may unnecessarily obscure the subject matter of the present invention will be omitted.

First of all, the present invention defines and backs up only the data desired by the user as a user-defined file shown in the example of FIG. 1 and backs up / restores records in table units. Accordingly, the user can create a user-defined file such as Fig. 1 that defines the DB backup / restore by referring to the table name of the desired DB using a conventional editor and save it in the American Standard Code for Information Interchange (ASCII) file format. Done.

In the above user definition file of FIG. 1, "#" is the start of a comment. The "!" Comes before the name of the database, and the tables below this statement use the given database. Therefore, the user-defined file of FIG. 1 is for a DB whose DB name 102 is "eventdb". The definition statement is composed of a table name 104, an operator 106, and parameters 108 and 110. In FIG. 1 the table name 104 is "table name", the operator 106 is "op", the parameters 108 and 110 are two and one parameter 108 is "param1" and the other parameter. (110) shows an example of "param2".

In the example of FIG. 1, the operator is one of time, condition, automatic deletion, duplicate check, duplicate deletion, storage space optimization, and index, and a value to be given to a parameter is determined according to the operator. For these operators in Figure 1, the time operator is "time", the condition operator is "cond", the auto delete operator is "autodel", the duplicate check operator is "check", the duplicate delete operator is "nodup", The storage optimization operator is shown as "stroage" and the index operator as "index".

First of these operators, the time operator "time" performs a backup by comparing the given time range with the value of the date-time field given as parameter 108. The field given here is meaningful only if it has a date-time attribute.

Secondly, the conditional operator "cond" is given a related-table field as parameter 108 and a common field as parameter 110. The conditional operator "cond" allows backup / delete according to the relevant table when the table does not have a date-time attribute. For example, in FIG. 1, since the "alarm-sub" table has the "alarm_id" field as a common field, when the record having the same "alarm_id" field of the "alarm_data" table is backed up / deleted, it is backed up / deleted.

Thirdly, the autodelete operator "autodel" is given a date-time field as parameter 108 and a period field as parameter 110. Automatic deletion operator "autodel" is an operator that automatically deletes records after a certain period of time. Records whose date-time fields are older than the duration field will be automatically deleted by the application. In this case, the unit of period is, for example, months, which may be changed according to an application program.

Fourth, the duplicate check operator "check" is given a check field as parameter 108. The duplicate check operator "check" prevents the restoration of duplicate records at the time of restoration. That is, if a record having the same check field value is attempted to be restored, it prevents duplicate values from being stored in the DB 200. Checking a field in which a unique is declared in the DB 200 design greatly helps maintain the consistency of the DB 200.

Fifth, the deduplication operator "nodup" is given a duplicate-delete field as a parameter 108. Duplicate deletion operator "nodup" is a function that periodically removes duplicates in order to save storage space, if there is an application program that allows the duplication of the DB (200). Duplicate-Delete If there is a duplicate field, only one is left and the other is automatically removed.

Sixth, the storage optimization operator "storage" operates without parameters. When there is a deletion of records, the storage optimization is performed. In the case of RDB, there are some products that do not increase the storage space used by deleting records. An example of such an RDB is Informix. Therefore, after performing a backup or delete, use the storage optimization operator "storage" to reallocate storage space. However, storage reallocation is time-consuming and requires careful use.

Seventh, the index operator "index" is given an indexing field as parameter 108 and an index-name field as parameter 110. After performing the storage optimization operator "storage" operation, the existing index can be deleted. In this case, the index operation by the index operator "index" is created when there is no index so that it does not interfere with application execution.

And as shown in Figure 1 by creating a user-defined file in the table unit record backup / restore of the table unit is made. By using the backup / restore unit as a table, the DB can be accessed during the backup / restore operation. Accordingly, it is possible to prevent data loss during backup / restore by improving access that was previously inaccessible during DB backup / restore, and backup / restore software even when the schema of the DB storage table is changed when using such a user-defined file. The operation of is not affected. Also, it can be applied to any RDB because it backs up / restores the table unit records to a temporary file without depending on the backup / restore tool of a specific DB. It also enables the sorting of tables as well as dates, making it easy to manage the data you want or important data.

Figure 2 shows a system configuration according to an embodiment of the present invention to backup / restore / delete and monitor the DB based on the user-defined file as described above. In FIG. 2, the DB 200 is a DB for storing data continuously obtained over time. The storage management block 202 outputs the DB archiver of FIG. 3 and the status window of FIG. 4 to be described later by the GUI 204, and based on a user-defined file 206 based on a user input from the DB archiver, the DB ( Perform backup / restore / delete for 200). The storage management block 202 also monitors the capacity of the DB 200 as described below, and outputs a warning message through the warning message processing block 208. The user definition file 206 is created and stored as in the example of FIG. 1 described above.

3 is a diagram illustrating a GUI of a DB archiver according to an exemplary embodiment of the present invention. The DB archiver 300 for selecting a backup / restore / delete operation by the user with a designation of a backup / restore / delete target period and a storage medium. The screen of the is shown. Here, reference numeral 302 is an icon for selecting a backup, 304 is an icon for selecting a restore, 306 is an icon for selecting a delete, 308 is a status check icon for monitoring DB capacity, and 314 is selected for execution. 316 is an icon for closing the DB archiver 300. Reference numeral 310 is an input window for designating a storage medium, and 312 is an input window for designating a backup / restore / delete target period. 3 shows an example in which the target period is designated from December 1, 1998 to December 10, 1998.

4 is a diagram illustrating a GUI of a status window 400 that is displayed on a screen when a status check icon 308 is input from the DB archiver 300 of FIG. 3 according to an embodiment of the present invention. In addition to showing the status of the ratio of the capacity used in preparation, the screen of the status window 400 for the user to set the storage capacity threshold ratio is shown. The state window 400 of FIG. 4 is output when the icon 308 is input by the user in the DB archiver 300 of FIG. Reference numeral 402 denotes an elliptic figure of the used capacity relative to the total capacity of the DB 200. For example, the hatched portion represents the used capacity and the remaining portion represents the unused capacity. In addition, reference numeral 404 is a window for displaying the total capacity of the DB 200, 406 is a window for displaying the currently used capacity, and 408 is a window for inputting and displaying a threshold ratio set by the user. 4 shows an example in which the total capacity is 10 GB, the currently used capacity is 5.5 GB, and the threshold ratio is set to 75%.

5 is a flowchart illustrating a backup / restore process according to an embodiment of the present invention. Referring to FIG. 5, in step 500, the GUI of the DB archiver 300 of FIG. 3 for selecting a backup / restore / delete or not by executing a backup / restore / delete target period and a storage medium. The screen is output by 204. In this state, steps 504 to 510 are performed by receiving the user input of step 502.

At this time, if the user wants to backup, the user creates a user-defined file 206 for the backup of the desired data and specifies the date in which the data to be backed up is stored in the DB archiver 300. As described above, when the backup execution is selected together with the backup target period and the storage medium in the DB archiver 300, the storage management block 202 responds to the operations in steps 512 and 510. By specifying the data to be backed up / restored / deleted for the DB 200 in table units, confirming the user-defined file 206 shown in FIG. 1 that defines the conditions for backup / restored / deleted, step 514. The DB 200 searches for records belonging to the period specified by the DB archiver 300 for the table defined in the user definition file 206. That is, the user sequentially searches the data stored in the DB 200 meeting the specified date and the conditions of the table specified in the user definition file 206. If no data meets the search criteria, a temporary file is created to make a copy. According to the conditional search of the entire DB, the retrieved data is copied to one file. Next, in step 516, if there is data that meets the search conditions, a temporary file is created and a copy is made and stored in the designated storage medium. In other words, after the search is complete, the copy is moved to the user-specified medium. At this time, the medium may use an ASCII file or tape. The process then returns to step 502 described above.

Here, suppose that a value given as in FIG. 3 is 1998/12/01 to 1998/12/10. In addition, in FIG. 1, the "alarm_data" table is defined to perform backup by the "loggingtime" field. Therefore, when performing a backup, the "alarm-data" table will back up records with the "loggingtime" field from 1998/12/01 to 1998/12/10.

When the user wants to restore, the user requests the restoration by specifying the ASCII file or tape name generated using the above-described storage method through the input window 310 in the DB archiver 300. As described above, when the user selects the restoration execution with the restoration target period and the storage medium in the DB archiver 300, the storage management block 202 responds to the operation at steps 504 and 510. In step 520, the user definition file 206 is checked, and in step 520, the table defined in the user definition file 206 is created in the DB 200, and an index used in the generated table is generated. Next, in step 522, the table is copied to the table created in the DB 200 from the designated storage medium in record units of the table. In other words, copy from the ASCII file or tape to the table created in the DB in the record unit of the table. The process then returns to step 502 described above.

Therefore, the storage unit is tabulated using user-defined files to improve data storage speed, stability, and ease of storage. By copying / moving records in table units, the DB 200 can be accessed even during data backup / restore, thereby improving stability.

In addition, if the user selects the deletion target in the DB archiver 300 together with the deletion target period, the storage management block 202 checks the user-defined file 206 in step 524, and the user in step 526. The record belonging to the period specified for the table defined in the definition file 206 is deleted from the DB 200. The process then returns to step 502 described above.

As described above, backup / restore using user-defined file enables not only backup / restore based on date, but also selective storage and restoration by table, thereby improving speed and stability with ease of backup / restore. . And since backup / restore uses table-based record read / write method, it can be applied to data backup / restore of any RDB. That is, it can be applied to DB backup and restore of all applications using RDB, and backup / restore is possible even while the application is running. In addition, since selective table write / read is used, it has the effect of speed improvement compared to the conventional method which needs to backup / restore all data based on date only. In addition, users can backup and restore, auto-delete, duplicate delete, and optimize storage space using only the technology of user-defined files. And just by changing these customization files, you can use them in any application that uses RDB.

On the other hand, if the user wants to automatically receive a message for exceeding the capacity threshold of the DB (200) sets the desired threshold ratio. To this end, when a user inputs a status check icon 308 for checking the capacity of the DB 200, the screen 404 displays the status window 400 by the GUI 204 in step 528. Thereafter, in steps 530 to 532, a threshold ratio is set according to a user input. At this time, the threshold ratio is set based on the capacity of the entire DB 200 as 100, and the set threshold ratio is stored in the form of an ASCII file. If it is not set, it is automatically set as the default value, for example, 70% of the total capacity.

When the threshold ratio is set as described above, in step (600) to (602) of FIG. 6, the ratio of the used capacity to the total capacity of the DB 200 is periodically checked to determine the threshold ratio of the used capacity. Check if it is exceeded. At this time, the checking interval is, for example, 10 minutes. If the ratio of the used capacity exceeds the threshold ratio, in step 604, a warning message for notifying the threshold value is displayed through the warning message processing block 208. After that, the process returns to step 600 above. At this time, the warning message uses a display method using a UNIX motif, for example. As such, the stored data and the capacity of the DB 200 are calculated and the message is automatically delivered to the user, thereby providing stability of the DB 200 itself.

Therefore, it is possible to set the capacity threshold ratio of the DB 200 desired by the user, and once the threshold ratio is monitored, when the threshold ratio is exceeded, the DB 200 and the entire software are automatically delivered to the user without the user checking directly. Prevent malfunctions beforehand. It is possible to set the threshold so that the available capacity of the DB can be selected and the automatic message delivery improves the reliability of DB and software operation.

Meanwhile, in the above description of the present invention, specific embodiments have been described, but various modifications can be made without departing from the scope of the present invention. In particular, in the embodiment of the present invention, all the embodiments for backup / restore / delete and monitoring, but may be selectively applied only when necessary during backup / restore / delete and monitoring. In addition, in monitoring, it can be applied only to confirming whether the threshold rate is exceeded and warning. Therefore, the scope of the invention should not be defined by the described embodiments, but should be defined by the equivalent of claims and claims.

As described above, the present invention can be applied to DB backup and restore of all applications using RDB by performing backup / restore using a user-defined file, and backup / restore can be performed even while the application is running. In addition, only user-defined file technology is available for backup / restore, automatic deletion, duplicate deletion, and storage space optimization.

Claims (11)

A method for backing up and restoring data in a database in a system that accumulates data obtained in response to a passage of time in a related table of a relational database, A process of outputting a database archiver for the user to select whether to execute backup / restore along with designation of backup / restore target period and storage medium by GUI; When the backup / restore execution is selected by the user with the designation of the backup / restore target period and storage medium in the database archiver, each of the backup / restore by specifying data desired for backup / restore for the database in table units. Checking the user-defined file that defines the conditions for And performing backup / restore between the database and the designated storage medium on a record basis for each table defined in the user-defined file according to the conditions of backup / restore. The method of claim 1, wherein the user-defined file is generated by the user and stored in advance in an ASCII file format. A method for backing up and restoring data in a database in a system that accumulates data obtained in response to a passage of time in a related table of a relational database, A process of outputting a database archiver by the GUI for selecting a backup target period and a storage medium with a GUI, If the backup execution is selected by the user with the designation of the backup target period and storage medium in the database archiver, the user-defined file which defines the backup conditions by specifying the data to be backed up for the database in table units is selected. To check, Searching the database for records belonging to the specified period for the table defined in the user definition file; And if there is data that meets the search conditions, creating a temporary file, making a copy, and storing the copy in the designated storage medium. The method of claim 3, wherein the user-defined file is generated by the user and stored in advance in an ASCII file format. 5. The method of claim 3 or 4, wherein the user-defined file includes an operator for duplicate deletion when making the copy. A method for backing up and restoring data in a database in a system that accumulates data obtained in response to a passage of time in a related table of a relational database, Displaying, by the GUI, a database archiver for the user to select whether to restore or not, along with a restoration target period and a storage medium; If the restore execution is selected by the user with the restoration target period and storage medium in the database archiver, the user-defined file defining the restoration conditions is defined by specifying the data to be restored in the table unit. To check, Creating a table defined in the user definition file in the database and creating an index to be used in the generated table; And copying, by record unit of the table, from the designated storage medium to the table created in the database. The method of claim 6, wherein the user-defined file is generated by the user and stored in advance in an ASCII file format. A method for backing up and restoring data in a database in a system that accumulates data obtained in response to a passage of time in a related table of a relational database, A process of outputting a database archiver for the user to select whether to execute backup / restore / delete with the designation of backup / restore / delete target period and storage medium by GUI; When the backup execution is selected by the user with the designation of the backup target period and storage medium in the database archiver, the data to be backed up, restored, or deleted for the database is designated in table units. Checking the user-defined file that defines the conditions for Searching the database for records belonging to the specified period for the table defined in the user definition file; If there is data that meets the search conditions, creating a temporary file, making a copy, and storing the copy in the designated storage medium; Identifying, by the user, the user-defined file if the restoration execution is selected with the designation of the restoration target period and storage medium in the database archiver; Creating a table defined in the user definition file in the database and creating an index to be used in the generated table; Copying, by record unit of a table, from the designated storage medium to a table created in the database; Checking the user defined file when the deletion execution is selected by the user with the designation of the deletion target period in the database archiver; And deleting a record belonging to the specified time period from the database for the table defined in the user definition file. The method of claim 8, wherein the user-defined file is generated by the user and stored in advance in an ASCII file format. A method for monitoring the capacity of a database in a system that accumulates data obtained in response to a passage of time in a related table of a relational database, Periodically checking a ratio of the used capacity to the total capacity of the database; And displaying a warning message when the ratio of the used capacity to the total capacity exceeds a preset threshold ratio as a result of the checking. A method for monitoring the capacity of a database in a system that accumulates data obtained in response to a passage of time in a related table of a relational database, Outputting, by the GUI, a database archiver for setting whether or not to check a state for checking the capacity of the database; When the status check is selected in the database archiver by the user, a status window is displayed for the user to set a storage threshold ratio as well as the status of the ratio of the used capacity to the total capacity of the database. Printing process, Setting the threshold ratio when the storage capacity threshold ratio is input by the user in the status window; Periodically checking a ratio of the used capacity to the total capacity of the database; And displaying a warning message when the ratio of the used capacity to the total capacity exceeds a preset threshold ratio as a result of the checking.