JP2002082821A - Device and method for managing file and recording medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a device and a method which appropriately eject or back up a file of a document, etc., in a file managing device for an electronic library assuring the originality of the document. SOLUTION: In the electronic library, when an electronic document file is ejected or backed up, a file for storing ejection processing history or backup processing history is generated, and ejection processing and backup processing are managed. Thus, it is possible to easily manage which medium the original document is ejected to and where the backup of the original document exists. When the uniqueness of the original document shown by the ejection history and backup history is protected, it is possible to avoid the situation that a plurality of original documents are generated in a plurality of electronic library recording media after all.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an electronic library as a file management device, and more particularly, to eviction and backup of files registered in an electronic library that electronically guarantees originality.

[0002]

2. Description of the Related Art With the recent development of information devices,
Documents and the like that have been managed on a paper basis are now being managed as electronic data. On the information processing device, such electronic data is copied,
Tampering can be easily performed, and it is highly possible that the originals of these documents are unknown. As a means for solving such a problem, an information device called an electronic library, which manages original electronic documents, has been put to practical use.

[0003] An electronic library, which makes it possible to distinguish between an original and a copy, realizes the originality by having the following functions. (1) The original is distinguished from the copy, and the original is unique. At this time, even when the original is moved to another electronic library, the original is made unique. (2) Falsification of the original is detected. (3) Record the operation facts on the original. Also, falsification of the operation fact is detected. Here, the operation is
Indicates all operations such as registration, reference, update, move, copy (copy), backup creation, eviction to other media, and restoration. In updating, the entity of each generation is also stored. (4) Control access authority to the original.

In this case, basically, a file (such as an electronic document) is stored in a RAID (Redundant Array of Independence).
In order to record on an ent Disks device, it is necessary to add a DISK or drive out to an external medium before the total capacity of the file to be stored becomes large and cannot be accommodated in the RAID device.

[0005] When a file is backed up, if the recording medium (DISK or the like) of the backup source is destroyed, the file is restored from the backup medium 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 in which the originality (or the originality of the original) is distinguished from the original, it is necessary to maintain the originality even in the restoration after backup. In order to guarantee the originality, the above (1) to (4)
It is necessary to have the characteristics of

FIG. 24 is a diagram showing a document management in an electronic library.
FIG. 6 is a diagram illustrating a series of documents serving as management units. Document 1
Is first created, it is stored in the electronic library and becomes the first version of document 1. This is managed as a set of information, together with management information on the first version of the document 1 that is required by the electronic library to guarantee the originality. Next, when the original document 1 is updated and a second edition is created, the second edition document 1 and the management information of the second edition document 1 are managed as one set. Similarly, the third edition of the document 1 and the management information of the third edition of the document 1 are managed as one set. As described above, if the same document 1 is repeatedly updated and sequentially updated from the first edition to the n-th edition, the documents from the first edition to the n-th edition of the same document are called one series. That is, a history of one document that has been changed after being sequentially updated is referred to as one series. Therefore, if two documents are changed after being updated, it is said that two series of documents exist.

[0007]

In order to guarantee the originality, not only a file server but also the above-mentioned special function is required. Even when the original is stored electronically, it is usually recorded on a RAID device, like a general file server. DISK when RAID device capacity is full
It is necessary to add a device or move old files to a tape or MO. For this reason, the eviction control requires different considerations from those of a normal file server. That is, (1) When kicking out, try not to kick it out at random. If it is possible to eject data at random, originals of each version number in the same series are ejected to different media, which makes management and operation complicated. (2) The ejected information must not be restored to another device. If this becomes possible, not only will the originals be duplicated, but security-critical issues will arise. (3) It is necessary to detect falsification of the ejected external medium. If the alteration of the external medium is not detected, the ejection source is intentionally broken down, and an unauthorized original can be created from the altered backup medium. (4) When a flushed file is used again, it is necessary to clearly manage to which medium the file has been flushed. (5) It is assumed that the user wants to cancel the eviction, for example, when the external medium becomes full during the eviction operation and the spare medium is not at hand. (6) The eviction history file is to be backed up in preparation for a RAID-DISK failure. In the restoration after the destruction of the RAID device, the DISK may be full in the following cases. (7) The eviction is not always limited to the external medium. The eviction to the external medium is manually performed. The dumping destination may be another electronic library.

FIG. 25 and FIG. 26 show the eviction process.
FIG. 14 is a diagram illustrating a case where a flushed document cannot be completely restored to a recording medium when the document is restored. First, FIG.
As shown in (1), the documents A to F stored in the first recording medium such as DISK are entirely backed up to another second recording medium. Then, as shown in FIG. 25B, if a new document G is added, the document G can be stored because there is still room in the first recording medium.

