System and Method for Sharing Storage Devices over a Network

• US 20090222509A1
• Filed: 02/29/2008
• Published: 09/03/2009
• Est. Priority Date: 02/29/2008
• Status: Abandoned Application

• Current Assignee: Konica Minolta Business Technologies Incorporated (Konica Minolta Inc.)
• Original Assignee: Konica Minolta Business Technologies Incorporated (Konica Minolta Inc.)
• Inventors: Christ, Randy, King, Chao
• Application Number:
  US12/040,561
• Publication Number:
  US 20090222509A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 11/1666 where the redundant component is memory or memory area
• CPC Class Codes: G06F 11/2097 maintaining the standby controller/processing unit updated initialisation or re-synchronisation thereof G06F11/1658 and subgroups
• CPC Class Codes: G06F 16/182 Distributed file systems
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Abstract

A distributed data sharing system provides storage areas for network clients. Files are written in such a manner that user data is protected and/or so that the network can make use of any available space at a network when saving files.

Claims

1. A method for data storage of a file among at least a network node A and B using an application including a client-side portion residing at a client node and server-side portion residing at a server node, the file residing at the client node and the client node configurable for separate communication links with each of the server node, node A, and node B, comprising the steps of:

the client accessing storage space at the server node after the server recognizes the client as a client of the server;

writing a first data segment of the file to node A and a second data segment of the file to node B, including the steps of;

choosing node A and node B for storage of the first and second data segments, respectively,

generating a segment A filename for the first data segment and a segment B filename for the second data segment, and

the client writing Segment A to node A and Segment B to node B; and

after writing segment A and B, the server saving a map that enables the re-assembly of the file from the first and second data segments.

2. The method of claim 1, wherein the client writing step occurs over a communication link with each of nodes A and B and independent of the server.

3. The method of claim 1, further including the client assigning file names for Segments A and B such that no portion or the logical name of the segment files are relatable to a portion of the logical name of the file.

4. The method of claim 3, wherein the non-relatable file names are generated from a random number.

5. The method of claim 4, wherein the client is adapted for performing at least one of the steps of receiving the logical names from the server and generating the logical names from a random number.

6. The method of claim 1, further including the server selecting nodes A and B based on a node-selection algorithm and recommending nodes A and B to the client.

7. The method of claim 6, wherein the node-selection algorithm selects nodes A and B based on at least one of the following criteria:

the level of network traffic at a node, the number of packets errors per transmission to/from a node, the type of storage medium at the node, and the type of communication link between the client node and node.

8. The method of claim 1, further including the server assigning a node score to each of the nodes A and B and the client selecting A and B based on each of the nodes exceeding a threshold node score reflecting a capability for the node to receive the data compared to other nodes over the network.

9. The method of claim 1, further including the client erasing the map after the segment A and segment B data is written to nodes A and B, respectively, and wherein the map relates the data in Segment A and Segment B to the relative locations of the data in the file, and the location of the segment A and segment B on the network, such that the map is needed to form the file from the data in the segment A and segment B files.

10. The method of claim 1, wherein the saving of the map step includes at least one of encrypting the map contents at the server node, and storing the map in a client only, password-protected location at the server node.

11. The method of claim 1, wherein the map includes the segment A and B filenames, the location of nodes A and B, information identifying the client node, and meta data.

12. The method of claim 1, wherein the client node is configurable for separate communication links with a plurality of nodes, including at least the server node, and nodes A and B, further comprising the steps of:

the client requesting from the server the available nodes for data storage and then receiving from the server the availability of the plurality of nodes,

the client segmenting the file into Segments A and B based on the availability of nodes A and B, and

the client writing Segments A and B to the respective nodes A and B, and a copy of the Segment A to a different one of the available plurality of nodes.

13. The method of claim 12, wherein the client node includes an application resident at the client node, wherein the application requests the file, such that if the segment A is not accessible to the client node, the map directs the client to select the copy of segment A from the different one of the available plurality of nodes, and the application reading the copy of segment A.

