IP Library › Granted Patent US 12,235,811
Granted Patent B2
US 12,235,811 · App. 17/351,733 · Granted Feb 25, 2025

Data deduplication in a disaggregated storage system

Inventors: Yosef Shatsky (Karnei Shomron, IL); Doron Tal (Geva Carmel, IL)
Assignee: EMC IP Holding Company LLC
G06F16/215G06F16/2255
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,235,811
App. No.
17/351,733
Granted
Feb 25, 2025
Kind
B2
Abstract

A data deduplication process is performed in a storage system which includes storage nodes, and storage control nodes which can access data directly from each storage node. A first storage control node sends a message to a second storage control node to initiate a deduplication process with respect to a given data block and an original data block owned by the second storage control node. The second storage control node increments a reference counter associated with the original data block, and sends a message to the first storage control which includes metadata. The first storage control node uses the metadata to read the original data block from a given storage node, performs a data compare process to determine whether the given data block matches the original data block, and creates a reference to the original data block, if the given data block matches the original data block.

Claims (90)

1. A method, comprising:

performing a data deduplication process in a data storage system, the data storage system comprising storage nodes, and storage control nodes comprising at least a first storage control node and a second storage control node, wherein each of the storage control nodes can access data directly from each of the storage nodes, wherein the data deduplication process comprises:

determining, by the first storage control node, whether a given data block is at least a potential duplicate of an original data block that is managed by another storage control node of the data storage system; and

in response to the first storage control node determining that the given data block is a potential duplicate of an original data block that is managed by the second storage control node:

sending, by the first storage control node, a first message to the second storage control node, wherein the first message comprises a request to initiate a deduplication process for determining whether the given data block is an actual duplicate of the original data block managed by the second storage control node;

incrementing, by the second storage control node, a reference counter associated with the original data block managed by the second storage control node, wherein the reference counter maintains a count indicative of a number of other storage control nodes that hold a reference to the original data block managed by the second storage control node, wherein the second storage control node increments the reference counter prior to determining whether or not the given data block is an actual duplicate of the original data block;

sending, by the second storage control node, a second message to the first storage control node, wherein the second message comprises metadata which comprises information to enable the first storage control node to read the original data block from a given storage node;

reading, by the first storage control node, the original data block from the given storage node based on the metadata of the second message;

performing, by the first storage control node, a data compare process to determine whether the given data block is an actual duplicate of the original data block;

creating, by the first storage control node, a reference to the original data block, in response to determining that the given data block is an actual duplicate of the original data block;

in response to receiving, by the second storage control node, a notification message from the first storage control node that the given data block is not an actual duplicate of the original data block, the second storage control node decrementing the count of the reference counter associated with the original data block; and

in an absence of receiving, by the second storage control node, a notification message from the first storage control node that the given data block is not an actual duplicate of the original data block, the second storage control node maintaining the count of the reference counter associated with the original data block.

2. The method of claim 1 , wherein determining, by the first storage control node, whether the given data block is at least a potential duplicate of an original data block that is managed by another storage control node of the data storage system, comprises:

computing, by the first storage control node, a hash value of the given data block;

performing, by the first storage control node, a lookup operation on a hash database to determine whether the hash database comprises a stored hash value which matches the computed hash value of the given data block; and

in response to the lookup operation finding a stored hash value which matches the computed hash value, the first storage control node:

determining that the given data block is at least potential duplicate of the original data block associated with the matching hash value; and

determining a location of the original data block based on the matching hash value;

wherein metadata of the first message, which is sent to the second storage control node, comprises the location of the original data block.

3. The method of claim 1 , wherein the data deduplication process further comprises:

in response to receiving the first message from the first storage control node, the second storage control node utilizing the metadata of the first message to determine whether the original data block exists;

wherein the second storage control node increments the reference counter associated with the original data block if the original data block is determined to exist.

4. The method of claim 1 , wherein prior to the first storage control node performing the data compare process, the data deduplication process further comprising:

performing, by the first storage control node, a read validation process by comparing the metadata of the second message to metadata contained in a header of the original data block read from the given storage node to determine whether the original data block read from the given storage node corresponds to the original data block identified by the metadata of the second message;

wherein the first storage control node performs the data compare process if the read validation process determines that the original data block read from the given storage node does correspond to the original data block identified by the metadata of the second message.

