JP2008046860A - File management system and file management method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a file management system capable of preventing a file from being illegally taken out. <P>SOLUTION: After receiving a file from a terminal apparatus 5, a master server program 30 generates dispersion information concerned with the file and stores the dispersion information in a dispersion information storage part 316 which is achieved by a non-volatile memory. The master server program 30 divides the file to be stored into the prescribed number of files in each prescribed file size on the basis of the dispersion information and transmits the divided files to slave servers 4. The transmitted divided files are stored in respective slave servers 4. When a file reference request is received from the terminal apparatus 5, the master server program 30 collects the divided files from the slave servers 4 on the basis of the dispersion information concerned with the file, combines the divided files to restore the original file, and transmits the restored file to the terminal apparatus 5. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a file management system for managing files in a distributed manner.

  Since a company owns a lot of personal information, if such personal information is leaked, the company often suffers great damage and loses trust. In general, it is said that leakage of personal information is more often caused by internal people such as workers who maintain the system than by unauthorized access from outside. In this case, the worker or the like takes out a personal information file from a server or the like that manages personal information. Therefore, in order to prevent leakage of personal information, a system in which developers, workers, etc. cannot extract personal information files is required.

Japanese Patent Application Laid-Open No. 2004-228561 discloses a technique for dividing an electronic document (image data or electronic form file) and storing it in a plurality of servers so that the stored electronic document can be searched.
However, when the storage location of each divided file is known, the file may be leaked because the divided file is taken out from each storage location. Further, since the user needs to access each divided file based on the storage location of each divided file given by the search result, the file operation work becomes troublesome. Furthermore, the user recognizes that the file is distributed and managed.

JP 2004-246642 A

  The present invention has been made from the above-described background, and an object of the present invention is to provide a file management system capable of preventing illegal file take-out.

  To achieve the above object, a file management system according to the present invention is a file management system having a parent server and a plurality of child servers, wherein the parent server divides a file, and the dividing unit. File storage means for storing the file divided by the dividing means, the relation storage means for storing relation information between the file divided by the above and the child server in which the file is stored. Have

Preferably, the relation storage means comprises a semiconductor memory device.
Preferably, the parent server includes a plurality of child servers based on a request reception unit that receives a request for a file, a request received by the request reception unit, and relationship information stored in the relationship storage unit. And combining means for combining the divided files stored in the file storage means.
Preferably, the information processing apparatus further includes a rearrangement unit that rearranges the divided files divided by the division unit to the plurality of child servers in a relationship different from the relationship information stored in the relationship storage unit.

  The file management method according to the present invention is a file management system having a parent server having a storage device and a plurality of child servers, wherein the parent server divides the file, and the divided file and the file are The stored relationship information with the child server is stored in the storage device, and the divided file is stored in the child server.

  Preferably, the parent server receives a request for a file, and combines the divided files stored in the plurality of child servers based on the received request and the stored relationship information.

  According to the file management system of the present invention, it is possible to prevent illegal file removal.

FIG. 1 is a diagram showing a file management system 1 according to an embodiment of the present invention.
As shown in FIG. 1, the file management system 1 includes a parent server 3, child servers 4-1 to 4 -n, and a terminal device 5 connected via a network 2. The network 2 is, for example, a LAN or WAN, and may be wired or wireless. In addition, when it shows without specifying any of several component parts, such as child server 4-1 to 4-n, it may abbreviate as the child server 4 etc. only.

  The terminal device 5 performs operations such as new file creation, reference, and deletion with respect to the parent server 3. The parent server 3 divides the file to be managed, and stores relationship information between the divided file and the child servers 4-1 to 4-n in which the divided file is stored. The child servers 4-1 to 4-n store the files divided by the parent server 3. Accordingly, the parent server 3 transmits / receives a file to / from the terminal device 5, while the child servers 4-1 to 4-n do not transmit / receive a file to / from the terminal device 5, and transmits / receives the divided files. Between 3 and 3. The parent server 3 may also store the divided files. When the parent server 3 receives a request for referring to the managed file from the terminal device 5, the parent server 3 combines the divided files stored in the child servers 4-1 to 4 -n based on the relation information. In response to the request from the terminal device 5 such as file reference.

