Cloud storage file control system, cloud storage file control method, and cloud storage file control program

The cloud storage file control system uses a virtual server device to manage file movement between cloud storages and on-premise servers, addressing the complexity of expanding cloud storage capacity by simplifying the implementation process.

JP7800067B2Active Publication Date: 2026-01-16NEC CORP
View PDF 15 Cites 0 Cited by

Patent Information

Application Number
JP2021185931
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-11-15
Publication Date
2026-01-16
Estimated Expiration
2041-11-15

AI Technical Summary

Technical Problem

Existing methods for expanding cloud storage capacity by adding additional storage require complex configuration changes and synchronization tasks when linking cloud storage with on-premise file servers, which are difficult for cloud users to implement.

Method used

A cloud storage file control system utilizing a virtual server device to manage file movement between multiple cloud storages and on-premise file servers, allowing seamless expansion of cloud storage capacity without altering the on-premise configuration.

Benefits of technology

Enables the addition of cloud storage capacity without changing the on-premise configuration, simplifying the implementation process and maintaining seamless synchronization.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007800067000001
    Figure 0007800067000001
  • Figure 0007800067000002
    Figure 0007800067000002
  • Figure 0007800067000003
    Figure 0007800067000003
Patent Text Reader

Abstract

To provide a file control system of a cloud storage configured to add a cloud storage without modifying an on-premise configuration.SOLUTION: A file control system of a cloud storage includes: a first cloud storage arranged on the cloud; a virtual server device connected to the first cloud storage; a second cloud storage connected to the virtual server device; a file server device arranged on premise; and a network for connecting the first cloud storage on the cloud and the on-premise file server device. The virtual server device controls migration of files between the first cloud storage connected to the file server device and the second cloud storage.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present invention relates to a cloud storage file control system, a cloud storage file control method, and a cloud storage file control program. [Background technology]

[0002] With the recent evolution of cloud computing, the number of operational models using cloud storage on the cloud is increasing. Among these, there are many operational models that link on-premise file servers with cloud storage, allowing users to enjoy the benefits of both cloud storage and on-premise file servers.

[0003] Among these operational styles, there is also an operational style in which copies of files stored in cloud storage are kept on on-premises file servers and function as caches. This type of operation reduces the amount of communication between the cloud and on-premises, and by storing cache data in a location close to the user, it is possible to achieve high response performance.

[0004] In addition, in many of these operational models, only frequently used files are stored as cache on the on-premises file server, and for less frequently used files, only metadata such as file names and access rights are stored, and the actual data is deleted. This makes it possible to store more files than the capacity of the on-premises file server.

[0005] For example, one such operational model is Microsoft's Azure (registered trademark) File Sync. Azure File Sync synchronizes files between Azure File, a cloud storage service, and on-premises file servers. All file data is stored in Azure Files, and a copy of the file is stored on the on-premises file server through synchronization by Azure File Sync. By limiting the amount of data stored on the file server, it is possible to store infrequently used files as metadata only if the limit is exceeded.

[0006] By linking such cloud storage with on-premise file servers, it is possible to obtain advantages such as high speed by storing copies of files close to the user, storage scalability, which is a feature of cloud computing, and disaster resistance by storing files in a remote location such as the cloud.

[0007] However, there are issues with storage scalability. Cloud storage may have a maximum storage capacity that can be stored in one cloud storage, and if you want to save files beyond this limit, you will need to add more cloud storage. Adding more cloud storage also requires changes to the configuration.

[0008] For example, if cloud storage (1) and an on-premise file server are synchronized over a network, and cloud storage (2) is added to the existing cloud storage (1), a new configuration must be created to perform synchronization between the newly added cloud storage (2) and the on-premise file server. Furthermore, tasks such as selecting and moving files to be stored in cloud storage (1) and files to be stored in cloud storage (2) must also be created.

[0009] As described above, the following methods have been proposed to address the issues regarding file allocation and movement when multiple storage devices exist.

[0010] In Patent Document 1, an intermediate device is placed between the client and the file server, and this intermediate device is configured to accept access from the client. If a file in primary storage is a stub file (dummy file) with no substance, the stub file contains location information for the actual file data, and by redirecting the file to secondary storage based on this information, the existence of multiple file servers is hidden from the client. This allows additional file servers to be hidden from the client, and capacity expansion can be performed without the client being aware of it.

[0011] Patent Document 2 relates to a method for eliminating duplicate files in communication messages by a processor.

[0012] Patent Document 3 relates to an integrated access control system that enables seamless application authentication and access control functions in an information processing system that includes multiple system environments.

[0013] Patent Document 4 relates to a data transfer system between devices connected via a low-speed network line.

[0014] Patent Document 5 relates to a virtual server utilization system that reduces the risk of leakage or loss of confidential data from a virtual server when the virtual server is used.

[0015] Patent Document 6 relates to a method for unifying a plurality of network storages into a virtualized form, so that a plurality of file systems appear as a single virtual file system to a client computer. [Prior art documents] [Patent documents]

[0016] [Patent Document 1] Patent No. 4349301 [Patent Document 2] Special Publication No. 2021-503660 [Patent Document 3] Japanese Patent Application Laid-Open No. 2013-190971 [Patent Document 4] Japanese Patent Application Laid-Open No. 2013-080334 [Patent Document 5] Japanese Patent Application Laid-Open No. 2013-003612 [Patent Document 6] Patent No. 4240930 Summary of the Invention [Problem to be solved by the invention]

[0017] The following analysis is provided by the present invention.

[0018] In the method of Patent Document 1 described above, when multiple storage devices exist, file placement and movement are performed by setting up an intermediate device between the cloud storage and the on-premise file server, but as mentioned above, file data is synchronized between the cloud storage and the on-premise file server. If an intermediate device according to the method of Patent Document 1 is placed between the on-premise file server and the cloud storage, the synchronization function will not work.

[0019] While it is possible to equip an intermediate device with a synchronization function, it would require complex implementation. Also, it would be more efficient to have such a function on the cloud side, but this is difficult for anyone other than the cloud operator, and is not feasible for cloud users.

[0020] The present invention aims to provide a cloud storage file control system, a cloud storage file control method, and a cloud storage file control program that contribute to realizing the addition of cloud storage without changing the on-premises configuration when adding cloud storage to expand the capacity of cloud storage that is synchronized with a file server device, without the need for complex implementation. [Means for solving the problem]

[0021] According to a first aspect of the present invention, a first cloud storage is arranged on a cloud; a virtual server device connected to the first cloud storage; and a second cloud storage is connected to the virtual server device. A file server device located on-premises; a network that connects the first cloud storage on the cloud and the on-premise file server device; A cloud storage file control system can be provided, characterized in that the virtual server device controls file movement between the first cloud storage and the second cloud storage connected to the file server device.

[0022] According to a second aspect of the present invention, there is provided a system including a first cloud storage and a second cloud storage, both of which are arranged on a cloud; a file server device including a virtual server device, which is located on-premises; a network that connects the first cloud storage and the second cloud storage on the cloud to the on-premise file server device; A cloud storage file control system can be provided, characterized in that the virtual server device within the file server device controls the movement of files between the first cloud storage and the second cloud storage connected to the on-premises file server device.

[0023] According to a third aspect of the present invention, there is provided a system including: a first cloud storage arranged on a cloud; a virtual server device connected to the first cloud storage; and a second cloud storage connected to the virtual server device. A file server device located on-premises; In a system including a network connecting the first cloud storage on the cloud and the on-premise file server device, A cloud storage file control method can be provided, which includes a step in which the virtual server device controls the movement of files between the first cloud storage and the second cloud storage connected to the file server device.

