File server load distribution system and method

Abstract: A load distribution system includes a plurality of servers, each having a memory device in which are stored a plurality of data files for transmission to a plurality of client stations, and a control server which is connected to the plurality of servers for controlling the distribution of transmission requests from client stations as loads on the servers by acquiring transmission counts for data files that are transmitted by the plurality of servers, and determining which server should respond to a transmission request as a data transmission server based on which server has a transmitted data count which is the smallest.

Description: BACKGROUND OF THE INVENTION FIELD OF THE INVENTION The invention relates to a load distribution system that distributes loads to a plurality of file or data servers that transmit files or data that are requested by user or client stations, and to a method of load distribution for such systems. DESCRIPTION OF THE RELATED ART Fig. 7 shows a conventional video server system that comprises, for example, two video servers (server 1 and server 2), three client stations 3-5, and a network connection device 6. While the following description is made with reference to a video server system for purposes of illustration, it is to be noted that the problems encountered are applicable to any type file or data server system. Conventionally, a client desiring a particular video file would directly select a video server through network connection device 6 and send a request to that video server for the transmission of the video file. However, if the load placed on the video server is already at maximum capacity, the client station cannot connect to it. For example, when all the clients 3, 4 and 5 request the transmission of a video file that is available only from the video server 1, the loads for the three clients are placed only on the video server 1, while no transmission load is placed on the video server 2. If the number of clients on the network exceeds the load capacity of the video server 1 and all these clients request the transmission of the same video file, the transmission capability of the video server 1 is exceeded, and the transmission of data by the video server 1 then becomes impossible. Even when the same video file is available at both video servers 1 and 2, so long as selection of specific video servers is left to the client stations, all loads may accumulate at a single video server. Given the arrangement of such a conventional video server, a problem that has arisen is that transmission requests from client stations tend to be directed to only one specific video server and thus all loads are placed on that server. Further, this problem cannot be resolved merely by increasing the number of video servers. The client stations may perform a process for distributing loads over a plurality of video servers. However, in order to do this, all the client stations must have information regarding the load states at the individual video servers, and if the distribution of server loads is performed by the client stations, processing time at the client stations and the load placed on the network will be increased. When a specific video file is frequently employed, the video file may be copied to a plurality of video servers in order to increase the transmission throughput for the video file in the system. However, if such copying is performed many times, available disk space is reduced, and video files that are less frequently used must be deleted to free up disk space. Consequently, a problem has arisen in that additional manpower is required for the accomplishment of management functions, such as the copying and deletion of files. SUMMARY OF THE INVENTION This invention solves the above-described problems. It is one object of the invention to provide a load distribution system for a plurality of servers whereby the loads placed on CPUs and networks, and the number of disk accesses or the loads placed on the disk-accessing capacities of the servers are distributed. It is another object of the invention to provide a method for load distribution over a plurality of servers to eliminate the problems encountered with the conventional systems. This object is solved by the system according to claim 1 and the method according to claim 10. Favourable improvements of the system and method of the invention are given in the respective dependent claims. BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 is a diagram illustrating the structure of a load distribution system according to a first preferred embodiment; Fig. 2 is a diagram illustrating the structure of a control server according to the embodiment of Fig. 1; Fig. 3 is a diagram illustrating the contents of a video server management table according to the embodiment of Fig. 1; Fig. 4 is a diagram illustrating the contents of a client management table according to the embodiment of Fig. 1; Fig. 5 is a flowchart of load distribution processing for a load distribution processing program according to the embodiment of Fig. 1; Fig. 6 is a flowchart of file copying processing for the load distribution processing program according to the embodiment of Fig. 1; and Fig. 7 is a diagram illustrating the structure of a conventional video server system. DESCRIPTION OF PREFERRED EMBODIMENTS A preferred embodiment of the invention will now be described with reference to the drawings. Fig. 1 is a block diagram illustrating the arrangement of a load distribution system according to a first preferred embodiment. The load distribution system includes two video servers 1 and 2, client stations 3, 4 and 5, a network connection device 6, a control server 7, a database 8, and a library server 9. Each video server has a memory (such as a disk drive, for example) in which are stored video data in a specified format such as video files, and the server transmits video data that are requested by client workstations. Client stations 3, 4 and 5 request transmission of video data. Network connection device 6 provides communication links between the servers and client stations. Control server 7 receives transmission requests from the client stations, and selects one of the video servers 1 and 2 for the transmission of requested data taking into account the current and future loads on the video servers 1 and 2. Database 8 stores an access history of transmission requests that the control server 7 has received, and also stores default values for the system. Library server 9 has a secondary memory device with a large memory capacity, and stores in the secondary memory device video files that are deleted at the video servers. The video servers and the client stations may be provided in any desired number, two video servers and three client stations being shown in Fig. 1 solely for purposes of explanation. The network connection device and protocol may be implemented in any suitable manner so long as the client stations, video servers and control server 7 can communicate with each other. Fig. 2 is a block diagram illustrating the structure of the control server 7. The control server 7 receives input data, which contain transmission request data such as a requested video file name, from the client stations 3 through 5, and stores the data in a buffer 11. A video server management table 12 stores data concerning various parameters of video servers 1 and 2. A client management table 13 stores data concerning various parameters of client stations 3 through 5. Output data sent to output buffer 14 indicates which one of the video servers 1 and 2 has been selected. A load distribution processing program 15 performs load distribution processing to select the optimal video server 1 or 2 consonant with the input data 11. The input data 11, the video server management table 12, the client management table 13 and the output data 14 are stored in the memory of the control server 7. In consonance with the input data, such as a requested video file name, that is acquired from the input data buffer 11, and the data in the video server management table 12, the client management table 13 and the database 8, the current operational states of the video servers 1 and 2 and data concerning the requested video file are obtained by the load distribution program to determine the optimal video server 1 or 2 for processing the request, and indicates the optimal video server in the output data 14. The load distribution processing'program 15 thus functions to calculate and determine the optimal video server based on the content of the input data, the video server management table, and the client management table. The data contained in the input data 11 may be only a requested video file name. However, static data that are stored in the database 8, e.g., mirror data and the bandwidth of a video file to be transmitted, may also be stored in the input data area 11 to reduce accesses to the data base 8 by the load distribution processing program 15 to a minimum. Fig. 3 is a diagram showing an example of the contents of the video server management table 12. The load distribution processing program 15 refers to these values when performing processing. Reference numeral 21 denotes names of the video servers that exist in the system (1 and 2 in the exemplary embodiment); reference numeral 22 denotes the maximum transmission counts of the video servers; reference numeral 23 denotes the number of current transmissions by the video servers; reference numeral 24 denotes the maximum bandwidths of the video servers; reference numeral 25 denotes the bandwidths being employed by the video servers for the current transmission; reference numeral 26 denotes the total disk capacities of the video servers; and reference numeral 27 denotes the maximum simultaneous transmission counts for the files of the video servers. Since the video server names 21, the maximum transmission counts 22, the maximum bandwidths 24, the total disk capacities 26, and the maximum simultaneous transmission counts 27 are static data that are specified in advance, they may be set in the management table 12 by reading them from the database 8 at the time of initialization of the control server 7. The current transmission count 23 and the bandwidths 25 that are currently being used are dynamic data that are updated in accordance with transmission requests from the client stations 3 through 5. When a transmission request from one of the client stations is processed and a specific video server is selected for data transmission, the transmission count 23 and the current bandwidth 25 for the specific video server are updated in table 12. Fig. 4 is a diagram showing an example of the contents of the client management table 13. The load distribution processing program 15 also refers to these values when performing processing. Reference numeral 31 denotes the client names of the client stations that are connected to the control server 7 through the network connection device; reference numeral 32 denotes file names of target video files; reference numeral 33 denotes a file size of the target video file; reference numeral 34 denotes a bandwidth that is required for transmitting the target video file; reference numeral 35 denotes a maximum transmission count of the video file; reference numeral 36 denotes the name of a video server that is a current target; and reference numeral 37 denotes current operational contents. Each time an operation by one of the client stations 3 through 5 occurs, the operational contents 37 are updated in order to store operating requests from the client stations. The other data are not updated so long as a target file is unchanged. Fig. 5 is a flowchart explaining the processing performed by the load distribution processing program 15 of the control server 7. The process is performed when one of the client stations 3 through 5 requests that the control server 7 transmit a specific video file. In this process, a particular video server is designated as a transmission video server for which the current transmission count 23 is less than the maximum transmission count 22, for which there is sufficient space in the bandwidth of the network, and for which the current transmission count of the requested video file is smaller than the maximum transmission count which is set at that video server. When the sum of the bandwidth 25 which is being used and the required bandwidth 34 for the requested video file is smaller than the maximum bandwidth 24, it is determined that space is available in the bandwidth of the network for transmission of the requested video file. The detailed process will now be explained. First, at step S101, the video servers in which a requested video file is stored are placed on list L1 in the memory. Then, at step S102, the current transmission counts 23 of the video server management table 12 are referred to, and whichever video server on list L1 has the smallest current transmission count is selected. For the selected video server (hereinafter referred to as VS1) at step S102, at the following step S103 the video server management table 12 is referred to and a check is performed to determine whether or not the current transmission count 23 has reached the maximum transmission count 22. If the determination at step S103 is no, processing goes on to step S104, in which a check is performed to determine whether or not there is sufficient space in the bandwidth of the network. If the check at step S103 indicates that the current transmission count for VS1 is at least a predetermined number below the maximum transmission count, and the check at step S104 indicates that a predetermined minimum bandwidth is available for VS1, VS1 is added to a third list L3 at step S114. If there is sufficient space in the bandwidth as determined at step S104, at step S105 the current transmission count 23 for the requested video file is acquired by referring to the video server management table 12, and a determination is made whether or not the number of transmissions of the requested video file to have reached the maximum transmission count 27. If not, processing goes to the next step S106 in which a check is performed to determine whether the requested video file is already being transmitted, by referring to client management table 13. If not, the process proceeds to step S107, where video server VS1 is designated as a transmission video server. If it is determined that the requested file is being transmitted at step S106, the server VS1 is entered in a second list L2 of video servers currently transmitting the requested video file. If the results of steps S103, S104, S105 or S106 are adverse, the server VS1 is not permitted to transmit the requested video file. At step S109, the selected server VS1 is removed from the list L1, and the list from which the VS1 server has been deleted is regarded as a new list L1. At step S110, it is determined whether the list L1 has been exhausted, i.e. , whether no video servers remain on the list. If not, the process goes back to step S102 where a new VS1 is selected for further processing. If the list L1 is determined to be empty at step S110, the process goes to step S111 where it is determined whether the list L2 is exhausted. If not, at step S112 the video server on list L2 with the smallest transmission count for the requested video file is selected as a new VS1, and at step S107, the VS1 server is designated as the transmission server. If the list L2 is empty, processing proceeds to step S113 where it is determined whether the requested video file should be copied to another video server. The reference information for this determination can be contained either in a transmission request, or may be part of the setup contents of the system. Thus, the optimal load distribution for a particular file can be set either for each request or for the entire system. If it is determined that the requested video file should be copied to another server, processing proceeds to step S201, which will be explained below in connection with the flow chart of Fig. 6. In this regard, the list L3 is consulted for the optimal video server to which to copy the video file. If it not determined to copy the requested file to another server, the process ends, and the client must wait to request the video file at a later time. It should be noted that the maximum transmission count 22 of the VS1 is not the limit of the ability of the VS1. Rather, at the time of the system setup, a theoretical upper limit value, which is smaller than the maximum transmission count consonant with the limit of the ability of the VS1, is set in advance in the database 8, and is defined as the maximum transmission count 22. When it is possible to perform processing during which the theoretically maximum transmission count 22 for the VS1 will be exceeded, e.g., copying at the time of the maximum transmissions, the load distribution processing can be then performed smoothly. Similarly, for the maximum bandwidth 24 of the network, a theoretical upper limit smaller than the actual limit is set in advance in the database 8, so that the load distribution processing can be smoothly performed. The setup values of the maximum transmission count 22 and the maximum bandwidth 24 are read into the video server management table 12 when the load distribution processing program 15 is initialized. An explanation will now be given of the flowchart process of Fig. 6. Fig. 6 shows a file load distribution process for performing a file copy, for which the distribution of the load on the disk capacity of the system is also taken into consideration. In this processing, a requested video file is copied to a video server for which the loads on the transmission and on the disk capacity are smaller than those of the others and in which the requested video file does not exist, and is transmitted from that video server, when all the video servers in which the video file requested for transmission have a high load. When a requested video file is present in all of the video servers, file copying is not required and this processing is not performed. The file load distribution processing takes into account mirror data, which indicates how many video servers each video file is stored within, and a maximum mirror count, which is set in advance for each video file in the system. The mirror data and the maximum mirror count are stored in advance in the database 8. Any format may be used for the mirror data so long as a current mirror count and a video server that is mirrored can be confirmed. The list of current mirror counts and a list of corresponding video servers may be stored separately. According to the form employed in this embodiment, the mirror data is a bit flag indicating a video server, and the current mirror count is found by counting the flags. The maximum mirror count is merely a value. The mirror data and the maximum mirror count may be acquired directly from the database 8, or may be acquired from input data. First, at step S201, by referring to the mirror data for a requested video file, it is confirmed in how many video servers the requested video file is stored, and a check is performed to determine whether or not the obtained mirror data value exceeds the maximum mirror count for the requested video file. If it is found that the current mirror data value for the requested video file has reached the maximum mirror count, program control branches to "Yes" and the processing is thereafter terminated. If the current mirror data value has not reached the maximum mirror count, program control branches to "No" and copying or mirroring can be performed. At step S202, a list L4 is prepared for the video servers in which the requested video file is not stored. It should be noted that the load distribution processing program prepares list L4 in the memory. Then, at step S203, the current transmission counts 23 in the video server management table 12 are referred to, and the video server that has the smallest current transmission count is selected from the list L4 and regarded as the VS1. If, at step S204, it is determined that the current transmission count 23 for the VS1 has reached the maximum transmission count 22 ("Yes"), or if, even when the result is "No", at step S205 it is determined that there is insufficient space in the currently unused bandwidth of the network ("No"), at the following step S208, the VS1 server is removed from the list L4 and the revised list is determined to be a new list L4. When, at step S204, the current transmission count 23 of the VS1 has not reached the maximum transmission count 22 ("No"), and when, at step S205, there is sufficient space in the currently unused bandwidth ("Yes"), at step S206, the amount of free disk space is requested from the VS1 to confirm the free disk space of the VS1. When a sufficient area on the disk is available to which a requested video file can be copied ("Yes"), at step S216 the VS1 is designated as a transmission video server. On the other hand, if, at step S206, the disk capacity is not sufficient ("No"), or when the unused disk capacity of the video server VS1 exceeds the upper limit of the disk capacity that is set in advance, at step S207 it is assumed that the VS1 can be a transmission video server if the unused disk capacity can be acquired, and the VS1 is added as the last entry of a disk shortage list L5. The VS1 is added as the last entry in the list L5 for the reason that since the video servers are selected in ascending order according to a current transmission count, they are also arranged on the list L5 in ascending order according to the current transmission count, so that the video server that has the smallest current transmission count can be sequentially extracted from the top of the list L5 and the amount of processing that is required can be reduced. When at step 5208 the list L4 is updated, at step S209, a check is performed to determine whether or not the list L4 has been exhausted. When the list L4 has not been exhausted ("No"), program control returns to step S203, and the above process is repeated until, at step S216, the transmission video server VS1 is designated, or until, at step S209, it is ascertained that the list L4 has been exhausted. If, at step S209, the list L4 has been exhausted ("Yes"), at the following step S210, the disk shortage list L5 is examined. When the list L5 has been exhausted ("Yes"), it is assumed that no video server has been found for designation as a transmission video server and processing is thereafter terminated. When, at step S210, the list L5 has not been exhausted ("No"), at step S211, the video server from the top of the list L5 is designated as VS1. When, at step S212, it is determined that there is no file that can be deleted from VS1 ("No"), at step S213 the VS1 is deleted from the list L5, the list is updated as a new L5, and program control thereafter returns to step S210. If, at step S212, there is a file that can be deleted ("Yes"), at step S214 that file is deleted, and at step S215 a check is performed to determine whether or not the free disk space of the video server VS1 is adequate for the copying of the requested video file. The determination of file deletion depends on the access frequency that is acquired from an access history. The access history is stored in the database 8 when a client requests transmission. At the time of the transmission request, the name of the requesting client station, the date, the file name, the server name and operational contents, for example, are entered as the access history. Thus, the access record for a video file and the load distribution for servers can be acquired. A video file which is the only file which remains in the system (as determined by using mirror data) is unavailable as a deletion target. However, by referring to the access history, video files that are ascertained to need not exist in the video server, because a long time has elapsed since the last access date, are copied to the library server 9 to retain these files in the system, beginning with the file which has the longest elapsed time since the last access date, and the video files in the video server are deleted so that the required free disk capacity in the video server can be acquired. When, at step S215, an adequate disk capacity can not be obtained ("No"), program control returns to step S212 and the deletion of unnecessary video files is continued. If, at step S215, an adequate disk capacity has been obtained for copying the requested video file, the VS1 is designated as a transmission video server at step S216. Sequentially, at step S217, a check is performed to determine whether or not the list L3 has been exhausted in order to decide which video server (hereafter referred to as a VS2) will be a source for the copying. The list L3, which was prepared at step S114, is of the video servers in which a requested video file is stored, that have current transmission counts 23 smaller than the maximum transmission counts 22 for the video servers, and that have sufficient space in the bandwidths of the network. If the list L3 has not been exhausted ("No"), at step S218 the video server on the list L3 that has the most available space in the bandwidth is designated the VS2. When the list L3 has been exhausted ("Yes"), at step S219 an arbitrary video server in which the requested video file is stored is designated as the VS2. Finally, at step S220, the requested video file is copied from the VS2 server to the VS1 server in order for it to be capable of being transmitted thereafter from the VS1 server. The transmission from VS1 may begin even before the copying from the VS2 to VS1 has been completed, and when transmission is performed in parallel with the copying process, an excellent response for the client stations can be obtained. Although not specified in this embodiment, there are two ways of using the video server VS1, which is designated by the load distribution processing program 15. One way is where the name of a requesting client and a video file name are transmitted to a designated video server VS1 so as to request the video server VS1 to perform the transmission, and the other way is where a designated video server name is returned to a client station to permit the client to access the video server directly. In this embodiment, either method may be employed. Further, although the list L1 is prepared at step S101 in this embodiment, since a list of video servers in which a requested video file is stored is known data, the list L1 may be prepared in advance in the database 8. In addition, although at steps S103, S104, S204 and S205, the transmission count and the bandwidth are referred to in order to determine whether or not transmission can be enabled, only the bandwidth need be referred to for such determination so long as the CPU of a video server is capable of adequate performance, for example, or only the transmission count need be referred to for such determination so long as the bandwidth for the video server is adequate. Further, although, at step S105 and S106, it is taken into consideration that all the transmissions for the same video file should not be allocated to a specific video server, a transmission load may be distributed without such consideration by referring only to current transmission counts or the current bandwidths of the video servers. As is described above, according to this embodiment, since the transmission counts of the video servers are averaged, the concentration of transmission requests to a specific file can be prevented and loads are therefore distributed. In addition, the used disk capacities of the video servers are averaged by copying frequently requested video files to other servers and deleting unused video files from the servers and moving them to an archival library server. Further, as a video file is copied to another video server when the transmission requests for the video file are frequent, the maximum transmission count for the system relative to the requested file is increased, and adequate service is ensured in response to transmission requests from clients. Since video files, the number of which is automatically increased by copying, are automatically deleted as the access frequency is reduced, the labor required for system management can be reduced. As a result of the automatic copying and deletion of video files, copies of a video file that is frequently used is increased, and accordingly, the transmission count for the video file in the system is increased. On the other hand, since the video files that are less frequently used are automatically deleted, the transmission counts for the video files in the system are reduced. Therefore, since the number of copies of the video files, i.e., the transmission counts of the video files, are proportional to their frequency of employment, load distribution in accordance with the disk capacity can be performed in consonance with the frequency of employment. According to a second embodiment of the invention, the access history for each video server is referred to, and data for load distribution for one day are obtained for each video server. It is anticipated that the load for each video server in the following period will be increased or decreased, and this anticipation can be employed as one reference for determination. For example, determination by using the reference is added at steps S102 and S112 in Fig. 5. If the load on the video server tends to be increased, the video server is removed and a video server for which the current and future transmission count is the smallest is selected. The load anticipation according to the one-day load distribution, which is acquired from the access history, can be employed not only for a transmission video server at the time of load distribution, but also for the two video servers that are concerned during a copying process, so that a smooth copying process can be performed. The acquisition of the load distribution data is not limited to units of a day, but may be acquired for units of a month, a week, or an hour, and the units can be selected as needed. Besides the above described reference for determination, an entry for a transmission start time and an entry for a file size can be provided in the client management table 13. The remaining time for a video file that is currently being transmitted is calculated to anticipate a future load, and a video server for which the current and future transmission counts are the smallest can also be selected. A third embodiment of the invention will now be described. In Embodiment 1, loads are distributed upon receipt of transmission requests for a video file not only by performing the transmission load distribution processing for the purpose of averaging transmission counts, but also by performing file load distribution processing to prevent requests for a specific video file to be directed to a single video server, and disk load distribution processing to average the used disk amounts. When a change in the file configuration of a video server is not desired, the file load distribution and the disk load distribution processing shown in Fig. 6 may be skipped, and only the transmission load distribution processing in Fig. 5 need be performed. Optimal load distribution concerning transmission can be provided by performing only the transmission load distribution processing. It should be noted that, in this case, load anticipation may be performed by using statistical information and the remaining time for a video file that is being transmitted. According to a fourth embodiment, when a copying operation is to be performed in response to a request from a client, the file load distribution and disk load distribution processing shown in Fig. 6 can also be performed to perform a copying process with no consideration being given to disk capacity. A video server, which is a copy source, is selected directly by a client, or is acquired in the same manner as in the procedure at step S114 for preparing the list L3. Although video data are employed as an example in the above described embodiments, data are not limited to video data, but may be animation data, static picture data, music data, speech data, text data, etc. Accordingly, the above described video server may be a server that processes data other than video data. The embodiments of the invention having the above-described structure have the following advantages. According to a first aspect of the invention, provided is a load distribution system with calculation means for acquiring a transmission count for each data set that is transmitted by each server, and determination means for selecting, as a data transmission server, a server which is transmitting data that are requested by clients and for which the transmission count is smallest. Since a server that is transmitting data that are requested by clients and for which the transmission count is the smallest performs data transmission, loads can be distributed to a plurality of servers. According to a further aspect of the invention, provided is a method comprising a calculation step of acquiring a transmission count for data that each server is transmitting, and a decision step of selecting, from among the servers that are transmitting the data that are requested by clients, as a data transmision server a server for which the transmission count for the data is the smallest. Since data transmission is performed by a server that is transmitting the data that are requested by clients and for which the transmission count for the data is the smallest, loads can be distributed to a plurality of servers.

