JP2006107531A - File management device and its method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a device and a method for properly performing a sweeping process or a backup process of a file such as a document, in a file management device such as an electronic library assuring original properties. <P>SOLUTION: When a sweeping process and a backup process are performed on an electronic library file in an electronic library, a file storing a history of the sweeping process or a history of a backup process is generated, and the sweeping and the backup processes are managed. Thus, a user can easily manage as to which medium an original document has been swept to or where a backup copy of the original document is. If the uniqueness of the original document shown in a sweep history and a backup history can be secured, the problem that a plurality of original documents are created on the storage media of a plurality of electronic libraries by the sweeping process or the backup process can be avoided. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to an electronic archive that is a file management apparatus, and more particularly, to the eviction and backup of a file registered in an electronic archive that electronically guarantees originality.

  With the recent development of information devices, documents and the like that have been conventionally managed on a paper basis are now managed as electronic data. On the information processing apparatus, it is easy to copy or tamper with such electronic data documents, and there is a high possibility that the originals of these documents are unclear. As a means for solving such problems, an information apparatus for managing an original electronic document called an electronic library has been put into practical use.

A device that distinguishes an original from a copy, an electronic library, realizes the originality by having the following functions.
(1) Distinguish the original from the copy and make the original unique. At this time, the original is made unique even when the original is moved to another electronic library.
(2) Detect tampering of the original.
(3) Record the operation facts on the original. Also, tampering with the operation fact is detected. Here, the operation indicates all operations such as registration, reference, update, move, copy (copy), creation of backup, eviction to other media, and restoration. In the update, each generation entity is also saved.
(4) Control access authority to the original.

  In this case, since files (electronic documents, etc.) are basically recorded in a RAID (Redundant Array of Independent Disks) device, the total capacity of the file to be stored becomes large, and the DISK can be expanded before it can fit in the RAID device. Or it must be driven out to an external medium.

  When backing up a file, if a recording medium (DISK or the like) as a backup source is destroyed, the backup medium is restored to the state at the time of backup. Of course, the information after the last backup cannot be restored. However, in the case of an electronic library that has originality (or uniqueness of the original), that is, a distinction between the original and the copy, it is necessary to maintain the originality even in restoration after backup. In order to guarantee the originality, it is necessary to provide the above characteristics (1) to (4) as in the case of eviction.

FIG. 24 is a diagram for explaining a document series as a management unit in document management of the electronic library.
When the document 1 is first created, it is stored in the electronic library and becomes the first version of the document 1. This and the management information related to the first version of the document 1 necessary for the electronic library to guarantee the originality are managed as a set of information. Next, when the original document 1 is updated and the second version is created, the management information of the second version of the document 1 and the second version of the document 1 is managed as one set. Similarly, the third version of the document 1 and the management information of the third version of the document 1 are managed as one set. As described above, when the same document 1 is repeatedly updated and sequentially updated from the first version to the n-th version, the documents from the first version to the n-th version of the same document are referred to as one series. In other words, a history of a document that has been changed due to sequential updating or the like is referred to as one series. Therefore, if two documents have been changed due to updates or the like, it is said that there are two series of documents.

In order to guarantee originality, the above special function is required instead of a simple file server. Even when the original is stored electronically, it is usually recorded in a RAID device, as with a general file server. When the capacity of the RAID device becomes full, it becomes necessary to add a DISK device or to drive out old files to a tape or MO. For this reason, in the control of eviction, consideration different from that of a normal file server is necessary. That is,
(1) When kicking out, do not randomly kick out. If it is possible to evict at random, the originals of each version number in the same series are evicted to separate media, and management and operation become complicated.
(2) The evicted information must not be restored to another device. When this is possible, not only do the originals exist in duplicate, but also an important security issue arises.
(3) It is necessary to detect falsification of the expelled external medium. If alteration of the external medium is not detected, the eviction source is deliberately broken, and an illegal original can be created from the altered backup medium.
(4) When the evicted file is used again, it is necessary to clearly manage to which medium the file is evicted.
(5) There may be a case where it is desired to cancel the eviction, for example, when the external medium becomes full during the eviction work and the spare medium is not at hand.
(6) The eviction history file is a backup target in preparation for a RAID-DISK failure. In restoration after RAID device destruction, DISK may become full in the following cases.
(7) Expulsion is not always an external medium. Since expulsion to an external medium is performed manually, there are cases where expulsion while online is inconvenient. There is a possibility that the destination is another electronic archive.

FIGS. 25 and 26 are diagrams for explaining a case where in the eviction process, when the evicted document is restored, it cannot be restored to the recording medium.
First, as shown in FIG. 25A, the documents A to F stored in the first recording medium such as DISK are fully backed up to another second recording medium. Then, as shown in FIG. 25B, if a new document G is added, the first recording medium is still free, so the document G can be stored.

  Next, as shown in FIG. 26A, since the first recording medium is full, it is assumed that the documents A to C are expelled. At this time, the documents A to C are moved to the third recording medium, and a history that the documents A to C are expelled is left. Next, as shown in FIG. 26 (b), the documents H to J are added to the empty areas generated as a result of evicting the documents A to C. At this time, when taking a backup of the document stored in the first recording medium, a backup is taken with respect to the difference from the previously backed up content. That is, the documents G to J added after the previous backup are backed up, and the history that the documents A to C have been expelled is backed up.

  Here, it is assumed that the first recording medium that is the RAID device is destroyed. Then, the documents A to J are to be restored to new recording media from the backed up contents. However, since the new recording medium has only the same capacity as the destroyed first recording medium, the documents A to G can be restored, but the documents H to J are newly recorded. It cannot be restored to the medium.