FIG. 2 is a diagram illustrating a hardware configuration of the parent server 3, the child server 4, and the terminal device 5.
As shown in FIG. 2, the parent server 3 or the like includes a CPU 10, a memory 12 such as a DRAM made of a volatile semiconductor storage device, a storage device 14 such as a hard disk drive for storing data in a readable / writable manner, and a network. 2 and a communication interface (IF) 16 for transmitting and receiving data to and from another computer, and a user interface (UI) device 18 including a touch panel or a liquid crystal display and a keyboard pointing device. These components are connected to each other via a bus 20.

FIG. 3 is a diagram showing a functional configuration of the parent server program 30 operating on the parent server 3.
As illustrated in FIG. 3, the parent server program 30 includes a request receiving unit 300, a combining unit 302, a dividing unit 304, a rearrangement unit 306, a shared information management unit 308, a division rearrangement control unit 310, a lock control unit 312, a division. A file storage unit 314 and a distributed information storage unit 316 are included. The parent server program 30 is loaded into the memory 12 of the parent server 3 and executed by the CPU 10. Hereinafter, the programs shown are also executed in the same manner.

  In the parent server program 30, the request accepting unit 300 accepts requests such as new creation, reference, and deletion of files from the terminal device 5 via the network 2. When receiving a file reference request, the request receiving unit 300 outputs a request to the combining unit 302 and transmits the file data combined by the combining unit 302 to the requesting terminal device 5. When receiving a new file creation and storage request, the request receiving unit 300 outputs the file data to the dividing unit 304.

  The dividing unit 304 divides the file. The dividing unit 304 may store at least one of the divided files in the divided file storage unit 314. Further, the dividing unit 304 determines which child server 4-1 to 4-n each of the divided files is arranged, and the divided server and the child server 4- in which the file is stored. 1 to 4-n (hereinafter also referred to as shared information) is generated and output to the shared information management unit 308. The shared information is uniquely identified by the file name or file identifier of the pre-division file. The shared information will be described in detail later.

  The dividing unit 304 determines to which child server 4 the divided file is arranged based on a random number or the like. The dividing unit 304 may determine the arrangement based on the number of parent servers 3 and child servers 4 configuring the file management system 1, or may determine based on the file size. The file dividing method and the arranging method are not particularly limited to this example.

  The division unit 304 performs a file division process and a distribution information generation process when a division process is instructed by a division rearrangement control unit 310 described later. In this case, the dividing unit 304 acquires the currently stored shared information via the shared information management unit 308.

