WO2008010473A1

WO2008010473A1 - Distributed file managing system

Info

Publication number: WO2008010473A1
Application number: PCT/JP2007/064057
Authority: WO
Inventors: Naoki Hayashi; Takashi Hayashi; Mana Aizawa
Original assignee: Panasonic Corporation
Priority date: 2006-07-19
Filing date: 2007-07-17
Publication date: 2008-01-24
Also published as: JP2009259265A; JPWO2008010473A1

Abstract

Provided is a distributed file managing system capable of providing an electronic file held by one of servers to a user who accesses an arbitrary server from the terminal used by the user. The distributed file managing system manages electronic files held by a plurality of servers. The distributed file managing system includes a terminal connected by a communication line and used by a user, a plurality of servers for receiving a user request, and a distributed file managing device for identifying a server holding the electronic file associated with the user request in accordance with an inquiry from the server and causing each of the servers to execute processes required for the request.

Description

Specification

Distributed file management system

Technical field

The present invention relates to a system for managing electronic files distributed on a computer network (hereinafter referred to as “network”).

Background art

[0002] A user who uses a terminal connected to a network via a network such as a LAN (Local Area Network) in an organization such as a company or a Wan (Wide Area Network) such as the Internet is connected to the network. You can access the electronic files held by the server. This makes it possible for users to browse or download electronic files that are distributed and stored on servers connected to the network, thereby promoting the distribution and use of information.

[0003] Conventionally, techniques for utilizing and managing electronic files that are distributed and held on a network in this way have been proposed.

[0004] For example, the technology described in Patent Document 1 is a file system management method that presents a virtual file system having a tree structure with a super directory at the top of the file system of each server as a vertex. . According to this technology, the user can access the electronic file held by the server from the same user interface as when accessing the electronic file held by the terminal used by the user.

[0005] Further, the technology described in Patent Document 2 does not share one electronic file held by each server with each terminal connected to the network. It is a mechanism or method that keeps electronic file groups redundantly, and completely synchronizes the contents of electronic files or electronic file groups that are held between servers.

Patent Document 1: Japanese Patent Laid-Open No. 5-250249

Patent Document 2: Japanese Patent Publication No. 10-510413

Disclosure of the invention Problems to be solved by the invention

However, the technique described in Patent Document 1 has a problem that the electronic file acquired by the user is not always the electronic file having the latest contents.

[0007] Since the technique described in Patent Document 1 does not disclose a technique for synchronizing electronic files distributed on a network, for example, an electronic file with the same name held by a plurality of servers. The contents of may differ.

[0008] With the technique described in Patent Document 2, each electronic file held by a plurality of servers is synchronized. However, all servers have the same electronic file group, and in order to synchronize each electronic file, when updating the content of the electronic file, The file needs to be updated. Therefore, there is a problem that network traffic increases at the time of update. This problem becomes more pronounced as the number of servers increases.

[0009] The present invention has been made to solve the above problem, and an electronic file desired by a user is held in any of a plurality of servers by accessing an arbitrary server from a terminal used by the user. The purpose is to provide a distributed file management system that makes it possible to provide the latest electronic files to users. It is another object of the present invention to provide a distributed file management system that can suppress the load on the network that is applied to achieve the above-mentioned purpose.

Means for solving the problem

[0010] In order to achieve the above object, a distributed file management system according to the present invention is a distributed file management system that manages electronic files held by a plurality of servers, and the distributed file management system includes: The plurality of servers connected by communication lines, terminals used by users, and a distributed file management device, and the distributed file management device receives a user request related to an electronic file. When the access source server receives a request for the terminal to obtain an electronic file containing a user-specified identifier, which is the holding server that is the server that holds the latest electronic file containing the identifier Inquiries are received from the access source Sano and the server that holds the latest electronic file. Information indicating whether there is When the inquiry is received by the holding server storage means and the inquiry receiving means that store the file holding information as described above, the holding server can be detected by referring to the file holding information. A holding server judging means for judging whether there is a file transmission request, which is a request for sending an electronic file including the user-specified identifier to the access source server, is judged by the holding server judging means to be a holding server; File transmission request means for transmitting to the server.

As described above, when the distributed file management apparatus receives an inquiry from the access source Sano,

The server that holds the latest electronic file and the server that holds the electronic file according to the user's request are determined based on the information indicating whether the server is out of place. Therefore, even if a user is connected via a terminal power network that he / she uses and accesses a deviation of a plurality of servers, at least one of the plurality of servers holds an electronic file desired by the user. As long as it is available, the latest electronic file according to the user's request can be obtained from the terminal. Therefore, the user does not need to be aware of whether or not the electronic file is the latest power and the server accessed from the terminal, and the user who is involved in the acquisition of the electronic file distributed and held on a plurality of servers on the network. Convenience can be improved.

[0012] When updating an electronic file held by each server, one of the servers holds the electronic file according to the user's request without performing processing for synchronizing the electronic file. As long as the terminal can obtain the latest electronic file according to the user's request. Therefore, it is possible to reduce the amount of information transferred over the network when updating an electronic file, and to reduce the load on each server.

[0013] Preferably, the holding server storage unit associates the server, the identifier of the electronic file, and a flag indicating whether or not the power is the latest in the electronic file group including the same identifier. The file holding information that is information is stored, and the holding server determining means refers to the file holding information, and associates it with the identifier specified by the user and the flag indicating the latest. A server is determined as the holding server

In this way, the distributed file management device has the same identifier as the server and the electronic file. It holds file holding information including information that associates the flag indicating whether or not it is the latest in the electronic file group including the identifier, and if an inquiry is received from the access source Sano, Based on the file holding information, the holding server for the electronic file according to the user's request is determined. Therefore, even if a user is connected via the terminal power network that he or she uses !, even if the misalignment of multiple servers is accessed, at least one of the multiple servers holds the electronic file desired by the user. Thus, as long as the latest electronic file according to the user's request can be obtained from the terminal. Therefore, the user does not need to be aware of whether the electronic file is up-to-date or not and the power of the terminal, and the user involved in obtaining the electronic file distributed and held on multiple servers on the network. It becomes possible to improve the convenience.

[0015] Also, when updating the electronic file held by each server, one of the servers holds the electronic file according to the user's request without performing processing for synchronizing the electronic file. As long as the terminal can obtain the latest electronic file according to the user's request. Therefore, it is possible to reduce the amount of information transferred over the network when updating an electronic file, and to reduce the load on each server.

[0016] More preferably, each server includes a file storage unit that stores an electronic file, a file transmission request receiving unit that receives the file transmission request transmitted by the file transmission request unit, and the file transmission request. File storage control means for reading out the electronic file from the file storage means, and file transmission means for acquiring the electronic file read by the file storage control means and transmitting the acquired electronic file to the access source server With.

[0017] In this way, the access source server acquires the electronic file related to the user's request from the holding server. As a result, the access source server can transmit the electronic file according to the user's request to the terminal used by the user.

[0018] More preferably, the file transmission means of another server further comprises file reception means for receiving the transmitted electronic file, and the file storage control means further includes the electronic file received by the file reception means. Is written in the file storage means.

Thus, the access source server holds the electronic file according to the user's request! / If not, the electronic file is acquired from the holding sano and held by itself. As a result, when a request for acquiring the same electronic file from any of the terminals is received again, the electronic file held by itself can be transmitted. For this reason, it is not necessary for the access source server to acquire again from the holding server for the electronic file acquired via one access source server, and the amount of information transferred over the network can be reduced. The load on each server can be reduced.

[0020] More preferably, each of the servers further includes a difference between information stored in the file storage unit before and after writing when the file storage control unit writes an electronic file in the file storage unit. Update notification means for notifying the distributed file management apparatus, and the distributed file management apparatus is included in the update notification reception means for receiving notification by the update notification means and the notification received by the update notification reception means. And holding information updating means for updating the file holding information based on the difference.

[0021] Further, the update notification means receives a request for the terminal to acquire an electronic file including a user-specified identifier, and the access source server holds the electronic file related to the acquisition request. In the case of reaching the above, the distributed file management device is notified of the electronic file identifier related to the acquisition request as the difference, and the update notification receiving unit receives the notification from the update notification unit, and updates the stored information The means associates the information indicating the access source server, the identifier of the electronic file included in the difference, and the flag indicating the latest according to the notification received by the update notification receiving means. The file holding information is updated by adding information.

[0022] Furthermore, the update notification means receives a write request, which is a request for holding the electronic file in the server, and the access source server holds the electronic file related to the write request. The distribution file management device is notified of the difference between the identifier of the electronic file related to the write request and the information indicating the retention based on the write request as the difference, and the update notification The accepting unit receives a notification from the update notifying unit, and the holding information updating unit has a server associated with the identifier included in the difference according to the notification accepted by the update notification accepting unit. And changing the flag corresponding to the server to a flag indicating that it is not the latest In addition, the file holding information is updated by adding information in which the information indicating the access source server is associated with the identifier included in the difference and the flag indicating the latest.

As described above, the file holding information held by the distributed file management apparatus is updated.

As a result, the latest state of the electronic file held by each server can be automatically stored in the file holding information.

[0024] More preferably, each of the servers further includes: a user request receiving unit that receives a user request related to an electronic file from the terminal; and the user request received by the user request receiving unit. Request type determination for determining whether the acquisition request, which is a request for the terminal to acquire an electronic file including a user-specified identifier, is a! / Contrast between a write request, which is a request for holding the electronic file in the server And a holding server inquiry means for inquiring of the distributed file management apparatus which electronic file holding server is related to the acquisition request when the request type determination means determines that the acquisition request is made. The inquiry accepting unit receives the electronic file related to the acquisition request from the holding server inquiry unit included in the access source server that received the acquisition request. Equity server mosquito ^, accepts a ヽ U inquiry as if it were a shift.

[0025] Further, the file storage control means further selects an electronic file related to the write request received by the user request reception means when the request type determination unit determines that the request is a write request. Write to file storage means.

In this way, the access source server makes an inquiry related to the user request to the distributed file management apparatus or executes its own process in response to the user request. This makes it possible to reduce the load on the distributed file management device.

[0027] More preferably, each of the servers further excludes processing related to writing of the electronic file related to the write request when the request type determining unit determines that the request is the write request. Lock request transmitting means for transmitting a request for locking to be released and a request for releasing the lock to the distributed file management device, and the distributed file management device further identifies an electronic file to be checked. Lock information holding means for holding lock information, which is information, and the lock request or unlock request from the lock request transmitting means. If the lock request is received, the lock information related to the lock request is held in the lock information holding means, and if the lock release request is received, the lock release request is A lock request receiving unit that deletes the lock information from the lock information holding unit, and the holding information update unit includes the difference between the electronic file indicated by the lock information and the notification received by the update notification receiving unit. If the electronic file indicated by is identical, the file holding information is updated after the lock information held by the lock information holding means is deleted.

[0028] As described above, by performing the lock process, the content of the file holding information held by the distributed file management device and the latest state of the electronic file held by each server can be prevented from being eaten or discriminated. It becomes possible to do.

[0029] In order to achieve the above object, a distributed file management system according to the present invention is a distributed file management system that manages electronic files held by a plurality of servers, and the distributed file management system includes: It is composed of the plurality of servers, terminals used by users, and a distributed file management device connected by a communication line. The distributed file management device is a server server that holds electronic files. When a plurality of servers hold electronic files having the same identifier with reference to the file holding information and holding server storage means for storing file holding information which is information indicating Deletion target judging means for judging whether or not to delete each electronic file so that the electronic file held by at least one of the servers remains. And a deletion request transmitting means for transmitting a request for deleting the electronic file to a server holding the electronic file determined to be deleted by the deletion target determining means.

[0030] Thus, when the distributed file management apparatus receives an inquiry from the access source Sano, the distributed file management apparatus, based on the information indicating which server holds the electronic file, holds the electronic file related to the user's request. Judging. For this reason, even if a user accesses a misalignment of a plurality of servers connected via a terminal power network used by the user, at least one of the plurality of servers maintains an electronic file desired by the user. As long as the user has the electronic file according to the user's request, the terminal capability can be acquired. Therefore, the user also accesses whether the electronic file is up-to-date and terminal power There is no need to be conscious of the server, and it is possible to improve the convenience of the user related to the acquisition of electronic files distributed and held in multiple servers on the network.

[0031] When updating an electronic file held by each server, it is possible to synchronize electronic files having the same identifier held redundantly by some servers. The electronic files that are held in duplicate are not necessarily all of the multiple servers. Therefore, when all of the servers hold all of the electronic files in duplicate, the files are updated on the network when the electronic files are updated. It is possible to reduce the amount of information transferred and reduce the load on each server. When electronic files including the same identifier are synchronized, the user can obtain the latest electronic file at the terminal.

[0032] Further, at least one of the electronic files held in duplicate is deleted.

This makes it possible to reduce the consumption of storage resources for each server to hold electronic files.

[0033] More preferably, the holding server storage means includes the server, an identifier of the electronic file, and a last access date that is a date when the user's request related to the electronic file held by the server is last received. The file retention information that is the associated information is stored, and the deletion target determination means refers to the file retention information, and the plurality of servers retain the same electronic file, and the plurality of servers retain the electronic files. Whether or not to delete each electronic file so that the electronic file with the latest access date is the newest when any of the files has also passed the predetermined period of the last access date. Determine whether.

[0034] Further, the holding server storage means associates the server, the identifier of the electronic file, and a flag indicating whether or not the latest in the electronic file group including the same identifier. The deletion target judging means refers to the file holding information, and a plurality of servers hold electronic files including the same identifier, and an electronic device including the same identifier is stored. Each electronic file is deleted so that only the electronic file associated with the flag indicating the latest contents is left when the flag indicating that it is not the latest is associated with any of the files Power to do Determine whether.

[0035] Further, when the plurality of servers hold an electronic file including the same identifier, the deletion target determining unit leaves the electronic file held by at least one of the plurality of servers. In addition, it is periodically determined whether or not each electronic file is to be deleted.

[0036] Further, the distributed file management apparatus further receives a write request which is a request for an access source server, which is a server that has received a user request related to an electronic file, to hold the electronic file in the server. In this case, a query accepting means for accepting from the access source server whether or not a server error that holds an electronic file including an electronic file that includes the same identifier as the electronic file related to the write request; The deletion target judging means refers to the file holding information when the inquiry receiving means receives an inquiry based on the write request, and a plurality of servers hold electronic files including the same identifier. In this case, the electronic server deletes each electronic file so that only the electronic file retained by the access source server receiving the write request is left. Judge whether or not it is correct.

[0037] In this manner, at least one electronic file held redundantly is deleted, periodically or when a write request is received. This makes it possible to effectively use storage resources consumed by each server to hold electronic files.

[0038] More preferably, in the distributed file management apparatus, the terminal further obtains an electronic file including an identifier specified by a user, which is an access source server that has received a user request related to the electronic file. When receiving an inquiry, an inquiry receiving unit that receives from the access source server an inquiry as to which holding server is the server that holds the electronic file related to the acquisition request, and the inquiry receiving unit receives the inquiry. When an inquiry based on an acquisition request is received, a holding server determination unit that determines the holding server by referring to the file holding information, and the holding server determination unit determines that the server is a holding server. The electronic file containing the user-specified identifier is transmitted to the access source server. The file I le transmission request is determined, and a file transmission request means for transmitting to have been servers determined to be holding server by the holding server determination means. [0039] Each server stores a file storage means for storing an electronic file !, a file transmission request receiving means for receiving the file transmission request transmitted by the file transmission request means, The file storage control means for reading out the electronic file related to the file transmission request and the electronic file read by the file storage control means are acquired, and the acquired electronic file is stored in the access source server. File transmission means for transmitting.

[0040] Furthermore, each of the servers further includes file receiving means for receiving an electronic file transmitted from the file transmitting means of another server, and the file storage control means is further configured to include the file receiving means. The received electronic file is written into the file storage means.

[0041] Thus, the access source server holds the electronic file according to the user's request! Otherwise, the electronic file is obtained from the holding sano and held by itself. As a result, when a request for acquiring the same electronic file from any of the terminals is received again, the electronic file held by itself can be transmitted. For this reason, it is not necessary for the access source server to acquire again from the holding server for the electronic file acquired via one access source server, and the amount of information transferred over the network can be reduced. The load on each server can be reduced.

[0042] More preferably, the distributed file management device further includes a clock unit that holds a current date and time, and the holding server determination unit that determines that the access source server is a holding server. First holding information updating means for updating the last access date included in the file holding information associated with the access source server and the identifier specified by the user according to the date held by the clock means.

[0043] Further, each of the servers further updates to notify the distributed file management device of the difference between the file storage means before and after the writing when the file storage control means writes an electronic file in the file storage means. The distributed file management device updates the file holding information by the update notification receiving means for receiving a notification from the update notification means and the difference included in the notification received by the update notification receiving means. Second holding information updating means. [0044] Further, the distributed file management device further includes a clock unit that holds the current date and time, and the update notification unit accesses the request for the terminal to acquire an electronic file including a user-specified identifier. When the original server receives and the access source server holds the electronic file related to the acquisition request, the identifier of the electronic file related to the acquisition request is stored in the distributed file management apparatus as the difference. The update notification receiving means receives a notification from the update notification means, and the second holding information update means receives information indicating the access source server in accordance with the notification received by the update notification receiving means. By adding information in which the identifier of the electronic file included in the difference is associated with the date acquired from the clock unit as the last access date, To update the serial Huai Le retention information.

[0045] Further, the update notification means receives a request for the terminal to acquire an electronic file including a user-specified identifier, and the access source server holds the electronic file related to the acquisition request. In the case of reaching the above, the distributed file management apparatus is notified of the electronic file identifier related to the acquisition request as the difference, and the update notification receiving means receives the notification from the update notification means, and the second In response to the notification received by the update notification receiving unit, the retained information update unit includes information indicating the access source server, an identifier of the electronic file included in the difference, and the flag indicating the latest. The file holding information is updated by adding the associated information.

[0046] Further, the distributed file management device further includes a clock unit that holds the current date and time, and the update notification unit issues a write request that is a request to hold the electronic file to the server. When the server receives and the access source server holds the electronic file related to the write request, it is the hold based on the identifier of the electronic file related to the write request and the write request. To the distributed file management device as the difference, the update notification receiving means receives a notification from the update notification means, and the second held information update means receives the update notification. According to the notification received by the means, the information indicating the access source server, the identifier included in the difference, and the date acquired from the clock unit as the last access date are associated By broadcast, The file holding information is updated.

[0047] Further, the update notification means receives a write request, which is a request for causing the server to hold an electronic file, and the access source server holds the electronic file related to the write request. The distribution file management device is notified of, as the difference, the identifier of the electronic file related to the write request and the information indicating the retention based on the write request, and the update notification The accepting unit receives a notification from the update notifying unit, and the second holding information updating unit is a server associated with the identifier included in the difference according to the notification accepted by the update notification accepting unit. If there is, the flag corresponding to the server is changed to a flag indicating that it is not the latest, and the information indicating the access source server and the difference are included in the difference And Besshi, by adding information that associates with the flag indicating a date, updating the file I le holds information.

In this manner, the file holding information held by the distributed file management apparatus is updated.

As a result, the latest correctness and status of the electronic file held by each server can be automatically stored in the file holding information.

In order to achieve the above object, a distributed file management system according to the present invention is a distributed file management system that manages electronic files held by a plurality of servers, and the distributed file management system includes: The plurality of servers connected by communication lines, terminals used by users, and a distributed file management device, and the distributed file management device receives a user request related to an electronic file. If the access source server receives a request for the terminal to obtain an electronic file containing a user-specified identifier, the holding server is a server that holds a genuine electronic file created by an authorized person including the identifier Inquiry means for accepting an inquiry from the access source server and an electronic file are stored. By referring to the file holding information when the inquiry receiving means receives the inquiry, the holding server storage means that stores file holding information that is information indicating which server is to be executed, Holding server determining means for determining which of the holding servers is, and transmitting an electronic file including the user-specified identifier to the access source server File transmission request means for transmitting a file transmission request, which is a request, to a server determined to be a holding server by the holding server determination means.

[0050] Further, the holding server storage unit stores file holding information which is information in which the server, the identifier of the electronic file, and the hash value of the electronic file are associated with each other, and the holding server determination unit includes When the inquiry accepting means accepts the inquiry, the file holding information is referred to, and the hash value of the electronic file held by the server associated with the user-specified identifier is acquired. Thus, if the hash value associated with the user-specified identifier matches the acquired hash value, the server associated with the user-specified identifier is determined to be a holding server.

As described above, when the distributed file management apparatus receives an inquiry from the access source sano, the distributed file management apparatus, based on the information indicating which server holds the electronic file, holds the electronic file related to the user's request. Judging. For this reason, even if a user accesses a misalignment of a plurality of servers connected via a terminal power network used by the user, at least one of the plurality of servers maintains an electronic file desired by the user. As long as the user has the electronic file according to the user's request, the terminal capability can be acquired. Therefore, the user does not need to be aware of whether the electronic file has the latest power or the terminal power, and the user's access to the electronic file distributed and held on multiple servers on the network is eliminated. Convenience can be improved.

[0052] When updating an electronic file held by each server, it is possible to synchronize electronic files having the same identifier held in duplicate by some servers. The electronic files that are held in duplicate are not necessarily all of the multiple servers. Therefore, when all of the servers hold all of the electronic files in duplicate, the files are updated on the network when the electronic files are updated. It is possible to reduce the amount of information transferred and reduce the load on each server. When electronic files including the same identifier are synchronized, the user can obtain the latest electronic file at the terminal.

[0053] It is possible to detect falsification of an electronic file and transmit only a genuine electronic file to the user, and it is possible to improve the reliability of the distributed file management system. [0054] More preferably, the holding server determination unit holds an electronic file including an identifier specified by the user by referring to the file holding information when the inquiry receiving unit receives the inquiry. A first determination unit for determining a server, and a hash value of the electronic file held by the server determined to hold an electronic file by the first determination unit, and the hash value and the file A second determination unit that determines that the server determined to hold the electronic file by the first determination unit is a holding server when the hash value included in the holding information matches the second determination unit, and Furthermore, the distributed file management apparatus receives the inquiry from the inquiry accepting unit, and the server that is determined to hold the electronic file by the first determination unit is sent to the server. A hash value requesting unit that requests a hash value of the electronic file held by the server, and a hash value requesting unit that receives the hash value of the electronic file related to the request from the server that transmitted the request. And a hash value request receiving means for receiving a request for a hash value of a specific electronic file from the hash value requesting means. A hash value calculation means for obtaining the specific electronic file included in the request received by the hash value request receiving means from the file storage means and calculating a hash value of the specific electronic file; and the hash value Hash value transmitting means for transmitting the hash value calculated by the calculating means to the hash value receiving unit.

In this way, each server holds, calculates the hash value of the electronic file, and transmits the calculated hash value to the distributed file management apparatus. As a result, the distributed file management apparatus can acquire the hash value of the electronic file actually held by the server, and verify that the electronic file held by the server has been tampered with. It becomes possible to do.

[0056] More preferably, the inquiry accepting unit further relates to the write request from an access source server that is a server that has received a request to write an electronic file to a file storage unit included in the access source server. An inquiry about which server holds an electronic file is received, and the holding server determination unit refers to the file holding information when the inquiry receiving unit further receives an inquiry based on the write request. From this, it is determined which server holds an electronic file including the same identifier as that of the electronic file related to the write request, and the distributed file management device further determines the electronic file by the holding server determination means. When it is determined that there is no server to hold, the value indicating the free state of the file storage means provided for storing the electronic file in each server is the largest. The server is determined and the value indicating the free state is the largest. A copy destination determination unit that determines that the server is a server that holds a copy of the electronic file related to the write request, and a server that is determined to hold a copy by the copy destination determination unit according to the write request to the server A copy destination transmission unit for transmitting the electronic file to the access source server is provided.

[0057] Further, the copy destination determination unit is a file storage provided for each server to store an electronic file when the holding server determination means determines that there is no server holding the electronic file! The server having the largest ratio of the free capacity to the total capacity of the means is determined, and the server having the largest ratio is determined as the server that holds the duplicate of the electronic file related to the write request.

[0058] Further, the copy destination determination unit is a file storage provided for each server to store an electronic file when the holding server determination means determines that there is no server holding the electronic file! The server with the largest available capacity is determined, and the server with the largest available capacity is determined as the server that holds the copy of the electronic file related to the write request.

As described above, when the electronic file related to the write request does not hold the server of the deviation and is not a new electronic file, the electronic file is also held by a server other than the access source server. Therefore, even when any one of the servers stops operating, the electronic file held by that server can be transmitted to the terminal used by the user.

[0060] Further, since the servers other than the access source server that holds the electronic file are determined according to the state of the free capacity of the part that stores the electronic file, the storage resources of each server are evenly distributed. It is possible to distribute the load on the server.

[0061] More preferably, each of the servers is an electronic file transmitted by the file transmission request unit. A file transmission request receiving means for receiving a file transmission request including an aisle identifier, a file storage control means for reading out an electronic file including an identifier included in the file transmission request from the file storage means, and the file storage control means. File transmission means for acquiring the read electronic file and transmitting the acquired electronic file to the access source server.

[0062] Each of the servers further includes a file receiving unit that receives an electronic file transmitted from the file transmitting unit of another server, and the file storage control unit is further received by the file receiving unit. The electronic file is written into the file storage means.

Thus, the access source server holds the electronic file according to the user request! Otherwise, the electronic file is obtained from the holding sano and held by itself. As a result, when a request for acquiring the same electronic file from any of the terminals is received again, the electronic file held by itself can be transmitted. For this reason, it is not necessary for the access source server to acquire again from the holding server for the electronic file acquired via one access source server, and the amount of information transferred over the network can be reduced. The load on each server can be reduced.

[0064] More preferably, each of the servers further, when the file storage control means writes an electronic file in the file storage means, sends the difference of the file storage means before and after writing to the distributed file management device. An update notification means for notifying, and the distributed file management device determines the file holding information based on the difference included in the notification received by the update notification reception means and the notification received by the update notification reception means. Holding information updating means for updating.

[0065] In addition, the update notification unit is included in the file storage unit included in the access source server when the access source server accepts a request for the terminal to acquire an electronic file including a user-specified identifier. When the electronic file related to the request is written, the identifier of the electronic file related to the acquisition request is notified to the distributed file management device as the difference, and the update notification receiving means notifies the update notification means of the notification. In response to the notification received by the update notification receiving means, The file holding information is updated by adding information in which the information indicating the access source server is associated with the identifier of the electronic file included in the difference.

[0066] Further, the update notifying unit receives the request for writing the electronic file in the file storage unit provided in the access source server, and the update notification unit receives the request from the file storage unit provided in the access source server. When the electronic file related to the request is written, the identifier and hash value of the electronic file related to the write request are notified to the distributed file management device as the difference, and the update notification receiving means In response to the notification by the update notification means, the retained information update means receives the information including the hash value in the difference received by the update notification reception means, and information indicating the access source server and the difference By adding the identifier of the electronic file included and the hash value of the electronic file included in the difference, the file To update the information held.

In this way, the file holding information held by the distributed file management apparatus is updated.