[0024] According to a fourth aspect of the present invention, there is provided a system including: a first cloud storage arranged on a cloud; a virtual server device connected to the first cloud storage; and a second cloud storage connected to the virtual server device. A file server device located on-premises; In a system including a network connecting the first cloud storage on the cloud and the on-premise file server device, A program can be provided that causes a computer installed in the virtual server device to execute a process for controlling file transfer between the first cloud storage and the second cloud storage connected to the file server device. This program can be recorded on a computer-readable storage medium. The storage medium can be a non-transient medium such as a semiconductor memory, a hard disk, a magnetic recording medium, or an optical recording medium. The present invention can also be embodied as a computer program product. [Effects of the Invention]

[0025] According to the present invention, it is possible to provide a cloud storage file control system, a cloud storage file control method, and a cloud storage file control program that contribute to realizing the addition of cloud storage without changing the on-premises configuration when adding cloud storage to expand the capacity of cloud storage that is synchronized with a file server device, without the need for complex implementation. [Brief explanation of the drawings]

[0026] [Figure 1] 1 is a diagram showing the configuration of a cloud storage file control system according to an embodiment of the present invention; [Figure 2] FIG. 10 is a diagram illustrating a comparison between the operation of a cloud storage file control system according to an embodiment of the present invention and that of an on-premise file server device in the absence of a virtual server device. [Figure 3] FIG. 10 is a diagram illustrating a comparison between the operation of a cloud storage file control system according to an embodiment of the present invention and that of an on-premise file server device in the absence of a virtual server device. [Figure 4] 1 is a diagram illustrating an example of a configuration of a file control system for cloud storage according to a first embodiment of the present invention. [Figure 5] FIG. 1 illustrates an example of a file server device according to a first embodiment of the present invention. [Figure 6] FIG. 2 is a diagram illustrating an example of a configuration of a virtual server device according to the first embodiment of the present invention. [Figure 7] FIG. 3 is a diagram illustrating an example of a setting table set in a setting file according to the first embodiment of the present invention. [Figure 8] FIG. 4 is a diagram illustrating an example of a dummy file table according to the first embodiment of the present invention. [Figure 9] FIG. 3 is a diagram illustrating an example of a request table according to the first embodiment of the present invention. [Figure 10] FIG. 4 is a diagram illustrating an example of a deletion request table according to the first embodiment of the present invention. [Figure 11] FIG. 4 is a diagram illustrating an example of an operation of a cloud storage monitoring unit of the virtual server device according to the first embodiment of the present invention, monitoring a usage threshold. [Figure 12] FIG. 4 is a diagram illustrating an example of the operation of a file exchange unit of a cloud storage management unit of the virtual server device according to the first embodiment of the present invention. [Figure 13] FIG. 4 is a diagram illustrating an example of a dummy file table according to the first embodiment of the present invention. [Figure 14] FIG. 10 is a diagram illustrating an example of an operation when actual data has been moved in the file server device according to the first embodiment of the present invention and a file having a moved code is accessed. [Figure 15] FIG. 3 is a diagram illustrating an example of a request table according to the first embodiment of the present invention. [Figure 16] FIG. 10 is a diagram illustrating an example of processing when a request ID is recorded in the request table according to the first embodiment of the present invention. [Figure 17] FIG. 10 is a diagram illustrating an example of processing by a file exchange unit of a cloud storage management unit of a virtual server device when a file name, location data where actual data exists, and size are notified in the first embodiment of the present invention. [Figure 18] FIG. 4 is a diagram illustrating an example of a dummy file table according to the first embodiment of the present invention. [Figure 19] FIG. 4 is a diagram illustrating an example of a request table according to the first embodiment of the present invention. [Figure 20] FIG. 4 is a diagram illustrating an example of a dummy file table according to the first embodiment of the present invention. [Figure 21] FIG. 10 is a diagram illustrating an example of an operation performed when actual data has been moved in the file server device according to the first embodiment of the present invention and a file having a moved code is deleted. [Figure 22] FIG. 4 is a diagram illustrating an example of a deletion request table according to the first embodiment of the present invention. [Figure 23] FIG. 10 is a diagram illustrating an example of processing when a deletion request ID is recorded in the deletion request table according to the first embodiment of the present invention. [Figure 24] FIG. 10 is a diagram illustrating an example of processing by a file exchange unit of a cloud storage management unit of a virtual server device when a file name and location data where actual data exists are notified according to the first embodiment of the present invention. [Figure 25] FIG. 4 is a diagram illustrating an example of a dummy file table according to the first embodiment of the present invention. [Figure 26] FIG. 4 is a diagram illustrating an example of a deletion request table according to the first embodiment of the present invention. [Figure 27] FIG. 10 is a diagram illustrating an example of the operation of the file server device according to the first embodiment of the present invention during a transfer process for a file whose actual data has been transferred and which has a transferred code. [Figure 28] FIG. 10 is a diagram illustrating an example of the configuration of a file control system for cloud storage according to a second embodiment of the present invention. [Figure 29] FIG. 10 is a diagram illustrating an example of the configuration of a parent file server device that has the functions of a virtual server device according to a second exemplary embodiment of the present invention. [Figure 30] FIG. 1 is a diagram showing the configuration of a computer that constitutes the cloud storage file control system of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0027] First, an overview of one embodiment of the present invention will be described with reference to the drawings. Note that the reference numerals in the drawings attached to this overview are attached to each element for convenience as an example to facilitate understanding, and are not intended to limit the present invention to the illustrated form. Furthermore, connecting lines between blocks in the drawings and the like referred to in the following description include both bidirectional and unidirectional lines. Unidirectional arrows are used to schematically indicate the flow of the main signal (data) and do not exclude bidirectionality.

[0028] 1 is a diagram showing the configuration of a cloud storage file control system according to one embodiment of the present invention. In one embodiment, the present invention can be realized by a cloud storage file control system 1, as shown in FIG.

[0029] More specifically, as shown in Figure 1, the cloud storage file control system 1 of one embodiment of the present invention includes a cloud storage (1) 110 (first cloud storage) arranged on the cloud 100, a virtual server device 120 connected to the cloud storage (1) 110 (first cloud storage), a cloud storage (2) 130 (second cloud storage) connected to the virtual server device 120, a file server device (1) 210 arranged on the on-premise 200, and a network 300 connecting the cloud storage (1) 110 (first cloud storage) on the cloud 100 and the file server device (1) 210 on the on-premise 200. The on-premise file server device (1) 210 and the cloud storage (1) 110 (first cloud storage) on the cloud are connected by the network 300, and files on the cloud storage (1) 110 (first cloud storage) are synchronized to create copies of files on the cloud storage on the file server device (1) 210.

[0030] The virtual server device 120 controls file movement between the cloud storage (1) 110 (first cloud storage) and the cloud storage (2) 130 (second cloud storage) connected to the file server device (1) 210.

[0031] 2 and 3 are diagrams comparing the operation of a cloud storage file control system 1 according to an embodiment of the present invention and an on-premise file server device when no virtual server device is present. Fig. 2 shows a case where only cloud storage (1) is in operation, while Fig. 3 shows a configuration where cloud storage (2) is added to cloud storage (1). A new configuration must be created to perform synchronization between the newly added cloud storage (2) 130 and the on-premise file server device (1) 210. Furthermore, tasks such as selecting and moving files to be placed in cloud storage (1) 110 and files to be placed in cloud storage (2) 130 must also be performed.

