System and method for storing a data file backup
A method for storing a data file copy is provided. The method includes the steps of: (a) dividing a duplicate of a data file stored in a mother node into a plurality of data pieces and storing each data piece in a child node of the mother node; (b) determining whether the data file in the mother node is destroyed when accessed by a user; and (c) merging all the data pieces stored in the child nodes to rebuild the data file, if the data file is destroyed. A related system is also disclosed.
1. A system for storing a data file backup, the system comprising at least one server, the server comprising a configuration file and a data file accessing module, wherein the configuration file specifies identification and addresses of child nodes of the server, the data file accessing module is configured for dividing a duplicate of a data file stored in the server into a plurality of data pieces, storing the data pieces into the child nodes, and merging the data pieces in the child nodes according to the configuration file, so as to rebuild the data file upon the condition that the data file has been destroyed.
2. The system as claimed in claim 1 , wherein the child nodes are different storage spaces in the server.
3. The system as claimed in claim 1 , wherein the child nodes are different storage spaces in different servers.
4. A computer-based method for storing a data file backup, comprising the steps of:
dividing a duplicate of a data file stored in a mother node into a plurality of data pieces and storing each of the data pieces in a corresponding child node of the mother node according to a configuration file of the mother node, wherein the configuration file specifies identification and addresses of the child nodes of the mother node;
determining whether the data file in the mother node has been destroyed when accessed by a user; and
merging all the data pieces stored in the child nodes to rebuild the data file according to the configuration file, upon the condition that the data file has been destroyed.
5. The method as claimed in claim 4 , wherein the dividing and storing step comprises the steps of:
(a) storing the data file in the mother node through an application programming interface;
(b) obtaining an initial checksum of the data file through the application programming interface;
(c) determining whether the mother node has child nodes;
(d) dividing a duplicate of the data file into a plurality of data pieces, if the mother node has child nodes;
(e) storing each data piece in a corresponding child node through the application interface; and
(f) repeating the steps (b) to (e) to each child node.
6. The method as claimed in claim 5 , wherein the merging step comprises the steps of:
(j) determining whether the mother node in which the data file is stored has child nodes;
(k) obtaining a current checksum of each data piece in each child node through the application programming interface, if the mother node has child nodes;
(l) determining whether the current checksum of each data piece is identical with a corresponding initial checksum of the data piece; and
(m) merging all the data pieces to rebuild the destroyed data file, if the current checksum of each data piece is identical with its initial checksum.
7. The method as claimed in claim 6 , wherein the merging step further comprises the step of:
returning to the step (j), if the current checksum of any data piece is different from its initial checksum.
8. The method as claimed in claim 6 , further comprising the step of:
displaying exception through the application programming interface, if the mother node in which the data file is stored has no child nodes.