JP2009259265A - System for managing distributed files - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a system for managing distributed files, which provides the file stored in one of plurality of servers to a user by accessing any server from a terminal used by the user. <P>SOLUTION: The system manages the distributed files stored in the plurality of servers, and comprises: a terminal used by the user, which is connected to a communication line; a plurality of servers receiving user's request; and a device for managing the distributed files, which determines a server having an electronic file associated with the user's request in response to an inquiry from the server, and enables each server to execute a required process for the request. Each server includes: a means for storing the file; a means for receiving a request to send the file; a means for controlling a file memory; a means for sending the file; a means for receiving the user's request; and a means for responding to the user's request. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

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

  Users using terminals 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 are held by a server connected to the network. Can access electronic files. Thereby, the user can browse or download the electronic files distributed and held in the servers connected to the network, and the distribution and utilization of information is promoted.

  Conventionally, techniques for utilizing and managing electronic files held in a distributed manner on a network have been proposed.

  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 that integrates file systems of servers 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.

  In addition, the technology described in Patent Document 2 does not use one electronic file held by each server jointly in each terminal connected to the network, but each server duplicates the same electronic file or group of electronic files. And a mechanism or method for completely synchronizing the contents of electronic files or electronic file groups held between servers.

JP-A-5-250249 Japanese National Patent Publication No. 10-510413

  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.

  Since the technique described in Patent Document 1 does not disclose a technique for synchronizing electronic files distributed on a network, for example, when the contents of electronic files with the same name held by a plurality of servers are different There is.

  In the technique described in Patent Document 2, the electronic files held by a plurality of servers are synchronized. However, all the servers hold the same electronic file group, and in order to synchronize each electronic file, when updating the contents of the electronic file, the electronic file held by all the servers is updated. There is a need to. Therefore, there is a problem that network traffic increases at the time of update. This problem becomes more prominent as the number of servers increases.

  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. As long as the latest electronic file is provided to the user, it is intended to provide a distributed file management system. It is another object of the present invention to provide a distributed file management system that can suppress the load on the network required to achieve the above object.

  To achieve the above object, a distributed file management system according to the present invention is a distributed file management system for managing electronic files held by a plurality of servers, and the distributed file management system is connected by a communication line. The plurality of servers, terminals used by users, and a distributed file management device, which is designated by the access source server that is a server that receives a user request related to an electronic file. When the terminal receives a request for acquiring the electronic file including the identifier, an inquiry as to which holding server is the server that holds the latest electronic file including the identifier is received from the access source server. Indicates which of the inquiry acceptance means and the server holding the latest electronic file is When the inquiry is received by the holding server storage unit storing the file holding information as information and the inquiry receiving unit, the file holding information is referred to, and the holding server is determined. A holding server determining unit that transmits a file transmission request that is a request for transmitting an electronic file including the user-specified identifier to the access source server, to the server that is determined to be the holding server by the holding server determining unit. File transmission requesting means.

  As described above, when the distributed file management apparatus receives an inquiry from the access source server, the distributed file management apparatus determines the electronic file holding server according to the user's request based on the information indicating which server holds the latest electronic file. to decide. Therefore, when a user accesses any of a plurality of servers connected via a network from a terminal used by the user, as long as at least one of the plurality of servers holds an electronic file desired by the user. The latest electronic file according to the user's request can be acquired from the terminal. Therefore, the user does not need to be aware of whether or not the electronic file is the latest and the server that is accessed from the terminal. It becomes possible to improve the property.

  In addition, when updating an electronic file held by each server, as long as one of the servers holds the electronic file according to the user's request, the user does not need to perform processing for synchronizing the electronic file. The terminal can obtain the latest electronic file related to the request. Therefore, it is possible to suppress the amount of information transferred on the network when updating the electronic file, and to reduce the load on each server.

  Preferably, the holding server storage means is a file that is information in which the server is associated with an identifier of the electronic file and a flag indicating whether or not the electronic file group includes the same identifier. The retention server is stored, and the retention server determination unit refers to the file retention information, and stores the server associated with the user-specified identifier and the flag indicating the latest. Judge as server.

  As described above, the distributed file management apparatus includes file holding information including information in which a server, an identifier of an electronic file, and a flag indicating whether the file is the latest in an electronic file group including the same identifier are associated with each other. When an inquiry is received from the access source server, the electronic file holding server related to the user's request is determined based on such file holding information. Therefore, when a user accesses any of a plurality of servers connected via a network from a terminal used by the user, as long as at least one of the plurality of servers holds an electronic file desired by the user. The latest electronic file according to the user's request can be acquired from the terminal. Therefore, the user does not need to be aware of whether or not the electronic file is the latest and the server that is accessed from the terminal, and the convenience of the user related to the acquisition of the electronic file that is distributed and held in a plurality of servers on the network. It becomes possible to improve the property.

  In addition, when updating an electronic file held by each server, as long as one of the servers holds the electronic file according to the user's request, the user does not need to perform processing for synchronizing the electronic file. The terminal can obtain the latest electronic file related to the request. Therefore, it is possible to suppress the amount of information transferred on the network when updating the electronic file, and to reduce the load on each server.

  More preferably, each of the servers includes a file storage unit storing an electronic file, a file transmission request receiving unit that receives the file transmission request transmitted by the file transmission request unit, and an electronic device related to the file transmission request. File storage control means for reading a 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.

  Thus, the access source server acquires the electronic file according to the user request from the holding server. Thereby, the access source server can transmit the electronic file according to the user's request to the terminal used by the user.

  More preferably, it further comprises a file receiving means for receiving an electronic file transmitted from the file transmitting means of another server, wherein the file storage control means further receives the electronic file received by the file receiving means as the file. Write to storage means.

  As described above, when the access source server does not hold the electronic file according to the user's request, the access source server acquires the electronic file from the holding server and holds it. Thereby, when the request | requirement which acquires the same electronic file from any one of terminals is received again, the electronic file which self hold | maintains can be transmitted. Therefore, the access source server does not need to acquire again from the holding server for the electronic file acquired via one access source server, and the amount of information transferred on the network can be suppressed. It is possible to reduce the load on the server.

  More preferably, each of the servers further includes, when the file storage control unit writes an electronic file in the file storage unit, a difference between the information stored in the file storage unit before and after the writing, in the distributed file An update notification means for notifying the management device, wherein the distributed file management device is configured to update the file holding by 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 information.

  Further, the update notification means has received a request for the terminal to acquire an electronic file including a user-specified identifier, and the access source server has held the electronic file related to the acquisition request. In this case, the distributed file management apparatus is notified of the electronic file identifier related to the acquisition request as the difference, the update notification receiving unit is notified by the update notification unit, and the holding information update unit is the update In response to the notification received by the notification receiving means, by adding information that associates the information indicating the access source server, the identifier of the electronic file included in the difference, and the flag indicating the latest The file holding information is updated.

  Furthermore, the update notification means has received a write request, which 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. In this case, 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, and the update notification receiving means In response to the notification from the update notification means, the retained information update means responds to the server when there is a server associated with the identifier included in the difference according to the notification received by the update notification reception means. The flag is changed to a flag indicating that the flag is not the latest, information indicating the access source server, an identifier included in the difference, and the latest By adding information that associates with the flag indicating Rukoto, it updates the file holding information.

  Thus, 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.

  More preferably, each of the servers further includes a user request receiving means for receiving a user request related to an electronic file from the terminal, and the user request received by the user request receiving means is a user-specified identifier. Request type determining means for determining whether the terminal is an acquisition request that is a request for acquiring an electronic file or a write request that is a request for holding the electronic file in the server, and a request type determining means A storage server inquiry means for inquiring of a distributed file management device which electronic file storage server is related to the acquisition request when it is determined that the acquisition request is, From the holding server inquiry means provided in the access source server that received the acquisition request, the holding server of the electronic file related to the acquisition request Accept the inquiry of whether a shift.

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

  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. As a result, the load on the distributed file management apparatus can be reduced.

  More preferably, each of the servers further includes a lock request that 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. The distributed file management device further includes lock request transmission means for transmitting the request for releasing the lock to the distributed file management device, and the distributed file management device further holds lock information that is information for identifying an electronic file to be locked. When the lock request or the lock release request is received from the lock information holding unit and the lock request transmission unit, and the lock request is received, the lock information holding unit holds the lock information related to the lock request. When the lock release request is received, the lock information related to the lock release request is changed to the lock information. A lock request receiving unit to be deleted from the holding unit, wherein the holding information update unit is the same as the electronic file indicated by the lock information and the electronic file indicated by the difference received by the update notification receiving unit. In this case, after the lock information held by the lock information holding means is deleted, the file holding information is updated.

  Thus, by performing the lock process, it is possible to prevent a discrepancy between the contents of the file holding information held by the distributed file management apparatus and the latest state of the electronic file held by each server.

  To achieve the above object, a distributed file management system according to the present invention is a distributed file management system for managing electronic files held by a plurality of servers, and the distributed file management system is connected by a communication line. And a plurality of servers, terminals used by users, and a distributed file management device, wherein the distributed file management device stores file holding information that is information indicating which server holds an electronic file. The stored holding server storage means and the electronic file held by at least one of the plurality of servers when the plurality of servers hold an electronic file having the same identifier with reference to the file holding information. Delete target judging means for judging whether or not to delete each of the electronic files, and the deletion The server holding the electronic file is determined to be deleted by elephant determining means, and a deletion request sending means for sending a request to delete the electronic file.

  As described above, when the distributed file management apparatus receives an inquiry from the access source server, the distributed file management apparatus determines the electronic file holding server related to the user's request based on the information indicating which server holds the electronic file. . Therefore, when a user accesses any of a plurality of servers connected via a network from a terminal used by the user, as long as at least one of the plurality of servers holds an electronic file desired by the user. The electronic file according to the user's request can be acquired from the terminal. Therefore, the user does not need to be aware of whether or not the electronic file is the latest and the server that is accessed from the terminal, and the convenience of the user related to the acquisition of the electronic file distributed and held in a plurality of servers on the network. It becomes possible to improve the property.

  In addition, when updating the electronic file held by each server, it is possible to synchronize electronic files having the same identifier held redundantly by some servers. Duplicate electronic files are not necessarily all of multiple servers, so transfer them over the network when updating electronic files, rather than when all servers hold all electronic files redundantly. It is possible to reduce the amount of information to be processed, and to 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.

  Furthermore, at least one electronic file held redundantly is deleted. Thereby, it is possible to suppress consumption of storage resources for each server to hold the electronic file.

  More preferably, 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. The file retention information that is information is stored, the deletion target determination means refers to the file retention information, a plurality of servers retain the same electronic file, and any of the electronic files retained by the plurality of servers When a predetermined period has elapsed since the last access date, it is determined whether or not to delete each electronic file so that the electronic file having the latest last access date remains.

  The holding server storage means is a file holding that is information in which the server is associated with an identifier of the electronic file and a flag indicating whether or not the electronic file group includes the same identifier. Information is stored, 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 latest one of the electronic files including the same identifier is stored. Whether or not to delete each electronic file so as to leave only the electronic file associated with the flag indicating the latest content when the flag indicating that the content is not associated To do.

  Further, the deletion target judging means is configured to leave each electronic file so as to leave the electronic file held by at least one of the plurality of servers when the plurality of servers hold the electronic file including the same identifier. It is determined periodically whether or not to delete.

  Furthermore, the distributed file management device further includes the access source server, which is a server that has received a user request relating to an electronic file, when receiving a write request that is a request for causing the server to hold the electronic file. Inquiry accepting means for accepting from the access source server an inquiry as to which server holds an electronic file that includes the same identifier as the electronic file related to the write request, and the deletion target judging means include the inquiry When the receiving unit receives an inquiry based on the write request, the access source server refers to the file holding information, and the plurality of servers hold electronic files including the same identifier. Determine whether to delete each electronic file so that only the retained electronic file remains by receiving That.

  In this way, at least one of the electronic files held redundantly is deleted, periodically or when a write request is received. This makes it possible to effectively use the storage resources that each server consumes to hold the electronic file.

  More preferably, the distributed file management device further includes a case where an access source server, which is a server that has received a user request relating to an electronic file, receives a request for the terminal to acquire an electronic file including a user-specified identifier. Inquiry receiving means for receiving from the access source server an inquiry as to which holding server is the server holding the electronic file related to the acquisition request, and the inquiry receiving means is an inquiry based on the acquisition request Is received by referring to the file holding information, the holding server determining means for determining which is the holding server, and the server determined to be the holding server by the holding server determining means, A request for transmitting an electronic file including the user-specified identifier to the access source server The Airu transmission request, and a file transmission request means for transmitting to the server is determined to be a holding server by the holding server determination means.

  Each of the servers 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 an electronic file related to the file transmission request. A file storage control unit that reads from the file storage unit; 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.

  Further, 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 further includes the electronic file received by the file receiving unit. Is written in the file storage means.

  As described above, when the access source server does not hold the electronic file according to the user's request, the access source server acquires the electronic file from the holding server and holds it. Thereby, when the request | requirement which acquires the same electronic file from any one of terminals is received again, the electronic file which self hold | maintains can be transmitted. Therefore, the access source server does not need to acquire again from the holding server for the electronic file acquired via one access source server, and the amount of information transferred on the network can be suppressed. It is possible to reduce the load on the server.

  More preferably, the distributed file management device further includes a clock unit that holds a current date and time, and the clock unit holds the access server when the holding server determination unit determines that the access source server is a holding server. The first holding information updating unit updates the last access date included in the file holding information associated with the access source server and the user-specified identifier depending on the date to be updated.

  Each of the servers further includes update notification means for notifying the distributed file management apparatus of a 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. And 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. Information updating means.

  Furthermore, the distributed file management device further includes a clock unit that holds the current date and time, and the update notification unit receives a request for the terminal to acquire an electronic file including a user-specified identifier. When 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 notified to the distributed file management device as the difference, and the update notification The accepting means receives a notification from the update notifying means, and the second holding information updating means receives the information indicating the access source server and the electronic information included in the difference according to the notice accepted by the update notice accepting means. By adding information in which the identifier of the file is associated with the date acquired from the clock unit as the last access date, the file To update the information held.

  Furthermore, the update notification means has received a request for the terminal to acquire an electronic file including a user-specified identifier, and the access source server has retained the electronic file related to the acquisition request. In this case, the distributed file management apparatus is notified of the identifier of the electronic file related to the acquisition request as the difference, and the update notification receiving unit receives the notification from the update notification unit, and the second holding information update unit In response to the notification received by the update notification receiving means, the information indicating the access source server, the identifier of the electronic file included in the difference, and the flag indicating the latest are associated with each other. By adding, the file holding information is updated.

  Furthermore, the distributed file management device further includes a clock unit that holds the current date and time, and the update notification unit receives the write request that is a request to hold the electronic file in the server. When the access source server has held the electronic file related to the write request, an identifier of the electronic file related to the write request and information indicating that the access is based on the write request, The difference is notified to the distributed file management device, the update notification receiving unit receives a notification from the update notification unit, and the second holding information update unit is responsive to the notification received by the update notification receiving unit. The information indicating the access source server, the identifier included in the difference, and the information obtained by associating the date acquired from the clock unit as the last access date To update the file holding information.

  Furthermore, the update notification means has received a write request, which 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. In this case, 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, and the update notification receiving means In response to the notification from the update notification means, the second holding information update means, when there is a server associated with the identifier included in the difference in response to the notification received by the update notification reception means, While changing the flag corresponding to the server to a flag indicating that it is not the latest, information indicating the access source server, an identifier included in the difference, By adding information that associates with the flag indicating a new, updating the file holding information.

  Thus, the file holding information held by the distributed file management apparatus is updated. As a result, the latest correct state of the electronic file held by each server can be automatically stored in the file holding information.

  To achieve the above object, a distributed file management system according to the present invention is a distributed file management system for managing electronic files held by a plurality of servers, and the distributed file management system is connected by a communication line. The plurality of servers, terminals used by users, and a distributed file management device, which is designated by the access source server that is a server that receives a user request related to an electronic file. When the terminal receives a request for acquiring an electronic file including the identifier, an inquiry is made as to which holding server is a server that holds a genuine electronic file created by an authorized person including the identifier. Inquiry accepting means for accepting from the access source server and a server for holding an electronic file The holding server storage means for storing file holding information, which is information indicating which, and when the inquiry receiving means receives an inquiry, the holding server refers to the file holding information so that the holding server A holding server determination unit that determines which is 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 by the holding server determination unit as a holding server. File transmission requesting means for transmitting to the designated server.

  The holding server storage unit stores file holding information which is information in which the server, the 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 query. When the accepting unit accepts the inquiry, the file designation information is referred to, and by obtaining the hash value of the electronic file held by the server associated with the user-specified identifier, If the hash value associated with the identifier matches the acquired hash value, the server associated with the user-specified identifier is determined as the holding server.

  As described above, when the distributed file management apparatus receives an inquiry from the access source server, the distributed file management apparatus determines the electronic file holding server related to the user's request based on the information indicating which server holds the electronic file. . Therefore, when a user accesses any of a plurality of servers connected via a network from a terminal used by the user, as long as at least one of the plurality of servers holds an electronic file desired by the user. The electronic file according to the user's request can be acquired from the terminal. Therefore, the user does not need to be aware of whether or not the electronic file is the latest and the server that is accessed from the terminal, and the convenience of the user related to the acquisition of the electronic file distributed and held in a plurality of servers on the network. It becomes possible to improve the property.

  In addition, when updating the electronic file held by each server, it is possible to synchronize electronic files having the same identifier held redundantly by some servers. Duplicate electronic files are not necessarily all of multiple servers, so transfer them over the network when updating electronic files, rather than when all servers hold all electronic files redundantly. It is possible to reduce the amount of information to be processed, and to 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.

  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.

  More preferably, 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 and a hash value of the electronic file held by the server determined to hold the electronic file by the first determination unit, and the hash value and the hash value included in the file holding information And the second determination unit that determines that the server determined to hold the electronic file by the first determination unit as a holding server when the first determination unit matches, the distributed file management device further includes the question When the combined acceptance unit accepts the inquiry, the server determines that the first determination unit stores the electronic file on the server determined to hold the electronic file. A hash value requesting unit for requesting the hash value of the electronic file, and a hash value receiving unit for receiving the hash value of the electronic file related to the request from the server to which the hash value requesting unit has transmitted the request. Each of the servers includes a file storage unit that stores an electronic file, a hash value request reception unit that receives a request for a hash value of a specific electronic file from the hash value request unit, and the hash value request reception unit. The specific electronic file included in the received request is acquired from the file storage means, and a hash value calculation means for calculating a hash value of the specific electronic file, and a hash value calculated by the hash value calculation means Hash value transmitting means for transmitting to the hash value receiving unit.

  In this way, each server calculates the hash value of the held electronic file, and transmits the calculated hash value to the distributed file management device. As a result, the distributed file management apparatus can acquire the hash value of the electronic file currently held by the server, and can verify that the electronic file held by the server has not been tampered with. Become.

  More preferably, the inquiry receiving unit further holds an electronic file related to the write request from an access source server that is a server that has received a request to write the electronic file in a file storage unit included in the access source server. In response to an inquiry as to which server is the 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. The server that holds an electronic file that includes an identifier identical to the identifier of the electronic file related to the write request is determined, and the distributed file management device further determines that there is no server that holds the electronic file by the holding server determination unit. File storage means provided for each server to store an electronic file when A copy destination determining unit that determines a server having the largest value indicating the free state, and determines a server having the largest value indicating the free state as a server that holds a copy of the electronic file related to the write request; A copy destination transmission unit that transmits to the access source server a transmission of the electronic file related to the write request to the server determined to hold the copy by the determination unit.

  Further, the copy destination determination unit, when it is determined by the holding server determination means that there is no server that holds the electronic file, the free space for the entire capacity of the file storage means provided for storing the electronic file in each server. The server having the largest capacity ratio is determined, and the server having the largest ratio is determined as a server that holds a copy of the electronic file related to the write request.

  Further, when the holding server determining unit determines that there is no server that holds the electronic file, the copy destination determining unit has the largest free space in the file storage unit provided for storing the electronic file in each server. A large server is determined, and a server having the largest free space is determined as a server that holds a copy of the electronic file related to the write request.

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

  In addition, since the servers other than the access source server that holds the new 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 can be used equally, and the load on the server Can be dispersed.

  More preferably, each server receives a file transmission request receiving unit including an identifier of an electronic file transmitted by the file transmission requesting unit, and an electronic file including an identifier included in the file transmission request. File storage control means for reading 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.

  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 further includes the electronic file received by the file receiving unit. Is written in the file storage means.

  As described above, when the access source server does not hold the electronic file according to the user's request, the access source server acquires the electronic file from the holding server and holds it. Thereby, when the request | requirement which acquires the same electronic file from any one of terminals is received again, the electronic file which self hold | maintains can be transmitted. Therefore, the access source server does not need to acquire again from the holding server for the electronic file acquired via one access source server, and the amount of information transferred on the network can be suppressed. It is possible to reduce the load on the server.

  More preferably, each of the servers further notifies 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. And the distributed file management device updates the file holding information based on the difference included in the notification received by the update notification receiving unit and the notification received by the update notification receiving unit. Means.

  In addition, the update notifying unit receives the request for the terminal to acquire an electronic file including a user-specified identifier, and the access source server accepts the electronic file related to the request in the file storage unit included in the access source server. Is written to the distributed file management device as the difference, and the update notification accepting unit receives the notification from the update notifying unit, and updates the retained information. In response to the notification received by the update notification receiving means, the file holding information is added 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. Update.

  Furthermore, 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 access source server accepts the electronic file related to the request in the file storage means provided in the access source server. Is written to the distributed file management device as the difference, and the update notification receiving means receives the notification from the update notification means. The holding information update unit receives information indicating the access source server, an identifier of the electronic file included in the difference, in response to the notification including the hash value included in the difference, received by the update notification receiving unit, By adding the hash value of the electronic file included in the difference, the file holding information Update.

  Thus, 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.

  To achieve the above object, a distributed file management system according to the present invention is a distributed file management system for managing electronic files held by a plurality of servers, and the distributed file management system is connected by a communication line. The first server includes a plurality of first servers and a terminal used by the user. Each of the first servers receives a user request related to acquisition or writing of an electronic file from the terminal used by the user, and In response to a user request, which one of the first server groups that manages the electronic files held by the server group is a server that holds the electronic files related to the user requests The file server means for inquiring the file and the file holding information, which is information indicating which server holds the electronic file, In response to an inquiry from an access source server that is a server that has received a user request, by referring to the file holding information and determining a holding server that is a server that holds an electronic file according to the user request, Management device means for managing electronic files held by the server group and first management for determining which of the first server group is the management device by communicating with the first server group Device determining means.

  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 by a communication line, and the second server includes: The file server means and second management device determination means for determining which of the first server groups is the management device by communicating with the first server group.

  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 functions as a distributed file management device stops operating due to a failure, other servers can continue to operate as the distributed file management device, so the distributed file management system continues to operate. It is possible to improve the stability of the distributed file management system.

  More preferably, the first management device determination unit includes a first management device holding unit that holds information indicating which of the first server groups is the current management device; A rank storage unit that stores rank information, which is information that defines the order in which one server group functions as the management apparatus, and a management apparatus that notifies the first server that the management apparatus is the management apparatus A notification unit, a first management device notification reception unit that receives a notification from the management device notification unit, and a first management device notification reception unit that receive the notification and then determine in advance without receiving a next notification. A change determination unit that determines that a change of the management device is necessary when a predetermined time has elapsed, and refers to the ranking information when the change determination unit determines that a change of the management device is required Is up and running And a management device determining unit for holding the information indicating the first server highest rank of in the first server group in the first management device holding portion.

  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, and the first management device A rank storage unit that stores rank information, which is information that defines the order in which a server group functions as the management apparatus, and the management apparatus is the management apparatus in each of the first server and the second 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 management device notification reception unit receive the notification before receiving the next notification in advance. A change determination unit that determines that a change of the management device is necessary when a predetermined time has elapsed, and the rank information is referred to when the change determination unit determines that a change of the management device is required By running A management device determination unit that causes the first management device holding unit to hold information indicating the first server having the highest rank in the first server group. The second management device determination unit Has received the notification from the second management device holding unit holding information indicating which of the first server group the current management device is, and the management device notification unit, and received the received A second management device notification receiving unit that causes the second management device holding unit to hold information indicating a notification transmission source.

  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 transmission source of the notification received by the first management device notification reception unit. Is not matched, it is determined that the management device needs to be changed.

  Furthermore, the management device means includes the identifier from the holding server storage unit that stores the file holding information, and the access source 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 containing the file, and when the inquiry reception unit receives an inquiry based on the acquisition request, by referring to the file holding information , A holding server determination unit that determines which of the holding servers is, and a server that is determined to be the holding server by the holding server determination unit, and transmits an electronic file according to the user request to the access source server A file transmission requesting unit that requests to do so.

  In this way, the first server having the function of the distributed file management apparatus communicates with another server, and it is detected that communication has been lost or communication has been restored, and a predetermined order is determined. Accordingly, the server having the highest rank among the first operating servers is set as the distributed file management apparatus. As a result, the server functioning as the distributed file management apparatus can be automatically switched, and the stability of the distributed file management system can be improved.

  More preferably, the inquiry reception unit further holds 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 a user-specified identifier in the server. The holding server determination unit refers to the file holding information when the inquiry receiving unit receives an inquiry based on the write request, so that the holding server The management device means further includes a holding response transmission unit that transmits information indicating the server determined to be the holding server by the holding server determination unit to the access source server. .

  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, and the file transmission request. A file storage control unit that reads an electronic file including an included identifier from the file storage unit, 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 With.

  Furthermore, 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 an electronic file received by the file receiving unit. Write a file to the file storage.

  As described above, when the access source server does not hold the electronic file according to the user's request, the access source server acquires the electronic file from the holding server and holds it. Thereby, when the request | requirement which acquires the same electronic file from any one of terminals is received again, the electronic file which self hold | maintains can be transmitted. Therefore, the access source server does not need to acquire again from the holding server for the electronic file acquired via one access source server, and the amount of information transferred on the network can be suppressed. It is possible to reduce the load on the server.

  More preferably, when the file storage control unit writes an electronic file in the file storage unit, the file server means notifies the first server group of a difference of the file storage unit before and after the writing. An update notification unit, wherein the management device means updates the file holding information based on the difference included in the notification received by the update notification reception unit and the update notification reception unit that receives the notification from the update notification unit. And an update unit.

  Further, the management device means further includes a file storage provided in the access source server when the update source unit 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 to the means, the identifier of the electronic file related to the acquisition request is notified to the distributed file management apparatus as the difference, and the update notification receiving unit is provided by the update notification means. In response to the notification, the holding information update unit adds information indicating the 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 receiving unit. By doing so, the file holding information is updated.

  Further, the management device means further includes a file storage provided in the access source server when the update notification unit receives a request for writing an electronic file in a file storage means provided in the access source server. When the electronic file related to the request is written in the 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 receiving means is the update notification means. In response to the notification, the holding information update unit receives the information indicating the access source server and the electronic file included in the difference in response to the notification including the hash value in the difference received by the update notification receiving unit. The file holding information is updated by adding the identifier.

  Thus, 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.

  The present invention can be realized not only as a distributed file management system including such characteristic means, but also as a distributed file management including steps as characteristic means included in an apparatus constituting the distributed file management system. It can also be realized as a method, or as a program that causes a computer to function as characteristic means included in an apparatus constituting a distributed file management system. Such a program can be distributed via a recording medium such as a CD-ROM (Compact Disc-Read Only Memory) or a communication network such as the Internet.

  A user can access any of a plurality of servers connected via a network from a terminal used by the user as long as at least one of the plurality of servers holds an electronic file desired by the user. It is possible to obtain the latest electronic file according to the request from the terminal. Therefore, the user does not need to be aware of whether or not the electronic file is the latest and the server that is accessed from the terminal, and the convenience of the user related to the acquisition of the electronic file distributed and held in a plurality of servers on the network. It becomes possible to improve the property.

  Furthermore, especially for electronic files that are frequently acquired via one server, the amount of information transferred over the network can be reduced, and the load on each server can be reduced. .

  Here, an electronic file frequently acquired is an electronic file that has been subject to an acquisition request two or more times by the same or different users, or two or more acquisitions by the same or different users within a certain period of time. The electronic file that was the subject of the request.

  Furthermore, regarding the management of the electronic file for providing the latest electronic file to the user, the amount of information transferred over the network can be suppressed, and the load on each server can be reduced.

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

  Furthermore, it is possible to detect falsification of the electronic file and transmit only the genuine electronic file to the user, thereby improving the reliability of the distributed file management system. Further, even when the operation of the server is stopped, the electronic file held by the server can be transmitted to the terminal used by the user.

  Furthermore, even when the operation of the distributed file management apparatus 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.

