Remote online volume cloning method and system
Cloning a volume from one source server to another destination server over a network, while the volume is online and orchestrator is configured to orchestrate the clone process over a CP to both servers and only the allocated blocks in the source volume, that belongs to server, are copied.
1 . A data storage system, comprising:
(i) at least one target server that comprises a storage media volume and configured to run an operating system designated to host data accessible over a data plane (DP) network using at least one target component,
(ii) at least one initiator server comprising a storage media volume and configured to run an operating system designated to access and expose stored data over the data plane (DP) network using at least one initiator component, and
(iii) at least one orchestrator configured to interact with the at least one target server and the at least one initiator server and designated to control a control plane (CP) of said DP network,
wherein the orchestrator is configured to create a data snapshot of the volume stored in the target server,
wherein the data snapshot is configured to be exposed to the initiator server through the initiator component,
wherein a clone of the volume of the target server is configured to be created on the volume of the initiator server, and
wherein the initiator server further comprises redundant arrays of independent disks (RAID), wherein allocated chunks are configured to pass through the CP to the orchestrator and then be sent to the volume and RAID of the initiator server in order to create the clone.
2 . The system of claim 1 , wherein the RAID is used to utilize in-kernel, zero copy procedure in order to create the clone.
3 . The system of claim 1 , wherein a controller is configured to delete components used to create the clone after creation of said clone.
4 . The system of claim 1 , wherein the orchestrator is configured to only use parts of storage media volume within the storage system.
5 . The system of claim 1 , wherein the orchestrator is configured to allocate new hot spare disk from a storage pool of the servers in case of failure.
6 . The system of claim 1 , wherein the orchestrator is configured to instruct each server to add a selected spare storage media to each shared volume.
7 . The system of claim 1 , wherein the orchestrator is configured to add a selected spare disk to each shared volume.
8 . The system of claim 1 , wherein the orchestrator is configured to instruct each server to dismiss a failed disk in each shared volume and rebuilding new spare drive chunk(s) with valid data.
9 . The system of claim 1 , wherein connection between the servers is conducted using a multipath connection.
10 . The system of claim 1 , wherein the orchestrator is configured to provide alerts and handle failures for remote block device connection between servers.
11 . The system of claim 1 , wherein multiple initiators components are configured to be created per network path to the initiator server.
12 . The system of claim 1 , wherein coordination between the initiator server and the target server is conducted using a CP orchestrator installed on each server.
13 . The system of claim 1 , wherein communication between either a target or initiator server accessible via the DP network and the orchestrator is done using a designated software component installed on each of said servers.
14 . The system of claim 1 , wherein the initiator 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 storage media at multiple target servers.
15 . The system of claim 14 , wherein the RAID SSC is configured to provide data redundancy originated from combined multiple initiator paths originated from the designated portion of the storage media of at least two target servers.
16 . The system of claim 15 , wherein the target servers are located at different locations and wherein the orchestration is allocated across different resiliency domains.
17 . The system of claim 16 , wherein the orchestration allocated while considering different resiliency domains also considers maintaining system balance.
18 . The system of claim 1 , wherein the orchestrator is configured to interact with the server using an administration protocol.
19 . A method for orchestrating and storing data, comprising:
(i) enabling at least one target server that comprises a storage media volume and configured to run an operating system to host data accessible over a data plane (DP) network using at least one target component,
(ii) enabling at least one initiator server that comprises a storage media volume and configured to run an operating system to access and expose a remote resource/s over the data plane (DP) network using at least one initiator component, and
(iii) enabling at least one orchestrator configured to interact with the at least one target server and the at least one initiator server to control a control plane (CP) of said DP network,
wherein the orchestrator is configured to create a data snapshot of the volume stored in the target server,
wherein the data snapshot is configured to be exposed to the initiator server through the initiator component,
wherein a clone of the volume of the target server is configured to be created on the volume of the initiator server, and
wherein the initiator server further comprises RAID, wherein allocated chunks are configured to pass through the CP to the orchestrator and then be sent to the volume and RAID of the initiator server in order to create the clone.