Also, in the backup of a file, in order to guarantee the originality, not only a file server but also the special function is necessary. Even when the original is stored electronically, it is usually recorded in a RAID device, as with a general file server. Even in the backup, recording to the tape device or the MO device is the same. Also, the updates that have occurred since the previous backup cannot be reflected if the RAID device fails. In order to remedy this, it is necessary to take a backup for each transaction, but this causes a significant decrease in system performance. However, in order to restore after backup, there are the following problems to be solved in addition to the case of a normal file server.
(1) When restoring, it is necessary to reliably restore all backed up information. Partial restoration cannot guarantee the original originality. For example, when a certain original is updated, if only a part of the update history is restored, the operation on the original cannot be guaranteed.
(2) As a countermeasure for (1), prepare a separate operational medium that shows the restoration procedure, and even when restoring along with it, the system manages which operational medium to use when there are multiple media There is a need to.
(3) The backed up information must not be restored to another device. When this is possible, not only do the originals exist twice, but also an important security issue arises.
(4) It is necessary to detect falsification of the backed up external medium. If tampering is not detected, the backup source is intentionally broken, and an illegal original can be created from the tampered backup medium.
(5) Assume that the original is moved to another electronic library after backup. Thereafter, when the RAID device fails and the document is restored, the original is duplicated in the original device and the destination device.
(6) It is necessary to set the backup timing flexibly and minimize performance degradation due to backup work.
(7) In a transaction involving a plurality of originals, it is necessary to control whether all of the originals are backed up at the time of backup or not. This is because a plurality of contradictory files are created after restoration.

  SUMMARY OF THE INVENTION An object of the present invention is to provide an apparatus and a method for appropriately expelling or backing up a file such as a document in a file management apparatus such as an electronic archive that guarantees originality.

  The file management apparatus of the present invention comprises a backup processing means for executing a backup process for recording an electronic file stored in a first recording medium on a second recording medium, information on the electronic file subjected to the backup process, History generation means for generating a history file in association with the identifier of the second recording medium at the backup destination, storage means for saving the history file in a third recording medium, and third information for storing the history file Medium information recording means for recording information on the recording medium in a fourth recording medium.

  The file management method of the present invention includes a step of executing a backup process for recording an electronic file recorded on a first recording medium on a second recording medium, information on the electronic file subjected to the backup process, and the backup A step of generating a history file in which the identifier of the previous recording medium is associated; a step of storing the history file in a third recording medium; and information on the third recording medium storing the history file And recording on the recording medium.

  According to the present invention, when an electronic file is processed, for example, when an electronic file is evicted or an electronic file is backed up, these histories are recorded, so it is clearly determined which electronic file is the original. I can do it. Therefore, only one original should be saved, and backup or eviction can differentiate storage means different from the original or files recorded on the recording medium from the original without losing the originality. Can manage electronic files.

According to the present invention, the eviction technology that guarantees the originality has not been established yet, but the eviction technology for effectively using the DISK capacity can be provided.
According to the present invention, a backup technique that guarantees originality has not been established yet, but a backup method that guarantees originality while maintaining performance can be provided.

First, the eviction process will be described.
When a document file is evicted, management and operation are more efficient in terms of management when evicting files of the same series as a set. For example, the original date, which has already been registered since the date of registration, is unlikely to be updated in the future. In addition, since updates occur regularly, there are cases where it is desirable to store only the latest version in a fast-access DISK. In the embodiment of the present invention, it is assumed that there is a mode in which files of the same series are driven out as a set and a mode in which only past files are driven out. These modes are realized by checking the update date and time of the same series of files specified by the user and expelling files other than the latest one, or when the same series of files is specified by the user. It is sufficient to carry out the process of expelling all the files, which will be easily realized by those skilled in the art.

  In addition, since each electronic library has an electronic library ID, the electronic library ID that has been the source of the eviction is also written on the eviction medium (the eviction destination recording medium of the eviction file) and restored, Prevent restoration to the electronic library.

Further, each electronic archive has a unique encryption key. When a file is evicted, the file is encrypted with the encryption key and recorded.
In the eviction process, when the evicted file is used again, it is necessary to clearly manage to which medium the evicted file is evicted. For this reason, the evicted medium is given an ID and the evicted file is used. And a history file that associates the eviction destination medium with each other. And when restoring, according to the contents of the history file, it is surely restored from the correct medium.

  If the external medium (push-out medium) becomes full during the eviction work and there is no spare medium at hand, there may be a case where it is desired to cancel the eviction. At this time, the data on the DISK is left as it is, and the data (unmanaged data) on the external medium created halfway is not registered in the eviction history file. As a result, the electronic library returns to the state before being expelled, but halfway data (unmanaged data) on the medium is made recognizable later as unmanaged data.

  When full backup, eviction, and differential backup are performed, as described above, there are cases where the data cannot be accommodated in the restoration destination DISK. In preparation for this, the total capacity of the full backup, differential backup and subsequent files is counted, and if it exceeds a predetermined capacity (for example, 70% of the DISK capacity), the full backup is performed again. To prompt the user.

  In the backup method in which differential backup is performed for backup after full backup, each backup is backed up in order of oldest operation history in units of original series, and if a file with eviction history is detected at the time of restoration, the file that has already been eviction Restore while deleting the entity.

  When restoring from a backup medium, the eviction history in the same medium is restored first. If the eviction is described in the file, the entity of the file restored in the restore procedure is deleted first.