[0068] In order to achieve the above object, a distributed file management system according to the present invention is a distributed file management system that manages electronic files held by a plurality of servers, and the distributed file management system includes: It is composed of a plurality of first servers connected by communication lines and a terminal used by the user. Each of the first servers relates to acquisition or writing of an electronic file from the terminal used by the user. An electronic file related to the user's request is received by a management device that is one of the first server group that receives the user's request and manages the electronic file held by the server group in response to the user's request. File server means for inquiring whether the server to be held is a deviation and file holding information as information indicating whether the server for holding the electronic file is a deviation are recorded. A holding server that is a server that holds an electronic file related to the user request by referring to the file holding information in response to an inquiry from an access source Sano that is a server that has received the user request. By determining, the first server group by communicating with the first server group, and management device means for managing the electronic file held by the server group And a first management device determination means for determining which is the management device.

[0069] In addition, the distributed file management system includes the plurality of first servers, at least one second server, and a terminal used by a user, which are connected via a communication line, and A second server that determines which of the first server group is the management device by communicating with the file server unit and the first server group; Is provided.

As described above, the distributed file management system includes a plurality of servers having a function for managing electronic files distributed and held in a plurality of servers. Therefore, even if a server that stops functioning as a distributed file management device due to a failure, etc. can be operated as a distributed file management device, other servers can operate as distributed file management devices. And the stability of the distributed file management system can be improved.

[0071] More preferably, the first management device determination unit includes a first management device holding unit that holds information indicating whether the current management device is the first server group; A rank storage unit for storing rank information, which is information that defines the order in which the first server group functions as the management device, and the management device is the management device in each first server. The management device notification unit to be notified, the first management device notification reception unit that receives the notification from the management device notification unit, and the first management device notification reception unit after receiving the notification, When a predetermined time elapses without receiving a notification, a change determination unit that determines that a change of the management device is necessary, and a case where the change determination unit determines that a change of the management device is necessary By referring to the ranking information, Information indicating the highest ranked high first server in the first server group that has a management device determining unit for holding the first management device holding portion.

[0072] Further, the first management device determination unit includes a first management device holding unit that holds information indicating which of the first server groups the current management device is, A rank storage unit that stores rank information, which is information that defines the order in which the first server group functions as the management apparatus, and the management apparatus includes the management apparatus in each of the first server and the second server. From the management device notification unit that notifies that the management device and the management device notification unit The first management device notification reception unit that receives the notification and the management device notification reception unit receives the previous notification, and when a predetermined time elapses without receiving the next notification, When the change determination unit determines that a change is necessary, and when the change determination unit determines that the management device needs to be changed, the first information is operated by referring to the ranking information. A management device determination unit that causes the first management device holding unit to store information indicating the first server having the highest rank in the server group, and the second management device determination unit includes the current management device determination unit. Holds information indicating which of the first server group the management device is! /, Receives a notification from the second management device holding unit and the management device notification unit, and receives the notification of the received notification Information indicating the transmission source is sent to the second management device holding unit. And a second management device notification reception unit for lifting.

[0073] Further, the change determination unit further includes the current management device indicated by the information held by the first management device holding unit and the information received by the first management device notification receiving unit. If the sender of the notification does not match, it is determined that the management device needs to be changed.

[0074] Further, the management device means includes: a holding server storage unit that stores the file holding information; and an access request server that has received an acquisition request that is a request for the terminal to acquire an electronic file including a user-specified identifier. An inquiry reception unit that receives an inquiry as to which server holds an electronic file including the identifier, and the file reception information is received when the inquiry reception unit receives an inquiry based on the acquisition request. By referring to the holding server determining unit that determines which holding server is the server and the server that is determined to be the holding server by the holding server determining unit, the electronic file according to the user request is accessed. A file transmission requesting unit for requesting transmission to the original server.

[0075] In this way, the first server having the function of the distributed file management apparatus communicates with another server, and it is detected in advance that communication has been lost or communication has been restored. The server with the highest rank among the first servers in operation according to the specified rank is the distributed file management device. As a result, the server functioning as the distributed file management device can be automatically switched, and the stability of the distributed file management system can be improved. [0076] More preferably, the inquiry reception unit further receives the identifier from the access source server that has received the write request that is a request for causing the server to hold an electronic file including a user-specified identifier. An inquiry as to which server holds the electronic file containing the file is received, and the holding server determination unit receives the file holding information when the inquiry receiving unit receives an inquiry based on the write request. The management device means further determines information indicating the server determined to be a holding server by the holding server determination unit by referring to the access source. It has a holding response transmitter for transmitting to the server.

[0077] Further, the file server means includes a file storage unit for storing an electronic file, a file transmission request receiving unit for receiving a file transmission request including an identifier of the electronic file transmitted by the file transmission request unit, A file storage control unit that reads an electronic file including an identifier included in the file transmission request from the file storage unit and the electronic file read by the file storage control unit are acquired, and the acquired electronic file is stored in the access source server. A file transmission unit for transmission.

[0078] Further, the file server means further includes a file receiving unit that receives an electronic file transmitted from the file transmitting unit of another server, and the file storage control unit further includes: The received electronic file is written into the file storage unit.

[0079] Thus, the access source server holds the electronic file according to the user's request! Otherwise, the electronic file is obtained from the holding sano and held by itself. As a result, when a request for acquiring the same electronic file from any of the terminals is received again, the electronic file held by itself can be transmitted. For this reason, it is not necessary for the access source server to acquire again from the holding server for the electronic file acquired via one access source server, and the amount of information transferred over the network can be reduced. The load on each server can be reduced.

[0080] More preferably, when the file storage control unit has written an electronic file in the file storage unit, the file server means further calculates the difference of the file storage unit before and after the writing to the first server group. An update notification unit for notifying The logical unit includes an update notification receiving unit that receives a notification from the update notification unit and a holding information update unit that updates the file holding information based on the difference included in the notification received by the update notification receiving unit.

[0081] Further, in the management apparatus means, the update notifying unit may be configured so that the access source server receives a request for the terminal to acquire an electronic file including a user-specified identifier. When the electronic file related to the request is written in the file storage means provided, the distributed file management device is notified of the identifier of the electronic file related to the acquisition request as the difference, and the update notification receiving unit In response to the notification from the update notification means, the retained information update unit receives information indicating the access source server and the identifier of the electronic file included in the difference in response to the notification received by the update notification reception means. The file holding information is updated by adding the associated information.

[0082] Further, the management device means may further be configured such that the update notification unit receives the request for writing the electronic file in the file storage means included in the access source server, so that the access source server receives the request. When the electronic file related to the request is written to the file storage means included in the file storage means, the identifier of the electronic file related to the write request is notified to the distributed file management device as the difference, and the update notification is received. The means receives the notification from the update notification means, and the retained information update means receives the information indicating the access source server according to the notification received by the update notification reception means and including the hash value in the difference. Then, the file holding information is updated by adding the identifier of the electronic file included in the difference.

Thus, the file holding information held by the distributed file management apparatus is updated.

It should be noted that the present invention can be realized as a distributed file management system including such characteristic means, and can be realized by using the characteristic means included in the apparatus constituting the distributed file management system as a step. A computer can be realized as a file management method or as a characteristic means included in the devices that make up a distributed file management system. It can also be realized as a program to be executed. Such a program can be distributed via a recording medium such as CD-ROM (Compact Disc-Read Only Memory) or a communication network such as the Internet. The invention's effect

[0085] When a user accesses any of a plurality of servers connected via a terminal power network used by the user, at least one of the plurality of servers holds an electronic file desired by the user. As long as it is possible, it is possible to obtain the latest electronic files according to user requests. Therefore, the user does not need to be aware of whether the electronic file has the latest power and the terminal power, and the convenience of the user for obtaining electronic files distributed and held on multiple servers on the network. It is possible to improve sex.

[0086] Furthermore, particularly for electronic files that are frequently acquired via a single server, the amount of information transferred on the network can be reduced, and the load on each server can be reduced. Is possible.

[0087] The electronic file frequently acquired here is an electronic file that has been subject to an acquisition request more than once by the same or different user, or twice by the same or different user within a certain period of time. This is an electronic file that is the subject of the above acquisition request.

[0088] Furthermore, regarding the management of electronic files for providing the latest electronic files to users, it is possible to reduce the amount of information transferred over the network, and to reduce the load on each server. Is possible.

[0089] Furthermore, it is possible to suppress consumption of storage resources for each server to hold an electronic file.

[0090] Furthermore, it is possible to detect falsification of an electronic file and transmit only the genuine electronic file to the user, and it is possible to improve the reliability of the distributed file management system. In addition, even when the server operation is stopped, the electronic file held by the server can be transmitted to the terminal used by the user.

[0091] Furthermore, even when the operation of the distributed file management device is stopped, the operation of the distributed file management system can be continued, and the stability of the distributed file management system can be improved. Is possible.

Brief Description of Drawings

FIG. 1 is a diagram showing an outline of a configuration of a distributed file management system according to Embodiment 1 of the present invention.

FIG. 2 is a diagram showing an example of an electronic file path common to electronic file information stored in a file storage unit included in each server according to the first embodiment.

FIG. 3A is a diagram showing a specific example of an electronic file stored in a file storage unit provided in server A according to the first embodiment.

FIG. 3B is a diagram showing a specific example of an electronic file stored in a file storage unit included in server B according to the first embodiment.

FIG. 3C is a diagram showing a specific example of an electronic file stored in a file storage unit included in server C according to the first embodiment.

FIG. 4 is a block diagram showing an example of a functional configuration provided in server A according to the first embodiment.

FIG. 5 is a block diagram showing an example of a functional configuration provided in the distributed file management apparatus according to the first embodiment.

6 is a diagram showing an example of management server information stored in the holding server storage unit. [FIG. 7] FIG. 7 is a diagram showing an example of file holding information stored in the holding server storage unit. Is

FIG. 8 is a time chart showing an example of processing executed in each device constituting the distributed file management system according to Embodiment 1 of the present invention when a user transmits an acquisition request for terminal power. .

FIG. 9 is a time chart showing an example of processing executed in each device constituting the distributed file management system according to the first embodiment of the present invention when the user transmits a write request with terminal power. is there.

[FIG. 10] FIG. 10 shows the processing executed by the distributed file management device, server A, server B, and terminal a when server A receives a request for acquiring file a from terminal a. 5 is a time chart showing an example of information transmitted and received between these devices.

[FIG. 11] FIG. 11 shows a distributed file management device, server A, and server when server A accepts an update request for file a held by server A after accepting an acquisition request for file a from terminal a. FIG. 7 is a diagram showing an example of processing executed between B and terminal a and information transmitted and received between these devices.

FIG. 12 is a diagram showing electronic file information stored in the file storage unit of server A that has received an acquisition request for file a from terminal a.

[FIG. 13] FIG. 13 shows a distributed file management device, server A, and server when server A receives an update request for file a held by server A after receiving an acquisition request for file a from terminal a. 7 is a time chart showing an example of processing executed in B and terminal a and information transmitted and received between these devices.

FIG. 14 is a diagram showing electronic file information stored in a file storage unit of Sano A updated by a request to update file a from terminal a.

FIG. 15 is a diagram showing file holding information updated in accordance with an update notification when server A receives an update request for file a from terminal a.

[FIG. 16] FIG. 16 is a diagram showing an example of a screen displayed on a monitor connected to a terminal used by the user for the user to input a request for a specific file.

FIG. 17 is a diagram showing an example of a result displayed on a monitor connected to a terminal used by a user when the user instructs acquisition of file a.

FIG. 18 is a diagram showing an example of a result displayed on a monitor connected to a terminal used by a user when the user instructs an update request for file a.

FIG. 19 is a diagram showing another example of file holding information stored in the holding server storage unit.

FIG. 20A is a diagram showing an example of an electronic file path common to electronic file information stored in a file storage unit included in server A according to the second embodiment.

FIG. 20B is a diagram showing an example of an electronic file path common to electronic file information stored in the file storage unit included in the server B according to Embodiment 2.

[FIG. 20C] FIG. 20C is stored in the file storage unit provided in server C according to the second embodiment. It is a figure which shows the example of the path | pass of the electronic file which is common to the electronic file information.

FIG. 21 is a block diagram showing an example of a functional configuration provided in server A320 according to the second embodiment.

22] FIG. 22 is a block diagram showing an example of a functional configuration provided in the distributed file management apparatus 310 according to the second embodiment.

[23] FIG. 23 is a diagram showing an example of file holding information stored in the holding server storage unit.

[24] FIG. 24 is a diagram showing an example of the deletion condition information according to the second embodiment.

25] FIG. 25 is a time chart showing an example of processing executed in each device constituting the distributed file management system according to the second embodiment of the present invention when the user transmits an acquisition request for terminal power. .

圆 26] FIG. 26 is a time chart showing an example of processing executed in each device constituting the distributed file management system according to the second embodiment of the present invention when the user transmits a write request with terminal power. is there.

27] FIG. 27 is a flow chart showing an example of processing executed in the distributed file management apparatus according to Embodiment 2 of the present invention when deleting an electronic file held by each server.

FIG. 28 is a diagram showing the file holding information 40 Oc after the electronic file deletion processing by the distributed file management device 310 is completed when the file holding information 400b has the contents shown in FIG.

[29] FIG. 29 is a block diagram showing an example of the functional configuration of the distributed file management apparatus according to the first modification.

FIG. 30 is a diagram showing an example of file holding information stored in a holding server storage unit.

31] FIG. 31 is a time chart showing an example of processing executed by each device according to the present modification when the server receives an update request from the user.

FIG. 32 is a diagram showing file holding information when the holding server determination unit executes the determination process in S212 when server A receives an update request for file d. [FIG. 33] FIG. 33 is a diagram showing the file holding information after the process executed by each device according to the present modification is completed when the server A accepts a request for updating the file d.

FIG. 34 is a diagram showing an example of file retention information when an electronic file having old contents is to be deleted.

FIG. 35A is a diagram showing a specific example of an electronic file stored in a file storage unit included in server A according to the third embodiment.

FIG. 35B is a diagram showing a specific example of the electronic file stored in the file storage unit provided in the server B according to Embodiment 3.

FIG. 35C is a diagram showing a specific example of the electronic file stored in the file storage unit provided in the server C according to the third embodiment.

FIG. 36 is a block diagram illustrating an example of a functional configuration provided in the server A according to the third embodiment.

[37] FIG. 37 is a block diagram showing an example of a functional configuration of the distributed file management apparatus according to the third embodiment.

38] FIG. 38 is a diagram showing an example of file holding information stored in the holding server storage unit.

39] FIG. 39 is a time chart showing an example of processing executed in each device constituting the distributed file management system according to the third embodiment of the present invention when the user transmits an acquisition request for terminal power. .

40] FIG. 40 is a time chart showing an example of processing executed in each device constituting the distributed file management system according to the third embodiment of the present invention when the user transmits a storage request for terminal power. .

41] FIG. 41 shows details of the copy destination determination processing shown in FIG. 40, and is a time chart showing an example of processing executed in each device constituting the distributed file management system according to Embodiment 3 of the present invention. .

[Fig.42] Fig.42 shows that when the user sends a request to update file f to server A, 6 is a diagram illustrating an example of file holding information in a holding server storage unit updated according to an update notification and a hash value transmitted from server A. FIG.

[43] FIG. 43 is a diagram showing a specific example for explaining the storage unit information.

FIG. 44 is a diagram showing an example of file holding information in the holding server storage unit after the processing in each device is completed when the user transmits a request to update the file f to the server A with terminal power.

45] FIG. 45 is a time chart showing an example of processing executed in each device constituting the distributed file management system according to the third embodiment of the present invention when the user transmits an update request for terminal power. .

[46] FIG. 46 is a diagram showing an example of file holding information in which a hash value is initialized when the distributed file management apparatus according to the third embodiment receives an update permission request.

FIG. 47 is a diagram showing an example of file retention information after execution of an electronic file update process related to a request when a user transmits a terminal capability update request in the third embodiment.

48] FIG. 48 is a diagram showing an outline of the configuration of the distributed file management system according to the fourth embodiment of the present invention.

FIG. 49A is a diagram showing a specific example of an electronic file stored in a file storage unit included in server A according to the fourth embodiment.

FIG. 49B is a diagram showing a specific example of the electronic file stored in the file storage unit provided in the server B according to Embodiment 4.

FIG. 49C is a diagram showing a specific example of the electronic file stored in the file storage unit provided in the server C according to the fourth embodiment.

FIG. 50 is a block diagram showing an example of an outline of a functional configuration included in a server A820 according to the fourth embodiment.

FIG. 51 is a block diagram showing an example of details of a functional configuration included in the file server unit 900 of the server A 820 according to the fourth embodiment.

[52] FIG. 52 is a block diagram showing an example of the details of the functional configuration of the management device unit and the management device determination unit of server A according to the fourth embodiment. [53] FIG. 53 is a diagram showing an example of management server information stored in the holding server storage unit according to the fourth embodiment.

FIG. 54 is a diagram showing an example of file holding information 1000b stored in the holding server storage unit 1000 according to Embodiment 4.

55] FIG. 55 is a time chart showing an example of processing executed in each device constituting the distributed file management system according to Embodiment 4 of the present invention when the user transmits an acquisition request for terminal power as well. .

圆 56] FIG. 56 is a time chart showing an example of processing executed in each device constituting the distributed file management system according to the fourth embodiment of the present invention when the user transmits a write request with terminal power. is there.

FIG. 57 is a time chart of processing executed in each server to determine a management device.

[58] FIG. 58 is a detailed flowchart of the first management device process executed by the management device determination unit of the normal server.

FIG. 59 is a detailed flowchart of the second management device process executed by the management device determination unit of the management device server.

[FIG. 60] FIG. 60 shows the distribution according to the fourth embodiment of the present invention when server A accepts an acquisition request for file d while server B is stopped and when server B recovers thereafter. It is a time chart which shows the specific example of the process performed in each apparatus which comprises a file management system.

FIG. 61 is a diagram showing an example of retained server information in the retained server storage units of server A and server C after the processing related to the acquisition request for file d executed while server B is stopped. .

FIG. 62 is a diagram showing an example of holding server information in the holding server storage unit of server B after the processing related to the acquisition request for file d executed while server B is stopped.

[63] FIG. 63 is a diagram showing an outline of the configuration of the distributed file management system according to the second modification of the present invention. 64] FIG. 64 is a diagram showing an example of the management server information in the holding server storage unit included in the server functioning as the distributed file management apparatus according to the second modification of the present invention.

65] FIG. 65 is a block diagram showing a functional configuration of server D, which is a server that does not function as the distributed file management device according to the second modification of the present invention.

Explanation of symbols

10, 310, 510, 610 Distributed file management device

15, 50 communication line

20, 30, 40, 320, 620, 820 Sano

25, 35, 45, 855 File storage

60, 65 terminals

71 User request receiver

73 Request type judgment section

75 Request information storage

77, 677 File storage controller

79, 1079 Holding server inquiry department

81 Hold response receiver

83 File transmission request receiver

85 File transmission section

87 File receiver

89 Lock request transmitter

91, 391, 1091 Update notification section

93 Completion notification receiver

95 User request response part

100, 400, 500, 700, 1000 Retention server storage

102 Inquiry reception

104, 404, 504, 704 Holding sano judgment section

106 Hold response transmitter

108 File transmission request part 110, 410 Update notification reception

112, 412 Retained information update part

114 Update completion notification section

116 Lock request receiver

118 Lock information storage

322 Deletion request receiver

420 Deletion condition storage

422 Clock

424, 524 Deletion target judgment unit

426 Deletion request section

624 Hash value request receiver

626 Hash value calculator

628 Hash value transmitter

630 Storage unit information request receiving unit

632 Storage unit information transmission unit

634 Copy destination receiver

728 Hash value request part

730 Hash value receiver

732 Update permission request receiver

734 Hash value initialization part

736 Update permission transmitter

738 Memory information request section

740 Storage unit information receiver

742 Copy destination judgment unit

744 Copy destination transmission unit

820, 900 File server part

910 Management unit

920, 1300 Management device judgment unit 1200, 1400 management device holder

1202 Management device notification unit

1204, 1402 Management device notification receiving part

1206 Change judgment section

1208 Management device decision unit

1210 Retention server information acquisition part

1212, 1412 Sano response section

1214 Server response reception part

BEST MODE FOR CARRYING OUT THE INVENTION

[0094] Hereinafter, Embodiment 1 to Embodiment 4 of the distributed file management system according to the present invention will be described with reference to the drawings.

[0095] (Embodiment 1)

A first embodiment according to the present invention will be described with reference to FIGS.

FIG. 1 is a diagram showing an outline of the configuration of the distributed file management system according to the first embodiment. The distributed file management system according to Embodiment 1 is connected to a terminal used by a user via a communication line, stores an electronic file, and a difference between a plurality of servers including a file storage unit is A terminal that accepts user requests related to electronic files to be transmitted, executes processes related to accepted user requests in cooperation with the distributed file management device or other servers, and uses the results of the executed processes by the user It is an example of a system that transmits to.

The distributed file management system according to the present embodiment is composed of distributed file management apparatus 10, server A20, server B30 and server C40, and terminal a60 and terminal b65.