FIG. 1 is a diagram showing an outline of the configuration of a distributed file management system according to Embodiment 1 of the present invention. FIG. 2 is a diagram illustrating an example of a path of an electronic file 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 illustrating a specific example of an electronic file stored in a file storage unit included in the server A according to the first embodiment. FIG. 3B is a diagram illustrating a specific example of an electronic file stored in the file storage unit included in the server B according to the first embodiment. FIG. 3C is a diagram illustrating a specific example of the electronic file stored in the file storage unit included in the server C according to the first embodiment. FIG. 4 is a block diagram illustrating an example of a functional configuration included in the server A according to the first embodiment. FIG. 5 is a block diagram illustrating an example of a functional configuration provided in the distributed file management apparatus according to the first embodiment. FIG. 6 is a diagram illustrating an example of management server information stored in the holding server storage unit. FIG. 7 is a diagram illustrating an example of file holding information stored in the holding server storage unit. 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 the user transmits an acquisition request from the terminal. FIG. 9 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 the user transmits a write request from the terminal. In FIG. 10, when server A receives an acquisition request for file a from terminal a, processing executed in the distributed file management apparatus, server A, server B, and terminal a, and transmission / reception between these apparatuses are performed. 5 is a time chart showing an example of information. FIG. 11 shows the distributed file management device, server A, server B, and terminal when the server A receives an update request for the file a held by the server A after receiving the request for acquiring the file a from the terminal a. It is a figure which shows the example of the process performed in a, and the information transmitted / received between these apparatuses. FIG. 12 is a diagram showing the electronic file information stored in the file storage unit of the server A that has received the acquisition request for the file a from the terminal a. FIG. 13 shows a distributed file management device, server A, server B, and terminal 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. It is a time chart which shows the example of the process performed in a, and the information transmitted / received between these apparatuses. FIG. 14 is a diagram showing the electronic file information stored in the file storage unit of the server A updated by the request for updating the file a from the terminal a. FIG. 15 is a diagram showing the file holding information updated according to the update notification when the server A receives an update request for the file a from the terminal a. FIG. 16 is a diagram showing an example of a screen for a user to input a request for a specific file displayed on a monitor connected to a terminal used by the user. FIG. 17 is a diagram illustrating an example of a result displayed on a monitor connected to a terminal used by the user when the user instructs acquisition request for the file a. FIG. 18 is a diagram illustrating an example of a result displayed on a monitor connected to a terminal used by the user when the user instructs an update request for the 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 illustrating an example of an electronic file path common to electronic file information stored in a file storage unit included in the server A according to the second embodiment. FIG. 20B is a diagram illustrating 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 the second embodiment. FIG. 20C is a diagram illustrating an example of an electronic file path common to electronic file information stored in a file storage unit included in the server C according to the second embodiment. FIG. 21 is a block diagram illustrating an example of a functional configuration included in the server A 320 according to the second embodiment. FIG. 22 is a block diagram illustrating an example of a functional configuration included in the distributed file management apparatus 310 according to the second embodiment. FIG. 23 is a diagram illustrating an example of file holding information stored in the holding server storage unit. FIG. 24 is a diagram showing an example of deletion condition information according to the second embodiment. FIG. 25 is a time chart showing an example of processing executed in each device constituting the distributed file management system according to Embodiment 2 of the present invention when the user transmits an acquisition request from the terminal. 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 a user transmits a write request from the terminal. FIG. 27 is a flowchart 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 400c after the electronic file deletion processing by the distributed file management apparatus 310 is completed when the file holding information 400b has the contents shown in FIG. FIG. 29 is a block diagram illustrating an example of a functional configuration included in the distributed file management apparatus according to the first modification. FIG. 30 is a diagram illustrating an example of file holding information stored in the holding server storage unit. FIG. 31 is a time chart illustrating 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 illustrating the file holding information when the holding server determination unit executes the determination process in S212 when the server A receives a request for updating the file d. FIG. 33 is a diagram illustrating the file holding information after the processing executed by each device according to the present modification is completed when the server A receives a request for updating the file d from the user. FIG. 34 is a diagram showing an example of file holding information when an electronic file having old contents is to be deleted. FIG. 35A is a diagram illustrating a specific example of the electronic file stored in the file storage unit included in the server A according to the third embodiment. FIG. 35B is a diagram illustrating a specific example of the electronic file stored in the file storage unit included in the server B according to the third embodiment. FIG. 35C is a diagram illustrating a specific example of the electronic file stored in the file storage unit included 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. FIG. 37 is a block diagram illustrating an example of a functional configuration included in the distributed file management apparatus according to the third embodiment. FIG. 38 is a diagram illustrating an example of file holding information stored in the holding server storage unit. FIG. 39 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 an acquisition request from the terminal. 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 storage request from the terminal. 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 is a diagram illustrating an example of file holding information in the holding server storage unit updated according to the update notification and the hash value transmitted from the server A when the user transmits an update request for the file f from the terminal to the server A. is there. FIG. 43 is a diagram illustrating a specific example for explaining the storage unit information. FIG. 44 is a diagram illustrating an example of file holding information in the holding server storage unit after the processing in each device is completed when the user transmits an update request for the file f from the terminal to the server A. 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 an update request from the terminal. FIG. 46 is a diagram illustrating 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 the user transmits an update request from the terminal in the third embodiment. FIG. 48 is a diagram showing an outline of the configuration of the distributed file management system according to Embodiment 4 of the present invention. FIG. 49A is a diagram illustrating a specific example of an electronic file stored in a file storage unit included in the server A according to the fourth embodiment. FIG. 49B is a diagram illustrating a specific example of an electronic file stored in the file storage unit included in the server B according to the fourth embodiment. FIG. 49C is a diagram illustrating a specific example of the electronic file stored in the file storage unit included in the server C according to the fourth embodiment. FIG. 50 is a block diagram illustrating an example of an outline of a functional configuration included in the server A 820 according to the fourth embodiment. FIG. 51 is a block diagram illustrating an example of the details of the functional configuration of the file server unit 900 of the server A 820 according to the fourth embodiment. FIG. 52 is a block diagram illustrating an example of the functional configuration of the management device unit and the management device determination unit of the server A according to the fourth embodiment. 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 the file holding information 1000b stored in the holding server storage unit 1000 according to the fourth embodiment. 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 from the terminal. 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 write request from the terminal. FIG. 57 is a time chart of processing executed in each server to determine a management device. FIG. 58 is a detailed flowchart of the first management apparatus process executed by the management apparatus 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 shows the distributed file management system according to the fourth embodiment of the present invention when the server A accepts the acquisition request for the file d while the server B is stopped and when the server B recovers thereafter. It is a time chart which shows the specific example of the process performed in each apparatus. FIG. 61 is a diagram illustrating an example of the holding server information in the holding server storage units of the server A and the server C after the processing regarding the acquisition request for the file d executed while the server B is stopped. FIG. 62 is a diagram illustrating an example of the holding server information in the holding server storage unit of the server B after the processing related to the acquisition request for the file d executed while the server B is stopped. 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. FIG. 64 is a diagram showing an example of management server information in the holding server storage unit provided in the server functioning as the distributed file management apparatus according to the second modification of the present invention. FIG. 65 is a block diagram showing a functional configuration of a server D that is a server that does not function as a distributed file management apparatus according to the second modification of the present invention.

  The first to fourth embodiments of the distributed file management system according to the present invention will be described below with reference to the drawings.