The divided file storage unit 314 stores the file divided by the dividing unit 304. This file is given an identifier for identifying the file before division. The divided file storage unit 314 is realized by at least one of the memory 12 and the storage device 14.
The shared information storage unit 316 stores the shared information of each file. The distributed information storage unit 316 is realized by the memory 12.

  The shared information management unit 308 stores the shared information input from the dividing unit 304 and identification information for identifying which file the shared information corresponds to in the shared information storage unit 316. Also, the shared information management unit 308 receives file identification information such as a file name (or file identifier) from the combining unit 302, the dividing unit 304, or the rearrangement unit 306, and extracts the shared information related to the file from the shared information storage unit 316. Then, the data is output to the combining unit 302 and the like.

  The shared information management unit 308 transmits the shared information stored in the shared information storage unit 316 to any of the child servers 4 when the parent server 3 on which the parent server program 30 operates stops. In this case, the shared information management unit 308 deletes the shared information stored in the shared information storage unit 316. When the parent server 3 is stopped, the shared information management unit 308 may delete the shared information stored in the shared information storage unit 316 after writing it to a file on the storage device 14, or may not be shown in FIG. The data may be deleted after being stored in the / O device.

  In this way, the parent server program 30 receives the file from the terminal device 5, divides the file, stores the divided file in the divided file storage unit 314, and stores the distributed information in the distributed information storage unit 316. . The divided file storage unit 314 may not be included in the parent server program 30 but may be included only in the child server program 40 described later. In this case, the information stored in the parent server 3 is only the distributed information.

  The combining unit 302 outputs identification information such as the file name of the file requested from the terminal device 5 to the shared information management unit 308 and receives the shared information of the file from the distributed information management unit 308. The combining unit 302 refers to the shared information, recognizes in which child server 4 each of the divided files obtained by dividing the requested file is stored, and sends the child server 4 storing the divided files to the child server 4 that stores the divided files. Request to send a split file. When the divided file is stored in the divided file storage unit 314 of the parent server program 30, the combining unit 302 extracts the divided file obtained by dividing the requested file from the divided file storage unit 314. The combining unit 302 combines each divided file transmitted from the child server 4 and the divided file stored in the divided file storage unit 314, and outputs the combined file to the request receiving unit 300.

  When the dividing unit 304 performs the shared information update process and the file dividing process, the rearrangement unit 306 refers to the shared information via the shared information management unit 308, receives the divided file from the dividing unit 304, and receives the shared information. Based on the above, each of the divided files is transmitted to the corresponding child server 4. Further, the rearrangement unit 306 has a relationship different from the shared information stored in the shared information storage unit 316 under the control of the division rearrangement control unit 310 to be described later, that is, the file is newly divided by the division unit 304. The newly divided divided files are rearranged in the plurality of child servers 4 in a relationship corresponding to the generated shared information. Note that the rearrangement unit 306 may transmit a notification of rearrangement to the child server 4, and the child server 4 may obtain (get) the divided file from the parent server 3.

  The division rearrangement control unit 310 controls the division unit 304 and the rearrangement unit 306 to execute the division process and the rearrangement process at a predetermined opportunity. For example, the division / relocation control unit 310 may cause the division / relocation processing to be executed at a predetermined interval such as every day, every week, every month, or at a predetermined time. May be executed. Further, the division / relocation control unit 310 may control the division / relocation processing for each file. In this case, the division / relocation control unit 310 may execute a division / relocation process by specifying a file corresponding to a predetermined file name or a file included in a predetermined directory (also referred to as a folder). Good. The division rearrangement process may be performed by a GUI (Graphical User Interface) using the UI device 18 of the parent server 3 or by a CLI (Comand Line Interface). Also, the execution target designation method such as the file name designation method is not particularly limited.

  The lock control unit 312 controls a state in which a file stored in a distributed manner on the parent server 3 and the child server 4 is prohibited from being referred to / updated from the terminal device 5 and a state in which the file is permitted. When the lock control unit 312 locks the reference or the like, the reference from the terminal device 5 is prohibited, and when the lock control unit 312 releases the lock, the reference or the like is permitted. For example, the lock control unit 312 prohibits reference to the file while the file division process or the rearrangement process is being executed.

FIG. 4 is a diagram for explaining distributed processing and rearrangement processing executed by the parent server program 30.
As illustrated in FIG. 4A, in the file management system 1, the file is divided into a plurality of files and distributed to a plurality of servers among the parent server 3 and the child servers 4-1 to 4-n. Stored. For example, when the file management system 1 includes two child servers 4-1 and 4-2, the “address book 01” file is divided into nine “address book 01-01” to “address book 01-09”. And distributed to three servers, a parent server 3 and child servers 4-1, 4-2.

  The file thus distributed and managed is divided and rearranged by the division rearrangement control unit 310 at a predetermined opportunity as illustrated in FIG. 4B. For example, a file that has been divided into nine parts is divided into fifteen parts and distributed to three servers.

FIG. 5 is a diagram illustrating shared information stored in the shared information storage unit 316.
As illustrated in FIG. 5, the distribution information includes a file name, a file sequence number, a current size, a new size, a current storage server ID, and a new storage server ID. The file name is a name for uniquely identifying a file that is distributed and managed. The shared information may include an identifier (file ID) for identifying the file separately from the file name.

  The file sequence number is a sequence number for identifying the divided file, and the divided file is uniquely identified by the file name and the file sequence number. The current size is the file size before the re-division process is executed. The new size is the file size after the re-division processing is executed. Note that the distribution information may include only the file size after the re-division processing is executed.

  The current storage server ID is the identifier (ID) of the server that stored the file before the relocation process is executed. The new storage server ID is an identifier of the server that stores the file after the rearrangement process is executed. Note that the distribution information may include only the file size after the rearrangement process is executed. Further, since the server ID is an identifier for uniquely identifying the server, the server ID may be a server name or a manufacturing number as long as it uniquely identifies the server.

  In this example, the file size of the file “Address Book 01” is 90 MB, and the file is re-divided from a state where it is divided into 9 into a state where it is divided into 15 parts. The divided file size is 10 MB before re-division and 6 MB after re-division. In each divided file, the server stored before re-division and the server stored after re-division may be the same or different.

  The coupling unit 302 of the parent server program 30 recognizes which child server 4 stores each divided file with reference to such distributed information. Further, the rearrangement unit 306 assigns a file sequence number for identifying the divided file to the divided file, and transmits the divided file to the child server 4 that is the storage destination.