[0098] The distributed file management device 10 is a device that manages information about electronic files held by a plurality of servers to be managed. The distributed file management device 10 accepts user requests related to electronic files (hereinafter referred to as " In response to an inquiry from the access source sano), information indicating the sano holding the electronic file related to the user's request (hereinafter referred to as “holding server”) is sent to the access source server. It is an example. [0099] The distributed file management apparatus 10 according to the present embodiment manages the server A20, the server B30, and the server C40, and stores information about the electronic file stored and held in the server A20. Manages information about electronic files stored and held on server B30 and information about electronic files stored and held on server C40

[0100] The communication line 15 is a communication line that connects the distributed file management apparatus 10 and each of the servers 20, 30, and 40. For example, the communication line 15 is connected via a LAN (Local Area Network) or a WAN (Wide Area Network). .

[0101] The server A20 includes a file storage unit 25 for storing electronic files, and receives a request related to the electronic file from each terminal 60, 65 and other servers 30, 40 used by the user. It is. When the server A20 receives the request, it cooperates with the distributed file management device 10 as necessary to process the received request and send the processed result to the request source.

[0102] Server B30 and server C40 also have the same function, and include a file storage unit 35 and a file storage unit 45, respectively.

[0103] Here, an example of the file structure relating to the electronic file stored in each file storage unit 25, 35, 45 according to Embodiment 1 will be described with reference to FIG. Storage

Specific examples of the electronic files stored in 25, 35, and 45 will be described with reference to FIGS. 3A to 3C.

FIG. 2 is a diagram showing an example of a folder configuration common to electronic files stored in a file storage unit included in each server according to the present embodiment. When an electronic file related to the management of the distributed file management apparatus 10 is held in each server, each server holds according to a predetermined common folder configuration.

[0105] Using the terminal 60 or 65, the user specifies an electronic file by a path indicating a predetermined common folder structure as shown in the figure, and requests related to the specified electronic file to each server. One of 20, 30, 40, for example, each terminal 60, 65 is preset and transmitted to the server.

Here, the “request related to the electronic file” is a request for acquiring the electronic file “ There are “acquisition request” and “write request” which is a request to write an electronic file. The “write request” includes an “update request” that is a request to update an existing electronic file and a “storage request” that is a request to store a new electronic file.

[0107] Each electronic file shown in the figure is specified by a relative path or file name having a folder related to the folder name Γ / dataJ as a vertex.

[0108] A folder with the folder name "Zdata" has an electronic file with the file name "a", an electronic file with the file name ^ b, and a file name "d" immediately below it. It has an electronic file and a folder whose folder name is “c”. A folder having a folder name “c” has an electronic file having a file name “e” and an electronic file having a file name “f” immediately below.

[0109] Here, the "electronic file" includes file attribute information such as file name and file update date, in addition to information serving as the entity of the electronic file. In the following, simply “file x” refers to an electronic file whose file name is “x”. In addition, when simply saying “folder x”, it means the folder whose folder name is “x”.

[0110] In addition, “file X-2” and “file X-3” refer to an electronic file with file name “x”. In other words, “File x”, “File X-2”, and “File X-3” are the power that can be specified as an electronic file with the file name “x”. Have different attribute information.

[0111] The terminology related to the "request for electronic file" and the notation method of the electronic file described here are commonly used in all the embodiments.

3A to 3C are diagrams showing specific examples of electronic files stored in the file storage unit included in each server according to Embodiment 1.

FIG. 3A is a diagram showing an example of the electronic file information 25a stored in the file storage unit 25 provided in the server A20 according to the first embodiment. This figure shows an example in which the file storage unit 25 according to the present embodiment stores “file a” and “file b”.

FIG. 3B is a diagram showing an example of the electronic file information 35a stored in the file storage unit 35 included in the server B30 according to the first embodiment. This figure shows an example in which the file storage unit 35 according to the present embodiment stores “file a-2”, “file d”, and “file e”. The

FIG. 3C is a diagram showing an example of the electronic file information 45a stored in the file storage unit 45 provided in the server C40 according to the first embodiment. This figure shows an example in which the file storage unit 45 according to the present embodiment stores “file d”.

[0116] Returning to the description of FIG.

[0117] The communication line 50 is a communication line that connects the servers 20, 30, 40 and the terminals 60, 65, and is, for example, a LAN or a WAN.

[0118] The terminal a60 is a terminal used by the user. When the terminal a60 receives a user request related to the electronic file, the terminal a60 transmits the request to any of the servers 20, 30, and 40. In addition, when the terminal a60 acquires the result from the server that transmitted the request, the terminal a60 provides the acquired result to the user by displaying the acquired result on a monitor. Terminal b65 has the same function.

[0119] As described above, each file indicated by a predetermined file configuration is distributed and held in a plurality of servers, and a user accesses a server while holding a desired electronic file. Even in such a case, the distributed file management apparatus 10 can process a user request related to the electronic file.

[0120] A functional configuration included in each device to enable such processing will be described with reference to FIGS.

[0121] FIG. 4 is a block diagram illustrating an example of a functional configuration included in the Sano A20 according to the first embodiment. Server A20 accepts a request from the user. When the user request is an acquisition request, the server A20 keeps the latest entity as long as one of the servers under the control of the distributed file management device 10 holds the electronic file related to the received acquisition request. The included electronic file is transmitted to the terminal used by the user. Server B30 and server C40 also have the same functional configuration as server A.

[0122] The server A20 includes a file storage unit 25, a user request reception unit 71, a request type determination unit 73, a request information holding unit 75, a file storage control unit 77, a holding server inquiry unit 79, Holding response reception unit 81, file transmission request reception unit 83, file transmission unit 85, file reception unit 87, lock request transmission unit 89, update notification unit 91, completion notification reception unit 93, user A request response unit 95.

Since the file storage unit 25 has been described with reference to FIG. 3, the description thereof is omitted here.

The user request receiving unit 71 is a part that receives a request related to an electronic file from the terminals 60 and 65 used by the user via the communication line 50.

The request type determining unit 73 is a part that determines the type of request related to the electronic file received by the user request receiving unit 71. In the first embodiment, the request related to the electronic file includes “acquisition request” and “write request” as described above, and the “write request” includes “update request” and “storage request”. There is. The request type determining unit 73 determines which of the requests related to the electronic file received by the user request receiving unit 71 is.

The request information holding unit 75 is a part that temporarily stores and holds information included in the request received by the user request receiving unit 71. The request information holding unit 75 is realized by, for example, a RAM (Random Access Memory).

The file storage control unit 77 is a part that controls the file storage unit 25. The file storage control unit 77 retrieves whether or not the file storage unit 25 stores a specific electronic file, reads the electronic file stored in the file storage unit 25, and stores the file storage unit 25 in the storage. The stored electronic file is updated and a new electronic file is stored in the file storage unit 25.

[0128] The holding server inquiry unit 79 holds an electronic file related to the user's request! /, And asks the distributed file management device 10 via the communication line 50, This is the part to be combined.

The holding response receiving unit 81 is a part that receives the response of the distributed file management apparatus 10 that has received the inquiry from the holding server inquiry unit 79 via the communication line 15. The holding response receiving unit 81 stores the electronic file related to the user's request when the server itself is an access source server, or the stored file storage unit 25, 3 Receives a response that states that 5 and 45 do not exist.

[0130] The file transmission request receiving unit 83 accesses the electronic file when the server provided with itself is not the access source server and the server provided with itself holds an electronic file related to the user's request. Distributed file management for requests sent to the original server This is the part that receives from the device 10.

[0131] The file transmission unit 85 receives the request received by the file transmission request reception unit 83, acquires the electronic file related to the request from the file storage control unit 77, and transmits the acquired electronic file to the access source server. It is a part.

[0132] The file receiving unit 87 is a part that receives an electronic file transmitted from the file transmitting unit 85 of another server.

[0133] When the request type determination unit 73 determines that the type of user request received by the user request reception unit 71 is a write request, the lock request transmission unit 89 performs electronic processing related to the write request. This is the part that sends to the distributed file management device 10 a lock request that eliminates processing related to file writing.

The update notification unit 91 is a part that notifies the distributed file management device 10 of the stored or updated content when the file storage control unit 77 stores or updates an electronic file.

The completion notification receiving unit 93 is a part that receives from the distributed file management apparatus 10 a notification that indicates the completion of processing.

The user request response unit 95 is a part that transmits a response to the user request received by the user request reception unit 71 to the terminals 60 and 65 used by the user via the communication line 50. The response here is an electronic file related to the acquisition request if the user request is an acquisition request, and a notification of completion of the write request if the user request is a write request.

FIG. 5 is a block diagram showing an example of a functional configuration provided in the distributed file management apparatus 10 according to the first embodiment.

The distributed file management apparatus 10 includes a holding server storage unit 100, an inquiry reception unit 102, a holding server determination unit 104, a holding response transmission unit 106, a file transmission request unit 108, and an update notification reception unit. 110, a holding information update unit 112, an update completion notification unit 114, a lock request reception unit 116, and a lock information holding unit 118.

The holding server storage unit 100 holds management server information, which is information for specifying a server set as a management target of the distributed file management apparatus 10, and each server included in the management server information. File retention information, which is information including electronic files. It is a memory part that remembers. The holding server storage unit 100 is realized by, for example, an HD (Hard Disk).

[0140] Here, a specific example of management server information and file holding information according to the present embodiment is illustrated.

This will be described with reference to FIG. 6 and FIG.

FIG. 6 is a diagram showing an example of management server information 100a stored in the holding server storage unit 100. As shown in the figure, the management server information 100a according to the present embodiment is composed of “server name” and “IP address”.

[0142] "Server name" includes the name given to the server that is the management target of the distributed file management apparatus 10. “IP address” contains the IP address assigned to each server. Then, the management server information 100a holds a server name and an IP address in association with each server that is the management target of the distributed file management apparatus 10.

This figure shows, for example, “I” for server A20 whose “server name” is indicated by “server A”.

P address ”power S“ 192. 168. XXX. 1 ”.

FIG. 7 is a diagram showing an example of the file holding information 100b stored in the holding server storage unit 100. As shown in FIG. As shown in the figure, the file holding information 100b according to the present embodiment includes a “file path”, a “server name”, and a “flag”.

[0145] "File path" contains the path of the electronic file held by each server! /. The electronic file path is common to all servers managed by the distributed file management apparatus 10 as described with reference to FIG.

[0146] "Server name" contains the same server name as the "server name" in the management server information 100a. The “server name” of the file holding information 100b is associated with the electronic file indicated by “file path”. In the “server name” of the file holding information 100b, the names of all servers holding the electronic file indicated by the corresponding “file path” are stored.

[0147] This figure shows, for example, an electronic file whose "file path" is indicated by "ZdataZa", that is, a server that holds "file a" or "file a-2". Indicates B30.

“Flag” is a flag indicating whether or not the electronic file held by each server has the latest content. The contents are rugs. In the present embodiment, “1” is stored when the electronic file held by each server has the latest contents, and “0” is stored when the electronic file does not have the latest contents.

In this figure, for example, for an electronic file whose “file path” is indicated by “ZdataZa”, the “flag” of the electronic file held by “server A” is “0”, and “server B” is Indicates that the “flag” of the stored electronic file is “1”.

That is, the electronic file held by “server A” is “ZdataZa” as shown in FIG. 3A. The electronic file held by “Server B” is “ZdataZa-2” as shown in FIG. 3B. Thus, the “flag” indicates that “server B” contains newer content than “server A” for the electronic file specified by “ZdataZa”.

[0151] This force returns to the explanation of FIG.

The inquiry reception unit 102 is a part that receives an inquiry about a server that holds an electronic file related to a user request from a server.

Retention server determination unit 104 is a part that refers to retention server storage unit 100 to determine a server that holds the latest electronic file related to the inquiry received by inquiry reception unit 102.

[0154] The holding response transmission unit 106 is a part that holds the latest electronic file according to the request of the access source server power user and responds whether or not the power is correct.

The file transmission request unit 108 is a part that requests transmission of an electronic file related to a user request to the holding server power access source server in accordance with the determination of the holding server determination unit 104.

[0156] The update notification accepting unit 110 stores a notification that the new electronic file is stored in the file storage unit included in the server or that the electronic file stored in the file storage unit is updated. It is a part received from the server.

[0157] The stored information updating unit 112 follows the content of the notification received by the update notification receiving unit 110.

The storage server storage unit 100 stores and updates the file storage information 100b.

The update completion notification unit 114 is a part that transmits to the server 20 a notification that indicates that the update of the holding server storage unit 100 by the holding information update unit 112 has been completed. [0159] The lock request receiving unit 116 is a part that receives a lock request transmitted from the server 20.

[0160] The lock information holding unit 118 completes the process of the information indicating the electronic file related to the lock request received by the lock request receiving unit 116 and executed by the holding information update unit 112 related to the electronic file. Up to this point, the part is temporarily stored.

[0161] Since the distributed file management device 10 and each server 20, 30, 40 have the above functions, the user can access any of the servers from the terminals 60, 65 used by the user. As long as each of the servers 20, 30, and 40 holds an electronic file, the electronic file can be acquired. In addition, regarding the electronic file related to the user's acquisition request, when multiple servers hold electronic files with different contents, the user holds which electronic file has the latest contents. In addition, it is possible to obtain an electronic file having the latest contents by accessing an arbitrary server.

FIG. 8 shows a series of processes executed in the distributed file management device 10 and each server 20, 30, 40 when the user transmits an acquisition request or a write request using the terminals 60, 65. This will be described with reference to FIG.

[0163] FIG. 8 is a diagram of processing executed by each device constituting the distributed file management system according to the first embodiment of the present invention when the user transmits an acquisition request from the terminals 60 and 65. It is a time chart which shows an example.

[0164] The "terminal" shown in this figure is a terminal used by the user, and in this embodiment, it is the difference between the terminal a60 or the terminal b65.

In addition, “access source sano” is a server that is a transmission destination to which the terminal 60 (65) used by the user transmits a user request. The access source server in the present embodiment is , Server A20, Server B30, or Server C40.

Furthermore, the “holding server” shown in the figure is a server that holds an electronic file related to a user request excluding the access source server. The holding server in the present embodiment is a candidate for the server A20, server B30, or server C40!

First, the user request receiving unit 71 of the access source server 20 (30, 40) is used by the user. The acquisition request transmitted by the terminal 60 (65) is received via the communication line 50 (S101). Here, the “acquisition request” is an electronic file related to the user's designation, and is a request for a terminal used by the user to acquire an electronic file having the latest contents.

[0168] Subsequently, the request type determination unit 73 acquires the request received by the user request reception unit 71, and determines whether the request is an "acquisition request" or a "write request". Since this figure is a time chart of processing related to an acquisition request, this determination is omitted.

Subsequently, when the holding server inquiry unit 79 inquires the distributed file management apparatus 10 about the holding server, the inquiry receiving unit 102 receives an inquiry of the holding server (S102).

Subsequently, the holding server determination unit 104 determines whether or not the access source server is a holding server by referring to the file holding information 10 Ob of the holding server storage unit 100 (S 103).

[0171] First, if it is determined that the access source server is a holding server (Yes in S103), then the holding response transmission unit 106 notifies that the access source server is the holding server (hereinafter referred to as " The holding response receiving unit 81 receives the holding notification (S104).

Subsequently, the file storage control unit 77 reads the electronic file related to the acquisition request from its own file storage unit 25 (35, 45) (S105). Here, “own” indicates that the same server is another part provided in the same server as the server provided with the part that is the subject of the operation.

[0173] Subsequently, the user request response unit 95 acquires the electronic file from the file storage control unit 77, transmits it to the terminal 60 (65) used by the user (S106), and ends the process.

[0174] If it is determined that the access source server is not a holding server (No in S103), continue

The holding server determination unit 104 determines whether there is a holding server (S107).

[0175] First, when it is determined that there is no holding server (No in S107), the holding response transmission unit 1 continues.

06 transmits a notification (hereinafter referred to as “non-holding notification”) indicating that there is no holding server, and the holding response receiving unit 81 receives the non-holding notification (S 108).

[0176] Subsequently, when the user request response unit 95 acquires the non-holding notification via the file storage control unit 77, the user request response unit 95 transmits the non-holding notification to the terminal 60 (65) that has transmitted the acquisition request (S109). ), The process is terminated. [0177] If it is determined that there is a holding server (Yes in S107), then the file transmission request unit 108 sends a file transmission request to the holding server, and the file transmission request receiving unit 83 of the holding server sends a file. A request is received (S 110).

[0178] Here, the "file transmission request" is a request for transmitting the electronic file to another server to the server holding the specific electronic file.

[0179] Subsequently, the file storage control unit 77 of the holding server reads the electronic file related to the file transmission request from its own file storage unit 25, 35, 45 (S111).

[0180] Subsequently, the file transmission unit 85 of the holding server transmits the electronic file read by the file storage control unit 77 to the access source server, and the file reception unit 87 of the access source server receives the electronic file (S 112).

[0181] Subsequently, the user request response unit 95 of the access source server has its own file storage control unit.

The electronic file related to the user's acquisition request is acquired via 77, and the electronic file is transmitted to the terminal ₆₀ (65) used by the user (S113).

Subsequently, the file storage control unit 77 of the access source server stores the electronic file received by the file reception unit 87 in its file storage unit 25, 35, 45 (S114).

[0183] Subsequently, the update notification unit 91 is a holding server storage unit 1 included in the distributed file management device 10.

A notification (hereinafter referred to as “update notification”) that updates the file holding information 100b of 00 is transmitted, and the update notification receiving unit 110 of the distributed file management apparatus 10 receives the update notification (S 115).

[0184] More specifically, the "update notification" here indicates that the file storage information 100b contains the new electronic finalization information in the access source storages 20, 30, and 40 in the finalization records 25, 35, and 45. This is a notification that the content has been updated or that the electronic file has been updated.

Subsequently, the holding information update unit 112 updates the file holding information 100b in the holding server storage unit 100 in accordance with the update notification acquired from the update notification receiving unit 110 (S116), and ends the process.

[0186] Fig. 9 shows the processing that is executed by each device constituting the distributed file management system according to the first embodiment of the present invention when the user transmits a write request from the terminals 60 and 65. It is a time chart which shows an example of. In the present embodiment, the processing executed by each device and the information transmitted / received between the devices are the same when the write request is an “update request” and when it is a “storage request”. .

[0188] The "terminal" and "access source Sano" shown in this figure are the same as the "terminal" and "access source server" shown in FIG.

[0189] First, the user request receiving unit 71 of the access source server 20 (30, 40) receives, via the communication line 50, the write request to which the terminal 60 (65) used by the user is also transmitted ( S201). Here, the “write request” is information including a request to update an electronic file held by the access source server or to hold a new electronic file in the access source server.

Subsequently, the request type determination unit 73 acquires the request received by the user request reception unit 71 and determines whether the request is an “acquisition request” or a “write request”. Since this figure is a time chart of processing related to a write request, this determination is omitted.

Subsequently, the request type determining unit 73 causes the request information holding unit 75 to hold the electronic file related to the write request (S202).

[0192] Subsequently, the lock request transmission unit 89 first receives a determination from the request type determination unit 73 that the acquired request is a write request, and receives a write request related to the electronic file related to the write request. A request (hereinafter referred to as “lock request”) is sent to the distributed file management apparatus 10, and the lock request receiving unit 116 receives the lock request (S203).

Subsequently, the lock request receiving unit 116 locks the lock information holding unit 118 by holding information about the electronic file related to the received lock request (S204).

[0194] Further, the file storage control unit 77 acquires the electronic file held by the request information holding unit 75 in response to the determination by the request type determining unit 73 that the acquired request is a write request. Write the acquired electronic file to its own file storage unit 25, 35, 45 205

) o

Subsequently, the file storage control unit 77 determines whether or not the writing has been completed (S206).

First, when it is determined that writing has not been completed (No in S206), the update notification unit 91 waits. [0197] If it is determined that the writing has been completed (Yes in S206), the update notification unit 91 receives a notification of completion from the file storage control unit 77 and transmits an update notification to the distributed file management apparatus 10. Then, the update notification receiving unit 110 of the distributed file management apparatus 10 receives the update notification (S207).

Subsequently, the holding information update unit 112 updates the file holding information 100b in the holding server storage unit 100 in accordance with the update notification acquired from the update notification receiving unit 110 (S116).

Subsequently, the retained information updating unit 112 releases the lock by deleting the information retained by the lock information retaining unit 118 (S209).

[0200] Subsequently, the update completion notification unit 114 receives the completion notification from the file storage control unit 77, notifies the access source server of the completion of the update processing, and the access source server completion notification reception unit 93 A notification is received (S210).

[0201] Subsequently, the user request response unit 95 of the access source server receives that the completion notification receiving unit 93 has received the completion notification, and that the user has completed processing related to the user's write request. The data is transmitted to the terminal 60 (65) to be used (S211), and the process is terminated.

[0202] The above is the processing executed in each device configuring the distributed file management system according to Embodiment 1 of the present invention. Subsequently, the distributed file according to Embodiment 1 of the present invention is exemplified by a case where server A20 receives an acquisition request for file a from terminal a60 and then receives an update request for file a held by server A20. The processing executed in each device constituting the management system will be described more specifically with reference to FIGS.

[0203] Fig. 10 shows the processes executed by the distributed file management device 10, the server A20, the server B30, and the terminal a60 when the server A20 receives an acquisition request for the file a from the terminal a60. 5 is a time chart showing an example of information transmitted / received between devices.

[0204] First, the user request receiving unit 71 of the server A20 that is the access source server receives the acquisition request transmitted from the terminal a60 used by the user via the communication line 50 (S101). The “acquisition request” here is information having a request for acquiring a file a having the latest contents by the terminal a60 used by the user. [0205] Subsequently, the request type determination unit 73 acquires the request received by the user request reception unit 71, determines that the request is an acquisition request (not shown), and then continues to hold server inquiry unit 79. When the distributed file management apparatus 10 is inquired about the holding server, the inquiry receiving unit 102 receives an inquiry from the holding server (S102).

Subsequently, the holding server determination unit 104 determines whether or not the server A20 is a holding server by referring to the file holding information 10 Ob in the holding server storage unit 100 (S103).

Here, when the file holding information 100b has the contents shown in FIG. 7, the server A20 has the file “Z dataZa”, that is, the force “flag” for holding the file “a” is “0”. Server A20 does not have file a with the latest contents. Therefore, the holding server determination unit 104 determines that the server A20 is not a holding server (No in S103).

[0208] If it is determined that the server A20 that is the access source server is not a holding server (No in S103), then the holding server determination unit 104 determines whether or not there is a holding server (S107).

) o

Here, when the file holding information 100b has the contents shown in FIG. 7, the server B30 holds the file indicated by “Zd ataZa”, that is, the file a, and the “flag” is “1”. . Therefore, the server B30 is a holding server, and the holding server determination unit 104 determines that there is a holding server (Yes in S107).

[0210] If it is determined that there is a holding server (Yes in S107), then the file transmission request unit 108 sends a transmission request for file a to server B30, which is the holding server, and the file on the holding server. The transmission request receiving unit 83 receives the transmission request for the file a (S110).

[0211] Here, "file a transmission request" includes a request for transmitting file a to server A20 to server B30 holding file a.

[0212] Subsequently, the file storage control unit 77 of the server B30 reads the file a from its own file storage unit 35 (Sl l l).

[0213] Subsequently, the file transmission unit 85 of the server B30 transmits the file a to the server A20 that is the access source server, and the file reception unit 87 of the server A20 receives the file a (S112).

) o [0214] Subsequently, the user request response unit 95 of the server A20 acquires the file a via its own file storage control unit 77, and transmits the acquired file a to the terminal a60 used by the user (S113). .

[0215] Subsequently, the file storage control unit 77 of the server A20 stores the acquired file a in its own file storage unit 25 (S114).

Here, FIG. 11 is a diagram showing the electronic file information 25a stored in the file storage unit 25 of the server A20 that has received the acquisition request for the file a from the terminal a60. “A” force in FIG. 3A showing the initial state of the file information 25a stored in the file storage unit 25 of the server A20 is updated to “a-2” in this figure.

[0217] This force also returns to the explanation of FIG.

Subsequently, the update notification unit 91 transmits an update notification, and the update notification reception unit 110 of the distributed file management apparatus 10 receives the update notification (S 115).

[0219] The "update notification" here includes the file storage information 100b and the file storage unit of the server A20.

25 is a notification that file a has been updated.

[0220] Subsequently, the holding information update unit 112 updates the file holding information 100b in the holding server storage unit 100 in accordance with the update notification acquired from the update notification receiving unit 110 (S116), and ends the process.

Here, FIG. 12 is a diagram showing the file holding information 100b updated in accordance with the update notification when the server A20 receives the acquisition request for the file a from the terminal a60. “0” force of “flag” of “server A” corresponding to “ZdataZa” in FIG. 7 showing the initial state of the file holding information 100b is updated to “1” in this figure.

[0222] The above is the process executed by the distributed file management device 10, the server A20, the server B30, and the terminal a60 when the server A20 receives the acquisition request for the file a from the terminal a60, and these Information transmitted and received between devices. After that, when an update request for file a held by server A20 is received, processing executed in distributed file management device 10, server A20, server B30, and terminal a60 and transmission / reception between these devices The information to be described will be described subsequently.

[0223] Figure 13 shows the server A20 after receiving an acquisition request for the file a from the terminal a60. When an update request for file a held by server A20 is accepted, the processing executed on distributed file management device 10, server A20, server B30, and terminal a60, and transmission / reception between these devices 5 is a time chart showing an example of information.

[0224] First, the user request receiving unit 71 of the server A20 that is the access source server receives the write request transmitted from the terminal a60 used by the user via the communication line 50 (S201). Here, the “write request” is information including a request to update the file a held by the server A.

Subsequently, the request type determination unit 73 acquires the request received by the user request reception unit 71, determines that the request is a write request (not shown), and then continues with the request type determination unit 73. Causes the request information holding unit 75 to hold the file a (S202).

Subsequently, first, the lock request transmission unit 89 receives the determination of the request type determination unit 73 that the acquired request is a write request, and locks the file a that is an electronic file related to the write request. The request is transmitted to the distributed file management apparatus 10, and the lock request receiving unit 116 receives the lock request (S203).

[0227] Subsequently, the lock request receiving unit 116 locks the lock information holding unit 118 by holding information about the file a that is the electronic file related to the received lock request (S204).

[0228] Further, the file storage control unit 77 receives the determination of the request type determination unit 73 that the acquired request is a write request, acquires the file a held by the request information holding unit 75, and The obtained file a is written into its own file storage unit 25, 35, 45 (205).

Here, FIG. 14 is a diagram showing the electronic file information 25a stored in the file storage unit 25 of the server A20 updated by the update request for the file a from the terminal a60. “A-2” power in FIG. 11 showing the file information 25a stored in the file storage unit 25 of the server A20 that has received the acquisition request for the file a is updated to “a-3” in this figure.

[0230] Return here to the explanation of FIG.

[0231] Subsequently, the file storage control unit 77 determines whether or not the writing is completed (S206). [0232] First, if it is determined that the writing is completed! /, (No in S206) , File storage control Part 77 continues writing until completion.

[0233] If it is determined that the writing has been completed (Yes in S206), the update notification unit 91 receives a notification of completion from the file storage control unit 77, and the file storage unit 25 of the server A20 receives a file. An update notification that indicates that a is updated is transmitted to the distributed file management apparatus 10, and the update notification reception unit 110 of the distributed file management apparatus 10 receives the update notification (S207) o

Subsequently, the retained information update unit 112 releases the lock by deleting the information related to the file a retained by the lock information retaining unit 118 (S 209).

[0236] Subsequently, the update completion notification unit 114 receives the completion notification from the file storage control unit 77, notifies the server A20 that is the access source server of the completion of the update process, and the server A20 completion notification reception unit. 93 receives a notification of completion (S210).

[0237] Subsequently, the user request response unit 95 of the server A20 confirms that the processing related to the user's write request has been completed in response to the completion notification receiving unit 93 receiving the notification of completion. Is transmitted to the terminal a60 used by the client (S211), and the process is terminated.

Here, FIG. 15 is a diagram showing the file holding information 100b that is updated according to the update notification when the server A20 receives an update request for the file a from the terminal a60. “1” power of “flag” of “server B” corresponding to “ZdataZa” in FIG. 12 showing the file holding information 100b after accepting the acquisition request of file a is updated to “0” in this figure! RU

[0239] The above is the distribution according to Embodiment 1 of the present invention when server A20 accepts an acquisition request for file a from terminal a60 and then accepts an update request for file a held by server A20. This is a process that is executed by each device constituting the file management system.

[0240] Next, an example of the input screen and the result display screen displayed on the monitor connected to the terminal 60 (65) used by the user will be described with reference to FIGS.

FIG. 16 is a diagram showing an example of a screen for a user to input a request for a specific file, which is displayed on a monitor connected to the terminal 60 (65) used by the user. User Sees the screen display shown in the figure and sends an acquisition request and a write request to the server.

[0242] The input screen 200 illustrated in the figure includes a file configuration display unit 202, a selected file display unit 204, an acquisition button 206, a write file input unit 208, and a write button 210.

The file configuration display unit 202 is a part that displays the path of the electronic file in each of the servers 20, 30, and 40 that are managed by the distributed file management apparatus 10.

[0244] The content displayed in the file structure display unit 202 is the same structure as the electronic file nose shown in FIG. 2, and the terminal 60 (65) power is also distributed file management via the servers 20, 30, 40. Acquired by accessing the file holding information 100b of the device 10.

[0245] The user selects an electronic file related to the acquisition request or the write request using an input device such as a mouse for the electronic file displayed on the file structure display unit 202. The file structure display unit 202 in this figure shows an example in which the cursor is on the file a and the file a is selected.

[0246] The selected file display unit 204 is a part that displays the electronic file selected by the user. In this figure, file a is selected as described above. Therefore, the “Selected file” in the selected file display unit 204 displays “ZdataZa” t and the path.

[0247] The acquisition button 206 is a button for transmitting an acquisition request to the terminal 60 (65). When the user presses the acquisition button 206 on the input screen 200 as shown in the figure, the terminal 60 (65) transmits the acquisition request for the file a to any of the servers 20, 30, and 40.

[0248] The write file input unit 208 is a part for updating the files held by the servers 20, 30, and 40 or inputting an electronic file to be newly stored. This figure is an example in which “terminal aZxyz” and the file xyz held by the terminal a60 (65) specified by the path are input.

[0249] The write button 210 is a button for sending a write request to the terminal 60 (65). When the user presses down the write button 210 on the input screen 200 as shown in the figure, since the terminal 60 (65) selects the file a for any of the servers 20, 30, and 40, the file a Send a write request. In addition, the substance of the file a stored in the file storage unit 25, 35, 45 updated by this write request is the file input to the write file input unit 208. Same as xyz entity.

FIG. 17 is a diagram showing an example of a result displayed on the monitor connected to the terminal 60 (65) used by the user when the user instructs acquisition of the file a.

[0251] The acquisition result display screen 220 shown in this figure transmits a file a acquisition request.

This is a screen displayed on the monitor when the terminal 60 (65) used by the user acquires the file a.

[0252] The acquisition result display screen 220 includes an acquisition file display unit 222, a browse button 224, and a save button 226.

[0253] The acquired file display unit 222 displays the name of the acquired file.

[0254] The browse button 224 is a button for displaying the acquired file on the monitor. When the user presses the mouse using a mouse, the acquired file is displayed on the monitor.

[0255] The save button 226 is a button for saving the acquired file in the storage unit provided in the terminal 60 (65). When the user presses using a mouse or the like, the acquired file is saved on the terminal 60.

(65) is stored in the storage unit.

FIG. 18 is a diagram showing an example of a result displayed on the monitor connected to the terminal 60 (65) used by the user when the user instructs to update the file a.

[0257] The update result display screen 230 shown in this figure is a screen displayed on the monitor when the processing related to the update request for the file a is completed.

The update result display screen 230 includes an update result display unit 232 and a confirmation button 234.

[0259] In the update result display section 232, when the write request to which the terminal 60 (65) is also transmitted is a request to update the electronic file, the name of the electronic file related to the request and its processing are displayed. Shown as complete.

[0260] Thus, the user using the terminal 60 (65) can know that the processing is completed.

[0261] The confirmation button 234 is a button for closing the update result display screen 230 when pressed.

[0262] With such display screens, the user can send a request on the monitor and obtain the result of the processing related to the request. [0263] The power described above for the distributed file management device and the distributed file management system according to Embodiment 1 of the present invention is not limited to this embodiment.

The holding server storage unit 100 may hold the “creation date” of the electronic file instead of the “flag” of the file holding information 100b.

FIG. 19 is a diagram showing another example of the file holding information 100c stored in the holding server storage unit 100. As shown in FIG. The file holding information 100c shown in this figure holds “creation date” instead of the “flag” of the file holding information 100b shown in FIG.

[0266] The electronic file whose "creation date" of the electronic file is closest to the current one retains the latest contents. Therefore, it is possible to determine whether or not the electronic contents held by each server are the latest based on the “creation date” of the electronic file.

[0267] For example, in the file holding information 100c shown in this figure, the file "a" whose "file path" is "ZdataZa" is held by "server A" and "server B", and "server A" It contains information that the “creation date” of the file a to be retained is “March 3, 2006” and the “creation date” of the file a retained by “Server B” is “March 20, 2006”.