[0032] In contrast, in the cloud storage file control system 1 of one embodiment of the present invention, even if cloud storage (2) 130 (second cloud storage) is added to cloud storage (1) 110 (first cloud storage), the virtual server device 120 moves files between cloud storage (1) 110 (first cloud storage) and cloud storage (2) 130 (second cloud storage), thereby securing free space in cloud storage (1) 110 (first cloud storage), concealing the existence of cloud storage (2) 130 (second cloud storage) from the file server device (1) 210, and preventing configuration changes due to an increase in stored files.

[0033] As described above, according to the cloud storage file control system 1 of one embodiment of the present invention, when adding cloud storage to expand the capacity of cloud storage synchronized with a file server device, it is possible to add cloud storage without changing the configuration of the on-premises file server device, without the need for complex implementation.

[0034] [First embodiment] Next, a cloud storage file control system 1 according to a first embodiment of the present invention will be described with reference to the drawings.

[0035] [Configuration of the first embodiment] First, the configuration of the first embodiment will be described with reference to Figs. 4 to 10. Fig. 4 is a diagram showing an example of the configuration of a cloud storage file control system 1 according to the first embodiment of the present invention. In Fig. 4, components with the same reference numerals as in Fig. 1 indicate the same components as in Fig. 1. The parts written in bold (120, 112, 113, 114, 210 to 230) are components added by the present invention. The other components are components based on existing technologies that have existed for a long time.

[0036] Referring to Figure 4, the cloud storage file control system 1 of the first embodiment of the present invention is divided into a part on the cloud 100 and an on-premise 200 part, and the part on the cloud 100 and the on-premise 200 part are connected by a network 300.

[0037] Cloud 100 is provided with cloud storage (1) 110 and cloud storage (2) 130 to cloud storage (n) 150. Also provided in cloud 100 is a virtual server device 120 configured with a virtual machine on the cloud, which is connected to all cloud storages. Cloud storage (1) 110 is connected to multiple on-premise file server devices (1) 210 to (n) 230. Cloud storage (1) 110 is provided with a dummy file table 112, a request table 113, and a deletion request table 114. Copies of the request table 113, the dummy file table 112, and the deletion request table 114 are stored in the on-premise file server devices (1) 210 to (n) 230 using a synchronization function.

[0038] The on-premise 200 is provided with file server devices (1) 210 to (n) 230, which are connected to the cloud storage (1) 110 and synchronize files with each other. Client devices (1) 215 to (n) 235 are connected to the file server devices (1) 210 to (n) 230, respectively.

[0039] Next, the configuration of a file server device according to a first embodiment of the present invention will be described. FIG. 5 is a diagram showing an example of a file server device according to the first embodiment of the present invention. Referring to FIG. 5, details of file server device (1) 210 are shown. The other file servers (2) 220 to (n) 230 may also have similar configurations. The parts written in bold (512) are components added by the present invention. The other components are components based on existing technologies that have existed for some time.

[0040] The file server device (1) 210 is an information processing device (central processing unit; processor; data processing device) that operates under program control.

[0041] The file server device (1) 210 includes a storage unit 500, a file processing unit 510, a file synchronization unit 520, and a communication processing unit 530.

[0042] The storage unit 500 provides a function for storing data.

[0043] File processing unit 510 corresponds to a file system in an operating system. With reference to Figure 5, file processing unit 510 includes file processing means 511 and file filter means 512. These means each operate roughly as follows.

[0044] The file processing means 511 of the file server device (1) 210 provides operation functions for files, such as opening, closing, updating data, and deleting files.

[0045] The file filter means 512 cooperates with the file processing means 511 to provide a function for examining the contents of a file during file operation processing. If a moved code is detected during processing to examine the file contents, this means that the actual data for that file has been moved from cloud storage (2) 130 to either cloud storage (n) 150. Therefore, the file ID (identification code) is checked from the dummy file table 112, and if the file is being opened, the ID is recorded in the request table 113. If the file is being deleted, the ID is recorded in the deletion request table 114.

[0046] Next, when a file is opened, the file server device (1) 210 periodically refers to the request table 113, and when a file is deleted, the file server device (1) 210 periodically refers to the deletion request table 114.

[0047] If the file is being opened and the ID of the file has been deleted from the request table 113, this indicates that the actual data of the file has been completely moved to the cloud storage (1) 110, and normal processing continues through the file processing means 511.

[0048] When deleting a file, if the ID of the file has been deleted from the deletion request table 114, this means that the actual data of the file has been deleted from cloud storage (2) 130 to cloud storage (n) 150, and so the file is deleted from cloud storage (1) 110 by continuing normal processing through the file processing means 511.

[0049] 5, the file synchronization unit 520 includes a file synchronization means 521. The file synchronization means 521 operates roughly as follows.

[0050] The file synchronization means 521 communicates with the cloud storage (1) 110 using the function of the communication processing unit 530, and realizes synchronization of the file data in the cloud storage (1) 110 and the file data in the storage unit 500 using the function of the file processing unit 510.

[0051] 5, the communication processing unit 530 includes a communication processing means 531. These means each operate roughly as follows.

[0052] The communication processing means 531 provides the file processing unit 510 and the file synchronization unit 520 with a communication function for transmitting and receiving data to and from the network 300 .

[0053] Next, the configuration of the virtual server device according to the first embodiment of the present invention will be described. Fig. 6 is a diagram showing an example of the configuration of the virtual server device according to the first embodiment of the present invention. Referring to Fig. 6, details of the virtual server device 120 are shown. In Fig. 6, the parts written in bold (600, 631) are components added by the present invention. The other components are components based on existing technologies that have existed for some time.

[0054] The virtual server device 120 is created based on a virtual machine running on the cloud 100 .

[0055] The virtual server device 120 includes a cloud storage management unit 600 , a storage unit 630 , a file processing unit 640 , a file synchronization unit 650 , and a communication processing unit 660 .

[0056] The cloud storage management unit 600 includes a cloud storage monitoring unit 610 and a file exchange unit 620 .

[0057] 6, the cloud storage monitoring unit 610 includes a cloud storage usage monitoring means 611 and a table monitoring means 612. These means each operate roughly as follows.

[0058] Cloud storage usage monitor 611 provides a function to periodically monitor the usage status and usage amount of cloud storage. For cloud storage (1) 110, if the usage amount exceeds the upper limit threshold defined in the setting table of setting file 631 stored in storage unit 630 of virtual server device 120, it notifies file exchange unit 620 of this.

[0059] The table monitoring means 612 provides a function (polling function) to periodically monitor the request table 113 and the deletion request table 114 of the cloud storage (1) 110. If it is confirmed that the data of the file to be accessed is recorded in the request table 113, it notifies the file exchange unit 620 of this fact.

[0060] If it is confirmed that the data of the file to be deleted is recorded in the deletion request table 114, the file exchange unit 620 is notified of this.

[0061] 6, the file exchange unit 620 includes a file selection means 621, a file exchange means 622, and a file deletion means 623. These means each operate roughly as follows.

[0062] When the file exchange unit 620 receives an instruction to transfer actual data of a file between the cloud storage (1) 110 and the cloud storage (2) 130 to the cloud storage (n) 150, the file selection means 621 determines which files in the cloud storage (1) 110 are to be the target of the actual data transfer and the cloud storage to which the data is to be transferred. The files to be selected are selected so that the total size is equal to or greater than the size of the free space that needs to be created in the cloud storage (1) 110.