14. A file storing method for storing a file over a network having a plurality of storage devices at network nodes, the file containing real data, comprising the steps of:

partitioning the real data into a plurality of real data segments;

generating a random filename for each one of the real data segments;

associating each of the real data segments with its respective randomly generated filename; and

storing each of the real data segments on one of the plurality of storage devices.

15. The method of claim 14, wherein the storing step includes storing the metadata needed to reconstruct the file from the data segments at a restricted node on the network, accessible to only the owner of the file.

16. The method of claim 14, wherein the storing step includes storing the real data segments in an order such that no data segment on a node can provide information about the type of information communicated by the data contained in the file.

17. The method of claim 14, wherein the real data segments are partitioned from the file according to a sequential order according to their relative byte locations in the file, and the real data segments are stored on one or more of the plurality of nodes one of a random, intermittent or non-sequential order.

18. The method of claim 14, wherein each of the partitioning, generating, associating and storing steps are carried out by accessing a local filesystem managed by a local operating system.

19. A computer network, comprising

a client node wherein the client is the owner of a file;

a plurality of nodes, each node including a storage space accessible by way of a first communication link comprising communication links between each of the nodes and the client node;

a plurality of data segments, wherein one or more of the data segments are stored on each of the plurality of storage spaces;

a server node having a storage wherein only the server storage has a map enabling the re-assembly of the file from the data segments, and

a second communication link between the client and the server such that the client is enabled for accessing the information needed to re-assemble the file when the client wishes to re-assemble the file from the data segments.

20. The computer network of claim 19, wherein the file is associated with source data comprising the plurality of data segments, further including:

a plurality of redundant data segments stored at one or more of the plurality of storage spaces, such that no copy of a data segment is located at the same node as the respective data segment.

21. A method for a computer to access data associated with a user'"'"'s file, the data being stored as a plurality of data segments distributed over a network having nodes, and as a plurality of copies of the data segments over the nodes, comprising the steps of

the computer requesting from a network node the locations of the data segments and copies of data segments;

the computer accessing a node in order to retrieve a data segment;

if the node is inaccessible, accessing a different node where a copy of the segment is stored; and

repeating the accessing the copy of the segment at a different node step until a copy of the segment is accessible to the computer.

22. Server software residing on a storage medium, comprising:

a first portion for selecting a plurality of network nodes for storing data portions over a network, wherein data in a source file comprises the data portions;

a second portion for selecting a filename for each of the data portions;

a third portion for storing the relationship between the filenames and the nodes where the data portions reside, and the relationship between the data portions and the data in the source file in a map file; and

a fourth portion for limiting access to the map file to only the owner of the source file.

23. The server software of claim 22, further comprising a server part and a client part, the server part comprising the first, second, third, fourth and fifth portions, and

the client portion being downloadable over a network by a node designated as a client node, and

each of the server and client parts being adapted to run as applications through an interface provided by a local operating system.

24. Client software residing on a storage medium, comprising:

a first portion for selecting a number of data segments for writing data from a source file, the data comprising the data segments;

a second portion for receiving filenames for each of the data segments, and the nodes over a network for storing each of the data segments;

a third portion for writing the data segments to a plurality of nodes using a communication link between a computer where the client software resides and each of the respective nodes;

a fourth portion for communicating the relationship between the filenames and the nodes where the data portions reside, and the relationship between the data portions and the data in the source file; and

a fifth portion for gaining access to a map file on a network node, the map file containing the communicated relationship between the filenames and the nodes where the data portions reside, and the relationship between the data portions and the data in the source file.

25. The client software of claim 24, wherein the fourth portion includes a client password and node identification information for gaining access to the map file, and the fourth portion includes a component for removing the information residing in the map file after all data portions have been successfully written and the relationships communicated to another computer.