Consistency group distributed snapshot method and system
A data storage method and system comprising: at least two servers that comprise a storage volume and configured to run an operating system designated to host data accessible and exposable over a data plane (DP) network, at least one orchestrator configured to interact with each of said servers and designated to control a control plane (CP) of said DP network, wherein each server is configured to manage its own DP components, wherein the orchestrator is configured to utilize the CP in order to take at least one consistency group snapshot, and further configured to manage an suspension and resumption in order to provide a consistent snapshotting of the volumes in a particular point in time.
1. A data storage system, comprising:
(i) at least two servers that comprise at least one direct attached storage volume and configured to run an operating system designated to host data accessible and exposable over a data plane (DP) network; and
(ii) at least one orchestrator configured to interact with each of said servers and designated to control a control plane (CP) of said DP network;
wherein each server is configured to manage its own DP components;
wherein the orchestrator is configured to utilize the CP in order to take at least one consistency group snapshot, and further configured to manage an IO suspension and resumption in order to provide a consistent snapshotting of the at least one direct attached storage volume in a particular point in time; and
wherein the orchestrator is designated to utilize a designated portion of the at least one direct attached storage volume by orchestrating storage stack components and a standard storage stack of the operating system embedded within the at least two servers.
2. The system of claim 1 , wherein the orchestrator is configured to back-off from consistency group snapshot process if one of the servers misbehave or timeout.
3. The system of claim 1 , wherein the orchestrator is configured to delete a taken constancy group snapshot.
4. The system of claim 1 , wherein the orchestrator is configured to roll back a taken consistency group snapshot.
5. The system of claim 1 , wherein the orchestrator is configured to schedule consistency group snapshotting.
6. The system of claim 1 , wherein the orchestrator is configured to only use parts of at least one media storage within the storage system.
7. The system of claim 1 , wherein the orchestrator is configured to allocate new hot spare disk from a storage pool in case of failure.
8. The system of claim 1 , wherein the orchestrator is configured to instruct each server to add a selected spare storage media to each storage volume.
9. The system of claim 1 , wherein the orchestrator is configured to add a selected spare disk to the at least one direct attached storage volume.
10. The system of claim 1 , wherein the orchestrator is configured to instruct each server to dismiss a failed disk in each direct attached shared storage volume and rebuilding a new spare drive chunk with valid data.
11. The system of claim 1 , wherein connection between the servers is conducted using a multipath connection.
12. The system of claim 1 , wherein the orchestrator is configured to provide alerts and handle failures for remote block device connection between servers.
13. The system of claim 1 , wherein multiple initiators are configured to be created per network path to each server.
14. The system of claim 1 , wherein coordination between the servers is conducted using a CP orchestrator installed on each server.
15. The system of claim 1 , wherein communication between the servers and the orchestrator is done using a designated software component installed on each of said servers.
16. The system of claim 1 , wherein the server is configured to utilize a redundant array of independent disks (RAID) storage stack component (SSC) configured to provide data redundancy originated from multiple designated portions of the at least one direct attached storage volume at multiple servers.
17. The system of claim 16 , wherein the RAID SSC is configured to provide data redundancy originated from combined multiple initiator paths originated from the designated portion of the at least one direct attached storage volume of at least two servers.
18. The system of claim 17 , wherein the servers are located at different locations and wherein the orchestration is allocated across different resiliency domains.
19. The system of claim 18 , wherein the orchestration allocated while considering different resiliency domains also considers maintaining system balance.
20. A method for orchestrating and storing data, comprising:
(i) enabling at least two servers that comprise at least one direct attached storage volume and configured to run an operating system to host data accessible and exposable over a data plane (DP) network; and
(ii) enabling at least one orchestrator to interact with each of said servers to control a control plane (CP) of said DP network;
wherein each server is configured to manage its own DP components;
wherein the orchestrator is configured to utilize the CP in order to take at least one consistency group snapshot, and further configured to manage an IO suspension and resumption in order to provide a consistent snapshotting of the at least one direct attached storage volume in a particular point in time; and
wherein the orchestrator is designated to utilize a designated portion of the at least one direct attached storage volume by orchestrating storage stack components and standard storage stack of the operating system embedded within the at least two servers.