[0063] The file selection means performs the file selection based on the file selection policy defined in the setting table of the setting file 631 stored in the storage unit of the virtual server device until the required size is reached.

[0064] After the file selection is completed, the path and file name of the selected file are notified to the file exchange means 622, and an instruction is given to transfer the actual data from the cloud storage (1) 110.

[0065] The file exchange means 622 executes actual data movement of files between the cloud storage (1) 110 and the cloud storage (2) 130 to the cloud storage (n) 150. There are two cases of actual data movement: when data leaves the cloud storage (1) 110 and when data enters the cloud storage (1) 110.

[0066] First, in the case of data leaving the cloud storage (1) 110, the path and file name of the file to be moved as actual data is provided to the file exchange means along with a move instruction from the cloud storage (1) 110.

[0067] The file exchange means 622 uses the file processing unit 640 to create a copy of the target file in the cloud storage with the largest free space among the cloud storages (2) 130 and (n) 150, which is the destination cloud storage.

[0068] Next, the actual data in the target file is rewritten to contain only the moved code. This moved code can be a number sequence or the string "Moved" as long as it is defined to indicate that the file has been moved. By doing this, the actual data in the target file will contain only the moved code, making it possible to reduce its size.

[0069] Next, information such as the destination of the file to which the actual data has been moved is recorded in the dummy file table 112 using the file processing unit 640. Details of the items recorded in the dummy file table 112 will be described later in detail in the section on the dummy file table 112.

[0070] In the second case, when data is transferred to cloud storage (1) 110, the ID of the file for which actual data is to be transferred to cloud storage (1) 110 is passed, and the current location of the file is confirmed from the dummy file table 112, and the file is transferred from the cloud storage where the file is located to cloud storage (1) 110 using the file processing unit 640.

[0071] Next, the records that match the ID are deleted from the request table 113 and the dummy file table 112.

[0072] The file deletion means 623 uses the ID of the file to be deleted that has been passed to it to check the current location of the actual data of that file from the dummy file table 112, and then deletes the file. Next, it deletes the information about that file from the deletion request table 114 and the dummy file table 112.

[0073] The storage unit 630 provides a function for storing data, and includes a setting file 631, as shown in FIG.

[0074] The configuration file 631 records the contents of the operations that can be defined by the user.

[0075] 7 is a diagram showing an example of a setting table 701 set in the setting file 631 according to the first embodiment of the present invention. Referring to Fig. 7, the "setting name" column lists the items that can be set, and the "setting value" column lists the setting values.

[0076] The "usage threshold" defines the usage rate of the cloud storage (1) 110 relative to its maximum capacity.

[0077] The "file selection policy" defines how files are selected by the file selection means 621 of the file exchange unit 620. Specifically, there are "random" which selects files randomly, "oldest first" which selects files in order of oldest last access time, and "importance" which assigns importance to files and selects them in order of least important, but the policy is not limited to these and other methods may be defined according to the operation.

[0078] File processing unit 640 corresponds to a file system in an operating system. With reference to Figure 6, file processing unit 640 includes file processing means 641. File processing means 641 operates roughly as follows.

[0079] The file processing means 641 provides operation functions for files, such as opening, closing, updating data, and deleting files.

[0080] 6, the file synchronization unit 650 includes a file synchronization means 651. The file synchronization means 651 generally operates as follows.

[0081] The file synchronization means 651 communicates with the cloud storage using the function of the communication processing unit 660, and realizes synchronization of the file data in the cloud storage and the file data in the storage unit 630 using the function of the file processing unit 640.

[0082] 6, the communication processing unit 660 includes a communication processing means 661. The communication processing means 661 generally operates as follows.

[0083] The communication processing unit 661 provides the file processing unit 640 , the file synchronization unit 650 , and the cloud storage management unit 600 with a communication function for transmitting and receiving data to and from the network 300 .

[0084] Next, the dummy file table 112, request table 113, and deletion request table 114, which are arranged in the cloud storage (1) 110, synchronized with the on-premise file server device, and have copies stored therein, will be described.

[0085] The dummy file table 112 is used to record files whose actual data has been moved from the cloud storage (1) 110 to another cloud storage.

[0086] 8 is a diagram showing an example of the dummy file table 112 according to the first embodiment of the present invention. Referring to Fig. 8, the dummy file table 112 is a table including an "ID" column, a "cloud storage name" column, a "path" column, an "original path" column, a "file name" column, a "size" column, and a "time" column.

[0087] The "ID" column is a code for uniquely identifying a file recorded in the dummy file table 112. A unique code such as a GUID or a sequential number sequence is recorded.

[0088] The "Cloud Storage Name" column records the name of the cloud storage where the actual data of the file is stored.

[0089] The "Path" column records the path where the actual data of the file is stored.

[0090] The "original path" column records the path of the file on the cloud storage (1) 110.

[0091] The "file name" column records the file name of the file.

[0092] The "Size" column records the size of the file.

[0093] The “time” column records the time when the file was recorded in the dummy file table 112 .

[0094] 9 is a diagram showing an example of the request table 113 according to the first embodiment of the present invention. The request table 113 is used to record files that are accessed from the dummy file table 112 and for which a request has been made to move the actual data to the cloud storage (1) 110.

[0095] Referring to FIG. 9, the request table 113 is a table including a "request ID" column and a "time" column.

[0096] The "request ID" column records the ID in the dummy file table 112 of the file that has been accessed and for which a request has been made to move the actual data to the cloud storage (1) 110.

[0097] In the "time" column, the time recorded in the request table 113 is recorded.

[0098] 10 is a diagram showing an example of the deletion request table 114 according to the first embodiment of the present invention. The deletion request table 114 is used to record files for which a deletion request has been made among files recorded in the dummy file table 112.

[0099] Referring to FIG. 10, the deletion request table is a table including a "deletion request ID" column and a "time" column.

[0100] The "deletion request ID" column records the ID in the dummy file table 112 of the file for which a deletion request has been made.

[0101] The "time" column records the time when the request was recorded in the deletion request table 114.

[0102] [Operation of the first embodiment] Next, the operation of the first embodiment of the present invention will be described in detail with reference to Figures 11 to 27. File processing operations other than those shown in the operation of the first embodiment of the present invention are general operations based on existing technology, and will not be described here.

[0103] [1. What happens when cloud storage (1) exceeds the usage threshold] First, the monitoring of the usage threshold in the setting table 701 in FIG. 7 and the operation when the cloud storage (1) 110 exceeds the usage threshold will be described with reference to FIGS.

[0104] 11 is a diagram illustrating an example of the operation of the cloud storage monitor 610 of the virtual server device 120 monitoring the usage threshold according to the first embodiment of the present invention. With reference to FIG. 11, the operation of the cloud storage monitor 610 of the virtual server device 120 monitoring the usage threshold will be described.

[0105] The cloud storage usage monitoring means 611 of the cloud storage monitoring unit 610 of the cloud storage management unit 600 of the virtual server device 120 checks whether the usage of the cloud storage (1) 110 exceeds the usage threshold of the setting table 701 mentioned above (step S1-1).

[0106] If the usage of the cloud storage (1) 110 does not exceed the usage threshold in step S1-1, the process waits for a certain period of time (step S1-2) and then executes step S1-1 again. The waiting time is adjusted according to operational requirements, with a target of about one second.