In this case, the file a held by “server B” whose “creation date” is closest to the present contains the latest contents, and the file a held by “server A” contains old contents.

As described above, when the distributed file management system according to Embodiment 1 accepts a write request, it writes a new electronic file only in the file storage unit of the access source server. In addition, when the distributed file management system according to Embodiment 1 receives an acquisition request, the user acquires an electronic file from a server that holds the electronic file including the latest contents, so that the user can access any server. An electronic file having the latest contents is provided to the user without being aware of whether or not the user has accessed.

[0270] With this, when there are a plurality of holding servers related to the update request, it is possible to suppress the data transfer amount compared to the case where updating is performed while synchronizing electronic files held by the plurality of holding servers. It becomes possible. In particular, when there are many servers that hold the same electronic file, the advantage of reducing the amount of data transferred during update is significant.

[0271] (Embodiment 2) In the distributed file management system according to the first embodiment, the access source server that has received the acquisition request holds the electronic file related to the acquisition request. In this case, the management is performed based on information from the distributed file management device. The server that holds the electronic file related to the acquisition request is identified among the servers related to the above, and the electronic file related to the acquisition request is acquired from the server and stored in its own file storage unit.

[0272] Therefore, when a long time elapses, all servers hold almost all electronic files in duplicate. It can be said that it is a wasteful use of storage that a large number of servers hold electronic files with few requests for acquiring or updating terminal capabilities.

[0273] Thus, Embodiment 2 provides a distributed file management system capable of effectively using storage.

[0274] A second embodiment according to the present invention will be described with reference to Figs.

[0275] The outline of the configuration of the distributed file management system shown in FIG. 1 is the same as that of the distributed file management system according to the second embodiment. Description is omitted.

[0276] The distributed file management system according to the second embodiment accepts user requests from the terminals 60 and 65 used by the user, and the terminals 60 and 65, and sets the file storage units 25, 35, and 45 respectively. Server A320, Server B330, Server C340, and a distributed file management device that manages information related to electronic files distributed and held in each server by sending and receiving information to and from these servers .

[0277] The folder structure of the electronic file stored in the file storage unit included in each server according to the second embodiment is indicated by a common path in each file storage unit as in the first embodiment. A specific example thereof is the same as the folder structure of the first embodiment shown in FIG. Therefore, the description here regarding the folder structure is omitted.

20A to 20C are diagrams illustrating specific examples of electronic files stored in the file storage unit included in each server according to Embodiment 2. FIG.

FIG. 20A is a diagram showing an example of electronic file information 25b stored in the file storage unit 25 provided in the server A320 according to the second embodiment. This figure shows an example in which the file storage unit 25 according to the present embodiment stores “file a”. FIG. 20B is a diagram showing an example of the electronic file information 35b stored in the file storage unit 35 provided in the server B330 according to the second embodiment. This figure shows an example in which the file storage unit 35 according to the present embodiment stores “file a”, “file”, and “file e”.

FIG. 20C is a diagram showing an example of the electronic file information 45b stored in the file storage unit 45 included in the server C340 according to Embodiment 2. This figure shows an example in which the file storage unit 45 according to the present embodiment stores “file d”.

FIG. 21 is a block diagram showing an example of a functional configuration provided in the Sano A320 according to the second embodiment. Server A320 receives a request from the user, and if the user request is an acquisition request, server A320 manages the electronic file related to the received acquisition request in the distributed file management device 310, in the same manner as Sano A20 according to the first embodiment. As long as one of the servers below holds, the electronic file containing the latest entity is sent to the terminal used by the user. Further, unlike the server A20 according to the first embodiment, the server A320 according to the second embodiment deletes an electronic file that satisfies certain conditions from the file storage unit 25 in accordance with a request from the distributed file management device 310. .

The server A 320 includes a file storage unit 25, a user request reception unit 71, a request type determination unit 73, a request information holding unit 75, a file storage control unit 77, a holding server inquiry unit 79, Update response reception unit 81, file transmission request reception unit 83, file transmission unit 85, file reception unit 87, lock request transmission unit 89, completion notification reception unit 93, user request response unit 95, update A notification unit 391 and a deletion request receiving unit 322 are provided.

[0284] For server A320 according to the second embodiment, parts having the same functions as those of server A20 according to the first embodiment are denoted by the same reference numerals, and the parts related to these parts are here. Description is omitted.

[0285] The deletion request receiving unit 322 receives, from the distributed file management device 310, a request to delete a part or all of the electronic file stored in its own file storage unit 25 via the communication line 15. It is a part.

[0286] In the update notification unit 391, the file storage control unit 77 stores a new electronic file in the file storage unit 25, updates the electronic file information 25a, or receives power from the electronic file information 25a. This is a part for notifying the distributed file management device 10 of the stored, updated, or deleted contents when part or all of the child file is deleted.

[0287] The above is the functional configuration of the Sano A320 according to the present embodiment. Server B330 and server C340 also have the same functional configuration as server A320.

FIG. 22 is a block diagram showing an example of a functional configuration provided in the distributed file management apparatus 310 according to the second embodiment. The difference between the distributed file management apparatus 310 according to the second embodiment and the distributed file management apparatus 10 according to the first embodiment is that the distributed file management apparatus 310 according to the second embodiment makes a user request for a certain period of time or longer. When a server does not receive a request, and multiple servers hold an electronic file, the server deletes the electronic file held by only one server.

The distributed file management apparatus 310 includes an inquiry reception unit 102, a holding response transmission unit 106, a file transmission request unit 108, an update completion notification unit 114, a lock request reception unit 116, and a lock information holding unit. 118, holding server storage unit 400, holding server determination unit 404, update notification reception unit 410, holding information update unit 412, deletion condition storage unit 420, clock unit 422, deletion target determination unit 424, A deletion request unit 426.

[0290] In the distributed file management device 310 according to the second embodiment, parts having the same functions as those of the distributed file management device 10 according to the first embodiment are denoted by the same reference numerals. The description here is omitted.

Similar to the holding server storage unit 100 according to the first embodiment, the holding server storage unit 400 includes management server information that is information about servers set as management targets of the distributed file management device 310, and a management server This is a storage unit that stores file holding information, which is information related to the electronic file held by each server included in the information. The holding server storage unit 400 is realized by, for example, an HD (Hard Disk).

[0292] The management server information 400a according to the second embodiment is the same as the management server information 100a according to the first embodiment described with reference to FIG.

A specific example of the file holding information according to Embodiment 2 will be described with reference to FIG.

FIG. 23 shows an example of the file holding information 400b stored in the holding server storage unit 400. It is a figure. As shown in the figure, the file holding information 400b according to the present embodiment is composed of “file path”, “server name”, and “access date”.

[0295] The "file path" and "server name" of the file holding information 400b according to the present embodiment are the "file path" of the file holding information 100b according to the first embodiment described with reference to FIG. And “server name” are stored in the same information, and detailed description thereof is omitted here.

[0296] The "access date" stores the date when the user request related to the electronic file indicated by the server power "file path" indicated by the information stored in the "server name" was last received.

This figure shows, for example, that an electronic file whose “file path” is “ZdataZa” is “2006083”, that is, “20 06” March 3 of the year ".

[0298] Here, let us return to the explanation of FIG.

The holding server determination unit 404 is a part that determines a server that holds an electronic file related to an inquiry received by the inquiry reception unit 102 by referring to the holding server storage unit 400.

[0300] Furthermore, if the holding server determination unit 404 determines that the access source server is the holding server of the electronic file related to the acquisition request, the holding server determination unit 404 outputs a useful determination to the holding information update unit 112.

[0301] Furthermore, the holding server determination unit 404 determines whether or not the holding server power of the electronic file related to the write request is in the access source server.

[0302] The update notification reception unit 410 stores new electronic files in the file storage units 25, 35, and 45 of each server, and updates the electronic files stored in the file storage units 25, 35, and 45. Or a part that receives a notification from the server that the electronic file stored in the file storage unit 25, 35, 45 has been deleted.

[0303] The holding information update unit 412 updates the file holding information 400b stored in the holding server storage unit 400 according to the information received from the holding server determination unit 404 or the information received by the update notification receiving unit 410. is there. [0304] The deletion condition storage unit 420 is a part that stores deletion condition information, which is information including conditions for deleting an electronic file held by each server.

FIG. 24 is a diagram showing an example of the deletion condition information 420a according to Embodiment 2. The deletion condition shown in this figure is an example on condition that the electronic file held by the server is deleted when “30 days” or more have passed since the “access date” of the file retention information 400b. is there.

[0306] This force returns to the description of FIG.

[0307] The clock unit 422 is a part that holds the current date and time.

[0308] The deletion target determination unit 424 is a unit that determines an electronic file to be deleted for each server. More specifically, the deletion target determination unit 424 has an electronic file whose date power indicated by the “access date” of the file retention information 400b is retained beyond the period included in the deletion condition information 420a, and When there are a plurality of servers holding the electronic file, it is determined that only the electronic file held by the server having the latest “access date” is left and the electronic file held by another server is deleted.

[0309] Deletion target determining section 424 according to the present embodiment executes the above determination processing at a predetermined cycle.

[0310] The deletion request unit 426 is a part that transmits a request to delete the electronic file to the server that holds the electronic file determined to be deleted by the deletion target determination unit 424.

[0311] Since the distributed file management apparatus 10 and the servers 20, 30, 40 are provided with the functions as described above, as in the first embodiment, the user can use any of the terminals 60, 65 used by the user. Regardless of whether the server is accessed, as long as each of the servers 20, 30, and 40 holds the electronic file, the electronic file can be obtained.

[0312] In addition, when a plurality of servers hold an electronic file related to a user's acquisition request, the electronic files are synchronized, and thus the user holds an electronic file having the latest contents. It is possible to obtain an electronic file having the latest contents by accessing an arbitrary server without being aware of the power of the user.

[0313] Furthermore, if the same electronic file is held in duplicate on multiple servers, According to the specified conditions, the electronic file held by one of the servers is left and the electronic file held by the other server is deleted, so that the storage can be effectively used.

FIG. 25 is a time chart showing an example of processing executed in each device configuring the distributed file management system according to Embodiment 2 of the present invention when the user transmits an acquisition request for terminal power. .

[0315] In this figure, processes denoted by the same reference numerals as those executed in each device according to Embodiment 1 shown in Fig. 8 indicate similar processes. For this reason, the description of the processes with the same reference numerals is omitted here.

[0316] The difference between the time chart shown in FIG. 8 and the time chart shown in FIG. 8 is that the access source server's retention judgment regarding the electronic file (S 103) is positively determined (in S 103 Yes), the retention information update process is executed (S310) before the retention notification (S104) is made.

[0317] If the holding server determination unit 404 determines that the access source server is the holding server (Yes in S103), then the holding information update unit 412 receives the determination of the holding server determination unit, and the access source The “access date” of the file retention information 400b regarding the electronic file related to the user request held by the server is updated with the date acquired from the clock unit 422 (S301).

) o

[0318] FIG. 26 shows an example of processing executed in each device constituting the distributed file management system according to Embodiment 2 of the present invention when a user transmits a write request from terminals 60 and 65. It is a time chart.

[0319] In this figure, the process given the same reference numeral as the process executed in each device according to Embodiment 1 shown in Fig. 9 shows the same process. For this reason, the description of the processes with the same reference numerals is omitted here.

[0320] The difference between the time chart shown in this figure and the time chart shown in Figure 8 is that the distributed file management device 310 determines whether there is a holding server other than the access source server, and holds other than the access source server. If there is a server, the electronic file held by the server is also updated. Through such processing, the power held redundantly by multiple servers The contents of child files are synchronized.

[0321] After the update completion notification unit 114 of the distributed file management device 310 receives the completion notification from the file storage control unit 77 and notifies the access source server of the completion of the update process (S209), the distributed file The holding server determination unit 404 of the management device 310 determines whether or not the holding server power of the electronic file related to the write request is in the access source server (S212).

[0322] If it is determined that there is no holding server below the access source server (No in S212), the distributed file management device 310 waits until a request or inquiry from Sano is accepted.

[0323] If it is determined that there is a holding server below the access source server (Yes in S212), the file transmission request unit 108 transmits a file transmission request to the access source server, and the file transmission of the access source server 320 is performed. The request receiving unit 83 receives a file transmission request (S213).

Here, the “file transmission request” includes a request for transmitting to the access source server an electronic file related to the user's write request to another holding server.

[0325] Subsequently, the file storage control unit 77 reads out an electronic file related to the file transmission request from its own file storage unit 25 (S214).

[0326] Subsequently, the file transmitting unit 85 of the access source server 320 transmits the electronic file read by the file storage control unit 77 to the holding server, and the file receiving unit 87 of the holding server receives the electronic file (S215 ).

The file storage control unit 77 of the holding server updates the electronic file stored in its own file storage unit 25 with the electronic file received by the file reception unit 87 (S216).

[0328] Subsequently, the update notification unit 391 transmits an update notification to the distributed file management device 310, and the update notification reception unit 410 of the distributed file management device 310 receives the update notification (S217).

[0329] More specifically, the "update notification" here indicates that a new electronic file is stored in the file storage unit 25, 35, 45 of the access source Sano 20, 30, 40, or the electronic file This is a notification that has been updated.

Subsequently, the holding information update unit 412 updates the file holding information 100b of the holding server storage unit 100 in accordance with the update notification acquired from the update notification receiving unit 410 (S218), and ends the process. End.

[0331] The above is the processing that is executed by each device when a server request is received from the server! In the present embodiment, as described above, the electronic file is deleted for a server that holds an electronic file for which a fixed period has passed since the last access by the user. Processing executed by the distributed file management apparatus 310 at this time will be described with reference to FIG.

FIG. 27 is a flowchart showing an example of processing executed in the distributed file management apparatus 310 according to Embodiment 2 of the present invention when deleting an electronic file held by each server.

First, the deletion target determining unit 424 determines whether or not it is a predetermined update time held by itself by comparing it with the current time acquired from the clock unit 422 (S300).

) o

[0334] If it is determined that the update time is not reached (No in S300), the deletion target determination unit 424 continues to determine whether or not it is the update time.

[0335] If it is determined that it is the update time (Yes in S300), the distributed file management apparatus 310 will explain all electronic files included in the file holding information 400b of the holding server storage unit 400 as follows. Judgment whether or not a certain time has passed since the last access (S30

The processing from 2) to update of stored information (S307) is repeated (S301).

First, the deletion target determination unit 424 obtains the “access date” of the file retention information 400b and the current date from the deletion condition information 420a and the clock unit 422, and the current date is also “access date”. It is determined whether or not the period included in the deletion condition information 420a has passed (S302).

[0337] If it is determined that the period included in the deletion condition information 420a has not passed since the "access date" (No in S302), the elapsed time is determined for the next electronic file (S 302) ) Is executed.

[0338] When it is determined that the period included in the deletion condition information 420a has elapsed from the "access date" as the current date (Yes in S302), the deletion target determination unit 424 holds the same electronic file. It is determined whether or not there are a plurality of servers (S303).

[0339] When it is determined that there is not more than one server holding the same electronic file (S303) No), the elapsed time determination process (S302) is executed for the next electronic file. Therefore, if there is only one electronic file holding server for which a certain period of time has passed since the last access date, the electronic file is not deleted.

