JP3490912B2 - Backup data management device and backup data management method - Google Patents

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an apparatus that needs to store data together with date information. When backing up the data, the program currently in operation is also stored together with the data in preparation for version upgrade of the program. Regarding the device to back up together.

[0002]

2. Description of the Related Art In a device for storing created data together with its date information, each data record has date information, or a file having date information stores the date data together. It is managed by that. For example, in an office processing apparatus for calculating a medical treatment cost in a medical institution, data of medical treatment performed on a patient is input and stored together with the date of the medical treatment. Then, at the beginning of the next month, medical fees are calculated based on the medical data for one month of the previous month and a receipt is issued. The medical institution submits it to the insurance agency and claims the insurance money. Therefore, in such a device, the data is collectively stored for each month. In addition, multiple months' worth are internally stored and managed in preparation for correction, addition, or deletion of data at a later date.

By the way, it has been conventionally practiced to copy and save data to an external storage medium in preparation for a crash of a built-in file device. This is so-called backup. The backup is usually performed manually at the operator's discretion, and is a storage medium that can be electrically or physically separated from the device, such as a magneto-optical disk (hereinafter referred to as MO disk).
Data is recorded on a disc). The more important the data is and the more frequently it occurs, the more backup is required.

On the other hand, a program for creating and editing the data is sometimes upgraded and updated to a new version. The reason for version upgrade may be due to internal reasons such as bug fixes and functional improvements, or due to external factors such as revision of compliance laws and changes in specifications. It is better to think that different versions of the program will give different results when the same data is input. Therefore, when it becomes necessary to handle the stored old data or the data recorded in the backup medium again, it is preferable to use the version of the program when the data was created.

Therefore, at the time of backup, the program currently in operation at that time is also recorded on the backup medium together with the data. When it becomes necessary to modify the data recorded on the backup medium, the program recorded together with the data is also read, and the read program is executed instead of the operating program to correct the data. Of.

[0006]

When a backup is taken, it is usual to record all the data stored inside in a backup medium. Then, the program being operated at that time, that is, the latest version of the program at that time is recorded together with the backup medium. However, the program recorded on the backup medium together with the data is not always the correct combination for the data. For example, if there is a device that internally stores data for up to 12 months, and the program has been upgraded in the past 12 months, the data before the version upgrade will be performed Cannot say that the current version of the program is a correct application.

Even if the program is upgraded with some compatibility with the old version,
Since the version upgrade may be performed irregularly many times, it cannot always be expected that the program is effective over the entire period of data recorded on the backup medium. In the past, the operator had no choice but to determine the period during which the program can be effectively applied to each backup medium.

[0008]

The present invention comprises means for storing data together with date, means for storing a program for editing the data, means for updating the program, and means for recording an update history. A means for recording the data and the program in the backup means, a means for recording the backup history, and an effective period during which the program recorded in the backup means can be applied to the data recorded in the backup means. The above problem is solved by providing means for deciding with reference to the update history and means for recording the valid period.

[0009]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS FIG. 1 is an office processing apparatus for calculating the number of medical care points in a medical institution, 10 is a processing apparatus, and 20 is a file apparatus. The processing device 10 includes a keyboard 18 for an operator to input medical care data, a display device 17 for displaying data and calculation results, and a magneto-optical disk device 19 for backing up data in the file device 20. Are connected. Further, inside the processing device 10, a medical treatment score is calculated based on medical treatment data input from the keyboard 18, the result is displayed on the display device 17, and a receipt or the like is printed by a printer (not shown). Section 11, a backup processing section 12 for copying the data stored in the file apparatus 20 to the MO disk 9 using the magneto-optical disk apparatus 19, and an installer 16 for updating the program forming the office processing section 11 to a new version. Is provided.

When a new version of the program is supplied via a floppy disk, a CD-ROM, a communication network (neither is shown), etc., the installer 16 replaces the current version of the program according to the instruction. , Version upgrade is implemented. The backup processing unit 12 also includes a data copy unit 13 that copies data from the file device 20 to a backup medium, and a backup content management table 40.
The table updating unit 14 that records the valid period of the backed up data and the valid period setting unit 15 that records the valid period of the backed up data. Although the MO disk is used as the backup medium in the embodiment, the present invention is not limited to this, and for example, C
A recording medium such as a D-R or a magnetic tape, which is a write-once type or a rewritable type, can be used.

