IP Library › Granted Patent US 12,309,271
Granted Patent B2
US 12,309,271 · App. 18/162,459 · Granted May 20, 2025

Techniques for maintaining file consistency during file system cross-region replication

Inventors: Satish Kumar Kashi Visvanathan (San Jose, CA); Viggnesh Venugopal (Santa Clara, CA); Stephen Anthony Fridella (Watertown, MA); Ashwin Vijayavel (Sunnyvale, CA)
Assignee: Oracle International Corporation
G06F16/1844G06F9/505G06F11/1417G06F11/1451G06F11/1464G06F11/2023G06F11/2028G06F16/128G06F16/1756G06F16/178G06F16/185G06F16/2365G06F16/27G06F21/602G06F21/6218H04L9/0819H04L9/0836H04L9/0891H04L9/0894H04L9/14H04L9/3228G06F16/1774G06F16/2246G06F2201/84
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,309,271
App. No.
18/162,459
Granted
May 20, 2025
Kind
B2
Abstract

Novel techniques are described for maintaining file consistency between different cloud infrastructure regions during cross-region file storage replication. The novel techniques comprise upon detecting a file deletion status (i.e., a file directory entry version marked as deletion) in a source file system during a replication cycle, retrieving file name from a valid file directory entry of a prior snapshot to construct a temporary file directory entry containing necessary information for a target file system to reconstruct a duplicate file directory entry version marked as deletion. The temporary file directory entry is transferred from the source file system to the target file system during the same replication cycle.

Claims (37)

1. A method, comprising:

performing, by a computing device, a file replication for a file in a first snapshot of a source file system during a replication cycle, the file replication being between the source file system and a target file system;

upon determining that a source file directory entry of the first snapshot contains a file deletion status, performing, by the computing device, a lookup to identify a file directory entry without a file deletion status in a second snapshot of the source file system, the second snapshot being created earlier in time than the first snapshot;

generating, by the computing device, a status based at least in part on the result of performing the lookup to identify a file directory entry without a file deletion status;

in accordance with the status indicating that a file directory entry without a file deletion status has been identified in the second snapshot, generating, by the computing device, a temporary file directory entry based at least in part on the identified file directory entry without a file deletion status; and

transferring, by the computing device, the temporary file directory entry from the source file system to the target file system.

2. The method of claim 1 , wherein the source file directory entry of the first snapshot containing a file deletion status has an encrypted file name associated with the file.

3. The method of claim 1 , wherein the temporary file directory entry has a plain text file name associated with the file, and the plain text file name is obtained by decrypting an encrypted file name in the identified file directory entry without a file deletion status in the second snapshot.

4. The method of claim 1 , further comprising creating a target file directory entry with a file deletion status by the target file system based on the temporary file directory entry, wherein the target file directory entry is a duplicate of the source file directory entry of the first snapshot containing a file deletion status.

5. The method of claim 4 , further comprising extending file deletion status in the target file directory entry with a file deletion status in the target file system until another file directory entry without file deletion status is received by the target file system during the file replication.

6. The method of claim 1 , wherein transferring the temporary file directory entry from the source file system to the target file system occurs during the same replication cycle.

7. The method of claim 1 , further comprising in response to the status indicating that no file directory entry without a file deletion status exists in all snapshots created earlier than the first snapshot in the source file system, the file replication for the file stops.

8. The method of claim 1 , wherein the source file system and the target file system are in different cloud infrastructure data centers.

9. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising:

performing, by a computing device, a file replication for a file in a first snapshot of a source file system during a replication cycle, the file replication being between the source file system and a target file system;

upon determining that a source file directory entry of the first snapshot contains a file deletion status, performing, by the computing device, a lookup to identify a file directory entry without a file deletion status in a second snapshot of the source file system, the second snapshot being created earlier in time than the first snapshot;

generating, by the computing device, a status based at least in part on the result of performing the lookup to identify a file directory entry without a file deletion status;