[0107] If it is determined in step S1-1 that the usage of the cloud storage (1) 110 exceeds the usage threshold, the size required to reduce the usage of the cloud storage (1) 110 to the usage threshold or less is calculated (step S1-3).

[0108] The size value calculated in step S1-3 is notified to the file exchange unit 620 (step S1-4), and a predetermined time wait is executed in step S1-2.

[0109] Next, the operation of the file exchange unit 620 of the cloud storage management unit 600 of the virtual server device 120 will be described with reference to Fig. 12. Fig. 12 is a diagram illustrating an example of the operation of the file exchange unit 620 of the cloud storage management unit 600 of the virtual server device 120 according to the first embodiment of the present invention.

[0110] The file exchange unit 620, which has received the size value in step S1-4, determines which files in the cloud storage (1) 110 will be the target of the actual data transfer and which cloud storage will be the transfer destination, using the file selection means 621. The files to be selected are selected so that the total size is equal to or greater than the size value received in step S1-4.

[0111] The file selection is performed based on the file selection policy defined in the setting table 701 (FIG. 7) of the setting file 631 stored in the storage unit 630 of the virtual server device 120 until the required size is reached (step S2-1).

[0112] Next, the free space of the cloud storage (2) 130 to the cloud storage (n) 150 is checked (step S2-2).

[0113] Based on the result of step S2-2, the cloud storage with the largest free space is selected as the storage to which the actual data is to be moved (step S2-3).

[0114] The file exchange means 622 creates a copy of the file selected in step S2-1 in the cloud storage selected in step S2-3 (step S2-4).

[0115] The actual data of the original file copied in step S2-4 is rewritten to contain only the moved code. This moved code can be a number sequence or the string "Moved" as long as it is defined to indicate that the file has been moved. This reduces the actual data of the target file to only the moved code, making it possible to reduce its size (step S2-5).

[0116] The files copied in step S2-4 are recorded in the dummy file table 112 (step S2-6). The following values ​​are recorded in each column of the dummy file table 112.

[0117] The "ID" column is a code for uniquely identifying a file recorded in the dummy file table 112. A unique code such as a GUID or a sequential number sequence is recorded.

[0118] The "Cloud Storage Name" column records the name of the cloud storage where the actual data of the file is stored.

[0119] The "Path" column records the path where the actual data of the file is stored.

[0120] The "original path" column records the path of the file on the cloud storage (1) 110.

[0121] The "file name" column records the file name of the file.

[0122] The "Size" column records the size of the file.

[0123] The “time” column records the time when the file was recorded in the dummy file table 112 .

[0124] Fig. 13 is a diagram showing an example of the dummy file table 112 according to the first embodiment of the present invention. The example shown in Fig. 13 shows a case where, in step S2-6, for example, two files, sample01.mp4 and sample02.mp4, are copied to the cloud storage (2) 130, and the actual data is transferred.

[0125] The above is the monitoring of the usage threshold and the operation when the usage threshold is exceeded by the cloud storage (1) 110. This operation creates free space in the cloud storage (1) 110, and the usage falls below the usage threshold.

[0126] [2. Behavior when accessing a file] Next, with reference to FIGS. 14 to 19, the operation when accessing a file in which actual data has been moved and which has moved code will be described.

[0127] 14 is a diagram illustrating an example of the operation when actual data has been moved in the file server device (1) 210 according to the first embodiment of the present invention and a file having a moved code is accessed. With reference to FIG. 14, the operation when actual data has been moved in the file server device (1) 210 and a file having a moved code is accessed will be described.

[0128] A file open processing request (open request) for file access is accepted by the file processing means 511 of the file processing unit 510 of the file server device (1) 210 (step S3-1).

[0129] Next, the file filter means 512 working in conjunction with the file processing means 511 reads the contents of the file (step S3-2).

[0130] Then, the file filter means 512 checks whether or not there is any code that has been moved (step S3-3).

[0131] If no moved code exists in step S3-3, the file open process continues as usual (step S3-8).

[0132] If there is a moved code in step S3-3, the file filter means 512 checks the ID of the file to be opened from the dummy file table 112 (step S3-4). For example, if sample01.mp4 in Fig. 13 is to be opened, the ID will be xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx0000. The dummy file table 112 exists in the cloud storage (1) 110, and a copy is created in the file server device (1) 210 and is synchronized.

[0133] Next, the file filter means 512 records the ID confirmed in step S3-4 as a request ID in the request table 113, and also records the time of recording in the request table 113 (step S3-5). For example, in this first embodiment, it looks like FIG. 15. FIG. 15 is a diagram showing an example of the request table 113 in the first embodiment of the present invention. The request table 113 exists in the cloud storage (1) 110, and a copy is created in the file server device (1) 210 and is synchronized.

[0134] Next, the file filter means 512 waits for a certain period of time (about 1 second) (step S3-6).

[0135] Next, the file filter means 512 refers to the contents of the request table 113 and checks whether the request ID written in step S3-5 exists (step S3-7). If the ID does not exist, this indicates that a file with the actual data already exists in the cloud storage (1) 110, and the file processing means 511 executes step S3-8 to continue file processing. If the request ID exists, it executes step S3-6 and waits.

[0136] Next, processing when a request ID is recorded in the request table 113 will be described with reference to Fig. 16. Fig. 16 is a diagram illustrating an example of processing when a request ID is recorded in the request table 113 according to the first embodiment of the present invention. The fact that a request ID is recorded in the request table 113 indicates that there is a request from cloud storage (2) 130 to open a file existing in cloud storage (n) 150. This processing is performed by the cloud storage management unit 600 of the virtual server device 120.

[0137] The table monitoring means 612 of the cloud storage monitoring unit 610 waits for a certain period of time (about 1 second) (step S4-1).

[0138] After the waiting in step S4-1 is completed, the table monitoring means 612 of the cloud storage monitoring unit 610 refers to the request table 113 to check whether the request ID exists (step S4-2). If the request ID does not exist, step S4-1 is executed and the process waits again. If the request ID exists, step S4-3 is executed.

[0139] The request ID is checked from the request table 113 (step S4-3).

[0140] The dummy file table 112 is referenced to confirm the request ID, the file name that matches the request ID, the location data where the actual data exists, and the size, and this is notified to the file exchange unit 620 (step S4-4).

[0141] 17 is a diagram illustrating an example of processing by the file exchange unit 620 of the cloud storage management unit 600 of the virtual server device 120 when the file name, location data where the actual data exists, and size are notified according to the first embodiment of the present invention. The processing by the file exchange unit 620 of the cloud storage management unit 600 of the virtual server device when the file name, location data where the actual data exists, and size are notified will be described with reference to FIG.

[0142] Based on the notified data, the size of the requested file is confirmed (step S5-1).

[0143] It is checked (step S5-2) whether there is sufficient free space in the cloud storage (1) 110 to store the file of the size checked in step S5-1. If there is sufficient free space, step S5-9 is executed.

[0144] If there is not enough free space, step S5-3 is executed.

[0145] The file exchange unit 620 uses the file selection means 621 to determine which files in the cloud storage (1) 110 are to be subject to actual data transfer, and which cloud storage is to be the transfer destination. The files to be selected are selected so that the total size is equal to or greater than the size value passed in step S4-4.

[0146] The file selection is performed based on the file selection policy defined in the setting table (FIG. 7) of the setting file stored in the storage unit of the virtual server device until the required size is reached (step S5-3).

