Distributed disaster recovery file sync server system
View Patent ↗Example implementations are directed to restoration of data not only from the servers, but also from the clients connected to the server. Algorithms are incorporated to identify content that was created or modified after the last backup. This algorithm also identifies and resolves changes in the mount points for shared folders, preventing information leakage. When the server recovers from a failure, it notifies the clients about the recovery on their next connection. Each client then determines the current state of its mount points and file paths and compares them with the server's mount points and file paths. After the comparison, the client comprehends and indicates the mount point differences by renaming them and sends entire local data (all files, folders, mount points) to the server. The server reconciles the differences.
1. A server comprising:
an interface configured to interface with a plurality of client devices;
a memory configured to store information regarding a version of a first file managed by the server at a recovery point, and
a processor configured to:
receive a plurality of files from the plurality of client devices to recover files in the server by using the plurality of files in the plurality of client devices, and
for a second file of the plurality of received files having a newer version than the version of the first file at the recovery point, manage the second file as a new version of the first file.
2. The server of claim 1 , wherein the processor is further configured to receive one or more updates to the first file from one of the plurality of client devices while receiving a plurality of files from the plurality of client devices to recover files in the server, wherein the one or more updates to the first file is stored as a conflict file for the one or more updates having a same version as the new version of the first file.
3. The server of claim 1 , wherein the processor is further configured to receive one or more updates to the first file from one of the plurality of client devices while receiving a plurality of files from the plurality of client devices to recover files in the server, wherein the one or more updates to the first file is stored as a conflict file for the one or more updates having:
a different version from the new version of the first file; and
a version that is not newer than the version of the first file.
4. The server of claim 1 , wherein the processor is configured to:
store ones of the plurality of files as a new file for the ones of the plurality of files that do not have a corresponding one of the files in the server; and
store updates as a new file for ones of the updates do not have a corresponding one of the files in the server.
5. The server of claim 1 , wherein the processor is configured to:
receive one or more updates to the first file from one of the plurality of client devices while receiving a plurality of files from the plurality of client devices to recover files in the server, wherein the one or more updates to the first file is used to update the first file before the second file is managed as the new version of the first file.
6. The server of claim 1 , wherein the processor is configured to:
discard received ones of the plurality of files from the plurality of client devices having a corresponding one of the files in the server that is a newer version than the received ones.
7. The server of claim 1 , wherein the processor is further configured to, for a third file of the plurality of received files having a newer version than the version of the first file at the recovery point, manage the third file as a conflict file to the second file.
8. A method for managing a server, comprising:
storing information regarding a version of a first file managed by the server at a recovery point,
receiving a plurality of files from the plurality of client devices to recover files in the server by using the plurality of files in the plurality of client devices,
for a second file of the plurality of received files having a newer version than the version of the first file at the recovery point, managing the second file as a new version of the first file.
9. The method of claim 8 , further comprising receiving one or more updates to the first file from one of the plurality of client devices while receiving a plurality of files from the plurality of client devices to recover files in the server, wherein the one or more updates to the first file is stored as a conflict file for the one or more updates having a same version as the new version of the first file.
10. The method of claim 8 , further comprising receiving one or more updates to the first file from one of the plurality of client devices while receiving a plurality of files from the plurality of client devices to recover files in the server, wherein the one or more updates to the first file is stored as a conflict file for the one or more updates having:
a different version from the new version of the first file; and
a version that is not newer than the version of the first file.
11. The method of claim 8 , further comprising storing ones of the plurality of files as a new file for the ones of the plurality of files that do not have a corresponding one of the files in the server; and storing updates as a new file for ones of the updates do not have a corresponding one of the files in the server.
12. The method of claim 8 , further comprising receiving one or more updates to the first file from one of the plurality of client devices while receiving a plurality of files from the plurality of client devices to recover files in the server, wherein the one or more updates to the first file is used to update the first file before the second file is managed as the new version of the first file.
13. The method of claim 8 , further comprising discarding received ones of the plurality of files from the plurality of client devices having a corresponding one of the files in the server that is a newer version than the received ones.
14. The method of claim 8 , further comprising, for a third file of the plurality of received files having a newer version than the version of the first file at the recovery point, managing the third file as a conflict file to the second file.