(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. In the distributed file management system according to the first embodiment, any of a plurality of servers connected to a terminal used by a user via a communication line and including a file storage unit storing an electronic file is transmitted from the terminal. Receives user requests related to the received electronic file, executes processing related to the received user request in cooperation with the distributed file management device or other servers, and sends the results of the executed processing to the terminal used by the user It is an example of the system which performs.

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

  The distributed file management apparatus 10 is an apparatus that manages information related to electronic files held by a plurality of servers to be managed. The distributed file management apparatus 10 receives a user request related to an electronic file (hereinafter referred to as an “access source server”). ) Is an example of an apparatus that transmits information indicating a server (hereinafter referred to as “holding server”) that holds an electronic file related to a user request to an access source server in response to an inquiry from the user.

  The distributed file management apparatus 10 according to the present embodiment manages the server A20, the server B30, and the server C40, information on the electronic file stored and held in the server A20, and the electronic that is stored and held in the server B30. Information related to the file and information related to the electronic file stored and held in the server C40 are managed.

  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, and is, for example, a LAN (Local Area Network) or a WAN (Wide Area Network).

  The server A20 is a device that includes a file storage unit 25 that stores electronic files, and that receives requests related to electronic files from the terminals 60 and 65 and other servers 30 and 40 used by the user. When the server A20 receives the request, the server A20 cooperates with the distributed file management apparatus 10 as necessary to process the received request, and transmits the processed result to the transmission source of the request.

  The server B30 and the server C40 also have the same function, and include a file storage unit 35 and a file storage unit 45, respectively.

  Here, an example of the file structure related to the electronic file stored in each file storage unit 25, 35, 45 according to the first embodiment will be described with reference to FIG. 2, and each file storage unit 25, 35 will be described. , 45 will be described with reference to FIGS. 3A to 3C.

  FIG. 2 is a diagram illustrating 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.

  The user uses the terminal 60 or 65 to specify an electronic file by a path indicating a predetermined common folder structure as shown in the figure, and sends a request related to the specified electronic file to each server 20, 30. , 40, for example, to a server preset in each terminal 60, 65.

  Here, the “request related to the electronic file” includes an “acquisition request” that is a request to acquire the electronic file and a “write request” that is a request to write the 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.

  Each electronic file shown in the figure is specified by a relative path or file name having a folder related to the folder name “/ data” as a vertex.

  A folder whose folder name is “/ data” is immediately below the electronic file whose file name is “a”, the electronic file whose file name is “b”, and the electronic file whose file name is “d”. And a folder whose folder name is “c”. The folder whose folder name is “c” has an electronic file whose file name is “e” and an electronic file whose file name is “f” immediately below.

  Here, the “electronic file” includes file attribute information such as a file name and a file update date, in addition to information as the entity of the electronic file. Hereinafter, when simply referred to as “file x”, it indicates an electronic file whose file name is “x”. In addition, simply “folder x” indicates a folder whose folder name is “x”.

  In addition, “file x_2” and “file x_3” indicate an electronic file whose file name is “x”. That is, “file x”, “file x — 2”, and “file x — 3” are specified as electronic files with the file name “x”, but the entity and file attribute information other than the file name are different. It is related.

  The terminology related to the “request regarding the electronic file” and the notation method of the electronic file described here are commonly used in all the embodiments.

  3A to 3C are diagrams illustrating specific examples of electronic files stored in a file storage unit included in each server according to the first embodiment.

  FIG. 3A is a diagram illustrating an example of the electronic file information 25a stored in the file storage unit 25 included 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 illustrating 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”.

  FIG. 3C is a diagram illustrating an example of the electronic file information 45a stored in the file storage unit 45 included 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”.

  Here, the description returns to FIG.

  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.

  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. Further, when the terminal a60 acquires the result from the server that transmitted the request, the terminal a60 provides the acquired result to the user, for example, by displaying the acquired result on a monitor. The terminal b65 has a similar function.

  As described above, each file indicated by a predetermined file configuration is distributed and held in a plurality of servers, and even if the user accesses a server that does not hold a desired electronic file, the distributed file The management apparatus 10 enables processing of a user request related to the electronic file.

  A functional configuration included in each apparatus to enable such processing will be described with reference to FIGS.

  FIG. 4 is a block diagram illustrating an example of a functional configuration included in the server A20 according to the first embodiment. The server A20 receives a request from the user. When the user request is an acquisition request, the server A 20 keeps the latest entity as long as one of the servers under the management of the distributed file management apparatus 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.

  The server A 20 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, and a holding response reception unit. 81, a file transmission request reception unit 83, a file transmission unit 85, a file reception unit 87, a lock request transmission unit 89, an update notification unit 91, a completion notification reception unit 93, and a user request response unit 95. Prepare.

  Since the file storage unit 25 has been described with reference to FIG. 3, 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 determination unit 73 is a part that determines the type of request related to the electronic file received by the user request reception unit 71. In the first embodiment, requests related to electronic files include “acquisition request” and “write request” as described above, and “write request” includes “update request” and “storage request”. There is. The request type determination unit 73 determines which of the requests related to the electronic file received by the user request reception 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 searches 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. The electronic file is updated, and a new electronic file is stored in the file storage unit 25.

  The holding server inquiry unit 79 is a part that inquires the distributed file management apparatus 10 via the communication line 50 about which server holds the electronic file according to the user's request.

  The holding response receiving unit 81 is a part that receives the response of the distributed file management apparatus 10 that has received an 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 in the case where the holding response receiving unit 81 is an access source server, or the stored file storage units 25 and 35. , 45 is received.

  The file transmission request receiving unit 83 stores the electronic file in the access source server when the server provided with the file transmission request reception unit 83 is not the access source server and the server provided with the self holds an electronic file related to the user request. This is a part that receives a transmission request from the distributed file management apparatus 10.

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

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

  When the request type determination unit 73 determines that the user request type received by the user request reception unit 71 is a write request, the lock request transmission unit 89 writes an electronic file related to the write request. This is a part that transmits a lock request for excluding related processing to the distributed file management apparatus 10.

  The update notification unit 91 is a part that notifies the distributed file management apparatus 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, or a notification of completion of the write request if the user request is a write request.

  FIG. 5 is a block diagram illustrating an example of a functional configuration included 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, an update notification reception unit 110, a holding An information update unit 112, an update completion notification unit 114, a lock request reception unit 116, and a lock information holding unit 118 are provided.

  The holding server storage unit 100 stores management server information, which is information for specifying a server set as a management target of the distributed file management apparatus 10, and an electronic file held by each server included in the management server information. It is a storage unit that stores file holding information that is information to be included. The holding server storage unit 100 is realized by, for example, an HD (Hard Disk).

  Here, specific examples of the management server information and the file holding information according to the present embodiment will be described with reference to FIG. 6 and FIG.

  FIG. 6 is a diagram illustrating an example of the 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 includes a “server name” and an “IP address”.

  The “server name” includes the name given to the server that is the management target of the distributed file management apparatus 10. The “IP address” contains the IP address assigned to each server. The management server information 100a holds the server name and the IP address in association with each server that is the management target of the distributed file management apparatus 10.

  This figure shows, for example, that the “IP address” is “192.168..xxx.1” for the server A20 whose “server name” is indicated by “server A”.

  FIG. 7 is a diagram illustrating an example of the file holding information 100b stored in the holding server storage unit 100. 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”.

  The “file path” contains the path of the electronic file held by each server. As described with reference to FIG. 2, the path of the electronic file is common to all servers managed by the distributed file management apparatus 10.

  The “server name” has 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.

  This figure shows, for example, that the servers holding the electronic file whose “file path” is indicated by “/ data / a”, that is, “file a” or “file a_2” are the server A20 and the server B30. Show.

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

  In this figure, for example, for an electronic file whose “file path” is indicated by “/ data / a”, the “flag” of the electronic file held by “server A” is “0” and held by “server B”. The “flag” of the electronic file to be displayed is “1”.

  That is, the electronic file held by “server A” is “/ data / a” as shown in FIG. 3A. Further, the electronic file held by “server B” is “/ data / a_2” as shown in FIG. 3B. Thus, the “flag” indicates that “server B” includes newer content than “server A” for the electronic file specified by “/ data / a”.

  From here, it returns to description 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 the server.

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

  The holding response transmission unit 106 is a part that responds whether or not the access source server holds the latest electronic file according to the user's request.

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

  The update notification receiving unit 110 is a part that receives a notification from the server that a new electronic file is stored in a file storage unit included in the server or that an electronic file stored in the file storage unit has been updated. It is.

  The holding information update unit 112 is a part that updates the file holding information 100 b stored in the holding server storage unit 100 in accordance with the content of the notification received by the update notification receiving unit 110.

  The update completion notification unit 114 is a part that transmits to the server 20 a notification with the content that the update of the holding server storage unit 100 by the holding information update unit 112 has been completed.

  The lock request receiving unit 116 is a part that receives a lock request transmitted from the server 20.

  The lock information holding unit 118 temporarily stores information indicating the electronic file related to the lock request received by the lock request receiving unit 116 until the processing executed by the holding information update unit 112 in relation to the electronic file is completed. It is a part to memorize and hold.

  Since the distributed file management apparatus 10 and the servers 20, 30, and 40 have the functions described above, each server 20 can be accessed regardless of which server the user accesses from the terminals 60 and 65 that the user uses. As long as any one of, 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 a plurality of servers hold electronic files having different contents, the user holds any electronic file having the latest contents. It is possible to obtain an electronic file having the latest contents without being aware of whether or not and accessing an arbitrary server.

  FIG. 8 and FIG. 9 show a series of processes executed in the distributed file management apparatus 10 and each server 20, 30, 40 when the user transmits an acquisition request or a write request using the terminals 60, 65. The description will be given with reference.

  FIG. 8 is a time chart illustrating 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 an acquisition request from the terminals 60 and 65. .

  The “terminal” shown in the figure is a terminal used by the user, and is either the terminal a60 or the terminal b65 in the present embodiment.

  In addition, the “access source server” shown in the figure 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 any one of the server A20, the server B30, and the 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. Any of the server A20, the server B30, and the server C40 is a candidate for the holding server in the present embodiment.

  First, the user request receiving unit 71 of the access source server 20 (30, 40) receives the acquisition request transmitted from the terminal 60 (65) used by the user 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.

  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 the access source server is a holding server by referring to the file holding information 100b of the holding server storage unit 100 (S103).

  First, when it is determined that the access source server is the holding server (Yes in S103), the holding response transmission unit 106 continues to notify that the access source server is the holding server (hereinafter referred to as “holding notification”). 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 it is a different part provided in the same server as the server provided with the part that is the subject of the operation.

  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.

  When it is determined that the access source server is not a holding server (No in S103), the holding server determination unit 104 determines whether there is a holding server (S107).

  First, when it is determined that there is no holding server (No in S107), the holding response transmission unit 106 transmits a notification (hereinafter, referred to as “non-holding notification”) that indicates that there is no holding server. The holding response receiving unit 81 receives a non-holding notification (S108).

  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 (S109), and ends the processing. To do.

  If it is determined that there is a holding server (Yes in S107), then the file transmission request unit 108 transmits a file transmission request to the holding server, and the file transmission request receiving unit 83 of the holding server receives the file transmission request. (S110).

  Here, the “file transmission request” is a request for transmitting the electronic file to another server to the server holding the specific electronic file.

  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).

  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 (S112).

  Subsequently, the user request response unit 95 of the access source server acquires an electronic file related to the user's acquisition request via its file storage control unit 77, and uses the electronic file by the terminal 60 (65 (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 own file storage unit 25, 35, 45 (S114).

  Subsequently, the update notification unit 91 transmits a notification (hereinafter referred to as “update notification”) that includes updating the file holding information 100 b of the holding server storage unit 100 included in the distributed file management apparatus 10, and distributes it. The update notification receiving unit 110 of the file management apparatus 10 receives the update notification (S115).

  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 server 20, 30, 40 in the file holding information 100b, or The notification is 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 according to the update notification acquired from the update notification receiving unit 110 (S116), and ends the process.

  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 a user transmits a write request from the terminals 60 and 65. is there.

  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”.

  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.

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

  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 determination unit 73 causes the request information holding unit 75 to hold the electronic file related to the write request (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 excludes the write request related to the electronic file related to the write request. A request (hereinafter referred to as “lock request”) is transmitted 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).

  Further, the file storage control unit 77 receives the determination by the request type determination unit 73 that the acquired request is a write request, acquires the electronic file held by the request information holding unit 75, and acquires the acquired electronic file. The file is written in its own file storage unit 25, 35, 45 (S205).

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

  First, when it is determined that the writing has not been completed (No in S206), the update notification unit 91 waits.

  When 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, transmits an update notification to the distributed file management apparatus 10, and performs distributed file management. The update notification receiving unit 110 of the device 10 receives the update notification (S207).

  Subsequently, the holding information update unit 112 updates the file holding information 100b of the holding server storage unit 100 according to the update notification acquired from the update notification receiving unit 110 (S116).

  Subsequently, the holding information update unit 112 releases the lock by deleting the information held by the lock information holding unit 118 (S209).

  Subsequently, the update completion notification unit 114 receives a notification of completion from the file storage control unit 77, notifies the access source server of the completion of the update process, and the completion notification receiving unit 93 of the access source server receives the notification of completion. (S210).

  Subsequently, the user request response unit 95 of the access source server receives the fact that the completion notification receiving unit 93 has received the notification of completion, and the terminal used by the user that processing related to the user's write request has been completed. 60 (65) (S211), and the process ends.

  The above is the processing executed in each device constituting 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 will be described by taking as an example the case where the server A20 receives a request for acquiring the file a from the terminal a60, and then receives the update request for the file a held by the server A20. The processing executed in each device constituting the management system will be described more specifically with reference to FIGS.

  FIG. 10 shows the processes executed in 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 between these devices. It is a time chart which shows the example of the information transmitted / received.

  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). Here, the “acquisition request” is information having a request for acquiring the file a having the latest contents by the terminal a60 used by the user.

  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 the holding server inquiry unit 79 performs distributed file management. When the device 10 is inquired 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 the server A20 is a holding server by referring to the file holding information 100b of the holding server storage unit 100 (S103).

  Here, when the file holding information 100b has the content shown in FIG. 7, the server A20 holds the file indicated by “/ data / a”, that is, the file a, but the “flag” is “0”. The server A20 does not hold the file a having the latest contents. Accordingly, the holding server determination unit 104 determines that the server A20 is not a holding server (No in S103).

  When it is determined that the server A20 as the access source server is not a holding server (No in S103), the holding server determination unit 104 determines whether there is a holding server (S107).

  Here, when the file holding information 100b has the contents shown in FIG. 7, the server B30 holds the file indicated by “/ data / a”, 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).

  If it is determined that there is a holding server (Yes in S107), the file transmission request unit 108 transmits a transmission request for the file a to the server B30 that is the holding server, and the file transmission request receiving unit 83 of the holding server. Receives a transmission request for file a (S110).

  Here, the “transmission request for file a” includes a request for transmitting the file a to the server A20 to the server B30 holding the file a.

  Subsequently, the file storage control unit 77 of the server B30 reads the file a from its own file storage unit 35 (S111).

  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).

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

  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 illustrating the electronic file information 25a stored in the file storage unit 25 of the server A20 that has received an acquisition request for the file a from the terminal a60. “A” in FIG. 3A indicating 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 the present drawing.

  From here, it returns to description 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 (S115).

  Here, the “update notification” is a notification having the content that the file a is updated in the file storage unit 25 of the server A20 in the file holding information 100b.

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

  Here, FIG. 12 is a diagram illustrating the file holding information 100b updated in accordance with the update notification when the server A20 receives an acquisition request for the file a from the terminal a60. “0” of “Flag” of “Server A” corresponding to “/ data / a” of FIG. 7 indicating the initial state of the file holding information 100b is updated to “1” in this drawing.

  As described above, when the server A20 receives an acquisition request for the file a from the terminal a60, the processing executed in the distributed file management device 10, the server A20, the server B30, and the terminal a60 and the transmission / reception between these devices Information. Thereafter, when an update request for the file a held by the server A20 is received, the processing executed in the distributed file management device 10, the server A20, the server B30, and the terminal a60 and the transmission / reception between these devices is performed. The following information will be explained.

  FIG. 13 shows the distributed file management device 10, the server A20, and the server B30 when the server A20 receives an update request for the file a held by the server A20 after receiving an acquisition request for the file a from the terminal a60. FIG. 5 is a time chart showing an example of processing executed in the terminal a60 and information transmitted / received between these devices. FIG.

  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). The “write request” here is information containing 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 the request type determination unit 73 The information holding unit 75 holds 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 distributes the lock request of the file a that is the electronic file related to the write request. 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 related to the file a, which is an electronic file related to the received lock request (S204).

  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 acquires the acquired file a Is written in its own file storage unit 25, 35, 45 (S205).

  Here, FIG. 14 is a diagram showing the electronic file information 25a stored in the file storage unit 25 of the server A20 that has been updated by the request to update the file a from the terminal a60. “A_2” in FIG. 11 indicating 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 drawing.

  From here, it returns to description of FIG.

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

  First, when it is determined that writing has not been completed (No in S206), the file storage control unit 77 continues writing until completion.

  When 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 updates the file a in the file storage unit 25 of the server A20. An update notification as content 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).

  Subsequently, the holding information update unit 112 updates the file holding information 100b of the holding server storage unit 100 according to the update notification acquired from the update notification receiving unit 110 (S116).

  Subsequently, the holding information update unit 112 releases the lock by deleting the information related to the file a held by the lock information holding unit 118 (S209).

  Subsequently, the update completion notification unit 114 receives a notification of completion 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 completion notification reception unit 93 of the server A20 completes the completion. A notification is received (S210).

  Subsequently, the user request response unit 95 of the server A20 receives the fact that the completion notification receiving unit 93 has received the notification of completion, and the terminal a60 used by the user that the processing related to the user's write request has been completed. (S211), and the process ends.

  Here, FIG. 15 is a diagram illustrating the file holding information 100b updated in accordance with the update notification when the server A20 receives an update request for the file a from the terminal a60. “1” of “Flag” of “Server B” corresponding to “/ data / a” in FIG. 12 indicating the file holding information 100b after receiving the acquisition request of the file “a” is updated to “0” in this figure. Has been.

  The above is the distributed file management system according to the first embodiment of the present invention when the server A20 accepts an acquisition request for the file a from the terminal a60 and then accepts an update request for the file a held by the server A20. Is a process executed in each device constituting the.

  Next, an example of an input screen and a result display screen displayed on a 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 inputting a request for a specific file displayed on a monitor connected to the terminal 60 (65) used by the user. The user sees the screen display shown in the figure and transmits an acquisition request and a write request to the server.

  The input screen 200 illustrated in this 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.

  The content displayed on the file structure display unit 202 has the same structure as the path of the electronic file shown in FIG. 2, and the file holding of the distributed file management apparatus 10 from the terminal 60 (65) via the servers 20, 30, 40. It is acquired by accessing the information 100b.

  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.

  The selected file display unit 204 is a part that displays an electronic file selected by the user. In this figure, the file a is selected as described above. Therefore, a path “/ data / a” is displayed in “selected file” of the selected file display unit 204.

  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 an acquisition request for the file a to any of the servers 20, 30, and 40.

  The write file input unit 208 is a part for inputting an electronic file for updating or newly storing a file held by the servers 20, 30, and 40. This figure is an example in which the file xyz held by the terminal a60 (65) specified by the path "terminal a / xyz" is input.

  The write button 210 is a button for transmitting a write request to the terminal 60 (65). When the user presses the write button 210 on the input screen 200 as shown in this figure, since the terminal 60 (65) has selected the file a in any of the servers 20, 30, and 40, the file a is written. Send request. Further, the entity of the file a stored in the file storage units 25, 35, 45 updated by this write request is the same as the entity of the file xyz input to the write file input unit 208.

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

  The acquisition result display screen 220 shown in the figure is a screen displayed on the monitor when the terminal 60 (65) used by the user acquires the file a by transmitting a request for acquiring the file a.

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

  The acquired file display unit 222 displays the name of the acquired file.

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

  The save button 226 is a button for saving the acquired file in the storage unit included in the terminal 60 (65). When the user presses using a mouse or the like, the acquired file is stored in the storage unit of the terminal 60 (65).

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

  The update result display screen 230 shown in the figure is a screen displayed on the monitor when 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.

  In the update result display section 232, when the write request transmitted from the terminal 60 (65) is a request to update the electronic file, the name of the electronic file related to the request and the processing is completed. Is shown.

  Thereby, the user using the terminal 60 (65) can know that the processing is completed.

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

  With such display screens, the user can send a request on the monitor and obtain the result of the processing related to the request.

  The distributed file management apparatus and the distributed file management system according to Embodiment 1 of the present invention have been described above, but 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 illustrating another example of the file holding information 100c stored in the holding server storage unit 100. 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.

  The electronic file whose “creation date” of the electronic file is the closest to the present holds the latest contents. Therefore, it is possible to determine whether or not the electronic content held by each server is the latest based on the “creation date” of the electronic file.

  For example, in the file holding information 100c shown in this figure, “server A” and “server B” hold the file “a” whose “file path” is “/ data / a”, and “server A” The information includes that the “creation date” of the file “a” to be held is “March 3, 2006” and the “creation date” of the file “a” held by “Server B” is “March 20, 2006”.

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

  As described above, the distributed file management system according to Embodiment 1 writes a new electronic file only in the file storage unit of the access source server when a write request is accepted. Further, when the distributed file management system according to the first embodiment receives an acquisition request, the user accesses any server by acquiring the electronic file from the server holding the electronic file including the latest contents. An electronic file having the latest contents is provided to the user without being conscious of whether or not it was done.

  As a result, when there are a plurality of holding servers related to the update request, it is possible to suppress the data transfer amount compared to a case where updating is performed while synchronizing electronic files held by the plurality of holding servers. In particular, when there are a large number of servers that hold the same electronic file, the advantage of suppressing the data transfer amount at the time of update is great.