[0340] If it is determined that there are a plurality of servers holding the same electronic file (S30

(Yes in 3) The “access date” is the newest among the servers holding the electronic file! The electronic files held by each server excluding the server are determined to be deleted (S304).

[0341] The deletion request unit 426 transmits a deletion request for the electronic file to the server holding the electronic file determined to be deleted by the deletion target determination unit 424 (S305).

[0342] The update notification reception unit 410 receives an update notification from the server that has executed the electronic file deletion processing related to the request from the deletion request unit 426 (S306).

[0343] The "update notification" received here is the file storage unit 25, 35 of the holding server 20, 30, 40,

45 is a notification indicating that the stored electronic file has been deleted.

Subsequently, the holding information update unit 412 updates the file holding information 400b according to the update notification received by the update notification receiving unit 410 (S307), and ends the processing.

[0345] When the electronic file held by each server is deleted, the distributed file management device 3

10 is a process to be executed. When the file retention information 400b has the contents shown in Fig. 23

The processing to be executed after the distributed file management device 310 determines that the deletion target determination unit 424 is the update time (Yes in S300) will be described in more detail.

[0346] First of all, file a whose “file path” is “ZdataZa”! /, And the current date obtained from the clock part 422 is “access date” “March 3, 2006 "Delete condition information from" 42

It is determined whether “30 days”, which is a period included in Oa, has passed! /, Or not (S302). Here, the current date is “March 30, 2006”.

[0347] "March 30th 2006" [March 3rd March 2006] Power, etc. "30" power ^^!

Next, the deletion target determination unit 424 executes the same determination process (S302) for the file b that is “ZdataZb” that is the next file!

[0348] Similarly to file a, file b also has a current date that has not passed the period included in the deletion condition since the "access date" (No in S302). Part 4

24 is the same judgment process for file e which is the next file “ZdataZcZe”. (S 302) is executed.

[0349] As with file a, the current date has not passed the period included in the deletion condition since the "access date" (No in S302). The unit 424 executes the same determination process (S 302) for the file d “ZdataZd” that is the next file.

[0350] For file d, the holding servers are server B330 and server C340. File d! /, The access date of server B330 is “March 3, 2006”, and the current date “March 30, 2006” is “Access Date”. The day has passed!

[0351] In addition, the “access date” of server C340 is “February 20, 2006”, and the current date “March 30, 2006” is “access”. 30 days have passed since the day!

[0352] Therefore, the deletion target determination unit 424 determines that the period included in the deletion condition information 420a has elapsed from the file "d" and the current date is "access date" (Yes in S302).

[0353] Subsequently, since there are a plurality of servers that hold the file d, the deletion target determination unit 424 has the newest “server B330 and server C340” that hold the file d. Sano other than the server B330, which is the server related to the “access date”, that is, the file d held by the server C340 is determined to be deleted (S303).

Subsequently, the deletion request unit 426 requests the server C340 to delete the file d (S304).

Subsequently, the update notification receiving unit 410 receives an update notification from the server C340 that has deleted the file d in response to a request from the deletion request unit 426 (S305).

The “update notification” received here is a notification that is stored in the file storage unit 45 of the server C340 and contains the information that the file d has been deleted.

Subsequently, the holding information update unit 412 updates the file holding information 400b according to the update notification received by the update notification receiving unit 410 (S306), and ends the process.

Here, FIG. 28 is a diagram showing the file holding information 400c after the electronic file deletion processing by the distributed file management device 310 is completed when the file holding information 400b has the contents shown in FIG. It is.

[0359] As described above, file a, file b, and file e are not deleted. The file retention information after 400b will not be changed.

[0360] Since the file d held by "Server C" has been deleted, the holding server of "ZdataZd" is updated to only "Server B".

[0361] In the second embodiment, examples of the input screen and the result display screen displayed on the monitor connected to the terminal 60 (65) used by the user are shown in Figs. 16 to 18 in the first embodiment. This is the same as the example of the input screen and the result display screen described with reference to FIG. Therefore, the explanation here is omitted.

As described above, the power described for the distributed file management apparatus and the distributed file management system according to the second embodiment of the present invention is not limited to this embodiment.

[0363] For example, the distributed file management apparatus 310 according to the second embodiment executes the deletion process at a predetermined cycle, but executes the deletion process when the server receives a user power update request. Also good.

[0364] Furthermore, the distributed file management apparatus 310 may execute the deletion process both in a predetermined cycle and when the server receives an update request from the user.

[0365] (Variation 1)

Here, with reference to FIG. 29 to FIG. 33, a description will be given of Modification 1 in which the deletion process is executed when the server receives an update request for user power.

FIG. 29 is a block diagram illustrating an example of a functional configuration included in the distributed file management apparatus 510 according to the first modification. When any of the managed servers receives the update request, the distributed file management apparatus 510 transmits a request to delete the electronic file related to the update request to the holding server other than the access source server.

[0367] The distributed file management apparatus 510 includes an inquiry reception unit 102, a holding response transmission unit 106, a file transmission request unit 108, an update completion notification unit 114, a lock request reception unit 116, and a lock information holding unit. 118, an update notification receiving unit 410, a holding information update unit 412, a deletion request unit 426, a holding server storage unit 500, a holding server determination unit 504, and a deletion target determination unit 524.

[0368] The holding server storage unit 500 is similar to the holding server storage unit 400 according to the second embodiment. This is a storage unit that stores management server information and file retention information. For example, HD (

Hard disk).

[0369] The management server information 500a according to the first modification is the same as the management server information 100a according to the first embodiment described with reference to FIG. 6, and thus description thereof is omitted here.

A specific example of the file holding information according to Modification 1 will be described with reference to FIG.

FIG. 30 is a diagram showing an example of the file holding information 500b stored in the holding server storage unit 500. As shown in the figure, the file holding information 500b according to the present embodiment is composed of “file path” and “server name”.

[0372] The "file path" and "server name" in the file holding information 500b according to this variation are shown in FIG.

“File path” of the file holding information 400b according to the second embodiment described with reference to FIG.

, “Server name” and similar information are stored respectively.

[0373] The difference between the file holding information 500b according to this modification and the file holding information 400b according to Embodiment 2 is that the file holding information 500b according to this modification does not include an "access date". It is in.

[0374] In the second embodiment, an electronic file whose fixed period has elapsed from the access date is a deletion candidate. In this modification, the electronic file on the holding server is deleted when the server receives an update request. Therefore, the access date becomes unnecessary.

[0375] Return here to the explanation of FIG.

The holding server determination unit 504 is a part that determines a server that holds an electronic file related to an inquiry received by the inquiry reception unit 102 by referring to the holding server storage unit 500.

[0377] Also, the holding server determination unit 504 determines a server that holds the electronic file related to the update request in addition to the access source server.

[0378] Similarly to the deletion target determination unit 424 according to Embodiment 2, the deletion target determination unit 524 is a part that determines an electronic file to be deleted for each server. The deletion target determination unit 524 according to this modification obtains information about the server that holds the electronic file related to the update request in addition to the access source server determined by the holding server determination unit 504, and deletes the acquired information about the server. Deliver to request part 426. [0379] Next, processing executed by each device according to the present modification when the server receives an update request from the user will be described with reference to the drawings.

FIG. 31 is a time chart illustrating an example of processing executed by each device according to the present modification when the server accepts an update request having a user power. In this figure, server A320 is assumed to be the access source server, and the case where server A320 receives an update request for file d will be specifically described as an example.

[0381] In this figure, processes denoted by the same reference numerals as those executed in each apparatus according to Embodiment 2 shown in Fig. 26 indicate similar processes. For this reason, the description of the processes with the same reference numerals is omitted here.

[0382] The difference between the process shown in this figure and the process shown in FIG. 26 is that there is a holding server other than the access source server in determining whether there is a holding server other than the access source server (S212). If it is determined (Yes in S212), it is in the subsequent processing.

Here, when the server A320 as the access source server receives the update request for the file d, the file holding information when the holding server determination unit 504 executes the determination processing in S212 is shown in FIG. As shown.

FIG. 32 is a diagram showing the file holding information 500c when the holding server determination unit 504 executes the determination process in S212 when the server A320 receives the update request for the file d. The initial state of the file holding information is the file holding information 500b shown in FIG.

In the file holding information 500c shown in the figure, “server A” is added to the “server name” corresponding to the file d by the holding information update process (S208).

[0386] With reference to FIG. 31, the following processing will be described when it is determined that there is a holding server other than the access source server (Yes in S212).

[0387] First, the holding server determination unit 504 receives the fact that the holding information update unit 412 has updated the file holding information 500b, and determines whether there is a holding server other than the access source server and if there is a holding server. Determines which server the holding server is (S212).

[0388] Regarding the file d, since the holding servers other than the server A320 that is the access source server are the "server B" and the "server C", the holding server determination unit 504 In addition, there are holding servers, and it is determined that the holding servers are “Server B” and “Server C”.

Subsequently, the deletion target determination unit 524 determines the deletion target in response to the determination of the holding server determination unit 504 (S313).

Here, the deletion target determining unit 524 determines the file d held by “server B” and “server C”, which are the holding servers determined by the holding server determining unit 504, as deletion targets (S313).

Subsequently, the deletion target determining unit 524 determines whether there is a deletion target (S314).

[0392] If it is determined that there is no deletion target (No in S314), the distributed file management device 310 waits until receiving a request or inquiry from the server.

[0393] If it is determined that there is a deletion target (Yes in S314), then the deletion request unit 426

The file deletion request is transmitted to the holding server, and the deletion request receiving unit 322 of the holding server receives the file deletion request (S315).

[0394] Here, since the file d held by "Server B" and "Server C" is determined as the deletion target, the deletion target determination unit 524 determines that there is a deletion target (Yes in S314), and Deletion request part 4

26 sends a request to delete file d to server B330 and server C340, and server B

The deletion request receiving unit 322 of 330 and the server C340 respectively receive the deletion request for the file d (S315).

Subsequently, the file storage control unit 77 of the holding server that has received the file deletion request deletes the electronic file related to the deletion request from the file information stored in the file storage unit (S316).

Here, each file d stored in the file storage control unit 77 force file storage unit 35, 45 of the server B330 and the server C340 is deleted (S316).

Subsequently, the update notification unit 391 of the holding server transmits an update notification, and the update notification reception unit 410 receives the update notification (S317). Here, the “update notification” is a notification indicating that the electronic file stored in the file storage units 25, 35, 45 of the holding servers 20, 30, 40 has been deleted.

[0398] Here, the update notification unit 391 of the server B330 and the server C340 is the file storage unit. An update notification with the content that the file d stored in 35 and 45 is deleted is transmitted, and the update notification receiving unit 410 receives the update notification (S317).

Subsequently, the holding information update unit 412 updates the file holding information 500c in the holding server storage unit 500 according to the update notification received by the update notification receiving unit 410 (S318), and ends the processing.

Here, the file holding information after the update processing by the holding information update unit 412 will be described with reference to the drawings.

[0401] FIG. 33 is a diagram showing the file holding information 500d after the processing executed by each device according to the present modification is completed when the server A320 receives a request for updating the user power file d. In the file holding information 500d shown in this figure, “Server B” and “Server C” have been deleted from the “Server name” corresponding to the file d from the file holding information 5 OOc force shown in FIG. “Server name” is the only “server name” corresponding to.

[0402] In Modification 1 described above, the deletion process is executed when an update request is received from the user, so the "access date" is not required. In addition, the access source server that has received the update request holds the electronic file related to the deletion even after processing. Therefore, the deletion target determination unit 424 can simplify the process that does not require determination of the deletion target based on whether or not there is a plurality of servers that hold the electronic file related to the deletion.

[0403] As described above, when the deletion process is executed both in a predetermined cycle and when the server receives a write request from the user, the distributed file management apparatus This can be realized by combining the function of the distributed file management apparatus 310 according to the second embodiment shown in FIG. 22 and the function of the distributed file management apparatus 310 according to the first modification shown in FIG.

[0404] Further, for example, the file holding information 400b further includes a “flag” indicating whether or not the content of the electronic file is the latest as in the first embodiment. You may include electronic files with old content in the file! / ヽ.

FIG. 34 is a diagram showing an example of the file holding information 400d when an electronic file having old contents is to be deleted. As shown in the figure, the file holding information 40 Od in this case is composed of “file path”, “server name”, “flag”, and “access date”. [0406] The "file path", "server name", and "access date" of the file holding information 400d are the "file path" of the file holding information 400b according to the second embodiment described with reference to FIG. "," Server name "and" access date "are stored in the same information. Further, the “flag” of the file holding information 400d stores the same information as the “flag” of the file holding information 100b according to Embodiment 1 described with reference to FIG.

[0407] The functional configuration of each device in this case is realized by combining the functions of each device according to Embodiment 1, Embodiment 2, and Modification 1.

[0408] (Embodiment 3)

In the distributed file management system according to the first embodiment and the second embodiment, a plurality of servers may hold an electronic file having the latest contents in an overlapping manner. In this way, the electronic file that is frequently acquired by the user can be reduced in the amount of information that travels through the communication line in the processing related to the acquisition request.

[0409] However, in Embodiment 1 and Embodiment 2, there is a problem in that it is effectively utilized that a plurality of servers hold the same electronic file redundantly.

[0410] Therefore, Embodiment 3 provides a distributed file management system that can actively prevent duplication of a plurality of servers and prevent tampering of electronic files by a third party. It also provides a distributed file management system that can improve the fault tolerance of servers and disks.

[0411] Embodiment 3 according to the present invention will be described with reference to Figs.

[0412] The outline of the configuration of the distributed file management system shown in FIG. 1 is the same as that of the distributed file management system according to the third embodiment. Description is omitted.

[0413] The distributed file management system according to Embodiment 3 includes terminals 60 and 65 used by a user and file storage units 25, 35, and 45, respectively, and a server that receives a user request from each terminal 60 and 65 A620, server B630, server C640, and a distributed file management device that manages electronic files distributed and held in each server by transmitting and receiving information to and from these servers. [0414] Also, the folder configuration common to the electronic files stored in the file storage unit included in each server shown in FIG. 2 is the same in the distributed file management system according to the third embodiment. A description of the folder structure is omitted here.

[0415] FIGS. 35A to 35C are diagrams showing specific examples of electronic files stored in the file storage unit included in each server according to Embodiment 3. FIG.

[0416] FIG. 35A is a diagram showing an example of the electronic file information 25b stored in the file storage unit 25 included in the server A620 according to the third embodiment. This figure shows an example in which the file storage unit 25 according to the present embodiment stores “file a” and “file b”.

[0417] FIG. 35B is a diagram showing an example of the electronic file information 35b stored in the file storage unit 35 provided in the server B630 according to Embodiment 3. This figure shows an example in which the file storage unit 35 according to the present embodiment stores “file a”, “file”, and “file e”.

[0418] FIG. 35C is a diagram showing an example of the electronic file information 45b stored in the file storage unit 45 included in the server C640 according to the third embodiment. This figure shows an example in which the file storage unit 45 according to the present embodiment stores “file b”, “file d”, and “file e”.

[0419] FIG. 36 is a block diagram illustrating an example of a functional configuration included in the Sano A620 according to the third embodiment. Server A 620 receives a request from the user as in the case of Sano A20 according to Embodiment 1, and when the user request is an acquisition request, server A 620 manages the electronic file related to the received acquisition request in As long as one of the servers below holds, it sends an electronic file containing the latest entity to the terminal used by the user. Further, unlike the server A20 according to the first embodiment, the server A620 according to the third embodiment calculates the value of the electronic file in order to detect tampering.

[0420] The server A 620 includes a file storage unit 25, a user request receiving unit 71, a request type determining unit 73, a request information holding unit 75, a holding server query unit 79, a holding response receiving unit 81, a file Transmission request receiving unit 83, file transmitting unit 85, file receiving unit 87, lock request transmitting unit 89, update notification unit 91, completion notification receiving unit 93, user request response unit 95, hash value request Receiving unit 624, hash value calculating unit 626, hash value transmitting unit 628, storage unit information An information request receiving unit 630, a storage unit information transmitting unit 632, a copy destination receiving unit 634, and a file storage control unit 677 are provided.

[0421] For the server A620 according to the third embodiment, parts having the same functions as those of the server A20 according to the first embodiment are denoted by the same reference numerals. Description is omitted.

The hash value request receiving unit 624 is a part that receives a request for a hash value of a specific electronic file from the distributed file management apparatus 610.

[0423] The hash value calculation unit 626 is a part that acquires the electronic file related to the request received by the hash value request reception unit 624 via the file storage control unit 77 and calculates the hash value of the electronic file.

The hash value transmission unit 628 is a part that transmits the hash value calculated by the hash value calculation unit 626 to the distributed file management device 610.

[0425] The storage unit information request receiving unit 630 is a part that receives information related to the state of the file storage unit 25 included in the storage unit information request, such as a request for free space.

[0426] The storage unit information transmission unit 632 sends a file storage unit 2 from a file storage control unit 677 to be described later.

This is a part that acquires information indicating the state of 5 and transmits it to the distributed file management apparatus 610.

[0427] When the electronic file related to the write request is a newly stored electronic file held in any Sano, the copy destination receiving unit 634 stores a copy of the electronic file. (Hereinafter referred to as “copy destination server”).

[0428] As a result, the electronic file related to the new storage is copied to the copy destination server, and therefore, at least two or more servers hold the same electronic file. For this reason, even if a failure occurs in any one server that holds the electronic file related to the user's acquisition request or the file storage unit of the server, the electronic file is also held in the other server. Therefore, the user can obtain the electronic file related to the request from another server.

Similarly to the file storage control unit 77 according to Embodiment 1, the file storage control unit 677 is a part that controls the file storage unit 25, and the file storage unit 25 is a specific electronic file. The file storage unit 25 stores and reads the electronic file stored in the file storage unit 25, updates the electronic file stored in the file storage unit 25, and the file storage unit. A new electronic file is stored in 25, and information indicating the state of the file storage unit 25 such as the free capacity of the file storage unit 25 is acquired.

[0430] The above is the functional configuration of the Sano A620 according to the present embodiment. Server B630 and server C640 also have the same functional configuration as server A620.

FIG. 37 is a block diagram showing an example of a functional configuration provided in the distributed file management apparatus 610 according to the third embodiment. The difference between the distributed file management apparatus 610 according to the third embodiment and the distributed file management apparatus 10 according to the first embodiment is that the distributed file management apparatus 610 according to the third embodiment has the hash of the electronic file related to the acquisition request. By obtaining the value from the server, the electronic file having the latest and correct contents is transmitted to the user, and one electronic file is managed so that at least two servers hold it.

[0432] The distributed file management device 610 includes an inquiry reception unit 102, a retention response transmission unit 106, a file transmission request unit 108, an update notification reception unit 110, a retention information update unit 112, and an update completion notification. Unit 114, lock request receiving unit 116, lock information holding unit 118, holding server storage unit 700, holding server determining unit 704, hash value requesting unit 728, hash value receiving unit 730, update permission request A receiving unit 732, a hash value initializing unit 734, an update permission transmitting unit 736, a storage unit information requesting unit 738, a storage unit information receiving unit 740, a copy destination determining unit 742, and a copy destination transmitting unit 744. Prepare.

The holding server storage unit 700 is a storage unit that stores management server information and file holding information, like the holding server storage unit 100 according to the first embodiment. The holding server storage unit 700 is realized by HD, for example.

[0434] The management server information 700a according to Embodiment 3 is the embodiment described with reference to FIG.

Since it is the same as the management server information 100a related to 1, description here is omitted.

A specific example of file retention information according to Embodiment 3 will be described with reference to FIG.

FIG. 38 is a diagram showing an example of the file holding information 700b stored in the holding server storage unit 700. As shown in the figure, the file retention information 700b according to the present embodiment is “FRAME”. It consists of “Isle pass”, “Server name”, and “Hash value”.

[0437] The "file path" and "server name" of the file holding information 700b according to the present embodiment are the "file path" of the file holding information 100b according to the first embodiment described with reference to FIG. And “server name” are stored in the same information, and detailed description thereof is omitted here.

[0438] In the "hash value", the hash value of the regular electronic file calculated in the server is stored. Here, the “regular electronic file” refers to an electronic file created or changed by a person who has authority to create or change the electronic file. In addition, the hash value according to the present embodiment is a value calculated using, for example, all or part of the electronic file as an input value using a predetermined hash function. The node function is pre-determined in common for all servers, and the input value is all or part of the electronic file. The force that is a part is also predetermined for all servers.

This figure shows that, for example, for the file a indicated by “ZdataZa”, the “hash value” is “19 32066” and the holding servers are “server A” and “server B”.

[0440] Also, as shown in this figure, all electronic files are held in two or more servers. Therefore, for example, even if a failure occurs in “server A”, file & can be obtained from “server B” and file b can be obtained as “server C”. Therefore, the fault tolerance of the entire system is improved by holding electronic files redundantly on different servers.

[0441] This force returns to the explanation of FIG.

The holding server determination unit 704 is a part that determines a server holding an electronic file related to the inquiry received by the inquiry reception unit 102 by referring to the holding server storage unit 700. When the holding server determination unit 704 according to the present embodiment determines the holding server of the electronic file related to the user acquisition request, the holding server determination unit 704 determines that the server holding the electronic file having regular contents is the holding server.

[0443] The cache value requesting unit 728 relates to the acquisition request held by the server to the server determined by the holding server determination unit 704 as a candidate for the holding server of the electronic file related to the acquisition request. This is the part that requests the hash value of the electronic file.

[0444] The nosh value receiving unit 730 is a part that receives the hash value from the server to which the hash value request unit 728 has transmitted the request.

[0445] The update permission request receiving unit 732 is a part that receives a request for permission regarding the update of the electronic file from the terminal 60 (65) used by the user when the user updates the electronic file.

[0446] When the update permission request receiving unit 732 receives the update permission request, the hash value initializing unit 734 initializes the "hash value" of the file holding information 700b corresponding to the electronic file related to the update It is. In the initialization of the hash value in this embodiment, the “hash value” is updated with “−1”.

[0447] In response to the fact that the hash value initialization unit 734 has initialized the "hash value", the update permission transmission unit 736 receives the update permission request received from the terminal 60 ( 65) is a part that transmits information whose content is to permit the update.

[0448] The storage unit information request unit 738 is a file storage unit included in each server in each server under the management of the distributed file management device 610 when the retained information update unit 112 performs an update related to new storage. This is a part that requests information indicating the status of the device (hereinafter referred to as “storage unit information”).

[0449] "Storage unit information" according to the present embodiment is, for example, information related to the free capacity of each file storage unit, and specifically, the ratio of the free capacity to the total storage capacity.

Storage unit information reception unit 740 is a part that receives storage unit information transmitted from each server in response to a request from storage unit information request unit 738.

The copy destination determination unit 742 is a part that determines a copy destination server based on the storage unit information received by the storage unit information reception unit 740. Copy destination determination unit 742 according to the present embodiment sets the server having the largest percentage of free space included in the storage unit information as the copy destination server.

[0452] The copy destination transmission unit 744 is a part that transmits information regarding the server determined as the copy destination server by the copy destination determination unit 742 to the access source server.

[0453] Distributed file management device 610 and each server 620, 630, 640 power S By providing the same as in the first embodiment, the user can select one of the servers 620, 630, and 640 electronically regardless of which server is accessed from the terminal 60 or 65 used by the user. As long as the file is held, the electronic file can be obtained.

[0454] Also, as in the second embodiment, the same electronic file held by a plurality of servers has a synchronization power S, so that the user can hold the electronic file having the latest contents on any server. In addition, it is possible to obtain an electronic file having the latest contents by accessing an arbitrary server.

[0455] Further, since at least two servers hold the same electronic file, even if one holding server or the storage unit of the holding server fails, the electronic file can be transferred from another holding server. It is possible to improve the fault tolerance of the entire system.

[0456] Furthermore, the distributed file management device 610 holds the hash value of each file. Therefore, it is possible to determine whether or not the electronic file held by each server is legitimate by referring to the no-shake value and to prevent unauthorized rewriting of the electronic file.

[0457] FIG. 39 shows a time indicating an example of processing executed in each device constituting the distributed file management system according to the third embodiment of the present invention when the user transmits an acquisition request from the terminal device. It is a chart.

The “terminal”, “access source server”, and “holding server” shown in this figure are the same as those in FIG. Therefore, the explanation here regarding these is omitted.

[0459] First, the user request receiving unit 71 of the access source server 20 (30, 40) receives the acquisition request transmitted also by the terminal 60 (65) force used by the user via the communication line 50 (S401). ). Here, the “acquisition request” is an electronic file that is specified by the user, and is information that includes a request that the terminal that the user uses the electronic file having the latest contents acquires.

Next, the request type determination unit 73 acquires the request received by the user request reception unit 71 and determines whether the request is an “acquisition request” or a “write request”. Since this figure is a time chart of processing related to an acquisition request, this determination is omitted. Subsequently, the file storage control unit 677 refers to its own file storage unit 25 to determine whether or not its own file storage unit 25 stores and holds the electronic file related to the acquisition request. (S402).

[0462] If it is determined that the electronic file is held! /, (No in S402), then the holding server inquiry unit 79 inquires the distributed file management device 10 about the holding server, and receives the inquiry reception unit 102. Accepts the query of the holding server (S403).

Subsequently, the holding server determination unit 704 performs the file holding information 10 of the holding server storage unit 100.

By referring to Ob, it is determined whether there is a holding server other than the access source server (S404).

[0464] If it is determined that there is no holding server other than the access source server (No in S404), then the holding response transmission unit 106 transmits a non-holding notification, and the holding response receiving unit 81 receives the non-holding notification. (S405).

[0465] Subsequently, when the user request response unit 95 acquires the non-holding notification via the file storage control unit 77, the user request response unit 95 transmits the non-holding notification to the terminal 60 (65) that transmitted the acquisition request (S406). End the process.

[0466] If it is determined that there is a holding server other than the access source server (Yes in S404), the hash value request unit 728 subsequently sends a request for the hash value of the electronic file related to the acquisition request to the holding server. Then, the hash value request receiving unit 624 of the holding server receives the request for the hash value (S407).

[0467] Subsequently, the hash value calculation unit 626 causes the file storage control unit 677 to acquire the electronic file related to the acquisition request from the file storage unit 25, acquires the electronic file from the file storage control unit 677, and The hash value of the electronic file is calculated (S408).

[0468] Subsequently, the hash value transmitting unit 628 transmits the hash value calculated by the hash value calculating unit 626, and the hash value receiving unit 730 receives the hash value (S409).

[0469] Subsequently, the holding server determination unit 704 determines whether the hash value included in the file holding information 70 Ob of the holding server storage unit 700 matches the hash value received by the hash value receiving unit 730. Whether or not the electronic file held by the holding server is valid is determined based on whether or not (S410). [0470] If the hash value included in the file holding information 700b does not match the hash value received by the hash value receiving unit 730, the holding server determining unit 704 determines that it is not normal (S41 ( TCNo).

[0471] In this case, subsequently, the holding response transmission unit 106 transmits a non-holding notification, and the holding response receiving unit

81 receives the non-holding notification (S411).

[0472] Subsequently, when the user request response unit 95 acquires the non-holding notification via the file storage control unit 677, the user request response unit 95 transmits the non-holding notification to the terminal 60 (65) that transmitted the acquisition request (S412). End processing.

[0473] If the hash value included in the file holding information 700b matches the hash value received by the hash value receiving unit 730, the holding server determining unit 704 determines that it is authentic ( Yes in S410).

[0474] In this case, subsequently, the file transmission request unit 108 transmits a file transmission request to the holding server, and the file transmission request receiving unit 83 receives the file transmission request (S413). Here, the “file transmission request” is a request transmitted to the holding server with the content of transmitting the electronic file related to the user acquisition request to the access source server.

[0475] Subsequently, in response to the file transmission request received by the file transmission request unit 108, the file storage control unit 677 reads the electronic file related to the user acquisition request by the file storage unit (S414).

[0476] Subsequently, the file transmission unit 85 of the holding server transmits an electronic file related to the user's acquisition request, and the file reception unit 87 of the access source server receives the electronic file (S415).

Subsequently, the file storage control unit 677 of the access source server stores the electronic file received by the file reception unit 87 in its own file storage unit 25 (S416).

Subsequently, the user request response unit 95 of the access source server acquires the electronic file related to the user acquisition request from the file storage control unit 677 and transmits it to the terminal 60 (65) used by the user (S417). ).

Subsequently, the update notification unit 91 of the access source server performs the storage process of the file storage control unit 677.

In response to the completion of (S416), an update notification is transmitted, and the update notification receiving unit 110 updates. A notification is accepted (S418).

[0480] Subsequently, the holding information update unit 112 updates the file holding information 700b of the holding server storage unit 700 according to the update notification acquired from the update notification receiving unit 110 (S419), and ends the process.

[0481] If it is determined that the electronic file is held! / ヽ (Yes in S402), then the hash value calculation unit 626 calculates the hash value of the electronic file (S420).

[0482] Subsequently, the hash value transmission unit 628 transmits the hash value calculated by the hash value calculation unit 626, and the hash value reception unit 730 receives the hash value (S421).

[0483] Subsequently, the holding server determination unit 704 determines whether or not the electronic file held by the holding server is authentic, similarly to the determination processing in S410 (S422).

[0484] If the holding server determination unit 704 determines that it is legitimate (Yes in S422), then the holding response transmission unit 106 transmits a holding notification to the access source server, and the holding response receiving unit 81 holds the holding notification. Is received (S423).

[0485] Subsequently, the file storage control unit 677 receives the holding notification received by the holding response receiving unit 81, and reads the electronic file related to the user acquisition request from the file storage unit 25 (S4).

twenty four).

[0486] Subsequently, the user request response unit 95 acquires the electronic file related to the user's acquisition request from the file storage control unit 677, and transmits it to the terminal 60 (65) used by the user (S425). The server ends the process.

[0487] If the holding server determination unit 704 determines that it is not legitimate (No in S410), the holding server determination unit 704 continues the file of the holding server storage unit 100 in the same manner as the determination process in S404. By referring to the holding information 100b, it is determined whether there is a holding server other than the access source server (S426).

[0488] If it is determined that there is no holding server other than the access source server (No in S426), continue

The holding response transmitting unit 106 transmits a non-holding notification, and the holding response receiving unit 81 receives the non-holding notification (S427).

[0489] Subsequently, when the user request response unit 95 acquires the non-holding notification via the file storage control unit 677, the user request response unit 95 transmits the non-holding notification to the terminal 60 (65) that transmitted the acquisition request (S428). The The access source server ends the process.

[0490] If it is determined that there is a holding server other than the access source server (Yes in S426), then, as with S407, the nose value sending unit 628 requests a hash value request from the hash value requesting unit 728 and the holding server. The receiving unit 624 sends and receives a request for the hash value of the electronic file related to the acquisition request (S429).

[0491] The processing after S430 shown in the figure is the same as the processing after S408 described above. Specifically, the processing from S430 force to S432 is the same as the processing from S408 force to S410, and the processing from S427 and S428 is the same as the processing from S411 and S412, respectively. The processing up to S437 is the same as the processing from S413 force to S417. Therefore, the description here regarding these processes is omitted.

FIG. 40 is a time chart showing an example of processing executed in each device constituting the distributed file management system according to Embodiment 3 of the present invention when the user transmits a terminal capability storage request. .

[0493] The "terminal" and the "access source server" shown in the figure are the same as the "terminal" and the "access source server" shown in FIG. 8, respectively, and thus description thereof is omitted here.

The “copy destination server” shown in the figure is a server that is determined by the distributed file management apparatus 610 as the copy destination of the electronic file related to the new storage. The copy destination server in this embodiment is one of server A620, server B630, and server C640.

First, the user request receiving unit 71 of the access source server 20 (30, 40) receives the storage request transmitted from the terminal 60 (65) used by the user via the communication line 50 (S501). ). Here, the “storage request” is information that includes a request for causing the access source server to hold a new electronic file.

[0496] Subsequently, the request type determination unit 73 acquires the request received by the user request reception unit 71, and the request is a difference between the "acquisition request", the "write request", and the "storage request". Determine whether. Since this figure is a time chart of processing related to a storage request, this determination is omitted.

[0497] Subsequently, the request type determining unit 73 causes the request information holding unit 75 to hold the electronic file related to the storage request (S502).

[0498] Next, first, the lock request transmission unit 89 requests that the acquired request is a write request. In response to the determination of the type determining unit 73, a lock request is transmitted to the distributed file management apparatus 10, and the hack request receiving unit 116 receives the lock request (S503).

Subsequently, the lock request receiving unit 116 causes the lock information holding unit 118 to hold information related to the electronic file related to the received lock request. Thus, the electronic file write request related to the lock request is locked (S504).

[0500] Further, the file storage control unit 677 determines that the acquired request is a storage request! /, And receives the determination of the request type determination unit 73, and receives the electronic file held by the request information holding unit 75. Acquire and newly store the acquired electronic file in its own file storage unit 25, 35, 45

(S505).

[0501] Subsequently, the hash value calculation unit 626 calculates a hash value of the newly stored electronic file (S506).

Subsequently, the update notification unit 91 transmits an update notification and a hash value to the distributed file management device 10, and the update notification reception unit 110 of the distributed file management device 10 receives the update notification and the hash value (S507). ).

Subsequently, the holding information update unit 112 updates the file holding information 700b in the holding server storage unit 700 according to the update notification and the hash value acquired from the update notification receiving unit 110 (S508).

[0504] Subsequently, the retained information update unit 112 releases the lock by deleting the information retained by the lock information retaining unit 118 (S509).

Subsequently, the update completion notification unit 114 receives the completion notification from the file storage control unit 677, notifies the access source server of the completion of the update process, and the access source server completion notification reception unit 93 is completed. Is received (S510).

[0506] Subsequently, the user request response unit 95 of the access source server receives that the completion notification receiving unit 93 has received the notification of completion, and that the user has completed processing related to the user's write request. Transmit to the terminal 60 (65) to be used (S511). As a result, the processing executed between the terminal 60 (65) and the access source server ends.

[0507] Following the transmission of the completion notification by the update completion notification unit 114 in S510, the distributed file management apparatus 610 allows the copy destination determination unit 742 to set the free space in the file storage unit of each server. Based on this, a copy destination server is determined (S512). Details of this processing will be described later.

[0508] Subsequently, the copy destination sending unit 744 sends a request to the copy source server to send the electronic file newly stored by the access source server to the copy source server, and the copy destination receiving unit 634 sends the request for this file. A transmission request is received (S513).

Subsequently, the file storage control unit 677 reads out the newly stored electronic file from its own file storage unit 25 (S514).

[0510] Subsequently, the file transmission unit 85 of the access source server transmits the newly stored electronic file to the copy destination server, and the file reception unit 87 of the copy destination server receives the newly stored electronic file (S515). .

Subsequently, the file storage control unit 677 of the copy destination server newly stores the electronic file received by the file receiving unit 87 in the file storage unit 35 (S516).

[0512] Subsequently, the update notification unit 91 of the copy destination server transmits an update notification to the distributed file management apparatus 610, and the update notification reception unit 110 receives the update notification (S517).

Subsequently, the holding information update unit 112 updates the file holding information 700b in the holding server storage unit 700 according to the update notification acquired from the update notification receiving unit 110 (S518), and ends the process.

FIG. 41 is a detail of the copy destination determination process (S512) shown in FIG. 40, and shows an example of the process executed in each device constituting the distributed file management system according to the third embodiment of the present invention. It is a time chart which shows.

[0515] First, the storage unit information request unit 738 is a server, that is, a server in this embodiment.

A storage unit information transmission request is transmitted to A620, server B630, and server C640, and storage unit information request reception unit 630 of each server receives the transmission request (respectively, as S551 and

, Corresponding to S552 and S553. ).

[0516] Subsequently, the file storage control unit 677 of the server A620 acquires or calculates storage unit information by referring to its own file storage unit 25 (S554).

[0517] Similarly, the file storage control units 677 of the server B630 and the server C640 also acquire storage unit information (corresponding to S555 and S556, respectively).

[0518] Subsequently, the storage unit information receiving unit 740 includes each server, that is, the server in this embodiment. Storage unit information about the file storage unit 25, the file storage unit 35, and the file storage unit 45 of each server (S557, S558, respectively) Corresponds to S559.) ₀

Subsequently, the copy destination determination unit 742 determines whether or not storage unit information has been received from all servers managed by the distributed file management device 610 (S560).

[0520] If there is even one server that has not received storage unit information, it is determined that storage unit information has not been received from all servers (No in S560), and copy destination determination unit 742 waits.

[0521] If it is determined that storage unit information has been received from all servers (Yes in S560), the copy destination determination unit 742 determines a copy destination server based on the acquired storage unit information (S561).

[0522] The above is the process executed by each device constituting the distributed file management system according to Embodiment 3 of the present invention when the user transmits a terminal capability storage request. Subsequently, assuming that the initial state of the file holding information 700b is the content shown in FIG. 38, when the user sends a storage request for the file f from the terminal manager to the server A620, the third embodiment of the present invention The processing executed in each device constituting the distributed file management system will be described more specifically.

[0523] First, the user request receiving unit 71 of the server A620 receives the storage request for the file f transmitted from the terminal 60 (65) used by the user via the communication line 50 (S501).

[0524] Subsequently, the request type determination unit 73 acquires the request received by the user request reception unit 71, and determines that the request power S is “storage request”. Subsequently, the request type determination unit 73 causes the request information holding unit 75 to hold the file f related to the storage request (S502).

[0525] Subsequently, first, the lock request transmission unit 89 transmits a lock request to the distributed file management device 10 in response to the determination by the request type determination unit 73 that the acquired request is a write request, and the request is received. The lock request receiving unit 116 receives the lock request (S503), and causes the lock information holding unit 118 to hold information on the electronic file related to the received lock request. As a result, the request to write file f is locked (S504).

[0526] The file storage control unit 677 receives the determination by the request type determination unit 73 that the acquired request is a storage request, acquires the electronic file held by the request information holding unit 75, and acquires the acquired electronic file. The electronic file is newly stored in its own file storage unit 25 (S505). [0527] Subsequently, the hash value calculation unit 626 calculates a hash value of the newly stored electronic file (S506). It is assumed that the hash value of the file f calculated here is “1814680”.

[0528] Subsequently, the update notification unit 91 transmits the update notification and the hash value to the distributed file management device 10, and the update notification reception unit 110 of the distributed file management device 10 receives the update notification and the hash value (S507). ).

Here, FIG. 42 shows the retained server storage unit 700 updated according to the update notification and the hash value transmitted from the server A 620 when the user transmits an update request for the file f from the terminal 60 to the server A 620. It is a figure which shows the example of the file holding information 700c.

[0531] The difference between the file retention information 700c shown in this figure and the initial state of the file retention information 700b shown in Fig. 38 is that in the file retention information 700c, the "file path" is "ZdataZf" and the "hash value" is " 1814680 ”and the information that“ Server name ”is“ Server A ”is added.