The eviction destination is not limited to an external medium, and can be another device having the same function.
FIG. 1 is a configuration example of an eviction history file used in the embodiment of the present invention.

  The eviction history file as shown in FIG. 1 is stored on a recording medium such as DISK, which is different from the eviction file. The eviction history file shown in FIG. 1 includes fields for document information in electronic library, time stamp, storage medium, and medium ID.

  The document information in the electronic library is, for example, a document name, and documents A, B, C, D, and E are stored in FIG. The time stamp records the date and time when each document has undergone the eviction process. This time stamp is a time recorded by a clock equipped in the electronic library. The timepiece is configured so that the time cannot be changed after it is set at the time of factory shipment of the electronic library. The storage medium is information for identifying the eviction destination recording medium, and in this case, “MO” is described. That is, in the case of FIG. 1, it is indicated that the type of the recording medium to which the documents A to E are evicted is MO. The medium ID is an identifier for uniquely determining the recording medium (in this case, MO) in which the documents A to E are stored, and the medium ID indicates which medium the documents A to E are stored in. Can be identified.

  Therefore, when restoring a document file that has been evicted, the electronic library refers to this evicting history file, and for example, when restoring a document A, the medium ID “ An instruction is issued to set the MO specified by “ABCD” in the recording medium reader. By doing so, the originals of the documents A to E can be centrally managed.

  Further, when falsification detection information is added to the original data, the data is encrypted with the key unique to the electronic library, and the data is evicted and restored, the data is restored based on the evicting history file. At this time, since restoration is performed while restoring with the key unique to the electronic library, it is ensured that the evicted data is prevented from being falsified and is reliably restored to the original electronic library.

2 to 5 are diagrams for explaining a method for avoiding the shortage of the DISK capacity when restoring the evicted file by detecting the DISK capacity.
First, as shown in FIG. 2A, if the documents A to C are stored in the first recording medium, the documents A, B, and C are fully backed up to the backup medium at a certain point in time. At the next time, as shown in FIG. 2B, the document D is added.

  Next, as shown in FIG. 3A, the documents A to C are expelled. Then, only the document D is left on the first recording medium, and the recordable area of the first recording medium is expanded. Next, as shown in FIG. 3B, when the document E is added, information about the documents A to C that have been expelled first, that is, the documents A to C, is stored in the first recording medium. Information indicating that it has been evicted is also stored. At this time, the eviction history file is stored in another recording medium. Next, in FIG. 4A, if there is a backup request when the document E is stored, differential backup is performed. That is, the documents D and E are backed up, and information indicating that the documents A to C have been evicted first is also backed up.

  Then, as shown in FIG. 4B, when the document F is added, the total capacity of the documents A to F exceeds 70% of the DISK capacity of the first recording medium in FIG. 4C. Is detected and a full backup request is made. Then, in FIG. 5A, the entire recorded contents recorded on the current first recording medium are backed up. That is, the information that the documents A to C have been expelled and the documents D to F are backed up. When such a backup and eviction is performed and the first recording medium that is a RAID is destroyed, the restoration is performed based on the result of the full backup performed immediately before. That is, the information indicating that the documents A, B, and C are evicted and the documents D to F are restored. In this way, since the documents A to C are not included in the information that is backed up on the entire surface, it is possible to avoid a situation where the recording capacity of the restoration destination is insufficient when the information is restored.

6 to 9 are diagrams for explaining the restore processing when a file having a eviction history at the time of restoration is detected.
First, as shown in FIG. 6A, the entire backup of the documents A to F recorded on the first recording medium which is the main recording device is performed. Thereby, the documents A to F are stored in the backup medium. Next, in FIG. 6B, it is assumed that the document G is added to the first recording medium. Next, in FIG. 7A, documents A, B, and C are expelled to another recording medium, and information indicating that documents A, B, and C have been expelled is stored in the first recording medium. At this time, the eviction history file is also recorded on another medium. In FIG. 7B, it is assumed that documents H and I are further added. Then, backup is performed in FIG. The backup here is a differential backup. That is, information indicating that the documents G, H, and I and the documents A, B, and C have been expelled is backed up.

  At this point, when the first recording medium that is a RAID is destroyed, restoration is performed in FIG. At this time, the documents A to F that were first backed up are restored.

  Next, the second backup (differential backup) is restored. First, in FIG. 9A, the document G is restored. Next, as shown in FIG. 9B, since the contents of the backup file include information indicating that the documents A, B, and C are evicted, the documents A, B, and C are set in an evicted state. At this time, the data eviction processing of the actual documents A to C is not performed. This is because the originals of documents A to C have already been evicted in FIG. Accordingly, in FIG. 9B, the documents A to C are deleted, and information indicating that the documents A to C are evicted is restored. Then, in FIG. 9C, the documents H and I are restored, and the restore process ends.

10 to 12 are diagrams for explaining another embodiment of the restore process of FIGS.
In the present embodiment, the process of FIG. 9 is executed as follows.
That is, as shown in FIG. 10, first, information indicating that the documents A, B, and C are evicted is restored from the second-time backup information stored in the backup medium. Then, in FIG. 11A, the document G that was previously backed up is restored, and then in FIG. 11B, the documents H and I are restored.

  Here, if the documents X, Y, and Z are added between the previous backup and the next backup, and the documents X, Y, and Z are expelled, the documents X, Y, and Z will be deleted during the next differential backup. Only the eviction history is backed up. That is, when the documents X, Y, and Z are stored in the first recording medium as shown in FIG. 12A and the documents X, Y, and Z are evicted as shown in FIG. Document data of the documents X, Y, and Z are stored in the backup medium, and information indicating that the documents X, Y, and Z are evicted is stored in the first recording medium. Then, as shown in FIG. 12C, when backup is performed, differential backup is performed, and information indicating that the documents X, Y, and Z are evicted is backed up.

