Storage Replication Method and System
A data storage method and system comprising: at least two servers that comprise a RAID storage volume and configured to run an operating system designated to host data accessible and exposable over a data plane (DP) network, wherein the servers are located remotely from each other, and wherein the RAID 1 is configured to be utilized for a remote replication procedure while connecting the two volumes of the at least two servers.
1 . A data storage system, comprising:
at least two servers that comprise a RAID 1 storage volume and configured to run an operating system designated to host data accessible and exposable over a data plane (DP) network,
wherein the servers are located remotely from each other, and
wherein the RAID 1 is configured to be utilized for a remote replication procedure while connecting the two volumes of the at least two servers.
2 . The system of claim 1 , configured to conduct a remote synchronous replication, using a resync bitmap of RAID 1.
3 . The system of claim 1 , configured to conduct a remote asynchronous replication, using a combination of LVM snapshot and RAID 1 components and by Connecting one local volume snapshot and a remote volume snapshot via the DP network.
4 . The system of claim 3 , configured to track changes from last asynchronous replication using LVM snapshot delta metadata or change tracking information.
5 . The system of claim 3 , configured to change list into RAID 1 bitmap, to replicate only the changes from last async operation.
6 . The system of claim 1 , further comprising at least one orchestrator configured to interact with each of said server and designated to control a control plane (CP) of said DP network.
7 . The system of claim 6 , wherein the orchestrator is configured to only use parts of the media storage/s within the storage system.
8 . The system of claim 6 , wherein the orchestrator is configured to allocate new hot spare disk from a storage pool in case of failure.
9 . The system of claim 6 , wherein the orchestrator is configured to instruct each server to add a selected spare storage media to each storage volume.
10 . The system of claim 6 , wherein the orchestrator is configured to add a selected spare disk to the shared storage volume.
11 . The system of claim 6 , wherein the orchestrator is configured to instruct each server to dismiss a failed disk in each shared storage volume and rebuilding the new spare drive chunk with valid data.
12 . The system of claim 1 , wherein the connection between the servers is conducted using a multipath connection.
13 . The system of claim 6 , wherein the orchestrator is configured to provide alerts and handle failures for remote block device connection between servers.
14 . The system of claim 1 , wherein multiple initiators are configured to be created per network path to each server.
15 . The system of claim 1 , wherein the coordination between the servers is conducted using a CP orchestrator installed on each server.
16 . The system of claim 6 , wherein the communication between the servers and the orchestrator is done using a designated software component installed on each of said servers.
17 . 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 storage volume at multiple servers.
18 . The system of claim 17 , wherein the RAID SSC is configured to provide data redundancy originated from combined multiple initiator paths originated from the designated portion of the storage volume of at least two servers.
19 . The system of claim 18 , wherein the servers are located at different locations and wherein the orchestration is allocated across different resiliency domains.
20 . The system of claim 19 , wherein the orchestration allocated while considering different resiliency domains also considers maintaining system balance.
21 . The system of claim 6 , wherein the orchestrator is configured to interact with the servers using an administration protocol.
22 . The system of claim 1 , wherein a designated portion of the storage volume is allocated using a logical volume manager (LVM) SSC.
23 . The system of claim 1 , wherein the storage volume is solid-state drive (SSD) based.
24 . The system of claim 1 , wherein the storage volume is storage class memory (SCM) based.
25 . The system of claim 1 , wherein the storage volume is random access memory (RAM) based.
26 . The system of claim 1 , wherein the storage volume is hard disk drive (HHD) based.
27 . The system of claim 6 , wherein the orchestrator is a physical controller.
28 . The system of claim 6 , wherein the orchestrator is a cloud-based service (SaaS).
29 . The system of claim 1 , wherein the operations on each server may be implemented, wholly or partially, by a data processing unit (DPU).
30 . A method for orchestrating and storing data, comprising the steps of:
(i) enabling at least two servers that comprise a RAID 1 storage volume and configured to run an operating system to host data accessible and exposable over a data plane (DP) network,
wherein the servers are located remotely from each other, and
wherein the RAID 1 is configured to be utilized for a remote replication procedure while connecting the two volumes of the at least two servers.