Claims: A load distribution system for distributing as loads transmission requests for selected data files issued by a plurality of client stations (3, 4, 5), comprising: (a) a plurality of servers (1, 2), each having a memory device in which are stored a plurality of data files, for transmitting requested data files to client stations; and (b) a control server (7) connected to said plurality of servers (1, 2) characterized in that said control server (7)includes calculation means for acquiring a transmission count for each of said plurality of servers and each of said data files that are transmitted by each of said plurality of servers (1, 2), and determination means (15) for receiving said transmission requests from said plurality of client stations (3, 4, 5), and selecting as a data transmission server for a data file, that is requested by one of said plurality of client stations (3, 4, 5) a server (1, 2) for which the transmission count for the data file that is requested by said one of said plurality of client stations (3, 4, 5) is smallest. A system according to claim 1, characterized by the determination means (15) for further copying a data file that is requested by said client stations (3, 4, 5) from a server (1, 2) storing said data file to a server (1, 2) that does not contain said data file, and for selecting said server (1, 2) to which said data file is copied as a data transmission server. A system according to claim 2, wherein said determination means (15) permits said server (1, 2) to which said data are copied to transmit data files in parallel with execution of copying of said data files to said server (1, 2). A system according to claim 2, wherein said determination means (15) uses maximum transmitted data counts and maximum transmission counts of identical data for said plurality of servers (1, 2) as threshold values for copy execution by said plurality of servers (1, 2), and employs said threshold values to determine whether or not said data files are to be copied. A system according to claim 2, wherein said determination means (15) uses a threshold value, for each item of said data, that indicates a maximum count for data copies to be stored, and employs said threshold value to determine whether or not copying of said data files is to be executed. A system according to claim 2, wherein said determination means (15) verifies a remaining storage capacity for each of said memory devices of said plurality of servers (1, 2), and selects said server (1, 2) to which said data files are to be copied in accordance with said remaining storage capacity. A system according to claim 6, wherein said control server (7) further comprises calculation means (15) for acquiring a transmission count for each of said data files that are transmitted by each of said plurality of servers (1, 2), and wherein, when said remaining storage capacity for said memory devices of each of said plurality of servers (1, 2) is smaller than the size of said data file to be copied, said determination means (15) deletes a data file from a selected server (1, 2) for which a transmission count is smallest. A system according to claim 7, further comprising a library server (9) having a memory device in which a plurality of data are stored, wherein before deletion of data said determination means (15) copies said data to said library server (9). A system according to claim 2, wherein said control server (7) further comprises calculation means (15) for acquiring a load distribution record for a predetermined one of said plurality of servers (1, 2) from transmission access histories for said plurality of servers (1, 2), and wherein, in accordance with said load distribution records, said determination means anticipates loads for said plurality of servers (1, 2) caused by copying operations, and selects as a copy destination server (1, 2) a server (1, 2) that has an anticipated load that is lowest. A load distribution method for distributing as loads among a plurality of servers (1, 2) transmission requests for selected data files issued by a plurality of client stations, characterized by the steps of: acquiring a transmission count for each of said plurality of servers (1, 2) and each of said data files that are transmitted by each of said plurality of servers (1, 2); receiving a transmission request for a data file from one of said client stations (3, 4, 5); and selecting as a data transmissing server for said data file,that is requested by said one of said client stations (3, 4, 5), from among said plurality of servers (1, 2) a server (1, 2), for which the transmission count for the data file that is requested by said one of said plurality of client stations (3, 4, 5) is smallest.

Inventors: MUNAKA TATSUJI, YOSHIDA HIROSHI, MUNAKA, TATSUJI, YOSHIDA, HIROSHI
Applicants: MITSUBISHI ELECTRIC CORP, MITSUBISHI DENKI KABUSHIKI KAISHA
Application year: 1996
Main classification: G06F17
IPC codes: H04L29, H04N5, G06F9