Data relocation management in data center networks

The system optimizes data recovery schemes in data center networks by using machine learning to adapt to changing performance characteristics, enhancing efficiency and meeting service level objectives through dynamic data relocation.

JP7582754B2Active Publication Date: 2024-11-13INTERNATIONAL BUSINESS MACHINE CORPORATION
View PDF 12 Cites 0 Cited by

Patent Information

Application Number
JP2022513200
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2019-08-28
Filing Date
2020-07-23
Publication Date
2024-11-13
Estimated Expiration
2040-07-23

AI Technical Summary

Technical Problem

Traditional data recovery schemes in data center networks fail to adapt to changing operational requirements and performance characteristics over time, leading to inefficient data relocation.

Method used

A system that modifies data recovery schemes using machine learning models to optimize data relocation based on real-time performance data and requirements, allowing for dynamic adjustment of secondary data centers to meet service level objectives.

Benefits of technology

Enhances network efficiency by improving data recovery performance and meeting service level objectives through adaptive data relocation strategies.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007582754000001
    Figure 0007582754000001
  • Figure 0007582754000002
    Figure 0007582754000002
  • Figure 0007582754000003
    Figure 0007582754000003
Patent Text Reader

Abstract

Techniques are provided for adaptive data recovery schemes. For example, one or more embodiments described herein may include a system that may include a memory capable of storing computer-executable components. The system may also include a processor operatively coupled to the memory and capable of executing the computer-executable components stored in the memory. The computer-executable components may include a data management component that may modify the data recovery scheme based on performance data and data recovery requirements exhibited by the data center's network. The data recovery scheme may direct the relocation of data within the network.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The subject disclosure relates to data center networks, Relocation The present invention relates to managing, and more particularly to optimizing, one or more data recovery schemes that may direct the distribution of data within a network of one or more data centers. [Background technology]

[0002] Data recovery schemes may be utilized to facilitate recovery of data by replicating and transferring data from a primary source in the event that the primary source is compromised. Traditional database recovery is designed as a direct source-to-target database replication that is pre-determined and remains static over time. For example, traditional data recovery schemes may dictate the replication and / or transfer of data from a primary data center to one or more secondary data centers in response to one or more operational failures associated with the primary data center where the data is primarily sourced and / or performed. The one or more secondary data centers may be pre-determined prior to executing the data recovery scheme. Additionally, once the secondary data centers are pre-determined, Relocation Their status as a destination typically remains unchanged throughout the operation of the primary data center. Summary of the Invention [Problem to be solved by the invention]

[0003] However, traditional data recovery schemes may not take into account multiple characteristics of the data and / or data centers that may change over time. For example, the operational requirements for carrying the data and / or the performance characteristics of one or more data centers may change after the data recovery scheme is established. Relocation By subjecting traditional data recovery schemes to multiple threats, they can perform much less efficiently than they were originally designed.

[0004] The following presents a summary to provide a basic understanding of one or more embodiments of the invention. This summary is not intended to identify key or essential elements, nor is it intended to delineate the scope of any particular embodiments or the scope of the claims. Its sole purpose is to present concepts in a simplified form as a prelude to the more detailed description that is presented later. In one or more embodiments described herein, a system, computer-implemented method, apparatus, and / or computer program product that can optimize one or more data recovery schemes are described.

[0005] According to one embodiment, a system is provided comprising computer-executable components (program) The system can include a memory for storing a data recovery scheme for a network of data centers. The system can also include a processor operatively coupled to the memory and capable of executing the computer-executable components stored in the memory. The computer-executable components can include a data management component that can modify a data recovery scheme based on performance data exhibited by the network of data centers and data recovery requirements. The data recovery scheme can be configured to manage the data recovery of a network of data centers. Relocation An advantage of such a system would be the generation of a data recovery scheme adapted to the measured performance characteristics of a given network data center.

[0006] In some examples, the data management component can modify the data recovery scheme to generate a modified data recovery scheme. The system can also include an evaluation component that can analyze 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 requirements compared to the data recovery scheme. The system can further include a step of analyzing the modified data recovery scheme in accordance with the modified data recovery scheme based on the evaluation component determining that the modified data recovery scheme is predicted to achieve improved performance data and meet the data recovery requirements. Relocation can be executed Relocation An advantage of such a system may be that it enables an iterative optimization process with autonomous evaluation of proposed changes.

[0007] According to one embodiment, a system is provided. The system can include a memory that stores computer-executable components. The system can also include a processor operatively coupled to the memory and capable of executing the computer-executable components stored in the memory. The computer-executable components can include a data management component that can generate a machine learning model to determine modifications to a data recovery scheme based on performance data exhibited by a network of data centers and data recovery requirements. The data recovery scheme can be configured to manage the movement of data within the network. Relocation An advantage of such a system may be that the autonomous nature of the system allows for adjustments to the data recovery scheme while still maintaining confidentiality of the data.

[0008] In some examples, the performance data may include the location of data centers, network bandwidth, network latency, bandwidth used by the data, latency exhibited during the execution of the data, and the time taken by the data to run. Relocation The data recovery requirements may include at least one member selected from a group consisting of a latency as shown in FIG. 1, and a second member selected from a second group consisting of a data center location, and a service level objective. An advantage of such a system may be improved achievement of one or more target service level objectives, such as a latency target, with a data recovery scheme that can be achieved by the capacity of the data center network.

[0009] According to one embodiment, a computer-implemented method is provided that includes generating, by a system operatively coupled to a processor, a machine learning model for determining modifications to a data recovery scheme based on performance data exhibited by a network of data centers and data recovery requirements. The data recovery scheme comprises: Relocation The advantage of such a computer-implemented method is that it can be used to optimize the data and / or data center based on operational characteristics of the data and / or data center. Relocation In some cases, the primary advantage is that the data center location (e.g., a secondary data center) can be easily changed and / or modified.

[0010] In some examples, the performance data may relate to a group of microservice applications included in the data and at least one data center of the network. The computer-implemented method also includes, by the system, determining, based on the performance data of the group of microservice applications, Relocation The computer-implemented method may further include generating, by the system, a first portion of a machine learning model for optimizing the performance of the at least one data center. RelocationAn advantage of such a computer-implemented method may be to generate a second part of the machine learning model for optimizing the

[0011] According to one embodiment, a computer-implemented method is provided that includes modifying, by a system operatively coupled to a processor, a data recovery scheme based on performance data exhibited by a network of data centers and data recovery requirements. The data recovery scheme comprises modifying a data recovery scheme based on performance data exhibited by a network of data centers and data recovery requirements. Relocation An advantage of such a computer-implemented method may be increased network utilization during execution of a data recovery scheme.

[0012] In some examples, the modifying can be based on the first machine learning model and the second machine learning model to generate a modified data recovery scheme. The computer-implemented method can also include analyzing, by the system, the modified data recovery scheme to determine whether the modified data recovery scheme is predicted to improve performance data compared to the data recovery scheme and meet the data recovery requirements. An advantage of such a computer-implemented method is that it can leverage machine learning principles to continually improve the efficiency of the method.

[0013] According to one embodiment, a computer program product for adaptively distributing data within a network of data centers is provided. The computer program product may include a computer readable storage medium having program instructions embodied thereon. The program instructions are executable by a processor to cause the processor to modify a data recovery scheme based on performance data exhibited by the network of data centers and data recovery requirements. The data recovery scheme may include modifying a data recovery scheme based on performance data exhibited by the network of data centers and data recovery requirements. RelocationThe benefits of such computer program products include the ability to predict, predictively analyze, and / or predictively display data based on changing performance characteristics that are measured in real-time or near real-time. Relocation It may mean that the scheme can be continually analyzed and / or subject to adaptation.

[0014] In some examples, the performance data may relate to a group of microservice applications included in the data and at least one data center of the network. Further, the program instructions may include, by the processor, aggregating the data based on the group of microservice applications. Relocation The program instructions may further cause the processor to generate a first machine learning model for optimizing the at least one data center. Relocation An advantage of such a computer program product may be to enable a data recovery system that can autonomously adapt to various changes in a given data center's network. [Brief description of the drawings]

[0015] [Figure 1] FIG. 1 is a block diagram of an exemplary, non-limiting system capable of optimizing one or more data recovery schemes within a network of one or more data centers, in accordance with one or more embodiments described herein. [Diagram 2] FIG. 1 is a block diagram of an exemplary and non-limiting data center network that can facilitate relocation of data from one or more primary data centers to one or more secondary data centers in accordance with one or more embodiments described herein. [Diagram 3]FIG. 1 is a block diagram of an exemplary, non-limiting system that can evaluate one or more data recovery schemes to determine whether one or more data recovery requirements are met, in accordance with one or more embodiments described herein. [Figure 4] FIG. 1 is a block diagram of an example and non-limiting system that can modify one or more data recovery schemes based on performance data regarding one or more groups of microservices contained within the data, in accordance with one or more embodiments described herein. [Diagram 5] FIG. 1 is a block diagram of an example, non-limiting system that can modify one or more data recovery schemes based on performance data regarding one or more data centers included in a data center network managed by a given data recovery scheme, in accordance with one or more embodiments described herein. [Figure 6] FIG. 1 is a block diagram of an example and non-limiting system capable of relocating data between one or more data center networks according to one or more modified data recovery schemes in accordance with one or more embodiments described herein. [Figure 7] FIG. 1 illustrates an exemplary, non-limiting data center network that can facilitate relocation of data from one or more primary data centers to one or more secondary data centers as dictated by one or more data recovery schemes in accordance with one or more embodiments described herein. [Figure 8] FIG. 1 is a flowchart of an example and non-limiting method that can facilitate modifying one or more data recovery schemes to increase relocation efficiency based on performance data and / or data recovery requirements associated with subject data and / or one or more data center networks, in accordance with one or more embodiments described herein. [Figure 9]FIG. 1 is a flowchart of an example and non-limiting method that can facilitate modifying one or more data recovery schemes to increase relocation efficiency based on performance data and / or data recovery requirements associated with subject data and / or one or more data center networks, in accordance with one or more embodiments described herein. [Figure 10] FIG. 1 is a flowchart of an example and non-limiting method that can facilitate modifying one or more data recovery schemes to increase relocation efficiency based on performance data and / or data recovery requirements associated with subject data and / or one or more data center networks, in accordance with one or more embodiments described herein. [Figure 11] FIG. 1 is a flowchart of an example and non-limiting method that can facilitate modifying one or more data recovery schemes to increase relocation efficiency based on performance data and / or data recovery requirements associated with subject data and / or one or more data center networks, in accordance with one or more embodiments described herein. [Figure 12] FIG. 1 illustrates a cloud computing environment in accordance with one or more embodiments described herein. [Figure 13] FIG. 2 illustrates an abstraction model layer according to one or more embodiments described herein. [Figure 14] FIG. 1 is a block diagram of an example non-limiting operating environment capable of facilitating one or more embodiments described herein. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] The following detailed description is merely illustrative and is not intended to limit the embodiments or the application or uses of the embodiments, or both, and is further not intended to be bound by any express or implied information presented in the preceding Background or Summary sections or in the Detailed Description section.

