IP Library Granted Patent US 12,259,798
Granted Patent B2
US 12,259,798 · App. 18/229,008 · Granted Mar 25, 2025

Automatically implementing a specification of a data protection intent

Inventors: Chinmaya Manjunath (San Jose, CA); Colin Scott Johnson (San Francisco, CA); Amitabh Sinha (Fremont, CA); Dayanand Sharma (Santa Clara, CA); Prakash Veljibhai Vaghela (Pune, IN); Karandeep Singh Chawla (Santa Clara, CA)
Assignee: Cohesity, Inc.
G06F11/2023G06F11/008G06F11/1448G06F11/1458G06F11/3051
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,259,798
App. No.
18/229,008
Granted
Mar 25, 2025
Kind
B2
Abstract

A current configuration of one or more data management services is monitored. It is determined that the current configuration is insufficient to achieve a data protection intent indicated by a specification of the data protection intent. In response to determining that the current configuration is insufficient to achieve the data protection intent indicated by the specification of the data protection intent, the current configuration of the one or more data management services is modified in a manner to achieve the data protection intent indicated by the specification of the data protection intent.

Claims (31)

1. A method, comprising:

monitoring a current configuration of one or more data management services;

executing a machine learning model that determines the current configuration is insufficient to achieve a data protection intent indicated by a specification of the data protection intent and determines one or more modifications to the current configuration that, when applied, would achieve the data protection intent indicated by the specification of the data protection intent; and

in response to determining that the current configuration is insufficient to achieve the data protection intent indicated by the specification of the data protection intent, modifying, based on the one or more modifications, the current configuration of the one or more data management services in a manner that achieves the data protection intent indicated by the specification of the data protection intent.

2. The method of claim 1 , wherein the data protection intent specifies at least a recovery point objective (RPO) and a recovery time objective (RTO).

3. The method of claim 2 , wherein connectivity issues associated with a primary site or a disaster recovery site cause the RPO or the RTO to be unachievable.

4. The method of claim 1 , wherein the data protection intent specification specifies a data pool that identifies one or more objects to be included in the data pool when a data management service of the one or more data management services is performed and the data management service to apply to the one or more objects to be included in the data pool.

5. The method of claim 4 , wherein the one or more objects to be included in the data pool share at least one of a tag, label, feature, and/or prefix.

6. The method of claim 4 , wherein a number of the objects included in the data pool has increased since a previous implementation of the one or more data management services.

7. The method of claim 6 , wherein the objects included in the data pool are virtual machines.

8. The method of claim 4 , wherein at least one of the one or more objects is a continuous data protection-enabled object.

9. The method of claim 4 , wherein the data management service is disaster recovery.

10. The method of claim 1 , wherein modifying the current configuration of the one or more data management services in the manner to achieve the data protection intent indicated by the specification of the data protection intent includes determining which of the one or more data management services are needed to implement a modified configuration to achieve the specified data protection intent.

11. The method of claim 1 , wherein modifying the current configuration of the one or more data management services in the manner to achieve the data protection intent indicated by the specification of the data protection intent includes determining a corresponding configuration for each of the determined one or more data management services.

12. The method of claim 1 , further comprising providing a notification that the current configuration of the one or more data management services is being modified.

13. The method of claim 12 , wherein the notification indicates how the current configuration of the one or more data management service is being modified.

14. A computer program product comprising non-transitory computer readable media storing computer instructions that, when executed, cause one or more processors to:

monitor a current configuration of one or more data management services;

execute a machine learning model that determines that the current configuration is insufficient to achieve a data protection intent indicated by a specification of the data protection intent and determines one or more modifications to the current configuration that, when applied, would achieve the data protection intent indicated by the specification of the data protection intent; and

in response to determining that the current configuration is insufficient to achieve the data protection intent indicated by the specification of the data protection intent, modify, based on the one or more determined modifications, the current configuration of the one or more data management services in a manner that achieves the data protection intent indicated by the specification of the data protection intent.

15. The computer program product of claim 14 , wherein the data protection intent specifies at least a recovery point objective (RPO) and a recovery time objective (RTO).

16. The computer program product of claim 15 , wherein connectivity issues associated with a primary site or a disaster recovery site cause the RPO or the RTO to be unachievable.