13 and 14 are diagrams for explaining a specific example of the eviction process.
As a specific example of the eviction process, for example, files A, B, and C are files related to a certain business, D, E, F, and G are related to another business, and the DISK capacity has been exhausted. Suppose you are trying to get rid of things that can be kicked out at once.

  First, processing is started with Begin Transaction, and first, unmanaged data is deleted. Then, the documents A to C are expelled from the DISK to the medium. When the eviction of the documents A to C is completed, the series of eviction processing is terminated by Commit. Next, an attempt is made to expel documents D and E. Also in this case, processing is started by Begin Transaction. Then, the document D is evicted first, and then the document E is evicted. However, document E cannot be ejected because the medium is full. Accordingly, assuming that the process started by Begin Transaction is unsuccessful, the rollback is performed and the process is terminated. As a result, the eviction process is interrupted and the eviction history is not added to the eviction history file. Therefore, the data of the document D written on the medium becomes unmanaged data. As a result, only A, B, and C are recorded in the eviction history file. On the other hand, A, B, C, and D are recorded on the medium. Subsequently, when similarly performing the eviction processing of F and G, in the eviction processing started with Begin Transaction, first, the document D, which is unmanaged data, is deleted from the medium. Then, the documents F and G are expelled from the disk to the medium, and if successful, commit and end the process. In this way, the document D on the medium is recognized as unmanaged data, deleted, and a transaction is established if the capacity of the documents F and G can be accommodated on the medium.

Next, backup processing will be described.
In the embodiment of the present invention, when a file is backed up, a history of which file is stored where is recorded on another medium.

  Conventionally, the restoration procedure is left to the operation of the system administrator. In many cases, if the restoration of some files is omitted and only the necessary files are restored, the operation can be endured. In the embodiment of the present invention, a reliable restore operation can be realized by performing the restore operation based on the contents of the backup history file.

  When there are a plurality of media storing backup files, the system knows which media should be used for restoration by using the backup history file, so that the work can be made more reliable.

Each electronic library has an electronic library ID. When the electronic archive ID is also written in the backup history file and restored, it cannot be restored to another electronic archive.
Alternatively, each electronic archive has a unique encryption key. When backing up, the file is encrypted and recorded with the encryption key.

  When an original transfer transaction after backup occurs at a certain point in time, the fact is recorded in a location (C-MOS memory or the like) other than a normal recording device (RAID device). When restoring, prevent double originals while collating with the destination electronic archive based on that fact.

Since the information can be deleted at the next backup time, the C-MOS memory capacity can be minimized.
The backup operation has a mode for full backup and a mode for backing up the difference changed after full backup. In order to enable differential backup while the device is in operation (online), the differential backup target file is extracted. Then, the exclusion is applied in order from the unused one. If a part of the file is in use, it waits until the use is released, and has a first mode for backing up all the target files after exclusion is completed. However, in this mode, since all other files are exclusive by the backup transaction until all target files are acquired, subsequent requests are awaited. For this reason, there is a second mode in which backup is performed after exclusion of only unused files among the target files, and is held until the next backup timing of the target files being used at that time.

FIG. 15 is a configuration example of a backup history file.
The backup history file includes fields for mode, time stamp, medium, number of sheets, medium ID, and label. The mode indicates the above-described full backup or differential backup. In FIG. 15, only the first backup is a full backup. The time stamp measures and records the time when the backup was performed with a clock attached to the electronic library as described above. The medium indicates what kind of medium the backup destination is, and in FIG. 15, all are MO. The number of sheets indicates how many media the backup file is recorded over, and FIG. 15 describes that two MOs are used at the time of the first full backup. For other differential backups, one MO is used at a time. The medium ID indicates the ID of the medium in which the backup file is stored, and indicates that the same medium is used in the second to fourth differential backups. The label is an identifier for uniquely determining the backup process, and a label is attached to each backup process. In FIG. 15, the second to fourth differential backup processes are given the same identifier as one transaction.

  Depending on the transaction, the files A0, B0, and C0 may be registered and updated in association with each other. When these files are updated to A1, B1, and C1 and then a backup is performed, a transaction other than the backup may happen to be in use while browsing the file C1. At this time, in the second mode, only A1 and B1 are backed up, and if the RAID is subsequently destroyed, if restored, it will be restored to A1, B1, C0 and the consistency of the three parties will not be satisfied. become. In order to prevent this, the following processing flow is adopted.

To access multiple files in association, take the following procedure.
(1) BEGIN TRANSACTION
(2) File A acquisition (exclusive), update (3) File B acquisition (exclusive), update (4) File C acquisition (exclusive), update (5) COMMIT (file A, B, C release)
The electronic library monitors the history of the transaction, recognizes that the files A, B, and C are related, and backs up only when A, B, and C can be acquired in the second mode. If any one of them is not acquired, backup is performed at the next backup timing.

In addition, restoration of backed up files is permitted only in the system initialization state (immediately after installation).
Even if the latest backup data is restored, the data after the backup cannot be restored. Therefore, when the registered document is inconvenient data, it is possible to discard the inconvenient data by restoring the backup data.

  In order to prevent such a situation, restoration is permitted only immediately after system installation. Restoration is performed when the disk is broken. In that case, the system is also installed. Therefore, restore is permitted only in the system installation state.