[0147] The free space of the cloud storage (2) 130 to the cloud storage (n) 150 is checked (step S5-4).

[0148] Based on the result of step S5-4, the cloud storage with the largest free space is selected as the storage to which the actual data is to be moved (step S5-5).

[0149] The file exchange means 622 creates a copy of the file selected in step S5-3 in the cloud storage selected in step S5-5 (step S5-6).

[0150] The actual data of the file from which the file was copied in step S5-6 is rewritten to contain only the moved code. This moved code can be a number sequence or the string "Moved" as long as it is defined to indicate that the file has been moved. By doing this, the actual data of the target file becomes the moved code only, making it possible to reduce the file size (step S5-7).

[0151] The files copied in step S5-6 are recorded in the dummy file table. The following values ​​are recorded in each column of the dummy file table 112.

[0152] The "ID" column is a code for uniquely identifying a file recorded in the dummy file table 112. A unique code such as a GUID or a sequential number sequence is recorded.

[0153] The "Cloud Storage Name" column records the name of the cloud storage where the actual data of the file is stored.

[0154] The "Path" column records the path where the actual data of the file is stored.

[0155] The "original path" column records the path of the file on the cloud storage (1) 110.

[0156] The "file name" column records the file name of the file.

[0157] The "Size" column records the size of the file.

[0158] The “time” column records the time when the file was recorded in the dummy file table 112 .

[0159] Fig. 18 is a diagram showing an example of the dummy file table 112 according to the first embodiment of the present invention. In the example of the dummy file table 112 shown in Fig. 18, two files, sample03.mp4 and sample04.mp4, have been copied to the cloud storage (2) 130 and the actual data has been transferred to the dummy file table 112 in the state shown in Fig. 13 (step S5-8).

[0160] The file notified in step S4-4 of FIG. 16 is moved to the cloud storage (1) 110 (step S5-9).

[0161] In step S5-9, information corresponding to the file moved to cloud storage (1) 110 is deleted from request table 113 and dummy file table 112. In this example of the first embodiment, the ID of the file is xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx0000 and the file name is sample01.mp4, so the request table 113 becomes like the example of the request table of the first embodiment of the present invention shown in Fig. 19, and the dummy file table 112 becomes like the example of the dummy file table 112 of the first embodiment of the present invention shown in Fig. 20 (step S5-10).

[0162] [3. Behavior when deleting files] Next, the operation of the file server device (1) 210 when deleting a file whose actual data has been moved and which has a moved code will be described with reference to FIGS.

[0163] 21 is a diagram illustrating an example of the operation when actual data has been moved in the file server device (1) 210 according to the first embodiment of the present invention and a file having a moved code is deleted. With reference to FIG. 21, the operation when actual data has been moved in the file server device (1) 210 and a file having a moved code is deleted will be described.

[0164] The file processing means 511 of the file processing unit 510 of the file server device (1) 210 accepts a file deletion request for file access (step S6-1).

[0165] The file filter means 512, which is linked to the file processing means 511, reads the contents of the file (step S6-2).

[0166] The file filter means 512 checks whether or not there is any moved code (step S6-3). If there is no moved code, step S6-8 is executed. If there is moved code, step S6-4 is executed.

[0167] Next, the file filter means 512 checks the ID of the file to be deleted from the dummy file table 112. For example, when an attempt is made to delete sample02.mp4, if the dummy file table is in the state shown in Fig. 20, the ID will be xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx0001 (step S6-4).

[0168] The file filter means 512 records the ID confirmed in step S6-4 in the deletion request table 114. For example, if an attempt is made to delete sample02.mp4 from the state of the dummy file table 112 in Fig. 20, the deletion request table 114 will look like the one shown in Fig. 22 (step S6-5). Fig. 22 is a diagram showing an example of the deletion request table 114 according to the first embodiment of the present invention.

[0169] The file filter means 512 waits for a certain period of time (about one second) (step S6-6).

[0170] The file filter means 512 checks whether the deletion request ID recorded in the deletion request table in step S6-5 exists in the deletion request table 114 (step S6-7). If it does not exist, this indicates that a file matching the deletion request ID that existed in a cloud storage other than cloud storage (1) 110 has been deleted. If the deletion request ID does not exist in the deletion request table 114, the file processing means 511 executes step S6-8. If the deletion request ID exists in the deletion request table 114, step S6-6 is executed.

[0171] The file processing means 511 deletes the file requested for deletion through normal deletion processing, which deletes the file requested for deletion from the cloud storage (1) 110 (step S6-8).

[0172] 23 is a diagram illustrating an example of processing when a deletion request ID is recorded in the deletion request table 114 according to the first embodiment of the present invention. Referring to FIG. 23, processing when a deletion request ID is recorded in the deletion request table 114 will be described. The fact that a deletion request ID is recorded in the deletion request table 114 indicates that there is a deletion request from cloud storage (2) 130 to a file existing in cloud storage (n) 150. This processing is performed by the cloud storage management unit 600 of the virtual server device 120.

[0173] The table monitoring means 612 of the cloud storage monitoring unit 610 waits for a certain period of time (about 1 second) (step S7-1).

[0174] After the wait in step S7-1 is completed, the table monitoring means 612 of the cloud storage monitoring unit 610 refers to the deletion request table 114 to check whether the deletion request ID exists (step S7-2). If the deletion request ID does not exist, step S7-1 is executed and the process waits again. If the deletion request ID exists, step S7-3 is executed.

[0175] The deletion request ID is checked from the deletion request table 114 (step S7-3).

[0176] The file name of the ID that matches the deletion request ID and the location data where the actual data exists are checked from the dummy file table 112, and this is notified to the file exchange unit 620 (step S7-4).

[0177] 24 is a diagram illustrating an example of processing by the file exchange unit of the cloud storage management unit of the virtual server device when the file name and location data where the actual data exists are notified according to the first embodiment of the present invention. Next, the processing by the file exchange unit 620 of the cloud storage management unit of the virtual server device 120 when the file name and location data where the actual data exists are notified will be described with reference to FIG.

[0178] Based on the notified data, the file is deleted from the corresponding cloud storage (step S8-1).

[0179] The data of the file is erased from the deletion request table 114 and the dummy file table 112 (step S8-2). For example, if sample02.mp4 is to be deleted from the state of the dummy file table in Fig. 20, the dummy file table 112 will be in the state of the example dummy file table of the first embodiment of the present invention in Fig. 25, and the deletion request table 114 will be like the example deletion request table of the first embodiment of the present invention in Fig. 26.

[0180] [4. File transfer process] Next, the operation of moving a file will be described. Fig. 27 is a diagram illustrating an example of the operation of the file server device (1) 210 according to the first embodiment of the present invention during the movement processing for a file whose actual data has been moved and which has a moved code.

[0181] With reference to FIG. 27, the operation of the file server (1) 210 during the transfer process for a file whose actual data has been transferred and which has a transferred code will be described.

[0182] A request for file transfer is received by file processing means 511 of file processing unit 510 (step S9-1).

[0183] The file filter means 512, which is linked to the file processing means 511, reads the contents of the file (step S9-2).

[0184] The file filter means 512 checks whether or not there is any moved code (step S9-3). If there is any moved code, step S9-4 is executed. If there is no moved code, step S9-5 is executed.

[0185] If the file filter means 512 confirms the presence of moved code in step S9-3, it rewrites the "original path" column in the dummy file table to the path of the destination (step S9-4).