(Embodiment 2)
In the distributed file management system according to the first embodiment, when the access source server that has received the acquisition request does not hold the electronic file related to the acquisition request, the information of the server related to the management is obtained from information from the distributed file management device. The server holding the electronic file related to the acquisition request is specified, the electronic file related to the acquisition request is acquired from the server, and stored in its own file storage unit.

  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 that are rarely requested for acquisition or update from a terminal.

  Therefore, in the second embodiment, a distributed file management system capable of effectively using storage is provided.

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

  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, and thus detailed description regarding the outline of the configuration of the distributed file management system is omitted here. .

  The distributed file management system according to the second embodiment includes terminals 60 and 65 used by a user, a server A 320 that receives a user request from each of the terminals 60 and 65, and includes file storage units 25, 35, and 45, respectively. The server B330, the server C340, and a distributed file management device that manages information related to electronic files distributed and held in each server by transmitting and receiving information to and from these servers.

  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. 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 a file storage unit included in each server according to the second embodiment.

  FIG. 20A is a diagram illustrating an example of the electronic file information 25b stored in the file storage unit 25 included 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 illustrating an example of the electronic file information 35b stored in the file storage unit 35 included in the server B 330 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 d”, and “file e”.

  FIG. 20C is a diagram illustrating an example of the electronic file information 45b stored in the file storage unit 45 included in the server C340 according to the second embodiment. 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 illustrating an example of a functional configuration included in the server A 320 according to the second embodiment. Similarly to the server A 20 according to the first embodiment, the server A 320 receives a request from the user. When the user request is an acquisition request, the server A 320 manages the electronic file related to the received acquisition request under the management of the distributed file management device 310. As long as any one of the servers is held, the electronic file including the latest entity is transmitted to the terminal used by the user. Also, 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, and a holding response reception unit. 81, a file transmission request reception unit 83, a file transmission unit 85, a file reception unit 87, a lock request transmission unit 89, a completion notification reception unit 93, a user request response unit 95, an update notification unit 391, A deletion request receiving unit 322.

  In the server A320 according to the second embodiment, parts having the same functions as those of the server A20 according to the first embodiment are denoted by the same reference numerals, and description thereof is omitted here.

  The deletion request receiving unit 322 is a part that receives a request for deleting a part or all of the electronic file stored in the file storage unit 25 from the distributed file management device 310 via the communication line 15.

  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 deletes part or all of the electronic file from the electronic file information 25a. In this case, the distributed file management apparatus 10 is notified of the stored, updated, or deleted contents.

  The above is the functional configuration of the server A 320 according to the present embodiment. The server B330 and the server C340 also have the same functional configuration as the server A320.

  FIG. 22 is a block diagram illustrating an example of a functional configuration included 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 or longer. When a plurality of servers hold an electronic file for which the server has not received a request, the server deletes the electronic file held by any one other than the 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, a lock information holding unit 118, and a holding Server storage unit 400, retention server determination unit 404, update notification reception unit 410, retention information update unit 412, deletion condition storage unit 420, clock unit 422, deletion target determination unit 424, and deletion request unit 426 With.

  In the distributed file management apparatus 310 according to the second embodiment, parts having the same functions as those of the distributed file management apparatus 10 according to the first embodiment are denoted by the same reference numerals. Description of is omitted.

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

  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 the second embodiment will be described with reference to FIG.

  FIG. 23 is a diagram illustrating an example of the file holding information 400b stored in the holding server storage unit 400. 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”.

  The “file path” and “server name” of the file holding information 400b according to the present embodiment are the “file path” and “file path” of the file holding information 100b according to the first embodiment described with reference to FIG. Since the same information is stored for each of the “server name”, a detailed description thereof is omitted here.

  The “access date” stores the date when the server indicated by the information stored in the “server name” last received a user request related to the electronic file indicated by the “file path”.

  For example, for the electronic file whose “file path” is “/ data / a”, the last day when “Server A” received the request from the user is “20066033”, that is, “March 2006” 3 days ".

  From here, it returns to description 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.

  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 the determination to the holding information update unit 112.

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

  The update notification reception unit 410 stores new electronic files in the file storage units 25, 35, and 45 included in each server, updates the electronic files stored in the file storage units 25, 35, and 45, or This is a part that receives a notification from the server that the contents of the electronic files stored in the storage units 25, 35, and 45 have been deleted.

  The holding information update unit 412 is a part that updates the file holding information 400 b stored in the holding server storage unit 400 in accordance with the information received from the holding server determination unit 404 or the information received by the update notification receiving unit 410.

  The deletion condition storage unit 420 is a part that stores deletion condition information that is information including a condition for deleting an electronic file held by each server.

  FIG. 24 is a diagram illustrating an example of the deletion condition information 420a according to the second embodiment. The deletion condition shown in the figure is an example on the 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 holding information 400b. .

  From here, it returns to description of FIG.

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

  The deletion target determination unit 424 is a part that determines an electronic file to be deleted for each server. More specifically, the deletion target determination unit 424 has an electronic file that has been retained for a period included in the deletion condition information 420a from the date indicated by the “access date” of the file retention information 400b, and When there are a plurality of servers holding electronic files, it is determined that only the electronic files held by the server with the newest “access date” are left and the electronic files held by other servers are deleted.

  The deletion target determination unit 424 according to the present embodiment executes the above determination process at a predetermined cycle.

  The deletion request unit 426 is a part that transmits a request to delete the electronic file to a server that holds the electronic file determined as a deletion target by the deletion target determination unit 424.

  Since the distributed file management apparatus 10 and each of the servers 20, 30, and 40 are provided with the functions as described above, the user accesses any server from the terminals 60 and 65 that the user uses as in the first embodiment. Regardless, as long as any one of the servers 20, 30, and 40 holds the electronic file, the electronic file can be acquired.

  In addition, when a plurality of servers hold electronic files related to user acquisition requests, the electronic files are synchronized, so the user is conscious of which server holds the electronic file having the latest contents. It is possible to obtain an electronic file having the latest contents without accessing the server and by accessing an arbitrary server.

  In addition, when the same electronic file is held repeatedly on multiple servers, the electronic file held by one of the servers is deleted and the electronic file held by another server is deleted according to a predetermined condition. Therefore, effective use of storage becomes possible.

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

  In this figure, the process which attached | subjected the same referential mark as the process performed in each apparatus which concerns on Embodiment 1 shown in FIG. 8 shows the same process. For this reason, descriptions of processes with the same reference numerals are omitted here.

  The difference between the time chart shown in this figure and the time chart shown in FIG. 8 is that a holding notification (S104) is made after an affirmative determination is made in the holding determination (S103) of the access source server regarding the electronic file (Yes in S103). Until then, the holding information update process is executed (S310).

  When the holding server determination unit 404 determines that the access source server is the holding server (Yes in S103), the holding information update unit 412 continues to receive the determination of the holding server determination unit, and the access source server holds. The “access date” of the file holding information 400b related to the electronic file related to the user request is updated with the date acquired from the clock unit 422 (S301).

  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 from the terminals 60 and 65. is there.

  In this figure, the process which attached | subjected the same referential mark as the process performed in each apparatus which concerns on Embodiment 1 shown in FIG. 9 shows the same process. For this reason, descriptions of processes with the same reference numerals are omitted here.

  The difference between the time chart shown in this figure and the time chart shown in FIG. 8 is that the distributed file management apparatus 310 determines whether there is a holding server other than the access source server, and there is a holding server other than the access source server. The electronic file held by the server is also updated. By such processing, the contents of the electronic files that are held redundantly in a plurality of servers are synchronized.

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

  If it is determined that there is no holding server below the access source server (No in S212), the distributed file management apparatus 310 waits until a request or inquiry from the server is received.

  When 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 request reception unit 83 of the access source server 320. 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.

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

  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 receiving unit 87 (S216).

  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).

  More specifically, the “update notification” here means that a new electronic file has been stored in the file storage units 25, 35, 45 of the access source servers 20, 30, 40, or the electronic file has been updated. This is a notification with the contents.

  Subsequently, the holding information update unit 412 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 410 (S218), and ends the process.

  The above is the processing executed in each device when any of the servers accepts a user request. In the present embodiment, as described above, for a server that holds an electronic file that has passed a certain period from the date of last access by the user, the electronic file is deleted. 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 determination 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).

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

  If it is determined that the update time is reached (Yes in S300), the distributed file management apparatus 310 starts the last access described below for all electronic files included in the file holding information 400b of the holding server storage unit 400. The processing from the determination of whether a predetermined time has passed (S302) to the update of the stored information (S307) is repeated (S301).

  First, the deletion target determination unit 424 acquires the “access date” of the file holding information 400b, the deletion condition information 420a, and the current date from the clock unit 422, and the current date is “delete date” from the deletion condition information. It is determined whether the period included in 420a has elapsed (S302).

  When it is determined that the period included in the deletion condition information 420a has not elapsed since the current date is “access date” (No in S302), an elapsed time determination process (S302) is executed for the next electronic file. .

  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 stores the same electronic file It is determined whether or not there is a plurality (S303).

  When it is determined that there are not a plurality of servers that hold the same electronic file (No in S303), an elapsed time determination process (S302) is executed for the next electronic file. Therefore, when there is only one electronic file holding server that has passed a certain period from the last access date, the electronic file is not deleted.

  Further, when it is determined that there are a plurality of servers holding the same electronic file (Yes in S303), each server holds except the server with the newest “access date” among the servers holding the electronic file. The electronic file is determined to be deleted (S304).

  The deletion request unit 426 transmits a deletion request for the electronic file to the server holding the electronic file determined as the deletion target by the deletion target determination unit 424 (S305).

  The update notification receiving unit 410 receives an update notification from the server that has executed the electronic file deletion process related to the request from the deletion request unit 426 (S306).

  The “update notification” received here is a notification that indicates that the electronic file stored in the file storage units 25, 35, 45 of the holding servers 20, 30, 40 has been deleted.

  Subsequently, the holding information update unit 412 updates the file holding information 400b in accordance with the update notification received by the update notification receiving unit 410 (S307), and ends the process.

  The above is the processing executed by the distributed file management apparatus 310 when deleting the electronic file held by each server. In the case where the file holding information 400b has the contents shown in FIG. 23, the distributed file management apparatus 310 more specifically performs the processing executed after the deletion target determining unit 424 determines that the update time is reached (Yes in S300). explain.

  First, for the file a whose “file path” is “/ data / a”, the current date acquired from the clock unit 422 is “access date” from “March 3, 2006”, and the deletion condition information 420a. It is determined whether or not “30 days”, which is a period included in the list, has elapsed (S302). Here, the current date is “March 30, 2006”.

  Since “March 30, 2006” has not passed “30 days” from “March 3, 2006” (No in S302), the deletion target determination unit 424 continues with the next file “ The same determination process (S302) is executed for the file b that is “/ data / b”.

  Similarly to the case of the file a, since the current date has not passed the period included in the deletion condition from the “access date” (No in S302), the deletion target determination unit 424 continues to The same determination process (S302) is executed for the file e which is the next file “/ data / c / e”.

  Similarly to the case of the file a, since the current date has not passed the period included in the deletion condition from the “access date” (No in S302), the deletion target determination unit 424 continues to delete the file e. The same determination process (S302) is executed for the file d which is “/ data / d” which is the next file.

  For file d, the holding servers are server B330 and server C340. For the file d, the “access date” of the server B 330 is “March 3, 2006”, and the current date “March 30, 2006” has not passed “30 days” from the “access date”. .

  Further, for the file d, the “access date” of the server C 340 is “February 20, 2006”, and the current date “March 30, 2006” has passed “30 days” from the “access date”. ing.

  Therefore, the deletion target determination unit 424 determines that the period included in the deletion condition information 420a has elapsed from the “access date” for the current date for the file d (Yes in S302).

  Subsequently, since there are a plurality of servers that hold the file d, the deletion target determination unit 424 relates to the latest “access date” among the servers B 330 and C 340 that are the servers that hold the file d. A server other than the server B330 that is the server to be executed, that is, the file d held by the server C340 is determined as a deletion target (S303).

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

  Subsequently, the update notification receiving unit 410 receives an update notification from the server C 340 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 indicates that the file d stored in the file storage unit 45 of the server C 340 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 apparatus 310 is completed when the file holding information 400b has the contents shown in FIG.

  As described above, since the file a, the file b, and the file e are not deleted, the file holding information 400b after the deletion process is not changed.

  Further, since the file d held by “server C” is deleted, the holding server of “/ data / d” is updated to only “server B”.

  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 will be described with reference to 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 above. Therefore, explanation here is omitted.

  The distributed file management apparatus and distributed file management system according to the second embodiment of the present invention have been described above, but the present invention is not limited to this embodiment.

  For example, the distributed file management apparatus 310 according to the second embodiment executes the deletion process at a predetermined cycle, but may execute the deletion process when the server receives an update request from the user.

  Further, 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.