FIG. 6 is a diagram showing a functional configuration of the child server program 40 operating on the child server 4.
As illustrated in FIG. 6, the child server program 40 includes a file request receiving unit 400, a divided file management unit 402, a distributed information management unit 404, a rearrangement request receiving unit 406, a divided file storage unit 314, and a distributed information storage unit 316. Have. 6 that are substantially the same as those shown in FIG. 3 are denoted by the same reference numerals.

  In the child server program 40, the file request receiving unit 400 receives requests from the combining unit 302 and the relocation unit 306 of the parent server program 30. When the file request accepting unit 400 accepts a file request from the combining unit 302 of the parent server program 30, the file request accepting unit 400 outputs the file name (or an identifier such as a file ID) of the file to the divided file managing unit 402. The corresponding divided file is received from the file management unit 402 and the divided file is transmitted to the parent server 3. When the file request receiving unit 400 receives the substance of the divided file from the rearrangement unit 306 of the parent server program 30, the file request receiving unit 400 outputs the divided file to the divided file management unit 402.

  The divided file management unit 402 manages the divided files stored in the divided file storage unit 314. More specifically, the divided file management unit 402 extracts the divided file related to the file specified from the file request receiving unit 400 from the divided file storage unit 314 and outputs the extracted file to the file request receiving unit 400. Further, the divided file management unit 402 receives the divided file from the file request receiving unit 400 and stores it in the divided file storage unit 314. Since the file name and the file order number before division are assigned to the divided file, the divided file is uniquely identified.

  The split file management unit 402 also extracts the split file related to the file specified from the rearrangement request reception unit 406 from the split file storage unit 314 and outputs it to the rearrangement request reception unit 406. When the relocation request accepting unit 406 receives a relocation request from the relocation unit 306 of the parent server program 30, the relocation request receiving unit 406 acquires the relocation target divided file via the divided file management unit 402 and sends it to the parent server 3. Send to.

  When the shared information is received from the shared information management unit 308 of the parent server program 30, such as when the parent server 3 is stopped, the shared information management unit 404 stores the shared information in the shared information storage unit 316. When the parent server 3 is restarted, the shared information management unit 404 acquires the shared information from the shared information storage unit 316 and transmits it to the parent server 3 and deletes the shared information from the shared information storage unit 316. . When the child server 4 is stopped while the parent server 3 is stopped, if the child server 4 stores the distributed information, the distributed information management unit 404 distributes to the other child servers 4. Information is transmitted, and the shared information is deleted from the shared information storage unit 316. In this case, in the other child server 4, the shared information management unit 404 of the child server program 40 stores the received shared information in the shared information storage unit 316.

Next, file storage processing, file reference processing, and relocation processing performed in the file management system 1 according to the embodiment of the present invention will be described.
FIG. 7 is a diagram showing a flowchart of the file saving process (S10) in the file management system 1 according to the embodiment of the present invention.
As shown in FIG. 7, in step 100 (S <b> 100), the request receiving unit 300 of the parent server program 30 (FIG. 3) determines whether a file storage request has been received from the terminal device 5. The parent server program 30 proceeds to the process of S102 when the file saving request is received, and returns to the process of S100 otherwise.

