IP Library Granted Patent US 12,210,421
Granted Patent B2
US 12,210,421 · App. 18/336,749 · Granted Jan 28, 2025

Data recovery modification based on performance data exhibited by a network of data centers and data recovery requirement

Inventors: Tomas Krojzl (Brno, CZ); Erik Rueger (Ockenheim, DE); Sharathchandra Pankanti (Fairfield County, CT)
Assignee: INTERNATIONAL BUSINESS MACHINES CORPORATION
G06F11/1464G06F11/1469G06N20/00G06F2201/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,210,421
App. No.
18/336,749
Granted
Jan 28, 2025
Kind
B2
Abstract

Techniques regarding adaptive data recovery schemes are provided. For example, one or more embodiments described herein can comprise a system, which can comprise a memory that can store computer executable components. The system can also comprise a processor, operably coupled to the memory, and that can execute the computer executable components stored in the memory. The computer executable components can comprise a data management component that can modify a data recovery scheme based on performance data exhibited by a network of data centers and a data recovery requirement. The data recovery scheme can direct a relocation of data within the network.

Claims (43)

1. A system, comprising:

a memory that stores computer executable components; and

a processor, operably coupled to the memory, and that executes at least one of the computer executable components that:

generates a machine learning model to optimize relocation of data based on a group of microservice applications, wherein the machine learning model identifies a relationship between a modification made to a data recovery scheme and a data recovery requirement based on performance data of the group of microservice applications.

2. The system of claim 1 , wherein the performance data comprises at least one member selected from a group consisting of location of data centers, bandwidth of a network, latency of the network, bandwidth used by the data, latency exhibited during execution of the data, and latency exhibited during relocation of the data.

3. The system of claim 2 , wherein the data recovery requirement comprises at least one second member selected from a second group consisting of the location of the data centers and a service level objective.

4. The system of claim 1 , wherein the at least one of the computer executable components further:

modifies the data recovery scheme to generate a modified data recovery scheme;

analyzes the modified data recovery scheme to determine whether the modified data recovery scheme is predicted to achieve improved performance data and meet the data recovery requirement in comparison to the data recovery scheme; and

performs the relocation of the data in accordance with the modified data recovery scheme based on a determination that the modified data recovery scheme is predicted to improve the performance data and meet the data recovery requirement.

5. The system of claim 4 , wherein the machine learning model identifies a second relationship between the modification to the data recovery scheme and the data recovery requirement based on the performance data of the group of microservice applications.

6. The system of claim 5 , wherein the performance data further regards at least one data center of a network, and wherein the at least one of the computer executable components further:

generates the machine learning model to optimize the relocation of the data based further on the at least one data center, wherein the machine learning model identifies a third relationship between a second modification made to the data recovery scheme and the data recovery requirement based on the performance data of the at least one data center.

7. A system, comprising:

a memory that stores computer executable components; and

a processor that executes at least one of the computer executable components that:

generates a machine learning model to determine a modification to a data recovery scheme based on performance data exhibited by a network of data centers and a data recovery requirement, wherein the data recovery scheme directs a relocation of data within the network; and

generates a first portion of the machine learning model to optimize the relocation of the data based on the performance data of a group of microservice applications within the data.

8. The system of claim 7 , wherein the performance data comprises at least one member selected from a group consisting of location of the data centers, bandwidth of the network, latency of the network, bandwidth used by the data, latency exhibited during execution of the data, and latency exhibited during the relocation of the data, and wherein the data recovery requirement comprises at least one second member selected from a second group consisting of the location of the data centers and a service level objective.

9. The system of claim 7 , wherein the at least one of the computer executable components further:

generates a second portion of the machine learning model to optimize the relocation of the data based on the performance data of at least one data center of the network.

10. The system of claim 7 , wherein the at least one of the computer executable components further:

performs the relocation of the data in accordance with the modification to the data recovery scheme based on a determination that the modification is predicted to improve performance data and meet the data recovery requirement.

11. The system of claim 7 , wherein the machine learning model identifies a relationship between the modification to the data recovery scheme and the data recovery requirement based on the performance data.

12. The system of claim 7 , wherein the at least one of the computer executable components further;

implements the modification to generate a modified data recovery scheme, and

analyzes the modified data recovery scheme to determine whether the modified data recovery scheme is predicted to achieve improved performance data and meet the data recovery requirement in comparison to the data recovery scheme.

13. A computer-implemented method, comprising:

generating, by a system operatively coupled to a processor, a machine learning model to determine a modification to a data recovery scheme based on performance data exhibited by a network of data centers and a data recovery requirement, wherein the data recovery scheme directs a relocation of data within the network;

generating, by the system, a first portion of the machine learning model to optimize the relocation of the data based on the performance data of a group of microservice applications within the data; and

performing, by the system, the relocation of the data in accordance with the modification to the data recovery scheme based on a determination that the modification is predicted to improve performance data and meet the data recovery requirement.