[0017] One or more embodiments are described below with reference to the drawings, in which like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a more thorough understanding of one or more embodiments. However, it will be apparent that in various instances, one or more embodiments may be practiced without these specific details.

[0018] Taking into account problems with conventional implementations of data recovery schemes, the present disclosure can be implemented to create solutions to one or more of these problems by adapting the data recovery scheme based on historical performance data for previous runs of the data, or characteristics of the data center, or both. Advantageously, one or more embodiments described herein can modify one or more initial data recovery schemes to optimize one or more defined data recovery requirements. For example, one or more embodiments can optimize one or more service level objectives ("SLOs") while satisfying one or more user-defined requirements.

[0019] Various embodiments of the present invention may be directed to a computer processing system, computer-implemented method, apparatus, or computer program product, or combination thereof, that facilitates efficient, effective, and autonomous (e.g., without direct human direction) adaptation of one or more data recovery schemes based on performance data exhibited by a given data and / or data center in a given network. One or more embodiments may generate an adaptive data recovery scheme that may change over time depending on established service level agreements ("SLAs") and / or experienced network utilization. For example, one or more embodiments may relate to a system, computer-implemented method, or computer program product, or combination thereof, that may analyze performance data exhibited across a network of data centers and adapt a data recovery scheme based on the performance data to, for example, optimize an SLO, recovery time objective ("RTO"), or recovery point objective ("RPO"), or combination thereof.

[0020] A computer processing system, computer implemented method, apparatus, and / or computer program product utilizes hardware and / or software to solve a problem that is highly technical in nature (e.g., generating and / or executing an adaptive data recovery scheme) and is not an abstract problem and cannot be performed as a series of mental activities by a human. The vast amount of data that can be managed by a data recovery scheme cannot be easily monitored and analyzed by an individual or multiple individuals with the same speed and / or efficiency as the embodiments described herein. Furthermore, the autonomous nature of one or more embodiments described herein allows confidentiality of the data and / or data disbursement to be maintained.

[0021] FIG. 1 illustrates a block diagram of an exemplary and non-limiting system 100 that can modify one or more data recovery schemes based on performance data exhibited by data of a given network and / or execution of one or more data centers. Repeated descriptions of similar elements used in other embodiments described herein are omitted for brevity. System (e.g., system 100 and the like), apparatus, or process aspects of various embodiments of the invention can comprise one or more machine-executable components embodied in one or more machines, e.g., embodied in one or more computer-readable medium (or media) associated with one or more machines. Such components, when executed by one or more machines, e.g., computers, computing devices, virtual machines, etc., can cause the machines to perform the described operations.

[0022] As shown in FIG. 1, the system 100 may include one or more servers 102, one or more networks 104, input devices 106, and / or a data center 108. The server 102 may include a data management component 110. The data management component 110 may further include a communication component 112 and / or an initialization component 114. The server 102 may also include or be otherwise associated with at least one memory 116. The server 102 may further include a system bus 118, which may be coupled to various components, such as, but not limited to, the data management component 110 and associated components, the memory 116, and / or a processor 120. Although FIG. 1 illustrates a server 102, in other embodiments, multiple devices of various types may be associated with or include the features illustrated in FIG. 1. Additionally, the server 102 may be in communication with one or more cloud computing environments.

[0023] The one or more networks 104 may include wired and wireless networks, including, but not limited to, a cellular network, a wide area network (WAN) (e.g., the Internet), or a local area network (LAN). For example, the server 102 may communicate with the one or more input devices 106 and / or the data center 108 (and vice versa) using substantially any desired wired or wireless technology, including, but not limited to, for example, cellular, WAN, Wireless Fidelity (Wi-Fi), Wi-Max, WLAN, Bluetooth technology, combinations thereof, and / or the like. Additionally, while in the illustrated embodiment, the data management component 110 may be provided on the one or more servers 102, it should be understood that the architecture of the system 100 is not so limited. For example, the data management component 110, or one or more components of the data management component 110, may be located on other computing devices, e.g., other server devices, client devices, etc.

[0024] The one or more input devices 106 may include one or more computerized devices, including, but not limited to, a personal computer, a desktop computer, a laptop computer, a mobile phone (e.g., a smart phone), a computerized tablet (e.g., including a processor), a smart watch, a keyboard, a touch screen, a mouse, combinations thereof, and / or the like. A user of the system 100 may utilize the one or more input devices 106 to input data into the system 100, thereby sharing the data with the server 102 and / or the data center 108 (e.g., via a direct connection, or via one or more networks 104, or both). For example, the one or more input devices 106 may transmit data to the communication component 112 (e.g., via a direct connection, or via one or more networks 104, or both). The one or more input devices 106 may also include one or more displays that may present one or more outputs generated by the system 100 to the user. For example, the one or more displays may include, but are not limited to, a cathode ray tube display ("CRT"), a light emitting diode display ("LED"), an electroluminescent display ("ELD"), a plasma display panel ("PDP"), a liquid crystal display ("LCD"), an organic light emitting diode display ("OLED"), combinations thereof, and / or the like.

[0025] A user of the system 100 can input one or more settings and / or commands into the system 100 utilizing one or more input devices 106 and / or one or more networks 104. For example, in various embodiments described herein, a user of the system 100 can operate and / or manipulate the server 102 and / or associated components via one or more input devices 106. A user of the system 100 can also utilize one or more input devices 106 to display one or more outputs (e.g., displays, data, visualizations, or the like, or combinations thereof) generated by the server 102 and / or associated components. Additionally, in one or more embodiments, the one or more input devices 106 can be included within and / or operably coupled to a cloud computing environment.

[0026] The one or more data centers 108 may store, execute, share, or otherwise manipulate, or a combination thereof, data managed by the one or more data recovery schemes. For example, the one or more data centers 108 may include one or more computer servers that may be used to store, process, or distribute, or a combination thereof, the given data. In various embodiments, the system may include multiple data centers 108, including one or more primary data centers 108 and one or more secondary data centers 108. The one or more primary data centers 108 may be data centers 108 that are initially responsible for storing, processing, or distributing, or a combination thereof, the given data. The one or more secondary data centers 108 may be data centers 108 that are initially responsible for storing, processing, or distributing, or a combination thereof, the given data. RelocationIn addition, multiple data centers 108 may communicate with each other and / or share data via a direct electrical connection and / or one or more networks 104.

[0027] In one or more embodiments, a user of the system 100 can designate one or more of the data centers 108 as primary data centers 108 via one or more input devices 106. Similarly, a user can designate one or more of the data centers 108 as secondary data centers 108 via one or more input devices 106. For example, the communication component 112 can receive the designation of one or more data centers via a direct electrical connection with the one or more input devices 106, or via one or more networks 104, or both, and / or share those designations with associated components of the data management component 110. This enables the data management component 110 to generate an initial data recovery scheme based on the user-defined designations. For example, the data management component 110 can generate a ... Relocation In addition, a user of the system 100 can utilize one or more input devices 106 to define one or more SLAs, SLOs, RPOs, and / or RTOs that are taken into account by the data management component 110 when generating the initial data recovery scheme.

[0028] In some embodiments, a user of the system 100 can provide an initial data recovery scheme to the data management component 110 via one or more input devices 106 (e.g., via the communication component 112, or one or more networks 104, or both). In various embodiments, a user of the system 100 can utilize the one or more input devices 106 to designate one or more data centers 108 as primary data centers 108 and input one or more data recovery requirements. The initialization component 114 can then autonomously designate one or more other data centers 108 as secondary data centers 108 to facilitate the data management component 110 generating the initial data recovery scheme.

[0029] For example, the initialization component 114 may evaluate data centers 108 accessible via one or more networks 104 to generate a list of available data center 108 pairs, where each data center 108 pair may include one or more designated primary data centers 108 associated with one or more other available data centers 108 (e.g., thereby designated as available secondary data centers 108). The initialization component 114 may then eliminate data center 108 pairs from the available list based on one or more data recovery requirements defined by a user of the system 100. For example, the initialization component 114 may eliminate given data centers 108 as potentially available secondary data centers 108 based on those data centers 108 being part of the same facility and / or infrastructure as the primary data center 108. By designating a secondary data center 108 that is separate from the facilities and / or infrastructure of the primary data center 108, the data management component 110 can generate a data recovery scheme that can facilitate data recovery in the event that the facilities and / or infrastructure of the primary data center 108 are compromised.

[0030] In another example, the initialization component 114 can exclude certain data centers 108 as potentially available secondary data centers 108 based on the data centers 108 being located in an unacceptable geography (e.g., as defined by a user of the system 100). Relocation You can define the geographic boundaries to which data is restricted (for example, to a particular municipality, state, region, or country, or any combination of these). Relocation), which may then eliminate data centers 108 located outside the geographic boundaries as candidates for designation as secondary data centers 108. This enables the initialization component 114 to eliminate secondary data center 108 candidates that conflict with one or more user-defined data recovery requirements to facilitate user needs, compliance with one or more administrative regulations, or both.

[0031] In one or more embodiments, the initialization component 114 can further exclude as potentially available data centers 108 those data centers 108 based on the performance capacity of the given data centers 108 and one or more target performance objectives of the data recovery scheme. For example, the initialization component 114 can exclude secondary data center 108 candidates that may not be able to achieve one or more latency SLOs during execution of the data recovery scheme. In various embodiments, the initialization component 114 can sort the remaining secondary data center 108 candidates based on bandwidth (e.g., average available bandwidth of the data centers 108). This can allow the initialization component 114 to facilitate the generation of the initial data recovery scheme by generating a list of available data centers 108 that can be designated as secondary data centers 108 for one or more given primary data centers 108. For example, the data management component 110 can analyze the list of available data centers 108 and designate one or more of those data centers 108 as secondary data centers 108 in generating one or more initial data recovery schemes.

[0032] 2 illustrates an exemplary, non-limiting diagram of a system 100 including three data centers 108, in accordance with one or more embodiments described herein. Repeated descriptions of similar elements used in other embodiments described herein are omitted for the sake of brevity. Although FIG. 2 illustrates three data centers 108, the architecture of the system 100 is not so limited. For example, embodiments including fewer or more than three data centers 108 are also contemplated.