17. The computer program product of claim 14 , wherein the data protection intent specification specifies a data pool that identifies one or more objects to be included in the data pool when a data management service of the one or more data management services is performed and the data management service to apply to the one or more objects to be included in the data pool.

18. The computer program product of claim 17 , wherein the one or more objects to be included in the data pool share at least one of a tag, label, feature, and/or prefix.

19. The computer program product of claim 17 , wherein a number of the objects included in the data pool has increased since a previous implementation of the one or more data management services.

20. A system, comprising:

a memory configured to store instructions; and

one or more processors coupled to the memory and configured to execute the instructions to:

monitor a current configuration of one or more data management services;

execute a machine learning model that determines the current configuration is insufficient to achieve a data protection intent indicated by a specification of the data protection intent and determines one or more modifications that, when applied, would achieve the data protection intent indicated by the specification of the data protection intent; and

in response to determining that the current configuration is insufficient to achieve the data protection intent indicated by the specification of the data protection intent, modify, based on the one or more determined modifications, the current configuration of the one or more data management services in a manner that achieves the data protection intent indicated by the specification of the data protection intent.

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 10, 2024
From: MANJUNATH, CHINMAYA; JOHNSON, COLIN SCOTT; SINHA, AMITABH; SHARMA, DAYANAND; VAGHELA, PRAKASH VELJIBHAI; CHAWLA, KARANDEEP SINGH
To: COHESITY, INC.
Reel/Frame 066270/0019 →
Continuity (3)
Continuation 17534226 · Nov 23, 2021
Provisional Application 63122723 · Dec 8, 2020
Related Publication 20240020209A1 · Jan 18, 2024
References Cited (165)
US 7421648B1 · Davis · 2008 [cited by applicant]
US 7437764B1 · Sobel · 2008 [cited by applicant]
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 8261122B1 · Kappel · 2012 [cited by examiner]
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 10275321B1 · Bajaj · 2019 [cited by applicant]
US 10496497B1 · Yadav · 2019 [cited by applicant]
US 10503612B1 · Wang · 2019 [cited by applicant]
US 10545776B1 · Kowalski · 2020 [cited by applicant]
US 10877928B2 · Nagrale · 2020 [cited by applicant]
US 10896097B1 · Purcell · 2021 [cited by applicant]
US 10990284B1 · Savir · 2021 [cited by examiner]
US 11036594B1 · Shats · 2021 [cited by examiner]
US 11176154B1 · Dasgupta · 2021 [cited by applicant]
US 11768745B2 · Manjunath et al. · 2023 [cited by applicant]
US 20030033344A1 · Abbott · 2003 [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 20060236061A1 · Koclanes · 2006 [cited by examiner]
US 20070153675A1 · Baglin · 2007 [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 20090300409A1 · Bates · 2009 [cited by examiner]
US 20090313503A1 · Atluri · 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 20110106776A1 · Torbjorn · 2011 [cited by applicant]
US 20110107246A1 · Torbjorn · 2011 [cited by applicant]
US 20120089572A1 · Raichstein · 2012 [cited by examiner]
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 · Vibhor · 2013 [cited by applicant]
US 20130322335A1 · Smith · 2013 [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 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 · D Sa · 2016 [cited by applicant]
US 20160085636A1 · Dornemann · 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 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 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 20170139791A1 · Hagan · 2017 [cited by examiner]
US 20170168903A1 · Dornemann · 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 20170337109A1 · Ramu · 2017 [cited by applicant]
US 20180004437A1 · Battaje · 2018 [cited by applicant]
US 20180004764A1 · Sudarsanam · 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 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 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 20190278662A1 · Nagrale · 2019 [cited by applicant]
US 20190278663A1 · Mehta · 2019 [cited by applicant]
US 20200026538A1 · Cui · 2020 [cited by applicant]
US 20200034254A1 · Natanzon · 2020 [cited by applicant]
US 20200057567A1 · Hutcheson · 2020 [cited by applicant]
US 20200057669A1 · Hutcheson · 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 20210382771A1 · Schniebel · 2021 [cited by applicant]
US 20210385254A1 · Pettit · 2021 [cited by applicant]
US 20220035714A1 · Schultz · 2022 [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]
“Recovering File from an Amazon EBS vol. 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 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]
Prosecution History from U.S. Appl. No. 17/534,226, now issued U.S. Pat. No. 11,768,745, dated Nov. 25, 2022 through May 4, 2023, 29 pp. [cited by applicant]