At the time of restoration (restoration), the procedure is notified to the administrator based on the data in the operation medium (medium used for the main operation by the user), and restoration is performed according to the procedure.
FIG. 16 is a diagram for explaining backup generations.

  The backup generation indicates how many times the backup has been received from the original, and is referred to as the Nth generation file (N is the number of backups). When there are multiple backup generations, the restoration work is ensured by storing which of the operation media should be used in a place other than RAID-DISK (C-MOS memory, RAM, etc.) Make things. The contents of the C-MOS memory are backed up to DISK. When the C-MOS memory is destroyed, the disk is restored from the DISK to the C-MOS memory. When the RAID-DISK is destroyed, the system is first restored, and the restoration procedure is performed in the order of C-MOS memory information → the latest operational medium → the backup medium.

FIG. 17 is a diagram showing a configuration of backup data.
Prevents falsification of backed up data and ensures that it is restored to the original electronic archive. For this purpose, a data structure as shown in FIG. 17 is adopted.

The following information is recorded in the header part.
(1) Electronic library ID (encrypted with an encryption key unique to each electronic library).
(2) Time stamp (same as above)
(3) Medium ID (ID corresponding to the operation medium is encrypted with an encryption key unique to the electronic library).

  Also, backup data is encrypted with a key unique to the electronic archive in order to prohibit falsification and browsing during backup. Further, an alteration detection code such as MAC (Mesage Authentication Code) is added. As a result, even if the encrypted data itself is randomly altered, it can be detected.

  In addition, the area for storing the encryption and electronic library ID in the electronic library is covered with an alarm grid, and the alarm grid is disconnected by the act of stealing the information. To do.

FIG. 18 is a diagram for explaining processing when the original is moved.
FIG. 19 is a diagram for explaining processing when performing backup of an original accompanying movement.
As shown in FIG. 18, some transactions move the original. With the movement of an original, an original in a certain electronic library is moved to another electronic library, and information that “the original has been moved to another electronic library” is recorded in the electronic library.

  Further, as shown in FIG. 19, when the original is moved after the original is backed up, and then the RAID of the electronic library 1 is destroyed, the restored originals of the electronic library 1 and the electronic library 2 exist twice. .

As for other actions (registration, update, etc.), as a matter of course, for RAID destruction after backup, the work in the meantime is lost, but the existence of a double original does not occur.
At the time of differential backup, the target files are only those that have changed since the previous backup. In the case of a device that guarantees originality, it is necessary to guarantee the operation fact of the original, and therefore, not only update but also all actions such as reference and movement are targeted for differential backup.

  For example, it is assumed that there are 10 files A0, B0, C0, D0, E0, F0, G0, H0, I0, and J0. After all of them were backed up in the previous backup, if A0 is updated and some operation occurs in all, such as B1 referring to A1 and B0, it is necessary to back up all of A1 to J1 in the next backup is there. Originally, when backing up, all of them should be controlled exclusively. When a backup transaction occurs, if A1, B1, and C1 are still being used (excluded) by other transactions, D1 to J1 are first excluded by the backup transaction. Acquire and wait for A1, B1, and C1 to be released (there are A2, B2, and C2 at that time). Then, after all targets are acquired, the backup work is started. In the meantime, if any other transaction wants to use any of D1 to J1, it cannot be used because it has been acquired for backup processing. Although this method is reliable, it is inevitable that performance will be degraded in terms of operation.

  Therefore, in the above, there is provided a mode in which only the acquired D1 to J1 are backed up and the backup of A2, B2, and C2 is given up this time. As a result, when another transaction wants to use D1 to J1, it is only necessary to wait for the backup time.

FIG. 20 is a diagram (part 1) for explaining transaction processing and backup.
In the electronic library, it is possible to define a transaction that is first established by performing a series of related operations on a plurality of originals. For example, the cover of reports and approval documents, attached file 1 (text), attached file 2 (images) are each managed as an original on the electronic library, and at the time of revision, the case where two attached files are updated as a set is also supported. To do. In this case, the original is operated according to the following procedure. Assuming that the above three files are A0, B0, and C0, when updating them as a set, the following is performed.
(1) BEGIN TRANSACTION (“1”)
(2) File A0 acquisition (exclusive), update (3) File B0 acquisition (exclusive), update (4) File C0 acquisition (exclusive), update (5) COMMIT (file A, B, C release)
First, in (1), it is declared that the subsequent transactions are sets. Processing of these documents is managed in the electronic library with a transaction ID (not shown) (here, “1”). After that, first, A0 is exclusively acquired, and then B0 and C0 are exclusively acquired. Once a file has been exclusively acquired, it is not released until COMMIT in (5). After COMMIT is completed, each file becomes A1, B1, and C1.

  Assuming that after the series of transactions is completed, backup is performed, and the backup transaction acquires A1 and B1, and another transaction acquires C1 for reference (viewing) before attempting to acquire C1. (It becomes C2 by this reference). Then, only A1 and B1 are backed up.

  In order to solve this, a file operated by a set for each transaction is registered in an area different from RAID (such as a battery-backed C-MOS memory), and only when the set can be acquired at the time of backup. Execute backup. After the backup is completed, the information in the C-MOS memory is cleared. When the backup is not performed, the information in the C-MOS memory is retained, and the information is used at the next backup.

FIG. 21 is a conceptual diagram of processing when recording transaction processing.
FIG. 22 is a diagram (No. 2) for explaining transaction processing and backup.

  The relationship between transaction processing and backup is as shown in FIG. First, documents A0, B0, and C0 are sequentially acquired and updated by Begin Transaction. Then, the process is terminated by Commit. Thereafter, it is assumed that the document D0 is updated. In the case of backing up, the updated documents A1 to D1 are sequentially acquired. In this case, it is assumed that the document C1 cannot be acquired. That is, it is assumed that C1 is referred to by other processing. Then, the backup of the documents A1 to C1, which are files associated with each other, is suspended by a series of processes, and the backup process is performed only for the document D1 generated independently of these documents. Thereafter, the documents A1 to D1 are released. As a result of such processing, only D1 is backed up now.

  As described above, the documents A1 to C1 that are generated and updated in association with the transaction surrounded by the begin transaction and the commit are not backed up unless all of them can be acquired. The consistency of A1 to C1 can be prevented from being destroyed by the backup process.