[0033] As shown in FIG. 2, data centers 108 may communicate with each other and / or servers 102 via one or more direct electrical connections and / or one or more networks 104. In FIG. 2, the data subject to management by one or more data recovery schemes is illustrated by multiple circles. In one or more embodiments, the data may include one or more microservices. Further, the one or more microservices may be divided into groups based on the functionality and / or requirements of the microservices. In various embodiments, microservices in the same group may be managed together via a data recovery scheme. Relocation For example, FIG. 2 illustrates two groups of microservices, with the first group of microservices represented by white circles and the second group of microservices represented by black circles. Additionally, each group of microservices may be associated with one or more respective databases to facilitate their functionality. The one or more groups of microservices may be initially stored, processed, and / or executed in the primary data center 108. For example, FIG. 2 illustrates the system 100 prior to performing a data recovery scheme, with the left data center 108 designated as the primary data center 108 (e.g., thereby containing the two groups of microservices) and the lower and right data centers 108 designated as secondary data centers 108.

[0034] In various embodiments, the data management component 110 (e.g., via the communication component 112 or the initialization component 114, or both) can collect performance data regarding data (e.g., one or more microservices) and one or more data centers 108, and / or one or more data recovery requirements (e.g., as defined by users of the system 100 and / or one or more SLAs). The performance data regarding one or more data centers 108 may describe, for example, but is not limited to, the location of the data center 108 (e.g., the address, municipality, region, country, continent, or territory of a given data center 108, or a combination thereof), a work group designation (e.g., one or more organizations affiliated with a given data center 108), a maximum allocated bandwidth between one or more data centers 108, an average network latency between one or more data centers 108, the operating capacity and / or characteristics of a given data center 108, the distance between the data centers 108, the fixed and / or recurring costs to support a given data center 108, a combination thereof, and / or the like. The performance data regarding data (e.g., one or more microservices groups) may describe, for example, a target application latency (e.g., the time required to send data to a designated secondary data center 108), a network ... RelocationThe parameters may describe, but are not limited to, a maximum time to load and / or deliver data updates, a colocation group designation (e.g., one or more requirements describing a target secondary data center 108), an anti-colocation group (e.g., one or more requirements that may be used to filter potential secondary data center 108 candidates), an average bandwidth used (e.g., total bandwidth used measured across databases of a given microservice group over a period of time, such as a day), an average application latency (e.g., maximum latency measured across databases of a given microservice group), combinations thereof, and / or the like. In various embodiments, recent performance history may be captured by periodically measuring and / or updating performance data regarding one or more data centers 108 and / or data.

[0035] 3 illustrates an exemplary and non-limiting diagram of the system 100 further including an evaluation component 302, according to one or more embodiments described herein. Repeated descriptions of similar elements used in other embodiments described herein are omitted for brevity. In one or more embodiments, the evaluation component 302 can analyze one or more data recovery schemes to determine whether a given data recovery scheme is predicted to achieve one or more target performance objectives. For example, the evaluation component 302 can analyze one or more initial data recovery schemes to generate one or more baseline metrics that can be utilized to determine whether future modifications to the data recovery schemes will provide performance improvements.

[0036] In one or more embodiments, the evaluation component 302 can: For example, the evaluation component 302 can reset an evaluation counter for the estimated bandwidth usage between a pair of given data centers 108 to a value of zero. The evaluation component 302 can then update the bandwidth usage for the given data center 108 pair for each managed microservice group. For example, the evaluation component 302 can increase the estimated bandwidth usage by an average bandwidth usage value (e.g., the total bandwidth used by the databases of the given microservice group). The evaluation component 302 can then count the amount of the microservice group that fails to meet one or more SLO targets. For example, the evaluation component 302 can count the missed SLO target when the average application latency of the given microservice group is greater than the target application latency (e.g., when the measured application latency is greater than the target SLO). Additionally, the evaluation component 302 can identify high traffic areas between the specified data centers 108. For example, the evaluation component 302 can calculate the bandwidth utilization as the estimated bandwidth used divided by the maximum allocated bandwidth (e.g., the percentage of a given bandwidth used between given data centers 108). The evaluation component 302 can also determine one or more evaluation values ​​based on the above functions. For example, the evaluation component 302 can calculate the percentage of unmet SLOs as the percentage of microservice groups that do not achieve one or more SLO targets. In another example, the evaluation component 302 can calculate the average bandwidth utilization as the squared deviation from the mean of the bandwidth utilization (e.g., this can describe the distribution of bandwidth for one or more data center 108 pairs managed by a given data recovery scheme).

[0037] 4 illustrates an exemplary, non-limiting diagram of the system 100 further including a data optimization component 402 in accordance with one or more embodiments described herein. Repeated descriptions of similar elements used in other embodiments described herein are omitted for brevity. In various embodiments, the data optimization component 402 optimizes the data (e.g., microservice groups) Relocation The one or more machine learning models can generate one or more machine learning models for optimizing the performance of the one or more microservices, and the machine learning models can identify one or more relationships between one or more modifications to the initial data recovery scheme and one or more data recovery requirements based on the performance data of the one or more groups of microservices.

[0038] In one or more embodiments, the data optimization component 402 can identify one or more modifications to the initial data recovery scheme that can be implemented by the data management component 110 to generate a modified data recovery scheme. The evaluation component 302 can then evaluate the modified data recovery scheme to calculate one or more evaluation values ​​that can be compared to the evaluation values ​​of the initial data recovery scheme to determine whether the modifications improve the efficiency of the data recovery scheme. Furthermore, the identification of potential modifications and the evaluation of modified data recovery schemes can be performed iteratively by the data optimization component 402 and / or the evaluation component 302 to optimize a given data recovery scheme by the data management component 110.

[0039] For example, in various embodiments, the data optimization component 402 may begin optimization iterations by replicating the data recovery scheme being analyzed (e.g., an initial data recovery scheme) and derive a machine learning model when the identified modifications no longer improve the effectiveness of the data recovery scheme. The data optimization component 402 may then begin generating one or more machine learning models by filtering out microservice groups whose average application latency is greater than a defined threshold (e.g., a user-defined threshold) of the target application latency. For example, if the defined threshold is 90% of the target application latency, the data optimization component 402 may filter out microservice groups of a given data recovery scheme whose average application latency is greater than 90% of the target application latency.

[0040] In one or more embodiments, the data optimization component 402 can further sort the microservice groups according to the ratio of average application latency to target application latency. For example, the data optimization component 402 can sort the microservice groups such that microservice groups that do not achieve one or more SLO targets are followed by microservice groups that are at risk of not achieving one or more SLO targets. The data optimization component 402 can also generate new metrics for microservice groups identified as not achieving or at risk of not achieving one or more SLO targets. RelocationThe data optimization component 402 may determine one or more modifications that may direct the destination (e.g., an alternative secondary data center 108) of the primary data center 108. For example, the data optimization component 402 may generate and / or analyze a list of available secondary data center 108 candidates for a given primary data center and microservice group. Additionally, the data optimization component 402 may filter out secondary data center 108 candidates based on location information, colocation group designation, or anti-colocation group information, or a combination thereof, associated with a given data center 108. For example, the list of secondary data center 108 candidates may be narrowed down to include only those within a defined geographic boundary. Additionally, the data optimization component 402 may filter out secondary data center 108 candidates whose latency, when paired with the primary data center 108, would not meet one or more SLO targets. For example, the data optimization component 402 may eliminate secondary data center 108 candidates whose target application latency is less than the average network latency multiplied by a latency compensation value, which may be calculated as the average application latency divided by the average network latency for a given data center 108 pairing (e.g., the latency compensation value may be a compensation for the difference between network latency and application latency).

[0041] Additionally, the data optimization component 402 can eliminate secondary data center 108 candidates whose estimated application latency would be worse than the existing application latency. For example, the data optimization component 402 can eliminate secondary data center 108 candidates whose given average application latency is less than the average network latency multiplied by a latency correction value. Additionally, the data optimization component 402 can sort the remaining secondary data center 108 candidates based on bandwidth utilization. For example, the data optimization component 402 can sort the remaining secondary data center 108 candidates to achieve the desired application latency while minimizing network load.

[0042] This allows the data optimization component 402 to adjust a given data recovery scheme by changing one or more target secondary data centers 108 based on the resulting list of candidate secondary data centers 108. For example, the data optimization component 402 may select one or more target secondary data centers 108 based on the machine learning model. Relocation (e.g., for the original data center 108 pairing, the data optimization component 402 can reduce the estimated bandwidth usage value by the amount of average bandwidth usage). This allows the data optimization component 402 to optimize the selection of a new secondary data center 108 for a given microservice group from various secondary data center 108 candidates. Relocation , and / or adjust the corresponding application latency to the average network latency multiplied by a latency compensation value.

[0043] Additionally, the data management component 110 may perform a new data center 108 pairing (e.g., pairing a given primary data center 108 with a newly identified alternative secondary data center 108) and increase the corresponding estimated bandwidth usage value by the amount of the measured average bandwidth usage. This may allow the data management component 110 to generate one or more modified data recovery schemes. Additionally, the evaluation component 302 may analyze the one or more modified data recovery schemes to determine one or more evaluation values. The evaluation component 302 may also compare the evaluation values ​​of the one or more modified data recovery schemes to evaluation values ​​of one or more previous versions of the data recovery scheme (e.g., one or more initial data recovery schemes) to determine whether the one or more modifications determined by the data optimization component 402 improve the evaluation value (e.g., whether the modifications determined by the data optimization component 402 reduce the percentage of SLO targets not being met, or the average bandwidth usage, or both).

[0044] If a given modification improves the reputation value, the data management component 110 can set aside and / or utilize the modified data recovery scheme. If a given modification does not improve the reputation value, the data management component 110 can roll back the modification, and the data optimization component 402 can identify one or more new modifications that utilize other secondary data centers 108 from the various newly identified alternative secondary data centers 108 (e.g., the new modifications can then be similarly analyzed by the evaluation component 302 in further iterations of the optimization process).

[0045] 5 illustrates an exemplary, non-limiting diagram of the system 100 further including a data center optimization component 502 in accordance with one or more embodiments described herein. Repeated descriptions of similar elements used in other embodiments described herein are omitted for brevity. In various embodiments, the data center optimization component 502 optimizes data via a data recovery scheme further based on performance data of the data center 108. Relocation The data center optimization component 502 may generate one or more machine learning models for optimizing the one or more data recovery requirements, and the machine learning models may identify one or more relationships between modifications to the data recovery scheme (e.g., an initial data recovery scheme) and one or more data recovery requirements based on performance data of the one or more data centers 108. In one or more embodiments, the data center optimization component 502 may further contribute to the one or more machine learning models generated by the data optimization component 402.

[0046] In one or more embodiments, the data center optimization component 502 can identify data centers 108 with high traffic and / or consider the traffic in one or more machine learning models (e.g., generated by the data optimization component 402) in determining one or more modifications to the data recovery scheme that can improve one or more evaluation values. For example, the data center optimization component 502 can further filter the secondary data centers 108 candidates to exclude data centers 108 with bandwidth utilization greater than the average bandwidth utilization. The data center optimization component 502 can also sort the secondary data centers 108 candidates based on bandwidth utilization. The data center optimization component 502 can also sort the microservice groups based on average application latency.