(Modification 1)
Here, Modification 1 in which the deletion process is executed when the server receives an update request from the user will be described with reference to FIGS. 29 to 33.

  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 servers to be managed 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.

  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, a lock information holding unit 118, an update A 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 are provided.

  Similar to the holding server storage unit 400 according to the second embodiment, the holding server storage unit 500 is a storage unit that stores management server information and file holding information, and is realized by, for example, an HD (Hard Disk) Is done.

  Since 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, description thereof is omitted here.

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

  FIG. 30 is a diagram illustrating 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 includes a “file path” and a “server name”.

  The “file path” and “server name” of the file holding information 500b according to this modification are the “file path” and the “server” of the file holding information 400b according to the second embodiment described with reference to FIG. “Name” and similar information are stored.

  The difference between the file holding information 500b according to this modification and the file holding information 400b according to the second embodiment is that the file holding information 500b according to this modification does not include an “access date”.

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

  From here, it returns to description 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 receiving unit 102 by referring to the holding server storage unit 500.

  The holding server determination unit 504 determines a server that holds an electronic file related to the update request in addition to the access source server.

  Similar to the deletion target determination unit 424 according to the second embodiment, 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 the present modification acquires information related to 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 related to the server. Hand over to 426.

  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 receives an update request from the user. In this figure, the case where the server A320 is an access source server and the server A320 receives an update request for the file d will be specifically described.

  In this figure, the process which attached | subjected the same referential mark as the process performed in each apparatus which concerns on Embodiment 2 shown in FIG. 26 shows the same process. For this reason, descriptions of processes with the same reference numerals are omitted here.

  The difference between the process shown in this figure and the process shown in FIG. 26 is that in the determination of whether there is a holding server other than the access source server (S212), it is determined that there is a holding server other than the access source server. (Yes in S212) 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 as shown in FIG. .

  FIG. 32 is a diagram illustrating the file holding information 500c when the holding server determination unit 504 executes the determination process in S212 when the server A 320 receives a request to update the file d. The initial state of the file holding information is assumed to be 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).

  From here, with reference to FIG. 31, the processing after it is determined that there is a holding server other than the access source server (Yes in S212) will be described.

  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. It is determined which server is (S212).

  Regarding the file d, since the holding servers other than the server A320 that is the access source server are “server B” and “server C”, the holding server determination unit 504 includes a holding server in addition to the access source server. The holding servers are determined to be “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 determination unit 524 determines the files d held by “server B” and “server C”, which are the holding servers determined by the holding server determination unit 504, as deletion targets (S313).

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

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

  If it is determined that there is a deletion target (Yes in S314), then the deletion request unit 426 transmits a file deletion request to the holding server, and the holding server deletion request receiving unit 322 requests the file deletion. Is received (S315).

  Here, since the file d held by “server B” and “server C” is determined to be a deletion target, the deletion target determination unit 524 determines that there is a deletion target (Yes in S314), and the deletion request unit 426 The deletion request for the file d is transmitted to the server B330 and the server C340, and the deletion request receiving unit 322 of the server B330 and the server C340 receives the deletion request for the file d, respectively (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, the file storage control unit 77 of the server B330 and the server C340 deletes each file d stored in the file storage units 35 and 45 (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 that indicates that the electronic file stored in the file storage units 25, 35, 45 of the holding servers 20, 30, 40 has been deleted.

  Here, the update notification unit 391 of the server B 330 and the server C 340 transmits an update notification that indicates that the file d stored in the file storage units 35 and 45 has been deleted, and the update notification reception unit 410 An update notification is received (S317).

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

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

  FIG. 33 is a diagram illustrating the file holding information 500d after the processing executed by each device according to the present modification is completed when the server A 320 receives an update request for the file d from the user. In the file holding information 500d shown in the figure, “server B” and “server C” are deleted from the “server name” corresponding to the file d from the file holding information 500c shown in FIG. The “server name” is only “server A”.

  In the first modification 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 the processing. Therefore, the deletion target determination unit 424 does not need to determine the deletion target based on whether or not there are a plurality of servers that hold electronic files related to deletion, and can simplify the process.

  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 performs the implementation shown in FIG. This can be realized by combining the function of the distributed file management apparatus 310 according to the second embodiment and the function of the distributed file management apparatus 310 according to the first modification shown in FIG.

  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, and the electronic file to be deleted has old content. You may include electronic files.

  FIG. 34 is a diagram showing an example of the file holding information 400d in the case where an electronic file having old contents is to be deleted. As shown in the figure, the file holding information 400d in this case is composed of “file path”, “server name”, “flag”, and “access date”.

  The “file path”, “server name”, and “access date” of the file holding information 400d are “file path” and “file path” of the file holding information 400b according to the second embodiment described with reference to FIG. The same information is stored for each of “server name” and “access date”. Further, in the “flag” of the file holding information 400d, the same information as the “flag” of the file holding information 100b according to the first embodiment described with reference to FIG. 7 is stored.

  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.

(Embodiment 3)
In the distributed file management system according to the first and second embodiments, a plurality of servers may hold an electronic file having the latest contents in an overlapping manner. In this way, it is possible to reduce the amount of information that moves through the communication line in the processing related to the acquisition request for electronic files that are frequently acquired by the user.

  However, the first embodiment and the second embodiment have a problem that a plurality of servers do not effectively utilize the same electronic file.

  Therefore, Embodiment 3 provides a distributed file management system that makes it possible to actively utilize duplication holding by a plurality of servers and prevent tampering of electronic files by a third party. Also provided is a distributed file management system that can improve fault tolerance of servers and disks.

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

  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, and thus detailed description on the outline of the configuration of the distributed file management system is omitted here. .

  The distributed file management system according to the third embodiment includes terminals 60 and 65 used by users and file storage units 25, 35, and 45, respectively, and a server A 620 that receives user requests from the terminals 60 and 65, and The server B 630, the server C 640, 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.

  In addition, since the folder configuration common to the electronic files stored in the file storage unit provided in each server shown in FIG. 2 is the same in the distributed file management system according to the third embodiment, Description is omitted.

  FIG. 35A to FIG. 35C are diagrams illustrating specific examples of electronic files stored in a file storage unit included in each server according to the third embodiment.

  FIG. 35A is a diagram illustrating an example of the electronic file information 25b stored in the file storage unit 25 included in the server A 620 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”.

  FIG. 35B is a diagram illustrating an example of the electronic file information 35b stored in the file storage unit 35 included in the server B 630 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 d”, and “file e”.

  FIG. 35C is a diagram illustrating an example of the electronic file information 45b stored in the file storage unit 45 included in the server C 640 according to Embodiment 3. 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”.

  FIG. 36 is a block diagram illustrating an example of a functional configuration included in the server A 620 according to the third embodiment. Server A 620 receives a request from the user, and if the user request is an acquisition request, server A 620 manages the electronic file related to the received acquisition request in the distributed file management apparatus 610. As long as any one of the servers below holds, the electronic file including the latest entity is transmitted 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 a hash value of the electronic file in order to detect falsification.

  The server A 620 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 holding server inquiry unit 79, a holding response receiving unit 81, and a 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 request response unit 95, hash value request reception unit 624 , A hash value calculation unit 626, a hash value transmission unit 628, a storage unit information request reception unit 630, a storage unit information transmission unit 632, a copy destination reception unit 634, and a file storage control unit 677.

  In 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, and description thereof is omitted here.

  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.

  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 apparatus 610.

  The storage unit information request receiving unit 630 is a part that receives information related to the state of the file storage unit 25 provided therein, for example, a request for free space.

  The storage unit information transmission unit 632 is a part that acquires information indicating the state of the file storage unit 25 from the file storage control unit 677 described later and transmits the information to the distributed file management apparatus 610.

  When the electronic file related to the write request is a newly stored electronic file that is not held by any server, the copy destination receiving unit 634 stores a copy of the electronic file (hereinafter, “copy”). It is a part that receives information on “destination server”.

  Thereby, since the electronic file related to the new storage is copied to the copy destination server, at least two or more servers hold the same electronic file. Therefore, 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 provided in the server, the electronic file is also held in another server, The user can obtain an electronic file related to the request from another server.

  Similarly to the file storage control unit 77 according to the first embodiment, the file storage control unit 677 is a part that controls the file storage unit 25, and determines whether the file storage unit 25 stores a specific electronic file. Search, read the electronic file stored in the file storage unit 25, update the electronic file stored in the file storage unit 25, store a new electronic file in the file storage unit 25, Information indicating the state of the file storage unit 25 such as the free capacity of the storage unit 25 is acquired.

  The above is the functional configuration of the server A 620 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 illustrating an example of a functional configuration included in the distributed file management apparatus 610 according to the third embodiment. The difference between the distributed file management device 610 according to the third embodiment and the distributed file management device 10 according to the first embodiment is that the distributed file management device 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, an 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.

  The distributed file management apparatus 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, an update completion notification unit 114, a lock Request receiving unit 116, lock information holding unit 118, holding server storage unit 700, holding server determination unit 704, hash value request unit 728, hash value reception unit 730, update permission request reception unit 732, hash A value initialization unit 734, an update permission transmission unit 736, a storage unit information request unit 738, a storage unit information reception unit 740, a copy destination determination unit 742, and a copy destination transmission unit 744 are provided.

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

  Since the management server information 700a according to the third embodiment is the same as the management server information 100a according to the first embodiment described with reference to FIG. 6, the description thereof is omitted here.

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

  FIG. 38 is a diagram illustrating an example of the file holding information 700b stored in the holding server storage unit 700. As shown in the figure, the file holding information 700b according to the present embodiment includes a “file path”, a “server name”, and a “hash value”.

  The “file path” and “server name” of the file holding information 700b according to the present embodiment are the “file path” and “file path” of the file holding information 100b according to the first embodiment described with reference to FIG. Since the same information is stored for each of the “server name”, a detailed description thereof is omitted here.

  The “hash value” stores the hash value of the regular electronic file calculated by the server. 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 hash function is predetermined in common in all servers, and the input value is all or a part of the electronic file, and in some cases in any part. It may be predetermined in common for all servers.

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

  Also, as shown in the figure, all electronic files are held in two or more servers. Therefore, for example, even when a failure occurs in “server A”, file a can be acquired from “server B” and file b can be acquired from “server C”. Therefore, fault tolerance in the entire system is improved by holding different electronic files in different servers.

  From here, it returns to description of FIG.

  The holding server determination unit 704 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 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's acquisition request, the holding server determination unit 704 determines that the server holding the electronic file having regular contents is the holding server.

  The hash value request unit 728 is a part that requests 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, and the hash value of the electronic file related to the acquisition request held by the server. .

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

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

  When the update permission request receiving unit 732 receives an update permission request, the hash value initializing unit 734 is a part that initializes the “hash value” of the file holding information 700b corresponding to the electronic file related to the update. In the initialization of the hash value according to the present embodiment, the “hash value” is updated with “−1”.

  In response to the fact that the hash value initialization unit 734 has initialized the “hash value”, the update permission transmission unit 736 sends the update permission request received by the update permission request reception unit 732 to the terminal 60 (65) that is the transmission source of the update permission request. This is a part that transmits information whose content is to permit the update.

  The storage unit information request unit 738 is information indicating the state of the 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. (Hereinafter referred to as “storage unit information”).

  The “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.

  The storage unit information receiving unit 740 is a part that receives storage unit information transmitted from each server in response to a request from the storage unit information requesting 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. The copy destination determination unit 742 according to the present embodiment sets the server having the largest percentage of free capacity included in the storage unit information as the copy destination server.

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

  Since the distributed file management device 610 and each of the servers 620, 630, and 640 have the functions as described above, the user accesses any server from the terminals 60 and 65 that the user uses as in the first embodiment. Regardless, as long as any of the servers 620, 630, and 640 holds the electronic file, the electronic file can be acquired.

  Further, as in the second embodiment, since the same electronic file held by a plurality of servers is synchronized, the user is conscious of which server holds the electronic file having the latest contents. In addition, an electronic file having the latest contents can be obtained by accessing an arbitrary server.

  Furthermore, since at least two servers hold the same electronic file, even if a failure occurs in one holding server or the storage unit of the holding server, the electronic file is acquired from another holding server. It is possible to improve the fault tolerance of the entire system.

  Further, 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 authentic by referring to the hash value, and it is possible to prevent unauthorized rewriting of the electronic file.

  FIG. 39 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 an acquisition request from the terminal.

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

  First, the user request receiving unit 71 of the access source server 20 (30, 40) receives the acquisition request transmitted from the terminal 60 (65) used by the user via the communication line 50 (S401). Here, the “acquisition request” is an electronic file related to the user's designation, and is information that includes a request for a terminal that the user uses the electronic file having the latest content to acquire.

  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).

  When it is determined that the electronic file is not held (No in S402), the holding server inquiry unit 79 inquires the distributed file management device 10 about the holding server, and the inquiry reception unit 102 makes an inquiry about the holding server. Accept (S403).

  Subsequently, the holding server determination unit 704 refers to the file holding information 100b in the holding server storage unit 100 to determine whether there is a holding server other than the access source server (S404).

  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). .

  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), and ends the processing. To do.

  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 then sends a request for the hash value of the electronic file related to the acquisition request to the holding server, and holds it. The hash value request receiving unit 624 of the server receives a hash value request (S407).

  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).

  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 (S409).

  Subsequently, the holding server determination unit 704 holds the holding server depending on whether or not the hash value included in the file holding information 700b of the holding server storage unit 700 matches the hash value received by the hash value receiving unit 730. It is determined whether or not the electronic file to be processed is legitimate (S410).

  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 determination unit 704 determines that the hash value is not valid (No in S410).

  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).

  Subsequently, when the non-holding notification is acquired via the file storage control unit 677, the user request response unit 95 transmits the non-holding notification to the terminal 60 (65) that has transmitted the acquisition request (S412), and ends the processing. To do.

  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 determination unit 704 determines that the file is valid (Yes in S410).

  In this case, subsequently, the file transmission request unit 108 transmits a file transmission request to the holding server, and the file transmission request reception 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.

  Subsequently, the file storage control unit 677 receives the file transmission request received by the file transmission request unit 108, and reads the electronic file related to the user acquisition request from the file storage unit (S414).

  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 receiving 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 receives the completion of the storage process (S416) of the file storage control unit 677 and transmits an update notification, and the update notification reception unit 110 receives the update notification (S418). .

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

  If it is determined that the electronic file is held (Yes in S402), the hash value calculation unit 626 calculates the hash value of the electronic file (S420).

  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).

  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 process in S410 (S422).

  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 reception unit 81 receives the holding notification. (S423).

  Subsequently, in response to the holding notification received by the holding response receiving unit 81, the file storage control unit 677 reads the electronic file related to the user acquisition request from the file storage unit 25 (S424).

  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), and the access source server ends the process. To do.

  Further, when the holding server determination unit 704 determines that it is not normal (No in S410), the holding server determination unit 704 subsequently stores the file holding information 100b in the holding server storage unit 100 in the same manner as the determination process in S404. By referring, it is determined whether there is a holding server other than the access source server (S426).

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

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

  If it is determined that there is a holding server other than the access source server (Yes in S426), the hash value transmission unit 628 continues with the hash value request unit 728 and the hash value request reception unit 624 of the holding server in the same manner as S407. The request for the hash value of the electronic file related to the acquisition request is transmitted / received (S429).

  The processing after S430 shown in the figure is the same as the processing after S408. Specifically, the processing from S430 to S432 is the same as the processing from S408 to S410, the processing at S427 and S428 is the same as the processing at S411 and S412, respectively, and the processing from S433 to S437 is from S413. The processing is the same as the processing up 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 storage request from the terminal.

  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 this figure is a server 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 any one of the server A 620, the server B 630, and the server C 640.

  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 including a request for causing the access source server to hold a new electronic file.

  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”, a “write request”, or a “storage request”. . Since this figure is a time chart of processing related to a storage request, this determination is omitted.

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

  Subsequently, the lock request transmission unit 89 first receives the determination of the request type determination unit 73 that the acquired request is a write request, and transmits the lock request to the distributed file management apparatus 10, and the lock request reception unit 116. Receives the lock request (S503).

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

  Further, the file storage control unit 677 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 storage request, and the acquired electronic file Is newly stored in its own file storage unit 25, 35, 45 (S505).

  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 the update notification and the hash value 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 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).

  Subsequently, the holding information update unit 112 releases the lock by deleting the information held by the lock information holding unit 118 (S509).

  Subsequently, the update completion notification unit 114 receives a notification of completion from the file storage control unit 677, notifies the access source server of completion of the update process, and the completion notification receiving unit 93 of the access source server receives the notification of completion. (S510).

  Subsequently, the user request response unit 95 of the access source server receives the fact that the completion notification receiving unit 93 has received the notification of completion, and the terminal used by the user that processing related to the user's write request has been completed. 60 (65) (S511). Thereby, the process performed between the terminal 60 (65) and the access source server ends.

  In the distributed file management apparatus 610, following the completion notification transmitted by the update completion notification unit 114 in S510, the copy destination determination unit 742 determines a copy destination server based on the free capacity of the file storage unit of each server (S512). . Details of this processing will be described later.

  Subsequently, the copy destination transmission unit 744 transmits a request for transmitting the electronic file newly stored by the access source server to the copy destination server, and the copy destination reception unit 634 receives the transmission request for this file. (S513).

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

  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).

  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 shows details of the copy destination determination processing (S512) 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. is there.

  First, the storage unit information request unit 738 transmits a storage unit information transmission request to each server, that is, the server A 620, the server B 630, and the server C 640 in this embodiment, and receives the storage unit information request of each server. Unit 630 receives the transmission request (corresponding to S551, S552, and S553, respectively).

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

  Similarly, the file storage control units 677 of the server B 630 and the server C 640 also acquire storage unit information (corresponding to S555 and S556, respectively).

  Subsequently, the storage unit information receiving unit 740 includes, from each server, that is, the server A 620, the server B 630, and the server C 640 in this embodiment, the file storage unit 25 of each server, the file storage unit 35, and the file storage. The storage unit information related to the unit 45 is received (corresponding to S557, S558, and S559, respectively).

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

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

  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).

  The above is the 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 from the terminal. Subsequently, assuming that the initial state of the file holding information 700b is the content shown in FIG. 38, the distributed file management according to Embodiment 3 of the present invention when the user transmits a file f storage request from the terminal to the server A 620. The processing executed in each device constituting the system will be described more specifically.

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

  Subsequently, the request type determination unit 73 acquires the request received by the user request reception unit 71 and determines that the request is a “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).

  Subsequently, the lock request transmission unit 89 first receives the determination of the request type determination unit 73 that the acquired request is a write request, and transmits the lock request to the distributed file management apparatus 10, and the lock request reception 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. Thereby, the write request for the file f is locked (S504).

  The file storage control unit 677 receives the determination of 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. Newly stored in its own file storage unit 25 (S505).

  Subsequently, the hash value calculation unit 626 calculates a hash value of the newly stored electronic file (S506). The hash value of the file f calculated here is “1814680”.

  Subsequently, the update notification unit 91 transmits the update notification and the hash value 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 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).

  Here, FIG. 42 shows the file holding information of the holding 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 700c.

  The difference between the file holding information 700c shown in the figure and the initial state of the file holding information 700b shown in FIG. 38 is that, in the file holding information 700c, the “file path” is “/ data / f” and the “hash value” is “ 1814680 ”and the information that“ server name ”is“ server A ”is added.

  After updating the file holding information in this way (S508), the holding information update unit 112 releases the lock (S509), and the update completion notification unit 114 and the completion notification reception unit 93 of the access source server transmit and receive a completion notification. (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).

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

  In the copy destination determination process (S512), transmission / reception of storage unit information transmission requests (from S551 to S553), storage unit information acquisition processing (from S554 to S556), and storage unit information transmission / reception processing (from S557 to S559) ) And are executed.

  Subsequently, the copy destination determination unit 742 waits until the storage unit information is received from all servers (No in S560). When the storage unit information is received from all servers (Yes in S560), the acquired storage unit information is received. The copy destination server is determined based on the above (S561).

  Here, a specific example in which the copy destination server is determined will be described taking the case where the storage unit information acquired by the copy destination determination unit 742 has the contents shown in FIG. 43 as an example.

  FIG. 43 is a diagram illustrating a specific example for explaining the storage unit information. In the present embodiment, each ratio described in the “vacancy ratio” is storage unit information of each file storage unit 25, 35, 45 included in each server. The “free ratio” is a ratio of the free capacity of each file storage unit to the total capacity. The acquisition of the free capacity and the total capacity of the file storage unit and the calculation of the free ratio are performed by the file storage control unit 677 (from S554 to S556).

  In this figure, for example, the “total storage capacity” of the file storage section 25 included in “server A” is “184256 MB” (Mega Byte), and the “storage section free capacity” is “120789 MB”. “Capacity” indicates an example of “66%” that is a value obtained by dividing 120789 by 184256.

  In this figure, the “free ratio” corresponding to “server B” is “73%”, which is the largest among the servers.

  Therefore, when the empty ratio is the content shown in the figure, the copy destination determination unit 742 determines “Server B” as the copy destination server (S561).

  When the copy destination server is determined in this way, the copy destination transmission unit 744 and the copy destination reception unit 634 of the server A 620 that is the access source server transmit and receive a request for transmitting the file f to the server B 630 (S513).

  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 A 620 and the file reception unit 87 of the server B 630 transmit and receive the file f (S515). .

  Subsequently, the file storage control unit 677 of the server B 630 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 B 630 transmit and receive update notifications (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.

  Here, FIG. 44 is a diagram illustrating 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. It is.

  In the file holding information 700d shown in the figure, in addition to the “server name” associated with the information whose “file path” is “/ data / f”, in addition to “server A” of the file holding information 700c shown in FIG. "Server B" is stored.

  The above is the processing executed in each device constituting the distributed file management system according to Embodiment 3 of the present invention when the user transmits an update request from the terminal. Next, 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 from the terminal will be described.

  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 an update request from the terminal.

  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).

  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.

  In this figure, when the file holding information 700b before the hash value is initialized has the contents shown in FIG. 38, the distributed file management apparatus 610 that has received the update permission request for the file b updates the file holding information 700b. An example is shown.

  In the present embodiment, the hash value initialization unit 734 initializes the hash value by storing “−1” in the “hash value” related to the update permission request.

  In this figure, since it is an update permission request for the file b, “−1” is stored in the “hash value” of the file b whose “file path” is “/ data / b”.

  From here, it returns to description of FIG.

  Subsequently, the update permission transmitting unit 736 transmits the update permission of the electronic file requested by the update permission request receiving unit 732 to the terminal 60 (65) used by the user (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 determines whether the request is an “acquisition request”, an “update request”, or a “storage request”. Since this diagram is a time chart of processing related to the update request, this determination is omitted.

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

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

  Subsequently, the file storage control unit 677 receives the determination of the request type determination unit 73 that the acquired request is an update request, acquires the electronic file held by the request information holding unit 75, and acquires the acquired electronic file. The electronic file stored in its own file storage unit 25, 35, 45 is updated with the file (S608).

  Subsequently, the file storage control unit 677 determines whether or not the update is completed (S609).

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

  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 calculates the hash value of the electronic file ( S610).

  Subsequently, similarly to the processing in S507 and S508 shown in FIG. 40, the update notification unit 91 of the access source server and the update notification reception unit 110 of the distributed file management device 610 transmit and receive the update notification and the hash value (S611). Subsequently, the holding information update unit 112 updates the file holding information 700b in the holding server storage unit 700 in accordance with the update notification and the hash value acquired from the update notification receiving unit 110 (S612).

  Here, FIG. 47 is a diagram illustrating an example of the file holding information after executing the update process of the electronic file related to the request when the user transmits an update request from the terminal in the third embodiment. This figure is an example when the file b is updated, and shows an example in which the “hash value” of the new file b is “3417510”.

  From here, it returns to description of FIG.

  Subsequently, from the unlocking process (S613) by the holding information update unit 112 to the transmission process (S615) of the completion notification to the terminal 60 (65) used by the user by the user request response unit 95 of the access source server, FIG. Since the processing from S509 to S511 shown in FIG. 40 is the same as that of FIG.

  Subsequently, the holding server determination unit 704 extracts a 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).

  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 own file storage unit 25 with 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 described with reference to 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 above. Therefore, explanation here is omitted.

  The distributed file management device and the distributed file management system according to Embodiment 3 of the present invention have been described above, but the present invention is not limited to this embodiment.

  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.

  For example, in the present embodiment, as shown in FIG. 46, the hash value is initialized by storing “−1” in the “hash value” of the file holding information 700e. The value stored in the hash value is not limited to “−1” and may be any value that cannot be taken as the hash value. Also, a NULL value may be stored.

