IP Library Granted Patent US 12,711,239
Granted Patent B2
US 12,711,239 · App. 18/499,023 · Granted Aug 18, 2026

Scanning a backup for vulnerabilities

Inventors: Nagapramod Mandagere (Los Altos, CA); Karandeep Singh Chawla (Santa Clara, CA); Virupaksha Kanjilal (Baltimore, MD); Nilesh Pathak (Sunnyvale, CA)
Assignee: Cohesity, Inc.
G06F21/577G06F11/1446G06F11/1469G06F2201/84G06F2221/033
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,711,239
App. No.
18/499,023
Filed
Oct 31, 2023
Granted
Aug 18, 2026
Kind
B2
Art Unit
2439
USPC
726/25
Abstract

A request associated with identifying a backup snapshot to restore among a plurality of backup snapshots is received. At least a first scanned backup snapshot of the plurality of backup snapshots was scanned for one or more vulnerabilities. In response to the request associated with identifying the backup snapshot to restore among the plurality of backup snapshots, a predetermined identification of one or more vulnerabilities of the first scanned backup snapshot is provided via a display interface. The predetermined identification indicates corresponding criticalities of the one or more vulnerabilities of the first scanned backup snapshot. A request to restore a scanned portion of the first scanned backup snapshot is received via the display interface. Data associated with the request to restore the scanned portion of the first scanned backup snapshot is provided.

Claims (39)

1 . A method, comprising:

receiving a request, from a requesting system, for identifying a backup snapshot to restore among a plurality of backup snapshots, wherein at least a scanned backup snapshot of the plurality of backup snapshots was scanned for one or more vulnerabilities;

in response to the request for identifying the backup snapshot to restore among the plurality of backup snapshots, providing, via a display interface, a predetermined identification of one or more vulnerabilities of the scanned backup snapshot, wherein the predetermined identification indicates (1) corresponding criticalities of the one or more vulnerabilities of the scanned backup snapshot and (2) a plurality of recovery times corresponding to restoring respective scanned portions of the scanned backup snapshot;

receiving, via the display interface, a request to restore a scanned portion of the scanned backup snapshot;

locating data of the scanned portion of the scanned backup snapshot by traversing a portion of a tree data structure corresponding to the scanned portion; and

providing the data of the scanned portion of the scanned backup snapshot to the requesting system, in order to apply one or more remedies corresponding to the one or more vulnerabilities of the scanned backup snapshot.

2 . The method of claim 1 , wherein the scanned portion is an entire portion of the scanned backup snapshot.

3 . The method of claim 1 , wherein the scanned portion is part of the scanned backup snapshot.

4 . The method of claim 1 , wherein the corresponding criticalities of the one or more vulnerabilities of the scanned backup snapshot include one or more of: very critical, critical, or non-critical.

5 . The method of claim 1 , wherein in response to the request associated with identifying the backup snapshot to restore among the plurality of backup snapshots further includes providing a recovery time of the plurality of recovery times, the recovery time associated with restoring the requested scanned portion of the scanned backup snapshot.

6 . The method of claim 5 , wherein the recovery time associated with restoring the requested scanned portion of the scanned backup snapshot is based on a security posture of a restore environment in which the scanned portion of the scanned backup snapshot is to be restored.

7 . The method of claim 6 , wherein the security posture is a high security posture, and wherein an amount of time to remedy the one or more vulnerabilities of the scanned backup snapshot in the restore environment having the high security posture is included in the provided recovery time associated with restoring the requested scanned portion of the scanned backup snapshot.

8 . The method of claim 6 , wherein the security posture is a medium security posture, and wherein an amount of time to remedy critical and very critical vulnerabilities of the one or more vulnerabilities of the scanned backup snapshot in the restore environment having the medium security posture is included in the provided recovery time associated with restoring the requested scanned portion of the scanned backup snapshot.

9 . The method of claim 6 , wherein the security posture is a low security posture, and wherein the recovery time associated with restoring the requested scanned portion of the scanned backup snapshot in the restore environment having the low security posture excludes an amount of time to remedy any of the one or more vulnerabilities of the scanned backup snapshot.