5. The method of claim 4 , wherein the data deduplication process further comprises:

in response to the read validation process determining that the original data block read from the given storage node does not correspond to the original data block identified by the metadata of the second message:

sending, by the first storage control node, a third message to the second storage control node, wherein the third message comprises a request for the second storage control node to provide the original data block to the first storage control node; and

in response to the third message, the second storage control node obtaining and sending the original data block to the first storage control node.

6. The method of claim 1 , wherein the data compare process performed by the first storage control node comprise a byte-by-byte comparison between the given data block and the original data block to determine whether the given data block is identical to the original data block.

7. The method of claim 1 , wherein the data deduplication process further comprises:

in response to the first storage control node determining, as a result of the data compare process, that the given data block is not an actual duplicate of the original data block, sending, by the first storage control node, the notification message to the second storage control node, that the given data block is not an actual duplicate of the original data block.

8. The method of claim 1 , wherein the data deduplication process comprises an in-line deduplication process in which the given data block is a portion of a file that is received by the first storage control node as part of an input/output write request.

9. An article of manufacture comprising a non-transitory processor-readable storage medium having stored therein program code of one or more software programs, wherein the program code is executable by one or more processors to implement a method which comprises:

performing a data deduplication process in a data storage system, the data storage system comprising storage nodes, and storage control nodes comprising at least a first storage control node and a second storage control node, wherein each of the storage control nodes can access data directly from each of the storage nodes, wherein the data deduplication process comprises:

determining, by the first storage control node, whether a given data block is at least a potential duplicate of an original data block that is managed by another storage control node of the data storage system; and

in response to the first storage control node determining that the given data block is a potential duplicate of an original data block that is managed by the second storage control node:

sending, by the first storage control node, a first message to the second storage control node, wherein the first message comprises a request to initiate a deduplication process for determining whether the given data block is an actual duplicate of the original data block managed by the second storage control node;

incrementing, by the second storage control node, a reference counter associated with the original data block managed by the second storage control node, wherein the reference counter maintains a count indicative of a number of other storage control nodes that hold a reference to the original data block managed by the second storage control node, wherein the second storage control node increments the reference counter prior to determining whether or not the given data block is an actual duplicate of the original data block;

sending, by the second storage control node, a second message to the first storage control node, wherein the second message comprises metadata which comprises information to enable the first storage control node to read the original data block from a given storage node;

reading, by the first storage control node, the original data block from the given storage node based on the metadata of the second message;

performing, by the first storage control node, a data compare process to determine whether the given data block is an actual duplicate of the original data block;

creating, by the first storage control node, a reference to the original data block, in response to determining that the given data block is an actual duplicate of the original data block;

in response to receiving, by the second storage control node, a notification message from the first storage control node that the given data block is not an actual duplicate of the original data block, the second storage control node decrementing the count of the reference counter associated with the original data block; and

in an absence of receiving, by the second storage control node, a notification message from the first storage control node that the given data block is not an actual duplicate of the original data block, the second storage control node maintaining the count of the reference counter associated with the original data block.

10. The article of manufacture of claim 9 , wherein the program code for determining, by the first storage control node, whether the given data block is at least a potential duplicate of an original data block that is managed by another storage control node of the data storage system, comprises program code for:

computing, by the first storage control node, a hash value of the given data block;

performing, by the first storage control node, a lookup operation on a hash database to determine whether the hash database comprises a stored hash value which matches the computed hash value of the given data block; and

in response to the lookup operation finding a stored hash value which matches the computed hash value, the first storage control node:

determining that the given data block is at least a potential duplicate of the original data block associated with the matching hash value; and

determining a location of the original data block based on the matching hash value;

wherein the metadata of the first message, which is sent to the second storage control node, comprises the location of the original data block.

11. The article of manufacture of claim 9 , wherein the program code for performing the data deduplication process further comprises program code for:

in response to receiving the first message from the first storage control node, the second storage control node utilizing the metadata of the first message to determine whether the original data block exists;

wherein the second storage control node increments the reference counter associated with the original data block if the original data block is determined to exist.

12. The article of manufacture of claim 9 , wherein the program code for performing the data deduplication process further comprises program code for:

prior to the first storage control node performing the data compare process:

performing, by the first storage control node, a read validation process by comparing the metadata of the second message to metadata contained in a header of the original data block read from the given storage node to determine whether the original data block read from the given storage node corresponds to the original data block identified by the metadata of the second message;

wherein the first storage control node performs the data compare process if the read validation process determines that the original data block read from the given storage node does correspond to the original data block identified by the metadata of the second message.

13. The article of manufacture of claim 12 , wherein the program code for performing the data deduplication process further comprises program code for:

in response to the read validation process determining that the original data block read from the given storage node does not correspond to the original data block identified by the metadata of the second message:

sending, by the first storage control node, a third message to the second storage control node, wherein the third message comprises a request for the second storage control node to provide the original data block to the first storage control node; and

in response to the third message, the second storage control node obtaining and sending the original data block to the first storage control node.

14. The article of manufacture of claim 9 , wherein data compare process performed by the first storage control node comprise a byte-by-byte comparison between the given data block and the original data block to determine whether the given data block is identical to the original data block.

15. The article of manufacture of claim 9 , wherein the program code for performing the data deduplication process further comprises program code for:

in response to the first storage control node determining, as a result of the data compare process, that the given data block is not an actual duplicate of the original data block, sending, by the first storage control node, the notification message to the second storage control node that the given data block is not an actual duplicate of the original data block.

16. A system, comprising:

a data storage system comprising storage nodes which comprise respective physical storage devices for storing data, and storage control nodes comprising at least a first storage control node operating on at least a first physical machine and a second storage control node operating on at least a second physical machine, wherein each of the storage control nodes can access data directly from each of the storage nodes; and

a data deduplication system implemented by the data storage system, wherein the data deduplication system is configured to perform a data deduplication process which comprises:

determining, by the first storage control node, whether a given data block is at least a potential duplicate of an original data block that is managed by another storage control node of the data storage system; and

in response to the first storage control node determining that the given data block is a potential duplicate of an original data block that is managed by the second storage control node:

sending, by the first storage control node, a first message to the second storage control node, wherein the first message comprises a request to initiate a deduplication process for determining whether the given data block is an actual duplicate of the original data block managed by the second storage control node;

incrementing, by the second storage control node, a reference counter associated with the original data block managed by the second storage control node, wherein the reference counter maintains a count indicative of a number of other storage control nodes that hold a reference to the original data block managed by the second storage control node, wherein the second storage control node increments the reference counter prior to determining whether or not the given data block is an actual duplicate of the original data block;

sending, by the second storage control node, a second message to the first storage control node, wherein the second message comprises metadata which comprises information to enable the first storage control node to read the original data block from a given storage node;

reading, by the first storage control node, the original data block from the given storage node based on the metadata of the second message;

performing, by the first storage control node, a data compare process to determine whether the given data block is an actual duplicate of the original data block;

creating, by the first storage control node, a reference to the original data block, in response to determining that the given data block is an actual duplicate of the original data block;

in response to receiving, by the second storage control node, a notification message from the first storage control node that the given data block is not an actual duplicate of the original data block, the second storage control node decrementing the count of the reference counter associated with the original data block; and

in an absence of receiving, by the second storage control node, a notification message from the first storage control node that the given data block is not an actual duplicate of the original data block, the second storage control node maintaining the count of the reference counter associated with the original data block.

17. The system of claim 16 , wherein the data deduplication system is configured to perform a data deduplication process which further comprises:

prior to the first storage control node performing the data compare process:

performing, by the first storage control node, a read validation process by comparing the metadata of the second message to metadata contained in a header of the original data block read from the given storage node to determine whether the original data block read from the given storage node corresponds to the original data block identified by the metadata of the second message;

wherein the first storage control node performs the data compare process if the read validation process determines that the original data block read from the given storage node does correspond to the original data block identified by the metadata of the second message.

18. The system of claim 17 , wherein the data deduplication system is configured to perform a data deduplication process which further comprises:

in response to the read validation process determining that the original data block read from the given storage node does not correspond to the original data block identified by the metadata of the second message:

sending, by the first storage control node, a third message to the second storage control node, wherein the third message comprises a request for the second storage control node to provide the original data block to the first storage control node; and

in response to the third message, the second storage control node obtaining and sending the original data block to the first storage control node.

19. The system of claim 16 , wherein the data compare process performed by the first storage control node comprise a byte-by-byte comparison between the given data block and the original data block to determine whether the given data block is identical to the original data block.

