IP Library › Granted Patent US 12,443,498
Granted Patent B2
US 12,443,498 · App. 18/273,230 · Granted Oct 14, 2025

Shared drive storage stack monitoring and recovery method and system

Inventor: Jonathan Amit (Omer, IL)
Assignee: VOLUMEZ TECHNOLOGIES LTD.
G06F3/0614G06F3/061G06F3/0619G06F3/0622G06F3/0631G06F3/064G06F3/065G06F3/0655G06F3/0665G06F3/067G06F3/0689G06F9/505G06F11/1076G06F11/1092G06F11/1464G06F11/1469G06F11/1662G06F11/2082G06F11/2087G06F11/2092G06F11/2094G06F16/128G06F16/178G06F16/1873H04L9/0822H04L41/0659H04L67/1095H04L67/1097G06F2201/85
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,443,498
App. No.
18/273,230
Granted
Oct 14, 2025
Kind
B2
Abstract

A data storage system and method 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.

Claims (34)

1. A data storage system, comprising:

(i) at least one target server that comprises a non-transitory storage media and configured to run an operating system designated to host data accessible over a data plane (DP) network;

(ii) at least one initiator server comprises a storage media and configured to run an operating system designated to access and expose at least one remote resource over the data plane (DP) network; 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 storage media of each of the at least one target server combined form a shared drive storage stack;

wherein the orchestrator is configured to utilize the CP in order to monitor and inspect operability and condition of the shared drive storage stack, and further configured to monitor, record and inspect proper operation of at least one block device 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, available and unexploited direct attached remote storage media that form the shared drive storage stack.

2. The system of claim 1 , wherein the shared drive storage stack comprises RAID components.

3. The system of claim 1 , wherein the orchestrator is configured to only use parts of at least one media storage within the storage system.

4. The system of claim 1 , wherein the orchestrator is configured to allocate new hot spare disk from a storage pool in case of failure.

5. The system of claim 1 , wherein the orchestrator is configured to instruct each server to add a selected spare storage media to each shared drive storage stack.

6. The system of claim 1 , wherein the orchestrator is configured to add a selected spare disk to the shared drive storage stack.

7. The system of claim 1 , wherein the orchestrator is configured to instruct each server to dismiss a failed disk in each shared drive storage stack and rebuilding new spare drive chunk with valid data.

8. The system of claim 1 , wherein connection between the servers is conducted using a multipath connection.

9. The system of claim 1 , wherein the orchestrator is configured to provide alerts and handle failures for remote block device connection between servers.

10. The system of claim 1 , wherein multiple initiators are configured to be created per network path to the initiator server.

11. The system of claim 1 , wherein the orchestrator is configured to identify a block device name on the remote server and on a local server, using information from the target 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 a designated portion of the storage media is allocated using a logical volume manager (LVM) SSC.

19. The system of claim 1 , wherein operations on each server may be implemented, wholly or partially, by a data processing unit (DPU).

20. A method for orchestrating and storing data, comprising steps of:

(i) enabling at least one target server that comprises a non-transitory storage media and configured to run an operating system to host data accessible over a data plane (DP) network;

(ii) enabling at least one initiator server configured to run an operating system to access and expose at least one remote resource over the data plane (DP) network; 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 storage media of each of the at least one target server combined form a shared drive storage stack;

wherein the orchestrator is configured to utilize the CP in order to monitor and inspect operability and condition of the shared drive storage stack, and further configured to monitor, record and inspect proper operation of at least one block device 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, available and unexploited direct attached remote storage media that form the shared drive storage stack.