FIG. 23 is a diagram illustrating a hardware configuration of an electronic library required when the processing of the embodiment of the present invention is realized by a program (software).
The CPU 11 is connected to the ROM 12, RAM 13, communication interface 14, C-MOS memory 15, recording medium 19, recording medium reading device 20, and input / output device 22 via the bus 10. In the case of such an electronic library, an electronic document to be stored is stored in a recording medium 19 such as a hard disk or a portable recording medium 21 such as an MO or a flexible disk. The CPU 11 directly accesses the electronic document from the recording medium 19 via the bus 10 and performs eviction processing and backup processing. The eviction destination and the backup destination are, for example, the portable recording medium 21, and the portable recording medium 21 receives access from the CPU 11 via the recording medium reading device 20. Although the electronic document can be stored in the RAM 13, the RAM 13 is a volatile memory. Therefore, in order to store the electronic document semipermanently, the electronic document is recorded on the recording medium 19 or the portable recording medium 21. There is a need to. The C-MOS memory 15 described in the above embodiment temporarily stores information indicating which electronic archive is backed up. The C-MOS memory 15 is a volatile memory such as the RAM 13 in FIG. 23, and the C-MOS memory 15 can be replaced by the RAM 13.

  Further, the ROM 12 stores a BIOS for enabling basic input / output of the electronic library, and the user instructs the CPU 11 to backup from the input / output device 22 or indicates that it should be ejected. It is possible to input a command or the like and to present a result of processing performed by the CPU 11 to the user. Here, the input / output device 22 includes a display, a mouse, a keyboard, and the like. Further, it is possible to store an electronic document storage process, a document management process, an eviction, a backup process, or an eviction history file and a backup history file generation program stored in the ROM 12 and executed. is there. Of course, the program for performing these processes can be recorded in the recording medium 19 or the portable recording medium 21, and the CPU 11 can perform the above-described processes by developing the program in the RAM 13 therefrom. is there.

  Further, the electronic library may be provided with a communication interface 14 for connecting to a database 18 such as another electronic library via the network 17. In this case, when the capacity of the recording medium 19 is full, or when the portable recording medium 21 cannot be used, etc., the communication interface 14 is used to store a document to be evicted in the database 18 such as another electronic archive, or It is also possible to store a backup file of a document to be backed up via the network 17.

  Furthermore, a program for performing processing related to the embodiment of the present invention such as electronic document storage processing, management processing, eviction, and backup processing is downloaded from the database 18 such as another electronic library via the network 17, and the CPU 11 It is also possible to execute this program. Alternatively, when the network 17 is configured as a LAN or the like, electronic document management can be performed under a network environment.

  In the description of the above embodiment, the encryption has not been described in detail, but it is well known that a unique ID is provided in the electronic library that is an information device, and a specific method of encryption is also provided. Are well known as represented by DES and the like, and will be easily realized by those skilled in the art.