(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 apparatus does not function due to a failure or the like, there is a problem that the user's request regarding the electronic file cannot be processed, and therefore the distributed file management system also does not function.

  Therefore, in the fourth embodiment, a distributed file management system having excellent fault tolerance is provided.

  A fourth embodiment according to the present invention will be described with reference to FIGS. 48 to 62. FIG.

  FIG. 48 is a diagram showing an outline of the configuration of the distributed file management system according to Embodiment 4 of the present invention. Similar to the first to third embodiments, the distributed file management system according to the fourth embodiment is a system that responds to user requests regarding electronic files, regardless of which access server is the one.

  The distributed file management system according to the present embodiment includes a server A 820, a server B 830, and a server C 840, and a terminal a 60 and a terminal b 65 connected via a communication line 50. Regarding the elements constituting the distributed file management system according to the present embodiment, elements having the same functions as the elements constituting the distributed file management system according to the first embodiment are denoted by the same reference numerals. A description of these elements is omitted.

  Each server 820, 830, 840 according to the present embodiment has a function of a distributed file management device that manages electronic files held in each server, holds electronic files, accepts user requests, When a user request is received, it also has a file server function that responds to the request in cooperation with the distributed file management apparatus or another server.

  Any one of the servers functions as a distributed file management device. In the present embodiment, the order in which servers are distributed file management apparatuses is determined in advance, and the server having the highest rank among the 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 or the like, another server can become a distributed file management device, and fault tolerance can be improved. Become.

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

  Each server includes a file storage unit for storing and holding electronic files, the server A 820 according to the present embodiment includes a file storage unit 25, the server B 830 includes a file storage unit 35, and the server C 840 stores a file. The unit 45 is provided.

  Here, also in the distributed file management system according to the fourth embodiment, the folder structure of the electronic file stored in the file storage unit provided in each server is common, and specifically, the folder structure shown in FIG. It is the same. Therefore, the description here regarding the folder structure is omitted.

  A specific example of the electronic file stored in each file storage unit 25, 35, 45 according to the fourth embodiment will be described with reference to the drawings.

  49A to 49C are diagrams illustrating specific examples of electronic files stored in a file storage unit included in each server according to the fourth embodiment.

  FIG. 49A is a diagram illustrating an example of the electronic file information 25d stored in the file storage unit 25 included in the server A 820 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 illustrating an example of the electronic file information 35d stored in the file storage unit 35 included in the server B 830 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 d”, and “file e”.

  FIG. 49C is a diagram illustrating an example of the electronic file information 45d stored in the file storage unit 45 included in the server C 840 according to Embodiment 4. This figure shows an example in which the file storage unit 45 according to the present embodiment stores “file d”.

  Subsequently, an example of a functional configuration included in each server will be described with reference to the drawings by taking the server A 820 as an example.

  FIG. 50 is a block diagram illustrating an example of an outline of a functional configuration included in the server A 820 according to the fourth embodiment. The 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 a plurality of 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 parts included in the file server unit 900, the management device unit 910, and the management device determination unit 920 will be described later.

  In addition, the file server unit 900, the management device unit 910, and the management device determination unit 920 transmit / receive information to / 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 according to the received requests.

  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 regarding electronic files held by the server A 820, the server B 830, or the server C 840. If the server A 820 is a management device server, the management device unit 910 sends an inquiry from another server. Accept.

  The management device determination unit 920 is a part that determines a management device server based on information transmitted to and received from a management device determination unit included in another server.

  The above is the outline of the functional configuration provided in the server A 820 according to the present embodiment. Next, details of the functions of each part will be described with reference to the drawings.

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

  The file server unit 900 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 response reception unit 81, and a file transmission request. Receiving unit 83, file transmitting unit 85, file receiving unit 87, lock request transmitting unit 89, completion notification receiving unit 93, user request response unit 95, holding server inquiry unit 1079, update notification unit 1091 As described above, these transmit / receive information to / from the management device unit 910 and the management device determination unit 920 via an internal bus (not shown).

  About each part which the file server part 900 which concerns on this Embodiment has, the part which has the same function as each part with which the server which concerns on Embodiment 1 shown in FIG. 4 is provided is attached | subjected the same referential mark. Here, detailed description of each of these parts is omitted.

  Similar to the holding server inquiry unit 79 according to the first embodiment, the holding server inquiry unit 1079 determines which server holds the electronic file according to the user's request via the communication line 50. This is a part for inquiring 910. Unlike the holding server inquiry unit 79 according to the first embodiment, the holding server inquiry unit 1079 inquires of the management server 910 about the holding server according to 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. Thereby, all the servers can hold the latest information on the holding server.

  FIG. 52 is a diagram illustrating an example of the functional configuration of the management device unit 910 and the management device determination unit 920 of the server A 820 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, a retention information update unit 112, The update completion notifying unit 114, the lock request receiving unit 116, the lock information holding unit 118, and the holding server storage unit 1000 include the file server unit 900 and the management device determination unit 920 as described above. Information is transmitted / received to / from each other via an internal bus (not shown).

  About each part which the management apparatus part 910 which concerns on this Embodiment has about the part which has the function similar to each part with which the distributed file management apparatus 10 which concerns on Embodiment 1 shown in FIG. Here, detailed description of each of these parts is omitted.

  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, an 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.

  FIG. 53 is a diagram illustrating an example of the management server information 1000a stored in the holding server storage unit 1000 according to the fourth embodiment. 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.

  The management server information 1000a shown in the figure includes “server name”, “IP address”, and “order”. Since “server name” and “IP address” are the same as “server name” and “IP address” according to the first embodiment, respectively, description thereof will be omitted.

  The “order” includes the order in which each server functions as a distributed file management apparatus.

  In this figure, for example, management server information whose “IP address” is “192.168..xxx.1” and whose “rank” is “3” is “server name” is “server A”. Including.

  Further, regarding “order”, “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 when “server B” stops operating, then “server C” becomes the management device server, and “server C” also operates. When stopped, it indicates that “server A” becomes a management apparatus server. Such an order is predetermined by an administrator of the distributed file management system according to the present embodiment.

  Next, FIG. 54 is a diagram illustrating an example of the file holding information 1000b stored in the holding server storage unit 1000 according to the fourth embodiment. The “file path” and “server name” of the file holding information 1000b according to the present embodiment are the “file path” and “file path” of the file holding information 100b according to the first embodiment described with reference to FIG. Since the same information is stored for each of the “server name”, a detailed description thereof is omitted here.

  This figure is an example including file holding information indicating that “server A” and “server B” hold an electronic file whose “file path” is “/ data / a”, for example.

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

  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, a holding server information acquisition unit 1210, A server response unit 1212 and a server response reception unit 1214 are included.

  The management device holding unit 1200 is a part that holds information for identifying the current management device server (hereinafter referred to as “management device information”).

  The management device notifying 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. This is a part for notifying that a server provided with each server at a predetermined time interval is the current management device server.

  Here, if the management device notification unit 1202 stores information indicating the server including itself in the management device storage unit 1200, the management device notification unit 1202 determines that the server including the management device notification unit 1202 is a management device server. If the information indicating the server including the server is not stored, it is determined that the server including the server is not a management apparatus server.

  The management device notification receiving unit 1204 is a part that receives a notification from the management device notification unit 1202 of the management device server.

  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.

  Specifically, first, the change determination unit 1206 is configured such that the transmission source of the response received by the management device notification reception unit 1204 is a server having a higher rank than the server indicated by the information held by the management device holding unit 1200. Therefore, 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, a response from a server having a higher rank than the server indicated by the information held by the management device holding unit 1200 is accepted when the server that has been down is restored. Therefore, each server can detect the recovery of the server that was down.

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

  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 uses the management server information 1000a in the holding server storage unit 1000 as the next management device server. Information that is determined by reference 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 as the next management device server among the servers in operation.

  The holding server information acquisition unit 1210 stores the file in the holding server storage unit 1000 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. The holding information 1000b is acquired.

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

  First, when the change determination unit 1206 determines that no change is necessary, the server response unit 1212 responds to the transmission source of the notification received by the management device notification reception unit 1204.

  In addition, when the change determination unit 1206 determines that the management apparatus server needs to be changed due to the server recovery, the server response unit 1212 acquires the server determined by the management apparatus determination unit 1208 by the holding server information acquisition unit 1210. A response including the file holding information 1000b is transmitted.

  The server response reception unit 1214 is a part that receives a response transmitted from the server response unit 1212 of another server.

  Here, when the file holding information 1000b is included in the received response, the server response receiving unit 1214 updates the file holding information 1000b of its own holding server storage unit 1000 with the file holding information 1000b.

  The file holding information 1000b is included in the response when a failure has occurred in the server that has received the response. Since the file holding information 1000b held by the server cannot be updated while a failure has occurred, the contents may be old. 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.

  The above is the functional configuration of the server A 820 according to the present embodiment. The functional configuration of the server A 820 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 B 830 and the file storage unit 45 in the server C 840. Therefore, description of the functional configuration of the server B 830 and the server C 840 is omitted.

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

  FIG. 55 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 an acquisition request from the terminal.

  In the present embodiment, 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 “Server B” is set in the management device holding unit 1200 of each server. It is assumed that the information shown is held.

  Also, the “terminal” shown in the figure is a terminal used by the user, and is either the terminal a60 or the terminal b65 in the present embodiment. Furthermore, this figure shows an example in which the server A820 is an access source server.

  Therefore, in this figure and the description of this figure, the process of “server A” 820 is a process executed by “access source server”, and the process of “server B” 830 is a process executed by “management device server”. .

  First, the management device notification unit 1202 of the server B 830 transmits “notification 1” to another server, and the management device notification reception unit 1204 of the server A 820 and the server C 840 receives “notification 1” (S701 and S702).

  Here, “notification 1” means that the management apparatus notification unit 1202 of the server B 830 that is the management apparatus server notifies other servers that it is operating continuously or intermittently at regular intervals. Information to be sent to.

  Subsequently, since the server indicated by the information held in the management device holding unit 1200 and the server that the management device notification receiving unit 1204 receives “notification 1” are both “server B”, the server A 820 and The change determination unit 1206 of the server C 840 determines that no change is necessary, and the server response unit 1212 of the server A 820 and the server C 840 that has received this determination transmits “response 1” to the server B 830. Then, the server response reception unit 1214 of the server B 830 receives “response 1” (S703 and S704).

  The processes from S701 to S704 so far are processes that are continued for the management apparatus determination unit 920 of each server to determine the management apparatus server.

  Subsequently, the user request receiving unit 71 of the server A820 as the access source server receives the acquisition request transmitted from the terminal 60 (65) used by the user via the communication line 50 (S705). Here, the “acquisition request” is a request for the terminal used by the user to acquire the electronic file specified by the user.

  Subsequently, the request type determination unit 73 of the server A 820 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 77 of the server A 820 determines whether or not its own file storage unit 25 stores the electronic file related to the acquisition request (S706).

  When it is determined that the 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 relate to the acquisition request from the file storage unit 25. The electronic file is read (S707).

  Subsequently, the user request response unit 95 of the server A820 acquires the electronic file related to the acquisition request from its own file storage control unit 77, and transmits the electronic file to the terminal 60 (65) used by the user (S708). .

  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 the electronic file related to the acquisition request to the server B830. The inquiry reception unit 102 of the server B 830 receives the inquiry of the holding server (S709).

  Subsequently, the retention server determination unit 104 of the server B 830 refers to the file retention information 1000b of the retention server storage unit 1000 to determine whether there is an electronic file retention server related to the acquisition request (S710).

  When it is determined that there is no holding server (No in S710), the holding response transmission unit 106 of the server B 830 transmits a non-holding notification to the server A 820 (S711).

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

  If it is determined that there is a holding server (Yes in S710), the holding server determination unit 104 of the server B 830 determines whether the server B 830 itself is a holding server (S713).

  If it is determined that the server itself is a holding server (Yes in S713), then the file storage control unit 77 of the server B 830 relates to an acquisition request from the file storage unit 35 based on the request of its own management device unit 910. The electronic file is read (S714).

  Subsequently, the file transmission unit 85 of the server B 830 acquires the electronic file related to the acquisition request from its own file storage control unit 77 and transmits it to the server A 820. Then, the file reception unit 87 of the server A 820 receives the electronic file transmitted by the file transmission unit 85 of the server B (S715).

  Subsequently, the user request response unit 95 of the server A 820 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).

  Subsequently, the file storage control unit 77 of the server A 820 stores the electronic file acquired from its own file reception unit 87 in its own file storage unit 25 (S717).

  Subsequently, the update notification unit 1091 of the server A 820 transmits an update notification with the content that the access source server has become the electronic file holding server related to the acquisition request to the server B 830 and the server C 840, and the server B 830 and the server The update notification receiving unit 110 of C840 receives the update notification (S718 and S719).

  Subsequently, the update notification reception unit 110 of the server A 820 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 A 820 acquires from the update notification reception unit 110. In accordance with the update notification, the file holding information 1000b in its own holding server storage unit 1000 is updated (S720).

  Further, the holding information update unit 112 of the server B 830 and the server C 840 acquires the update notification from each update notification receiving unit 110 and updates the file holding information 1000b of each holding server storage unit 1000 according to the acquired update notification ( S721 and S722).

  Subsequently, “notification 1” is transmitted / received between the server B 830 and the server A 820, and between the server B 830 and the server C 840, and “response 1” is transmitted / received similarly to the processing from S701 to S704. (S723 to S726). Since S723 is the same processing as S701, S724 is S702, S725 is S703, and S726 is S704, the detailed description is omitted here. Furthermore, 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.

  If it is determined that the server itself is not a holding server (No in S713), the file transmission request unit 108 of the server B 830 subsequently sends a request to transmit the electronic file related to the acquisition request to the server A 820 that is the access source server. The data is transmitted to the holding server (S727). Here, it is assumed that the server C840 is a holding server.

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

  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).

  Subsequently, the user request response unit 95 of the server A 820 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).

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

  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 write request from the terminal.

  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 1200 of each server has It is assumed that information indicating “server B” is held.

  Also, the “terminal” shown in the figure is a terminal used by the user, and is either the terminal a60 or the terminal b65 in the present embodiment. Furthermore, this figure shows an example in which the server A820 is an access source server.

  Therefore, in this figure and the description of this figure, the process of “server A” 820 is a process executed by “access source server”, and the process of “server B” 830 is a process executed by “management device server”. .

  First, the processing from S701 to S704 shown in this drawing is processing that is continued for each server to determine the server that functions as the distributed file management device, and is the processing with the same reference numerals in FIG. Each is the same. Therefore, explanation here is omitted.

  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 cause the access source server to hold a new electronic file.

  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).

  Subsequently, first, the lock request transmission unit 89 of the server A 820 receives the determination of the request type determination unit 73 that the acquired request is a write request, and the server B 830 functioning as a distributed file management device. The lock request receiving unit 116 of the server B 830 receives the lock request (S803).

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

  Further, the file storage control unit 77 of the server A 820 receives the determination of the request type determination unit 73 that the acquired request is a write request, acquires the electronic file held by the request information holding unit 75, and acquires the electronic file. The electronic file is written in its own file storage unit 25 (S805).

  Subsequently, the file storage control unit 77 of the server A 820 determines whether or not the writing is completed (S806).

  When it is determined that the writing has not been completed (No in S806), the update notification unit 1091 of the server A 820 waits.

  If it is determined that the writing has been completed (Yes in S806), the update notification unit 1091 of the server A 820 receives a notification of completion from its own file storage control unit 77, and the access source server performs electronic processing related to the write request. An update notification having the content of becoming a file holding server is transmitted to the server B 830, and the update notification receiving unit 110 of the server B 830 receives the update notification (S807).

  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 transmits an inquiry of the holding server of the electronic file related to the write request to the server B830. The inquiry receiving unit 102 in B830 receives an inquiry from the holding server (S808).

  Subsequently, the update notification unit 1091 of the server A 820 receives a notification of completion from its own file storage control unit 77 and updates that the access source server has become an electronic file holding server related to the write request. The notification is transmitted to the server C840, and the update notification receiving unit 110 of the server C840 receives the update notification (S809).

  Subsequently, the update notification reception unit 110 of the server A 820 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 A 820 acquires from the update notification reception unit 110. According to the update notification, the file holding information 1000b in its own holding server storage unit 1000 is updated (S810).

  Further, the holding information update unit 112 of the server B 830 and the server C 840 acquires the update notification from each update notification receiving unit 110 and updates the file holding information 1000b of each holding server storage unit 1000 according to the acquired update notification ( S811 and S812).

  Subsequently, the holding information update unit 112 releases the lock by deleting the information held by the lock information holding unit 118 (S813).

  Subsequently, the update completion notification unit 114 receives the completion notification from the file storage control unit 77 and notifies the server A 820 of the completion of the update process, and the completion notification reception unit 93 of the server A 820 receives the completion notification ( S814).

  Subsequently, the user request response unit 95 of the server A 820 receives the completion notification received by the completion notification receiving unit 93, and the terminal 60 used by the user that the processing related to the user's write request has been completed. To (65) (S815).

  Subsequently, the holding server determination unit 104 of the server B 830 determines whether there is a holding server other than the server A 820 that is the access source server by referring to the file holding information 1000b of its own holding server storage unit 1000 (S816). .

  If it is determined that there is a holding server (Yes in S816), the file transmission requesting unit 108 of the server B 830 acquires information specifying the holding server from its own holding server determining unit 104, so that the electronic A file transmission request including the content of transmitting the file to the holding server is transmitted to the server A 820, and the file transmission request receiving unit 83 of the server A 820 receives the file transmission request (S817). This figure shows an example in which the holding server when “Yes” is determined in S816 is “server C” 840. Therefore, the following processing of “server C” 840 is processing executed by the “holding server”.

  Subsequently, the file storage control unit 77 of the server A 820 obtains the file transmission request received by the file transmission request receiving unit 83 from the file transmission request receiving unit 83, and the electronic file related to the write request from its own file storage unit 25. Is read (S818).

  Subsequently, the file transmission unit 85 of the server A 820 acquires the electronic file related to the write request and the file transmission request from the file storage control unit 77, transmits the electronic file related to the write request to the server C 840, and the server C 840 The file receiving unit 87 receives the electronic file (S819).

  Subsequently, the file storage control unit 77 of the server C 840 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).

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

  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 B 830 as the management apparatus server is stopped and then spread.

  In this figure, it is assumed that the management server information 1000a in the holding server storage unit 1000 of the server A820, the server B830, and the server C840 has the contents shown in FIG. Therefore, when the server B 830 stops, the next management apparatus server is the server C 840.

  First, the server B 830 serving as the management apparatus server stops (S901). Therefore, the server B 830 cannot transmit “notification 1” to the server A 820 and the server C 840. The description in this figure in which “Notification 1” is marked with a cross indicates this.

  Next, the management device determination unit 920 of the server A 820 cannot receive the notification from the server B 830 that is the management device server within a certain time, and therefore the management device server is the server C 840 that is the next ranked server. Is the management apparatus server, and the management apparatus information held by itself is changed from the server B 830 to the server C 840 (S902).

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

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

  Subsequently, the management device notification unit 1202 of the server C 840 that has become the management device server transmits “notification 2” to another server, and the management device notification reception unit 1204 of the server A 820 receives “notification 2” (S904). Server B 830 cannot accept “Notification 2” because it is stopped (S905). The “X” attached to the “Notification 2” arrow in FIG.

  Here, “notification 2” is information that is transmitted continuously or intermittently at regular intervals in order to notify other servers that it is operating, as in “notification 1”. This notification is transmitted by the management device notification unit 1202 of the server C840 that is the management device server.

  Subsequently, the management device determination unit 920 of the server A 820 determines that there is no need to change the management device in the first management device determination process (S906).

  Subsequently, the server response unit 1212 of A820 transmits “response 2” to the server C840, and the server response reception unit 1214 of the server C840 receives “response 2” (S907).

  Subsequently, the management device determination unit 920 of the server A 820 continues the first device determination process, and the management device determination units 920 of the server A 820 and the server C 840 repeat transmission / reception of “notification 2” and “response 2” (FIG. Not shown).

  Subsequently, it is assumed that the server B 830 is restored (S908).

  The management device notification unit 1202 of the restored server B 830 transmits “notification 1” to the other servers, and the management device notification reception unit 1204 of the server A 820 and the server C 840 receives “notification 1”, respectively (S909 and S910).

  Subsequently, because the management device determination unit 920 of the server A 820 has received a notification from the server B 830 that is higher in rank than the server C 840 indicated by the information stored as the current management device server in the first management device determination process. The server B 830 is determined as the management device server, and the management device information held by itself is changed from the server C 840 to the server B 830 (S 911).

  Subsequently, the server response unit 1212 of the server A 820 transmits “response 1”, and the server response reception unit 1214 of the server B 830 receives “response 1” from the server A 820 (S912).

  Further, since the management device determination unit 920 of the server C 840 has received a notification from the server B 830 having higher rank than itself, the management device determination unit 920 determines that the server B 830 is a management device server, and changes the management device information held by itself from the server C 840 to the server B 830 (S913).

  Here, a process that the management apparatus server determines intermittently in order to determine the current management apparatus server and retain correct management apparatus information is referred to as a “second management apparatus determination process”, and details thereof will be described later.

  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 the file holding information 1000b. “Response 1” including “” is received from the server C 840 (S914).

  Subsequently, the server response receiving unit 1214 of the server B 830 that has received “response 1” including the file holding information 1000b uses the file holding information 1000b to store the file holding information 1000b stored in its own holding server storage unit 1000. Update (S915). As a result, the file holding information 1000b held by the server B 830 becomes the latest content.

  Subsequently, the management device notification unit 1202 of the server B 830 transmits “notification 1” to another server, and the management device notification reception unit 1204 of the server A 820 and the server C 840 receives “notification 1” (S916 and S917). .

  Subsequently, the management device determination unit 920 of each of the server A 820 and the server C 840 determines that there is no need to change the management device in the first management device determination process (S918 and S919).

  Subsequently, the server response unit 1212 of the server A 820 and the server C 840 transmits “response 1” to the server B 830. Then, the server response reception unit 1214 of the server B 830 receives “response 1” (S920 and S921).

  Subsequently, the management device determination unit 920 of the server A 820 and the server C 840 continues the first device determination process, and the management device determination unit 920 of the server A 820 and the server C 840 transmits and receives “notification 1” and “response 1”. Repeat (not shown).

  FIG. 58 is a detailed flowchart of the first management apparatus process executed by the management apparatus determination unit 920 of the normal server.

  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.

  When it is determined that the predetermined time has not elapsed (No in S1001), that is, when the next notification is received within a predetermined time from the immediately preceding notification, the change determination unit 1206 continues the management device holding unit 1200. Is acquired and the management server information 1000a of the storage server storage unit 1000, and the rank of the server that is the transmission source of the next notification is indicated by the management device information held by the management device holding unit 1200. It is determined whether or not the server is higher than the server (S1002).

  When it is determined that the server that is the transmission source is not higher than the server indicated by the management apparatus information (No in S1002), the change determination unit 1206 determines that the management apparatus server does not need to be changed, and the time elapse determination process ( Return to S1001).

  If it is determined that a certain time has elapsed (Yes in S1001), or it is determined that the certain time has not elapsed (No in S1001), and the server that is the transmission source is from the server indicated by the management device information If it is determined that the host is higher (Yes in S1002), the change determination unit 1206 determines that the management device server needs to be changed, and the management device determination unit 1208 that has received this determination determines the management device server (S1003). ).

  Here, when it is determined that the management apparatus server needs to be changed because a certain time has elapsed (Yes in S1001), the management apparatus determination unit 1208 holds the determination and the management apparatus holding unit 1200 holds. Management server information is acquired from the change determination unit 1206, the “rank” of the management server information 1000a is acquired from the holding server storage unit 1000, and the server corresponding to the next rank of the server indicated by the management device information is Determine as a new management device server.

  In addition, since 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 1208 makes this determination. And the information for specifying the server that is the transmission source are obtained from the change determination unit 1206, and the server that is the transmission source is determined as a new management apparatus server.

  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). Thereby, the first management apparatus determination process by the management apparatus determination unit 920 of the normal server 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 (S1100).

  When it is determined that the transmission source is not higher than the server including the transmission source (No in S1100), the change determination unit 1206 waits.

  If it is determined that the transmission source is higher than the server including the transmission source (Yes in S1100), the management device determination unit 1208 determines this determination and information for specifying the transmission source server from the change determination unit 1206. The server which is acquired and is a 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).

  Subsequently, when the management server determination unit 1208 acquires information for specifying the server determined as a new management device server, the storage server information acquisition unit 1210 acquires the file storage information 1000b of its own storage server storage unit 1000. Then, the acquired file holding information 1000b and information for specifying the server are delivered to the server response unit 1212 (S1103).

  Accordingly, the first management device determination process by the management device determination unit 920 of the management device server ends.

  Next, 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 configuration of each device constituting the distributed file management system according to the fourth embodiment of the present invention when the server B 830 recovers after the server A 820 accepts the acquisition request for the file d while the server B 830 is stopped. It is a time chart which shows the specific example of the process performed.

  Also here, it is assumed that the management server information in the holding server storage unit 1000 of each server is 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, it is assumed that the initial contents of the electronic file information stored in the file storage units 25, 35, and 45 of each server are the contents shown in FIG.

  First, after the server B 830 serving as the management apparatus server stops (S901), the server A 820 transmits “response 2” to the server C 840 that has newly become the management apparatus server (S907). It is the same as the process which attached | subjected the same referential mark. Therefore, the description here regarding these is omitted. The management apparatus server at this time is changed to the server C840.

  Subsequently, the user request receiving unit 71 of the server A 820 receives an acquisition request for the file d from the terminal 60 (65) used by the user (S1201).

  Subsequently, the request type determination unit 73 of the server A 820 determines whether the request received by the user request reception unit 71 is an “acquisition request” (not shown), and then continues to the file storage control unit of the server A 820. 77 determines whether its own file storage unit 25 stores the electronic file related to the acquisition request (S1202).

  As shown in FIG. 49A, the file storage unit 25 of the server A 820 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 does not store the electronic file related to the acquisition request (No in S1202).

  In response to the determination of the file storage control unit 77, the holding server inquiry unit 1079 of the server A 820 transmits an inquiry of the holding server of the electronic file related to the acquisition request to the server C 840, and the inquiry reception unit 102 of the server B 830 The inquiry of the holding server is accepted (S1203).

  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 there is a holding server for the electronic file related to the acquisition request (S1204).

  As shown in FIG. 54, since the holding servers of the file d are “server B” and “server C”, the holding server determination unit 104 of the server C 840 determines that there is a holding server (Yes in S1204). Subsequently, it is determined whether or not the server C840 itself is a holding server (S1205).

  As described above, since “Server C” is a holding server, it is determined that the server C is a holding server (Yes in S1205), and then the file storage control unit 77 of the server C 840 has its own management device unit 910. In response to the request, the file d is read from the file storage unit 45 (S1206).

  Subsequently, the file transmission unit 85 of the server C 840 acquires the file d from its own file storage control unit 77 and transmits it to the server A 820. Then, the file receiving unit 87 of the server A 820 receives the file d (S1207).

  Subsequently, the user request response unit 95 of the server A 820 acquires the file d via the file storage control unit 77 and transmits it to the terminal 60 (65) used by the user (S1208).

  Subsequently, the file storage control unit 77 of the server A 820 stores the electronic file acquired from its own file reception unit 87 in its own file storage unit 25 (S1209).

  Subsequently, the update notification unit 1091 of the server A 820 transmits an update notification with the content that it has become the holding server of the file d to the server C 840, and the update notification reception unit 110 of the server C 840 sends the update notification. Accept (S1210).

  Subsequently, the update notification reception unit 110 of the server A 820 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 A 820 acquires from the update notification reception unit 110. According to the update notification, the file holding information 1000b in its own holding server storage unit 1000 is updated (S1211).

  Also, the holding information update unit 112 of the server C 840 acquires an update notification from each update notification receiving unit 110, and updates the file holding information 1000b of each holding server storage unit 1000 according to the acquired update notification (S1212).

  Thereafter, the server C 840 and the server A 820 continue the processing from transmission / reception of “notification 2” (S904) to transmission / reception of “response 2” (S907).

  The file holding information held by each server when the processing so far is finished will be described with reference to the drawings.

  FIG. 61 is a diagram illustrating an example of the holding server information 1000c in the holding 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. In the holding server information 1000c of the server A 820 and the server C 840, “server A” is newly added to the holding server of “file d”.

  FIG. 62 is a diagram illustrating an example of the holding server information 1000b in the holding server storage unit of the server B 830 after the processing related to the acquisition request for the file d executed while the server B 830 is stopped. Since the server B 830 is stopped, the holding server information 1000d is not updated, and “server A” is not newly added to the holding server of “file d”.

  Thus, the file holding information 1000d held by the stopped server may not hold correct information. Therefore, the process described below is executed.

  From here, it returns to description of FIG.

  It is assumed that the server B 830 has been restored (S908).

  Subsequently, the transmission and reception of “Notification 1” between the server B 830 and the server A 820 (S909) to the update of the retained server information by the server B (S915) are the same as the processes given the same reference numerals in FIG. Therefore, the description here regarding these is omitted.

  Here, the “response 1” transmitted by the server response unit 1212 of the server C 840 in S914 includes the latest file holding information 1000c shown in FIG. Therefore, the server B 830 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 B 830 It becomes possible to function correctly as a management apparatus server.

  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 will be described with reference to 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 above. Therefore, explanation here is omitted.

  The distributed file management system according to Embodiment 4 of the present invention has been described above, but the present invention is not limited to this embodiment.