[0532] After updating the file holding information in this way (S508), the holding information updating unit 112 releases the lock (S509), and the update completion notification unit 114 and the completion notification receiving unit 93 of the access source server are notified of completion. (S510), the user request response unit 95 of the access source server transmits to the terminal 60 (65) used by the user that processing related to the user's write request has been completed (S511).

[0533] Subsequently, the distributed file management apparatus 610 determines a copy destination server (S512).

[0534] In the copy destination determination process (S512), transmission / reception of the storage unit information transmission request (from S551)

S553), storage unit information acquisition processing (S554 to S556), and storage unit information transmission / reception processing (S557 to S559) are executed.

[0535] Subsequently, the copy destination determination unit 742 waits until it receives storage unit information from all servers.

If the storage unit information is received from all servers (No in S560) (Yes in S560), the copy destination server is determined based on the acquired storage unit information (S561).

Here, it is assumed that the storage unit information acquired by the copy destination determination unit 742 has the contents shown in FIG. A specific example of determining a copy destination server will be described as an example.

FIG. 43 is a diagram showing a specific example for explaining the storage unit information. In the present embodiment, each ratio described in the “vacant ratio” is storage unit information of each file storage unit 25, 35, 45 provided in each server. The “free ratio” is a percentage of the total free capacity of each file storage unit. The file storage control unit 677 performs the acquisition of the free capacity and the total capacity of the file storage unit and the calculation of the free rate (S554 to S556).

In this figure, for example, the “storage unit total capacity” of the file storage unit 25 included in “server A” is “1 84256 MB” (Mega Byte), and the “storage unit free space” is “120789 MB”. For this reason, “Free Space” is “66%”, which is 120789 divided by 184256.

[0539] In this figure, the "free ratio" corresponding to "server B" is "73%", which is the largest among the servers.

[0540] Therefore, when the empty ratio is the content shown in the figure, the copy destination determination unit 742 displays "server

BJ is determined as the copy destination server (S561).

[0541] When the copy destination server is determined in this way, the copy destination sending unit 744 and the copy destination receiving unit 634 of the server A620 that is the access source server transmit and receive a request to send the file f to the server B630. (S513).

[0542] Subsequently, the file storage control unit 677 reads the file f from its own file storage unit 25 (S514), and the file transmission unit 85 of the server A620 and the file reception unit 87 of the server B630 transmit and receive the file f. (S 515).

[0543] Subsequently, the file storage control unit 677 of the server B630 stores the file f in the file storage unit 35 (S516), and the update notification unit 91 and the update notification reception unit 110 of the server B630 transmit and receive an update notification ( S517).

[0545] Here, Fig. 44 shows an example of the file holding information 700d in the holding server storage unit 700 after the processing in each device is completed when the user transmits an update request for the file f from the terminal 60 to the server A620. FIG. [0546] In the file holding information 700d shown in this figure, the "server name" associated with the information whose "file path" is "ZdataZf" is assigned to "server A" of the file holding information 700c shown in FIG. In addition, “Server B” is stored! RU

[0547] The above is the processing that is executed by each device configuring the distributed file management system according to Embodiment 3 of the present invention when the user transmits a terminal capability update request. Next, processing executed in each device constituting the distributed file management system according to Embodiment 3 of the present invention when the user transmits a terminal capability update request will be described.

[0548] FIG. 45 is a time chart showing an example of processing executed in each device constituting the distributed file management system according to Embodiment 3 of the present invention when the user transmits a terminal capability update request. .

First, the update permission request receiving unit 732 receives a request for permission to update a specific electronic file from the terminal 60 (65) used by the user (S601).

[0550] Subsequently, the hash value initialization unit 734 initializes the hash value of the file holding information 700b associated with the electronic file included in the request received by the update permission request reception unit 732 (S602). .

Here, FIG. 46 is a diagram illustrating an example of the file holding information 700e in which the hash value is initialized when the distributed file management apparatus 610 according to Embodiment 3 receives the update permission request.

[0552] This figure shows that the file retention information 700b before the hash value is initialized has the content shown in FIG. An example of updating 700b is shown.

In the present embodiment, hash value initialization unit 734 performs “hash value related to update permission request”.

“1” is stored in “” to initialize the value.

In this figure, since it is an update permission request for file b, “1” is stored in “nosh value” of file b whose “file path” is “ZdataZb”!

[0555] Here, let us return to the explanation of FIG.

[0556] Subsequently, the update permission transmission unit 736 sends an update permission request to the terminal 60 (65) used by the user. The solicitation / reception unit 732 transmits permission to update the requested electronic file (S603).

Subsequently, the user request receiving unit 71 of the access source server 20 (30, 40) receives the update request transmitted from the terminal 60 (65) used by the user via the communication line 50 (S201).

). Here, the “update request” is information including a request for updating an electronic file held by the access source server.

Subsequently, the request type determination unit 73 acquires the request received by the user request reception unit 71, and whether the request is a difference between “acquisition request”, “update request”, and “storage request”. Judging. Since this diagram is a time chart of processing related to the update request, this determination is omitted.

Subsequently, the request type determining unit 73 causes the request information holding unit 75 to hold the electronic file related to the update request (S605).

The subsequent lock request transmission / reception processing (S606) and lock processing (S607) are the same as the lock request transmission / reception processing (S203) and lock processing (S204) shown in FIG. Therefore, the explanation here regarding these is omitted.

[0561] Subsequently, the file storage control unit 677 obtains the electronic file held by the request information holding unit 75 in response to the determination by the request type determining unit 73 that the acquired request is an update request. Then, the electronic file stored in its own file storage unit 25, 35, 45 is updated by the acquired electronic file (S608).

[0562] Subsequently, the file storage control unit 677 determines whether or not the update has been completed (S609).

[0563] First, when it is determined that the update has been completed (No in S609), the hash value calculation unit 626 waits.

[0564] If it is determined that the update has been completed (Yes in S609), the hash value calculation unit 626 acquires a new electronic file related to the update from the file storage control unit 677, and hashes the electronic file. The value is calculated (S610).

[0565] Subsequently, the update notification unit 91 of the access source server and the update notification reception unit 110 of the distributed file management device 610 are similar to the processing in S507 and S508 shown in Fig. 40. The holding information update unit 112 subsequently updates the file holding information 700b of the holding server storage unit 700 according to the update notification and the hash value acquired from the update notification receiving unit 110. (S612). [0566] FIG. 47 shows an example of file retention information after execution of the electronic file update process related to the request in the third embodiment when the user transmits a terminal capability update request. FIG. This figure shows an example in the case where the file b is updated, and shows an example in which the “nosh value” of the new file b is “3417510”.

[0567] Here, let us return to the explanation of FIG.

[0568] Subsequently, from the unlocking process (S613) by the retained information updating unit 112, the user request response unit 95 of the access source server transmits the completion notification to the terminal 60 (65) used by the user (S615). ) Is the same as the processing from S509 to S511 shown in FIG. 40, and the description is omitted here.

[0569] Subsequently, the holding server determination unit 704 extracts the holding server in response to the update of the file holding information 500b by the holding information update unit 112 (S616).

Subsequently, the file transmission request unit 108 transmits a file transmission request to the access source server, and the file transmission request reception unit 83 of the access source server 320 receives the file transmission request (S617).

Subsequently, the file storage control unit 677 reads the electronic file related to the file transmission request from its own file storage unit 25 (S618).

[0572] Subsequently, the file transmitting unit 85 of the access source server 320 transmits the electronic file read by the file storage control unit 677 to the holding server, and the file receiving unit 87 of the holding server receives the electronic file (S619). ).

Subsequently, the file storage control unit 677 of the holding server updates the electronic file stored in its file storage unit 25 by the electronic file received by the file receiving unit 87.

(S620).

In the third embodiment, examples of the input screen and the result display screen displayed on the monitor connected to the terminal 60 (65) used by the user are shown in FIGS. 16 to 18 in the first embodiment. This is the same as the example of the input screen and the result display screen described with reference to FIG. Therefore, the explanation here is omitted.

[0575] The power described above for the distributed file management device and the distributed file management system according to Embodiment 3 of the present invention is not limited to this embodiment. Yes.

For example, in this embodiment, “storage unit information” is “ratio of free space” of the storage unit, but “storage unit information” may be “free space” itself.

[0577] Also, for example, in this embodiment, the hash value is initialized by storing "1" in the "hash value" of the file holding information 700e as shown in FIG. Therefore, the value stored in the hash value is not limited to “1”, and any value that cannot be taken as a hash value may be used. A NULL value may be stored.

[0578] (Embodiment 4)

As described in the first to third embodiments, in the distributed file management system according to the present invention, a distributed file management apparatus is indispensable for processing a user request related to an electronic file. For this reason, if the distributed file management device does not function due to a failure or the like, the user's request for the electronic file cannot be processed, and therefore the distributed file management system does not function.

[0579] Thus, Embodiment 4 provides a distributed file management system with excellent fault tolerance.

[0580] Embodiment 4 according to the present invention will be described with reference to Figs. 48 to 62.

FIG. 48 is a diagram showing an outline of the configuration of the distributed file management system according to the fourth embodiment of the present invention. The distributed file management system according to the fourth embodiment is a system that responds to a user request regarding an electronic file regardless of which access server is the same as in the first to third embodiments.

[0582] The distributed file management system according to the present embodiment includes server A820, server B830, and server C840, and terminal a60 and terminal b65 connected via communication line 50. Regarding the elements constituting the distributed file management system according to the present embodiment, elements having the same functions as those constituting the distributed file management system according to the first embodiment are denoted by the same reference numerals. The explanation of these elements is omitted.

[0583] Each of the servers 820, 830, and 840 according to the present embodiment has a function of a distributed file management apparatus that manages electronic files held in each server, and also stores electronic files. It also has a file server function that accepts user requests and responds to requests in cooperation with the distributed file management device or other servers when user requests are received.

[0584] One of the servers functions as a distributed file management device. In this embodiment, the order in which servers are distributed file management apparatuses is determined in advance, and the server having the highest rank among operating servers functions as the distributed file management apparatus. As a result, even if a server functioning as a distributed file management device stops operating due to a failure, other servers can become distributed file management devices, improving fault tolerance. It becomes.

In the present embodiment, a server functioning as a distributed file management device is referred to as a “management device server”.

[0586] Each server includes a file storage unit for storing and holding electronic files. The Sano A820 according to this embodiment includes a file storage unit 25, and the server B830 includes a file storage unit 35. The C840 includes a file storage unit 45.

[0587] Here, also in the distributed file management system according to the fourth embodiment, the file storage unit included in each server stores the same electronic file folder structure. Specifically, FIG. The folder structure is the same as that shown in FIG. Therefore, the explanation here regarding the folder structure is omitted.

[0588] A specific example of the electronic file stored in each file storage unit 25, 35, 45 according to Embodiment 4 will be described with reference to the drawings.

49A to 49C are diagrams showing specific examples of electronic files stored in the file storage unit included in each server according to Embodiment 4. FIG.

FIG. 49A is a diagram showing an example of the electronic file information 25d stored in the file storage unit 25 provided in the server A820 according to the fourth embodiment. This figure shows an example in which the file storage unit 25 according to the present embodiment stores “file a” and “file b”.

FIG. 49B is a diagram showing an example of the electronic file information 35d stored in the file storage unit 35 provided in the server B830 according to Embodiment 4. This figure shows an example in which the file storage unit 35 according to the present embodiment stores “file a”, “file”, and “file e”. FIG. 49C is a diagram showing an example of the electronic file information 45d stored in the file storage unit 45 provided in the server C840 according to the fourth embodiment. This figure shows an example in which the file storage unit 45 according to the present embodiment stores “file d”.

[0593] Next, an example of a functional configuration included in each server will be described with reference to the drawings by taking the server A820 as an example.

FIG. 50 is a block diagram showing an example of an outline of a functional configuration provided in the server A820 according to the fourth embodiment. Server A has both the function of a file server that holds electronic files and the function of a distributed file management device that manages electronic files held by multiple file servers.

The server A 820 includes a file server unit 900, a management device unit 910, and a management device determination unit 920.

The file server unit 900, the management device unit 910, and the management device determination unit 920 are connected to each other via an internal bus (not shown). Therefore, each part of the file server unit 900, the management device unit 910, and the management device determination unit 920 transmits and receives information through the internal bus inside the server A820. Details of the parts included in the file server unit 900, the management device unit 910, and the management device determination unit 920 will be described later.

[0597] In addition, the file server unit 900, the management device unit 910, and the management device determination unit 920 transmit and receive information to and from the terminals 60 and 65 or other servers via the communication line 50.

The file server unit 900 is a part that realizes a function as a file server. That is, the file server unit 900 receives a user request or a request transmitted from the management apparatus server. Then, the file server unit 900 executes processing corresponding to these received requests.

[0599] The management device unit 910 is a part that realizes a function as a distributed file management device. In other words, the management device unit 910 manages information related to the electronic files held by the server A820, the server B830, or the server C840, and when the server A820 is a management device server, Inquiries from are accepted.

[0600] The management device determination unit 920 transmits / receives information to / from the management device determination unit provided in another server. This is a part for determining the management device server based on! /.

[0601] The above is the outline of the functional configuration of the Sano A820 according to the present embodiment. Next, details of the functions of each part will be described with reference to the drawings.

[0602] FIG. 51 is a diagram showing an example of the functional configuration of the file server unit 900 of the Sano A820 according to the fourth embodiment.

[0603] The file server unit 900 includes a file storage unit 25, a user request receiving unit 71, a request type determining unit 73, a request information holding unit 75, a file storage control unit 77, a holding response receiving unit 81, File transmission request reception unit 83, file transmission unit 85, file reception unit 87, lock request transmission unit 89, completion notification reception unit 93, user request response unit 95, holding server inquiry unit 1079, update And a notification unit 1091, which transmit / receive information to / from the management device unit 910 and the management device determination unit 920 via an internal bus (not shown) as described above.

[0604] For each part of the file server unit 900 according to the present embodiment, parts having the same functions as the parts provided in the server according to the first embodiment shown in FIG. Here, detailed description of each of these parts is omitted.

[0605] The holding server query unit 1079 is similar to the holding server query unit 79 according to the first embodiment. This is the part that makes an inquiry to the management device 910 via the communication line 50. Unlike the holding server inquiry unit 79 according to the first embodiment, the holding server inquiry unit 10 79 inquires of the management apparatus 910 about the holding server in accordance with an instruction acquired from the file storage control unit 77.

The update notification unit 1091 is a part that notifies each server of the stored or updated content when the file storage control unit 77 stores or updates an electronic file. As a result, all the servers can hold the latest information on the holding server.

FIG. 52 is a diagram showing an example of details of the functional configuration of the management device unit 910 and the management device determination unit 920 of the server A820 according to the fourth embodiment.

First, the management device unit 910 includes an inquiry reception unit 102, a retention server determination unit 104, a retention response transmission unit 106, a file transmission request unit 108, an update notification reception unit 110, and a retention information update. New section 112, update completion notifying section 114, lock request receiving section 116, lock information holding section 11 8 and the holding server storage unit 1000, which transmit / receive information to / from the file server unit 900 and the management device determination unit 920 via an internal bus (not shown) as described above.

[0609] For each part included in the management apparatus unit 910 according to the present embodiment, the same part as each part included in the distributed file management apparatus 10 according to the first embodiment shown in FIG. Reference numerals are attached, and detailed descriptions of these parts are omitted here.

[0610] The holding server storage unit 1000 is a storage unit that stores management server information and file holding information, similar to the holding server storage unit 100 of the first embodiment, and is realized by, for example, HD. . The content of each information is different from the holding server storage unit 100 of the first embodiment. Details of each information will be described with reference to the drawings.

Here, FIG. 53 is a diagram showing an example of the management server information 1000a stored in the holding server storage unit 1000 according to Embodiment 4. The management server information 1000a includes information indicating the order in which each server functions as a distributed file management apparatus, in addition to information for specifying a server set as a management target.

[0612] The management server information 1000a shown in this figure is composed of "Sano name", "IP address", and "rank". “Server name” and “IP address” are the same as “Sano name” and “IP address” according to the first embodiment, respectively, so description thereof will be omitted.

[0613] "Order" includes the order in which each server functions as a distributed file management device.

[0614] This figure shows, for example, that the “IP address” of the server whose “server name” is “server A” is “192. 1”.

68. XXX. 1 ”, including management server information whose“ rank ”is“ 3 ”.

[0615] Also, regarding "ranking", "Server B" is "1", "Server C" is "2", and "Server A" is "3". This is because “Server B” first becomes the management device server, and if “Server B” stops operating, then “Server C” becomes the management device server, and “Server C” also becomes active. When stopped, it indicates that “Server A” is the management device server. Such order is determined in advance by the administrator of the distributed file management system according to the present embodiment. Next, FIG. 54 is a diagram showing an example of the file holding information 1000b stored in the holding server storage unit 1000 according to Embodiment 4. The “file path” and “server name” of the file holding information 1 000b according to the present embodiment are the “file path” of the file holding information 100b according to the first embodiment described with reference to FIG. Since “server name” and the same information are stored, detailed description is omitted here.

[0617] This figure is an example including file holding information indicating that "server A" and "server B" hold an electronic file whose "file path" is "ZdataZa", for example. .

Next, the management device determination unit 920 shown in FIG. 52 will be described.

[0619] The management device determination unit 920 includes a management device holding unit 1200, a management device notification unit 1202, a management device notification reception unit 1204, a change determination unit 1206, a management device determination unit 1208, and a holding server information acquisition. A unit 1210, a server response unit 1212, and a server response reception unit 1214.

The management device holding unit 1200 is a part that holds information for specifying the current management device server (hereinafter, “management device information” t).

[0621] The management device notification unit 1202 refers to the management device holding unit 1200 to determine whether or not the server provided with the management device notification unit 1202 is a management device server, and the server including the management device notification unit 1202 is the management device server In this case, it is a part for notifying that a server provided with each server is a current management device server at a predetermined time interval.

[0622] Here, when the information indicating the server including the management apparatus holding unit 1200 is stored in the management apparatus holding unit 1200, the management apparatus notification unit 1202 determines that the server including the management apparatus notification unit 1202 is the management apparatus server. It is determined that the information indicating the server including itself is not stored in the storage unit 1200, and in this case, the server including itself is not the management apparatus server.

[0623] The management device notification accepting unit 1204 is a part that accepts notification from the management device notification unit 1202 of the management device server.

[0624] The change determination unit 1206 is a part that determines whether or not the management device server needs to be changed based on the notification received by the management device notification reception unit 1204.

[0625] Specifically, first, the change determination unit 1206 determines that the transmission source of the response received by the management device notification reception unit 1204 is in order from the server indicated by the information held by the management device holding unit 1200. If the server is higher in rank, it is determined that a change is necessary. At this time, the management server information 1000a in the holding server storage unit 1000 is referred to in order to determine the order. As described above, the response from the server having higher rank than the server indicated by the information held by the management device holding unit 1200 is accepted when the downed server is recovered. Therefore, each server can detect the recovery of the server that was down.

Next, change determination section 1206 determines that a change is necessary when a predetermined time has elapsed without management apparatus notification reception section 1204 receiving the notification. In this way, the management device notification accepting unit 1204 does not accept the fixed-time notification when the operation of the server is stopped, for example, when a failure occurs in the management device server. Therefore, each server can detect the operation stop of the management apparatus server.

[0627] When the change determination unit 1206 determines that the server functioning as the distributed file management device needs to be changed, the management device determination unit 1208 assigns the next management device server to the holding server storage unit 1000. Information that is determined by referring to the management server information 1000a and that identifies the determined server is stored in the management device holding unit 1200. Here, the management device determination unit 1208 determines the server with the highest rank in the management server information 1000a among the servers in operation as the next management device server.

[0628] The holding server information acquisition unit 1210 stores the holding server storage when the management device determination unit 1208 determines a server because the change determination unit 1206 determines that the management device server needs to be changed due to server recovery. Get the file holding information 1000b of the copy 1000.

Server response unit 1212 is a part that responds to the management device server according to the determination of change determination unit 1206 when management device notification reception unit 1204 receives the notification.

[0630] First, when the change determination unit 1206 determines that there is no need for a change, the server response unit 1212 responds to the transmission source of the notification received by the management device notification reception unit 1204.

[0631] In addition, when the change determination unit 1206 determines that the management device server needs to be changed due to the server recovery, the server response unit 1212 sends the retained server information to the server determined by the management device determination unit 1208. The acquisition unit 1210 sends a response including the file holding information 1000b acquired.

[0632] The server response reception unit 1214 receives the response transmitted from the server response unit 1212 of another server. It is a part that accepts answers.

[0633] If the file holding information 1000b is included in the received response, the server response receiving unit 1214 uses the file holding information 1000b to store the file holding information 1000b of its own holding server storage unit 1000. Update.

[0634] The file holding information 1000b is included in the response when a failure has occurred in the server that received the response. While the failure occurred, the file retention information 1000b held by the server cannot be updated, so the contents may be out of date. Thus, by updating the file holding information 1000b when the server is restored, the restored server can immediately function correctly as a management apparatus server.

[0635] The above is the functional configuration of the Sano A820 according to the present embodiment. The functional configuration of the server A820 described here is common except that the file storage unit 25 of the file server unit 900 is the file storage unit 35 in the server B830 and the file storage unit 45 in the server C840. . Therefore, description of the functional configuration of the server B830 and the server C840 is omitted.

Next, processing executed in the distributed file management system according to the present embodiment will be described with reference to the drawings.

[0637] FIG. 55 is a time chart showing an example of processing executed in each device constituting the distributed file management system according to Embodiment 4 of the present invention when the user transmits a terminal capability acquisition request. .

In this embodiment, the management server information 1000a has the contents shown in FIG. 53. Therefore, “Server B” having the highest order is the management device server, and the management device holding unit 1200 of each server has “ It is assumed that information indicating “Server B” is held.

[0639] "Terminal" shown in the figure is a terminal used by the user, and in this embodiment, is either terminal a60 or terminal b65. Furthermore, this figure shows an example in which server A820 is the access source server.

Therefore, in this figure and the explanation of this figure, the process of “Server A” 820 is a process executed by “Accessing Server”, and the process of “Server B” 830 is executed by “Management Device Sano”. This process. [0641] First, the management device notification unit 1202 of the server B830 transmits "Notification 1" to the other servers, and the management device notification reception unit 1204 of the server A820 and the server C840 each receives "Notification 1 J. Accept (S701 and S702).

[0642] Here, "Notification 1" means that the management device notification unit 1202 of the server B830, which is the management device server, is continuously or constant in order to notify other servers that it is operating. Information that is transmitted intermittently at intervals.

[0643] Subsequently, the server indicated by the information held in management device holding unit 1200 and the server for which management device notification receiving unit 1204 has received "notification 1" are both "server B" Therefore, the change determination unit 1206 of the server A820 and the server C840 determines that no change is necessary, and the server response unit 1212 of the server A820 and the server C840 that receives this determination transmits “response 1” to the server B830. Then, the server response reception unit 1 214 of the server B830 receives “response 1” (S703 and S704).

[0644] The processing from S701 to S704 so far is processing that is continued for the management device determination unit 920 of each server to determine the management device server.

[0645] Subsequently, the user request receiving unit 71 of the server A820, which is the access source server, receives the acquisition request to which the terminal 60 (65) used by the user is transmitted via the communication line 50 (S705). Here, the “acquisition request” is a request that the terminal that the user uses the electronic file specified by the user acquires.

[0646] Subsequently, the request type determination unit 73 of the server A820 acquires the request received by the user request reception unit 71, and determines whether the request is a difference between the "acquisition request" and the "write request". to decide . Since this figure is a time chart of processing related to an acquisition request, this determination is omitted.

Subsequently, the file storage control unit 77 of the server A 820 determines whether or not the file storage unit 25 of the server A 820 stores the electronic file related to the acquisition request (S706).

[0648] If it is determined that its own file storage unit 25 stores the electronic file related to the acquisition request (Yes in S706), the file storage control unit 77 of the server A820 continues to the file storage unit 25. The electronic file related to the acquisition request is read out from (S707).

[0649] Subsequently, the user request response unit 95 of the server A820 is the file storage control unit 77 of itself. Terminal that acquires the electronic file related to the acquisition request and uses the electronic file by the user

60 (65) is transmitted (S708).

[0650] Subsequently, when it is determined that the file storage unit 25 of its own does not store the electronic file related to the acquisition request (No in S706), the holding server inquiry unit 1079 of the server A820

Sends an inquiry to the server that holds the electronic file related to the acquisition request to

The 0 inquiry reception unit 102 receives the inquiry of the holding server (S709).

Subsequently, the holding server determination unit 104 of the server B830 refers to the file holding information 1000b of the holding server storage unit 1000 to determine whether or not the holding server of the electronic file related to the acquisition request has power. Judgment is made (S710).

[0652] If it is determined that there is no holding server (No in S710), the holding response transmitter of Sano B830

106 transmits a non-holding notification to server A820 (S711).

[0653] Subsequently, the user request response unit 95 of the server A820 transmits a non-holding notification to the terminal 60 (65) used by the user (S712).

[0654] If it is determined that there is a holding server (Yes in S710), then the holding server determination unit ₁₀₄ of the server B830 determines whether or not the server B830 itself is a holding server (

S713).

[0655] If it is determined that it is a holding server (Yes in S713), then the file storage control unit 77 of the server B830 obtains from the file storage unit 35 based on the request of its own management device unit 910. The electronic file related to the request is read (S714).

[0656] Subsequently, the file transmission unit 85 of the server B830 acquires the electronic file related to the acquisition request from its own file storage control unit 77, and transmits it to the Sano A820. Then, the file receiving unit 87 of the server A 820 receives the electronic file transmitted by the file transmitting unit 85 of the server B (S715).

[0657] Subsequently, the user request response unit 95 of the server A820 acquires the electronic file related to the acquisition request via the file storage control unit 77, and transmits it to the terminal 60 (65) used by the user (S716).

[0658] Subsequently, the file storage control unit 77 of the server A820 stores the electronic file acquired from its own file reception unit 87 in its own file storage unit 25 (S717). [0659] Subsequently, the update notification unit 1091 of the server A820 sends an update notification to the server B830 and the server C840, which indicates that the access source server has become the electronic file holding server related to the acquisition request. The update notification receiving unit 110 of the server B830 and the server C840 receives the update notification (S718 and S719).

[0660] Subsequently, the update notification reception unit 110 of the server A820 obtains the update notification from its own update notification unit 1091 via the internal bus, and the retained information update unit 112 of the server A820 receives the update notification reception unit. According to the update notification acquired from 110, the file holding information 1000b of its own holding server storage unit 1000 is updated (S720).

[0661] In addition, the retention information update unit 112 of the server 830 and the server 840 acquires the update notification from each update notification reception unit 110, and the file of each storage server storage unit 1000 according to the acquired update notification. Update retention information 1000b (S721 and S722

) o

[0662] Subsequently, in the same manner as in S701 to S704, “Notification 1” is transmitted and received between server B830 and server A820, and between server B830 and server C840, and “response 1 ' ^S Forces are transmitted and received (S723 forces up to S726). Since S723 corresponds to S701, S724 corresponds to S702, S725i to S703, and S726i to S704, the detailed processing is omitted here. Further, the management device determination unit 920 of each server does not show the power for continuously determining the management device server. Since the description of the management device determination process will be described later, it is omitted here.