10 . The method of claim 6 , wherein the recovery time associated with restoring the requested scanned portion of the scanned backup snapshot is further based on an amount of time for providing to the restore environment the data associated with the requested scanned portion of the scanned backup snapshot.

11 . The method of claim 1 , further comprising: filtering one or more versions of the scanned portion based on a security posture selected by a user via the display interface.

12 . The method of claim 1 , further comprising: determining a sequence of the one or more remedies to be applied to the data associated with the scanned portion.

13 . The method of claim 1 , further comprising:

filtering the one or more vulnerabilities of the scanned backup snapshot based on a restore environment in which the scanned portion of the scanned backup snapshot is to be restored; and

determining the plurality of recovery times based on the filtering of the one or more vulnerabilities.

14 . A computer program product, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:

receiving a request, from a requesting system, for identifying a backup snapshot to restore among a plurality of backup snapshots, wherein at least a scanned backup snapshot of the plurality of backup snapshots was scanned for one or more vulnerabilities;

in response to the request for identifying the backup snapshot to restore among the plurality of backup snapshots, providing, via a display interface, a predetermined identification of one or more vulnerabilities of the scanned backup snapshot, wherein the predetermined identification indicates (1) corresponding criticalities of the one or more vulnerabilities of the scanned backup snapshot and (2) a plurality of recovery times corresponding to restoring respective scanned portions of the scanned backup snapshot;

receiving, via the display interface, a request to restore a scanned portion of the scanned backup snapshot;

locating data of the scanned portion of the scanned backup snapshot by traversing a portion of a tree data structure corresponding to the scanned portion; and

providing the data of the scanned portion of the scanned backup snapshot to the requesting system, in order to apply one or more remedies corresponding to the one or more vulnerabilities of the scanned backup snapshot.

15 . The computer program product of claim 14 , wherein the corresponding criticalities of the one or more vulnerabilities of the scanned backup snapshot include one or more of: very critical, critical, or non-critical.

16 . The computer program product of claim 14 , wherein in response to the request associated with identifying the backup snapshot to restore among the plurality of backup snapshots further includes providing a recovery time of the plurality of recovery times, the recovery time associated with restoring the requested scanned portion of the scanned backup snapshot.

17 . The computer program product of claim 16 , wherein the recovery time associated with restoring the requested scanned portion of the scanned backup snapshot is based on a security posture of a restore environment in which the scanned portion of the scanned backup snapshot is to be restored.

18 . The computer program product of claim 17 , wherein the security posture of the restore environment is a high security posture, a medium security posture, or a low security posture.

19 . The computer program product of claim 17 , wherein the recovery time associated with restoring the requested scanned portion of the scanned backup snapshot is further based on an amount of time for providing to the restore environment the data associated with the requested scanned portion of the scanned backup snapshot.

20 . A system, comprising:

a processor; and

a memory coupled with the processor, wherein the memory is configured to provide the processor with instructions which when executed cause the processor to:

receive a request, from a requesting system, for identifying a backup snapshot to restore among a plurality of backup snapshots, wherein at least a scanned backup snapshot of the plurality of backup snapshots was scanned for one or more vulnerabilities;

in response to the request for identifying the backup snapshot to restore among the plurality of backup snapshots, providing, via a display interface, a predetermined identification of one or more vulnerabilities of the scanned backup snapshot, wherein the predetermined identification indicates (1) corresponding criticalities of the one or more vulnerabilities of the scanned backup snapshot and (2) a plurality of recovery times corresponding to restoring respective scanned portions of the scanned backup snapshot;

receive, via the display interface, a request to restore a scanned portion of the scanned backup snapshot;

locate data of the scanned portion of the scanned backup snapshot by traversing a portion of a tree data structure corresponding to the scanned portion; and

provide the data of the request to restore the scanned portion of the scanned backup snapshot to the requesting system, in order to apply one or more remedies corresponding to the one or more vulnerabilities of the scanned backup snapshot.