Assignments (2)
SECURITY INTEREST Recorded May 12, 2026
From: VOLUMEZ TECHNOLOGIES LTD.
To: BANK HAPOALIM B.M.
Reel/Frame 074630/0594 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 8, 2023
From: AMIT, JONATHAN
To: VOLUMEZ TECHNOLOGIES, LTD.
Reel/Frame 065495/0517 →
Continuity (16)
Provisional Application 63141263 · Jan 25, 2021
Provisional Application 63141267 · Jan 25, 2021
Provisional Application 63141151 · Jan 25, 2021
Provisional Application 63141194 · Jan 25, 2021
Provisional Application 63141205 · Jan 25, 2021
Provisional Application 63141155 · Jan 25, 2021
Provisional Application 63141139 · Jan 25, 2021
Provisional Application 63141213 · Jan 25, 2021
Provisional Application 63141236 · Jan 25, 2021
Provisional Application 63141257 · Jan 25, 2021
Provisional Application 63141179 · Jan 25, 2021
Provisional Application 63141133 · Jan 25, 2021
Provisional Application 63141227 · Jan 25, 2021
Provisional Application 63141245 · Jan 25, 2021
Provisional Application 63141162 · Jan 25, 2021
Related Publication 20240143209A1 · May 2, 2024
References Cited (134)
US 5721840A · Soga · 1998 [cited by applicant]
US 6714980B1 · Markson et al. · 2004 [cited by applicant]
US 7111084B2 · Tan et al. · 2006 [cited by applicant]
US 7313724B1 · Kekre et al. · 2007 [cited by applicant]
US 7334095B1 · Fair et al. · 2008 [cited by applicant]
US 8046548B1 · Chatterjee et al. · 2011 [cited by applicant]
US 8423733B1 · Ozdemir · 2013 [cited by applicant]
US 8743872B2 · Chidambaram et al. · 2014 [cited by applicant]
US 8751533B1 · Dhavale et al. · 2014 [cited by applicant]
US 8848727B2 · Saraiya et al. · 2014 [cited by applicant]
US 9112890B1 · Ori · 2015 [cited by applicant]
US 9405483B1 · Wei et al. · 2016 [cited by applicant]
US 9436716B2 · Starovoitov et al. · 2016 [cited by applicant]
US 9489150B2 · Aszmann et al. · 2016 [cited by applicant]
US 9613046B1 · Xu et al. · 2017 [cited by applicant]
US 9881014B1 · Bono et al. · 2018 [cited by applicant]
US 10210048B2 · Sancheti · 2019 [cited by applicant]
US 10365978B1 · Whitney et al. · 2019 [cited by applicant]
US 10460110B1 · Allo et al. · 2019 [cited by applicant]
US 10628058B1 · Riley et al. · 2020 [cited by applicant]
US 10642779B2 · Zhu et al. · 2020 [cited by applicant]
US 10782997B1 · Krishna Murthy et al. · 2020 [cited by applicant]
US 11461109B1 · Krasilnikov et al. · 2022 [cited by applicant]
US 20040024962A1 · Chatterjee et al. · 2004 [cited by applicant]
US 20050050271A1 · Honda et al. · 2005 [cited by applicant]
US 20050074003A1 · Ball et al. · 2005 [cited by applicant]
US 20050240792A1 · Sicola et al. · 2005 [cited by applicant]
US 20050256961A1 · Alon et al. · 2005 [cited by applicant]
US 20060085607A1 · Haruma · 2006 [cited by applicant]
US 20070239944A1 · Rupanagunta et al. · 2007 [cited by applicant]
US 20080049276A1 · Abe · 2008 [cited by applicant]
US 20080162817A1 · Batterywala · 2008 [cited by applicant]
US 20090132617A1 · Soran et al. · 2009 [cited by applicant]
US 20090265510A1 · Walther et al. · 2009 [cited by applicant]
US 20100115008A1 · Nakatani et al. · 2010 [cited by applicant]
US 20100199042A1 · Bates et al. · 2010 [cited by applicant]
US 20100250748A1 · Sivasubramanian et al. · 2010 [cited by applicant]
US 20110246423A1 · Jess · 2011 [cited by applicant]
US 20110296102A1 · Nishihara et al. · 2011 [cited by applicant]
US 20120079318A1 · Colgrove et al. · 2012 [cited by applicant]
US 20120110252A1 · McKean · 2012 [cited by applicant]
US 20120117241A1 · Witt et al. · 2012 [cited by applicant]
US 20120147888A1 · Lu et al. · 2012 [cited by applicant]
US 20140047040A1 · Patiejunas et al. · 2014 [cited by applicant]
US 20140115162A1 · Kalyanaraman et al. · 2014 [cited by applicant]
US 20140215147A1 · Pan · 2014 [cited by applicant]
US 20140229675A1 · Aizman et al. · 2014 [cited by applicant]
US 20150006665A1 · Krishnamurthy et al. · 2015 [cited by applicant]
US 20150012701A1 · Cudak et al. · 2015 [cited by applicant]
US 20150120936A1 · Palan et al. · 2015 [cited by applicant]
US 20160004616A1 · Narita et al. · 2016 [cited by applicant]
US 20160077917A1 · Battepati et al. · 2016 [cited by applicant]
US 20160085588A1 · Rakitzis et al. · 2016 [cited by applicant]
US 20160179411A1 · Connor et al. · 2016 [cited by applicant]
US 20160210066A1 · Yamaura et al. · 2016 [cited by applicant]
US 20160246864A1 · Boldt et al. · 2016 [cited by applicant]
US 20160283126A1 · Bhagwat et al. · 2016 [cited by applicant]
US 20160342470A1 · Cudak et al. · 2016 [cited by applicant]
US 20170147437A1 · Borlick et al. · 2017 [cited by applicant]
US 20170192682A1 · Atia et al. · 2017 [cited by applicant]
US 20170286179A1 · Dimnaku et al. · 2017 [cited by applicant]
US 20180107409A1 · Condict et al. · 2018 [cited by applicant]
US 20180165169A1 · Camp · 2018 [cited by examiner]
US 20180173554A1 · Caradonna et al. · 2018 [cited by applicant]
US 20180181348A1 · Kusters et al. · 2018 [cited by applicant]
US 20180260125A1 · Botes et al. · 2018 [cited by applicant]
US 20180314445A1 · Karale et al. · 2018 [cited by applicant]
US 20190004899A1 · Gao et al. · 2019 [cited by applicant]
US 20190028691A1 · Hinds et al. · 2019 [cited by applicant]
US 20190034104A1 · Agarwal et al. · 2019 [cited by applicant]
US 20190042090A1 · Raghunath et al. · 2019 [cited by applicant]
US 20190089537A1 · Gray · 2019 [cited by applicant]
US 20190163374A1 · Venkatesh et al. · 2019 [cited by applicant]
US 20190266103A1 · Pearson et al. · 2019 [cited by applicant]
US 20190354406A1 · Ganguli et al. · 2019 [cited by applicant]
US 20190357281A1 · Elbaz et al. · 2019 [cited by applicant]
US 20190386957A1 · Leon · 2019 [cited by applicant]
US 20200034077A1 · Haravu et al. · 2020 [cited by applicant]
US 20200065317A1 · Sarkar et al. · 2020 [cited by applicant]
US 20200081806A1 · Brown et al. · 2020 [cited by applicant]
US 20200117750A1 · Chen et al. · 2020 [cited by applicant]
US 20200136943A1 · Banyal et al. · 2020 [cited by applicant]
US 20200218617A1 · Knestele · 2020 [cited by examiner]
US 20200233881A1 · Harduf et al. · 2020 [cited by applicant]
US 20200252290A1 · Puttagunta et al. · 2020 [cited by applicant]
US 20200265050A1 · Shimizu et al. · 2020 [cited by applicant]
US 20200285543A1 · Sancheti · 2020 [cited by applicant]
US 20200293499A1 · Kohli et al. · 2020 [cited by applicant]
US 20200310662A1 · Staab et al. · 2020 [cited by applicant]
US 20200310915A1 · Alluboyina et al. · 2020 [cited by applicant]
US 20200329101A1 · Kumar et al. · 2020 [cited by applicant]
US 20200348872A1 · Tylik et al. · 2020 [cited by applicant]
US 20200409797A1 · Mathew et al. · 2020 [cited by applicant]
US 20210109683A1 · Cain · 2021 [cited by applicant]
US 20210194825A1 · Goodman et al. · 2021 [cited by applicant]
US 20210314400A1 · Longinov et al. · 2021 [cited by applicant]
US 20220027051A1 · Kant et al. · 2022 [cited by applicant]
US 20220075539A1 · Juch et al. · 2022 [cited by applicant]
US 20220191131A1 · Gupta · 2022 [cited by examiner]
US 20220301157A1 · Soares et al. · 2022 [cited by applicant]
US 20220417004A1 · Sapuntzakis · 2022 [cited by applicant]
US 20230112764A1 · Nazari et al. · 2023 [cited by applicant]
EP 1577736A2 · 2005 [cited by applicant]
EP 3404527A1 · 2018 [cited by applicant]
EP 3493046A1 · 2019 [cited by applicant]
EP 3663902A1 · 2020 [cited by applicant]
WO WO2005055043A1 · 2005 [cited by applicant]
WO 2016083837A1 · 2016 [cited by applicant]
WO 2018164782A1 · 2018 [cited by applicant]
Communication Pursuant to Article 94(3) EPC issued in European Application No. 22742390.2 dated Jun. 12, 2024, 8 pages. [cited by applicant]
Extended European Search Report for European Patent Application No. 22742392.8 dated Jun. 6, 2024, 10 pages. [cited by applicant]
Non Final Office Action for U.S. Appl. No. 18/273,194 mailed Jun. 18, 2024, 24 pages. [cited by applicant]
Supplementary European Search Report for EP Patent Application No. 22742390.2 dated May 31, 2024, 4 pages. [cited by applicant]
Final Office Action for U.S. Appl. No. 18/273,194 mailed Oct. 29, 2024, 34 pages. [cited by applicant]
Non Final Office Action for U.S. Appl. No. 18/273,137 mailed Nov. 21, 2024, 34 pages. [cited by applicant]
Non Final Office Action for U.S. Appl. No. 18/273,141 mailed Nov. 7, 2024, 24 pages. [cited by applicant]
Non Final Office Action for U.S. Appl. No. 18/273,174, mailed Nov. 22, 2024, 25 pages. [cited by applicant]
Non Final Office Action for U.S. Appl. No. 18/273,188 mailed Oct. 18, 2024, 8 pages. [cited by applicant]
Non Final Office Action for U.S. Appl. No. 18/273,215 mailed Dec. 4, 2024, 12 pages. [cited by applicant]
Non Final Office Action for U.S. Appl. No. 18/273,240 mailed Sep. 16, 2024, 40 pages. [cited by applicant]
Partial Supplementary European Search Report for EP Patent Application No. 22742391.0 dated Nov. 28, 2024, 16 pages. [cited by applicant]
Extended European Search Report for EP Patent Application No. 22742386.0 dated Nov. 28, 2024, 11 pages. [cited by applicant]
Extended European Search Report for EP Patent Application No. 22742388.6 dated Dec. 11, 2024, 59 pages. [cited by applicant]
Extended European Search Report for EP Patent Application No. 22742389.4 dated Dec. 3, 2024, 12 pages. [cited by applicant]
Non Final Office Action for U.S. Appl. No. 18/273,148, mailed Jan. 30, 2025, 11 pages. [cited by applicant]
Partial Supplementary European Search Report for EP Patent Application No. 22742393.6 dated Dec. 11, 2024, 16 pages. [cited by applicant]
Partial Supplementary European Search Report for EP Patent Application No. 22742394.4 dated Dec. 11, 2024, 17 pages. [cited by applicant]
Partial Supplementary European Search Report for EP Patent Application No. 22742395.1 dated Dec. 16, 2024, 15 pages. [cited by applicant]
Partial Supplementary European Search Report for EP Patent Application No. 22742396.9 dated Dec. 4, 2024, 16 pages. [cited by applicant]
Partial Supplementary European Search Report for EP Patent Application No. 22742397.7 dated Dec. 18, 2024, 17 pages. [cited by applicant]
Final Office Action for U.S. Appl. No. 18/273,240 mailed Mar. 27, 2025, 29 pages. [cited by applicant]
Non Final Office Action for U.S. Appl. No. 18/273,162, mailed May 21, 2025, 13 pages. [cited by applicant]
“What is a Block Device,” PhoenixNAP Global IT Services, Apr. 18, 2024, https://phoenixnap.com/glossary/block-device, 3 pages. [cited by applicant]
Final Office Action for U.S. Appl. No. 18/273,215, mailed Jun. 11, 2025, 13 pages. [cited by applicant]