Synchronization storage solution after an offline event

1. A method for synchronizing a source server and a target server after an offline event at the source server, the method comprising:

determining an offline event at a source server, wherein the source server and a target server were in a replication relationship prior to the offline event at the source server;

retrieving, from the source server, a list of snapshots;

determining a common snapshot between the source server and the target server;

promoting the target server to new source server, such that the target server receives new write requests subsequent to the offline event and registers the new write requests in a clone of the common snapshot, thereby generating an updating common snapshot clone;

in response to the source server coming back online, identifying un-replicated data that was written to the source server prior to the offline event but was not written to the common snapshot or replicated to the target server;

generating a delta sync snapshot from the updated common snapshot clone generated by the target server and the un-replicated data from the source server;

reverting the source server to the common snapshot; and

replicating the delta sync snapshot from the target server to the source server, such that the target server, acting as new source server, is in a synchronized replication relationship with the source server, acting as new target server.

2. The method of claim 1 , further comprising, in response to determining that the common snapshot could not be located, initiating a full synchronization of the source server and the target server.

3. The method of claim 1 , further comprising:

in response to the source server being online, subsequent the offline event, determining existence of a writable clone; and

in response to the writable clone existing, performing a file update.

4. The method of claim 1 , further comprising:

building a file list, from the source server, subsequent the common snapshot.

5. The method of claim 4 , wherein the file list comprises at least one of:

files modified on the source server and target server;

files modified on the source server and unmodified on target server;

files modified on the source server and do not exist on target server; and

files modified on the source server and unmodified and locked on the target server.

6. The method of claim 4 , further comprising:

processing the file list;

generating a report based on the processing; and

transmitting an alert comprising the report.

7. A system for synchronizing a source server and a target server after an offline event at the source server, the system comprising:

a processor; and

a memory storing instructions which when executed by the processor cause the processor to:

determine an offline event at a source server, wherein the source server and a target server were in a replication relationship prior to the offline event at the source server;

retrieve, from the source server, a list of snapshots;

determine a common snapshot between the source server and the target server;

promote the target server to new source server, such that the target server receives new write requests subsequent to the offline event and registers the new write requests in a clone of the common snapshot, thereby generating an updating common snapshot clone;

in response to the source server coming back online, identify un-replicated data that was written to the source server prior to the offline event but was not written to the common snapshot or replicated to the target server;

generate a delta sync snapshot from the updated common snapshot clone generated by the target server and the un-replicated data from the source server;

revert the source server to the common snapshot; and

replicate the delta sync snapshot from the target server to the source server, such that the target server, acting as new source server, is in a synchronized replication relationship with the source server, acting as new target server.

8. The system of claim 7 , wherein the instructions further cause the processor to initiate a full synchronization of the source server and the target server in response to determining that the common snapshot could not be located.

9. The system of claim 8 , comprising further instructions which when executed cause the processor to:

in response to the source server being online, subsequent the offline event, determine the existence of a writable clone; and

in response to the writeable clone existing, perform a file update.

10. The system of claim 7 , wherein the file update comprises:

building a file list, from the source server, subsequent the common snapshot.

11. The system of claim 10 , wherein the file list comprises at least one of:

files modified on the source server and target server;

files modified on the source server and unmodified on target server;

files modified on the source server and do not exist on target server; and

files modified on the source server and unmodified and locked on the target server.

12. The system of claim 10 , comprising further instructions which when executed cause the processor to:

process the file list;

generate a report based on the processing; and

transmit an alert comprising the report.

13. A non-transitory computer readable medium storing instructions which when executed by a processor cause the processor to:

determine an offline event at a source server, wherein the source server and a target server were in a replication relationship prior to the offline event at the source server;

retrieve, from the source server, a list of snapshots;

determine a common snapshot between the source server and the target server;

promote the target server to new source server, such that the target server receives new write requests subsequent to the offline event and registers the new write requests in a clone of the common snapshot, thereby generating an updating common snapshot clone;

in response to the source server coming back online, identify un-replicated data that was written to the source server prior to the offline event but was not written to the common snapshot or replicated to the target server;

generate a delta sync snapshot from the updated common snapshot clone generated by the target server and the un-replicated data from the source server;

revert the source server to the common snapshot; and

replicate the delta sync snapshot from the target server to the source server, such that the target server, acting as a new source server, is in a synchronized replication relationship with the source server, acting as a new target server.

14. The non-transitory computer readable medium of claim 13 , wherein when the common snapshot is not located the instructions cause the processor to initiate a full synchronization of the source server and the target server.

15. The non-transitory computer readable medium of claim 13 , comprising further instructions which when executed cause the processor to:

in response to the source server being online, subsequent the offline event, determine existence of a writable clone; and

in response to the writable clone existing, perform a file update.

16. The non-transitory computer readable medium of claim 13 , wherein the file update comprises:

building a file list, from the source server, subsequent the common snapshot.

17. The non-transitory computer readable medium of claim 16 , wherein the file list comprises at least one of:

files modified on the source server and target server;

files modified on the source server and unmodified on target server;

files modified on the source server and do not exist on target server; and

files modified on the source server and unmodified and locked on the target server.

18. The non-transitory computer readable medium of claim 16 , comprising further instructions which when executed cause the processor to:

process the file list;

generate a report based on the processing; and

transmit an alert comprising the report.