In step 102 (S102), the dividing unit 304 generates shared information regarding the file to be saved, and stores the shared information in the shared information storage unit 316 via the shared information management unit 308.
In step 104 (S104), the dividing unit 304 divides the storage target file into a predetermined number for each predetermined file size based on the shared information.

  In step 106 (S106), the rearrangement unit 306 transmits each of the divided files to the corresponding child server 4 based on the shared information. The transmitted divided file is deleted from the parent server 3. When the parent server 3 stores the divided file, the dividing unit 304 stores the divided file in the divided file storage unit 314 based on the distribution information. In each child server 4, the file request reception unit 400 of the child server program 40 (FIG. 6) receives the transmitted divided file and stores it in the divided file storage unit 314 via the divided file management unit 402.

FIG. 8 is a diagram showing a flowchart of the file reference process (S20) in the file management system 1 according to the embodiment of the present invention.
As shown in FIG. 8, in step 200 (S <b> 200), the request receiving unit 300 of the parent server program 30 determines whether a file reference request is received from the terminal device 5. If the parent server program 30 receives a file reference request, the parent server program 30 proceeds to the process of S202, and otherwise returns to the process of S200.

In step 202 (S202), the combining unit 302 refers to the shared information stored in the shared information storage unit 316 and related to the reference target file via the shared information management unit 308.
In step 204 (S204), the combining unit 302 collects divided files based on the shared information. More specifically, the combining unit 302 acquires the divided file related to the file stored in the divided file storage unit 314, and assigns the identifier (file name, file ID, etc.) of the file to each child server 4. And the corresponding divided file is received from the child server 4.

In step 206 (S206), the combining unit 302 combines and restores the files based on the collected file order numbers of the divided files, and outputs them to the file request receiving unit 400.
In step 208 (S208), the file request receiving unit 400 transmits the restored file to the requesting terminal device 5. The transmitted file is deleted from the parent server 3.

FIG. 9 is a diagram showing a flowchart of the relocation processing (S30) in the file management system 1 according to the embodiment of the present invention. Note that, among the processes shown in FIG. 9, substantially the same processes as those shown in FIGS. 7 and 8 are denoted by the same reference numerals.
As shown in FIG. 9, in step 300 (S300), the division rearrangement control unit 310 of the parent server program 30 determines whether or not it is an opportunity for rearrangement. The parent server program 30 proceeds to the process of S202 if it is an opportunity for rearrangement, and returns to the process of S300 otherwise.

  When it is determined that the relocation is triggered, the division / relocation control unit 310 outputs to the combining unit 302, the division unit 304, and the relocation unit 306 that the division / relocation processing is to be executed. Therefore, in the processes of S202 to S206, the combining unit 302 collects the divided files based on the stored shared information, combines the divided files, and restores the files before the division. Thereafter, in the processes of S102 and S104, the dividing unit 304 generates shared information indicating a relationship different from the stored shared information, and divides the file based on the generated distributed information. Further, in the process of S106, the relocation unit 306 transmits the divided file to the child server 4 based on the generated distribution information. Each child server 4 stores the transmitted divided file, and the parent server 3 deletes the transmitted divided file.

  As described above, the file management system 1 according to the embodiment of the present invention is a file management system having a parent server and a plurality of child servers, and the parent server includes a dividing unit that divides a file, A file having relation storage means for storing relation information between the file divided by the dividing means and the child server storing the file, wherein the child server stores the file divided by the dividing means; Having storage means; Thereby, since the storage location of the divided file is not known by the user, it is possible to prevent the file from being illegally taken out. Further, even when any one of the divided files is illegally obtained, the contents of the entire file are prevented from being specified, so that substantial damage can be minimized. Since the user does not need to individually access a plurality of servers that store the divided files, the convenience for the user is improved.

  Further, the file management system 1 according to the embodiment of the present invention relocates the divided files divided by the dividing unit to the plurality of child servers in a relationship different from the relationship information stored in the relationship storage unit. And repositioning means. As a result, the divided file is divided and arranged again at a predetermined opportunity, so that it is more difficult for the user to access each of the divided files.

  Furthermore, the file management system 1 according to the embodiment of the present invention stores distributed information in a memory composed of a semiconductor storage device. As a result, users such as developers and file viewers cannot refer to the distributed information by the operation of accessing the file, and cannot know the storage location of the file. Can be prevented.

  In the file management system 1 according to the embodiment of the present invention, each of the parent server 3 and the child servers 4-1 to 4-n may constitute a so-called hot standby configuration. For example, the hot standby machine of the parent server 3 is the child server 4-1, the hot standby machine of the child server 4-2 is the child server 4-2, and the hot standby machine of the child server 4-n is the parent server 4-2. Server 3. In this case, when one of the servers stops, the hot standby machine of the stopped machine detects this, and takes over the function of the stopped machine either automatically or manually. In this case, the stopped machine transmits the stored distributed information and divided files to the corresponding hot standby machine immediately before stopping.

  In the file management system 1 according to the embodiment of the present invention, when all of the parent server 3 and the child servers 4-1 to 4-n are stopped, the distributed information is erased because it is stored in the volatile memory. The Therefore, when the parent server 3 and the child servers 4-1 to 4-n are activated again, the parent server 3 collects the divided files and reconstructs the distributed information.

  Also, it is assumed that somebody logs on illegally directly to the child server 4, acquires a divided file, and destroys a system file. Therefore, in the file management system 1, measures such as setting the logon port of the child server 4 to Disable and stopping the logon function may be taken. Even in this case, since data can be transmitted and received between the parent server 3 and the child server 4, the user can refer to and save the file.

  Further, the file management system 1 may adopt a configuration in which the network connecting the terminal device 5 and the parent server 3 and the network connecting the parent server 3 and the child server 4 are different networks. Thereby, unauthorized access from the terminal device 5 to the child server 4 via the network can be prevented.