[0047] This allows the data center optimization component 502 to further contribute to identifying modifications to a given data recovery scheme based on a list of secondary data centers 108 candidates that are further refined based on the data traffic generated at the data center 108 and / or the application latency experienced by one or more microservice groups. For example, the data center optimization component 402 may select a data center 108 that is a high traffic data center 108. Relocation The data center optimization component 502 may further refine the identification of one or more modifications generated by the data optimization component 402 to identify modifications to a given data recovery scheme that may improve the evaluation value. As described herein, the evaluation component 302 may analyze any of the modifications identified by the data optimization component 402 and / or the data center optimization component 502 to ascertain whether a given modification may improve the evaluation value of the data recovery scheme compared to a previous version of the given data recovery scheme.

[0048] FIG. 6 is a block diagram of a method for detecting a cellular endothelial cell according to one or more embodiments described herein. Relocation 6 shows an exemplary and non-limiting diagram of system 100 further including component 602. Repeated descriptions of similar elements used in other embodiments described herein are omitted for the sake of brevity. In various embodiments, Relocation Component 602 can implement one or more modified data recovery schemes in response to evaluation component 302 determining that modifications identified by data optimization component 402 and / or data center optimization component 502 can improve the efficiency of a previously established data recovery scheme. For example, Relocation The component 602 can replicate and / or transfer one or more microservice groups from the primary data center 108 to one or more target secondary data centers 108 according to the modified data recovery scheme. Relocation The component 602 can remove the data from one or more primary data centers 108 .

[0049] FIG. 7 is a block diagram of a method for detecting a cellular endothelial cell according to one or more embodiments described herein. Relocation By Component 602 Relocation FIG. 7 shows an example, non-limiting diagram of a system 100 including data collected by the system. Repeated descriptions of similar elements used in other embodiments described herein are omitted for the sake of brevity. For example, FIG. Relocation 7 illustrates the system 100 of FIG. 2 after executing the modified data recovery scheme by component 602. As shown in FIG. 7 (e.g., as depicted by the dashed arrows shown in FIG. 7), the first microservice group is moved to the lower secondary data center 108. Relocation The second group of microservices can then be deployed to the secondary data center 108 on the right. Relocation In various embodiments, a first group of microservices can be paired with a lower secondary data center 108 and a second group of microservices can be paired with a right secondary data center 108 based on one or more machine learning models developed by the data optimization component 402 and / or the data center optimization component 502. Relocation The data recovery scheme implemented by the component 602 may include directing the recovery of data to a secondary data center 108 based on recently and / or historically indicated and measured performance data (e.g., relating to a group of microservices and / or a data center 108). Relocation can be instructed.

[0050] 8 illustrates a flow diagram of an exemplary, non-limiting method 800 that can facilitate the generation of one or more modifications to a data recovery scheme in accordance with one or more embodiments described herein. Repeated descriptions of similar elements used in other embodiments described herein are omitted for the sake of brevity.

[0051] At 802, the method 800 includes, by the system 100 operatively coupled to the processor 120 (e.g., via the communication component 112 and / or the initialization component 114), initiating a data transfer within the network 104 of the data center 108. Relocation For example, the one or more data recovery schemes can be input by one or more users into the system 100 via one or more input devices 106. In various embodiments, the one or more data recovery schemes can be initially generated by the system 100 (e.g., via the initialization component 114) based on one or more designated primary data centers 108, performance data for given data and / or data centers 108 of the network 104, and / or user-defined data recovery requirements. The one or more data recovery schemes can describe the replication and / or transfer of data from the one or more primary data centers 108 to one or more secondary data centers 108 as described herein.

[0052] At 804, the method 800 may include generating, by the system 100 (e.g., via the data optimization component 402 or the data center optimization component 502, or both), one or more machine learning models to determine one or more modifications to the one or more data recovery schemes of 802 based on the performance data exhibited by the network 104 of the data centers 108, or the one or more data recovery requirements, or both. For example, the one or more modifications may include determining whether to optimize the performance of one or more secondary data centers 108 paired with one or more primary data centers 108, or the microservice groups contained within the data, or both. Relocation The modification may be a prior modification. The one or more machine learning models may identify modifications based on measured performance data characterizing the past behavior of the microservice groups, or the past behavior of one or more data centers 108, or both, to achieve SLA targets and / or increase utilization of the network 104, according to various embodiments described herein. For example, the one or more modifications may relate to modifying a pairing of data centers 108 that exhibit performance data that does not meet one or more target SLOs, whereby the modification may attempt to reduce the number of unmet SLO targets exhibited during execution of the data recovery scheme. In another example, the one or more modifications may relate to modifying a pairing of data centers 108 that depend on a high traffic secondary data center 108, whereby the modification may attempt to increase utilization of the network 104.

[0053] 9 illustrates a flow diagram of an exemplary, non-limiting method 900 that can facilitate the generation of one or more modifications to a data recovery scheme in accordance with one or more embodiments described herein. Repeated descriptions of similar elements used in other embodiments described herein are omitted for the sake of brevity.

[0054] At 902, the method 900 includes, by the system 100 operatively coupled to the processor 120 (e.g., via the communication component 112 and / or the initialization component 114), initiating a data transfer within the network 104 of the data center 108. Relocation For example, the one or more data recovery schemes can be input by one or more users into the system 100 via one or more input devices 106. In various embodiments, the one or more data recovery schemes can be initially generated by the system 100 (e.g., via the initialization component 114) based on one or more designated primary data centers 108, performance data for given data and / or data centers 108 of the network 104, and / or user-defined data recovery requirements. The one or more data recovery schemes can describe the replication and / or transfer of data from the one or more primary data centers 108 to one or more secondary data centers 108 as described herein.

[0055] At 904, the method 900 includes optimizing, by the system 100 (e.g., via the data optimization component 402), a data optimization based on the performance data of the group of one or more microservice applications. Relocation For example, the machine learning model may include generating one or more first portions of the one or more machine learning models for optimizing the data. RelocationIn addition, the machine learning model can be developed based on performance data regarding the past behavior of one or more microservice groups contained within the data subject to management by the data recovery scheme. For example, the one or more machine learning models can be used to determine alternative SLA targets for one or more microservice groups. Relocation One or more secondary data centers 108 other than the secondary data center 108 specified in the data recovery scheme as the destination may be identified.

[0056] At 906, the method 900 may further include optimizing the data by the system 100 (e.g., via the data center optimization component 502) further based on performance data of at least one data center 108 operatively coupled to the network 104. Relocation The method may include generating one or more second portions of the one or more machine learning models to optimize the utilization of the network 104. For example, the machine learning models may further refine a determination of one or more modifications to the data recovery scheme to improve utilization of the network 104. For example, the one or more machine learning models may identify one or more secondary data centers 104 that exhibited a large amount of data traffic, which may enable the system 100 (e.g., via the data management component 110) to modify the data recovery scheme to pair a given primary data center 108 with an underutilized secondary data center 108 to more efficiently utilize the network 104 of the data center 108 while still meeting the SLO targets.

[0057] 10 illustrates a flow diagram of an exemplary, non-limiting method 1000 that can facilitate the generation of one or more modifications to a data recovery scheme in accordance with one or more embodiments described herein. Repeated descriptions of similar elements used in other embodiments described herein are omitted for the sake of brevity.

[0058] At 1002, the method 1000 includes, by the system 100 operatively coupled to the processor 120 (e.g., via the communication component 112 and / or the initialization component 114), initiating a data transfer within the network 104 of the data center 108. Relocation For example, the one or more data recovery schemes can be input by one or more users into the system 100 via one or more input devices 106. In various embodiments, the one or more data recovery schemes can be initially generated by the system 100 (e.g., via the initialization component 114) based on one or more designated primary data centers 108, performance data for given data and / or data centers 108 of the network 104, and / or user-defined data recovery requirements. The one or more data recovery schemes can describe the replication and / or transfer of data from the one or more primary data centers 108 to one or more secondary data centers 108 as described herein.

[0059] At 1004, the method 1000 may include modifying, by the system 100 (e.g., via the data optimization component 402, the data center optimization component 502, or the evaluation component 302, or a combination thereof), one or more data recovery schemes based on the performance data exhibited by the network 104 of the data center 108 and one or more data recovery requirements. For example, the method 1000 may include generating one or more machine learning models that may identify one or more modifications to the data recovery schemes that may improve achievement of SLO targets, or utilization of the network 104, or both. Further, in various embodiments, the method 1000 may include evaluating the one or more identified modifications to determine whether implementation of a given modification is predicted to achieve an intended improvement. Additionally, a given modification may be based on performance data measured for the given data (e.g., average bandwidth used, average application latency, target application latency, colocation group, and / or anti-colocation group), and / or performance data measured for one or more of the data centers 108 (e.g., geographic placement and / or partner allocation, maximum allocated bandwidth, and / or average network latency), thereby enabling the method 1000 to adapt one or more data recovery schemes based on the operation of the data and / or data centers 108 to increase the efficiency of the data recovery scheme while meeting one or more data recovery requirements (e.g., one or more target SLOs, target application latency, and / or target data center 108 location).

[0060] 11 illustrates a flow diagram of an exemplary, non-limiting method 1100 that can facilitate the generation of one or more modifications to a data recovery scheme in accordance with one or more embodiments described herein. Repeated descriptions of similar elements used in other embodiments described herein are omitted for the sake of brevity.

[0061] At 1102, the method 1100 includes, by the system 100 operatively coupled to the processor 120 (e.g., via the communication component 112 and / or the initialization component 114), initiating a data transfer within the network 104 of the data center 108. Relocation For example, the one or more data recovery schemes can be input by one or more users into the system 100 via one or more input devices 106. In various embodiments, the one or more data recovery schemes can be initially generated by the system 100 (e.g., via the initialization component 114) based on one or more designated primary data centers 108, performance data for given data and / or data centers 108 of the network 104, and / or user-defined data recovery requirements. The one or more data recovery schemes can describe the replication and / or transfer of data from the one or more primary data centers 108 to one or more secondary data centers 108 as described herein.