in accordance with the status indicating that a file directory entry without a file deletion status has been identified in the second snapshot, generating, by the computing device, a temporary file directory entry based at least in part on the identified file directory entry without a file deletion status; and

transferring, by the computing device, the temporary file directory entry from the source file system to the target file system during the same replication cycle, the source file system and the target file system being in different cloud infrastructure data centers.

10. The non-transitory computer-readable medium of claim 9 , wherein the source file directory entry of the first snapshot containing a file deletion status has an encrypted file name associated with the file.

11. The non-transitory computer-readable medium of claim 9 , wherein the temporary file directory entry has a plain text file name associated with the file, and the plain text file name is obtained by decrypting an encrypted file name in the identified file directory entry without a file deletion status in the second snapshot.

12. The non-transitory computer-readable medium of claim 9 , further comprising creating a target file directory entry with a file deletion status by the target file system based on the temporary file directory entry, wherein the target file directory entry is a duplicate of the source file directory entry of the first snapshot containing a file deletion status.

13. The non-transitory computer-readable medium of claim 12 , further comprising extending file deletion status in the target file directory entry with a file deletion status in the target file system until another file directory entry without file deletion status is received by the target file system during the file replication.

14. The non-transitory computer-readable medium of claim 9 , further comprising in response to the status indicating that no file directory entry without a file deletion status exists in all snapshots created earlier than the first snapshot in the source file system, the file replication for the file stops.

15. A system, comprising:

one or more processors; and

one or more non-transitory computer readable media storing computer-executable instructions that, when executed by the one or more processors, cause the system to perform operations comprising:

performing, by a computing device, a file replication for a file in a first snapshot of a source file system during a replication cycle, the file replication being between the source file system and a target file system;

upon determining that a source file directory entry of the first snapshot contains a file deletion status, performing, by the computing device, a lookup to identify a file directory entry without a file deletion status in a second snapshot of the source file system, the second snapshot being created earlier in time than the first snapshot;

generating, by the computing device, a status based at least in part on the result of performing the lookup to identify a file directory entry without a file deletion status;

in accordance with the status indicating that a file directory entry without a file deletion status has been identified in the second snapshot, generating, by the computing device, a temporary file directory entry based on the identified file directory entry without a file deletion status; and

transferring, by the computing device, the temporary file directory entry from the source file system to the target file system during the same replication cycle, the source file system and the target file system being in different cloud infrastructure data centers.

16. The system of claim 15 , wherein the source file directory entry of the first snapshot containing a file deletion status has an encrypted file name associated with the file.

17. The system of claim 15 , wherein the temporary file directory entry has a plain text file name associated with the file, and the plain text file name is obtained by decrypting an encrypted file name in the identified file directory entry without a file deletion status in the second snapshot.

18. The system of claim 15 , further comprising creating a target file directory entry with a file deletion status by the target file system based on the temporary file directory entry, wherein the target file directory entry is a duplicate of the source file directory entry of the first snapshot containing a file deletion status.

19. The system of claim 18 , further comprising extending file deletion status in the target file directory entry with a file deletion status in the target file system until another file directory entry without file deletion status is received by the target file system during the file replication.