Next, as shown in FIG. 26A, since the first recording medium is full, it is assumed that the documents A to C are to be ejected. At this time, documents A to C are stored in the third recording medium.
And the history that the documents A to C have been kicked out is left. Next, as shown in FIG.
Documents H to J are added to the empty area generated as a result of removing. At this time, when backing up the document stored in the first recording medium, a backup is made of 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, which is a RAID device, has been destroyed. Then, it is attempted to restore the documents A to J to a new recording medium from the backed up contents. However, since this new recording medium has only the same capacity as the destroyed first recording medium, the documents A to G
Up to now, documents H to J cannot be restored to a new recording medium.

[0011] Also, in the case of backing up a file, in order to guarantee the originality, not only a file server but also the above-mentioned special function is required. Even when the original is stored electronically, it is usually recorded on a RAID device, like a general file server. Even in the backup, recording on a tape device, an MO device or the like is no different. Updates that have occurred since the previous backup cannot be reflected if the RAID device fails. To remedy this, it is necessary to take a backup for each transaction, but this will cause a significant decrease in system performance. However, in order to restore after backup, there are the following problems to be solved other than the case of a normal file server. (1) When restoring, it is necessary to surely restore all the backed up information. Original restoration cannot be guaranteed by partial restoration. For example, when a certain original is updated, restoring only a part of the update history cannot guarantee operation of the original. (2) As a countermeasure of (1), when an operation medium indicating a restoration procedure is separately prepared, and restoration is performed along with the operation medium, the system side manages which operation medium to use when there are a plurality of such media. There is a need to. (3) The backed up information must not be restored to another device. If this becomes possible, not only will the originals be duplicated, but also security-critical issues will arise. (4) It is necessary to detect falsification of the backup external medium. If tampering is not detected, the backup source will be deliberately broken and an unauthorized original can be created from the falsified backup medium. (5) Assume that the original has been moved to another electronic library after the backup. After that, when the RAID device breaks down and the document is restored, the original device and the destination device have duplicate originals. (6) It is necessary to flexibly set the backup timing and minimize the performance degradation due to the backup operation. (7) In a transaction in which a plurality of originals are related, it is necessary to control whether all the originals are backed up or not at the time of backup. This is because a plurality of inconsistent files are created after the restoration.

An object of the present invention is to provide an apparatus and a method for appropriately eviction or backup of files such as documents in a file management apparatus such as an electronic library that guarantees originality.

[0013]

According to the present invention, there is provided a file management apparatus comprising: storage means for storing an electronic file; processing means for processing the electronic file; and history generation for generating a history file for recording the history of the processing. Means, and storage means for storing the history file.

According to the file management method of the present invention, (a) storing an electronic file, (b) processing the electronic file, and (c) generating a history file for recording a history of the processing. And (d) saving the history file.

According to the present invention, when processing an electronic file, for example, when eviction of an electronic file or backup of an electronic file is performed, these histories are recorded, so that it is possible to determine which electronic file is the original. You can make a clear judgment. Therefore, only one original should be saved, and by backup or eviction, it is possible to differentiate the storage means different from the original or the file recorded on the recording medium from the original, without impairing the original. , Can manage electronic files.

[0016]

DESCRIPTION OF THE PREFERRED EMBODIMENTS First, the flushing process will be described. When a document file is expelled, it is more efficient to administer and operate files in the same series as a set in terms of management. For example, an original that has already passed since registration and is unlikely to be updated in the future. In addition, since the update is periodically performed, there is a case where only the latest version is desired to be stored in the fast-access DISK. In the embodiment of the present invention, it is assumed that there is a mode in which the same series of files are expelled as a set and a mode in which only the past files are expelled. The realization of these modes is to check the update date and time of the same series of files specified by the user, perform a process to evict files other than the latest one, or if the user specifies the same series of files,
What is necessary is just to perform the process of removing all the files of the same series, and it will be easily realized by those skilled in the art.

Further, since each electronic library has an electronic library ID, it is necessary to write the electronic library ID which is the source of the eviction on the eviction medium (recording destination recording medium of the eviction file) and restore the same. , So that it cannot be restored to another electronic library.

Further, each electronic library has a unique encryption key. At the time of file eviction, 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 file has been eviscerated.
And keep a history file that associates the ejected file with the ejection destination medium. And
When restoring, be sure to restore from the correct medium according to the contents of the history file.

When the external medium (eject medium) is full during the ejection operation and there is no spare medium at hand, it is assumed that the ejection is to be canceled. 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 inside of the electronic library returns to the state before the eviction, but halfway data (unmanaged data) on the medium is made recognizable later as unmanaged data.

When a full backup, eviction, and differential backup are performed, as described above, when restoring,
In some cases, the data may not fit in the restoration destination DISK. In preparation for this, the total capacity of the full backup, the differential backup, and the files generated thereafter is counted, and when the total capacity exceeds a predetermined capacity (for example, 70% of the DISK capacity), the full backup is performed again. Prompt the user.

In a backup method in which a differential backup is taken as a backup after a full backup, each backup is backed up in the order of the original history in the oldest operation history, and when a file having an ejection history at the time of restoration is detected, the file is already ejected. Restore while deleting the entity of the file that has already been deleted.