In the embodiment, the file device 20 is composed of a hard disk device, in which the current month data 21 in which the medical care data for the current month is stored and past medical care data for a plurality of months are stored. The past data 22 to be stored, a history table 30 in which the history of the program installed by the installer 16 is recorded, and a management table 40 in which the history of the backup by the backup processing unit 12 is recorded are stored in the form of a file. Then, the medical care data is stored in the file together with the information of the date indicating the date when the medical care action such as treatment and medication is performed. In the example, the most recent 12 including the current month
Monthly medical data can be stored.

FIG. 2 shows the record structure of each of the history table 30 and the management table 40. The same figure (a)
As shown in, the history table 30 records the version number 31 of the installed program, the installation date 32, and the applicable period 33.
These data are additionally recorded by the installer 16 each time installation is performed, that is, each time the program version is upgraded. However, the application period 33 is recorded by the backup processing unit 12 instead of the installer 16, as described later.

The term "applicable period" indicates the year or month in which the version of the program may be used or should be used. In the example, even when the version upgrade was performed on the way instead of the first day of the month, the month was included in the application period of the program that was effective on the last day of the month, that is, operated. There is. The installation date 32 indicates the date when the new version of the program is installed in the office processing apparatus, that is, the date when the installation work is performed. It is not the day when the old program was modified and a new version was created. Therefore,
Even if the same version of the program is installed, the record contents of the history table 30 will be different if the date of execution is different.

On the other hand, FIG. 3B shows the record structure of the management table 40. This month's data 21 in the file device 20
Also, the medical care data stored as the past data 22 is recorded when the backup processing unit 12 backs up the MO disk 9. The backup processing unit 12 copies all the medical care data of the current month data 21 and the past data 22 to the MO disk 9, and further copies the operating programs constituting the office processing unit 11 to the MO disk 9. Then, as information indicating the contents backed up on the MO disc 9, a version number 42 of the program, a medical data retention period 43, a recording date 44 indicating the date of backup, and a MO disc 9 for managing and identifying the same. The unique management number 45 is added to the management table 40 and recorded. Further, the same management data as the contents of this record is also recorded on the MO disk 9. As described above, in the embodiment, one backup medium is produced by one operation, and a management number is assigned to each backup medium for management. In addition, data is not backed up on the same medium.

By the way, when backing up data,
The backup processing unit 12 uses the valid period 41 at the beginning of the record.
Is not recorded. The term of validity means the MO disk 9
It shows the year and month that the program recorded together can be applied to the maximum 12 months of medical care data stored in. As will be described later, this is recorded by the table updating unit 14 at the time of manufacturing the preserved MO disk 9 which should also be called a master backup disk.

The program forming the office processing unit 11 is stored in the file device 20 as a program file (not shown). The backup processing unit 12 can read the program file from the file device 20, copy it to the MO disk 9, and determine the version number.

Next, the operation of the embodiment will be described. First, the installation of the program will be described with reference to FIG. The installer 16 is FD or CD-R according to the instruction.
The program is read from the recording medium such as the OM and the program file currently stored in the file device 20 is overwritten to update the program to the new version (step S31). Then, the version number of the introduced program is recorded in the history table 30 (see the same S
32), the current date is also recorded in the installation date 32 of the history table 30 (at step S33).

The history table 30 recorded in this way
An example of is shown in FIG. Installation date of the table 32
Therefore, this device started operation on January 4, 1998, and the version number 31 of the program first introduced is 1.
It turns out that it is 50. After that, it was upgraded to version 1.60 on March 20, and now it is April 22.
It can be seen that the version 1.70 introduced on the day is the latest program version. The application period 33 is not recorded by the installer 16. This will be described later.

Next, the daily backup work will be described with reference to FIG. In the example apparatus, the first month of the previous month 1
Since we will issue a receipt based on the medical data for months,
Data is stored on a monthly basis. Therefore, it is assumed that most of the backup work will be carried out at the beginning of the next month after the end of the month-end paperwork and the completion of the data for one month.

Therefore, in response to an instruction from the operator, first, the data copy section 13 of the backup processing section 12
The past data 22 stored in the file device 20 is copied to the MO disk 9 in order of oldest month (step S4).
1). Next, the current month's data 21 is copied to the MO disk 9 (at step S42), and the program file is copied to the MO disk 9 (at step S43). Then up to 12
The months and the program are copied to the MO disk 9. Then, in response to this, the table updating unit 14 displays the version number of the copied operating program and the MO
The management table 4 shows the holding period indicating the years and months to which the medical care data recorded on the disk 9 is, the current date, and the unique management number given to the MO disk 9.
0 and the MO disk 9 are both recorded (S
44 to S47).