(Appendix 1) Storage means for storing electronic files;
Processing means for processing the electronic file;
History generation means for generating a history file for recording the history of the processing;
Storage means for storing the history file;
A file management apparatus comprising:
(Supplementary note 2) The file management apparatus according to supplementary note 1, wherein the process is an electronic file eviction.
(Supplementary Note 3) The history file includes operations for registering, updating, and referring to electronic files, and the number of operations, and a first mode for expelling all of the electronic file series. The file management device according to appendix 2, further comprising a second mode for expelling only the latest electronic file.
(Additional remark 4) The history file stores an identifier of the eviction source medium, and when restoring the evicted electronic file, the restoration is not performed except for the medium specified by the identifier. The file management device according to attachment 2.
(Supplementary note 5) The file management device according to supplementary note 2, wherein an electronic file to be evicted is encrypted with a key unique to the file management device.
(Supplementary note 6) When a series of related electronic files are evicted, if there is an electronic file that cannot be evicted among all of the series of related electronic files, the evicting process is interrupted. The file management device according to attachment 2.
(Supplementary note 7) When an electronic file in which the history of eviction is recorded in the history file is detected at the time of restoration, the electronic file in which the eviction history is recorded is restored from the restoration destination. The file management device according to attachment 2, wherein the file management device is deleted.
(Supplementary note 8) The file management apparatus according to supplementary note 1, wherein the process is a backup process.
(Appendix 9) The history file records the history of eviction processing in addition to the history of backup. When restoring an electronic file from the backup destination, the history of eviction processing is first restored and recorded in the eviction history. 9. The file management apparatus according to appendix 8, wherein the electronic file being deleted is deleted after restoration.
(Supplementary note 10) The file management apparatus according to supplementary note 8, wherein the history file stores information relating to a backed up file and an identifier of a backup destination medium.
(Supplementary note 11) The file management apparatus according to supplementary note 10, wherein the history file stores an identifier of a backup source medium.
(Supplementary note 12) The file management device according to supplementary note 8, wherein the electronic file is backed up after being encrypted using a key unique to the file management device as a backup source.
(Additional remark 13) The said backup process has the full backup mode which backs up all the electronic files stored in the said storage means, and the differential backup mode which backs up only the difference with the last backup content, It is characterized by the above-mentioned. The file management apparatus according to appendix 8.
(Additional remark 14) When the said backup process extracts the electronic file of differential backup object, when this electronic file is inaccessible, it waits for backup process until it becomes accessible, and the electronic file of differential backup object 14. The file management apparatus according to appendix 13, wherein only accessible electronic files are backed up.
(Supplementary Note 15) When a series of related electronic files are backed up, if there is an electronic file that cannot be backed up among all of the series of related electronic files, the backup process is interrupted. The file management apparatus according to appendix 8.
(Supplementary Note 16) (a) storing an electronic file;
(B) processing the electronic file;
(C) generating a history file for recording the history of the processing;
(D) storing the history file;
A file management method comprising:
(Supplementary note 17) The file management method according to supplementary note 16, wherein the process is eviction of an electronic file.
(Supplementary Note 18) The history file is a first mode in which operations such as registration, update, reference, etc. of electronic files and the number of operations are managed to expel all the series of one electronic file, and one of the electronic files The file management method according to appendix 17, further comprising a second mode for expelling only the latest electronic file.
(Supplementary note 19) The history file stores an identifier of the eviction source medium, and when restoring the evicted electronic file, no restoration is performed except for the medium specified by the identifier. The file management method according to appendix 17.
(Supplementary note 20) The file management method according to supplementary note 17, wherein an electronic file to be evicted is encrypted with a key unique to the file management apparatus.
(Supplementary note 21) When a series of related electronic files are evicted, if there is an electronic file that cannot be evicted from all the related electronic files, the evicting process is interrupted. The file management method according to appendix 17.
(Supplementary Note 22) When an electronic file in which the history of eviction is recorded in the history file is detected at the time of restoration, the electronic file in which the eviction history is recorded is restored from the restoration destination. 18. The file management method according to appendix 17, wherein the file management method is deleted.
(Supplementary note 23) The file management method according to supplementary note 16, wherein the process is a backup process.
(Supplementary Note 24) In the history file, the history of the eviction process is recorded in addition to the backup history, and when the electronic file is restored from the backup destination, the eviction process history is first restored and recorded in the eviction history. 24. The file management method according to appendix 23, wherein the stored electronic file is deleted after restoration.
(Supplementary note 25) The file management method according to supplementary note 23, wherein the history file stores information relating to a backed up file and an identifier of a backup destination medium.
(Supplementary note 26) The file management method according to supplementary note 25, wherein an identifier of a backup source medium is stored in the history file.
(Supplementary note 27) The file management method according to supplementary note 23, wherein the electronic file is backed up after being encrypted using a key unique to the file management apparatus as a backup source.
(Supplementary note 28) The backup process has a full backup mode for backing up all electronic files stored in the storage means and a differential backup mode for backing up only the difference from the previous backup content. The file management method according to attachment 23.
(Supplementary note 29) When the electronic file to be differentially backed up is extracted, if the electronic file is inaccessible, the backup process waits for the backup process until the electronic file becomes accessible, 29. The file management method according to appendix 28, wherein only an accessible electronic file is backed up.
(Supplementary note 30) When backing up a series of related electronic files, if there is an electronic file that cannot be backed up among all of the series of related electronic files, the backup process is interrupted. The file management method according to attachment 23.
(Supplementary Note 31) In a computer, (a) storing an electronic file;
(B) processing the electronic file;
(C) generating a history file for recording the history of the processing;
(D) storing the history file;
A computer-readable recording medium storing a program for realizing a file management method characterized by comprising:
(Supplementary note 32) The recording medium according to supplementary note 31, wherein the processing is eviction of an electronic file.
(Supplementary Note 33) The history file includes operations for registering, updating, and referring to electronic files, and the number of operations, and the first mode for expelling all of the series of one electronic file, The recording medium according to appendix 32, further comprising: a second mode for expelling only the latest electronic file.
(Additional remark 34) The history file stores an identifier of the eviction source medium, and when restoring the evicted electronic file, no restoration is performed except for the medium specified by the identifier. The recording medium according to attachment 32.
(Supplementary note 35) The recording medium according to supplementary note 32, wherein an electronic file to be evicted is encrypted with a key unique to the file management apparatus.
(Supplementary Note 36) When a series of related electronic files are evicted, the evicting process is interrupted when there is an electronic file that cannot be evicted among all of the series of related electronic files. The recording medium according to attachment 32.
(Supplementary Note 37) If an electronic file in which the history of eviction is recorded in the history file is detected at the time of restoration, the electronic file in which the eviction history is recorded is restored from the restoration destination. The recording medium according to attachment 32, wherein the recording medium is deleted.
(Supplementary note 38) The recording medium according to supplementary note 31, wherein the process is a backup process.
(Appendix 39) The history file records the history of eviction processing in addition to the backup history, and when restoring an electronic file from the backup destination, the history of eviction processing is first restored and recorded in the eviction history. 39. The recording medium according to attachment 38, wherein the electronic file being deleted is deleted after restoration.
(Supplementary note 40) The recording medium according to supplementary note 38, wherein the history file stores information relating to a backed up file and an identifier of a backup destination medium.
(Supplementary note 41) The recording medium according to supplementary note 40, wherein the history file stores an identifier of a backup source medium.
(Supplementary note 42) The recording medium according to supplementary note 38, wherein the electronic file is backed up after being encrypted using a key unique to the file management apparatus as a backup source.
(Supplementary note 43) The backup process has a full backup mode for backing up all electronic files stored in the storage means and a differential backup mode for backing up only the difference from the previous backup content. The recording medium according to appendix 38.
(Supplementary Note 44) When the electronic file to be differentially backed up is extracted and the electronic file is inaccessible, the backup process waits for the backup process until it becomes accessible, 44. The recording medium according to appendix 43, wherein only accessible electronic files are backed up.
(Supplementary Note 45) When a series of related electronic files are backed up, if there is an electronic file that cannot be backed up among all of the series of related electronic files, the backup process is interrupted. The recording medium according to appendix 38.