(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 apparatus.

  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 of the file storage units of the server is changed, The file retention information of the server with the function is updated in order to maintain synchronization. When a distributed file management system is configured by a large number of servers, the processing for synchronizing the file holding information and the amount of communication information increase.

  Therefore, when the distributed file management system is configured by a large number of servers, the fault tolerance of the distributed file management system is improved by including a server having a function of the distributed file management device in a part of the server group. In addition, by including a server that does not have the function of a distributed file management device as part of its server group, it is possible to suppress an increase in the load related to the processing of each server and an increase in the amount of communication information It becomes.

  Such a modification according to the fourth embodiment 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 includes a server A 820, a server B 830, a server C 840, a server D 850, a terminal a 60, and a terminal b 65, and these devices are connected via a communication line 50. Yes. That is, the configuration of the distributed file management system shown in this figure is obtained by adding a server D850 to the configuration of the distributed file management system according to the fourth embodiment. Since devices other than the server D850 are the same as those in the fourth embodiment, a detailed description thereof is omitted here.

  The server D850 includes a file storage unit 855 that is a storage unit that stores an electronic file, as with other servers. The server D850 is different from other servers in that it does not have a function as a distributed file management device.

  Therefore, the management server information of the holding server storage unit 1000 included in the server A 820, the server B 830, and the server C 840, which is a server having a function as a distributed file management device, has a function as a distributed file management device in the server D 850. It has become possible to identify that it has not.

  FIG. 64 is a diagram showing an example of management server information 1000e in the holding server storage unit 1000 provided in the server functioning as the distributed file management apparatus according to the second modification of the present invention.

  The management server information 1000e shown in this figure is composed of “server name”, “IP address”, and “order”, like the management server information 1000a according to the fourth embodiment shown in FIG. In this modification, the information stored in these is the same as in the embodiment. The difference is that information is not included in the “rank” corresponding to the server so that a server that does not have the function as the distributed file management apparatus can be identified.

  For example, in this figure, the only information stored in association with “Server D” is “IP address”, and “Rank” is a NULL value. As described above, 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, when the management apparatus server is stopped, the server D850 is not a candidate for the next management apparatus server.

  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, a value not assigned to the “rank” associated with the server having the function of the distributed file management device, such as “−1” as the “rank”, may be used. In addition, a flag indicating whether the server has a function as a distributed file management apparatus may be further added.

  FIG. 65 is a block diagram showing a functional configuration of a server D850 that is a server that does not function as the distributed file management apparatus according to the second modification of the present invention.

  The server D850 includes a file server unit 900 and a management device determination unit 1300. Each part is connected by an internal bus (not shown).

  Similar to the file server unit 820 of the server A 820 shown in FIG. 51, the file server unit 900 of the server D 850 is a part that realizes a function as a file server, and has the same functional configuration as the file server unit 820 of the server A 820. Prepare. The functions provided in each part of the file server unit 900 shown in the 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, the detailed description regarding the function with which each site | part of the file server part 900 of the server D850 is provided here is abbreviate | omitted.

  Similar to the management device determination unit 920 of the server A 820 illustrated in FIG. 52, the management device determination unit 1300 is a part that determines a management device server based on information transmitted to and received from the management device server.

  The management device determination unit 1300 of the server D850 according to this modification includes a management device holding unit 1400, a management device notification reception unit 1402, and a server response unit 1412.

  Similar to the management device holding unit 1200 illustrated in FIG. 52, the management device holding unit 1400 is a part that holds management device information.

  Similar to the management device notification reception unit 1204 illustrated in FIG. 52, the management device notification reception unit 1402 is a part that receives a notification from the management device notification unit 1202 of the management device server. 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.

  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 a management device server that is a response destination.

  By providing such a function, a server that does not have the function of the distributed file management apparatus can detect the distributed file management server, and if a request from the user is accepted, the distributed file management is performed as necessary. The server can be inquired about the electronic file holding server according to the user's request.

  In this modification, the case where there is one server that does not have the function of the distributed file management apparatus is taken as an example, but it goes without saying that there may be a plurality of servers.

  The distributed file management system according to the first to fourth embodiments of the present invention has been described above, but the present invention is not limited to these embodiments.

  For example, in the first to third embodiments, the case where there are three servers under the management of the distributed file management apparatus has been described as an example. However, there may be a plurality of servers. In addition, as the number of servers increases, the effect of each embodiment becomes more prominent, such as the user being able to acquire a desired electronic file without being aware of the location of the electronic file.

  The present invention can be applied to an apparatus or system for managing an electronic file group distributed and held by a plurality of servers, in particular, a system configured by a plurality of file servers and an apparatus for managing each file server, The present invention can be applied to a system composed of a plurality of WWW (World Wide Web) servers and devices that manage the respective WWW servers.

10, 310, 510, 610 Distributed file management device 15, 50 Communication line 20, 30, 40, 320, 620, 820 Server 25, 35, 45, 855 File storage unit 60, 65 Terminal 71 User request reception unit 73 Request type Determination unit 75 Request information holding unit 77, 677 File storage control unit 79, 1079 Holding server inquiry unit 81 Holding response receiving unit 83 File transmission request receiving unit 85 File transmitting unit 87 File receiving unit 89 Lock request transmitting unit 91, 391, 1091 Update notification unit 93 Completion notification reception unit 95 User request response unit 100, 400, 500, 700, 1000 Retention server storage unit 102 Inquiry reception unit 104, 404, 504, 704 Retention server determination unit 106 Retention response transmission unit 108 File Transmission request unit 110, 410 Update notification Attachment unit 112, 412 Holding information update unit 114 Update completion notification unit 116 Lock request receiving unit 118 Lock information holding unit 322 Deletion request receiving unit 420 Deletion condition storage unit 422 Clock unit 424, 524 Deletion target determination unit 426 Deletion request unit 624 Hash Value request reception unit 626 Hash value calculation unit 628 Hash value transmission unit 630 Storage unit information request reception unit 632 Storage unit information transmission unit 634 Copy destination reception unit 728 Hash value request unit 730 Hash value reception unit 732 Update permission request reception unit 734 Hash Value initialization unit 736 Update permission transmission unit 738 Storage unit information request unit 740 Storage unit information reception unit 742 Copy destination determination unit 744 Copy destination transmission unit 820, 900 File server unit 910 Management device unit 920, 1300 Management device determination unit 1200, 1400 management device holding unit 1202 Management device notification unit 1204, 1402 Management device notification reception unit 1206 Change determination unit 1208 Management device determination unit 1210 Retention server information acquisition unit 1212, 1412 Server response unit 1214 Server response reception unit

Claims (11)

A distributed file management system for managing electronic files held by a plurality of servers,
The distributed file management system includes: a plurality of servers connected by communication lines; a terminal used by a user who acquires the electronic file from any one of the plurality of servers; and a distributed file management device. Configured,
The distributed file management device includes:
Created by an authorized person that includes the identifier when the terminal receives the request that the terminal obtains the electronic file that includes the user-specified identifier, when the access source server that has received the user's request related to the electronic file Inquiry accepting means for accepting an inquiry as to which holding server is a server holding a genuine electronic file from the access source server;
Holding server storage means for storing file holding information which is information indicating which server holds an electronic file;
A holding server determination unit that determines which of the holding servers is by referring to the file holding information when the inquiry receiving unit receives an inquiry;
File transmission request means for transmitting a file transmission request, which is a request for transmitting an electronic file including the user-specified identifier to the access source server, to a server determined to be a holding server by the holding server determination means. ,
Each of the servers
File storage means for storing the electronic file;
A file transmission request receiving means for receiving the file transmission request transmitted by the file transmission request means;
File storage control means for reading out the electronic file related to the file transmission request from the file storage means;
A 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;
User request receiving means for receiving a user request related to the electronic file from the terminal;
When the request received by the user request receiving unit is the acquisition request, the electronic request file 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 When the request is a write request, the completion of writing of the electronic file related to the write request is received from the file storage control means, and the terminal that is the source of the write request is notified that the writing has been completed A distributed file management system, comprising: a user request response means for performing 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,
The holding server determination unit refers to the file holding information when the inquiry receiving unit receives an inquiry, and the hash value of the electronic file held by the server associated with the user-specified identifier 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 1, wherein: The holding server determining unit refers to the file holding information when the inquiry receiving unit receives an inquiry, and determines a server that holds an electronic file including a user-specified identifier. When,
When the hash value of the electronic file held by the server that is determined to hold the electronic file by the first determination unit is acquired, and the hash value included in the file holding information matches And a second determination unit that determines the server determined to hold the electronic file by the first determination unit as a holding server,
The distributed file management device further includes:
A hash value requesting unit that requests a hash value of the electronic file held by the server to a server that is determined by the first determination unit to hold the electronic file when the inquiry receiving unit receives the inquiry. When,
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
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;
The distributed file management system according to claim 2, further comprising: a hash value transmitting unit that transmits the hash value calculated by the hash value calculating unit to the hash value receiving unit. The inquiry accepting unit may further include an access source server that has received a request to write an electronic file in a file storage unit included in the access source server, and a server that holds the electronic file related to the write request. We accept inquiries about whether
The holding server determining 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 identifier of
The distributed file management device further includes:
When it is determined by the holding server determination means that there is no server that holds the electronic file, the server determines the server having the largest value indicating the free state of the file storage means provided for storing the electronic file by each server, A copy destination determination unit that determines a server having the largest value indicating an empty state as a server that holds a copy of the electronic file related to the write request;
The copy destination determination unit includes a copy destination transmission unit that transmits to the access source server transmission of an electronic file related to the write request to the server that is determined to hold a copy by the copy destination determination unit. The distributed file management system according to any one of claims 1 to 3. The copy destination determining unit, when the holding server determining unit determines that there is no server holding the electronic file, the free capacity of the file storage unit provided for storing the electronic file in each server. 5. The distributed file management system according to claim 4, wherein a server having the largest ratio is determined, and a server having the largest ratio is determined as a server that holds a copy of the electronic file related to the write request. The copy destination determination unit is a server having the largest free space in the file storage means provided for each server to store the electronic file when the holding server determination means determines that there is no server holding the electronic file. The distributed file management system according to claim 4, wherein the server having the largest free space is determined as a server that holds a copy of the electronic file related to the write request. Each of the servers
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;
A file storage control means for reading out an electronic file including the identifier included in the file transmission request from the file storage means;
The file storage control unit includes a file transmission unit that acquires the electronic file read out and transmits the acquired electronic file to the access source server. 7. Distributed file management system described in the section. Each server further includes:
Comprising file receiving means for receiving an electronic file transmitted from the file transmitting means of another server;
The distributed file management system according to any one of claims 1 to 7, wherein the file storage control unit further writes the electronic file received by the file receiving unit into the file storage unit. . 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:
The update notification receiving means for receiving notification by the update notification means, and the 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 any one of claims 1 to 8. The update notification means writes the electronic file related to the request to the file storage means provided 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. The electronic file identifier related to the acquisition request is notified to the distributed file management device as the difference,
The update notification receiving means receives notification from the update notification means,
In accordance with the notification received by the update notification reception unit, the holding information update unit adds information indicating the access source server and information that associates the identifier of the electronic file included in the difference, The distributed file management system according to claim 9, wherein the file holding information is updated. The update notification means writes the electronic file related to the request to the file storage means provided in the access source server when the access source server accepts a request to write the electronic file in the file storage means provided in the access source server. The distributed file management device is notified of the electronic file identifier and hash value related to the write request as the difference,
The update notification receiving means receives notification from the update notification means,
The holding information update unit is configured to receive information indicating the access source server, an identifier of an electronic file included in the difference, and an identifier of the electronic file included in the difference, in response to the notification including the hash value included in the difference received by the update notification receiving unit The distributed file management system according to claim 9, wherein the file holding information is updated by adding a hash value of an electronic file included in the difference.

Images