FIG. 8 is an example of a screen display displayed by the backup processing unit 12 when the backup job is started.
This is an example in which the date on which the backup is made, that is, the recording date is "February 1, 1998". Therefore, from the history table 30 of FIG. 6, the version of the program at that time is “1.50”, and the holding period is from “January 4, 1998” to “February 1998” of the device introduction date. "1 day" Two months have been displayed until the day. The management number of the MO disk 9 is "00.
It can be seen that "1" is added. Then, when the function key of the keyboard 18 is pressed according to the display on the lower left of the screen, the data and program of the contents displayed on the screen by the backup processing unit 12 are copied to the MO disk 9 and the management data is stored in the management table. Record at 40.

In the embodiment, the contents of the management table 40 can be displayed on the screen. FIG. 9 shows an example in which the record information of the management table 40 is displayed on the screen of the display device 17. In this example, it is shown that the backup was performed once in the past, and the management number of the MO disk 9 is 00.
It can be seen that the program version is 1.50, the retention period is from January to February 1998, and the recording date is February 1, 1998 as the content recorded therein. However, the valid period 41 is not set yet. In this example, since the backup was performed on February 1, the medical data for February, that is, the current month's data is for one day, but is backed up on the MO disk 9.
Therefore, the holding period 43 is two months from January 1998 to February 1998.

Therefore, when setting the valid period of the MO disk 9, the function key of the keyboard 18 is pressed according to the display of the management setting at the lower left of the screen. In response to this instruction, the backup processing unit 12 operates according to the flow shown in FIG. That is, first, the applicable period 33 of the history table 30 is set, and then the valid period of the MO disk 9 is set and recorded.

Setting operation of the applicable period 33 (step S6)
1) will be described in detail with reference to FIG.
Reads the first record of the history table 30 (step S51) and determines whether the start month of the applicable period 33 of the record is already set. If not set (S52; No), the month of the installation date 32 recorded in the record is recorded as the start month of the effective period 41 (S53). The start month is the start time of the period, and represents the first month of the period in the embodiment. And, the month before the first month is the version one generation before,
That is, it is recorded at the end of the effective period 41 of the immediately preceding record (at step S53). The end of the month is the end of the period,
Similarly, it represents the last month of the period. However, if there is no previous record, the setting for the last month is not performed. Then, subsequent records are sequentially read and this process is repeated. Therefore, the end record is not set for the last record, that is, the latest version.

When the setting of the history table 30 is completed in this way, returning to FIG. 7, the record information is read from the MO disk 9 (at step S62), and the application period 33 corresponding to the version number is referred to the history table 30. The obtained first month is set as the first month of the effective period (at step S63). Then, when the start month is not included in the holding period 43, the first month of the holding period 43 is set as the start month of the valid period (S6 in the same step).
5). Next, the end of the valid period is determined from the recording date as follows (at step S66). That is, if the recording date of the MO disk 9 is from the 1st to the 24th of a certain month, the preceding month is the ending month, and if the recording date of the 25th or later is the ending month. . This is based on the idea that backups taken after the 25th will generally cover the medical care data for the month.

If there is a contradiction as a result of comparison, such as when the start month and the end month determined in this way are reversed, the process proceeds to error processing. If there is no contradiction, the effective period of the management table 4
0 and the MO disc 9 are recorded (S68).

Then, another record in the management table 40 is inspected for the MO disk 9 having the same valid period as the valid period or the valid period included in the valid period (S69). If there is such an MO disk 9, it is judged that there is duplication, and a message for notifying it is displayed on the display means (S71). Then, when the operator instructs the discarding of the old MO disk 9, the record of the management record is deleted from the management table 40 (at the same step S).
73).

FIG. 10 shows the effective period setting section 15 of the backup processing section 12 as a result of instructing the management setting on the display screen of FIG. 9 to set the effective period of the MO disk 9.
It is a display example of the effective period set by. Effective period setting section 1
5 is the recorded program version 1.50
From the history table 30, it can be seen from the history table 30 that the installation date 32 is January 4, 1998, so the first month of the effective period is determined to be January 1998. Next, since the recording date is February 1 of the same year, the last month is the month before February,
Decided to be January. In this way, the effective period indicated by the underline on the screen is displayed from January 1998 to January of the same year.

Then, when the operator instructs the registration according to the display on the lower left of the screen, the valid period setting unit 15 records the determined valid period in both the management table 40 and the MO disk 9 concerned. Then, returning to the original screen displaying the contents of the management table 40, as shown in FIG.
The valid period of the MO disk 9 whose management number is 001 is displayed.