When restoring from a backup medium, the eviction history in the same medium is to be restored first, and if eviction is described in the file, the substance of the file restored by the restore procedure is first restored. delete.

The destination of the eviction is not limited to the external medium, but may be another device having the same function. FIG.
5 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 in FIG. 1 includes fields of document information in the electronic library, a time stamp, a storage medium, and a medium ID.

The document information in the electronic library is, for example, a document name. In FIG. 1, documents A, B, C, D, and E are stored. The time stamp records the date and time when each document was subjected to the eviction process. The time stamp is a time recorded by a clock provided in the electronic library. This 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 ejection destination recording medium, and in this case, is described as “MO”. That is, in the case of FIG. 1, it is indicated that the type of the recording medium from which the documents A to E have been kicked out is MO. The medium ID is an identifier for uniquely determining a recording medium (MO in this case) in which the documents A to E are stored. The medium ID indicates on which medium the documents A to E are stored. Can be specified.

Therefore, when restoring a document file that has been kicked out, the electronic library refers to this dumping history file and gives a user who wishes to restore the document file, for example, when restoring document A, Medium ID
An instruction is issued to set the MO specified by “ABCD” in the recording medium reading device. In this way, the originals of the documents A to E can be centrally managed.

Further, the original data is added with falsification detection information, the data is encrypted with a key unique to the electronic library, and the data is expelled. When the data is restored, the data is restored based on the expelled history file. At this time, since restoration is performed while restoring using the key unique to the electronic library, falsification of the expelled data is prevented, and it is guaranteed that the data is securely restored to the original electronic library.

FIGS. 2 to 5 show the case where the removed file is restored by detecting the DISK capacity.
FIG. 9 is a diagram for explaining a method of avoiding a shortage of SK capacity.

First, as shown in FIG.
Assuming that documents A to C are stored in the recording medium, documents A, B, and C are fully backed up on a backup medium at a certain point in time. At the next point, as shown in FIG.
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. 3 (b), when the document E is added, the first ejected documents A to C are stored in the first recording medium.
, That is, information that the documents A to C have been expelled. At this time, the flushing history file is stored in another recording medium. Next, in FIG. 4A, when the document E is stored,
If a backup request is made, a 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 expelled first is also backed up.

Then, as shown in FIG. 4B, when the document F is added, in FIG. 4C, the total capacity of the documents A to F becomes 70% of the DISK capacity of the first recording medium. % Is detected and a full backup request is made. Then, in FIG. 5A, the entire recording contents currently recorded on the first recording medium are backed up. That is, information indicating that documents A to C have been ejected, and document D
-F is backed up. If the first recording medium, which is a RAID, is destroyed during such backup and eviction, restoration is performed based on the result of the immediately preceding full backup. That is, the information that the documents A, B, and C have been expelled and the documents D to F are restored. By doing so, the documents A to C are not included in the information to be fully backed up.
The fact that the recording capacity of the restoration destination is insufficient can be avoided.

FIGS. 6 to 9 are diagrams for explaining the restore processing when a file having an eviction history at the time of restoration is detected. First, as shown in FIG. 6A, a full backup of documents A to F recorded on a first recording medium which is a main recording device is performed. Thus, the documents A to F are stored in the backup medium. next,
In FIG. 6B, it is assumed that the document G has been added to the first recording medium. Next, in FIG. 7A, documents A, B,
C is ejected to another recording medium, and information indicating that documents A, B, and C have been ejected is stored in the first recording medium. At this time,
The eviction history file is also recorded on another medium. Then, 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 that the documents G, H, and I and the documents A, B, and C have been expelled is backed up.

At this point, if the first recording medium which is RAID is destroyed, restoration is performed in FIG. 8B. At this time, the documents A to F, which were first fully 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, the contents of the backup file include information indicating that the documents A, B, and C have been expelled.
Put B and C in the kick-out state. At this time, the actual document A
No data elimination process is performed. This is because the originals of the documents A to C have already been expelled in FIG. Therefore, in FIG. 9B, information indicating that the documents A to C have been deleted and the documents A to C have been expelled is restored. Then, in FIG. 9C, the documents H and I are restored, and the restore processing ends.

FIGS. 10 to 12 are diagrams for explaining another embodiment of the restore processing shown in FIGS. In the present embodiment, the processing of FIG. 9 is executed as follows.

That is, as shown in FIG. 10, first, information indicating that the documents A, B, and C have been flushed is restored from the second backup information stored in the backup medium. Then, in FIG. 11A, the document G, which 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 are added at the time of the next differential backup. , Z are only backed up. That is, as shown in FIG.
When Y and Z are stored in the first recording medium and the documents X, Y and Z are expelled as shown in FIG. 12B, the document data of the documents X, Y and Z are stored in the backup medium. At the same time, information that the documents X, Y, and Z have been expelled is stored in the first recording medium. And then, FIG.
As shown in (c), when taking a backup,
The backup becomes a differential backup, and information indicating that the documents X, Y, and Z have been expelled is backed up.