[0663] If it is determined that the server itself is not a holding server (No in S713), then the file transmission request unit 108 of the server B830 transmits the electronic file related to the acquisition request to the server A820 that is the access source server. The request to be transmitted is transmitted to the holding server (S727). Here, it is assumed that the server C840 is a holding server.

[0664] Subsequently, the file storage control unit 77 of the server C840 serving as the holding server reads the electronic file related to the acquisition request from the file storage unit 25 (S728).

[0665] Subsequently, the file transmission unit 85 of the server C840 acquires the electronic file related to the acquisition request from the file storage control unit 77, and transmits the acquired electronic file to the server A820 (S729). [0666] Subsequently, the user request response unit 95 of the server A820 acquires the electronic file related to the acquisition request via the file storage control unit 77, and transmits it to the terminal 60 (65) used by the user (S730).

[0667] Subsequently, the processing after S717 is executed. Since the processing after S717 has already been described, the description thereof is omitted here.

[0668] FIG. 56 is a time chart showing an example of processing executed in each device constituting the distributed file management system according to Embodiment 4 of the present invention when the user transmits a terminal capability write request. is there.

Here, as in the case of FIG. 55, the management server information 1000a has the contents shown in FIG. 53. Therefore, “Server B” having the highest rank is set as the management device server, and the management device holding unit of each server. Assume that 1200 indicates information indicating “server B”.

[0670] Further, the "terminal" shown in the figure is a terminal used by the user, and is either terminal a60 or terminal b65 in the present embodiment. Furthermore, this figure shows an example in which server A820 is the access source server.

Therefore, in this figure and the explanation of this figure, the process of “Server A” 820 is a process executed by “Accessing Server”, and the process of “Server B” 830 is “Executed by Management Device Sano” This process.

[0672] First, the processing from S701 to S704 shown in this figure is the processing that is continued for each server to determine the server that functions as the distributed file management device, and is the same as in FIG. This is the same as the processing given the reference numerals. Therefore, the explanation here is omitted.

[0673] Subsequently, the user request receiving unit 71 of the server A820 as the access source server receives the write request transmitted from the terminal 60 (65) used by the user via the communication line 50 (S801). . Here, the “write request” is information that includes a request to update an electronic file held by the access source server or to make the access source server hold a new electronic file.

[0674] Subsequently, the request type determination unit 73 of the server A820 causes the request information holding unit 75 to hold the electronic file related to the write request (S802). [0675] Subsequently, first, the lock request transmission unit 89 of the server A820 receives the determination of the request type determination unit 73 that the acquired request is a write request, and functions as a distributed file management device. The lock request receiving unit 116 of the server B830 receives the request for the request (S803).

[0676] Subsequently, the lock request receiving unit 116 of the server B830 locks the lock information holding unit 118 by holding information on the electronic file related to the received lock request (S804).

[0677] The file storage control unit 77 of the server A820 receives the determination of the request type determination unit 73 that the acquired request is a write request, and the electronic file stored in the request information storage unit 75 is stored. And the obtained electronic file is written in its own file storage unit 25 (S805).

[0678] Subsequently, the file storage control unit 77 of the server A820 determines whether or not the writing is completed (S806).

[0679] If it is determined that the writing has been completed (No in S806), the update notification unit 1091 of the server A820 waits.

[0680] If it is determined that the writing is completed (Yes in S806), the update notification unit 1091 of the server A820 receives a notification of completion from its own file storage control unit 77, and the access source server writes it. An update notification is sent to the server B830 to indicate that it has become a holding server for the electronic file related to the request, and the update notification receiving unit 110 of the server B830 receives the update notification (S807).

[0681] Subsequently, the holding server inquiry unit 1079 of the server A820 receives a notification of completion from its own file storage control unit 77, and sends an inquiry about the holding server of the electronic file related to the write request to the server B830. The inquiry reception unit 102 of the server B830 receives the inquiry of the holding server (S808).

[0682] Subsequently, the update notification unit 1091 of the server A820 receives a notification of completion from its file storage control unit 77, and confirms that the access source server has become a storage server for the electronic file related to the write request. The update notification as content is transmitted to the server C840, and the update notification receiving unit 110 of the server C840 receives the update notification (S809). [0683] Subsequently, the update notification reception unit 110 of the server A820 acquires the above update notification from its own update notification unit 1091 via the internal bus, and the retained information update unit 112 of the server A820 receives the update notification reception unit. In accordance with the update notification acquired from 110, the file holding information 1000b of its own holding server storage unit 1000 is updated (S810).

[0684] In addition, the retention information update unit 112 of the server 830 and the server 840 acquires the update notification from each update notification reception unit 110, and the file of each storage server storage unit 1000 according to the acquired update notification. Update retention information 1000b (S811 and S812

) o

[0685] Subsequently, the retained information updating unit 112 releases the lock by deleting the information retained by the lock information retaining unit 118 (S813).

[0686] Subsequently, the update completion notification unit 114 receives the completion notification from the file storage control unit 77.

Then, the completion of the update process is notified to the server A820, and the completion notification receiving unit 93 of the server A820 receives the notification of completion (S814).

Subsequently, the user request response unit 95 of the server A 820 confirms that the processing related to the user write request has been completed in response to the completion notification receiving unit 93 receiving the completion notification. (S815).

[0688] Subsequently, the holding server determination unit 104 of the server B830 has its own holding server storage unit 100.

By referring to the file holding information 1000b of 0, server A that is the access source server

The presence / absence of a holding server other than 820 is determined (S816).

[0689] If it is determined that there is a holding server (Yes in S816), the file transmission requesting unit 108 of the server B830 obtains information by identifying the holding server from its own holding server determining unit 104, and writes it. A file transmission request including the content of transmitting the electronic file related to the request to the holding server is transmitted to the server A820, and the file transmission request receiving unit 83 of the Sano A820 receives the file transmission request (S817). This figure shows an example in which the holding server is “Server C” 840 when an affirmative determination is made in S816. Therefore, the following “server” 840 is a process executed by the “holding server”.

[0690] Subsequently, the file storage control unit 77 of the server A820 obtains the file transmission request received by the file transmission request receiving unit 83 from the file transmission request receiving unit 83, and acquires its own file. The electronic file related to the write request is read from the storage unit 25 (S818).

[0691] Subsequently, the file transmission unit 85 of the server A820 acquires the electronic file related to the write request and the file transmission request from the file storage control unit 77, and transmits the electronic file related to the write request to the server C840. The file receiver 87 of the server C840 receives the electronic file (S819).

[0692] Subsequently, the file storage control unit 77 of the server C840 acquires the electronic file received by the file reception unit 87 from its own file reception unit 87, and updates its own file storage unit 45 with the electronic file ( S820).

[0693] Subsequently, the processing from S722 to S725 shown in the figure is continued. These processes are processes continued for each server to determine the management apparatus server, and are the same as the processes given the same reference numerals in FIG. Therefore, the explanation here is omitted. Further, although the management device determination unit 920 of each server continuously determines the management device server, it is not shown. Since the description of the management device determination process will be described later, it is omitted here.

[0694] Next, a procedure related to management device determination processing by the management device determination unit 920 of each server will be described with reference to the drawings.

FIG. 57 is a time chart of processing executed in each server to determine the management apparatus server. This figure is a time chart showing a specific example of processing executed in each server in order to determine the management apparatus server when the operation of the server B830 as the management apparatus server is stopped and then spread.

In this figure, server A820, server B830, and server C840 holding server storage unit 1

The management server information 1000a of 000 has the contents shown in FIG. Therefore, when the server B830 is stopped, the next management apparatus server is the server C840.

[0697] First, the server B830, which is the management apparatus server, stops (S901). Therefore, the server

B830 cannot send “Notification 1” to server A820 and server C840. To "Notification 1"

The description in this figure with an X mark represents this.

[0698] Next, the management device determination unit 920 of the server A820 executes the server B83 which is a management device server.

The notification cannot be received within a certain time from 0, so the management device server Server C840, which is the server of the rank of the server, is determined as the management apparatus server, and the management apparatus information held by itself is changed from server B830 to server C840 (S902).

Here, the process that each server, not the management apparatus server, determines the current management apparatus server and performs intermittently in order to retain correct management apparatus information is referred to as a “first management apparatus determination process”. The details will be described later.

[0700] Similarly, the management device determination unit 920 of the server C840 also determines that the server C840 is a management device server in the first management device determination processing, and the management device information held by itself from the server B830 to the server Change to C840 (S903).

[0701] Subsequently, the management device notification unit 1202 of the server C840 that has become the management device server reports "Notification 2

Is transmitted to the other server, and the management device notification receiving unit 1204 of the server A820 receives “Notification 2” (S904). Server B830 cannot accept “Notification 2” because it is stopped (S905). The X on the “Notification 2” arrow in this figure indicates this.

[0702] Here, "Notification 2" refers to information that is sent continuously or intermittently at regular intervals to notify other servers that it is operating, as with "Notification 1". This notification is transmitted by the management device notification unit 1202 of the server C840 that is the management device server.

[0703] Subsequently, the management device determination unit 920 of the server A820 performs the first management device determination process.

Then, it is determined that there is no need to change the management device (S906).

[0704] Subsequently, the server response unit 1212 of the A820 transmits "response 2" to the server C840, and the server

The server response acceptance unit 1214 of C840 accepts “response 2” (S907).

[0705] Subsequently, the management device determination unit 920 of the server A820 continues the first device determination processing, and the management device determination unit 920 of the server A820 and the server C840 transmits "notification 2" and "response 2". Repeat reception (shown as ヽ).

[0706] Next, it is assumed that the server B830 is restored (S908).

[0707] The management device notification unit 1202 of the restored server B830 transmits "Notification 1" to the other servers, and the management device notification reception unit 1204 of the server A820 and the server C840 each receives "Notification 1". (S909 and S910).

[0708] Subsequently, the management device determination unit 920 of the server A820 retains the current management device server in the first management device determination process and ranks higher than the server C840 indicated by the information indicated. Since the notification is received from the upper server B830, the server B830 is determined as the management device server, and the management device information held by itself is changed from the server C840 to the server B830 (S911).

Subsequently, server response unit 1212 of server A820 transmits “response 1”, and server response reception unit 1214 of server B830 receives “response 1” from server A820 (S912).

[0710] Further, since the management device determination unit 920 of the server C840 has received a notification from the server B830 having a higher rank than itself, the management device determination unit 920 determines that the server B830 is a management device server, and stores the management device information held by itself. To server B830 (S913).

[0711] Here, the process in which the management apparatus server determines the current management apparatus server and performs intermittently in order to properly hold the management apparatus information is called "second management apparatus determination process". Details will be described later.

[0712] Subsequently, the server response unit 1212 of the server C840 transmits “response 1” including the file holding information 1000b stored in its own holding server storage unit 1000, and the server response reception unit 1214 of the server B830. Receives “Response 1” including file holding information 1 OOOb from server C840 (S914).

[0713] Subsequently, the server response receiving unit 1214 of the server B830 that has received “response 1” including the file holding information 1000b is stored in its holding server storage unit 1000 based on the file holding information 1000b. The file holding information 1000b is updated (S915). As a result, the file holding information 1000b held by the server B830 becomes the latest content.

[0714] Subsequently, the management device notification unit 1202 of the server B830 sends “Notification 1” to the other servers, and the management device notification reception unit 1204 of the server A820 and the server C840 receives “Notification 1 J respectively”. (S 916 and S 917).

[0715] Subsequently, the management device determination units 920 of the server A820 and the server C840 determine that the management device does not need to be changed in the first management device determination processing (S918 and S919).

[0716] Subsequently, the server response unit 1212 of the server A820 and the server C840 transmits "response 1" to the server B830. Then, the server response reception unit 1214 of the server B830 receives “response 1” (S920 and S921). [0717] Subsequently, the management device determination unit 920 of server A820 and server C840 continues the first device determination processing, and the management device determination unit 920 of server 820 and server C840 performs "notification 1" and "response 1". Repeatedly send and receive (and illustrated).

FIG. 58 is a detailed flowchart of the first management device process executed by the normal server management device determination unit 920.

[0719] First, the change determination unit 1206 determines whether or not a predetermined time has elapsed since the management device notification reception unit 1204 received the notification immediately before (S1001). The change determination unit 1206 holds this fixed time.

[0720] If it is determined that a certain time has not elapsed (No in S1001), that is, if the next notification is received within a certain time from the previous notification, the change determination unit 1206 continues to manage The information held by the device holding unit 1200 and the management server information 1000a of the holding server storage unit 1000 are acquired, and the ranking of the server that is the transmission source of the next notification is held by the management device holding unit 1 200. It is determined whether or not the management device information is higher than the server indicated (S1002).

[0721] When determining that the server that is the sender is not higher than the server indicated by the management device information

(No in S1002), the change determination unit 1206 determines that there is no need to change the management apparatus server, and returns to the determination process of time passage (S1001).

[0722] If it is determined that a certain time has passed (Yes in S1001), or it is determined that the certain time has not passed (No in S1001), and the server that is the transmission source is the management device When it is determined that the information is higher than the server indicated by the information (Yes in S1002), the change determination unit 1206 determines that the management device server needs to be changed. A server is determined (S1003).

[0723] Here, when it is determined that the management device server needs to be changed because a certain time has elapsed (Yes in S1001), the management device determination unit 1208 determines this determination and the management device holding unit. 1 The management device information held by the 200 is obtained from the change determination unit 1206, and the “rank” of the management server information 1000a is obtained from the holding server storage unit 1000, and the server next indicated by the management device information is obtained. The server corresponding to the rank of the server is determined as a new management device server [0724] Also, because the server that is the transmission source is higher than the server indicated by the management device information (Yes in S1002), if it is determined that the management device server needs to be changed, the management device determination unit The 1208 obtains this determination and information for specifying the transmission source server from the change determination unit 1206, and determines the transmission source server as a new management apparatus server.

[0725] Subsequently, the management device determination unit 1208 updates and holds the management device information held by the management device holding unit 1200 with the information for specifying the management device server determined by itself (S1004). . As a result, the first management device determination process by the normal server management device determination unit 920 ends.

FIG. 59 is a detailed flowchart of the second management device process executed by the management device determination unit 920 of the management device server.

First, when the management device notification receiving unit 1204 receives a notification, the change determining unit 1206 determines whether or not the transmission source of the notification is higher than the server including the notification (S110 0). .

[0728] If it is determined that the transmission source is not higher than the server provided with the transmission source (No in S1100), change determination section 1206 waits.

[0729] If it is determined that the transmission source is higher than the server including itself (Yes in S1100), the management device determination unit 1208 uses this determination and information for specifying the server that is the transmission source. The server that is acquired from the change determination unit 1206 and is the transmission source is determined as a new management apparatus server (S1101).

Subsequently, the management device determination unit 1208 updates and holds the management device information held by the management device holding unit 1200 with the information for specifying the management device server determined by itself (S1102). .

[0731] Subsequently, when the holding server information acquisition unit 1210 acquires information for identifying the server determined by the management device determination unit 1208 as a new management device server, the holding server information acquisition unit 1210 stores the information of its own holding server storage unit 1000. The file holding information 1000b is acquired, and the acquired file holding information 1 000b and the information for specifying the server are delivered to the server response unit 1212 (S1103) Thereby, the first management device determination process by the management device determination unit 920 of the management device server ends.

[0733] Next, the processing executed in each device constituting the distributed file management system according to Embodiment 4 will be described with a more specific example.

FIG. 60 shows the distributed file management system according to the fourth embodiment of the present invention when server B 830 recovers after server A 820 receives a file d acquisition request while server B 830 is stopped. 6 is a time chart showing a specific example of processing executed in each of the constituent devices.

[0735] Also here, it is assumed that the management server information of the holding server storage unit 1000 of each server is the management server information 1000a shown in FIG. Further, it is assumed that the initial content of the file holding information in the holding server storage unit 1000 of each server is the file holding information 1000b shown in FIG. Furthermore, the initial contents of the electronic file information stored in the file storage units 25, 35, and 45 of each server are assumed to be the contents shown in FIG.

[0736] First, after the server B830, which is the management device server, is stopped (S901), until the server A820 sends "Response 2" to the server C840 that has newly become the management device server, the processing of (S907) This is the same as the process given the same reference number in FIG. Therefore, the description here regarding these is omitted. The management apparatus server at this time is changed to the server C840.

[0737] Subsequently, the user request receiving unit 71 of the server A820 receives an acquisition request for the file d from the terminal 60 (65) used by the user (S1201).

[0738] Subsequently, the request type determination unit 73 of the server A820 determines whether the request received by the user request reception unit 71 is an “acquisition request” (not shown), and then continues with the process of the server A820. The file storage control unit 77 determines whether or not the own file storage unit 25 stores the electronic file related to the acquisition request (S1202).

[0739] As shown in FIG. 49A, the file storage unit 25 of the server A820 does not store the file d. Therefore, the file storage control unit 77 of the server A 820 determines that its own file storage unit 25 has stored the electronic file related to the acquisition request (No in S 1202).

[0740] The holding server query unit 1079 of the server A820 receives the judgment of the file storage control unit 77. Then, the server C840 sends an inquiry about the holding server of the electronic file related to the acquisition request, and the inquiry receiving unit 102 of the server B830 receives the inquiry about the holding server (S1203)

[0741] Subsequently, the holding server determination unit 104 of the server C840 refers to the file holding information 1000b of the holding server storage unit 1000 to determine whether the holding server of the electronic file related to the acquisition request has power. Judgment is made (S 1204).

[0742] As shown in FIG. 54, the holding servers of the file d are “server B” and “server C”.

The holding server determination unit 104 of the server C840 determines that there is a holding server (in S1204

Yes), it is subsequently determined whether or not the server C840 itself is a holding server (S 1205).

[0743] As described above, since "Server C" is the holding server, it is determined that it is the holding server (Yes in S1205), and then the file storage control unit 77 of the server C840 determines itself. In response to a request from the management apparatus unit 910, the file d is read from the file storage unit 45 (S1206).

[0744] Subsequently, the file transmission unit 85 of the server C840 acquires the file d from its own file storage control unit 77 and transmits it to the server A820. Then, the file receiving unit 87 of the server A820 receives the file d (S1207).

[0745] Subsequently, the user request response unit 95 of the server A820 transfers the file d to the file storage control unit.

It is acquired via 77 and transmitted to the terminal 60 (65) used by the user (S1208).

[0746] Subsequently, the file storage control unit 77 of the server A820 stores the electronic file acquired from its own file reception unit 87 in its own file storage unit 25 (S1209).

[0747] Subsequently, the update notification unit 1091 of the server A820 transmits an update notification with the content that it has become the holding server of the file d to the server C840, and the update notification reception unit 110 of the server C840 An update notification is accepted (S1210).

[0748] Subsequently, the update notification reception unit 110 of the server A820 acquires the update notification from its own update notification unit 1091 via the internal bus, and the retained information update unit 112 of the server A820 receives the update notification reception unit. According to the update notification acquired from 110, the file holding information 1000b of its own holding server storage unit 1000 is updated (S1211).

[0749] Further, the retained information update unit 112 of the server C840 acquires an update notification from each update notification reception unit 110, and each of the retained server storage units 10 according to the acquired update notification. The file holding information 1000b of 00 is updated (S1212).

[0750] Thereafter, the server C840 and the server A820 continue the processing from the transmission / reception of "Notification 2" (S904) to the transmission / reception of "Response 2" (S907).

[0751] The file holding information held by each server when the processing so far is finished will be described with reference to the drawings.

[0752] Fig. 61 is a diagram showing an example of the server information 1000c stored in the storage server storage unit of the server A820 and the server C840 after the processing related to the acquisition request for the file d executed while the server B830 is stopped. It is. In the holding server information 1000c of server A820 and server C840, “server A” is newly added to the holding server of “file d”.

[0753] FIG. 62 is a diagram showing an example of the holding server information 1000b in the holding server storage unit of the server B830 after the processing related to the acquisition request for the file d executed while the server B830 is stopped is completed. . Because server B830 is stopped, holding server information lOOOd has not been updated, and “server A” is newly added to the holding server of “file d”.

[0754] As described above, the file holding information 1000d held by the stopped server may not hold the correct information. Therefore, the process described below is executed.

[0755] Here, let us return to the explanation of FIG.

[0756] Assume that server B830 is restored (S908).

[0757] Subsequently, the process from transmission / reception of "Notification 1" between server B830 and server A820 (S909) to the update of retained server information by server B (S915) is the same as the process with the same reference number in FIG. It is. Therefore, the description here regarding these is omitted.

Here, “response 1” transmitted by server response unit 1212 of server C840 in S914 includes the latest file holding information 1000c shown in FIG. Therefore, the server B830 that has received “response 1” can update the file holding information 1000b stored in its holding server storage unit 1000 with the file holding information 1000c in S915, and the restored server B830 It can function correctly as a management device server

[0759] In Embodiment 2, it is displayed on a monitor connected to terminal 60 (65) used by the user. The example of the input screen and the result display screen shown are the same as the example of the input screen and the result display screen described with reference to FIGS. 16 to 18 in the first embodiment. Therefore, the explanation here is omitted.

[0760] Although the distributed file management system according to the fourth embodiment of the present invention has been described above, the present invention is not limited to this embodiment.

[0761] (Modification 2)

For example, the server constituting the distributed file management system according to the present embodiment may include a server that does not have a function as a distributed file management device.

[0762] In the fourth embodiment, the case where there are three servers constituting the distributed file management system has been described as an example. However, the number of servers constituting the distributed file management system may be larger. A server having a function as a distributed file management device stores file retention information in the retention server storage unit 1000, and if any file storage unit of the server is changed, all the distributed file management devices are used. The file retention information of the server with the above function is updated in order to maintain synchronization. When a distributed file management system is configured with a large number of servers, the amount of processing and communication information for synchronizing this file retention information increases.

[0763] Therefore, when the distributed file management system is configured by a large number of servers, by including a server having the function of the distributed file management device as a part of the server group, the distributed file management system can It is possible to improve the faultiness and include a server that does not have the function of the distributed file management device in a part of the server group, thereby increasing the load related to the processing of each server and the amount of communication information. It is possible to suppress the increase.

[0764] One modification according to Embodiment 4 will be described with reference to FIGS. 63 to 65. FIG.

FIG. 63 is a diagram showing an outline of the configuration of the distributed file management system according to the second modification of the present invention. The distributed file management system shown in this figure is composed of a Sano A820, a server B830, a Sano C840, a server D850, a terminal a60, and a terminal b65. These devices are connected via a communication line 50. Yes. That is, distributed file management shown in this figure The system configuration is obtained by adding the server D850 to the configuration of the distributed file management system according to the fourth embodiment. Since the devices other than the server D850 are the same as those in the fourth embodiment, a detailed description thereof is omitted here.

[0766] The server D850 includes a file storage unit 855, which is a storage unit that stores electronic files, in the same manner as other servers. The server D850 is different from other servers in that it has a function as a distributed file management device.

[0767] Therefore, the management server information of the holding server storage unit 1000 included in the server A820, the server B830, and the server C840, which are servers having a function as a distributed file management device, is stored in the server D850 as a distributed file management device. It has a function so that it can be identified.

FIG. 64 is a diagram showing an example of the management server information lOOOe of the holding server storage unit 1000 included in the server functioning as the distributed file management device according to the second modification of the present invention.

[0769] The management server information lOOOe shown in this figure is composed of "server name", "IP address", "rank", and power as well as the management server information 1000a according to the fourth embodiment shown in FIG. Is done. In this modification, the information stored in these is the same as in the embodiment. The difference is that in order to be able to identify servers that do not have a function as a distributed file management device, no information is included in the “rank” corresponding to those servers.

[0770] For example, in this figure, the only information stored in association with "Server D" is "IP address", and "Rank" is a null value. In this way, when “rank” is a null value, a server having a function as a distributed file management apparatus can identify that “server D” is a server not having a function as a distributed file management apparatus. For example, if the management device server stops, server D850 must be a candidate for the next management device server.

[0771] Note that the method of indicating that the server does not have a function as a distributed file management device is not limited to this. In addition to the “rank” being a null value, it may be a value not assigned to the “rank” associated with the server having the function of the distributed file management device, such as “rank” being “1”. In addition, a flag indicating whether or not the server has a function as a distributed file management apparatus may be added.

FIG. 65 shows a server that does not function as the distributed file management device according to the second modification of the present invention. It is a block diagram which shows the functional structure with which server D850 which is is.

[0773] The server D850 is also configured with a file server unit 900 and a management device determination unit 1300.

. Each part is connected by an internal bus (not shown).

[0774] The file server unit 900 of the server D850 is a part that implements a function as a file server, similar to the file server unit 820 of the server A820 shown in FIG. It has the same functional configuration. The functions provided in each part of the file server unit 900 shown in this figure are the same as the functions provided in each part of the file server unit 820 of the server A 820 given the same reference numerals in FIG. Therefore, a detailed description of the functions provided in each part of the file server unit 900 of the server D850 is omitted here.

[0775] Similar to the management device determination unit 920 of the server A820 shown in FIG. 52, the management device determination unit 1300 determines the management device server based on information transmitted to and received from the management device server. It is.

[0776] The management device determination unit 1300 of the server D850 according to this variation includes a management device holding unit 1400, a management device notification receiving unit 1402, and a server response unit 1412.

[0777] Management device holding unit 1400 is a unit that holds management device information, like management device holding unit 1200 shown in FIG.

[0778] The management device notification receiving unit 1402 is a part that receives a notification from the management device notification unit 1202 of the management device server, similarly to the management device notification reception unit 1204 shown in FIG. The management device notification receiving unit 1402 causes the management device holding unit 1400 to hold information indicating the server that is the transmission source of the received notification as management device information.

That is, the management device determination unit 1300 of the server that does not have the function as the distributed file management device determines that the server that is the notification source is the management device server.

[0780] The server response unit 1412 is a part that responds to the management device server when the management device notification reception unit 1402 receives the notification. The server response unit 1412 acquires the management device information held by the management device holding unit 1400, and sets the server indicated by the acquired management device information as the management device server that is the response destination.

[0781] By providing such a function, a server that does not have the function of a distributed file management device Can detect the distributed file management server, and when it receives a request from the user, it can query the distributed file management server for the electronic file holding server related to the user's request as necessary. it can.

[0782] In this modification, it is needless to say that multiple servers may be used as an example in which there is one server that does not have the function of the distributed file management device.

[0783] The power described above for the distributed file management system according to Embodiments 1 to 4 of the present invention The present invention is not limited to these embodiments.

[0784] For example, in Embodiments 1 to 3, the case where there are three servers managed by the distributed file management device has been described as an example, but there may be a plurality of servers. Also,

As described above, the effect of each embodiment becomes remarkable, such as the user being able to acquire a desired electronic file without being aware of the location of the electronic file.

Industrial applicability

[0785] The present invention can be applied to a device or system that manages a group of electronic files that are distributed and held by a plurality of servers, and particularly includes a plurality of file servers and a device that manages each file server. The present invention can be applied to a system that includes a plurality of WWW (World Wide Web) servers and devices that manage each WWW server.

Claims