20. The system of claim 16 , wherein the data deduplication system is configured to perform a data deduplication process which further comprises:

in response to the first storage control node determining, as a result of the data compare process, that the given data block is not an actual duplicate of the original data block, sending, by the first storage control node, the notification message to the second storage control node that the given data block is not an actual duplicate of the original data block.

Assignments (8)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (058014/0560) Recorded Jun 10, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
Reel/Frame 062022/0473 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (057931/0392) Recorded Jun 10, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
Reel/Frame 062022/0382 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (057758/0286) Recorded Jun 10, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
Reel/Frame 061654/0064 →
SECURITY INTEREST Recorded Oct 6, 2021
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 058014/0560 →
SECURITY INTEREST Recorded Oct 6, 2021
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 057758/0286 →
SECURITY INTEREST Recorded Oct 6, 2021
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 057931/0392 →
SECURITY AGREEMENT Recorded Oct 1, 2021
From: DELL PRODUCTS, L.P.; EMC IP HOLDING COMPANY LLC
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
Reel/Frame 057682/0830 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 18, 2021
From: SHATSKY, YOSEF; TAL, DORON
To: EMC IP HOLDING COMPANY LLC
Reel/Frame 056586/0731 →
Continuity (1)
Related Publication 20220405254A1 · Dec 22, 2022
References Cited (82)
US 5381539A · Yanai et al. · 1995 [cited by applicant]
US 5551003A · Mattson et al. · 1996 [cited by applicant]
US 5764880A · Gerdt et al. · 1998 [cited by applicant]
US 6052799A · Li et al. · 2000 [cited by applicant]
US 6941420B2 · Butterworth et al. · 2005 [cited by applicant]
US 8560503B1 · McManis · 2013 [cited by examiner]
US 8843676B2 · Rajamanickam et al. · 2014 [cited by applicant]
US 9141554B1 · Candelaria · 2015 [cited by examiner]
US 9152335B2 · Sundaram · 2015 [cited by examiner]
US 9372751B2 · McNutt · 2016 [cited by applicant]
US 9514014B2 · Webman et al. · 2016 [cited by applicant]
US 9892045B1 · Douglis et al. · 2018 [cited by applicant]
US 10078598B1 · Wallace et al. · 2018 [cited by applicant]
US 10331561B1 · Shilane et al. · 2019 [cited by applicant]
US 10445180B2 · Butterworth et al. · 2019 [cited by applicant]
US 10809928B2 · Battaje · 2020 [cited by examiner]
US 11537573B2 · Ghanbari · 2022 [cited by examiner]
US 20020032835A1 · Li et al. · 2002 [cited by applicant]
US 20080021853A1 · Modha et al. · 2008 [cited by applicant]
US 20090204761A1 · Caprioli et al. · 2009 [cited by applicant]
US 20090276593A1 · Jacobson et al. · 2009 [cited by applicant]
US 20110029497A1 · Benhase · 2011 [cited by examiner]
US 20130054906A1 · Anglin · 2013 [cited by examiner]
US 20130305002A1 · Hallak et al. · 2013 [cited by applicant]
US 20140089275A1 · Akirav · 2014 [cited by examiner]
US 20140244935A1 · Ezra et al. · 2014 [cited by applicant]
US 20140304464A1 · Bert · 2014 [cited by examiner]
US 20160103764A1 · Banerjee et al. · 2016 [cited by applicant]
US 20180060367A1 · Ioannou · 2018 [cited by examiner]
US 20180113640A1 · Fernandez et al. · 2018 [cited by applicant]
US 20180267893A1 · Barzik et al. · 2018 [cited by applicant]
US 20180292995A1 · Tal · 2018 [cited by examiner]
US 20180300075A1 · Fernandez et al. · 2018 [cited by applicant]
US 20180349053A1 · Battaje · 2018 [cited by examiner]
US 20190227845A1 · Sridhar et al. · 2019 [cited by applicant]
US 20220237205A1 · Kamran · 2022 [cited by examiner]
WO PCTUS2019024885 · 2020 [cited by applicant]
WO PCTUS2019024900 · 2020 [cited by applicant]
WO 2020204880A1 · 2020 [cited by applicant]
WO 2020204882A1 · 2020 [cited by applicant]
Dell EMC, “Dell EMC VxRack FLEX,” Dell EMC Product Overview, 2018, 5 pages. [cited by applicant]
G. Soundararajan et al., “Dynamic Resource Allocation for Database Servers Running on Virtual Storage,” FAST 2009: Proceedings of the 7th conference on File and storage technologies, Feb. 2009, pp. 71-84. [cited by applicant]
Dell EMC, “EMC ScaleIO Basic Architecture Documentation,” Technical White Paper, Mar. 2017, 22 pages. [cited by applicant]
EMC2, “EMC ScaleIO Design Considerations and Best Practices,” Technical White Paper, Jun. 2016, 30 pages. [cited by applicant]
I. Koltsidas et al., “SoftwAre Log-Structured Array (SALSA)—A Unified Stack for SSDs and SMR Disks,” IBM Research Report, Dec. 2, 2015, 13 pages. [cited by applicant]
S. M. Rumble et al., “Log-Structured Memory for DRAM-Based Storage,” Proceedings of the 12th USENIX Conference on File and Storage Technologies, Santa Clara, CA, Feb. 17-20, 2014, 17 pages. [cited by applicant]
Dell EMC, “Dell EMC VxFlex Family Overview,” Technical White Paper, May 2019, 44 pages. [cited by applicant]
J. Nakano et al., “ReVivel/O: Efficient Handling of I/O in Highly-Available Rollback-Recovery Servers,” HPCA, 10.1109/2006.1598129, pp. 200-211. [cited by applicant]
Wikipedia, “Raft (Computer Science),” https://en.wikipedia.org/wiki/Raft_(computer_science), Feb. 10, 2020, 4 pages. [cited by applicant]
Wikipedia, “Paxos (Computer Science),” https://en.wikipedia.org/wiki/Paxos_(computer_science), Dec. 6, 2019, 21 pages. [cited by applicant]
Wikipedia, “State Machine Replication,” https://en.wikipedia.org/wiki/State_machine_replication, Dec. 14, 2019, 9 pages. [cited by applicant]
Dell Technologies, “Dell EMC PowerFlex: Secure Snapshots,” Technical White Paper, Jul. 2020, 17 pages. [cited by applicant]
Dell Technologies, “Dell EMC PowerFlex: Protected Maintenance Mode,” Technical White Paper, Jul. 2020, 20 pages. [cited by applicant]
Dell Technologies, “Dell EMC PowerFlex: Introduction to Replication,” Technical White Paper, Jun. 2020, 34 pages. [cited by applicant]
Dell Technologies, “Dell EMC PowerFlex: Networking Best Practices and Design Considerations,” Best Practices, Jun. 2020, 64 pages. [cited by applicant]
Dell EMC, “Getting To Know Dell EMC PowerFlex,” Version 3.5.x, Rev. 02, Jan. 2021, 66 pages. [cited by applicant]
U.S. Appl. No. 16/807,709 filed in the name of Avi Puder et al. on Mar. 3, 2020, and entitled “Management of Shared Resources in a Software-Defined Storage Environment.” [cited by applicant]
U.S. Appl. No. 16/822,818 filed in the name of Itay Keller et al. on Mar. 18, 2020, and entitled “Storage System Implementing Snapshot Longevity Ranking for Efficient Management of Snapshots.” [cited by applicant]
U.S. Appl. No. 16/822,848 filed in the name of Itay Keller et al. on Mar. 18, 2020, and entitled “Assignment of Longevity Ranking Values of Storage Volume Snapshots Based on Snapshot Policies.” [cited by applicant]
U.S. Appl. No. 16/823,813 filed in the name of Itay Keller et al. on Mar. 19, 2020, and entitled “Managing Incompressible Data in a Compression-Enabled Log-Structured Array Storage System.” [cited by applicant]
U.S. Appl. No. 16/830,469 filed in the name of Roi Tagar et al. on Mar. 26, 2020, and entitled “Storage Block Balancing Using Volume Part Migration.” [cited by applicant]
U.S. Appl. No. 16/830,473 filed in the name of Yugal Peleg Lieblich et al. on Mar. 26, 2020, and entitled “Replicated State Cluster with Standby Node State Assessment During Leadership Transition.” [cited by applicant]
U.S. Appl. No. 16/830,946 filed in the name of Gil Ben Zeev et al. on Mar. 26, 2020, and entitled “Storage Volume Migration Scheduling Based on Storage Volume Priorities and Specified Constraints.” [cited by applicant]
U.S. Appl. No. 16/832,763 filed in the name of Michal Yarimi et al. on Mar. 27, 2020, and entitled “Managing Storage Device Errors During Processing of Inflight Input/Output Requests.” [cited by applicant]
U.S. Appl. No. 16/834,363 filed in the name of Itay Keller et al. on Mar. 30, 2020, and entitled “Managing Least Recently Used Cache Using Reduced Memory Footprint Sequence Container.” [cited by applicant]
U.S. Appl. No. 16/836,824 filed in the name of Itay Keller et al. on Mar. 31, 2020, and entitled “Management of Volume Snapshots in a Data Storage System.” [cited by applicant]
U.S. Appl. No. 16/888,742 filed in the name of Rivka Matosevich et al. on May 31, 2020, and entitled “Balancing Resiliency and Performance by Selective Use of Degraded Writes and Spare Capacity in Storage Systems.” [cited by applicant]
U.S. Appl. No. 16/918,654 filed in the name of Rivka Matosevich et al. on Jul. 1, 2020, and entitled “Sharing Memory Resources Between Asynchronous Replication Workloads.” [cited by applicant]
U.S. Appl. No. 16/983,423 filed in the name of Dan Aharoni et al. on Aug. 3, 2020, and entitled “Deferred Reclamation of Invalidated Entries that are Associated with a Transaction Log in a Log-Structured Array.” [cited by applicant]
U.S. Appl. No. 17/024,912 filed in the name of Anurag Sharma et al. on Sep. 18, 2020, and entitled “Automatic Discovery and Configuration of Server Nodes.” [cited by applicant]
U.S. Appl. No. 17/065,754 filed in the name of Dan Aharoni et al. on Oct. 8, 2020, and entitled “Direct Response to IO Request in Storage System with Remote Replication.” [cited by applicant]
U.S. Appl. No. 17/070,073 filed in the name of Dan Aharoni et al. on Oct. 14, 2020, and entitled “Direct Response to IO Request in Storage System Having an Intermediary Target Apparatus.” [cited by applicant]
U.S. Appl. No. 17/070,288 filed in the name of Anurag Sharma et al. on Oct. 14, 2020, and entitled “Pipeline-Based System for Configuration Checking and Reporting Associated with an Information Processing System.” [cited by applicant]
U.S. Appl. No. 17/071,407 filed in the name of John Moran et al. on Oct. 15, 2020, and entitled “Dynamic Remediation Actions in Response to Configuration Checks in an Information Processing System.” [cited by applicant]
U.S. Appl. No. 17/077,105 filed in the name of Yosef Shatsky et al. on Oct. 22, 2020, and entitled “Volume Tiering in Storage Systems.” [cited by applicant]
U.S. Appl. No. 17/106,988 filed in the name of Rivka Matosevich et al. on Nov. 30, 2020, and entitled “Managing Host Connectivity to a Data Storage System.” [cited by applicant]
U.S. Appl. No. 17/123,525 filed in the name of Itay Keller et al. on Dec. 16, 2020, and entitled “Deferred Reclamation of Invalidated Entries Associated with Replication in a Log-Structured Array.” [cited by applicant]
U.S. Appl. No. 17/145,646 filed in the name of Yosef Shatsky et al. on Jan. 11, 2021, and entitled “Redistribution of Processing Groups between Server Nodes Based on Hardware Resource Utilization.” [cited by applicant]
U.S. Appl. No. 17/232,203 filed in the name of Roman Spiegelman on Apr. 16, 2021, and entitled “Object Synchronization of Server Nodes in a Network Computing Environment.” [cited by applicant]
U.S. Appl. No. 17/236,256 filed in the name of Doron Tal et al. on Apr. 21, 2021, and entitled “Recovery from Partial Device Error in Data Storage System.” [cited by applicant]
U.S. Appl. No. 17/306,601 filed in the name of Rivka Matosevich et al. on May 3, 2021, and entitled “Managing Replication Journal in a Distributed Replication System.” [cited by applicant]
U.S. Appl. No. 17/308,166 filed in the name of Adi Bar Shalom et al. on May 5, 2021, and entitled “Journal Barrier Consistency Determination.” [cited by applicant]
Cited By (1)
US 12,561,728