FIGS. 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 task, and D, E, and F and G are related to another task.
Since the DISK capacity has been exhausted, a case will be considered in which an attempt is made to expel those that can be expelled in a lump.

First, processing is started by Begin Transaction, and first, unmanaged data is deleted. And document A
Drive ~ C from DISK to media. When the eviction of the documents A to C ends, a series of eviction processing ends by Commit. Next, an attempt is made to eject documents D and E. Also in this case, the process is started by Begin Transaction. Then, the user tries to eject the document D first, and then ejects the document E. However, the document E cannot be ejected because the medium is full. Therefore, it is determined that the process started by the Begin Transaction is unsuccessful, and a Rollback is performed to end the process. As a result, the eviction process is interrupted halfway, so that the eviction history is not added to the eviction history file. Therefore, the data of the document D written on the medium is 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, in the case of performing the flushing process for F and G in the same manner, in the flushing process started by the Begin Transaction, first, the document D, which is unmanaged data, is deleted from the medium. Then, the documents F and G are ejected from the disk to the medium, and if successful, the process is terminated by committing. As described above, the document D on the medium is recognized as unmanaged data, is deleted, and the transaction is established when the capacities of the documents F and G fit on the medium.

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

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

When there are a plurality of media storing the backup file, which medium should be used for the restoration is determined.
The work can be made more reliable by the system knowing from the backup history file.

Each electronic library has an electronic library ID. The electronic library ID is also written in the backup history file, and when it is restored, it cannot be restored to another electronic library.

Alternatively, each electronic library has a unique encryption key. When backing up, the file is encrypted with the encryption key and recorded. When an original transfer transaction occurs after backup 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, based on the fact, it checks the destination electronic library and prevents double originals.

Since the information can be deleted at the time of the next backup, the capacity of the C-MOS memory can be minimized. The backup operation includes a full backup mode and a mode for backing up the changed data after the full backup. In order to enable the differential backup during the operation (online) of the device, the differential backup target files are extracted. Exclusion is applied in order from unused ones. If some of the files are in use, the system waits until the use is released, and provides a first mode in which all the target files are backed up after exclusion is completed. However, in this mode, other files are excluded by the backup transaction until all the target files are obtained, so that a request generated thereafter is kept waiting.
For this reason, there is a second mode in which backup is performed after exclusive use of only unused files among the target files, and the backup is held until the next backup timing of the target files in use at that time.

FIG. 15 shows an example of the configuration of a backup history file. The backup history file contains the mode,
The fields of time stamp, medium, number of sheets, medium ID, and label are provided. The mode indicates the above-described full backup or differential backup. In FIG. 15, only the first backup is a full backup. The timestamp measures the time when the backup was performed using the clock attached to the electronic library as described above,
It is to be recorded. The medium indicates what the backup destination medium is. In FIG.
It has become. The number of sheets indicates how many media the backup file is recorded on, and
In FIG. 15, MO is set to 2 at the time of the first full backup.
It is described that two sheets are used. At the time of other differential backup, MOs are used one by one. 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 a backup process, and a label is attached to each backup process. In FIG. 15, in the second to fourth differential backup processes, an identifier is given as the same transaction as the process.

Depending on the transaction, file A
0, B0, and C0 may be registered and updated in association with each other. When these files are updated to A1, B1, and C1, and a backup is attempted, a transaction other than the backup may accidentally use the file C1 while browsing. At this time, in the second mode, only A1 and B1 are backed up, and if the RAID is subsequently destroyed, when the data is restored, it becomes A1, B1, C0 and restored in a state where the consistency of the three is not satisfied. become. The following processing flow is adopted to prevent this.

When a plurality of files are accessed in association with each other, the following procedure is taken. (1) BEGIN TRANSACTION (2) Acquire file A (exclusive), update (3) Acquire file B (exclusive), update (4) Acquire file C (exclusive), update (5) COMMIT (release files A, B, C) The electronic library monitors the history of the transaction and recognizes that the files A, B, and C are associated with each other. In the second mode, only the files A, B, and C can be obtained at the time of backup. Backup is performed, and if any one of them cannot be obtained, backup is performed at the timing of the next backup.

The restoration of the backed-up file is permitted only in the system initialization state (immediately after installation). Even if the latest backup data is restored, data after the backup cannot be restored. Therefore, if the registered document is inconvenient data, the inconvenient data can be discarded by restoring the backup data.

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

At the time of restoration (restore), a procedure is notified to an administrator based on data in the operation medium (medium used by the user for the main work), and restoration is performed according to the procedure. I do.

FIG. 16 is a diagram for explaining a backup generation. The backup generation indicates how many times the file has been backed up from the original, and is referred to as the Nth generation file (N is the number of backups). When there are a plurality of backup generations, which one of the operation media should be used is determined in a location other than the RAID-DISK (C-MOS memory or RAM).
Etc.) to ensure restoration work. Further, the contents of the C-MOS memory are backed up to DISK. DISK when C-MOS memory is destroyed
To the C-MOS memory, and when the RAID-DISK is destroyed, the system is restored first, and the restoration procedure is performed in the order of the C-MOS memory information → the latest operation medium → the backup medium.