[0186] The file processing means 511 performs the file transfer through normal transfer processing (step S9-5).

[0187] The above is a description of the operation of Example 1. As mentioned above, file processing operations other than those of the example shown here are general operations based on existing technology, and therefore are not described here.

[0188] As described above, the cloud storage file control system 1 of the first embodiment of the present invention does not require complex implementation or an intermediate device, and when adding cloud storage to expand the capacity of cloud storage synchronized with a file server device, it is possible to add cloud storage without changing the on-premise configuration, i.e., the connection configuration between the on-premise file server device and the cloud storage. In this way, even if the capacity of the cloud storage is expanded by adding cloud storage, the user of the on-premise client device does not need to be aware of this.

[0189] [Second embodiment] Next, the configuration of the cloud storage file control system 1 according to the second embodiment of the present invention will be described with reference to the drawings. Fig. 28 is a diagram showing an example of the configuration of the cloud storage file control system 1 according to the second embodiment of the present invention. In Fig. 28, components with the same reference numerals as those in Figs. 1 and 4 indicate the same components as those in Figs. 1 and 4.

[0190] In the first embodiment of the present invention, the virtual server device 120 constructed on the virtual machine on the cloud 100 moves actual data between the cloud storages (1) 110 and (n) 150. However, it is also possible to configure the parent file server device 240 on the premises 200 to have the functions of the virtual server device 120.

[0191] 28 shows a cloud storage file control system 1 according to a second embodiment of the present invention, which has a configuration in which the file server device (1) 210 according to the first embodiment of the present invention is provided with the functions of the virtual server device 120. Here, the file server device obtained by providing the file server device (1) 210 according to the first embodiment of the present invention with the functions of the virtual server device 120 is called a parent file server device 240.

[0192] In the cloud storage file control system 1 of the second embodiment of the present invention shown in Figure 28, cloud storage (1) 110 on cloud 100 is connected to parent file server device 240, file server device (2) 220, and file server device (n) 230 via network 300, and cloud storages (1) 110 to (n) 150 on cloud 100 are connected to parent file server device 240 via network 300.

[0193] Fig. 29 is a diagram showing an example of the configuration of a parent file server 240 that has the functions of a virtual server according to the second embodiment of the present invention. Referring to Fig. 29, the parent file server 240 has a configuration equivalent to that of the virtual server 120 shown in Fig. 6, in which file filter means 512 is provided.

[0194] The cloud storage file control system 1 of the second embodiment of the present invention shown in FIG. 28, which uses the parent file server device 240 shown in FIG. 29, can perform operations similar to those of the cloud storage file control system 1 of the first embodiment of the present invention.

[0195] Although the embodiments of the present invention have been described above, the present invention is not limited to the above-described embodiments, and further modifications, substitutions, and adjustments can be made without departing from the basic technical concept of the present invention. For example, the network configurations, element configurations, and message expression formats shown in the drawings are examples to aid in understanding the present invention, and the present invention is not limited to the configurations shown in these drawings. Furthermore, in the following description, "A and / or B" means at least either A or B.

[0196] Furthermore, the procedures shown in the first and second embodiments can be realized by a program that causes a computer (9000 in FIG. 30) that functions as the cloud storage file control system 1 of the present invention to realize the functions of the cloud storage file control system 1. Such a computer is exemplified by a configuration that includes a CPU (Central Processing Unit) 9010, a communication interface 9020, a memory 9030, and an auxiliary storage device 9040 in FIG. 30. That is, the cloud storage file control program is executed by the CPU 9010 in FIG. 30, and an update process of each calculation parameter stored in the auxiliary storage device 9040, etc. is performed.

[0197] The memory 9030 is a RAM (Random Access Memory), a ROM (Read Only Memory), or the like.

[0198] That is, each part (processing means, function) of the cloud storage file control system shown in the first and second embodiments can be realized by a computer program that causes the processor of the computer to execute each of the above-mentioned processes using its hardware.

[0199] Finally, preferred embodiments of the present invention will be summarized. [First form] (See the first aspect of cloud storage file control system above.) [Second form] (See the second perspective on cloud storage file control systems above.) [Third Form] The file control system for cloud storage according to the first or second aspect includes: the virtual server device includes a cloud storage monitoring unit, a file exchange unit, and a file processing unit; the first cloud storage includes a dummy file table that manages file movement between the first cloud storage and the second cloud storage; the cloud storage monitoring unit periodically monitors the usage of the first cloud storage, and when the usage of the first cloud storage exceeds a predetermined threshold, notifies the file exchange unit that the threshold has been exceeded; When the file exchange unit receives the notification, it executes the transfer of actual data of the file from the first cloud storage to the second cloud storage; It is preferable that the file processing unit records the ID of the moved file and information about the moved file in the dummy file table. [Fourth Form] The file control system for cloud storage according to the third aspect includes: The first cloud storage further includes a request table; the on-premise file server device acquires the ID of the file to be opened from the dummy file table, and writes the ID of the file to be opened into the request table; It is preferable that the virtual server device periodically monitors the request table and performs a transfer of the open file from the second cloud storage to the first cloud storage based on the ID of the open file written in the request table and the information in the dummy file table. [Fifth Form] The file control system for cloud storage according to the third or fourth aspect includes: The first cloud storage further includes a deletion request table; the on-premise file server device acquires an ID of a file to be deleted from the dummy file table, and writes the ID of the file to be deleted into the deletion request table; It is preferable that the virtual server device periodically monitors the deletion request table and deletes the file to be deleted from the second cloud storage based on the ID of the file to be deleted written in the deletion request table and the information in the dummy file table. [Sixth Form] The cloud storage file control system according to any one of the second to fifth aspects includes: It is preferable that the information about the moved file to be recorded in the dummy file table includes the name of the destination cloud storage, the path where the actual data of the moved file is stored, the original path of the moved file on the first cloud storage, the file name of the moved file, the file size of the moved file, and the time the moved file was moved. [7th form] (See the third aspect of file control in cloud storage above.) [8th form] A seventh aspect of the present invention provides a file control method for cloud storage, wherein the first cloud storage includes a dummy file table that manages file movement between the first cloud storage and the second cloud storage; The virtual server device, periodically monitoring the usage of the first cloud storage, and when the usage of the first cloud storage exceeds a predetermined threshold, notifying the user that the threshold has been exceeded; When the notification is received, executing a transfer of actual data of the file from the first cloud storage to the second cloud storage; It is preferable to include a step of recording the ID of the moved file and information about the moved file in the dummy file table. [9th Form] (See the program for the fourth perspective above) [10th Form] A program according to a ninth aspect includes the first cloud storage including a dummy file table that manages file movement between the first cloud storage and the second cloud storage; A computer provided in the virtual server device, a process of periodically monitoring the usage of the first cloud storage, and notifying the user when the usage of the first cloud storage exceeds a predetermined threshold; When the notification is received, a process of moving actual data of the file from the first cloud storage to the second cloud storage; It is preferable to execute a process of recording the ID of the moved file and information about the moved file in the dummy file table. The seventh and ninth embodiments can be expanded into the third to sixth embodiments in the same manner as the first embodiment.

