Remote storage method and system
A data storage method and system comprising: at least one target server that comprises a storage media and configured to run an operating system designated to host data accessible over a data plane (DP) network, at least one initiator server comprises a storage media and configured to run an operating system designated to access and expose a remote resource/s over the data plane (DP) network, and 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 the combined storage medias form a shared drive storage stack, wherein the orchestrator is configured to utilize the CP in order to monitor and inspect the operability and condition of the shared drive storage stack, and further configured to monitor, record and inspect the proper operation of block device/s stored within said shared drive storage stack, wherein the orchestrator is configured to identify a malfunction affecting the shared drive storage stack, and wherein the orchestrator is configured to conduct a non-centralized rebuild procedure by managing a simultaneous and coordinated utilization of at least one operatable remote storage media that form the shared drive storage stack.
1 . A data storage system, comprising:
(i) at least one target server that comprises a direct attached storage media volume and configured to run an operating system on said server designated to host data accessible over a data plane (DP) network using at least one target component,
(ii) at least one initiator server comprises a direct attached storage media volume and configured to run an operating system on said server 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 each of said servers and designated to control a control plane (CP) of said DP network,
wherein the orchestrator is configured to coordinate the at least one target server and the at least one initiator server and conduct a remote device attachment procedure without need for rescan/bus scan.
2 . The system of claim 1 , wherein the orchestrator is configured to locate and pass BUS parameters info from all the servers in the system.
3 . The system of claim 1 , wherein the orchestrator is designated to coordinate the device attachment, setting up the target with specific bus IDs and provide the initiator server with required bus IDs.
4 . The system of claim 1 , wherein the orchestrator is configured to expose a remote device, remove it from the target with specific bus IDs, and instructs the initiator to remove the specific bus IDs device from the operating system.
5 . The system of claim 1 , wherein the orchestrator is designated to remove a volume without the need for a bus scan.
6 . The system of claim 1 , wherein the orchestrator is designated to locate Host Bus Adapters (HBA) address in the at least one target server target ID in the at least one initiator server, and block device name as part of the remote device attachment procedure.
7 . The system of claim 1 , wherein the initiator server further comprises redundant arrays of independent disks (RAID) and 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 a clone.
8 . The system of claim 1 , wherein the orchestrator is configured to only use parts of the media storage/s within the storage system.
9 . 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.
10 . The system of claim 1 , wherein the orchestrator is configured to instruct each server to add a selected spare direct attached storage media to each shared volume.
11 . 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 with valid data.
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 components are configured to be created per network path to the initiator server.
14 . The system of claim 1 , wherein the coordination between the initiator server and the target server is conducted using a CP orchestrator installed on each server.
15 . 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.
16 . 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 direct attached storage media at multiple target 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 direct attached storage media of at least two target servers.
18 . The system of claim 17 , wherein the target 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 one target server that comprises a direct attached storage media volume and configured to run an operating system on said server 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 direct attached storage media volume and configured to run an operating system on said server 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 each of said servers to control a control plane (CP) of said DP network,
wherein the orchestrator is configured to coordinate the at least one target server and the at least one initiator server and conduct a remote device attachment without need for rescan/bus scan.