FIG. 17 shows the structure of the backup data. It prevents falsification of the backed up data and ensures that it is restored to the original electronic library. For this purpose, a data configuration as shown in FIG. 17 is employed.

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

Further, in order to prohibit falsification and browsing in the backup, the backup data is encrypted with a key unique to the electronic library. MAC (Mesage Authentication
Code) is added. This makes it possible to detect even if the encrypted data itself is tampered with at random.

The area for storing the encryption and the ID of the electronic library in the electronic library is covered with an alarm grid. The alarm grid is cut off by the act of stealing the information, and the information is erased by using the alarm grid as a trigger. Strengthen security.

FIG. 18 is a diagram for explaining the processing when the original is moved. FIG. 19 is a diagram for explaining a process in the case of backing up an original with movement.

As shown in FIG. 18, some transactions move the original. Moving originals means moving originals in one electronic library to another electronic library,
In the electronic library, "The original was moved to another electronic library."
Record the information that says

As shown in FIG. 19, after the original is backed up, the original is moved, and then the RA of the electronic library 1 is transferred.
When the ID is destroyed, the restored electronic library 1 and electronic library 2
Will be duplicated.

Other acts (registration, update, etc.) will of course disappear for the RAID destruction after backup, but no duplicate originals will be generated. At the time of the differential backup, the target files are only those that have changed since the previous backup. In the case of an apparatus that guarantees the originality, since it is necessary to guarantee the operation facts of the original, all actions such as referencing and moving, as well as updating, are subject to differential backup.

For example, A0, B0, C0, D0, E0,
It is assumed that ten files F0, G0, H0, I0, and J0 exist. If all operations have been performed on all of them in the previous backup, A0 is updated and A1 and B0 are referred to as B1 by referring to A1 and B0.
In the next backup, all of A1 to J1 need to be backed up. Originally, when backup is performed, all of them should be exclusively controlled. However, when a backup transaction occurs, if A1, B1, and C1 are being used (excluded) by another transaction, the backup transaction first excludes D1 to J1. Acquire, A1, B
1. It will wait for C1 to be released (at that time, A2, B2, C2). Then, after all the objects have been acquired, the backup operation is started. In the meantime, if another transaction wants to use any of D1 to J1, it cannot be used because acquisition for backup processing has been performed. Although this method is reliable, performance degradation is inevitable in terms of operation.

Therefore, in the above, D1-
A mode is provided in which only J1 is backed up and A2, B2, and C2 are backed up this time. As a result, other transactions become D1-J
If one wants to use 1, it is sufficient to wait only for the backup time.

FIG. 20 is a diagram (part 1) for describing transaction processing and backup. In the electronic library, it is possible to define a transaction that is established only when a series of related operations are performed on a plurality of originals. For example, the cover of a report or a request for approval, the attached file 1 (text), and the attached file 2 (image) are each managed as originals in the electronic library, and at the time of revision, the case where two attached files are updated as a set is also supported. I do. At this time, the operation of the original is performed in the following procedure. If the above three files are A0, B0, and C0, and they are updated 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. Transaction ID not shown
(Here, “1”) manages the processing for these documents in the electronic library. After that, first, A0 is exclusively acquired, and then B0 and C0 are exclusively acquired. Once the file has been exclusively acquired, it is not released until COMMIT in (5). COM
After the MIT is completed, the files become A1, B1, and C1.

After the series of transactions has been completed, a backup is performed. The backup transaction acquires A1 and B1, and before the transaction attempts to acquire C1, another transaction acquires C1 for reference (viewing). Suppose that it has been done (it becomes C2 by this reference). Then, only A1 and B1 are backed up.

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

FIG. 21 is a conceptual diagram of a process for recording a transaction process. FIG. 22 is a diagram (part 2) for describing transaction processing and backup.

The relationship between transaction processing and backup is as shown in FIG. First, Begin Transaction
To sequentially obtain and update documents A0, B0, and C0. Then, the processing ends with Commit. afterwards,
It is assumed that the document D0 has been updated. When backing up, the updated documents A1 to D1 are sequentially acquired, but 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, through a series of processes, for documents A1 to C1, which are files associated with each other,
The backup is suspended, and the backup process is performed only on the document D1 generated independently of these documents. Then, the documents A1 to D1 are released. By such processing, only D1 is backed up now.

As described above, Begin Transaction and Commit
Documents A1 to C1 generated and updated in association with each other in a transaction surrounded by are not backed up unless all of them can be obtained, thereby ensuring consistency of related documents A1 to C1. It can be prevented from being destroyed by backup processing.