[0200] The disclosures of the above-mentioned patent documents are incorporated herein by reference. Modifications and adjustments of the embodiments and examples are possible within the scope of the entire disclosure of the present invention (including the scope of the claims), and further based on the basic technical concept thereof. Furthermore, various combinations and selections of the various disclosed elements (including each element of each claim, each element of each embodiment or example, each element of each drawing, etc.) are possible within the scope of the disclosure of the present invention. In other words, the present invention naturally includes various modifications and alterations that would be possible by a person skilled in the art in accordance with the entire disclosure and technical concept, including the scope of the claims. In particular, with regard to the numerical ranges described herein, any numerical value or subrange included within the range should be construed as being specifically described, even if not otherwise specified. [Explanation of symbols]

[0201] 1. Cloud storage file control system 100 Cloud 110 Cloud Storage(1) 112 Dummy File Table 113 Request Table 114 Delete Request Table 120 Virtual Server Device 130 Cloud Storage(2) 140 Cloud Storage(3) 150 cloud storage(n) 200 On-Premise 210~230 File server devices (1)~(n) 215~235 Client devices (1)~(n) 240 Parent file server device 300 Network 500 Storage Unit 510 File Processing Unit 511 File Processing Methods 512 File Filtering Methods 520 File Synchronization Unit 521 File Synchronization Methods 530 Communication Processing Unit 531 Communication Processing Means 600 Cloud Storage Management Department 610 Cloud Storage Monitoring Department 611 Cloud storage usage monitoring method 612 Table Monitoring Means 620 File Exchange Department 621 File Selection Method 622 File Exchange Methods 623 File Deletion Method 630 Storage Department 631 configuration files 640 File Processing Unit 641 File Processing Means 650 File Synchronization Unit 651 File Synchronization Methods 660 Communication Processing Unit 661 Communication Processing Means 701 Settings Table 9000 computers 9010 CPU 9020 Communication Interface 9030 Memory 9040 Auxiliary storage device

Claims

1. a first cloud storage arranged on a cloud, a virtual server device connected to the first cloud storage, and a second cloud storage connected to the virtual server device; A file server device located on-premises; a network connecting the first cloud storage on the cloud and the on-premise file server device; The virtual server device controls file movement between the first cloud storage and the second cloud storage connected to the file server device, the virtual server device includes a cloud storage monitoring unit, a file exchange unit, and a file processing unit; the first cloud storage includes a dummy file table that manages file movement between the first cloud storage and the second cloud storage; the cloud storage monitoring unit periodically monitors the usage of the first cloud storage, and when the usage of the first cloud storage exceeds a predetermined threshold, notifies the file exchange unit that the threshold has been exceeded; When the file exchange unit receives the notification, it executes the transfer of actual data of the file from the first cloud storage to the second cloud storage; the file processing unit records the ID of the moved file and information about the moved file in the dummy file table; The first cloud storage further includes a request table; the on-premise file server device acquires the ID of the file to be opened from the dummy file table, and writes the ID of the file to be opened into the request table; The virtual server device periodically monitors the request table and, based on the ID of the file to be opened written in the request table and the information in the dummy file table, moves the file to be opened from the second cloud storage to the first cloud storage.

2. a first cloud storage and a second cloud storage, both of which are located on a cloud; a file server device including a virtual server device, which is located on-premises; a network that connects the first cloud storage and the second cloud storage on the cloud to the on-premise file server device; A cloud storage file control system, wherein the virtual server device in the file server device controls file movement between the first cloud storage and the second cloud storage connected to the on-premise file server device, the virtual server device includes a cloud storage monitoring unit, a file exchange unit, and a file processing unit; the first cloud storage includes a dummy file table that manages file movement between the first cloud storage and the second cloud storage; the cloud storage monitoring unit periodically monitors the usage of the first cloud storage, and when the usage of the first cloud storage exceeds a predetermined threshold, notifies the file exchange unit that the threshold has been exceeded; When the file exchange unit receives the notification, it executes the transfer of actual data of the file from the first cloud storage to the second cloud storage; the file processing unit records the ID of the moved file and information about the moved file in the dummy file table; The first cloud storage further includes a request table; the on-premise file server device acquires the ID of the file to be opened from the dummy file table, and writes the ID of the file to be opened into the request table; The virtual server device periodically monitors the request table and, based on the ID of the file to be opened written in the request table and the information in the dummy file table, moves the file to be opened from the second cloud storage to the first cloud storage.

3. The first cloud storage further includes a deletion request table; the on-premise file server device acquires an ID of a file to be deleted from the dummy file table, and writes the ID of the file to be deleted into the deletion request table; 3. The cloud storage file control system of claim 1, wherein the virtual server device periodically monitors the deletion request table and deletes the file to be deleted from the second cloud storage based on the ID of the file to be deleted written in the deletion request table and the information in the dummy file table.

4. 4. The cloud storage file control system of claim 1, wherein the information about the moved file that is recorded in the dummy file table includes the name of the destination cloud storage, the path where the actual data of the moved file is saved, the original path of the moved file on the first cloud storage, the file name of the moved file, the file size of the moved file, and the time the moved file was moved.

5. a first cloud storage arranged on a cloud, a virtual server device connected to the first cloud storage, and a second cloud storage connected to the virtual server device; A file server device located on-premises; In a system including a network connecting the first cloud storage on the cloud and the on-premise file server device, a step in which the virtual server device controls file movement between the first cloud storage and the second cloud storage connected to the file server device; the first cloud storage includes a dummy file table that manages file movement between the first cloud storage and the second cloud storage; The virtual server device, periodically monitoring the usage of the first cloud storage, and when the usage of the first cloud storage exceeds a predetermined threshold, notifying the user that the threshold has been exceeded; When the notification is received, executing a transfer of actual data of the file from the first cloud storage to the second cloud storage; a step of recording an ID of the moved file and information about the moved file in the dummy file table; The first cloud storage further includes a request table; The virtual server device, The on-premise file server device acquires the ID of the file to be opened from the dummy file table and writes the ID of the file to be opened into the request table. a step of executing a transfer of the file to be opened from the second cloud storage to the first cloud storage based on the ID of the file to be opened written in the request table and the information in the dummy file table.

6. a first cloud storage arranged on a cloud, a virtual server device connected to the first cloud storage, and a second cloud storage connected to the virtual server device; A file server device located on-premises; In a system including a network connecting the first cloud storage on the cloud and the on-premise file server device, a program that causes a computer provided in the virtual server device to execute a process of controlling file movement between the first cloud storage and the second cloud storage connected to the file server device, the first cloud storage includes a dummy file table that manages file movement between the first cloud storage and the second cloud storage; A computer provided in the virtual server device, a process of periodically monitoring the usage amount of the first cloud storage, and notifying the user when the usage amount of the first cloud storage exceeds a predetermined threshold; When the notification is received, a process of moving actual data of the file from the first cloud storage to the second cloud storage; executes a process of recording the ID of the moved file and information about the moved file in the dummy file table; The first cloud storage further includes a request table; A computer provided in the virtual server device, a process in which the on-premise file server device acquires the ID of the file to be opened from the dummy file table and writes the ID of the file to be opened into the request table; and a process in which the on-premise file server device periodically monitors the request table. A program that executes a process of moving the file to be opened from the second cloud storage to the first cloud storage based on the ID of the file to be opened written in the request table and the information in the dummy file table.

Citation Information

Patent Citations

  • Method and device for virtual unification of plurality of network storages

    JP2004046661A

  • Leveling method for disk residual capacity between virtually unified network storages

    JP2005038368A

  • Network storage system

    JP2006003962A

  • System and method for concealing data when utilizing virtual server

    JP2013003612A

  • Data migration system and data migration method

    JP2013080334A