Further, let us now consider a case where an effective period is set for the MO disk 9 created in the backup operation on March 2, 1998. FIG. 12 shows an example of the screen display. Since the recording date of the MO disc 9 having the management number 002 is March 2, the program version is 1.
50, Data retention period is recorded from January to March. From this, the first month of the valid period of the data will be January, while the last month will be the month immediately preceding the March of the recording date,
February is set. After that, when registration is instructed, the valid period from January 1998 to February 1998, which is underlined, is recorded in both the management table 40 and the MO disk 9.

By the way, the valid period of the MO disk 9 with the management number 001 is one month of January 1998, and is included in that of the management number 002. Moreover, since the version of the program is 1.50 and the same, it is possible to replace the MO disk 9 with the management number 001 with the MO disk 9 with the management number 002. Therefore, step S
Since the inspection after 69 determines that there is duplication, the backup processing unit 12 indicates, for example, "There is a medium whose validity period overlaps" on the original screen displaying the contents of the management table 40, as shown in FIG. Is displayed, and the valid periods of both are underlined. In response to this, if the operator instructs the disposal of the old version according to the display on the lower left of the screen, the backup processing unit 12
Deletes the management information of management number 001 from the management table 40, issues a mount request for the same disk,
The management information and backup data are erased from the MO disk 9. This makes it possible to reuse the old version disc.

[0032]

According to the present invention, it becomes possible to easily set the effective period for which the program recorded together is applicable to the data recorded on the backup medium for each medium and record the data. This makes it easy to determine the backup medium that contains the data to be modified and the correct combination of programs.
It

[Brief description of drawings]

FIG. 1 is a block diagram showing a configuration of an embodiment.

FIG. 2 is a diagram showing a record structure of a history table and a management table in the embodiment.

FIG. 3 is a diagram showing an installation procedure in the embodiment.

FIG. 4 is a diagram showing a backup procedure in an embodiment.

FIG. 5 is a diagram showing a procedure of setting a history table in the embodiment.

FIG. 6 is a diagram showing the contents of a history table according to the embodiment.

FIG. 7 is a diagram showing a procedure for setting an effective period in the embodiment.

FIG. 8 is a screen display example of a backup job in the embodiment.

FIG. 9 is a screen display example of a backup job in the embodiment.

FIG. 10 is a screen display example of a backup job in the embodiment.

FIG. 11 is a screen display example of a backup job in the embodiment.

FIG. 12 is a screen display example of a backup job in the embodiment.

FIG. 13 is a screen display example of a backup job in the embodiment.

[Explanation of symbols]

Reference Signs List 10 processing device 11 office processing unit 12 backup processing unit 13 data copying unit 14 table updating unit 1
5 Effective period setting unit 16 Installer 17 Display device 18 Keyboard 19 Magneto-optical disk device 9 MO disk 2
0 File device 21 Current month data 22 Past data 30 History table 31 Version number 32 Installation date
33 Application period 40 Management table 41 Effective period 42 Version number 43 Retention period 44 Recording date 45 Management number

Front page continuation (58) Fields surveyed (Int.Cl. ⁷ , DB name) G06F 9/445

Claims (2)

(57) [Claims] 1. Data is stored on a monthly basis and
Storage means for storing a program for editing data in
And means for updating the program, means for recording the update history, and external backup of the data on a monthly basis.
Record the program and copy the program
And means for recording the up means, means and the lifetime can be applied to programs that are also recorded in the backup unit to the data recorded in the backup unit updates footwear for recording the backup history
History and backup history
The month including the date of program renewal
Start month, and the month including the date when the backup was performed
It will be the end month of the effective period, and at that time, backup will be performed
If the date you made is before the specified day of the month,
A deciding means for deciding the month before the end month as the end month, and the deciding means
The validity period determined by the stage is stored in the internal storage unit or the buffer.
Hands to record on at least one of the backup means
A backup data management device characterized in that a step is provided. 2. Data is stored on a monthly basis and
Storage means for storing a program for editing data in
And a means for updating the program,
In the updater management device, the data is recorded monthly on an external backup means.
And the same program as the same backup means
The step of recording and the step of recording the history of the update.
And the above data to external backup means on a monthly basis.
Record and backup the same program as above
The step of recording in the means and the history of the backup
The step of recording and the recording in the backup means
The backup means for the data
The effective period for which the recorded program is applicable is updated above.
Steps to be decided by referring to new history and backup history
The month including the date of program update
Set to the start month of the effective period, including the date of backup.
The valid month is the end month of the validity period, and the backup
If the date of execution is before the specified day of the month
Is the step of determining the month preceding the ending month as the ending month,
The effective period is stored in the internal storage means or
A method for managing backup data , comprising the step of recording in at least one of the means.
Law.