FIG. 23 is a view for explaining a hardware configuration of an electronic library required when the processing of the embodiment of the present invention is realized by a program (software). CP
U11 is connected to the ROM 12 and the RAM 1 via the bus 10.
3, communication interface 14, C-MOS memory 1
5, connected to the recording medium 19, the recording medium reading device 20, and the input / output device 22. In the case of such an electronic library, an electronic document to be stored is stored in a recording medium 1 such as a hard disk.
9, a MO, a floppy (registered trademark) disk, or another portable recording medium 21. The CPU 11 directly accesses the electronic document from the recording medium 19 via the bus 10 and performs an eviction process and a backup process. The ejection destination and the backup destination are, for example, the portable recording medium 21, and the portable recording medium 21 is the recording medium reading device 20.
The access from the CPU 11 is received via the. The electronic document can be stored in the RAM 13,
Since the RAM 13 is a volatile memory, it is necessary to record the electronic document on the recording medium 19 or the portable recording medium 21 in order to semi-permanently store the electronic document. C described in the above embodiment
-The MOS memory 15 temporarily stores information as to which electronic library was used for backup. C-MOS memory 1
Reference numeral 5 denotes a volatile memory such as the RAM 13 shown in FIG. 23, and the C-MOS memory 15 can be replaced with the RAM 13.

The ROM 12 stores a BIOS or the like for enabling basic input / output of the electronic library. The user inputs or issues a command to the CPU 11 from the input / output device 22 to back up. It is possible to input a command to the effect and the like, and to present the result of the 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. In addition, basic processing of electronic archives,
An electronic document storage process, a document management process, an eviction and backup process, or an eviction history file and a backup history file generation program can be stored in the ROM 12 and executed. Of course, the program for performing these processes is stored in the recording medium 19 or the portable recording medium 2.
1 and the CPU 11 stores the information in the RAM 1
3, the above processing can be performed.

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 becomes full,
When the portable recording medium 21 cannot be used, the communication interface 14 is used to store a backup file of a document to be evicted or a document to be backed up in the database 18 such as another electronic library via the network 17. It is also possible.

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