14. The computer-implemented method of claim 13 , wherein the performance data comprises at least one member selected from a group consisting of location of the data centers, bandwidth of the network, latency of the network, bandwidth used by the data, latency exhibited during execution of the data, and latency exhibited during the relocation of the data, and wherein the data recovery requirement comprises at least one second member selected from a second group consisting of the location of the data centers and a service level objective.

15. The computer-implemented method of claim 13 , further comprises:

generating, by the system, a second portion of the machine learning model to optimize the relocation of the data based further on the performance data of at least one data center of the network.

16. The computer-implemented method of claim 15 , wherein the modification generates a modified data recovery scheme, and wherein the computer-implemented method further comprises:

analyzing, by the system, the modified data recovery scheme to determine whether the modified data recovery scheme is predicted to achieve improved performance data and meet the data recovery requirement in comparison to the data recovery scheme.

17. A computer-implemented method, comprising:

removing, by a system, a secondary data center candidate from a network of data centers based on performance data, wherein the performance data regards a group of microservice applications comprised within the performance data and at least one data center of the network; and

generating, by the system, a machine learning model to optimize relocation of the data based on the group of microservice applications.

18. The computer-implemented method of claim 17 , wherein the performance data comprises at least one member selected from a group consisting of location of the data centers, bandwidth of the network, latency of the network, bandwidth used by the data, latency exhibited during execution of the data, and latency exhibited during the relocation of the data, and wherein the data recovery requirement comprises at least one second member selected from a second group consisting of the location of the data centers and a service level objective.

19. The computer-implemented method of claim 17 , wherein the machine learning model identifies a relationship between a modification made to a data recovery scheme and a data recovery requirement based on the performance data regarding the group of microservice applications.

20. The computer-implemented method of claim 19 , wherein the performance data further regards the at least one data center, and wherein the computer-implemented method further comprises:

generating, by the system, a second machine learning model to optimize the relocation of the data based further on the at least one data center.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 16, 2023
From: KROJZL, TOMAS; RUEGER, ERIK; PANKANTI, SHARATHCHANDRA
To: INTERNATIONAL BUSINESS MACHINES CORPORATION
Reel/Frame 064015/0454 →
Continuity (2)
Continuation 16554030 · Aug 28, 2019
Related Publication 20230333943A1 · Oct 19, 2023
References Cited (75)
US 5367698A · Webber · 1994 [cited by examiner]
US 7325019B2 · Lam et al. · 2008 [cited by applicant]
US 7395352B1 · Lam et al. · 2008 [cited by applicant]
US 8132043B2 · Dash et al. · 2012 [cited by applicant]
US 8572431B2 · Adler et al. · 2013 [cited by applicant]
US 9465827B1 · Cox et al. · 2016 [cited by applicant]
US 10021185B1 · Kleinschnitz, Jr. · 2018 [cited by examiner]
US 10270644B1 · Valsecchi · 2019 [cited by examiner]
US 10296255B1 · Tummala · 2019 [cited by examiner]
US 11010410B1 · Annamalai · 2021 [cited by examiner]
US 11405329B1 · Cuthbert · 2022 [cited by examiner]
US 20030065762A1 · Stolorz · 2003 [cited by examiner]
US 20070198797A1 · Kavuri · 2007 [cited by examiner]
US 20110282982A1 · Jain · 2011 [cited by applicant]
US 20120297238A1 · Watson et al. · 2012 [cited by applicant]
US 20140046917A1 · Smith · 2014 [cited by examiner]
US 20140098685A1 · Shattil · 2014 [cited by examiner]
US 20140173229A1 · Reohr · 2014 [cited by examiner]
US 20150317220A1 · Sampalh et al. · 2015 [cited by applicant]
US 20150331752A1 · Haider et al. · 2015 [cited by applicant]
US 20160226745A1 · Tran · 2016 [cited by examiner]
US 20170060900A1 · Marinov et al. · 2017 [cited by applicant]
US 20170220281A1 · Gupta et al. · 2017 [cited by applicant]
US 20180069925A1 · Lavasani · 2018 [cited by applicant]
US 20180077080A1 · Gazier et al. · 2018 [cited by applicant]
US 20180102985A1 · Byers et al. · 2018 [cited by applicant]
US 20180227240A1 · Liu et al. · 2018 [cited by applicant]
US 20190138287A1 · De Capoa et al. · 2019 [cited by applicant]
US 20190171966A1 · Rangasamy et al. · 2019 [cited by applicant]
US 20190188089A1 · Mueller et al. · 2019 [cited by applicant]
US 20190250998A1 · Bedadala et al. · 2019 [cited by applicant]
US 20190268216A1 · Wu · 2019 [cited by examiner]
US 20200004569A1 · Gupta · 2020 [cited by examiner]
US 20200125453A1 · Kommera · 2020 [cited by examiner]
US 20200125545A1 · Idicula · 2020 [cited by examiner]
US 20200379807A1 · Tang · 2020 [cited by examiner]
US 20200387433A1 · Wang · 2020 [cited by examiner]
US 20210064480A1 · Krojzl et al. · 2021 [cited by applicant]
US 20210127241A1 · Moubayed · 2021 [cited by examiner]
US 20210271549A1 · Khayat · 2021 [cited by examiner]
US 20210398073A1 · Mishra · 2021 [cited by examiner]
US 20220141130A1 · Sum Wong · 2022 [cited by examiner]
US 20220164186A1 · Pamidala · 2022 [cited by examiner]
CN 1577276A · 2005 [cited by applicant]
CN 103547994A · 2014 [cited by applicant]
CN 103873546A · 2014 [cited by applicant]
CN 107402851A · 2017 [cited by applicant]
CN 108337260A · 2018 [cited by applicant]
CN 109144967A · 2019 [cited by applicant]
CN 109844728A · 2019 [cited by applicant]
CN 110109779A · 2019 [cited by applicant]
WO 2010039151A1 · 2010 [cited by applicant]
List of IBM Patents or Applications Treated as Related (Appendix P), 2 pages. [cited by applicant]
Notice of Reasons for Refusal received for Japanese Patent Application Serial No. 2022-513200 dated Feb. 20, 2024, 19 pages (including English Translation). [cited by applicant]
Notice of Reasons for Refusal received for Japanese Patent Application Serial No. 2022-513200 dated Jul. 22, 2024. [cited by applicant]
Disaster Recovery as a Service Market by Service Type {Backup & Recovery, Real-Time Replication, Data Protection and Professional Services), Service Provider, Deployment Model, Organization Size, Vertical, and Region—Gl… [cited by applicant]
Manaktala “Optimization of Disaster Recovery Leveraging Enterprise Architecture Ontology” The Ohio State University Graduate Program in Computer Science and Engineering (2013).https://eld.ohiolink.edu/rws_eld/documentJe… [cited by applicant]
Mell et al., “The NIST Definition of Cloud Computing”, National Institute of Standards and Technology, Sep. 2011, 7 pages. [cited by applicant]
Invitation to pay additional fee received for PCT Application Serial No. PCT/EP2020/070789 dated Nov. 16, 2020, 12 pages. [cited by applicant]
Non Final Office Action received for U.S. Appl. No. 16/554,030 dated Oct. 4, 2021, 71 pages. [cited by applicant]
Final Office Action received for U.S. Appl. No. 16/554,030 dated Feb. 4, 2022, 72 pages. [cited by applicant]
Non-Final Office Action received for U.S. Appl. No. 16/554,030 dated May 11, 2022, 76 pages. [cited by applicant]
International Search Report and Written Opinion for International Application No. PCT/EP2020/070789 dated Apr. 3, 2021, 20 pages. [cited by applicant]
Office Action received for Chinese Patent Application Serial No. 202080059323.1 dated Oct. 21, 2022, 16 pages. [cited by applicant]
Final Office Action received for U.S. Appl. No. 16/554,030 dated Dec. 7, 2022, 85 pages. [cited by applicant]
Ji et al., “Based on the movement of the traffic prediciton front light transmitting network bandwidth adjustment method and device”, Machine Translation of Foreign Patent CN 110839184-A published Feb. 25, 2020 (Year: 2… [cited by applicant]
Communication pursuant to Article 94(3) EPC for EP Application No. 20746169.0 dated Feb. 17, 2023, 4 Pages. [cited by applicant]
Notice of Allowance received for U.S. Appl. No. 16/554,030 dated Mar. 8, 2023, 48 pages. [cited by applicant]
Office Action received for Chinese Patent Application Serial No. 202080059323.1 dated Jan. 28, 2023, 14 pages. [cited by applicant]
Office Action received for Chinese Patent Application Serial No. 202080059323.1 dated May 23, 2023, 5 pages. [cited by applicant]
Ying et al., “Survey of Mobility Prediction in Wireless Network”, Journal on Communications, vol. 40, No. 8, Aug. 2019, 12 pages. [cited by applicant]
Yong Ji, “Design of Infrastructure Based on Micro-services Architecture”, Computer Engineering & Software, vol. 37, No. 5, 2016, 5 pages. [cited by applicant]
Ahmad et al., “Strategy and Procedures for Migration to the Cloud Computing”, IEEE 5th International Conference on Engineering Technologies & Applied Sciences, Nov. 22-23, 2018, 5 pages. [cited by applicant]
Notice of Allowance received for U.S. Appl. No. 16/554,030 dated Jun. 15, 2023, 10 pages. [cited by applicant]
Response to the Communication pursuant to Article 94(3) EPC received for European Patent Application Serial No. 20746169.0 dated Jun. 27, 2023, 3 pages. [cited by applicant]
Cited By (1)
US 12,368,736