The scope of the claims

[1] A distributed file management system that manages electronic files held by multiple servers.

The distributed file management system is composed of the plurality of servers, terminals used by users, and a distributed file management device connected by a communication line,

The distributed file management device includes:

When an access source server that receives a user request related to an electronic file receives a request for the terminal to acquire an electronic file including a user-specified identifier, the latest electronic file including the identifier is retained. Inquiry receiving means for receiving from the access source server an inquiry as to which holding server is a server to perform;

Holding server storage means for storing and holding file holding information, which is information indicating which server holds the latest electronic file;

When the inquiry accepting means accepts an inquiry, referring to the file holding information, the holding server judging means for judging which is the holding server and an electronic file including the user-specified identifier A file transmission request unit that transmits a file transmission request, which is a request to be transmitted to the access source server, to a server that is determined to be a holding server by the holding server determination unit.

Distributed file management system characterized by that.

[2] The holding server storage means is information in which the server, the identifier of the electronic file, and a flag indicating whether or not the latest in the electronic file group including the same identifier is associated with each other Remember file retention information,

The holding server judging means judges the server associated with the user-specified identifier and the flag indicating the latest as the holding server by referring to the file holding information. Do

The distributed file management system according to claim 1, wherein:

[3] Each server is A file storage means for storing electronic files;

A file transmission request receiving means for receiving the file transmission request transmitted by the file transmission request means;

A file storage control means for reading the electronic file related to the file transmission request by the file storage means; and

A file transmission unit that acquires the electronic file read by the file storage control unit and transmits the acquired electronic file to the access source server;

The distributed file management system according to claim 2, wherein:

[4] Each server is

And a file receiving means for receiving the electronic file transmitted from the file transmitting means of another server.

The file storage control means further writes the electronic file received by the file receiving means into the file storage means.

The distributed file management system according to claim 3, wherein:

[5] Each server further includes:

When the file storage control means writes an electronic file to the file storage means, the update notification means for notifying the distributed file management device of the difference between the information stored in the file storage means before and after writing,

The distributed file management device includes:

Update notification accepting means for accepting notification by the update notifying means;

Holding information updating means for updating the file holding information based on the difference included in the notification received by the update notification receiving means.

The distributed file management system according to claim 4, wherein:

[6] The update notification means is configured so that the access source server receives a request for the terminal to acquire an electronic file including a user-specified identifier, and the access source server holds the electronic file related to the acquisition request. If it arrives, the distributed file management device is notified of the electronic file identifier related to the acquisition request as the difference,

The update notification receiving means receives notification from the update notification means, In response to the notification received by the update notification receiving unit, the holding information update unit includes information indicating the access source server, an identifier of the electronic file included in the difference, and the flag indicating the latest Update the file retention information by adding the associated information

The distributed file management system according to claim 5, wherein:

[7] The update notification means is configured so that the access source server receives a write request that is a request to hold the electronic file in the server, and the access source server holds the electronic file related to the write request. When it arrives, the distributed file management device is notified as the difference between the identifier of the electronic file related to the write request and the information indicating the retention based on the write request,

The update notification receiving means receives notification from the update notification means,

The holding information update unit determines that the flag corresponding to the server is not the latest when there is a server associated with the identifier included in the difference in response to the notification received by the update notification reception unit. The information stored in the access source server, the identifier included in the difference, and the information indicating the latest flag are added to change the file holding information. 6. The distributed file management system according to claim 5, wherein updating is performed.

[8] Each server further includes:

User request receiving means for receiving a user request related to the electronic file from the terminal;

The user request received by the user request receiving means is an acquisition request that is a request for the terminal to acquire an electronic file including a user-specified identifier, and a write request that is a request for causing the server to hold an electronic file. A request type judging means for judging whether or not,

When the request type determining unit determines that the request is the acquisition request, the electronic file holding server for the acquisition request is provided with a holding server inquiry unit that queries the distributed file management device as to whether it is a deviation. ,

The inquiry accepting unit is provided in the access source server that has accepted the acquisition request. Receives an inquiry from the server inquiry means as to which electronic file holding server is associated with the acquisition request.

8. The distributed file management system according to claim 1, wherein the distributed file management system is any one of claims 1 to 7.

[9] The file storage control means further stores an electronic file related to the write request received by the user request reception means when the request type determination unit determines that the request is a write request. Write on means

The distributed file management system according to claim 8, wherein:

[10] Each server is

Further, when the request type determination unit determines that the request is the write request, a request for locking that excludes processing related to writing of the electronic file related to the write request and a request for releasing the lock are made. And a lock request transmission means for transmitting to the distributed file management device,

The distributed file management device includes:

Furthermore, lock information holding means for holding lock information which is information for identifying an electronic file to be locked,

The lock request transmission means force When the lock request or the lock release request is received and the lock request is received, the lock information holding means holds the lock information related to the lock request, and the lock release A lock request receiving unit that deletes the lock information related to the request to release the lock from the lock information holding unit when a request is received;

If the electronic file indicated by the lock information is the same as the electronic file indicated by the difference in the notification received by the update notification receiving means, the holding information updating means holds the lock information holding means. The file holding information is updated after the lock information is deleted

10. The distributed file management system according to claim 8 or 9, wherein:

[11] Each server is

Further, when the request received by the user request receiving unit is the acquisition request, When the electronic file related to the acquisition request is transmitted to the terminal that is the transmission source of the acquisition request, and the request received by the user request receiving unit is the write request, the file storage control unit writes the electronic file. User request response means for receiving completion of writing of the electronic file related to the request and notifying the terminal that is the transmission source of the write request that writing is completed

The distributed file management system according to claim 8, wherein the distributed file management system is any one of claims 8 to 10.

[12] A distributed file management method for managing electronic files held by a plurality of servers, wherein an access source server that receives a user request related to an electronic file receives an electronic file including an identifier specified by the user. An inquiry reception step for receiving from the access source Sano an inquiry as to which holding server is a server holding the latest electronic file including the identifier when a request acquired by the terminal is received; ,

When the inquiry is accepted in the inquiry acceptance step, the holding server is referred to by referring to file holding information which is information indicating which server holds the latest electronic file. A holding server determination step for determining whether or not a file transmission request that is a request for transmitting an electronic file including the user-specified identifier to the access source server is determined to be a holding server in the holding server determination step. A file transmission request step to be transmitted to the server.

A distributed file management method.

[13] A distributed file management program for managing electronic files held by multiple servers.

When an access source server that receives a user request related to an electronic file receives a request for the terminal to acquire an electronic file including a user-specified identifier, the latest electronic file including the identifier is retained. An inquiry reception step for receiving an inquiry as to which holding server is a server to be accessed from the access source Sano; When the inquiry is accepted in the inquiry acceptance step, the holding server is referred to by referring to file holding information which is information indicating which server holds the latest electronic file. A holding server determination step for determining whether or not a file transmission request that is a request for transmitting an electronic file including the user-specified identifier to the access source server is determined to be a holding server in the holding server determination step. Causes the computer to execute the file transmission request step

A distributed file management program.

[14] A distributed file management system that manages electronic files held by multiple servers.

The distributed file management device includes:

Storage server storage means for storing file holding information, which is information indicating which server holds an electronic file!

With reference to the file holding information, when a plurality of servers hold an electronic file having the same identifier, the electronic files held by at least one of the plurality of servers are left. A deletion object determining means for determining whether or not to delete the electronic file;

A distributed file management system comprising: a deletion request transmission unit that transmits a request to delete the electronic file to a server that holds the electronic file determined to be deleted by the deletion target determination unit.

[15] The holding server storage means associates the server, the identifier of the electronic file, and the last access date that is the date when the user's request related to the electronic file held by the server was last received. Store file retention information,

The deletion target judging means refers to the file holding information, holds the same electronic file by a plurality of servers, and determines which of the electronic files held by the plurality of servers is If it is determined that the last access date has also passed a predetermined period, it is determined whether or not to delete each electronic file so that the electronic file with the latest access date remains the newest. Do

15. The distributed file management system according to claim 14, wherein:

[16] The holding server storage means is information in which the server, the identifier of the electronic file, and a flag indicating whether or not the latest in the electronic file group including the same identifier is associated with each other Remember file retention information,

The deletion target judging means refers to the file holding information, a plurality of servers holds an electronic file including the same identifier, and the electronic file including the same identifier is not up to date. Whether or not to delete each electronic file so that only the electronic file associated with the flag indicating the latest contents is left. To judge

15. The distributed file management system according to claim 14, wherein:

[17] When the plurality of servers hold an electronic file that includes the same identifier, the deletion target determination means leaves each electronic file held by at least one of the plurality of servers. The distributed file management system according to any one of claims 14 to 16, wherein it is periodically determined whether or not to delete an electronic file.

[18] The distributed file management device further includes:

When an access source server that is a server that has received a user request related to an electronic file receives a write request that is a request to hold the electronic file to the server, it is the same as the electronic file related to the write request. Inquiry accepting means for accepting an inquiry as to which server holds an electronic file including an identifier from the access source server;

The deletion object judging means refers to the file holding information when the inquiry receiving means receives an inquiry based on the write request, and a plurality of servers hold electronic files including the same identifier. In this case, the access source server deletes each electronic file so that only the electronic file retained by receiving the write request remains. Determine whether or not to remove

The distributed file management apparatus according to claim 14, wherein:

[19] The distributed file management device further includes:

When an access source server that is a server that has received a user request related to an electronic file receives a request for the terminal to acquire an electronic file including a user-specified identifier, the electronic file related to the acquisition request is retained. A query accepting unit that accepts an inquiry as to whether the holding server is a server from the access source server, and the file holding when the query accepting unit accepts an inquiry based on the acquisition request. A holding server judging means for judging which of the holding servers is by referring to the information;

A file transmission request, which is a request for transmitting an electronic file including the user-designated identifier to the server that is determined to be a holding server by the holding server determination unit, is sent to the holding server determination unit. File transmission request means for transmitting to a server determined to be a holding server by

19. The distributed file management system according to claim 14, wherein the distributed file management system is any one of claims 14 to 18.

[20] The distributed file management device further includes:

A clock means for holding the current date and time;

The file holding information associated with the access source server and the user-specified identifier according to the date held by the clock means when the holding server determination unit determines that the access source server is a holding server. And first holding information updating means for updating the last access date included in

20. The distributed file management system according to claim 19, wherein:

[21]

A file storage means for storing electronic files;

A file for reading the electronic file related to the file transmission request. An aisle memory control means;

20. The distributed file management system according to claim 19, wherein:

[22] Each server is

The distributed file management system according to claim 21, wherein:

[23] Each server further includes:

An update notification means for notifying the distributed file management device of the difference between the file storage means before and after writing when the file storage control means writes an electronic file to the file storage means;

The distributed file management device includes:

A second holding information updating unit that updates the file holding information based on the difference included in the notification received by the update notification receiving unit.

23. The distributed file management system according to claim 22, wherein

[24] The distributed file management device further includes:

It has a clock that holds the current date and time,

The update notification means is when the access source server receives a request for the terminal to acquire an electronic file including a user-specified identifier, and the access source server holds the electronic file related to the acquisition request. In addition, the distributed file management apparatus is notified of the identifier of the electronic file related to the acquisition request as the difference,

The second holding information update unit is configured to identify information indicating the access source server and an electronic file included in the difference in response to the notification received by the update notification reception unit. The file holding information is updated by adding information that associates the child with the date acquired from the clock unit as the last access date.

24. The distributed file management system according to claim 23.

[25] The update notification means is configured so that the access source server receives a request for the terminal to acquire an electronic file including a user-specified identifier, and the access source server holds the electronic file related to the acquisition request. When it arrives, the distributed file management apparatus is notified of the electronic file identifier related to the acquisition request as the difference,

In response to the notification received by the update notification receiving means, the second held information updating means confirms that the information indicating the access source server, the identifier of the electronic file included in the difference, and the latest information are updated. The file retention information is updated by adding information associated with the flag shown.

24. The distributed file management system according to claim 23.

[26] The distributed file management device further includes:

It has a clock that holds the current date and time,

The update notification means, when the access source server receives a write request that is a request to hold the electronic file in the server, and the access source server has held the electronic file related to the write request. To the distributed file management device as the difference between the identifier of the electronic file related to the write request and the information indicating the retention based on the write request,

In response to the notification received by the update notification receiving unit, the second held information updating unit receives information indicating the access source server, an identifier included in the difference, and the last access date from the clock unit. The file retention information is updated with the information associated with the acquired date.

24. The distributed file management system according to claim 23.

[27] The update notification means receives the write request that is a request to hold the electronic file in the server, and the access source server receives the write request. When the electronic file is held, the distributed file management apparatus is notified as the difference between the identifier of the electronic file related to the write request and information indicating that the hold is based on the write request. And

In response to the notification received by the update notification receiving means, the second holding information update means sets the flag corresponding to the server when there is a server associated with the identifier included in the difference. By changing to a flag indicating that it is not the latest, and adding information that associates the information indicating the access source server, the identifier included in the difference, and the flag indicating the latest, Update file retention information

24. The distributed file management system according to claim 23.

[28] A distributed file management method for managing electronic files held by a plurality of servers, referring to file holding information that is information indicating which server holds an electronic file and assigning the same identifier. When a plurality of servers hold electronic files, the deletion target for determining whether or not to delete each electronic file so that the electronic file held by at least one of the plurality of servers remains. A determination step, and a deletion request transmission step of transmitting a request to delete the electronic file to a server holding the electronic file determined to be deleted in the deletion target determination step.

A distributed file management method.

[29] A distributed file management program for managing electronic files held by multiple servers.

Referring to file holding information, which is information indicating which server holds an electronic file, and when multiple servers hold an electronic file having the same identifier, A deletion object determination step for determining whether or not to delete each electronic file so as to leave the electronic file held by at least one; and a server for holding the electronic file determined to be deleted in the deletion object determination step And a delete request sending step for sending a request to delete the electronic file. Let computer run

A distributed file management program.

[30] A distributed file management system that manages electronic files held by multiple servers.

The distributed file management device includes:

When an access source server that is a server that receives a user request related to an electronic file receives a request for the terminal to obtain an electronic file that includes a user-specified identifier, the access source server is created by an authorized person including the identifier. Inquiry accepting means for accepting a query as to whether the server is a server holding a genuine electronic file, whether it is a deviation,

Distributed file management system characterized by that.

[31] The holding server storage unit stores file holding information which is information in which the server, an identifier of the electronic file, and a hash value of the electronic file are associated with each other, and the holding server determination unit stores the question When the joint acceptance means accepts the inquiry, it refers to the file retention information and obtains the hash value of the electronic file held by the server that is associated with the identifier specified by the user! If the hash value associated with the user-specified identifier matches the acquired hash value, the server associated with the user-specified identifier is determined as a holding server. The distributed file management system according to claim 30, wherein:

[32] The holding server determination unit determines a server holding an electronic file including a user-specified identifier by referring to the file holding information when the inquiry receiving unit receives an inquiry. 1 decision part,

The hash value of the electronic file held by the server determined to hold the electronic file by the first determination unit is acquired, and the hash value and the hash value included in the file holding information are matched. A second determination unit that determines that the server determined to hold the electronic file by the first determination unit is a holding server.

The distributed file management device further includes:

A hash value for requesting the server determined to hold the electronic file by the first determination unit when the inquiry reception unit receives the inquiry, to request the hash value of the electronic file held by the server. Request means;

A hash value receiving means for receiving the hash value of the electronic file related to the request from the server to which the hash value requesting means has transmitted the request;

Each of the servers

A file storage means for storing electronic files;

A hash value request receiving means for receiving a request for a hash value of a specific electronic file from the hash value requesting means;

A hash value calculating means for obtaining the specific electronic file included in the request received by the hash value request receiving means from the file storage means and calculating a hash value of the specific electronic file;

Hash value transmission means for transmitting the hash value calculated by the hash value calculation means to the hash value reception unit.

32. The distributed file management system according to claim 31, wherein:

[33] The inquiry reception means further holds the electronic file related to the write request from the access source server that has received the request to write the electronic file in the file storage means included in the access source server. In response to an inquiry about which server The holding server determination unit further refers to the file holding information when the inquiry receiving unit receives an inquiry based on the write request, thereby identifying the same as the identifier of the electronic file related to the write request. Determine the server that holds the electronic file containing the

The distributed file management device further includes:

When the holding server determining means determines that there is no server holding the electronic file, the server indicating the largest value indicating the free state of the file storage means provided for storing the electronic file by each of the servers is determined. A value indicating the empty state is the largest.

A copy destination transmitting unit for transmitting to the access source server transmission of an electronic file related to the write request to the server determined to hold the copy by the copy destination determining unit;

33. The distributed file management system according to any one of claims 30 to 32, wherein:

[34] The copy destination determination unit may include a file storage unit provided for each server to store an electronic file when the storage server determination unit determines that there is no server holding the electronic file. The server having the largest ratio of the free capacity to the total capacity is determined, and the server having the largest ratio is determined as the server that holds the copy of the electronic file related to the write request.

34. The distributed file management system according to claim 33.

[35] The copy destination determination unit may include a file storage unit provided for each server to store an electronic file when the storage server determination unit determines that there is no server holding the electronic file. The server with the largest available capacity is determined as the server, and the server with the largest available capacity is determined as the server that holds the copy of the electronic file related to the write request.

34. The distributed file management system according to claim 33.

[36] A file transmission request receiving means for receiving a file transmission request including an identifier of the electronic file transmitted by the file transmission request means;

File storage control means for reading out an electronic file including an identifier included in the file transmission request from the file storage means;

36. The distributed file management system according to any one of claims 30 to 35, wherein:

[37] Each server further includes:

File receiving means for receiving an electronic file transmitted from the file transmitting means of another server;

37. The distributed file management system according to any one of claims 30 to 36, wherein:

[38] Each server further includes:

The distributed file management device includes:

38. The distributed file management system according to any one of claims 30 to 37, wherein:

[39] When the access source server accepts a request for the terminal to obtain an electronic file including a user-specified identifier, the update notification means includes an electronic file related to the request in a file storage means provided in the access source server. When the file is written, Notifying the distributed file management device of the identifier of the electronic file related to the acquisition request as the difference,

In accordance with the notification received by the update notification receiving unit, the holding information update unit adds information that associates the information indicating the access source server with the identifier of the electronic file included in the difference, Update the file retention information

The distributed file management system according to claim 38, wherein:

[40] The update notification means receives the request for writing the electronic file in the file storage means provided in the access source server, and the electronic mail related to the request is provided in the file storage means provided in the access source server. When a file is written, the distributed file management apparatus is notified of the identifier and hash value of the electronic file related to the write request as the difference,

In response to the notification including the hash value included in the difference received by the update notification receiving unit, the retained information update unit includes information indicating the access source server, an identifier of the electronic file included in the difference, and the The file retention information is updated by adding the value of the electronic file included in the difference and the hash value.

The distributed file management system according to claim 38, wherein:

[41] A distributed file management method for managing electronic files held by a plurality of servers, wherein an access source server that has received a user request related to an electronic file stores an electronic file including a user-specified identifier. When the terminal receives a request to be acquired, a holding server that holds a genuine electronic file created by an authorized person including the identifier is inquired about whether it is a deviation or not. Inquiry acceptance step to accept server power,

When the inquiry is accepted in the inquiry reception step, the holding server refers to the file holding information which is information indicating which server holds the electronic file. A holding server determining step for determining whether or not the electronic file including the user-specified identifier is transmitted to the access source server; A file transmission request step for transmitting a file transmission request as a request to the server determined to be the holding server in the holding server determination step.

A distributed file management method.

[42] A distributed file management program for managing electronic files held by multiple servers.

When an access source server that is a server that receives a user request related to an electronic file receives a request for the terminal to obtain an electronic file that includes a user-specified identifier, the access source server is created by an authorized person including the identifier. Inquiry accepting step for accepting an inquiry as to whether or not the holding server is a server holding a genuine electronic file,

When the inquiry is accepted in the inquiry reception step, the holding server refers to the file holding information which is information indicating which server holds the electronic file. A holding server determining step for determining whether there is a file transmission request, which is a request for transmitting an electronic file including the user-specified identifier to the access source server, in the holding server determining step; Causes the computer to execute a file transmission request step to be transmitted to the determined server

A distributed file management program.

[43] A distributed file management system that manages electronic files held by multiple servers.

The distributed file management system is composed of a plurality of first servers connected by communication lines and terminals used by users,

Each of the first servers is

One of the first server groups that receives a user request for acquiring or writing an electronic file from a terminal used by the user and manages the electronic file held by the server group in response to the user request. A file server means for inquiring which server holds an electronic file related to the user's request, and file holding information which is information indicating which server holds an electronic file. A server that stores information and refers to the file holding information in response to an inquiry from an access source server that is a server that has received the user's request, and holds the electronic file according to the user's request. Management device means for managing an electronic file held by the server group by determining a holding server;

First management device determination means for determining which of the first server group is the management device by communicating with the first server group

A distributed file management apparatus.

[44] The distributed file management system includes the plurality of first servers, at least one second server, and a terminal used by a user, connected via a communication line, and the second server. Is

The file server means;

Second management device determination means for determining which of the first server groups is the management device by communicating with the first server group

44. The distributed file management apparatus according to claim 43, wherein:

[45] The first management device determination means includes:

A first management device holding unit holding information indicating which of the first server group the current management device is;

A rank storage unit that stores rank information that is information that defines the order in which the first server group functions as the management device;

A management device notifying unit for notifying that each of the management devices is the management device;

A first management device notification receiving unit that receives a notification from the management device notification unit, and a predetermined time without receiving a next notification after the first management device notification receiving unit receives the notification. A change determination unit that determines that the management device needs to be changed when it has passed,

When the change determination unit determines that the management device needs to be changed, the first server having the highest rank in the first server group in operation is referred to by referring to the rank information. A management device determination unit that causes the first management device holding unit to hold information indicating And having

44. The distributed file management system according to claim 43, wherein:

[46] The first management device determination means includes:

A management device notifying unit for notifying the first management server and the second server that the management device is the management device;

A first management device notification receiving unit that receives a notification from the management device notification unit; and a case where a predetermined time elapses without receiving a next notification after the management device notification receiving unit receives the notification. A change determination unit that determines that the management device needs to be changed;

When the change determination unit determines that the management device needs to be changed, the first server having the highest rank in the first server group in operation is referred to by referring to the rank information. A management device determination unit that causes the first management device holding unit to hold information indicating

The second management device determination means includes

A second management device holding unit that holds information indicating which of the first server group the current management device is! /

A second management device notification receiving unit that receives the notification from the management device notification unit and causes the second management device holding unit to hold information indicating a transmission source of the received notification

45. The distributed file management system according to claim 44, wherein:

[47] The change determination unit further includes the current management device indicated by the information held by the first management device holding unit and the notification received by the first management device notification receiving unit. 47. The distributed file management system according to claim 45 or claim 46, wherein it is determined that the management device needs to be changed when the transmission source does not match.

[48] The management device means includes:

A holding server storage unit for storing the file holding information;

Query that receives an inquiry from the access source server that has received an acquisition request, which is a request for the terminal to acquire an electronic file including a user-specified identifier, as to which server holds the electronic file including the identifier. A reception department;

A holding server determination unit that determines the holding server by referring to the file holding information when the inquiry receiving unit receives an inquiry based on the acquisition request;

A file transmission requesting unit that requests the server determined to be the holding server by the holding server determining unit to transmit the electronic file related to the user request to the access source server;

48. The distributed file management system according to any one of claims 43 to 47, wherein:

[49] The inquiry reception unit may further include an electronic file including the identifier from the access source server that has received a write request that is a request for holding the electronic file including the user-specified identifier in the server. Server server that holds the

The holding server judging unit judges the holding server by referring to the file holding information when the inquiry receiving unit receives an inquiry based on the write request, and

The management device means further includes:

A holding response transmitter that transmits information indicating the server determined to be a holding server by the holding server determination unit to the access source server;

49. The distributed file management system according to claim 48, wherein:

[50] The file server means comprises:

A file storage unit for storing electronic files;

A file transmission request receiving unit that receives a file transmission request including an identifier of an electronic file transmitted by the file transmission request unit; A file storage control unit for reading an electronic file including an identifier included in the file transmission request from the file storage unit;

50. The distributed file management system according to claim 48 or claim 49, wherein:

[51] The file server means further includes:

A file receiving unit for receiving an electronic file transmitted from the file transmitting unit of another server;

The file storage control unit further writes the electronic file received by the file receiving unit into the file storage unit.

51. The distributed file management system according to claim 50, wherein:

[52] The file server means further includes:

An update notification unit for notifying the first server group of differences in the file storage unit before and after writing when the file storage control unit writes an electronic file in the file storage unit;

The management device means includes

An update notification receiving unit for receiving a notification from the update notification unit;

A retention information update unit that updates the file retention information based on the difference included in the notification received by the update notification reception unit.

52. The distributed file management system according to claim 51, wherein:

[53] The management device means further includes:

The update notifying unit writes the electronic file related to the request to the file storage unit included in the access source server when the access source server accepts the request for the terminal to acquire the electronic file including the user-specified identifier. The distributed file management apparatus is notified of the identifier of the electronic file related to the acquisition request as the difference,

The update notification receiving unit receives notification from the update notification means,

The holding information update unit is responsive to the notification received by the update notification receiving unit. The file holding information is updated by adding information that associates the information indicating the access source server with the identifier of the electronic file included in the difference.

53. The distributed file management system according to claim 52, wherein:

[54] The management device means further includes:

The update notification unit receives a request for writing an electronic file in a file storage unit included in the access source server, so that the electronic file related to the request is stored in the file storage unit included in the access source server. When written, the identifier of the electronic file related to the write request is notified to the distributed file management device as the difference,

The holding information update unit adds information indicating the access source server and an identifier of the electronic file included in the difference according to the notification received by the update notification receiving unit and including the hash value in the difference. To update the file retention information.

54. The distributed file management system according to claim 53.

[55] A distributed file management method for managing electronic files held by a plurality of servers, which accepts a user request for obtaining or writing an electronic file from a terminal used by the user, and responds to the request from the user. A file server step for inquiring to a management apparatus, which is one of the first server groups that manage the electronic files held by the server group, which server holds the electronic files according to the user's request. In response to an inquiry from the access source server that is the server that received the user's request, the user refers to the server holding the electronic file and the file holding information that is information indicating whether or not the By determining the holding server that holds the electronic file related to the request, the electronic file held by the server group is determined. And management apparatus step to management,

And a first management device determination step for determining which of the first server groups is the management device by communicating with the first server group.

A distributed file management method. A distributed file management program that manages electronic files held by multiple servers.

One of the first server groups that accepts user requests for obtaining or writing electronic files from a terminal used by the user and manages the electronic files held by the server group in response to the user requests. In response to an inquiry from an access source server that is a server that has received the user's request, and a file server step that inquires a certain management apparatus which server holds the electronic file related to the user's request. By referring to the file holding information that is information indicating whether or not the server holds the electronic file, it is possible to determine the holding server that is the server holding the electronic file according to the user's request. A management device step for managing electronic files held by the server group;

By communicating with the first server group, the computer is caused to execute a first management device determination step for determining which of the first server groups is the management device.

A distributed file management program.