1 is a diagram showing a file management system 1 according to an embodiment of the present invention. It is a figure which shows the hardware constitutions of the parent server 3, the child server 4, and the terminal device 5. 3 is a diagram showing a functional configuration of a parent server program 30 that operates on the parent server 3. FIG. It is a figure explaining the distributed process and the rearrangement process which are performed by the parent server program. It is a figure which illustrates the shared information memorize | stored in the shared information storage part. It is a figure which shows the function structure of the child server program 40 which operate | moves on the child server 4. FIG. It is a figure which shows the flowchart of the file preservation | save process (S10) in the file management system 1 which concerns on embodiment of this invention. It is a figure which shows the flowchart of the file reference process (S20) in the file management system 1 which concerns on embodiment of this invention. It is a figure which shows the flowchart of the rearrangement process (S30) in the file management system 1 which concerns on embodiment of this invention.

Explanation of symbols

1 File management system 2 Network 3 Parent server 4 Child server 5 Terminal device 10 CPU
12 Memory 14 Storage device 16 Communication IF
18 UI device 30 Parent server program 40 Child server program 300 Request reception unit 302 Connection unit 304 Division unit 306 Relocation unit 308 Distributed information management unit 310 Division rearrangement control unit 312 Lock control unit 314 Division file storage unit 316 Distribution information storage unit 400 File request reception unit 402 Division file management unit 404 Distributed information management unit 406 Relocation request reception unit

Claims (6)

A file management system having a parent server and a plurality of child servers,
The parent server is
A dividing means for dividing the file;
Relationship storage means for storing relationship information between the file divided by the dividing means and the child server in which the file is stored;
The file management system, wherein the child server has file storage means for storing the file divided by the dividing means. The file management system according to claim 1, wherein the relation storage unit includes a semiconductor storage device. The parent server is
A request accepting means for accepting a request for a file;
A combining unit that combines the divided files stored in the file storage unit of the plurality of child servers based on the request received by the request reception unit and the relationship information stored in the relationship storage unit; The file management system according to claim 1, further comprising: 4. The apparatus according to claim 1, further comprising a rearrangement unit that rearranges the divided files divided by the division unit to the plurality of child servers in a relationship different from the relationship information stored in the relationship storage unit. File management system described in. In a file management system having a parent server having a storage device and a plurality of child servers,
In the parent server,
Split the file,
Storing relationship information between the divided file and the child server storing the file in the storage device;
A file management method for storing the divided files in the child server. In the parent server,
Accept file requests,
The file management method according to claim 5, wherein the divided files stored in the plurality of child servers are combined based on the received request and the stored relationship information.

Images