In the above description of the embodiment, the encryption has not been described in detail, but it is well known that a unique ID is provided in the electronic library which is an information device.
In addition, since a specific method of encryption is well known as typified by DES, it will be easily realized by those skilled in the art. (Supplementary Note 1) Storage means for storing an electronic file, 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 device comprising: (Supplementary Note 2) The file management device according to Supplementary Note 1, wherein the process is eviction of an electronic file. (Supplementary Note 3) The history file is an electronic file registration,
There are a first mode for managing operations such as updating and reference, and the number of operations, and for flushing out the entire series of one electronic file, and a second mode for flushing out only the latest electronic file of one electronic file. The file management device according to claim 2, further comprising: (Supplementary Note 4) The history file stores an identifier of a medium to be ejected, and when restoring an electronic file that has been ejected, restoration is not performed on a medium other than 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 the electronic file to be expelled is encrypted with a key unique to the file management device. (Supplementary Note 6) When a series of related electronic files are to be flushed, if there is an electronic file that cannot be flushed out of all the series of related electronic files, the flushing process is interrupted. The file management device according to attachment 2. (Supplementary Note 7) At the time of restoration, if an electronic file in which the history flushed to the history file is recorded is detected, the electronic file in which the flushing history is recorded is restored from the restored electronic files. 3. The file management device according to claim 2, wherein the file management device deletes the file. (Supplementary note 8) The file management device according to supplementary note 1, wherein the process is a backup process. (Supplementary Note 9) In the history file, the history of the eviction process is recorded in addition to the backup history. When restoring the electronic file from the backup destination, the history of the eviction process is restored first and recorded in the eviction history. 9. The file management apparatus according to claim 8, wherein the electronic file that has been deleted is deleted after the restoration. (Supplementary note 10) The file management device according to supplementary note 8, wherein the history file stores information on the 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 backup source file management device. (Supplementary Note 13) The backup process has a full backup mode for backing up all electronic files stored in the storage unit and a differential backup mode for backing up only differences from the previous backup contents. 8. The file management device according to supplementary note 8, wherein (Supplementary Note 14) In the backup process, when the electronic file to be subjected to the differential backup is extracted, if the electronic file is inaccessible, the backup process waits until the electronic file becomes accessible. 14. The file management device according to claim 13, wherein only the accessible electronic file is backed up. (Supplementary Note 15) When backing up a series of related electronic files, if there is an electronic file that cannot be backed up among all the series of related electronic files, the backup process is interrupted. 8. The file management device according to supplementary note 8, wherein (Supplementary Note 16) (a) storing the electronic file; (b) processing the electronic file;
A file management method, comprising: (c) generating a history file for recording the history of the processing; and (d) storing the history file. (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 manages operations such as registration, update, and reference of an electronic file, and the number of operations, and a first mode for removing all the series of one electronic file;
Appendix 17 characterized by having a second mode for flushing out only the latest electronic file from one electronic file.
File management method described in. (Supplementary Note 19) The history file stores an identifier of a medium to be ejected, and when restoring an electronic file that has been ejected, restoration is not performed on a medium other than the medium specified by the identifier. A file management method according to attachment 17. (Supplementary note 20) The file management method according to supplementary note 17, wherein the electronic file to be expelled is encrypted with a key unique to the file management device. (Supplementary Note 21) In a case where a series of related electronic files are to be expelled, of the series of related electronic files,
18. The file management method according to claim 17, wherein if there is an electronic file that cannot be removed, the removal process is interrupted. (Supplementary Note 22) At the time of restoration, if an electronic file in which the history flushed to the history file is recorded is detected, the electronic file in which the flush history is recorded is restored from the restored electronic files from the restore destination. 18. The file management method according to supplementary note 17, wherein the file 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, a history of the eviction process is recorded in addition to the backup history. When restoring an electronic file from a backup destination, the history of the eviction process is restored first and recorded in the eviction history. 24. The file management method according to Supplementary Note 23, wherein the stored electronic file is deleted after the restoration. (Supplementary note 25) The file management method according to supplementary note 23, wherein the history file stores information on the backed-up file and an identifier of a backup destination medium. (Supplementary note 26) The file management method according to supplementary note 25, wherein the history file stores an identifier of a backup source medium. (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 backup source file management apparatus. (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 differences from the previous backup contents. 23. The file management method according to attachment 23. (Supplementary Note 29) In the backup process, when the electronic file to be subjected to the differential backup is extracted, if the electronic file is inaccessible, the backup process waits until the electronic file becomes accessible. 30. The file management method according to claim 28, wherein only the accessible electronic files are 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 the series of related electronic files, the backup process is interrupted. 23. The file management method according to attachment 23. (Supplementary Note 31) (a) storing an electronic file in a computer; (b) processing the electronic file; (c) generating a history file for recording a history of the processing; and (d). And storing the history file. A computer-readable recording medium storing a program for implementing a file management method. 32. 32. The recording medium according to Supplementary Note 31, wherein the processing is eviction of an electronic file. (Supplementary Note 33) The history file manages operations such as registration, update, and reference of an electronic file, and manages the number of operations, and expels all the series of one electronic file.
A second mode in which only the latest electronic file out of one electronic file is provided.
A recording medium according to claim 1. (Supplementary Note 34) The history file stores an identifier of an ejection source medium, and when restoring an ejected electronic file, restoration is not performed on a medium specified by the identifier. A recording medium according to Supplementary Note 32. (Supplementary note 35) The recording medium according to supplementary note 32, wherein the electronic file to be expelled is encrypted with a key unique to the file management device. (Supplementary Note 36) In a case where a series of related electronic files are expelled, of the series of related electronic files,
33. The recording medium according to Supplementary Note 32, wherein when there is an electronic file that cannot be ejected, the ejection process is interrupted. (Supplementary Note 37) At the time of restoration, if an electronic file in which the history flushed to the history file is recorded is detected, the electronic file in which the flushing history is recorded is restored from the restored electronic files. 33. The recording medium according to supplementary note 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. (Supplementary Note 39) In the history file, a history of the eviction process is recorded in addition to the backup history. When restoring the electronic file from the backup destination, the history of the eviction process is restored first and recorded in the eviction history. 39. The recording medium according to Supplementary Note 38, wherein the stored electronic file is deleted after the restoration. (Supplementary note 40) The recording medium according to supplementary note 38, wherein the history file stores information on the backed-up file and an identifier of a medium of a backup destination. (Supplementary note 41) The recording medium according to supplementary note 40, wherein an identifier of a backup source medium is stored in the history file. (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 device that is the backup source. (Supplementary Note 43) The backup process has a full backup mode for backing up all electronic files stored in the storage unit and a differential backup mode for backing up only differences from the previous backup contents. 39. The recording medium according to Supplementary Note 38. (Supplementary Note 44) In the backup process, when the electronic file to be subjected to the differential backup is extracted, if the electronic file is inaccessible, the backup process waits until the electronic file becomes accessible, and the backup of the electronic file to be subjected to the differential backup is performed. 44. The recording medium according to attachment 43, wherein only the accessible electronic file is backed up. (Supplementary note 45) When backing up a series of related electronic files, if there is an electronic file that cannot be backed up among all the series of related electronic files, the backup process is interrupted. 39. The recording medium according to Supplementary Note 38.

[0074]

According to the present invention, although the eviction technique which guarantees the originality has not been established yet, the eviction technique for effectively utilizing 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.

[Brief description of the drawings]

FIG. 1 is a configuration example of an eviction history file used in an embodiment of the present invention.

FIG. 2 is a diagram (part 1) for explaining a method of detecting a DISK capacity to avoid running out of a DISK capacity when restoring an expelled file;

FIG. 3 is a diagram (part 2) illustrating a method of detecting a DISK capacity to avoid running out of a DISK capacity when restoring an expelled file.

FIG. 4 is a diagram (part 3) illustrating a method of detecting a DISK capacity to avoid running out of the DISK capacity when restoring an expelled file.

FIG. 5 is a diagram (part 4) for explaining a method of detecting a DISK capacity to avoid running out of a DISK capacity when restoring an expelled file;

FIG. 6 is a view for explaining restore processing when a file having an eviction history at the time of restoration is detected (part 1)
It is.

FIG. 7 is a view for explaining restore processing when a file having an eviction history at the time of restoration is detected (part 2);
It is.

FIG. 8 is a view for explaining restore processing when a file having an eviction history at the time of restoration is detected (part 3);
It is.

FIG. 9 is a view for explaining restore processing when a file having an eviction history at the time of restoration is detected (part 4);
It is.

FIG. 10 is a diagram (part 1) for explaining another embodiment of the restore processing of FIGS. 6 to 9;

FIG. 11 is a diagram (part 2) for explaining another embodiment of the restoration processing in FIGS. 6 to 9;

FIG. 12 is a diagram (part 3) for explaining another embodiment of the restore processing in FIGS. 6 to 9;

FIG. 13 is a diagram (part 1) illustrating a specific example of the eviction process.

FIG. 14 is a diagram (part 2) illustrating a specific example of the eviction process.

FIG. 15 is a configuration example of a backup history file.

FIG. 16 is a diagram for explaining a backup generation.

FIG. 17 is a diagram showing a configuration of backup data.

FIG. 18 is a diagram illustrating a process in a case where the original is moved.

FIG. 19 is a diagram for explaining a process in the case of backing up an original with movement.

FIG. 20 is a diagram (part 1) for describing transaction processing and backup.

FIG. 21 is a conceptual diagram of a process for recording a transaction process.

FIG. 22 is a diagram (part 2) for describing transaction processing and backup.

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 implemented by a program (software).

FIG. 24 is a diagram illustrating a document sequence serving as a management unit in document management in an electronic library.

FIG. 25 is a diagram (part 1) illustrating a case where a flushed document cannot be completely restored on a recording medium when the flushed document is restored.

FIG. 26 is a diagram (part 2) illustrating a case where a flushed document cannot be completely restored to a recording medium when the flushed document is restored.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 10 Bus 11 CPU 12 ROM 13 RAM 14 Communication interface 17 Network 18 Database such as other electronic archives 19 Recording medium 20 Recording medium reading device 21 Portable recording medium 22 I / O device

 ────────────────────────────────────────────────── ─── Continuing on the front page (72) Inventor Seigo Kotani 4-1-1, Kamiodanaka, Nakahara-ku, Kawasaki-shi, Kanagawa Prefecture Inside Fujitsu Limited (72) Inventor Takashi Yoshioka 4-1-1, Kamiodanaka, Nakahara-ku, Kawasaki-shi, Kanagawa No. 1 Inside Fujitsu Limited (72) Inventor Keizo Sato 4-1-1, Kamiodanaka, Nakahara-ku, Kawasaki-shi, Kanagawa Prefecture No. 1 Inside Fujitsu Limited (72) Hiroki Inoue 4-1-1, Kamiodanaka, Nakahara-ku, Kawasaki-shi, Kanagawa Prefecture No. 1 F-term in Fujitsu Limited (Reference) 5B018 GA04 HA03 KA03 MA14 5B082 CA17 DD04 DE07 EA11 GA04 GA05 GA11

Claims (11)

[Claims] A storage unit for storing an electronic file; a processing unit for processing the electronic file; a history generation unit for generating a history file for recording a history of the processing; and a storage unit for storing the history file. , A file management device. 2. The file management apparatus according to claim 1, wherein the processing is eviction of an electronic file. 3. The history file stores an identifier of an ejection source medium, and when restoring an ejected electronic file, restoration is not performed on a medium other than the medium specified by the identifier. The file management device according to claim 2, wherein: 4. When a series of related electronic files are expelled, of the series of related electronic files,
3. The file management device according to claim 2, wherein when there is an electronic file that cannot be ejected, the ejection process is interrupted. 5. The file management apparatus according to claim 1, wherein the processing is a backup processing. 6. The history file records a history of an eviction process in addition to a backup history. When restoring an electronic file from a backup destination, the history of an eviction process is restored first, and the eviction history is stored in the history file. The file management apparatus according to claim 5, wherein the recorded electronic file is deleted after the restoration. 7. 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 differences from the previous backup contents. The file management device according to claim 5, wherein 8. When backing up a series of related electronic files, if there is an electronic file that cannot be backed up among all the series of related electronic files, the backup process is interrupted. The file management device according to claim 8, wherein 9. An electronic file storing step, (b) processing the electronic file, (c) generating a history file for recording a history of the processing, and (d) storing the electronic file. Storing a history file. 10. A computer, wherein: (a) storing an electronic file; (b) processing the electronic file; (c) generating a history file for recording a history of the processing; A) storing the history file; and a computer-readable recording medium storing a program for realizing a file management method. 11. A computer comprising: (a) storing an electronic file; (b) processing the electronic file; (c) generating a history file for recording a history of the processing; A) storing the history file; and a program for realizing a file management method.