[0062] At 1104, the method 1100 includes optimizing, by the system 100 (e.g., via the data optimization component 402), the data based on performance data of the group of one or more microservice applications contained within the data. Relocation For example, the machine learning models may include generating one or more machine learning models for optimizing the performance of the data. RelocationIn addition, the machine learning model can be developed based on performance data regarding the historical behavior of the one or more microservice groups (e.g., average bandwidth used, average application latency, target application latency, colocation groups, or anti-colocation groups, or combinations thereof). For example, the one or more machine learning models can be used to determine one or more modifications to a data recovery scheme that can increase the number of SLA targets achieved during a given period. Additionally, the machine learning model can be developed based on performance data regarding the historical behavior of the one or more microservice groups (e.g., average bandwidth used, average application latency, target application latency, colocation groups, or anti-colocation groups, or combinations thereof). For example, the one or more machine learning models can be used to determine alternative SLA targets for the one or more microservice groups. Relocation In various embodiments, the one or more machine learning models may identify alternative secondary data centers 108 to pair with one or more given primary data centers 108 based on measured performance data of the past operation of one or more microservice groups. Additionally ... a given primary data center 108 based on measured performance data of the past operation of one or more microservice groups. Relocation Priority can be given to adjustment of the

[0063] At 1106, the method 1100 may further include optimizing the data by the system 100 (e.g., via the data center optimization component 502) based on the performance data of at least one data center 108 in the network 104 of data centers 108. RelocationThe one or more second machine learning models may further refine the determination of one or more modifications to the data recovery scheme to improve utilization of the network 104. For example, the one or more second machine learning models may identify one or more secondary data centers 104 that exhibited a large amount of data traffic, which may enable the system 100 (e.g., via the data management component 110) to modify the data recovery scheme to pair a given primary data center 108 with an underutilized secondary data center 108 to more efficiently utilize the network 104 of the data centers 108 while still meeting the SLO targets. In various embodiments, the one or more second machine learning models may further analyze the average bandwidth usage by a given data center 108, or the total bandwidth capacity of a given data center 108, or both, to efficiently distribute workload among the available secondary data centers 108, according to various embodiments described herein.

[0064] At 1108, the method 1100 may include modifying, by the system 100 (e.g., via the data management component 110), the one or more data recovery schemes based on the first and / or second machine learning models to generate modified data recovery schemes. For example, the method 1100 may include modifying, within a simulation environment, the one or more data recovery schemes according to the one or more modifications identified by the first and / or second machine learning models. By modifying the data recovery schemes within a simulation of a given network 104 of a data center 108, the method 1000 may predict the success of a given modified data recovery scheme prior to implementation across the network 104.

[0065] At 1110, the method 1100 may include analyzing, by the system 100 (e.g., via the evaluation component 302), the one or more modified data recovery schemes to determine whether the modified data recovery schemes are predicted to improve performance data compared to the original data recovery scheme and meet one or more data recovery requirements (e.g., SLO targets, latency requirements, or location requirements, or a combination thereof). For example, the analysis at 1110 may include determining one or more evaluation values ​​according to various embodiments described herein. Modifications predicted to improve the evaluation value over a previously established benchmark may be implemented in the network 104, while modifications predicted to reduce the evaluation value or leave the evaluation value unaffected may not be implemented in the network 104. In various embodiments, features 1104, 1106, 1108, or 1110, or combinations thereof, of the method 1100 may be repeated multiple times until all possibilities have been explored by the machine learning model or until modifications predicted to improve the evaluation value have been identified, or both.

[0066] Although this disclosure includes detailed descriptions of cloud computing, it should be understood that implementation of the teachings described herein is not limited to a cloud computing environment. Rather, embodiments of the invention may be implemented in conjunction with any other type of computing environment not currently known or later developed.

[0067] Cloud computing is a model of service delivery for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) that can be rapidly provisioned and released with minimal administrative effort or interaction with a service provider. The cloud model may include at least five characteristics, at least three service models, and at least four deployment models.

[0068] Its features are as follows.

[0069] On-Demand Self-Service: Cloud consumers can unilaterally provision computing capacity, such as server time and network storage, automatically as needed, without the need for human interaction with the provider of the service.

[0070] Broad Network Access: Capabilities are available over the network and are accessed through standard mechanisms that facilitate use by heterogeneous thin or thick client platforms (e.g., cell phones, laptops, and PDAs).

[0071] Resource Pooling: Pooling provider computing resources to serve multiple consumers using a multi-tenant model where various physical and virtual resources are dynamically allocated and reallocated according to demand. Consumers generally have no control over or knowledge of the exact location of the resources provided to them, although there is a sense of location independence in that the location may be identifiable at a higher level of abstraction (e.g., country, state, or data center).

[0072] Rapid Elasticity: Capacity can be rapidly and elastically provisioned, sometimes automatically, to quickly scale out and rapidly release to quickly scale in. To the consumer, provisionable capacity often appears to be unlimited and can be purchased in any quantity at any time.

[0073] Metered Services: Cloud systems leverage metering capabilities at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts) to automatically control and optimize resource usage. Resource usage can be monitored, managed, and reported to provide transparency to both providers and consumers of the services utilized.

[0074] The service model is as follows:

[0075] Software as a Service (SaaS): The ability offered to the consumer is to use the provider's applications running on a cloud infrastructure. The applications are accessible from a variety of client devices through thin-client interfaces such as web browsers (e.g., web-based email). The consumer has no management or control over the underlying cloud infrastructure, including networks, servers, operating systems, storage, or even individual application features, with the possible exception of limited user-specific application configuration settings.

[0076] Platform as a Service (PaaS): The capability offered to a consumer is to deploy applications that the consumer creates or acquires, written using programming languages ​​and tools supported by the provider, onto a cloud infrastructure. The consumer does not manage or control the underlying cloud infrastructure, including networks, servers, operating systems, or storage, but does control the deployed applications and possibly the application hosting environment configuration.

[0077] Infrastructure as a Service (IaaS): The ability offered to consumers is to provision processing, storage, network, and other basic computing resources onto which the consumer can deploy and run any software, which may include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure, but does control the operating systems, storage, deployed applications, and possibly limited control over selected networking components (e.g., host firewalls).

[0078] The deployment model is as follows:

[0079] Private Cloud: The cloud infrastructure is operated exclusively for an organization. It can be managed by the organization or a third party and can be on-premise or off-premise.

[0080] Community Cloud: Cloud infrastructure is shared by several organizations to support a specific community with common concerns (e.g., mission, security requirements, policies, and compliance considerations). It may be managed by the organization or a third party and may reside on-premise or off-premise.

[0081] Public Cloud: The cloud infrastructure is made available to the general public or large industry organizations and is owned by an organization that sells cloud services.

[0082] Hybrid Cloud: A cloud infrastructure is a composite of two or more clouds (private, community, or public) that remain unique entities but are joined by standardized or proprietary technologies that enable data and application portability (e.g., cloud bursting for load balancing between clouds).

[0083] Cloud computing environments are service-oriented with an emphasis on statelessness, low coupling, modularity, and semantic interoperability. At the core of cloud computing is an infrastructure that includes a network of interconnected nodes.

[0084] Referring now to FIG. 12, an exemplary cloud computing environment 1200 is illustrated. As illustrated, the cloud computing environment 1200 includes one or more cloud computing nodes 1202 with which local computing devices used by cloud consumers, such as, for example, a personal digital assistant (PDA) or cell phone 1204, a desktop computer 1206, a laptop computer 1208, or an automobile computer system 1210, or combinations thereof, may communicate. The nodes 1202 may communicate with each other. They may be physically or virtually grouped (not shown), for example, in one or more networks, such as the private, community, public, or hybrid clouds described above, or combinations thereof. This enables the cloud computing environment 1200 to provide infrastructure-as-a-service, platform-as-a-service, and / or software-as-a-service services without the cloud consumer having to maintain resources on a local computing device. It should be understood that the types of computing devices 1204-1210 shown in FIG. 12 are intended to be exemplary only, and that the computing node 1202 and cloud computing environment 1200 can communicate with any type of computerized device via any type of network and / or network-addressable connection (e.g., using a web browser).

[0085] Referring now to FIG. 13, a set of functional abstraction layers provided by cloud computing environment 1200 (FIG. 12) is shown. Repeated descriptions of similar elements used in other embodiments described herein are omitted for the sake of brevity. It should be understood in advance that the components, layers, and functions shown in FIG. 13 are intended to be exemplary only, and embodiments of the present invention are not limited thereto. As shown, the following layers and corresponding functions are provided:

[0086] Hardware and software layer 1302 includes hardware and software components. Examples of hardware components include mainframe 1304, reduced instruction set computer (RISC) architecture based server 1306, server 1308, blade server 1310, storage device 1312, and network and networking components 1314. In some embodiments, software components include network application server software 1316 and database software 1318.

[0087] The virtualization layer 1320 provides an abstraction layer from which the following examples of virtual entities may be provided: virtual servers 1322, virtual storage 1324, virtual networks including virtual private networks 1326, virtual applications and operating systems 1328, and virtual clients 1330.

[0088] In one example, management layer 1332 may provide the following functions: Resource provisioning 1334 provides dynamic procurement of computing and other resources utilized to execute tasks within the cloud computing environment. Metering and pricing 1336 provides cost tracking as resources are utilized within the cloud computing environment and accounting or billing for the consumption of these resources. In one example, these resources may include application software licenses. Security provides identity verification of cloud consumers and tasks as well as protection for data and other resources. User portal 1338 provides consumers and system administrators access to the cloud computing environment. Service level management 1340 provides allocation and management of cloud computing resources such that service levels are met. Service level agreement (SLA) planning and fulfillment 1342 provides advance arrangement and procurement of cloud computing resources anticipated to be required in the future according to SLAs.

[0089] Workload layer 1344 provides examples of functionality for which a cloud computing environment may be utilized. Examples of workloads and functions that may be provided from this layer include mapping and navigation 1346, software development and lifecycle management 1348, virtual classroom instructional delivery 1350, data analytics processing 1352, transaction processing 1354, and data recovery 1356. Various embodiments of the present invention may utilize the cloud computing environment described with reference to Figures 12 and 13 to analyze performance data of various data centers 108 via network 104, modify one or more data recovery schemes based on the performance data, and / or implement modified data recovery schemes.

[0090] The present invention may be a system, method, or computer program product, or combination thereof, at any possible level of technical detail integration. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to execute aspects of the present invention. A computer readable storage medium may be a tangible device capable of holding and storing instructions for use by an instruction execution device. A computer readable storage medium may be, for example, but not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination thereof. A non-exhaustive list of more specific examples of computer readable storage media includes portable computer diskettes, hard disks, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disk read only memory (CD-ROM), digital versatile disk (DVD), memory stick (MRAM), and the like. Registered trademark ), Floppy ( Registered trademark ) disks, mechanically encoded devices such as punch cards or grooved ridge structures having instructions recorded thereon, and any suitable combination of these. Computer-readable storage media, as used herein, should not be construed as being a transitory signal per se, such as, for example, radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., light pulses passing through a fiber optic cable), or electrical signals transmitted over a wire.