20. The system of claim 15 , further comprising in response to the status indicating that no file directory entry without a file deletion status exists in all snapshots created earlier than the first snapshot in the source file system, the file replication for the file stops.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 24, 2023
From: KASHI VISVANATHAN, SATISH KUMAR; VENUGOPAL, VIGGNESH; FRIDELLA, STEPHEN ANTHONY; VIJAYAVEL, ASHWIN
To: ORACLE INTERNATIONAL CORPORATION
Reel/Frame 062802/0229 →
Continuity (5)
Provisional Application 63378486 · Oct 5, 2022
Provisional Application 63412243 · Sep 30, 2022
Provisional Application 63357526 · Jun 30, 2022
Provisional Application 63352992 · Jun 16, 2022
Related Publication 20230409559A1 · Dec 21, 2023
References Cited (189)
US 5806075A · Jain et al. · 1998 [cited by applicant]
US 6615333B1 · Hoogerbrugge et al. · 2003 [cited by applicant]
US 7308545B1 · Kekre et al. · 2007 [cited by applicant]
US 7546431B2 · Stacey et al. · 2009 [cited by applicant]
US 8271992B2 · Chatley et al. · 2012 [cited by applicant]
US 8326803B1 · Stringham · 2012 [cited by applicant]
US 8332375B2 · Chatley et al. · 2012 [cited by applicant]
US 8336056B1 · Gadir · 2012 [cited by applicant]
US 8464101B1 · Natanzon et al. · 2013 [cited by applicant]
US 8522252B2 · Chatley et al. · 2013 [cited by applicant]
US 8548949B2 · Jennas, II et al. · 2013 [cited by applicant]
US 8700855B2 · Revanuru · 2014 [cited by applicant]
US 8832027B1 · Bushman · 2014 [cited by applicant]
US 8856079B1 · Subramanian et al. · 2014 [cited by applicant]
US 9047307B1 · Ghemawat et al. · 2015 [cited by applicant]
US 9189495B1 · Hughes et al. · 2015 [cited by applicant]
US 9489434B1 · Rath · 2016 [cited by applicant]
US 9535746B2 · Gupta et al. · 2017 [cited by applicant]
US 9760358B2 · Sapaliga et al. · 2017 [cited by applicant]
US 9916203B1 · Pogde et al. · 2018 [cited by applicant]
US 9928246B1 · Xu et al. · 2018 [cited by applicant]
US 9952767B2 · Zheng et al. · 2018 [cited by applicant]
US 10459632B1 · Chen et al. · 2019 [cited by applicant]
US 10503753B2 · Mitkar et al. · 2019 [cited by applicant]
US 10514986B2 · Bangalore et al. · 2019 [cited by applicant]
US 10664358B1 · Chen et al. · 2020 [cited by applicant]
US 10698941B2 · Maybee et al. · 2020 [cited by applicant]
US 10721141B1 · Verma et al. · 2020 [cited by applicant]
US 10756888B2 · Han · 2020 [cited by applicant]
US 10908828B1 · Meiri et al. · 2021 [cited by applicant]
US 10922132B1 · Shiramshetti et al. · 2021 [cited by applicant]
US 11005935B1 · Littlefield et al. · 2021 [cited by applicant]
US 11036677B1 · Grunwald et al. · 2021 [cited by applicant]
US 11080041B1 · Ah Kun et al. · 2021 [cited by applicant]
US 11086545B1 · Dayal et al. · 2021 [cited by applicant]
US 11151092B2 · Chmiel et al. · 2021 [cited by applicant]
US 11372725B2 · Bajaj · 2022 [cited by applicant]
US 11513997B2 · Keller et al. · 2022 [cited by applicant]
US 11575727B1 · Woodruff et al. · 2023 [cited by applicant]
US 11714782B2 · Subramanian et al. · 2023 [cited by applicant]
US 11809735B1 · Kumar et al. · 2023 [cited by applicant]
US 11836110B2 · Matsushita et al. · 2023 [cited by applicant]
US 11860673B1 · Kodakandla et al. · 2024 [cited by applicant]
US 12001404B2 · Kashi Visvanathan et al. · 2024 [cited by applicant]
US 12147394B2 · Kashi Visvanathan et al. · 2024 [cited by applicant]
US 12182078B2 · Kashi Visvanathan et al. · 2024 [cited by applicant]
US 12197790B2 · Nelson · 2025 [cited by applicant]
US 20020112123A1 · Becker et al. · 2002 [cited by applicant]
US 20020129214A1 · Sarkar · 2002 [cited by applicant]
US 20030182313A1 · Federwisch et al. · 2003 [cited by applicant]
US 20050165862A1 · Loafman et al. · 2005 [cited by applicant]
US 20060271598A1 · Wong et al. · 2006 [cited by applicant]
US 20080049254A1 · Phan et al. · 2008 [cited by applicant]
US 20080109496A1 · Holenstein et al. · 2008 [cited by applicant]
US 20080168218A1 · Arakawa et al. · 2008 [cited by applicant]
US 20080172542A1 · Kaushik · 2008 [cited by applicant]
US 20080250234A1 · Webber · 2008 [cited by applicant]
US 20090138480A1 · Chatley et al. · 2009 [cited by applicant]
US 20090138481A1 · Chatley et al. · 2009 [cited by applicant]
US 20090144224A1 · Phan et al. · 2009 [cited by applicant]
US 20090144284A1 · Chatley et al. · 2009 [cited by applicant]
US 20090144422A1 · Chatley et al. · 2009 [cited by applicant]
US 20090307277A1 · Grubov et al. · 2009 [cited by applicant]
US 20110213765A1 · Cui et al. · 2011 [cited by applicant]
US 20110231172A1 · Gold · 2011 [cited by applicant]
US 20120131595A1 · Kim et al. · 2012 [cited by applicant]
US 20120317079A1 · Shoens et al. · 2012 [cited by applicant]
US 20120323844A1 · Chatley et al. · 2012 [cited by applicant]
US 20130005491A1 · Cox et al. · 2013 [cited by applicant]
US 20130339407A1 · Sharpe et al. · 2013 [cited by applicant]
US 20140052692A1 · Zhang et al. · 2014 [cited by applicant]
US 20150066857A1 · Dayal et al. · 2015 [cited by applicant]
US 20150074536A1 · Varadharajan et al. · 2015 [cited by applicant]
US 20150120893A1 · Sapaliga et al. · 2015 [cited by applicant]
US 20150378636A1 · Yadav et al. · 2015 [cited by applicant]
US 20160188380A1 · Eastep et al. · 2016 [cited by applicant]
US 20160335278A1 · Tabaaloute et al. · 2016 [cited by applicant]
US 20160359963A1 · Chatley et al. · 2016 [cited by applicant]
US 20160359976A1 · Chatley et al. · 2016 [cited by applicant]
US 20170046093A1 · Butt · 2017 [cited by examiner]
US 20180101311A1 · Koszewnik · 2018 [cited by applicant]
US 20190171497A1 · Agarwal et al. · 2019 [cited by applicant]
US 20190235917A1 · Koneru et al. · 2019 [cited by applicant]
US 20190384743A1 · Lv et al. · 2019 [cited by applicant]
US 20200065196A1 · Desai et al. · 2020 [cited by applicant]
US 20200210223A1 · Saka et al. · 2020 [cited by applicant]
US 20200250684A1 · Puehse et al. · 2020 [cited by applicant]
US 20200257700A1 · Xu et al. · 2020 [cited by applicant]
US 20200301882A1 · Pogde et al. · 2020 [cited by applicant]
US 20200310919A1 · Bajaj · 2020 [cited by applicant]
US 20200333970A1 · Mukku et al. · 2020 [cited by applicant]
US 20200334111A1 · Potnis et al. · 2020 [cited by applicant]
US 20200409974A1 · Ayzenberg et al. · 2020 [cited by applicant]
US 20210157504A1 · Hinman · 2021 [cited by applicant]
US 20210173945A1 · Karr et al. · 2021 [cited by applicant]
US 20210200771A1 · Kuang et al. · 2021 [cited by applicant]
US 20210216625A1 · Miller et al. · 2021 [cited by applicant]
US 20210226861A1 · Barsalou et al. · 2021 [cited by applicant]
US 20210294775A1 · Keller et al. · 2021 [cited by applicant]
US 20210342299A1 · Kumarasamy et al. · 2021 [cited by applicant]
US 20210389883A1 · Derryberry et al. · 2021 [cited by applicant]
US 20210390078A1 · Aahlad et al. · 2021 [cited by applicant]
US 20210390113A1 · Danilov et al. · 2021 [cited by applicant]
US 20220058094A1 · Gunturu et al. · 2022 [cited by applicant]
US 20220060323A1 · Payne et al. · 2022 [cited by applicant]
US 20220121365A1 · Wang et al. · 2022 [cited by applicant]
US 20220147490A1 · Shivani et al. · 2022 [cited by applicant]
US 20220182297A1 · Verma et al. · 2022 [cited by applicant]
US 20220188267A1 · Patil et al. · 2022 [cited by applicant]
US 20220198322A1 · Kuperman et al. · 2022 [cited by applicant]
US 20220222358A1 · Sahita et al. · 2022 [cited by applicant]
US 20220229734A1 · Seela et al. · 2022 [cited by applicant]
US 20220263657A1 · Chang et al. · 2022 [cited by applicant]
US 20220308965A1 · Gunda et al. · 2022 [cited by applicant]
US 20230029677A1 · Gupta et al. · 2023 [cited by applicant]
US 20230134314A1 · Braganza et al. · 2023 [cited by applicant]
US 20230177069A1 · Xiang et al. · 2023 [cited by applicant]
US 20230222096A1 · Fan et al. · 2023 [cited by applicant]
US 20230333777A1 · Shveidel et al. · 2023 [cited by applicant]
US 20230385153A1 · George et al. · 2023 [cited by applicant]
US 20230409442A1 · Kashi Visvanathan et al. · 2023 [cited by applicant]
US 20230409522A1 · Kashi Visvanathan et al. · 2023 [cited by applicant]
US 20230409535A1 · Kashi Visvanathan et al. · 2023 [cited by applicant]
US 20230409559A1 · Kashi Visvanathan et al. · 2023 [cited by applicant]
US 20230409597A1 · Kashi Visvanathan et al. · 2023 [cited by applicant]
US 20230412375A1 · Bisht et al. · 2023 [cited by applicant]
US 20240028466A1 · Duggal et al. · 2024 [cited by applicant]
US 20240094937A1 · Kashi Visvanathan et al. · 2024 [cited by applicant]
US 20240134828A1 · Kashi Visvanathan et al. · 2024 [cited by applicant]
US 20240281413A1 · Kashi Visvanathan et al. · 2024 [cited by applicant]
CA 2954888A1 · 2007 [cited by applicant]
CN 104641365A · 2015 [cited by applicant]
CN 117215721A · 2023 [cited by applicant]
JP 2017531256A · 2017 [cited by applicant]
WO 2015110171A1 · 2015 [cited by applicant]
WO 2023244601A1 · 2023 [cited by applicant]
U.S. Appl. No. 18/166,992, Non-Final Office Action mailed on Jun. 20, 2024, 9 pages. [cited by applicant]
U.S. Appl. No. 18/169,121, Non-Final Office Action mailed on Aug. 14, 2024, 29 pages. [cited by applicant]
U.S. Appl. No. 18/181,414, Final Office Action mailed on Aug. 12, 2024, 22 pages. [cited by applicant]
U.S. Appl. No. 18/181,414, Non-Final Office Action mailed on Mar. 14, 2024, 78 pages. [cited by applicant]
U.S. Appl. No. 18/304,161, Notice of Allowance mailed on Mar. 19, 2024, 20 pages. [cited by applicant]
U.S. Appl. No. 18/326,447, Non-Final Office Action mailed on Jun. 12, 2024, 8 pages. [cited by applicant]
U.S. Appl. No. 18/332,462, Final Office Action mailed on Jul. 25, 2024, 26 pages. [cited by applicant]
U.S. Appl. No. 18/332,462, Non-Final Office Action, Mailed On Apr. 25, 2024, 18 pages. [cited by applicant]
Chapman et al., “Provenance and the Price of Identity”, Provenance and Annotation of Data and Process, 2008, 15 pages. [cited by applicant]
Mahajan et al., “Effective and Efficient Compromise Recovery for Weakly Consistent Replication”, Microsoft Research, Silicon Valley, 2009, pp. 131-144. [cited by applicant]
Tremel et al., “Reliable, Efficient Recovery for Complex Services with Replicated Subsystems”, Institute of Electrical and Electronics Engineers, 2020, 12 pages. [cited by applicant]
International Application No. PCT/US2023/024235, International Search Report and Written Opinion mailed on Sep. 4, 2023, 13 pages. [cited by applicant]
International Application No. PCT/US2023/024236, International Search Report and Written Opinion mailed on Sep. 6, 2023, 10 pages. [cited by applicant]
International Application No. PCT/US2023/024239, International Search Report and Written Opinion mailed on Aug. 11, 2023, 14 pages. [cited by applicant]
International Application No. PCT/US2023/024835, International Search Report and Written Opinion mailed on Aug. 8, 2023, 14 pages. [cited by applicant]
International Application No. PCT/US2023/025194, International Search Report and Written Opinion mailed on Aug. 18, 2023, 13 pages. [cited by applicant]
“Announcing Amazon Elastic File System Replication” Available Online at: https://aws.amazon.com/about-aws/whats-new/2022/01/amazon-elastic-file-system-replication/, Jan. 25, 2022, 2 pages. [cited by applicant]
“Amazon EFS replication”, Amazon Elastic File System, Available Online at: https://docs.aws.amazon.com/efs/latest/ug/efs-replication.html, Oct. 3, 2022, 18 pages. [cited by applicant]
“About Consistency Group Snapshot Restore”, Working with consistency groups, Available Online at: https://sort.veritas.com/public/documents/HSO/2.0/linux/productguides/html/hfo_admin_ubuntu/ch07s10.htm, 2 pages. [cited by applicant]
“About HyperScale Consistency Groups”, Working with consistency groups, Available Online at: https://sort.veritas.com/public/documents/HSO/2.0/linux/productguides/html/hfo_admin_ubuntu/ch07s02.htm, 1 page. [cited by applicant]
“AWS KMS concepts”, AWS Key Management Service, Available Online at: https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#kms_keys, Oct. 3, 2022, 36 pages. [cited by applicant]
“Caringo's Swarm Hybrid Cloud Object Storage Platform Now Integrated with Reach Engine by Levels Beyond and Microsoft Azure Broadcast Beat”, Production Industry Resource, Available Online at: https://www.broadcastbeat.c… [cited by applicant]
“Caringo Swarm Hybrid Cloud for Azure”, Available Online at: https://azure.github.io/Storage/docs/storage-partners/partners/MultiProtocol/Caringo-Azure.pdf, 2017, 1 page. [cited by applicant]
“Create Amazon EBS Snapshots”, Available Online at: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-creating-snapshot.html, 2022, 4 pages. [cited by applicant]
“Create Consistency Groups”, Available Online at: https://library.netapp.com/ecmdocs/ECMP12404965/html/GUID-AA34DCF7-6827-4ACC-AA5E-63B1FEA8EFCE.html, Jan. 2016, 2 pages. [cited by applicant]
“How AWS DataSync works”, AWS DataSync, Available Online at: https://docs.aws.amazon.com/datasync/latest/userguide/how-datasync-works.html, Oct. 3, 2022, 5 pages. [cited by applicant]
“How File Replicator works”, Veritas, Available Online at: https://sort.veritas.com/public/documents/vie/7.0/linux/productguides/html/infoscale_replication_admin/c h02s02.html, Oct. 3, 2022, 1 page. [cited by applicant]
“Replication for File System Agents”, Available Online at: https://documentation.commvault.com/v11/essential/129963_replication_for_file_system_agents.html, Dec. 7, 2021, 2 pages. [cited by applicant]
Mashtizadeh et al., “Replication, History, and Grafting in the Ori File System” https://www.scs.stanford.edu/˜dm/home/papers/mashtizadeh:ori.pdf, Nov. 3-6, 2013, pp. 151-166. [cited by applicant]
“Snapshot Schedules and Snapshot Consistency Groups”, Available Online at: https://thinksystem.lenovofiles.com/storage/help/index.jsp?topic=%2Fthinksystem_system_manager_11.50.1%2F34EADFOC-B783-4FED-B187-28B016EE22B6_.h… [cited by applicant]
“Snapshotting a Consistency Group”, Available Online at: https://www.IBM.com/docs/en/xiv-storage-system?topic=commands-snapshotting-consistency-group, Jun. 12, 2022, 5 pages. [cited by applicant]
“The Definitive Guide to Rubrik Cloud Data Management”, Available Online at: https://www.rubrik.com/content/dam/rubrik/en/resources/white-paper/Definitive-guide-rubrik-cloud-data-management.pdf, Jun. 8, 2021, 41 pages. [cited by applicant]
“What is AWS DataSync”, AWS, Available Online at: DataSynchttps://docs.aws.amazon.com/datasync/latest/userguide/what-is-datasync.html, Oct. 3, 2022, 3 pages. [cited by applicant]
“CephFS Mirroring”, Ceph Internals, Available online at: https://docs.ceph.com/en/reef/dev/cephfs-mirroring/, 2016, 9 pages. [cited by applicant]
“Google Scholar/Patents Search—Text Refined”, Available online at: https://patents.google.com/?g=(file+system+replication+failure+binary+tree+pairs)&scholar&og=file+system+replication+failure+binary+tree+pairs, Accessed… [cited by applicant]
“SnapshotIQ”, Available online at: https://infohub.delltechnologies.com/en-US/l/high-availability-and-data-protection-with-dell-powerscale-scale-out-nas/snapshots-116/, 4 pages. [cited by applicant]
U.S. Appl. No. 17/991,688 , Non-Final Office Action, Mailed On Nov. 19, 2024, 11 pages. [cited by applicant]
U.S. Appl. No. 18/094,302 , Notice of Allowance, Mailed On Nov. 29, 2024, 14 pages. [cited by applicant]
U.S. Appl. No. 18/181,414, Notice of Allowance, mailed On Sep. 30, 2024, 12 pages. [cited by applicant]
U.S. Appl. No. 18/304,226, Non-Final Office Action, mailed On Nov. 19, 2024, 16 pages. [cited by applicant]
U.S. Appl. No. 18/332,475, Non-Final Office Action, mailed On Dec. 19, 2024, 15 pages. [cited by applicant]
U.S. Appl. No. 18/536,067, Non-Final Office Action, mailed On Jan. 29, 2025, 17 pages. [cited by applicant]
U.S. Appl. No. 18/646,676, Notice of Allowance, mailed On Jan. 2, 2025, 21 pages. [cited by applicant]
Khurana et al., “Efficient Snapshot Retrieval Over Historical Graph Data”, Institute of Electrical and Electronics Engineers, Jul. 24, 2012, pp. 997-1008. [cited by applicant]
LAPP , “Busting the Buffer Myth for Multicast Media Over IP”, Available Online at: https://blogs.cisco.com/sp/busting-the-buffer-myth-for-multicast-media-over-ip, Feb. 22, 2021, 9 pages. [cited by applicant]
U.S. Appl. No. 17/991,688, Notice of Allowance mailed on Mar. 7, 2025, 8 pages. [cited by applicant]
U.S. Appl. No. 18/094,302, Notice of Allowance mailed on Mar. 13, 2025, 14 pages. [cited by applicant]
U.S. Appl. No. 18/169,124, Notice of Allowance mailed on Mar. 20, 2025, 13 pages. [cited by applicant]
U.S. Appl. No. 18/497,877, Non-Final Office Action mailed on Mar. 3, 2025, 25 pages. [cited by applicant]
U.S. Appl. No. 18/508,990, Non-Final Office Action mailed on Mar. 3, 2025, 11 pages. [cited by applicant]
Chang et al., Job Scheduling and Data Replication on Data Grids, Future Generation Computer Systems, vol. 23, No. 7, Aug. 2007, pp. 846-860. [cited by applicant]
U.S. Appl. No. 18/304,226, “Final Office Action”, mailed Apr. 4, 2025, 20 pages. [cited by applicant]
U.S. Appl. No. 18/521,176, “Non-Final Office Action”, mailed Apr. 4, 2025, 6 pages. [cited by applicant]