It is a structural example of the eviction history file used in the embodiment of the present invention. FIG. 10 is a diagram (part 1) for explaining a method for avoiding a shortage of DISK capacity when restoring a kicked-out file by detecting the DISK capacity; FIG. 10 is a diagram (part 2) for explaining a method for avoiding a shortage of the DISK capacity when restoring the evicted file by detecting the DISK capacity; FIG. 11 is a diagram (No. 3) for explaining a method for avoiding a shortage of DISK capacity when restoring a kicked-out file by detecting the DISK capacity; FIG. 11 is a diagram (part 4) for explaining a method for avoiding the shortage of the DISK capacity when restoring the evicted file by detecting the DISK capacity; FIG. 10 is a diagram (part 1) for explaining a restore process when a file having an eviction history is detected at the time of restoration; FIG. 10 is a diagram (part 2) for explaining the restore process when a file having an eviction history is detected at the time of restoration; FIG. 11 is a diagram (part 3) for explaining the restore processing when a file having an eviction history is detected at the time of restoration; FIG. 10 is a diagram (part 4) for explaining the restore processing when a file having an eviction history is detected at the time of restoration; FIG. 10 is a diagram (part 1) illustrating another embodiment of the restore process of FIGS. FIG. 10 is a second diagram illustrating another embodiment of the restore process of FIGS. FIG. 10 is a third diagram illustrating another embodiment of the restore process of FIGS. It is FIG. (1) explaining the specific example of a eviction process. It is FIG. (2) explaining the specific example of a eviction process. It is an example of a structure of a backup history file. It is a figure explaining the generation of backup. It is a figure which shows the structure of backup data. It is a figure explaining the process in case the movement of an original is accompanied. It is a figure explaining the process in the case of performing the backup of the original accompanying a movement. FIG. 6 is a diagram (part 1) for explaining transaction processing and backup. It is a conceptual diagram of the process in the case of recording the transaction process. FIG. 10 is a diagram (part 2) for explaining transaction processing and backup. It is a figure explaining the hardware constitutions of the electronic library required when implement | achieving the process of embodiment of this invention with a program (software). It is a figure explaining the series of the document used as a management unit in the document management of an electronic library. FIG. 11 is a diagram (part 1) for explaining a case in which in the eviction process, when the eviction document is restored, it cannot be restored to the recording medium. FIG. 11 is a diagram (part 2) for explaining a case where in the eviction process, when the eviction document is restored, it cannot be restored to the recording medium.

Explanation of symbols

10 bus 11 CPU
12 ROM
13 RAM
14 Communication Interface 17 Network 18 Database of Other Electronic Library 19 Recording Medium 20 Recording Medium Reading Device 21 Portable Recording Medium 22 Input / Output Device

Claims (9)

Backup processing means for executing backup processing for recording the electronic file stored in the first recording medium on the second recording medium;
A history generation means for generating a history file in which information on the electronic file subjected to the backup process is associated with an identifier of the second recording medium of the backup destination;
Storage means for storing the history file in a third recording medium;
Medium information recording means for recording information on a third recording medium storing the history file in a fourth recording medium;
A file management apparatus comprising:   The file management apparatus according to claim 1, wherein the third recording medium is created for each backup generation, and a history file relating to the backup generation is recorded. Means for performing restoration to write back the electronic file stored in the second recording medium to the first recording medium;
The third recording medium corresponding to the latest generation is specified based on the recorded content of the fourth recording medium, and the backup destination recorded in the history file recorded in the specified third recording medium is recorded. Restore procedure notifying means for notifying the user that restoration is to be executed from the second recording medium;
The file management apparatus according to claim 2, further comprising: Executing a backup process for recording the electronic file recorded on the first recording medium on the second recording medium;
Generating a history file associating information on the electronic file subjected to the backup process and an identifier of the recording medium of the backup destination;
Storing the history file in a third recording medium;
Recording information on a third recording medium storing the history file on a fourth recording medium;
A file method comprising:   5. The file management method according to claim 4, wherein the third recording medium is created for each backup generation, and a history file relating to the backup generation is recorded. Means for performing restoration to write back the electronic data stored in the second recording medium to the first recording medium;
The third recording medium corresponding to the latest generation is specified based on the recorded content of the fourth recording medium, and the backup destination recorded in the history file recorded in the specified third recording medium is recorded. A restore procedure notifying step for notifying the user that restoration is to be executed from the second recording medium;
The file management method according to claim 5, further comprising: Computer
Backup processing means for executing backup processing for recording the electronic file stored in the first recording medium on the second recording medium;
A history generation means for generating a history file in which information on the electronic file subjected to the backup process is associated with an identifier of the second recording medium of the backup destination;
Storage means for storing the history file in a third recording medium;
Medium information recording means for recording information on a third recording medium storing the history file in a fourth recording medium;
A program characterized by functioning as   8. The program according to claim 7, wherein the third recording medium is created for each backup generation, and a history file relating to the backup generation is recorded. The program according to claim 7, further comprising:
Computer
Means for performing restoration to write back the electronic file stored in the second recording medium to the first recording medium;
The third recording medium corresponding to the latest generation is specified based on the recorded content of the fourth recording medium, and the backup destination recorded in the history file recorded in the specified third recording medium is recorded. Restore procedure notifying means for notifying the user that restoration is to be executed from the second recording medium;
A program characterized by functioning as

Images