[0091] The computer readable program instructions described herein may be downloaded from a computer readable storage medium to the respective computing / processing device or to an external computer or storage device over a network, such as, for example, the Internet, a local area network, a wide area network, or a wireless network, or a combination thereof. The network may include copper transmission cables, optical transmission fiber, wireless transmission, routers, firewalls, switches, gateway computers, or edge servers, or a combination thereof. A network adapter card or network interface of each computing / processing device receives the computer readable program instructions from the network and transfers the computer readable program instructions for storage in a computer readable storage medium within the respective computing / processing device.

[0092] Computer readable program instructions for carrying out the operations of the present invention may be assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state setting data, configuration data for an integrated circuit, or Smalltalk ( Registered trademarkThe computer readable program instructions may be source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as C++, C++, or the like, and procedural programming languages ​​such as the "C" programming language or similar programming languages. The computer readable program instructions may be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or a connection may be made to an external computer (e.g., via the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuits, field programmable gate arrays (FPGAs), or programmable logic arrays (PLAs), may personalize the electronic circuitry by utilizing state information of the computer readable program instructions to execute the computer readable program instructions to perform aspects of the present invention.

[0093] Aspects of the present invention are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer readable program instructions.

[0094] These computer-readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine such that, when the instructions are executed by the processor of the computer or other programmable data processing apparatus, means are generated for implementing the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams. These computer-readable program instructions may also be stored on a computer-readable storage medium capable of directing a computer, programmable data processing apparatus, or other device, or combination thereof, to function in a particular manner, such that the computer-readable storage medium on which the instructions are stored constitutes an article of manufacture including instructions that implement aspects of the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams.

[0095] Furthermore, computer-readable program instructions may be loaded into a computer, other programmable data processing apparatus, or other device to cause the computer, other programmable apparatus, or other device to perform a series of operational steps, thereby generating a computer-implemented process that, when executed on the computer, other programmable apparatus, or other device, implements the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams.

[0096] The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowcharts or block diagrams may represent a module, segment, or part of instructions that includes one or more executable instructions for implementing the specified logical function. In some alternative implementations, the functions described in the blocks may occur out of the order shown. For example, depending on the functionality involved, two blocks shown in succession may in fact be executed substantially simultaneously, or the blocks may possibly be executed in the reverse order. It will also be noted that each block in the block diagrams and / or flowchart illustrations, and combinations of blocks in the block diagrams and / or flowchart illustrations, may be implemented by a dedicated hardware-based system that performs the specified functions or acts or executes a combination of dedicated hardware and computer instructions.

[0097] To provide additional context for the various embodiments described herein, Figure 14 and the following discussion are intended to provide a general description of a suitable computing environment 1400 in which various embodiments of the embodiments described herein may be implemented. Although the embodiments have been described above in the general context of computer-executable instructions that may be executed on one or more computers, those skilled in the art will appreciate that the embodiments may also be implemented in combination with other program modules, or as a combination of hardware and software, or both.

[0098] Generally, program modules include routines, programs, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Those skilled in the art will also appreciate that the methods of the present invention can be practiced with other computer system configurations, including single-processor or multi-processor computer systems, minicomputers, mainframe computers, Internet of Things ("IoT") devices, distributed computing systems, and personal computers, handheld computing devices, microprocessor-based or programmable consumer electronics, and the like, each of which can be operatively coupled to one or more associated devices.

[0099] The illustrated embodiments of the present disclosure may also be practiced in distributed computing environments where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

[0100] A computing device typically includes various media, which may include computer-readable storage media, machine-readable storage media, or communication media, or a combination thereof, and these two terms are used differently from each other in this specification as follows. A computer-readable storage medium or machine-readable storage medium may be any available storage medium that can be accessed by a computer, and includes both volatile and non-volatile media, removable and non-removable media. By way of example and not limitation, a computer-readable storage medium or machine-readable storage medium may be implemented in association with any method or technology for storing information, such as computer-readable or machine-readable instructions, program modules, structured or unstructured data, etc.

[0101] A computer-readable storage medium may include, but is not limited to, random access memory ("RAM"), read-only memory ("ROM"), electrically erasable programmable read-only memory ("EEPROM"), flash memory or other memory technology, compact disk read-only memory ("CD-ROM"), digital versatile disk ("DVD"), Blu-ray disk ("BD") or other optical disk storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage device, solid state drive or other solid state storage device, or other tangible and / or non-transitory medium that can be used to store the desired information. In this regard, the terms "tangible" or "non-transitory" herein as applied to storage, memory, or computer-readable medium should be understood as modifiers to exclude only the propagating, transitory signal itself, and no disclaimer is made with respect to all standard storage, memory, or computer-readable medium that is not only the propagating, transitory signal itself.

[0102] The computer-readable storage medium can be accessed by one or more local or remote computing devices for various operations on the information stored by the medium, for example, via an access request, query, or other data retrieval protocol.

[0103] Communication media typically embodied computer readable instructions, data structures, program modules, or other structured or unstructured data in a data signal, such as a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery or transmission media. The term "modulated data signal or signals" refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal or signals. By way of example, and not limitation, communication media include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.

[0104] Referring again to FIG. 14, an exemplary environment 1400 for implementing various embodiments of the aspects described herein includes a computer 1402 including a processing unit 1404, a system memory 1406, and a system bus 1408. The system bus 1408 couples system components including, but not limited to, the system memory 1406 to the processing unit 1404. The processing unit 1404 can be any of a variety of commercially available processors. Dual microprocessors and other multi-processor architectures can also be utilized as the processing unit 1404.

[0105] The system bus 1408 can be any of several types of bus structures, which can be further interconnected to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. The system memory 1406 includes a ROM 1410 and a RAM 1412. A basic input / output system ("BIOS") can be stored in non-volatile memory, such as, for example, a ROM, an erasable programmable read-only memory ("EPROM"), or an EEPROM, which includes basic routines that help transfer information between elements within the computer 1402, such as during start-up. The RAM 1412 can also include a high-speed RAM, such as a static RAM, for caching data.

[0106] The computer 1402 includes an internal hard disk drive ("HDD") 1414 (e.g., EIDE, SATA), one or more external storage devices 1416 (e.g., magnetic floppy ( Registered trademark ) Disk Drive ("FDD"), Memory Stick ( Registered trademark) or flash drive reader, memory card reader, etc.), and optical disk drive 1420 (e.g., capable of reading and writing to CD-ROM disks, DVDs, BDs, etc.). Although internal HDD 1414 is illustrated as being located within computer 1402, internal HDD 1414 may also be configured for external use within a suitable chassis (not shown). Also, although not illustrated in environment 1400, a solid state drive ("SSD") may be used in addition to or in place of HDD 1414. HDD 1414, external storage device 1416, and optical disk drive 1420 may be connected to system bus 1408 by HDD interface 1424, external storage interface 1426, and optical drive interface 1428, respectively. HDD interface 1424 may include at least one or both of Universal Serial Bus ("USB") and Institute of Electrical and Electronics Engineers ("IEEE") 1394 interface technologies. Other external drive connection technologies are within the contemplation of the embodiments described herein.

[0107] The drives and their associated computer-readable storage media provide non-volatile storage of data, data structures, computer-executable instructions, and the like. In the case of computer 1402, the drives and storage media accommodate the storage of any data in a suitable digital format. Although the above description of computer-readable storage media refers to each type of storage device, those skilled in the art will appreciate that other types of computer-readable storage media, whether now existing or later developed, may also be used in the exemplary operating environment, and further that such storage media may include computer-executable instructions for performing the methods described herein.

[0108] A number of program modules can be stored in the drives and RAM 1412, including an operating system 1430, one or more application programs 1432, other program modules 1434, and program data 1436. All or portions of the operating system, applications, modules, and / or data may also be cached in RAM 1412. The systems and methods described herein can be implemented utilizing various commercially available operating systems or combinations of operating systems.

[0109] The computer 1402 may optionally include emulation technology. For example, a hypervisor (not shown) or other intermediary may emulate a hardware environment for the operating system 1430, and the emulated hardware may optionally differ from the hardware shown in FIG. 14. In such an embodiment, the operating system 1430 may include one of multiple virtual machines ("VMs") hosted on the computer 1402. Additionally, the operating system 1430 may include a Java ( Registered trademark A runtime environment, such as the .NET Framework or the .NET runtime environment, may be provided to the application 1432. The runtime environment is a consistent execution environment that allows the application 1432 to run on any operating system that includes the runtime environment. Similarly, the operating system 1430 may support containers, and the application 1432 may be in the form of a container, which is a lightweight, stand-alone, executable package of software that includes, for example, code, runtime, system tools, system libraries, and settings for the application.

[0110] Additionally, computer 1402 may be enabled with a security module, such as a Trusted Processing Module ("TPM"). For example, with a TPM, a boot component may hash the next boot component in time and wait for the result to match a protected value before loading the next boot component. This process may occur at any layer in the code execution stack of computer 1402, for example, applied at the application execution level or at the operating system ("OS") kernel level, thereby enabling security at any code execution level.

[0111] A user may enter commands and information into the computer 1402 via one or more wired / wireless input devices, such as a keyboard 1438, a touch screen 1440, and a pointing device, such as a mouse 1442. Other input devices (not shown) may include a microphone, an infrared ("IR") remote control, a radio frequency ("RF") remote control, or other remote control, a joystick, a virtual reality controller or headset, or both, a game pad, a stylus pen, an image input device, such as a camera, a gesture sensor input device, a vision movement sensor input device, an emotion or face detection device, a biometric input device, such as a fingerprint or iris scanner, or the like. These and other input devices are often connected to the processing unit 1404 via an input device interface 1444, which may be coupled to the system bus 1408, but may also include a parallel port, an IEEE 1394 serial port, a game port, a USB port, an IR interface, a BLUETOOTH ( Registered trademark ) interface.

[0112] A monitor 1446 or other type of display device can also be connected to the system bus 1408 via an interface, such as a video adapter 1448. In addition to the monitor 1446, computers typically include other peripheral output devices (not shown), such as speakers, printers, etc.

[0113] The computer 1402 can operate in a networked environment using logical connections via wired and / or wireless communications to one or more remote computers, such as a remote computer 1450. The remote computer 1450 can be a workstation, a server computer, a router, a personal computer, a portable computer, a microprocessor-based entertainment device, a peer device or other common network node, and typically includes many or all of the elements described relative to the computer 1402, although for purposes of brevity, only a memory / storage device 1452 is shown. The logical connections depicted include wired / wireless connections to a local area network ("LAN") 1454, or to larger networks, such as a wide area network ("WAN") 1456, or both. Such LAN and WAN networking environments are commonplace in offices and businesses and facilitate enterprise-wide computer networks, such as intranets, all of which may be connected to a global communications network, such as the Internet.

[0114] When used in a LAN networking environment, the computer 1402 can be connected to the local network 1454 via a wired and / or wireless communication network interface or adapter 1458. The adapter 1458 can facilitate wired or wireless communication to the LAN 1454, which can also include a wireless access point ("AP") disposed on the LAN 1454 for communicating with the adapter 1458 in a wireless mode.

[0115] When used in a WAN networking environment, the computer 1402 may include a modem 1460 or may be connected to a communications server on the WAN 1456 via other means for establishing communications over the WAN 1456, such as, for example, via the Internet. The modem 1460 may be internal or external and may be a wired or wireless device and may be connected to the system bus 1408 via the input device interface 1444. In a networked environment, program modules depicted relative to the computer 1402, or portions thereof, may be stored in a remote memory / storage device 1452. It will be appreciated that the illustrated network connections are examples and other means of establishing a communications link between the computers may be used.

[0116] When used in either a LAN or WAN networking environment, the computer 1402 can access a cloud storage system or other network-based storage system in addition to or instead of the external storage device 1416 described above. Typically, the connection between the computer 1402 and the cloud storage system can be established via the LAN 1454 or WAN 1456, for example, by an adapter 1458 or modem 1460, respectively. Upon connecting the computer 1402 to the associated cloud storage system, the external storage interface 1426, with the aid of the adapter 1458 and / or modem 1460, can manage the storage provided by the cloud storage system as if it were any other type of external storage. For example, the external storage interface 1426 can be configured to provide access to cloud storage sources as if those sources were physically connected to the computer 1402.

[0117] The computer 1402 is operable to communicate with any wireless device or entity operatively disposed in wireless communication, such as printers, scanners, desktop and / or portable computers, portable data assistants, communications satellites, any equipment or location associated with a radio-detectable tag (e.g., kiosks, newsstands, product shelves, etc.), and telephones. This includes wireless technologies such as Wireless Fidelity ("Wi-Fi") and BLUETOOTH ( Registered trademark ) wireless technology. Thus, the communication can be in a predefined structure, like a traditional network, or it can simply be an ad-hoc communication between at least two devices.

[0118] The above description includes merely examples of systems, computer program products, and computer-implemented methods. Of course, for purposes of describing the present disclosure, it is not possible to describe every conceivable combination of components, products, or computer-implemented methods, or combinations thereof, but one of ordinary skill in the art can recognize that numerous further combinations and permutations of the present disclosure are possible. Furthermore, to the extent that the terms "includes," "has," "possesses," and the like are used in the detailed description, claims, appendices, and drawings, such terms shall be as inclusive as the term "comprising" when interpreted as such when used as a transitional term in the claims. The description of the various embodiments is presented for illustrative purposes, but is not intended to be exhaustive or limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terms used herein are selected to best explain the principles of the embodiments, practical applications, or technical improvements to the art found in the marketplace, or to enable those of ordinary skill in the art to understand the embodiments disclosed herein.

[0119] The present invention is summarized below. [Section 1] 1. A system comprising: a memory storing one or more computer readable programs; a processor operatively coupled to the memory, the processor being adapted to execute the computer readable program; Equipped with The computer readable program comprises: modifying a data recovery scheme based on performance data and data recovery requirements associated with a network of data centers, the data centers comprising one or more primary data centers initially responsible for storing, processing, or delivering, or a combination thereof, a given data, and one or more secondary data centers to which the given data is to be relocated; the performance data is for a group of microservice applications contained within the data, and includes at least one member selected from the group consisting of: a location of the data center, a bandwidth of the network, a latency of the network, a bandwidth used by the data, a latency exhibited during execution of the data, and a latency exhibited during the relocation of the data; the data recovery requirements include at least one second member selected from a second group consisting of: the location of the data center, and a service level objective; the data recovery scheme directs the relocation of data within the network of the data centers, and may describe the replication and / or transfer of data from the one or more primary data centers to the one or more secondary data centers; generating a machine learning model for optimizing the relocation of the data based on the group of microservice applications, where the machine learning model identifies a relationship between modifications to the data recovery scheme and the data recovery requirements based on the performance data of the group of microservice applications. The system. [Section 2] The computer readable program comprises: further causing the processor to modify the data recovery scheme to generate a modified data recovery scheme, where the modified data recovery scheme directs reallocation of data within the network of data centers and may describe replicating and / or transferring data from the one or more primary data centers to the one or more secondary data centers; The computer readable program comprises: further causing the processor to analyze the modified data recovery scheme to determine whether the modified data recovery scheme is predicted to achieve improved performance data compared to the original data recovery scheme and to meet the data recovery requirements; The computer readable program comprises: and further causing the processor to perform the relocation of the data in accordance with the modified data recovery scheme based on the evaluation component determining that the modified data recovery scheme is predicted to improve the performance data and meet the data recovery requirements. Item 1. The system according to item 1. [Section 3] the performance data further relates to at least one data center of the network; The computer readable program comprises: further causing the processor to generate a machine learning model for optimizing the relocation of the data further based on the at least one data center, where the machine learning model identifies a relationship between a second modification to the data recovery scheme and the data recovery requirements based on the performance data of the at least one data center. Item 1 or 2. The system according to item 1 or 2. [Section 4] The computer readable program comprises: analyzing one or more initial data recovery schemes and configuring an initial state for each data center pair specified by the analyzed data recovery schemes, where the data center pair comprises a primary data center and a secondary data center; Item 3. The system according to any one of items 1 to 3. [Section 5] 1. A system comprising: A memory for storing a computer readable program; a processor operatively coupled to the memory for executing the computer readable program; Equipped with The computer readable program comprises: and causing the processor to generate a machine learning model for determining modifications to a data recovery scheme based on performance data associated with a network of a data center, the data center comprising one or more primary data centers initially responsible for storing, processing and / or delivering a given data, and one or more secondary data centers to which the given data is to be relocated, the performance data being related to a group of microservices applications contained within the data, the performance data being related to a location of the data center, the bandwidth of the network, the latency of the network, the bandwidth used by the data, the execution time of the data, the bandwidth of the network, the latency of the network, the bandwidth of the network, the execution time of the data ... and a latency indicated during the relocation of the data; the data recovery requirements include at least one member selected from a second group consisting of the location of the data center and a service level objective; the data recovery scheme directs the relocation of data within the network of data centers and may describe the replication and / or transfer of data from the one or more primary data centers to the one or more secondary data centers; and the machine learning model identifies a relationship between the modifications to the data recovery scheme and the data recovery requirements based on the performance data. The computer readable program comprises: causing the processor to exclude potential secondary data centers from the network of data centers based on the performance data; The computer readable program comprises: further causing the processor to generate a first portion of a machine learning model for optimizing the relocation of the data based on the performance data of the group of microservice applications. The system. [Section 6] the performance data further relates to at least one data center of the network; The computer readable program comprises: generating a second portion of the machine learning model for optimizing the relocation of the data further based on the performance data of the at least one data center. Item 5. The system according to item 5. [Section 7] The computer readable program comprises: further causing the processor to modify the data recovery scheme to generate a modified data recovery scheme, where the modified data recovery scheme directs reallocation of data within the network of data centers and may describe replicating and / or transferring data from the one or more primary data centers to the one or more secondary data centers; The computer readable program comprises: further causing the processor to analyze the modified data recovery scheme to determine whether the modified data recovery scheme is predicted to achieve improved performance data as compared to the original data recovery scheme and to meet the data recovery requirements. Item 5. The system according to item 5. [Section 8] 1. A computer-implemented method, comprising: generating a machine learning model for determining modifications to a data recovery scheme based on performance data associated with a network of a data center, the data center comprising one or more primary data centers initially responsible for storing, processing and / or delivering a given data, and one or more secondary data centers to which the given data is to be relocated, the performance data being related to a group of microservices applications contained within the data, the performance data including a location of the data center, a bandwidth of the network, a latency of the network, a bandwidth used by the data, a latency exhibited during execution of the data, and a latency of the data, the performance data including a bandwidth associated with the network ... the performance data including a bandwidth associated with the network, a latency exhibited during execution of the data, and the performance data including a bandwidth associated with the network, a latency exhibited during execution of the data, the performance data including a bandwidth the data recovery requirements include at least one second member selected from a second group consisting of the location of the data center, and a latency exhibited during the relocation of the data center, the data recovery requirements include at least one second member selected from a second group consisting of the location of the data center, and a service level objective, the data recovery scheme directs the relocation of data within the network of data centers and may describe the replication and / or transfer of data from the one or more primary data centers to the one or more secondary data centers, and the machine learning model identifies a relationship between modifications to the data recovery scheme and the data recovery requirements based on the performance data of the group of microservice applications. sorting the data centers based on the data center average available bandwidth of said network; eliminating potential secondary data centers from said network based on said performance data; generating a first portion of a machine learning model for optimizing the relocation of the data based on the performance data of the group of microservice applications; The computer-implemented method comprising: [Section 9] The system further comprises: Sorting data centers based on the data center's average available bandwidth in said network. Item 9. The computer-implemented method of item 8, further comprising: [Section 10] The system further comprises: eliminating potential secondary data centers from said network based on said performance data; Item 10. The computer-implemented method of item 9, further comprising: [Section 11] generating a second portion of the machine learning model for optimizing the relocation of the data further based on the performance data of the at least one data center; and 11. The computer-implemented method according to any one of items 8 to 10, further comprising: [Section 12] The modifying includes generating a modified data recovery scheme; The system comprises: Analyzing the modified data recovery scheme to determine whether the modified data recovery scheme is expected to achieve improved performance data as compared to the original data recovery scheme and meet the data recovery requirements. 12. The computer-implemented method of claim 11, further comprising: [Section 13] 13. The computer-implemented method of any one of claims 8 to 12, wherein the relocation of the data is performed via a cloud computing environment. [Section 14] 1. A computer-implemented method, comprising: modifying a data recovery scheme based on performance data associated with a network of data centers and data recovery requirements, where the data centers comprise one or more primary data centers initially responsible for storing, processing and / or delivering a given data, and one or more secondary data centers to which the given data is to be relocated, the performance data being related to a group of microservice applications contained within the data and including at least one member selected from the group consisting of: a location of the data center, a bandwidth of the network, a latency of the network, a bandwidth used by the data, a latency exhibited during execution of the data, and a latency exhibited during the relocation of the data, the data recovery requirements including at least one second member selected from a second group consisting of: a location of the data center, and a service level objective, the data recovery scheme directing the relocation of data within the network of the data centers and may describe the replication and / or transfer of data from the one or more primary data centers to the one or more secondary data centers; generating a machine learning model for optimizing the relocation of the data based on the group of microservice applications; 4. A computer-implemented method comprising: [Section 15] The system further comprises: Sorting the microservice groups according to a ratio of average application latency to target application latency, where the sorting comprises sorting the microservice groups such that microservice groups that are not achieving one or more service level objective targets are followed by microservice groups that are at risk of not achieving one or more service level objective targets. 15. The computer-implemented method of claim 14, further comprising: [Section 16] The system further comprises: eliminating potential secondary data centers from said network of data centers based on said performance data; 16. The computer-implemented method of claim 15, further comprising: [Section 17] The system further comprises: generating, by the system, a second machine learning model for optimizing the relocation of the data further based on the at least one data center. 17. The computer-implemented method according to any one of items 14 to 16, further comprising: [Section 18] the modifying is based on the machine learning model and the second machine learning model to generate a modified data recovery scheme; The system comprises: Analyzing the modified data recovery scheme to determine whether the modified data recovery scheme is expected to achieve improved performance data as compared to the original data recovery scheme and meet the data recovery requirements. 16. The computer-implemented method of claim 15, further comprising: [Section 19] 17. The computer-implemented method of any one of claims 14 to 16, wherein the relocation of the data is performed via a cloud computing environment. [Section 20] A computer program for adaptively distributing data within a network of data centers, the computer program causing a system to execute a computer-implemented method according to any one of claims 8 to 13. [Section 21] A computer program for adaptively distributing data within a network of data centers, the computer program causing a system to execute a computer-implemented method according to any one of claims 14 to 19.

Claims

1. 1. A system comprising: a memory storing one or more computer readable programs; a processor operatively coupled to the memory for executing the computer readable program; Equipped with The computer readable program comprises: modifying a data recovery scheme based on performance data and data recovery requirements associated with a network of data centers, the data centers comprising one or more primary data centers initially responsible for storing, processing and / or delivering a given data, and one or more secondary data centers to which the given data is to be relocated; the performance data relates to a group of microservice applications contained within the data, and includes at least one member selected from the group consisting of: a location of the data center, a bandwidth of the network, a latency of the network, a bandwidth used by the data, a latency exhibited during execution of the data, and a latency exhibited during the relocation of the data; the data recovery requirements include at least one second member selected from a second group consisting of: a location of the data center, and a service level objective; the data recovery scheme directs the relocation of data within the network of the data center, and may describe the replication and / or transfer of data from the one or more primary data centers to the one or more secondary data centers; generating a machine learning model for optimizing the relocation of the data based on the group of microservice applications, where the machine learning model identifies a relationship between modifications to the data recovery scheme and the data recovery requirements based on the performance data of the group of microservice applications. The system.

2. The computer readable program comprises: further causing the processor to modify the data recovery scheme to generate a modified data recovery scheme, where the modified data recovery scheme directs a relocation of data within the network of data centers and may describe replicating and / or transferring data from the one or more primary data centers to the one or more secondary data centers; The computer readable program comprises: further causing the processor to analyze the modified data recovery scheme to determine whether the modified data recovery scheme is predicted to achieve improved performance data compared to the data recovery scheme and to meet the data recovery requirements; The computer readable program comprises: and further causing the processor to perform the relocation of the data in accordance with the modified data recovery scheme based on the evaluation component determining that the modified data recovery scheme is predicted to improve the performance data and meet the data recovery requirements. The system of claim 1 .

3. the performance data further relates to at least one data center of the network; The computer readable program comprises: further causing the processor to generate a machine learning model for optimizing the relocation of the data further based on the at least one data center, where the machine learning model identifies a relationship between a second modification to the data recovery scheme and the data recovery requirements based on the performance data of the at least one data center.

3. A system according to claim 1 or 2.

4. The computer-readable program comprises: analyzing one or more initial data recovery schemes and configuring an initial state of each data center pair specified by the analyzed data recovery schemes, where the data center pair comprises a primary data center and a secondary data center; A system according to any one of claims 1 to 3.

5. A system comprising: A memory for storing a computer readable program; a processor operatively coupled to the memory for executing the computer readable program; Equipped with The computer readable program comprises: and causing the processor to generate a machine learning model for determining modifications to a data recovery scheme based on performance data associated with a network of a data center, the data center comprising one or more primary data centers initially responsible for storing, processing and / or delivering a given data, and one or more secondary data centers to which the given data is to be relocated, the performance data being related to a group of microservices applications contained within the data, the performance data being related to a location of the data center, the bandwidth of the network, the latency of the network, the bandwidth used by the data, the execution time of the data, the bandwidth of the network, the latency of the network, the bandwidth of the network, the execution time of the data, the bandwidth of the network, the latency of the network, the bandwidth of the network, the execution time of the data, the bandwidth of the network, the latency of the network, the bandwidth of the network, the execution time of the data, the bandwidth of the network, the bandwidth of the network, the latency of the network, the bandwidth ... and at least one member selected from a group consisting of latency indicated in a row and latency indicated during the relocation of the data, the data recovery requirements including at least a second member selected from a second group consisting of the location of the data center and a service level objective, the data recovery scheme directing the relocation of data within the network of the data centers and may describe the replication and / or transfer of data from the one or more primary data centers to the one or more secondary data centers, and the machine learning model identifies a relationship between the modifications to the data recovery scheme and the data recovery requirements based on the performance data. The computer readable program comprises: causing the processor to exclude potential secondary data centers from the network of data centers based on the performance data; The computer readable program comprises: further causing the processor to generate a first portion of a machine learning model for optimizing the relocation of the data based on the performance data of the group of microservice applications. The system.

6. the performance data further relates to at least one data center of the network; The computer readable program comprises: generating a second portion of the machine learning model for optimizing the relocation of the data further based on the performance data of the at least one data center. The system of claim 5.

7. The computer readable program comprises: further causing the processor to modify the data recovery scheme to generate a modified data recovery scheme, where the modified data recovery scheme directs a relocation of data within the network of data centers and may describe replicating and / or transferring data from the one or more primary data centers to the one or more secondary data centers; The computer readable program comprises: further causing the processor to analyze the modified data recovery scheme to determine whether the modified data recovery scheme is predicted to achieve improved performance data compared to the data recovery scheme and to meet the data recovery requirements. The system of claim 5.

8. A computer-implemented method, comprising: a system operatively coupled to a processor, comprising: generating a machine learning model for determining modifications to a data recovery scheme based on performance data associated with a network of a data center, the data center comprising one or more primary data centers initially responsible for storing, processing and / or delivering a given data, and one or more secondary data centers to which the given data is to be relocated, the performance data being related to a group of microservice applications contained within the data, the performance data including a location of the data center, a bandwidth of the network, a latency of the network, a bandwidth used by the data, a latency exhibited during execution of the data, and a latency of the data, the performance data including ... the performance data including a bandwidth used by the data, the latency of the data, the performance data including a bandwidth used by the data, the latency of the data, the latency of the data, the performance data including a bandwidth used by the data, the latency of the data, the latency of the data, the performance data including a bandwidth used by the data, the latency of the data recovery requirements include at least one second member selected from a second group consisting of the location of the data center and a service level objective; the data recovery scheme directs the relocation of data within the network of data centers and may describe the replication and / or transfer of data from the one or more primary data centers to the one or more secondary data centers; and the machine learning model identifies a relationship between modifications to the data recovery scheme and the data recovery requirements based on the performance data of the group of microservice applications. sorting the data centers based on the data center average available bandwidth of the network; generating a first portion of a machine learning model for optimizing the relocation of the data based on the performance data of the group of microservice applications; The computer-implemented method comprising:

9. The system, Sorting the data centers based on the data center average available bandwidth of the network. The computer-implemented method of claim 8 , further comprising:

10. The system, eliminating potential secondary data centers from the network based on the performance data; The computer-implemented method of claim 9 , further comprising:

11. The system, generating a second portion of the machine learning model for optimizing the relocation of the data further based on the performance data of the at least one data center. The computer-implemented method of any one of claims 8 to 10, further comprising:

12. the modifying includes generating a modified data recovery scheme; The system comprises: analyzing the modified data recovery scheme to determine whether the modified data recovery scheme is predicted to achieve improved performance data compared to the original data recovery scheme and to meet the data recovery requirements. The computer-implemented method of claim 11 , further comprising:

13. The computer-implemented method of claim 8, wherein the relocation of the data is performed via a cloud computing environment.

14. A computer-implemented method, comprising: a system operatively coupled to a processor, comprising: modifying a data recovery scheme based on performance data and data recovery requirements associated with a network of data centers, the data centers comprising one or more primary data centers initially responsible for storing, processing and / or delivering a given data, and one or more secondary data centers to which the given data is to be relocated, the performance data being related to a group of microservice applications contained within the data and including at least one member selected from the group consisting of: a location of the data center, a bandwidth of the network, a latency of the network, a bandwidth used by the data, a latency exhibited during execution of the data, and a latency exhibited during the relocation of the data, the data recovery requirements including at least one second member selected from a second group consisting of: the location of the data center, and a service level objective, the data recovery scheme directing the relocation of data within the network of the data center and may describe the replication and / or transfer of data from the one or more primary data centers to the one or more secondary data centers; and generating a machine learning model for optimizing the relocation of the data based on the group of the microservice applications; 4. A computer-implemented method comprising:

15. The system, comprising: Sorting the microservice groups according to a ratio of average application latency to target application latency, where the sorting comprises sorting the microservice groups such that microservice groups that do not achieve one or more service level objective targets are followed by microservice groups that are at risk of not achieving one or more service level objective targets. The computer-implemented method of claim 14 further comprising:

16. The system, comprising: eliminating potential secondary data centers from the network of data centers based on the performance data; The computer-implemented method of claim 15 further comprising:

17. The system, comprising: generating, by the system, a second machine learning model for optimizing the relocation of the data further based on the at least one data center; The computer-implemented method of any one of claims 14 to 16, further comprising:

18. the modifying is based on the machine learning model and the second machine learning model to generate a modified data recovery scheme; The system comprises: analyzing the modified data recovery scheme to determine whether the modified data recovery scheme is predicted to achieve improved performance data compared to the original data recovery scheme and to meet the data recovery requirements.

20. The computer-implemented method of claim 17, further comprising:

19. The computer-implemented method of claim 14, wherein the relocation of the data is performed via a cloud computing environment.

20. A computer program for adaptively distributing data within a network of a data center, the computer program causing a system to execute a computer-implemented method according to any one of claims 8 to 13.

21. A computer program for adaptively distributing data in a network of data centers, the computer program causing a system to perform the computer-implemented method of any one of claims 14 to 19.

Citation Information

Patent Citations

  • Method for establishing data recovery exercise environment based on micro-service

    CN110109779A

  • Dynamic global level clustering method, device and system based on financial clients

    CN110134742A

  • Dynamic application placement based on cost and availability of energy in datacenters

    US20110282982A1

  • Method and Apparatus for Automated Migration of Data Among Storage Centers

    US20140173229A1

  • Method of data storage on cloud data center for reducing processing and storage requirements by engaging user equipment

    US20150331752A1