Assignments (2)
SECURITY INTEREST Recorded Dec 9, 2024
From: VERITAS TECHNOLOGIES LLC; COHESITY, INC.
To: JPMORGAN CHASE BANK. N.A.
Reel/Frame 069890/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 19, 2024
From: MANDAGERE, NAGAPRAMOD; CHAWLA, KARANDEEP SINGH; KANJILAL, VIRUPAKSHA; PATHAK, NILESH
To: COHESITY, INC.
Reel/Frame 066181/0027 →
Continuity (3)
Continuation 17573483 · Jan 11, 2022
Continuation 16660521 · Oct 22, 2019
Related Publication 20240061940A1 · Feb 22, 2024
References Cited (207)
US 6061769A · Kapulka · 2000 [cited by applicant]
US 7421648B1 · Davis · 2008 [cited by applicant]
US 7437764B1 · Sobel · 2008 [cited by examiner]
US 8020037B1 · Schwartz · 2011 [cited by applicant]
US 8086585B1 · Brashers · 2011 [cited by applicant]
US 8112661B1 · La France · 2012 [cited by applicant]
US 8190583B1 · Shekar · 2012 [cited by applicant]
US 8312471B2 · Davis · 2012 [cited by applicant]
US 8364648B1 · Sim-Tang · 2013 [cited by applicant]
US 8607342B1 · Liao · 2013 [cited by applicant]
US 9268689B1 · Chen · 2016 [cited by applicant]
US 9304864B1 · Bushman · 2016 [cited by applicant]
US 9311190B1 · Bushman · 2016 [cited by applicant]
US 9361185B1 · Bushman · 2016 [cited by applicant]
US 9471441B1 · Lyadvinsky · 2016 [cited by applicant]
US 9489230B1 · Patwardhan · 2016 [cited by applicant]
US 9594514B1 · Bono · 2017 [cited by applicant]
US 9621428B1 · Lev · 2017 [cited by applicant]
US 9983812B1 · Don · 2018 [cited by applicant]
US 10037223B2 · Park · 2018 [cited by applicant]
US 10089148B1 · Blitzer · 2018 [cited by applicant]
US 10162528B2 · Sancheti · 2018 [cited by applicant]
US 10169077B1 · Sigl, Sr. · 2019 [cited by applicant]
US 10175896B2 · Battaje · 2019 [cited by applicant]
US 10216449B1 · Li · 2019 [cited by examiner]
US 10229269B1 · Patton et al. · 2019 [cited by applicant]
US 10275321B1 · Bajaj · 2019 [cited by applicant]
US 10460107B2 · Crofton · 2019 [cited by examiner]
US 10496497B1 · Yadav · 2019 [cited by applicant]
US 10503516B1 · Faibish et al. · 2019 [cited by applicant]
US 10503612B1 · Wang · 2019 [cited by applicant]
US 10545776B1 · Kowalski · 2020 [cited by applicant]
US 10650146B1 · Gaurav et al. · 2020 [cited by applicant]
US 10877928B2 · Nagrale · 2020 [cited by applicant]
US 10896097B1 · Purcell · 2021 [cited by applicant]
US 10943011B2 · Gaurav et al. · 2021 [cited by applicant]
US 10956374B2 · Shui et al. · 2021 [cited by applicant]
US 11036594B1 · Shats · 2021 [cited by applicant]
US 11176154B1 · Dasgupta · 2021 [cited by applicant]
US 11250136B2 · Mandagere et al. · 2022 [cited by applicant]
US 11275834B1 · Offer · 2022 [cited by applicant]
US 11841953B2 · Mandagere et al. · 2023 [cited by applicant]
US 11983270B2 · Gaurav et al. · 2024 [cited by applicant]
US 20030033344A1 · Abbott · 2003 [cited by applicant]
US 20040243775A1 · Coulter et al. · 2004 [cited by applicant]
US 20040250033A1 · Prahlad · 2004 [cited by applicant]
US 20060069861A1 · Amano · 2006 [cited by applicant]
US 20060182255A1 · Luck, Jr. · 2006 [cited by applicant]
US 20070153675A1 · Baglin · 2007 [cited by applicant]
US 20080047013A1 · Claudatos et al. · 2008 [cited by applicant]
US 20080208926A1 · Smoot · 2008 [cited by applicant]
US 20090089657A1 · Davis · 2009 [cited by applicant]
US 20090171707A1 · Bobak · 2009 [cited by applicant]
US 20090313503A1 · Atluri · 2009 [cited by applicant]
US 20090319449A1 · Gamon et al. · 2009 [cited by applicant]
US 20100031170A1 · Carullo · 2010 [cited by applicant]
US 20100070725A1 · Prahlad · 2010 [cited by applicant]
US 20100106933A1 · Kamila · 2010 [cited by applicant]
US 20100122248A1 · Robinson · 2010 [cited by applicant]
US 20110022879A1 · Chavda · 2011 [cited by applicant]
US 20110078497A1 · Lyne et al. · 2011 [cited by applicant]
US 20110106776A1 · Torbjorn · 2011 [cited by applicant]
US 20110107246A1 · Torbjorn · 2011 [cited by applicant]
US 20120203742A1 · Goodman · 2012 [cited by applicant]
US 20130006943A1 · Chavda · 2013 [cited by applicant]
US 20130179481A1 · Halevy · 2013 [cited by applicant]
US 20130191347A1 · Bensinger · 2013 [cited by applicant]
US 20130219135A1 · Knowles · 2013 [cited by applicant]
US 20130227558A1 · Du · 2013 [cited by applicant]
US 20130232480A1 · Winterfeldt · 2013 [cited by applicant]
US 20130232497A1 · Jalagam · 2013 [cited by applicant]
US 20130254402A1 · Anand · 2013 [cited by applicant]
US 20130322335A1 · Smith · 2013 [cited by applicant]
US 20140007239A1 · Sharpe et al. · 2014 [cited by applicant]
US 20140040206A1 · Ramakrishnan · 2014 [cited by applicant]
US 20140052692A1 · Zhang · 2014 [cited by applicant]
US 20140059306A1 · Bender · 2014 [cited by applicant]
US 20140165060A1 · Muller · 2014 [cited by applicant]
US 20140297588A1 · Babashetty · 2014 [cited by applicant]
US 20140359229A1 · Cota-Robles · 2014 [cited by applicant]
US 20140372553A1 · Blackburn · 2014 [cited by applicant]
US 20150149411A1 · Plisko et al. · 2015 [cited by applicant]
US 20150193487A1 · Demidov · 2015 [cited by applicant]
US 20150254150A1 · Gordon · 2015 [cited by applicant]
US 20150278046A1 · Zellermayer · 2015 [cited by applicant]
US 20150347242A1 · Martos · 2015 [cited by applicant]
US 20150363270A1 · Hammer · 2015 [cited by applicant]
US 20150370502A1 · Aron · 2015 [cited by applicant]
US 20150378765A1 · Singh · 2015 [cited by applicant]
US 20160004450A1 · Lakshman · 2016 [cited by applicant]
US 20160034356A1 · Aron · 2016 [cited by applicant]
US 20160048408A1 · Madhu · 2016 [cited by applicant]
US 20160070714A1 · Janice · 2016 [cited by applicant]
US 20160085636A1 · Dornemann · 2016 [cited by applicant]
US 20160098323A1 · Mutha · 2016 [cited by applicant]
US 20160125059A1 · Jain · 2016 [cited by applicant]
US 20160162378A1 · Garlapati · 2016 [cited by applicant]
US 20160188898A1 · Karinta · 2016 [cited by applicant]
US 20160203060A1 · Singh · 2016 [cited by applicant]
US 20160232061A1 · Gaschler · 2016 [cited by applicant]
US 20160283329A1 · Natanzon · 2016 [cited by examiner]
US 20160321339A1 · Tekade · 2016 [cited by applicant]
US 20160357640A1 · Bushman · 2016 [cited by applicant]
US 20160357641A1 · Bushman · 2016 [cited by applicant]
US 20160357769A1 · Bushman · 2016 [cited by applicant]
US 20160378988A1 · Bhashkar et al. · 2016 [cited by applicant]
US 20170031613A1 · Lee · 2017 [cited by applicant]
US 20170031622A1 · Nagarajan · 2017 [cited by applicant]
US 20170060710A1 · Ramani · 2017 [cited by applicant]
US 20170060884A1 · Goodman · 2017 [cited by applicant]
US 20170123935A1 · Pandit · 2017 [cited by applicant]
US 20170168903A1 · Dornemann · 2017 [cited by applicant]
US 20170177867A1 · Crofton et al. · 2017 [cited by applicant]
US 20170185491A1 · Hajare · 2017 [cited by applicant]
US 20170185729A1 · Boray · 2017 [cited by applicant]
US 20170193116A1 · Wong · 2017 [cited by applicant]
US 20170206212A1 · Srivilliputtur Mannarswamy · 2017 [cited by applicant]
US 20170212680A1 · Waghulde · 2017 [cited by applicant]
US 20170279615A1 · Naik · 2017 [cited by applicant]
US 20170337109A1 · Ramu · 2017 [cited by applicant]
US 20180004437A1 · Battaje · 2018 [cited by applicant]
US 20180004764A1 · Sudarsanam · 2018 [cited by applicant]
US 20180034772A1 · Sun et al. · 2018 [cited by applicant]
US 20180060106A1 · Madtha · 2018 [cited by applicant]
US 20180060187A1 · Chavda · 2018 [cited by applicant]
US 20180081766A1 · Ghuge · 2018 [cited by applicant]
US 20180081902A1 · Mckenzie · 2018 [cited by applicant]
US 20180088973A1 · Subhraveti · 2018 [cited by applicant]
US 20180095846A1 · Sanakkayala · 2018 [cited by applicant]
US 20180113625A1 · Sancheti · 2018 [cited by applicant]
US 20180196820A1 · Kremer · 2018 [cited by applicant]
US 20180212896A1 · Chang · 2018 [cited by applicant]
US 20180253414A1 · Hailpern · 2018 [cited by applicant]
US 20180293120A1 · Arora · 2018 [cited by examiner]
US 20180293374A1 · Chen · 2018 [cited by applicant]
US 20180316577A1 · Freeman · 2018 [cited by applicant]
US 20180329637A1 · Battaje · 2018 [cited by applicant]
US 20190065277A1 · Raikov · 2019 [cited by applicant]
US 20190073276A1 · Yuen · 2019 [cited by applicant]
US 20190108266A1 · Manvar · 2019 [cited by applicant]
US 20190108341A1 · Bedhapudi et al. · 2019 [cited by applicant]
US 20190129799A1 · Kumarasamy · 2019 [cited by applicant]
US 20190132203A1 · Wince · 2019 [cited by applicant]
US 20190197020A1 · Yap · 2019 [cited by applicant]
US 20190215358A1 · Kobayashi · 2019 [cited by applicant]
US 20190220198A1 · Kashi Visvanathan · 2019 [cited by applicant]
US 20190228097A1 · Kassa · 2019 [cited by applicant]
US 20190235973A1 · Brewer et al. · 2019 [cited by applicant]
US 20190278662A1 · Nagrale · 2019 [cited by applicant]
US 20190278663A1 · Mehta · 2019 [cited by applicant]
US 20190286533A1 · O'Mahony et al. · 2019 [cited by applicant]
US 20200026538A1 · Cui · 2020 [cited by applicant]
US 20200034254A1 · Natanzon · 2020 [cited by applicant]
US 20200042703A1 · Herman Saffar et al. · 2020 [cited by applicant]
US 20200057567A1 · Hutcheson · 2020 [cited by applicant]
US 20200057669A1 · Hutcheson · 2020 [cited by applicant]
US 20200099699A1 · Saad · 2020 [cited by applicant]
US 20200110755A1 · Waldman · 2020 [cited by applicant]
US 20200159625A1 · Hutcheson · 2020 [cited by applicant]
US 20200167238A1 · Killamsetti · 2020 [cited by applicant]
US 20200183794A1 · Dwarampudi · 2020 [cited by applicant]
US 20200233571A1 · Yuravlivker · 2020 [cited by applicant]
US 20200278274A1 · Shetty · 2020 [cited by applicant]
US 20200285449A1 · Mcintosh · 2020 [cited by applicant]
US 20200394072A1 · Sreekantaswamy · 2020 [cited by applicant]
US 20210056203A1 · Qiao · 2021 [cited by applicant]
US 20210081087A1 · Wayne · 2021 [cited by applicant]
US 20210103556A1 · Nagrale · 2021 [cited by applicant]
US 20210232579A1 · Schechter · 2021 [cited by applicant]
US 20210318851A1 · Sahu · 2021 [cited by applicant]
US 20210385254A1 · Pettit · 2021 [cited by applicant]
CN 106126371A · 2016 [cited by applicant]
“Recovering File from an Amazon EBS Volume Backup”—Josh Rad, AWS, Feb. 1, 2019 https://aws.amazon.com/blogs/compute/recovering-files-from-an-amazon-ebs-volume-backup/ (Year: 2019). [cited by examiner]
“Disaster Recovery Guide: DR in Virtualized Environments”—Zerto, Sep. 2016 https://www.insight.com/content/dam/insight-web/en_US/pdfs/zerto/zerto-disaster-recovery-guide.pdf (Year: 2016). [cited by examiner]
Author Unknown, Carl Eschenbach, Sequoia Capital & Lynn Lucas, Cohesity CUBE Conversation, Aug. 2019, Youtube, Aug. 15, 2019, https://www.youtube.com/watch?v=mYMlwy8ZKuQ. [cited by applicant]
Author Unknown, Cohesity CyberScan: Leverage Backup Data to Respond to Cyber Threats, Youtube, Aug. 1, 2019, https://www.youtube.com/watch?v=VLjauRFm5Sw. [cited by applicant]
Author Unknown, Rawlinson Rivera, Cohesity & Brock Mowry, Whoa, VMworld 2019, Youtube, Aug. 27, 2019, https://www.youtube.com/watch?v=njGfrgRh-NE. [cited by applicant]
Author Unknown, Vulnerability Protection with CyberScan, Youtube, Sep. 9, 2019, https://www.youtube.com/watch?v=R1upyfXRtbQ. [cited by applicant]
Jessica Lyons Hardcastle, Cohesity Adds Security Capabilities With CyberScan, SDxCentral, Aug. 1, 2019, https://www.sdxcentral.com/articles/news/cohesity-adds-security-capabilities-with-cyberscan/2019/08/. [cited by applicant]
Johnny Yu, Cohesity CyberScan Scans Backup Copies for Security Risks, TechTarget, Aug. 2, 2019, https://www.techtarget.com/searchdatabackup/news/252467832/Cohesity-CyberScan-scans-backup-copies-for-security-risks. [cited by applicant]
Mark Cox, Cohesity Lets Vulnerabilities be Scanned in Backups with New CyberScan Application, channelbuzz.ca, Aug. 1, 2019, https://channelbuzz.ca/2019/08/cohesity-lets-vulnerabilities-be-scanned-in-backups-with-new-cyb… [cited by applicant]
Michael Rink, Cohesity Expands Security Capabilities, StorageReview, Aug. 1, 2019, https://www.storagereview.com/news/cohesity-expands-security-capabilities. [cited by applicant]
Stephen Withers, Cohesity CyberScan Checks Backups for Vulnerabilities, ITWire, Aug. 1, 2019, https://itwire.com/business-it-news/security/cohesity-cyberscan-checks-backup-for-vulnerabilities.html. [cited by applicant]
Response to Extended Search Report dated Mar. 18, 2024, from counterpart European Application No. 23216744.5 filed Oct. 16, 2024, 21 pp. [cited by applicant]
“Backup Solution Guide”—Synology https://download.synology.com/download/www-res/brochure/backup_solution_guide_en-global .pdf (Year: 2019). [cited by applicant]
“Own DIY Cloud Backup Solution with 8TB Hard Disk and Synology”—Mac & Egg, Jun. 2019 https://macandegg.com/2019/06/own-diy-cloud-backup-solution-with-8-tb-hard-disk-and-synology/ (Year: 2019). [cited by applicant]
Actifio. “Getting Started with Actifio VDP.” Sep. 23, 2020. https://web.archive.org/web/20200923181125/https://docs.actifio.com/10.0/PDFs/Introducing.pdf (Year: 2020). [cited by applicant]
C. Grace. “Site Recovery Manager Technical Overview.” Dec. 1, 2020. https://web.archive.org/web/20201201181602/https://core.vmware.com/resource/site-recovery-manager-technical-overview (Year: 2020). [cited by applicant]
Cloud Endure. “Cloud Endure Documentation.” Dec. 1, 2020. https://web.archive.org/web/20201201022045/https://docs.cloudendure.com/CloudEndure%20Documentation.htm (Year: 2020). [cited by applicant]
Cohesity, Cohesity Data Protection White Paper, 2016, Cohesity, pp. 1-12 (Year: 2016). [cited by applicant]
Gaetan Castlelein, Cohesity SnapFS and SnapTree, Aug. 9, 2017, Cohesity, pp. 1-4 (Year: 2017). [cited by applicant]
M. Chuang. “Announcing VMware Cloud Disaster Recovery.” Sep. 29, 2020. https://web.archive.org/web/20201102133037/https://blogs.vmware.com/virtualblocks/2020/09/29/announcing-vmware-cloud-disaster-recovery/ (Year: 2020). [cited by applicant]
M. Mclaughlin. “VMware Cloud Disaster Recovery is Now Available.” Oct. 20, 2020. https://web.archive.org/web/20201103021801/https://blogs.vmware.com/virtualblocks/2020/10/20/vmware-cloud-disaster-recovery-is-now-availab… [cited by applicant]
Red Hat. “Red Hat Virtualization 4.3 Disaster Recovery Guide.” Jul. 17, 2019. https://web.archive.org/web/20190717013417/https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html/disaster_recovery_gu… [cited by applicant]
Red Hat. “Red Hat Virtualization 4.3 Product Guide.” Jul. 17, 2019. https://web.archive.org/web/20190717013254/https://access.redhat.com/documentation/en-us/red_hat_ virtualization/4.3/html/product_guide/index (Year: 20… [cited by applicant]
VMware. “Site Recovery Manager Administration.” May 31, 2019. https://docs.vmware.com/en/Site-Recovery-Manager/8.5/srm-admin-8-5.pdf (Year: 2019). [cited by applicant]
VMware. “Site Recovery Manager Evaluation Guide.” Oct. 19, 2020. https://web.archive.org/web/20201019155135/https://core.vmware.com/resource/site-recovery-manager-evaluation-guide (Year: 2020). [cited by applicant]
Zerto. “Zerto Disaster Recovery Guide.” Sep. 2016. https://www.zerto.com/wp-content/uploads/2016/09/Zerto-Disaster-Recovery-Guide_CIO_eBook.pdf (Year: 2016). [cited by applicant]
Extended Search Report from counterpart European Application No. 23216744.5 dated Mar. 18, 2024, 5 pp. [cited by applicant]
International Preliminary Report on Patentability from International Application No. PCT/US2020/056370 dated Apr. 26, 2022, 6 pp. [cited by applicant]
International Search Report and Written Opinion of International Application No. PCT/US2020/056370 dated Jan. 13, 2021, 8 pp. [cited by applicant]
Notice of Intent to Grant and Text Intended to Grant from counterpart European Application No. 20804117.8 dated Jul. 4, 2023, 99 pp. [cited by applicant]
Prosecution History from U.S. Appl. No. 16/660,521, now issued U.S. Pat. No. 11,250,136, dated Jan. 28, 2020 through Oct. 20, 2021, 86 pp. [cited by applicant]
Prosecution History from U.S. Appl. No. 17/573,483, now issued U.S. Pat. No. 11,841,953, dated Feb. 8, 2022 through Aug. 23, 2023, 59 pp. [cited by applicant]
Extended Search Report from counterpart European Application No. 25195045.7 dated Oct. 17, 2025, 9 pp. [cited by applicant]
First Office Action and Search Report, and translation thereof, from counterpart Chinese Application No. 202080073488.4 dated Apr. 17, 2026, 12 pp. [cited by applicant]
Response to Extended Search Report dated Oct. 17, 2025, from counterpart European Application No. 25195045.7 filed May 12, 2026, 20 pp. [cited by applicant]