Fault processing method and related equipment

Abstract

The invention provides a fault processing method and related equipment. The method is applied to a cloud management platform, and comprises the following steps: obtaining a business resource pool creation request and a disaster recovery resource pool creation request of a tenant, and creating a business resource pool comprising M first physical servers and a disaster recovery resource pool comprising N second physical servers for the tenant; receiving a disaster recovery strategy configured by the tenant; and under the condition that at least one cloud instance in any number of first physical servers in the M first physical servers breaks down or is upgraded, running a backup of the at least one cloud instance which breaks down or is upgraded in the M first physical servers in the N second physical servers according to the disaster recovery strategy. According to the method, when the cloud instance in the service resource pool breaks down or is upgraded, the backup of the cloud instance can be operated in the disaster recovery resource pool according to the disaster recovery strategy configured by the tenant, so that the influence on the service of the tenant is reduced.

Description

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on August 14, 2023, with application number 202311020386.8, and priority to the Chinese patent application with the invention name “A Fault Handling Method and Related Equipment”, all contents of which are incorporated by reference in this application. Technical Field

[0002] The present application relates to the field of cloud computing, and more specifically, to a fault handling method, a fault handling apparatus, a computing device cluster, a computer program product, and a computer-readable storage medium. Background Art

[0003] With the maturity of technologies such as the fifth generation mobile communication technology (5G) and the Internet of Things (IoT), live broadcasting, online education, augmented reality (AR) / virtual reality (VR), and enterprise digital transformation, relying on cloud resources for business development has become the preferred choice for various industries. However, based on tenants' needs for data security or business independence, cloud vendors need to build independent and exclusive small resource pools for tenants. For example, building independent and exclusive resources or exclusive edge nodes in a public cloud. In order to provide tenants with highly reliable cloud service capabilities, cloud vendors usually recommend tenants to purchase a disaster recovery resource pool when tenants purchase an exclusive business resource pool. Both the business resource pool and the disaster recovery resource pool may include at least one physical server, each physical server is used to carry one or more cloud instances of the tenant, and each cloud instance is used to run the tenant's business. When a cloud instance running in a business resource pool fails or is upgraded, the cloud vendor will run the backup of the failed or upgraded cloud instance in the disaster recovery resource pool in the order of failure or upgrade to ensure the reliability of the business. The cloud instance may include a virtual machine (VM), a container, etc. The resource types included in the disaster recovery resource pool usually need to be consistent with the business resource pool, but the number of resources may be different. However, running the backup of the cloud instance according to the time sequence of cloud instance failure or upgrade is difficult to ensure that the tenant's important business is restored in time, and when the amount of resources included in the disaster recovery resource pool is small and there are many cloud instances that fail or are upgraded in the business resource pool, it is easy to cause the tenant's business to be interrupted and difficult to restore.

[0004] Therefore, how to handle failures when cloud instances in the business resource pool fail or are upgraded, thereby reducing the impact on tenants' businesses, becomes an urgent problem to be solved. Summary of the invention

[0005] The present application provides a fault handling method, a fault handling apparatus, a computing device cluster, a computer program product, and a computer-readable storage medium. When a cloud instance in a business resource pool fails or is upgraded, a backup of the failed or upgraded cloud instance can be run in the disaster recovery resource pool according to the disaster recovery strategy configured by the tenant, thereby reducing the impact on the tenant's business.

[0006] In a first aspect, a fault handling method is provided, wherein the method is applied to a cloud management platform, the cloud management platform is used to manage an infrastructure for providing a cloud instance, the infrastructure including at least one data center. The method comprises: obtaining a tenant's business resource pool creation request, creating a business resource pool for the tenant in an infrastructure according to the business resource pool creation request, wherein the business resource pool comprises M first physical servers, each of which is used to carry one or more cloud instances of the tenant, and M is a positive integer greater than 0; obtaining a tenant's disaster recovery resource pool creation request, creating a disaster recovery resource pool for the tenant in the infrastructure according to the disaster recovery resource pool creation request, wherein the disaster recovery resource pool comprises N second physical servers, and in the case that at least one cloud instance in any number of the M first physical servers fails or is upgraded, the N second physical servers are used to run a backup of at least one cloud instance in the M first physical servers that fails or is upgraded, and N is a positive integer greater than 0, and N is less than or equal to M; receiving a disaster recovery policy configured by the tenant, wherein the disaster recovery policy is used to indicate a disaster recovery priority of a cloud instance running on the business resource pool; in the case that at least one cloud instance in any number of the M first physical servers fails or is upgraded, running a backup of at least one cloud instance in the M first physical servers that fails or is upgraded in the N second physical servers according to the disaster recovery policy.

[0007] In an embodiment of the present application, when a cloud instance in a business resource pool fails or is upgraded, a backup of the failed or upgraded cloud instance can be run in the disaster recovery resource pool according to the disaster recovery strategy configured by the tenant, thereby reducing the impact on the tenant's business.

[0008] In combination with the first aspect, in certain implementations of the first aspect, the disaster recovery priority is determined based on at least one of the following: a business priority of the cloud instance, an amount of resources included in the cloud instance, or a type of resources included in the cloud instance.

[0009] In the embodiment of the present application, according to the disaster recovery strategy configured by the tenant, it can be ensured that the tenant's important business can be restored first. Alternatively, when the resources in the disaster recovery resource pool are insufficient, appropriate resources can be allocated to the backup of each cloud instance, so that as many backups of cloud instances as possible can be run in the disaster recovery resource pool. Alternatively, the resource configuration of the backup of the cloud instance in the disaster recovery resource pool can be made consistent with the resource configuration of the cloud instance in the business resource pool as much as possible, thereby reducing the impact on the tenant's business.

[0010] In combination with the first aspect, in certain implementations of the first aspect, the disaster recovery strategy includes a priority policy, which is used to indicate that the disaster recovery priority is determined according to the business priority of the cloud instance. According to the priority policy, backups of at least one cloud instance are run in N second physical servers in descending order of disaster recovery priority.

[0011] In an embodiment of the present application, the cloud management platform can run a backup of at least one cloud instance in a disaster recovery resource pool according to the business priority of the cloud instance, thereby ensuring that the cloud instance where the tenant's important business is located can be restored first.

[0012] In combination with the first aspect, in certain implementations of the first aspect, the disaster recovery strategy also includes a preemption strategy, which is used to indicate that the disaster recovery priority of the first cloud instance is higher than the disaster recovery priority of the second cloud instance, the business priority of the first cloud instance is higher than the business priority of the second cloud instance, the backup of the first cloud instance is not running in N second physical servers, the backup of the second cloud instance is running in N second physical servers, the first cloud instance and the second cloud instance are different cloud instances that fail or are upgraded in the M first physical servers, and according to the preemption strategy, the backup of the second cloud instance running in the N second physical servers is replaced by the backup of the first cloud instance.

[0013] In an embodiment of the present application, when the resources in the disaster recovery resource pool are insufficient, the cloud management platform can seize the backup resources of the cloud instance with a lower priority to run the backup of the cloud instance with a higher priority in the disaster recovery resource pool, thereby ensuring that the tenant's important business can be restored first.

[0014] In combination with the first aspect, in some implementations of the first aspect, the priority of the first cloud instance is higher than the preset priority, and the priority of the second cloud instance is lower than or equal to the preset priority.

[0015] In an embodiment of the present application, the cloud management platform or tenant can set that only cloud instances with a higher priority than a preset priority can occupy resources in the disaster recovery resource pool, thereby further ensuring that the backup of cloud instances with higher priority can run first.

[0016] In combination with the first aspect, in certain implementations of the first aspect, priority information configured by a tenant is received, where the priority information is used to indicate a service priority of a cloud instance running on a service resource pool.

[0017] In an embodiment of the present application, the cloud management platform can receive the business priority of each cloud instance configured by the tenant, and thereby determine the disaster recovery priority of the cloud instance that fails or is being upgraded based on the business priority of the cloud instance.

[0018] In combination with the first aspect, in certain implementations of the first aspect, the disaster recovery strategy also includes a downgrading strategy, which is used to indicate that the disaster recovery priority is determined according to the amount of resources included in the cloud instance, and the downgraded resource amount of each cloud instance is determined according to the amount of resources included in each cloud instance in at least one cloud instance that fails or is upgraded and the amount of resources included in N second physical servers, and the downgraded resource amount of each cloud instance is less than or equal to the amount of resources included in each cloud instance in the business resource pool; according to the downgrading strategy and the downgraded resource amount of each cloud instance, a backup of at least one cloud instance is run in the N second physical servers.

[0019] In an embodiment of the present application, when the resources in the disaster recovery resource pool are insufficient, the cloud management platform can allocate resources in the disaster recovery resource pool to the backups of more cloud instances as much as possible by reducing the amount of resources included in the backup of each cloud instance, thereby running as many backups of cloud instances as possible in the disaster recovery resource pool.

[0020] In combination with the first aspect, in certain implementations of the first aspect, downgrade information configured by the tenant is received, the downgrade information including a minimum downgrade ratio and / or minimum resource quantity information; the downgraded resource quantity of each cloud instance is determined based on the downgrade information, the resource quantity included in each cloud instance, and the resource quantity included in N second physical servers.

[0021] The minimum downgrade ratio is used to indicate the minimum ratio of the amount of resources included in the business resource pool of the cloud instance to the amount of downgraded resources. The minimum resource amount information is used to indicate the minimum amount of resources included in the cloud instance. The ratio of the amount of resources included in the business resource pool of each cloud instance to the amount of downgraded resources is greater than or equal to the minimum downgrade ratio of each cloud instance, and / or the amount of downgraded resources of each cloud instance is greater than or equal to the minimum amount of resources of each cloud instance.

[0022] In an embodiment of the present application, the tenant can configure the minimum downgrade ratio and / or minimum resource amount for each cloud instance, so as to run as many backups of cloud instances as possible in the disaster recovery resource pool while avoiding the situation where too few resources are allocated to the backup of the cloud instance, resulting in the inability to run the backup of the cloud instance.

[0023] In combination with the first aspect, in certain implementations of the first aspect, the disaster recovery strategy also includes a best matching strategy, which is used to indicate that the disaster recovery priority is determined according to the resource type included in the cloud instance, and the resources matching each cloud instance are determined according to the resource type included in each cloud instance in at least one cloud instance and the resource type included in N second physical servers; based on the best matching strategy and the resources matching each cloud instance, a backup of at least one cloud instance is run on the N second physical servers.

[0024] In an embodiment of the present application, the cloud management platform can allocate matching resources to the backup of each cloud instance in the disaster recovery resource pool, so that the resource type allocated to the backup of each cloud instance in the disaster recovery resource pool and the resource type allocated to each cloud instance in the business resource pool are consistent, thereby avoiding affecting the operation of the backup of the cloud instance, thereby reducing the impact on the tenant's business.

[0025] In combination with the first aspect, in certain implementations of the first aspect, resource priority information configured by the tenant is received, and the resource priority information is used to indicate the priority of each resource included in the cloud instance; based on the resource priority information, the resource types included in each cloud instance, and the resource types included in the N second physical servers, the resources matching each cloud instance are determined in descending order of the resource priorities.

[0026] In an embodiment of the present application, the tenant can configure the priority of each resource so that the cloud management platform can allocate matching resources for the backup of each cloud instance based on the priority of the resource, thereby further reducing the impact on the tenant's business.

[0027] In combination with the first aspect, in certain implementations of the first aspect, the disaster recovery strategy includes a sequential disaster recovery strategy, which is used to indicate that the disaster recovery priority is determined according to the time sequence in which cloud instances fail or are upgraded, and according to the sequential disaster recovery strategy and the time sequence in which at least one cloud instance fails or is upgraded, backups of one or more cloud instances are run in sequence in N second physical servers.

[0028] In an embodiment of the present application, the cloud management platform can determine the disaster recovery priority of each cloud instance according to the order in which each cloud instance fails or is upgraded, so as to run the backup of the cloud instance in a more timely manner, thereby reducing the impact on the tenant's business.

[0029] In combination with the first aspect, in certain implementations of the first aspect, the disaster recovery reliability of the disaster recovery resource pool is predicted based on the business resource pool creation request, the disaster recovery resource pool creation request and the disaster recovery strategy. The disaster recovery reliability is used to indicate that when at least one cloud instance in any number of the M first physical servers fails or is upgraded, the N second physical servers run a backup of at least one cloud instance that fails or is upgraded; and the disaster recovery reliability is provided to the tenants.

[0030] In an embodiment of the present application, the cloud management platform can predict the disaster recovery reliability of the disaster recovery resource pool based on the resources included in the disaster recovery resource pool created by the tenant's request and the disaster recovery strategy configured by the tenant, and provide it to the tenant, thereby assisting the tenant in creating a disaster recovery resource pool with suitable resources and a suitable disaster recovery strategy, thereby reducing the tenant's cost and providing higher reliability for the tenant's business.

[0031] In a second aspect, a fault handling device is provided, which includes a module for implementing the first aspect or any possible implementation manner of the first aspect.

[0032] In a third aspect, the present application provides a computing device cluster, comprising at least one computing device, each computing device comprising a processor and a memory; the processor of at least one computing device is used to execute instructions stored in the memory of at least one computing device, so that the computing device cluster executes the method of the above-mentioned first aspect or any one of the implementation methods of the first aspect.

[0033] In a fourth aspect, the present application provides a computer program product comprising instructions, which, when executed by a computer device cluster, causes the computer device cluster to execute the method of the first aspect or any one of the implementation modes of the first aspect.

[0034] In a fifth aspect, the present application provides a computer-readable storage medium, including computer program instructions. When the computer program instructions are executed by a computing device cluster, the computing device cluster executes the method of the above-mentioned first aspect or any one of the implementation modes of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 It is a schematic structural diagram of a fault handling system according to an embodiment of the present application.

[0036] Figure 2 It is a schematic structural diagram of a fault handling system according to another embodiment of the present application.

[0037] Figure 3 It is a schematic flowchart of a fault handling method according to an embodiment of the present application.

[0038] Figure 4It is a schematic diagram of a business resource pool and a disaster recovery resource pool according to an embodiment of the present application.

[0039] Figure 5 is a schematic diagram of a first graphical interface according to an embodiment of the present application.

[0040] Figure 6 It is a schematic flow chart of a method for determining a disaster recovery strategy and resources included in a disaster recovery resource pool according to an embodiment of the present application.

[0041] Figure 7 is a schematic diagram of a second graphical interface according to an embodiment of the present application.

[0042] Figure 8 It is a schematic flowchart of a fault handling method according to another embodiment of the present application.

[0043] Fig. 9 It is a schematic diagram of determining the disaster recovery priority of a cloud instance according to a priority strategy according to an embodiment of the present application.

[0044] Fig.10 is a schematic diagram of a third graphical interface according to an embodiment of the present application.

[0045] Fig.11 It is a schematic diagram of determining the disaster recovery priority of a cloud instance according to a preemption strategy according to an embodiment of the present application.

[0046] Fig.12 It is a schematic diagram of determining the disaster recovery priority of a cloud instance according to a downgrade strategy according to an embodiment of the present application.

[0047] Fig.13 It is a schematic structural diagram of a fault handling device according to an embodiment of the present application.

[0048] Fig.14 is a schematic structural diagram of a computing device according to an embodiment of the present application.

[0049] Fig.15 It is a schematic structural diagram of a computing device cluster according to an embodiment of the present application.

[0050] Fig.16 It is a schematic diagram of a connection between computing devices 1400A and 1400B via a network according to one embodiment of the present application. DETAILED DESCRIPTION

[0051] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0052] The embodiments of the present application will present various aspects, embodiments or features around a system including multiple devices, components, modules, etc. It should be understood and appreciated that each system may include additional devices, components, modules, etc., and / or may not include all devices, components, modules, etc. discussed in conjunction with the figures. In addition, combinations of these schemes may also be used.

[0053] In addition, in the embodiments of the present application, words such as "exemplary" and "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplary" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of the word "exemplary" is intended to present concepts in a concrete way.

[0054] The business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of technology and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0055] References to "one embodiment" or "some embodiments" etc. described in this specification mean that a particular feature, structure or characteristic described in conjunction with the embodiment is included in one or more embodiments of the present application. Thus, the phrases "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear at different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0056] In the embodiments of the present application, "at least one" refers to one or more, and "plurality" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can be represented by: including the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and subsequent associated objects are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can be represented by: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple.

[0057] The method in the embodiment of the present application can be applied to various cloud management platforms. The cloud management platform is used to manage the infrastructure that provides cloud instances, and the infrastructure includes at least one data center. Each data center includes at least one resource among computing resources, storage resources or network resources.

[0058] Figure 1 It is a schematic structural diagram of the fault handling system 100 provided in an embodiment of the present application. Figure 1 The fault handling system 100 in the embodiment includes a cloud management platform 110. The cloud management platform 110 can be used to manage the infrastructure for providing cloud instances, and the infrastructure includes at least one data center (e.g., data center 140). The data center 140 may include at least one resource among computing resources, storage resources, and network resources. A tenant may apply to use resources in the data center 140 through the cloud management platform 110. The tenant is a tenant of a public cloud who has registered a public cloud account and purchased public cloud resources.

[0059] The cloud management platform 110 can obtain a tenant's business resource pool creation request, and create a business resource pool 120 for the tenant in the infrastructure according to the business resource pool creation request. The business resource pool 120 includes M first physical servers (e.g., first physical server 121 and / or first physical server 122), each of which is used to host one or more cloud instances of the tenant, and M is a positive integer greater than 0. Each cloud instance is used to run at least one business of the tenant. The cloud instance can be, for example, a virtual machine, a container, etc. Each first physical server can provide computing resources and / or storage resources for the tenant.

[0060] When the service resource pool 120 includes multiple first physical servers, at least two of the multiple first physical servers may be the same or different. The two first physical servers are different in that at least one of the types of processors included in the two first physical servers, the number of cores included in the processors, the computing power provided by the processors, the types of storage spaces, and the sizes of storage spaces is different.

[0061] The cloud management platform 110 may obtain a tenant's disaster recovery resource pool creation request, and create a disaster recovery resource pool 130 for the tenant in the infrastructure according to the disaster recovery resource pool creation request. The disaster recovery resource pool 130 includes N second physical servers (e.g., second physical server 131 and / or second physical server 132). In the event that at least one cloud instance in any number of the first physical servers among the M first physical servers fails or is upgraded, the N second physical servers are used to run a backup of at least one cloud instance in the M first physical servers that fails or is upgraded, where N is a positive integer greater than 0 and less than or equal to M.

[0062] In some embodiments, the cloud instance failure or upgrade may be that the cloud instance itself fails or is upgraded. Alternatively, the cloud instance failure or upgrade may be that the first physical server where the cloud instance is located fails or is upgraded.

[0063] For example, when the first physical server 121 in the business resource pool 120 fails, at least one cloud instance running in the first physical server 121 cannot operate normally (i.e., fails), and the cloud management platform 110 can run a backup of the at least one cloud instance in the second physical server 131, so that the business in the at least one cloud instance can be restored, thereby reducing the impact on the tenant's business.

[0064] In some embodiments, the second physical server included in the disaster recovery resource pool 130 may be the same as or different from the first physical server included in the business resource pool 120. For example, the second physical server 131 may be the same as or different from the first physical server 121 in at least one of the type of processor included, the number of cores included in the processor, the computing power provided by the processor, the type of storage space, and the size of the storage space.

[0065] When the cloud instance in the business resource pool 120 has not failed or been upgraded, the N second physical servers in the disaster recovery resource pool 130 may not be running, so the tenant is generally configured as follows: the amount of resources included in the disaster recovery resource pool 130 is less than the amount of resources included in the business resource pool 120. However, after the cloud instance in the business resource pool 120 fails or is upgraded, if the amount of resources included in the disaster recovery resource pool 130 is less than the amount of resources included in the cloud instance that failed or was upgraded in the business resource pool 120, the backup of some cloud instances of the tenant cannot be run in the disaster recovery resource pool 130, which is likely to cause a significant impact on the tenant's business. Therefore, the cloud management platform 110 can provide at least one disaster recovery strategy to the tenant, so that according to the disaster recovery strategy configured by the tenant, the backup of at least one cloud instance is run in the N second physical servers, thereby ensuring that the tenant's important business is restored first, or restoring as many cloud instances as possible, or making the resources allocated to the cloud instance before and after the migration as consistent as possible, thereby reducing the impact on the tenant's business.

[0066] The cloud management platform 110 may receive a disaster recovery policy configured by a tenant, and the disaster recovery policy is used to indicate the disaster recovery priority of the cloud instances running on the business resource pool 120. In the event that at least one cloud instance in any number of the first physical servers among the M first physical servers fails or is being upgraded, a backup of at least one cloud instance in the M first physical servers that fails or is being upgraded is run in the N second physical servers according to the disaster recovery policy.

[0067] Optionally, the disaster recovery priority may be determined according to at least one of the following: a service priority of the cloud instance, an amount of resources included in the cloud instance, or a type of resources included in the cloud instance.

[0068] Optionally, the disaster recovery strategy may include at least one of the following: a priority strategy, a preemption strategy, a downgrade strategy, a best match strategy, and a sequential disaster recovery strategy.

[0069] Optionally, the cloud management platform 110 can also predict the disaster recovery reliability of the disaster recovery resource pool according to the business resource pool creation request, the disaster recovery resource pool creation request, and the disaster recovery strategy. The disaster recovery reliability is used to indicate the ability of the N second physical servers to run the backup of at least one cloud instance that fails or is upgraded when at least one cloud instance in any number of the first physical servers among the M first physical servers fails or is upgraded. The cloud management platform 110 can also provide the disaster recovery reliability to the tenant, thereby providing guidance for the tenant to configure the resources included in the disaster recovery resource pool and the disaster recovery strategy.

[0070] Figure 2 It is another schematic structural diagram of the fault handling system provided in an embodiment of the present application. Figure 2 The fault handling system 200 in the embodiment includes a cloud management platform 210. The cloud management platform 210 can manage the infrastructure for providing cloud instances, and the infrastructure includes at least one data center (e.g., data center 240). The cloud management platform 210 can also create a business resource pool 220 and a disaster recovery resource pool 230 for the tenant according to the tenant's request. Figure 1 Similar to the business resource pool 120 in FIG. 1 , the disaster recovery resource pool 230 is similar to the business resource pool 120 in FIG. Figure 1 The cloud management platform 210 may include a disaster recovery strategy configuration component 211, a disaster recovery pool selection component 212, a disaster recovery resource monitoring component 213, a disaster recovery scheduling component 214, and a disaster recovery execution component 215.

[0071] The disaster recovery strategy configuration component 211 can provide at least one disaster recovery strategy for the tenant, and can also receive a disaster recovery strategy configured by the tenant. The disaster recovery strategy is used to indicate the disaster recovery priority of the cloud instance running on the business resource pool 220.

[0072] In some embodiments, the disaster recovery priority is determined based on at least one of the following: a business priority of the cloud instance, an amount of resources included in the cloud instance, or a type of resources included in the cloud instance.

[0073] In some embodiments, the disaster recovery strategy configuration component 211 may also receive priority information configured by a tenant, where the priority information is used to indicate the service priority of the cloud instance running on the service resource pool 220 .

[0074] In some embodiments, the disaster recovery strategy configuration component 211 may also receive downgrade information configured by the tenant, the downgrade information including the minimum downgrade ratio and / or the minimum resource quantity information. The minimum downgrade ratio is used to indicate the minimum ratio between the amount of resources included in the cloud instance in the business resource pool 220 and the amount of downgraded resources. The minimum resource quantity information is used to indicate the minimum amount of resources included in the cloud instance.

[0075] In some embodiments, the disaster recovery strategy configuration component 211 may also receive resource priority information configured by the tenant, where the resource priority information is used to indicate the priority of each resource included in the cloud instance.

[0076] The disaster recovery pool selection component 212 can obtain the tenant's business resource pool creation request and disaster recovery resource pool creation request. The business resource pool creation request is used to request the creation of a business resource pool 220, and the disaster recovery resource pool creation request is used to request the creation of a disaster recovery resource pool 230.

[0077] In some embodiments, the disaster recovery pool selection component 212 can also predict the disaster recovery reliability of the disaster recovery resource pool according to the business resource pool creation request, the disaster recovery resource pool creation request and the disaster recovery strategy configured by the tenant. The disaster recovery reliability is used to indicate the ability of the N second physical servers to run the backup of at least one cloud instance that fails or is upgraded when at least one cloud instance in any number of the first physical servers in the M first physical servers fails or is upgraded. The disaster recovery pool selection component 212 can also provide the disaster recovery reliability to the tenant, thereby assisting the tenant to create a disaster recovery resource pool 230 with appropriate resources and configure an appropriate disaster recovery strategy.

[0078] The disaster recovery resource monitoring component 213 can monitor the operation of the first physical server in the business resource pool 220, and can also monitor the usage of resources in the business resource pool 220 and / or the disaster recovery resource pool 230. The usage of the resource may include the usage capacity and / or the remaining capacity of the resource. The disaster recovery resource monitoring component 213 can also notify the disaster recovery scheduling component 214 when it is detected that at least one cloud instance in the business resource pool 220 fails or is upgraded.

[0079] When the disaster recovery resource monitoring component 213 detects that at least one cloud instance in the business resource pool 220 fails or is being upgraded, the disaster recovery scheduling component 214 can determine the disaster recovery priority of each cloud instance in the at least one cloud instance that fails or is being upgraded in the business resource pool 220 according to the disaster recovery strategy configured by the tenant. The disaster recovery scheduling component 214 can also send the disaster recovery priority of the at least one cloud instance to the disaster recovery execution component 215.

[0080] In some embodiments, the at least one disaster recovery strategy may include any one or more of a priority strategy, a preemption strategy, a downgrade strategy, a best match strategy, and a sequential disaster recovery strategy.

[0081] The disaster recovery execution component 215 may run the backup of one or more cloud instances in the at least one cloud instance in the N second physical servers in the disaster recovery resource pool 230 according to the disaster recovery priority of the at least one cloud instance.

[0082] Optionally, the cloud management platform 210 may further include a disaster recovery component 216. After at least one cloud instance that has failed or is undergoing an upgrade recovers to normal or completes the upgrade, the disaster recovery component 216 may continue to run the at least one cloud instance in the M first physical servers in the business resource pool 220, and interrupt the backup operation of at least one cloud instance in the N second physical servers.

[0083] Figure 1 , Figure 2 The fault handling system in the service resource pool can run the backup of the failed or upgraded cloud instance in the disaster recovery resource pool according to the disaster recovery strategy configured by the tenant when at least one cloud instance in the service resource pool fails or is upgraded, thereby reducing the impact on the tenant's business. The fault handling system can ensure that the tenant's important business can be restored first according to the disaster recovery strategy configured by the tenant, or when the resources in the disaster recovery resource pool are insufficient, appropriate resources can be allocated to the backup of each cloud instance, so as to run as many backups of cloud instances as possible in the disaster recovery resource pool, or the resource configuration of the backup of the cloud instance in the disaster recovery resource pool can be made as consistent as possible with the resource configuration of the cloud instance in the service resource pool, thereby reducing the impact on the tenant's business.

[0084] Figure 3 It is a schematic flowchart of the fault handling method provided in the embodiment of the present application. Figure 3 The method in can be Figure 1 or Figure 2 The cloud management platform is executed in. Figure 3 The method comprises the following steps.

[0085] S310, obtaining a service resource pool creation request of a tenant, and creating a service resource pool for the tenant in the infrastructure according to the service resource pool creation request.

[0086] The cloud management platform may obtain a tenant's business resource pool creation request, where the business resource pool creation request is used to request the creation of a business resource pool. The cloud management platform may also create a business resource pool for the tenant in an infrastructure managed by the cloud management platform based on the business resource pool request. The infrastructure may include at least one data center.

[0087] Optionally, the service resource pool creation request may include the quantity and / or type of resources included in the service resource pool requested to be created by the tenant. The type of the resource includes at least one of the following: computing resources, storage resources, and network resources.

[0088] Optionally, the tenant may determine the quantity and / or type of resources required in the service resource pool according to the operating requirements of the tenant's service and the costs required for various resources.

[0089] Optionally, the cloud management platform may provide a graphical interface for the tenant, so that the tenant may select or upload the business resource pool creation request on the graphical interface. The embodiment of the present application does not limit the specific form of the graphical interface.

[0090] Optionally, the cloud management platform may create a business resource pool including M first physical servers for the tenant, where M is a positive integer greater than 0. Each of the M first physical servers is used to host one or more cloud instances of the tenant. The cloud instance may be a virtual machine or a container, etc. Each cloud instance may be used to run at least one business of the tenant.

[0091] S320, obtaining a disaster recovery resource pool creation request of the tenant, and creating a disaster recovery resource pool for the tenant in the infrastructure according to the disaster recovery resource pool creation request.

[0092] The cloud management platform can obtain the tenant's disaster recovery resource pool creation request, which is used to request the creation of a disaster recovery resource pool. The cloud management platform can also create a disaster recovery resource pool for the tenant in the infrastructure managed by the cloud management platform according to the disaster recovery resource pool request.

[0093] Optionally, the disaster recovery resource pool creation request may include the quantity and / or type of resources included in the disaster recovery resource pool requested to be created by the tenant. The type of the resource includes at least one of the following: computing resources, storage resources, and network resources.

[0094] Optionally, the tenant may determine the quantity and / or type of resources required in the disaster recovery resource pool according to the operating requirements of the tenant's business and the costs required for various resources.

[0095] Optionally, the cloud management platform may provide a graphical interface for the tenant, so that the tenant can select or upload the disaster recovery resource pool creation request on the graphical interface. The embodiment of the present application does not limit the specific form of the graphical interface.

[0096] Optionally, the cloud management platform may create a disaster recovery resource pool including N second physical servers for the tenant, where N is a positive integer greater than 0. In the event that at least one cloud instance in any number of the first physical servers among the M first physical servers fails or is being upgraded, the N second physical servers are used to run a backup of at least one cloud instance in the M first physical servers that fails or is being upgraded.

[0097] For example, the resources included in the disaster recovery resource pool created by the tenant can be as follows: Figure 4 shown. Figure 4 Schematic diagram of a service resource pool and a disaster recovery resource pool created by a tenant request provided in an embodiment of the present application. Figure 4 As shown, a tenant can create a business resource pool 410 including four physical servers according to business demand requests, and the four physical servers are two type A physical servers, a type B physical server, and a type C physical server. Among them, the computing resources and storage resources included in the two type A physical servers are the same. The computing resources and / or storage resources included in the type A physical server, the type B physical server, and the type C physical server are different. The same resources refer to the type and quantity of resources are the same. Different resources refer to the type and / or quantity of resources are different. Each physical server in the business resource pool 410 can carry at least one cloud instance, and each cloud instance is used to run at least one business of the tenant.

[0098] like Figure 4As shown, based on the resources included in the business resource pool 410, the disaster recovery resource pool created by the tenant request can be any one of the disaster recovery resource pool 420, the disaster recovery resource pool 430 or the disaster recovery resource pool 440. Among them, the disaster recovery resource pool 420 includes two type A physical servers, a type B physical server and a type C physical server, that is, the resources included in the disaster recovery resource pool 420 are the same as the resources included in the business resource pool 410. Even if all cloud instances running in the business resource pool 410 fail or are upgraded, the disaster recovery resource pool 420 can also run the backup of all cloud instances. However, the cost required for the disaster recovery resource pool 420 is high, and when the cloud instances running in the business resource pool 410 do not fail or are not upgraded, or when there are few cloud instances that fail or are upgraded, there is a problem of resource waste. The disaster recovery resource pool 430 includes type A physical servers and type B physical servers, and the disaster recovery resource pool 440 only includes type A physical servers. That is, the amount of resources included in the disaster recovery resource pool 430 and the disaster recovery resource pool 440 is less than the amount of resources included in the business resource pool 410. The cost required by the disaster recovery resource pool 430 or the disaster recovery resource pool 440 is relatively low, but when there are many cloud instances that fail or are being upgraded in the business resource pool 410, it may not be possible to run the backup of all the cloud instances that fail or are being upgraded in the disaster recovery resource pool, or it may be necessary to reduce the amount of resources included in some cloud instances to ensure that the business is not interrupted.

[0099] S330: Receive the disaster recovery strategy configured by the tenant.

[0100] The cloud management platform can receive the disaster recovery policy configured by the tenant, which is used to indicate the disaster recovery priority of the cloud instances running on the business resource pool.

[0101] In some embodiments, the disaster recovery priority is determined based on at least one of the following: a business priority of the cloud instance, an amount of resources included in the cloud instance, or a type of resources included in the cloud instance.

[0102] In some embodiments, the disaster recovery strategy may include at least one of the following: a priority strategy, a preemption strategy, a downgrade strategy, a best match strategy, and a sequential disaster recovery strategy.

[0103] Optionally, the cloud management platform may provide a first graphical interface to the tenant, so that the tenant may select or upload the disaster recovery strategy configuration information on the first graphical interface.

[0104] For example, the cloud management platform may provide a first graphical interface such as Figure 5 shown. Figure 5 is a schematic diagram of a first graphical interface provided in an embodiment of the present application. Figure 5As shown in the first graphical interface 500 in FIG. 1 , the tenant can select the following five disaster recovery strategies in the first graphical interface 500: priority strategy, forced occupation strategy, downgrade strategy, best match strategy, and sequential disaster recovery strategy. The tenant can select at least one disaster recovery strategy from the five disaster recovery strategies by checking the selection boxes corresponding to the five disaster recovery strategies.

[0105] Exemplarily, the first graphical interface 500 may also include an explanation of the meaning of each disaster recovery strategy so that the tenant can understand the meaning of each disaster recovery strategy.

[0106] It should be understood that the first graphical interface is only an exemplary description. The cloud management platform can provide tenants with other forms of graphical interfaces so that tenants can select or upload disaster recovery strategy configuration information in the graphical interface.

[0107] When a tenant needs to ensure that important services are restored first, the tenant can select a priority policy and / or a preemption policy. The priority policy is used to indicate that the disaster recovery priority of a cloud instance is determined according to the service priority of the cloud instance. When the service priority of a cloud instance is higher, the disaster recovery priority of the cloud instance is higher. When the service priority of a cloud instance is lower, the disaster recovery priority of the cloud instance is lower. The cloud management platform can run the backup of at least one cloud instance that fails or is being upgraded in the disaster recovery resource pool in descending order of disaster recovery priority according to the priority policy.

[0108] The preemption policy is used to indicate that the disaster recovery priority of the first cloud instance is higher than that of the second cloud instance, and the business priority of the first cloud instance is higher than that of the second cloud instance. The backup of the first cloud instance is not running in the N second physical servers, and the backup of the second cloud instance is running in the N second physical servers. The first cloud instance and the second cloud instance are different cloud instances that have failed or are being upgraded in the M first physical servers. According to the preemption policy, the cloud management platform replaces the backup of the second cloud instance running in the disaster recovery resource pool with the backup of the first cloud instance.

[0109] In some embodiments, the priority of the first cloud instance may be higher than a preset priority, and the priority of the second cloud instance may be lower than or equal to the preset priority. That is, a cloud instance with a higher priority may occupy the resources of a cloud instance with a lower priority than or equal to the preset priority, so that the backup of the cloud instance with a higher priority may be preferentially run in the disaster recovery resource pool. The preset priority may be determined by the cloud management platform itself, or may be configured by the tenant.

[0110] When the tenant needs to ensure that as many services as possible are restored, the tenant can choose a downgrade strategy. The downgrade strategy is used to indicate that the disaster recovery priority of the cloud instance is determined according to the amount of resources included in the cloud instance. For example, the cloud management platform can determine the downgraded resource amount of each cloud instance based on the amount of resources included in each cloud instance that fails or is upgraded and the amount of resources included in the disaster recovery resource pool, so as to run the backup of at least one cloud instance in the disaster recovery resource pool according to the downgrade strategy and the downgraded resource amount of each cloud instance. The downgraded resource amount of each cloud instance is less than or equal to the amount of resources included in the business resource pool of each cloud instance. That is, the cloud management platform can reduce the amount of resources included in the backup of each cloud instance so that the backup of each cloud instance can run in the disaster recovery resource pool.

[0111] In some embodiments, the cloud management platform may determine the amount of downgraded resources for each cloud instance based on the downgrade information, the amount of resources included in each cloud instance, and the amount of resources included in the disaster recovery resource pool. The downgrade information includes a minimum downgrade ratio and / or minimum resource quantity information. The minimum downgrade ratio is used to indicate the minimum ratio between the amount of resources included in the business resource pool and the amount of downgraded resources of the cloud instance. The minimum resource quantity information is used to indicate the minimum amount of resources included in the cloud instance. The ratio of the amount of resources included in the business resource pool of each cloud instance to the amount of downgraded resources is greater than or equal to the minimum downgrade ratio of the cloud instance, and / or the amount of downgraded resources of each cloud instance is greater than or equal to the minimum amount of resources of each cloud instance. The downgrade information may be determined by the cloud management platform itself, or may be configured by a tenant.

[0112] When a tenant needs to ensure that the resource configuration of the cloud instance where the business is located is as consistent as possible, the tenant can select the best matching strategy. The best matching strategy is used to indicate that the disaster recovery priority of the cloud instance is determined according to the resource type included in the cloud instance. For example, the cloud management platform can determine the resources in the disaster recovery resource pool that match each cloud instance based on the resource types included in each cloud instance and the resource types included in the disaster recovery resource pool, so as to run the backup of at least one cloud instance in the disaster recovery resource pool according to the best matching strategy and the resources matched by each cloud instance. That is, the cloud management platform can match the resource types included in each cloud instance so that the resource configuration of the backup of the cloud instance in the disaster recovery resource pool is consistent with the resource configuration of the cloud instance in the business resource pool, thereby minimizing the impact on the business running in the backup of the cloud instance.

[0113] In some embodiments, the cloud management platform can determine the resource type that is matched first according to the priority of the resource, thereby determining the resource that matches each cloud instance according to the resource type included in each cloud instance and the resource type included in the disaster recovery resource pool. The priority of the resource can be determined by the cloud management platform itself, or can be configured by the tenant.

[0114] When tenants need to restore services that have failed or are undergoing upgrades as soon as possible, they can select a sequential disaster recovery strategy. This sequential disaster recovery strategy is used to indicate that the disaster recovery priority of cloud instances is determined according to the time sequence in which cloud instances fail or are upgraded. For example, the cloud management platform can determine that the backup of a cloud instance that fails or is upgraded first runs in the disaster recovery resource pool first, and the backup of a cloud instance that fails or is upgraded later runs in the disaster recovery resource pool later.

[0115] Optionally, the cloud management platform can also predict the disaster recovery reliability of the disaster recovery resource pool based on the business resource pool creation request, the disaster recovery resource pool creation request and the disaster recovery strategy configured by the tenant. The disaster recovery reliability is used to indicate the ability of the N second physical servers to run the backup of at least one cloud instance that fails or is upgraded when at least one cloud instance in any number of the first physical servers among the M first physical servers fails or is upgraded. The cloud management platform can also provide the disaster recovery reliability to the tenant, thereby assisting the tenant in creating a disaster recovery resource pool with appropriate resources and configuring an appropriate disaster recovery strategy.

[0116] S340, when at least one cloud instance in any number of the M first physical servers fails or is being upgraded, a backup of at least one cloud instance that fails or is being upgraded in the M first physical servers is run in the N second physical servers according to the disaster recovery strategy.

[0117] The cloud management platform can monitor at least one cloud instance in the business resource pool in real time. When it is detected that one or more cloud instances have failed or are being upgraded, the cloud management platform can run a backup of the at least one cloud instance that has failed or is being upgraded in N second physical servers in the disaster recovery resource pool according to the disaster recovery strategy configured by the tenant.

[0118] Optionally, the cloud management platform may determine the disaster recovery priority of each cloud instance in the at least one cloud instance that fails or is being upgraded according to the disaster recovery strategy. The cloud management platform may also run the backup of the at least one cloud instance in the N second physical servers in sequence according to the disaster recovery priority of each cloud instance.

[0119] In some embodiments, the cloud management platform may allocate resources in the N second physical servers to the backup of each cloud instance according to the disaster recovery strategy, so as to run the backup of each cloud instance in the resources allocated to the backup of the cloud instance.

[0120] Optionally, the cloud management platform can also run the restored or upgraded cloud instance in the business resource pool when the cloud instance that failed or was being upgraded in the business resource pool returns to normal or completes the upgrade. When the backup of the cloud instance is running in the disaster recovery resource pool, the backup of the cloud instance is interrupted.

[0121] In some embodiments, the resource configuration of the cloud instance that fails or is being upgraded in the business resource pool and the resource configuration of the backup of the cloud instance in the disaster recovery resource pool may be different, but after the cloud instance is restored to normal or the upgrade is completed, the resource configuration of the cloud instance in the business resource pool is the same as the resource configuration before the failure or upgrade. The resource configuration includes the type and quantity of resources.

[0122] In an embodiment of the present application, when at least one cloud instance in a business resource pool fails or is upgraded, a backup of the failed or upgraded cloud instance can be run in the disaster recovery resource pool according to the disaster recovery strategy configured by the tenant, thereby reducing the impact on the tenant's business. The method in an embodiment of the present application can ensure that the tenant's important business can be restored first according to the disaster recovery strategy configured by the tenant, or when the resources in the disaster recovery resource pool are insufficient, appropriate resources can be allocated to the backup of each cloud instance, so as to run as many backups of cloud instances as possible in the disaster recovery resource pool, or the resource configuration of the backup of the cloud instance in the disaster recovery resource pool can be made as consistent as possible with the resource configuration of the cloud instance in the business resource pool, thereby reducing the impact on the tenant's business.

[0123] Figure 6 It is a schematic flowchart of a method for determining a disaster recovery strategy and resources included in a disaster recovery resource pool provided in an embodiment of the present application. Figure 6 The method in can be Figure 1 or Figure 2 The cloud management platform is executed in. Figure 6 The method comprises the following steps.

[0124] S610 , predicting the disaster recovery reliability of the disaster recovery resource pool according to the business resource pool creation request, the disaster recovery resource pool creation request and the disaster recovery strategy.

[0125] The disaster recovery reliability of the disaster recovery resource pool is used to indicate the ability of the backup of at least one cloud instance that fails or is being upgraded in the disaster recovery resource pool when at least one cloud instance in any number of first physical servers in the business resource pool fails or is being upgraded. The business resource pool includes M first physical servers, each of which is used to host at least one cloud instance of a tenant, and each cloud instance is used to run at least one business of the tenant. The disaster recovery resource pool includes N second physical servers.

[0126] Optionally, the cloud management platform may express the disaster recovery reliability through a service level agreement (SLA).

[0127] Optionally, the cloud management platform can input the resources included in the business resource pool and the disaster recovery resource pool requested by the tenant, as well as the disaster recovery strategy configured by the tenant, into the reliability prediction model, thereby predicting the disaster recovery reliability of the disaster recovery resource pool. The reliability prediction model can be used to predict the time required for the backup of the at least one cloud instance running in the business resource pool to run in the disaster recovery resource pool when the at least one cloud instance running in the business resource pool fails or is upgraded.

[0128] The smaller the difference between the amount of resources included in the disaster recovery resource pool and the amount of resources included in the business resource pool, the stronger the disaster recovery reliability of the disaster recovery resource pool. The larger the difference between the amount of resources included in the disaster recovery resource pool and the amount of resources included in the business resource pool, the weaker the disaster recovery reliability of the disaster recovery resource pool. The closer the types of resources included in the disaster recovery resource pool and the types of resources included in the business resource pool, the stronger the disaster recovery reliability of the disaster recovery resource pool. The less similar the types of resources included in the disaster recovery resource pool and the types of resources included in the business resource pool, the weaker the disaster recovery reliability of the disaster recovery resource pool. When running the backup of the cloud instance in the disaster recovery resource pool according to the disaster recovery policy, the more backups of the cloud instance can be run, the stronger the disaster recovery reliability of the disaster recovery resource pool. When running the backup of the cloud instance in the disaster recovery resource pool according to the disaster recovery policy, the fewer backups of the cloud instance can be run, the weaker the disaster recovery reliability of the disaster recovery resource pool.

[0129] Optionally, the cloud management platform may provide a second graphical interface to the tenant, so that the tenant may select or upload at least one of the following on the second graphical interface: a business resource pool creation request, a disaster recovery resource pool creation request, or a disaster recovery strategy.

[0130] For example, the cloud management platform can provide a second graphical interface such as Figure 7 shown. Figure 7 is a schematic diagram of a second graphical interface 700 provided in an embodiment of the present application. Figure 7 As shown in the second graphical interface 700 in the figure, the tenant can select or upload a business resource pool creation request in the second graphical interface 700. The business resource pool creation request is used to request the creation of a business resource pool. For example, the tenant can select or enter the type of resources included in the business resource pool requested to be created or the type of equipment that carries the resources in the selection box or input box corresponding to "Type" in "Business Resource Pool Resource Configuration". The tenant can also select or enter the quantity of each resource or the quantity of each equipment included in the business resource pool requested to be created in the selection box or input box corresponding to "Purchase Quantity" in "Business Resource Pool Resource Configuration".

[0131] like Figure 7As shown in the second graphical interface 700 in the figure, the tenant can also select or upload a disaster recovery resource pool creation request in the second graphical interface 700. The disaster recovery resource pool creation request is used to request the creation of a disaster recovery resource pool. For example, the tenant can select or enter the type of resources included in the disaster recovery resource pool requested to be created or the type of equipment that carries the resources in the selection box or input box corresponding to "Type" in "Disaster Recovery Resource Pool Resource Configuration". The tenant can also select or enter the quantity of each resource or the quantity of each equipment included in the disaster recovery resource pool requested to be created in the selection box or input box corresponding to "Purchase Quantity" in "Disaster Recovery Resource Pool Resource Configuration".

[0132] It should be understood that the second graphical interface is only an exemplary description. The cloud management platform can provide tenants with other forms of graphical interfaces, so that tenants can select or upload at least one of the following in the graphical interface: business resource pool creation request, disaster recovery resource pool creation request or disaster recovery strategy.

[0133] Exemplarily, the type and quantity of resources included in the device carrying the resources may also be displayed in the second graphical interface 700. The unit price of each resource or each device may also be displayed in the second graphical interface 700.

[0134] Exemplarily, the tenant may also select or upload a disaster recovery strategy in the second graphical interface 700. The operations of the tenant selecting or uploading a disaster recovery strategy in the second graphical interface 700 and the first graphical interface 500 are similar and will not be described in detail herein.

[0135] S620, providing disaster recovery reliability to the tenant, and assisting the tenant in determining a disaster recovery strategy and resources included in a disaster recovery resource pool.

[0136] The cloud management platform can predict the disaster recovery reliability of the disaster recovery resource pool and provide the disaster recovery reliability to the tenant in real time. For example, the cloud management platform can display in real time in the second graphical interface 700 that the disaster recovery reliability of the disaster recovery resource pool is 99.9%. The tenant can adjust the resource configuration and / or disaster recovery strategy of the disaster recovery resource pool according to the disaster recovery reliability provided by the cloud management platform, so as to determine a disaster recovery resource pool including suitable resources and / or a suitable disaster recovery strategy.

[0137] In an embodiment of the present application, the disaster recovery reliability of the disaster recovery resource pool can be predicted through the tenant's business resource pool creation request, disaster recovery resource pool creation request and disaster recovery strategy, thereby assisting the tenant to more reasonably select the resources and / or disaster recovery strategy included in the disaster recovery resource pool required by the tenant.

[0138] Figure 8 It is a schematic flowchart of the fault handling method provided in the embodiment of the present application. Figure 8 The method in can be Figure 1 or Figure 2 The cloud management platform is executed in. Figure 8 The following steps are included.

[0139] S810, determine the disaster recovery priority of at least one cloud instance according to at least one of a priority strategy, a preemption strategy, a downgrade strategy, a best match strategy, and a sequential disaster recovery strategy.

[0140] Optionally, the cloud management platform may determine the disaster recovery priority of at least one cloud instance according to a priority policy. The priority policy is used to indicate that the disaster recovery priority of a cloud instance is determined according to the business priority of the cloud instance. For example, the cloud management platform may determine that when the business priority of a cloud instance is higher, the disaster recovery priority of the cloud instance is higher. When the business priority of the cloud instance is lower, the disaster recovery priority of the cloud instance is lower, such as Fig. 9 shown.

[0141] Fig. 9 It is a schematic diagram of determining the disaster recovery priority of a cloud instance according to a priority strategy provided in an embodiment of the present application. Fig. 9 The business resource pool 910 in the example includes a first physical server 911 and a first physical server 912. The first physical server 911 can carry three cloud instances, namely, cloud instance 1, cloud instance 2, and cloud instance 3. The first physical server 912 can run three cloud instances, namely, cloud instance 4, cloud instance 5, and cloud instance 6. The business priorities of cloud instance 1, cloud instance 2, and cloud instance 4 are high, and the business priorities of cloud instance 3, cloud instance 5, and cloud instance 6 are low. When cloud instance 1 to cloud instance 6 all fail, the cloud management platform can determine, based on the priority policy, that the disaster recovery priority of cloud instance 1, cloud instance 2, and cloud instance 4 is higher than that of cloud instance 3, cloud instance 5, and cloud instance 6.

[0142] Assumptions Fig. 9In the case where the disaster recovery resource pool 920 includes only one second physical server 921, and the resources in the second physical server 921 can only carry three cloud instances, the cloud management platform can run the backups of cloud instance 1, cloud instance 2, and cloud instance 4 in the second physical server 921. The amount of resources included in the backup of cloud instance 1 in the second physical server 921 is the same as the amount of resources included in the first physical server 911, and / or the type of resources included in the backup of cloud instance 1 in the second physical server 921 is the same as the type of resources included in the first physical server 911. Similarly, the amount of resources included in the backup of cloud instance 2 in the second physical server 921 is the same as the amount of resources included in the first physical server 911, and / or the type of resources included in the backup of cloud instance 2 in the second physical server 921 is the same as the type of resources included in the first physical server 911. The amount of resources included in the backup of the cloud instance 4 in the second physical server 921 is the same as the amount of resources included in the cloud instance 4 in the first physical server 912, and / or the type of resources included in the backup of the cloud instance 4 in the second physical server 921 is the same as the type of resources included in the cloud instance 4 in the first physical server 912.

[0143] Optionally, the cloud management platform may receive priority information configured by the tenant. The priority information is used to indicate the service priority of the cloud instance running on the service resource pool. Alternatively, the priority information may be used to indicate the priority of each service in one or more services of the tenant, and the priority of each cloud instance may be determined according to the priority of at least one service running in each cloud instance.

[0144] In some embodiments, the cloud management platform may provide a third graphical interface to the tenant, so that the tenant may select or upload the priority information on the third graphical interface.

[0145] For example, the cloud management platform may provide a third graphical interface such as Fig.10 shown. Fig.10 It is a schematic diagram of the third graphical interface provided in an embodiment of the present application. Fig.10 The third graphic interface 1010 and the third graphic interface 1020 are included.

[0146] like Fig.10As shown in the third graphical interface 1010 in FIG. 1010 , the tenant can select and input the two items of "cloud instance identification" and "priority" in the third graphical interface 1010 to determine the service priority of each cloud instance. In the selection box or input box corresponding to the "cloud instance identification", the identification information of the cloud instance can be selected or input, and in the selection box or input box corresponding to the "priority", the service priority of the corresponding cloud instance can be selected or input. The tenant can configure the service priority of cloud instance 1 to be high, and configure the service priority of cloud instance 3 to be low.

[0147] like Fig.10 As shown in the third graphical interface 1020 in the diagram, tenants can select and input the three items of "Business ID", "Cloud Instance ID" and "Priority" in the third graphical interface 1020 to determine the priority of each business, and then determine the business priority of each cloud instance. In the selection box or input box corresponding to the "Business ID", the identification information of the business can be selected or input, in the selection box or input box corresponding to the "Cloud Instance ID", the identification information of the cloud instance where each business is located can be selected or input, and in the selection box or input box corresponding to the "Priority", the priority of each business can be selected or input. Tenants can configure the priority of business 1 to be high, and configure the priority of business 2 to be low.

[0148] When only one service is running in a cloud instance, the priority of the cloud instance can be determined according to the priority of the service. When multiple services are running in a cloud instance, the priority of the cloud instance can be the highest priority among the priorities of the multiple services. Alternatively, the priority of the cloud instance can be the highest priority among the priorities of the multiple services.

[0149] For example, suppose that cloud instance 1 runs service 1, service 2, and service 3, and the priority of service 1 is high, and the priorities of service 2 and service 3 are low. The service priority of cloud instance 1 may be the highest priority among the priorities of service 1, service 2, and service 3, that is, the service priority of cloud instance 1 may be high. Alternatively, the service priority of cloud instance 1 may be the highest priority among the priorities of service 1, service 2, and service 3, that is, the service priority of cloud instance 1 may be low.

[0150] Optionally, the cloud management platform may determine the disaster recovery priority of at least one cloud instance based on a preemption policy. The preemption policy is used to indicate that the disaster recovery priority of a cloud instance is determined based on the business priority of the cloud instance. For example, the preemption policy is used to indicate that the disaster recovery priority of a first cloud instance is higher than that of a second cloud instance, and the business priority of the first cloud instance is higher than the business priority of the second cloud instance. The backup of the first cloud instance is not running in the disaster recovery resource pool, the backup of the second cloud instance is already running in the disaster recovery resource pool, and the first cloud instance and the second cloud instance are different cloud instances in the business resource pool that have failed or are undergoing an upgrade. The cloud management platform may replace the backup of the second cloud instance running in the disaster recovery resource pool with the backup of the first cloud instance based on the preemption policy, such as Fig.11 shown.

[0151] Fig.11 It is a schematic diagram of determining the disaster recovery priority of a cloud instance according to a preemption strategy provided in an embodiment of the present application. Fig.11 The business resource pool 910 and the disaster recovery resource pool 920 are included. Fig. 9 . After cloud instance 1, cloud instance 2, and cloud instance 3 in business resource pool 910 fail, the cloud management platform can run the backups of cloud instance 1, cloud instance 2, and cloud instance 3 in disaster recovery resource pool 920. After the backups of cloud instance 1, cloud instance 2, and cloud instance 3 run in disaster recovery resource pool 920, if cloud instance 4, cloud instance 5, and cloud instance 6 also fail. Since the business priorities of cloud instance 1, cloud instance 2, and cloud instance 4 are high, and the business priorities of cloud instance 3, cloud instance 5, and cloud instance 6 are low, that is, the business priority of cloud instance 4 is higher than the business priority of cloud instance 3. Therefore, the cloud management platform can determine that the disaster recovery priority of cloud instance 4 is higher than the disaster recovery priority of cloud instance 3, thereby replacing the backup of cloud instance 3 running in disaster recovery resource pool 920 with the backup of cloud instance 4. That is, the cloud management platform can interrupt the operation of the backup of cloud instance 3 in the disaster recovery resource pool, and run the backup of cloud instance 4 in the second physical server 921.

[0152] In some embodiments, if the backup of a cloud instance (e.g., cloud instance 3) that is interrupted in a disaster recovery resource pool generates local data, the cloud management platform can save the local data so that when the cloud instance resumes operation in the business resource pool, the local data can be used to continue running the business.

[0153] In some embodiments, the cloud management platform may issue an alarm to the tenant before the backup of the cloud instance in the disaster recovery resource pool is interrupted, so as to notify the tenant that the backup of the cloud instance is about to be interrupted.

[0154] In some embodiments, the priority of the first cloud instance is higher than the preset priority, and the priority of the second cloud instance is lower than or equal to the preset priority. In other words, only the backup of the cloud instance with a priority higher than the preset priority can occupy the resources in the disaster recovery resource pool, so as to run in the disaster recovery resource pool. The preset priority can be determined by the cloud management platform, or can be configured by the tenant.

[0155] When the tenant does not configure a priority for a service or cloud instance, the tenant can configure a seizure flag for the service and / or cloud instance. When the tenant configures a seizure flag for a service, the cloud instance running the service can also be configured with a seizure flag. The cloud management platform can replace the backup of the third cloud instance running in the disaster recovery resource pool with the backup of the fourth cloud instance based on the seizure flag and the seizure policy. The third cloud instance does not have a seizure flag, or each service running in the third cloud instance does not have a seizure flag. The fourth cloud instance is configured with a seizure flag, or at least one service running in the fourth cloud instance is configured with a seizure flag. The third cloud instance and the fourth cloud instance are different cloud instances in the service resource pool that have failed or are undergoing an upgrade.

[0156] Optionally, the cloud management platform may determine the disaster recovery priority of at least one cloud instance according to a downgrade strategy. The downgrade strategy is used to indicate that the disaster recovery priority of the cloud instance is determined according to the amount of resources included in the cloud instance. For example, the cloud management platform may determine the amount of downgraded resources for each cloud instance according to the amount of resources included in each cloud instance that fails or is being upgraded and the amount of resources included in the disaster recovery resource pool, and run the backup of each cloud instance in the disaster recovery resource pool according to the downgrade strategy and the amount of downgraded resources of each cloud instance, such as Fig.12 The downgraded resource amount of each cloud instance is less than or equal to the resource amount included in the business resource pool of each cloud instance.

[0157] In some embodiments, the ratio of the amount of resources included in the business resource pool and the amount of de-provisioned resources for each cloud instance in the multiple cloud instances may be the same or different.

[0158] Fig.12 It is a schematic diagram of determining the disaster recovery priority of a cloud instance according to a downgrade strategy provided in an embodiment of the present application. Fig.12 The business resource pool 910 and the disaster recovery resource pool 920 are included. Fig. 9The configuration in is the same. Assume that each cloud instance in cloud instance 1 to cloud instance 6 includes 4U8G of resources, and the second physical server 921 includes 12U24G of resources. Among them, the cloud instance includes 4U8G of resources, which means that the cloud instance includes 4 processor cores and a memory capacity of 8 gigabytes (GB). Similarly, the second physical server 921 includes 12U24G of resources, which means that the second physical server 921 includes 12 processor cores and a memory capacity of 24GB. When cloud instances 1 to 6 in the business resource pool 910 fail, the cloud management platform can determine the amount of downgraded resources for each cloud instance as 12U24G / 6=2U4G based on the amount of resources included in cloud instances 1 to 6 and the amount of resources included in the second physical server 921. That is, the cloud management platform can allocate 2U4G of resources in the second physical server 921 for the backup of each cloud instance in cloud instance 1 to cloud instance 6. The ratio of the amount of resources included in the business resource pool and the amount of downgraded resources for each cloud instance in cloud instance 1 to cloud instance 6 is 4U8G:2U4G=2:1. The cloud management platform can also run the backup of each cloud instance in the resources allocated to the backup of each cloud instance. In other words, the cloud management platform can determine to run the backup of each cloud instance in cloud instance 1 to cloud instance 6 in the second physical server 921 according to the downgrade strategy, but the amount of resources included in the disaster recovery resource pool 920 for the backup of each cloud instance is less than the amount of resources included in the business resource pool 910 for each cloud instance.

[0159] In some embodiments, the cloud instance 1 to the cloud instance 6 may be cloud instances that must be restored after a failure configured by the tenant.

[0160] In some embodiments, the sum of the amount of downgraded resources of the at least one cloud instance that fails or is undergoing an upgrade is less than or equal to the amount of resources included in the disaster recovery resource pool.

[0161] In some embodiments, the ratio of computing resources to storage resources included in the business resource pool for each cloud instance and the ratio of computing resources to storage resources included in the disaster recovery resource pool for the backup of each cloud instance may be the same or different. For example, cloud instance 7 may include 4U8G resources in the business resource pool, and the cloud management platform may allocate 2U4G or 2U3G resources in the disaster recovery resource pool for the backup of cloud instance 7.

[0162] In some embodiments, the cloud management platform may determine the amount of downgraded resources for each cloud instance based on the downgrade information, the amount of resources included in each cloud instance, and the amount of resources included in the disaster recovery resource pool. The downgrade information includes a minimum downgrade ratio and / or minimum resource quantity information. The minimum downgrade ratio is used to indicate the minimum ratio between the amount of resources included in the business resource pool and the amount of downgraded resources of the cloud instance. The minimum resource quantity information is used to indicate the minimum amount of resources included in the cloud instance. The downgrade ratio of each cloud instance is greater than or equal to the minimum downgrade ratio of each cloud instance, and / or, the amount of downgraded resources of each cloud instance is greater than or equal to the minimum amount of resources of each cloud instance. The downgrade ratio of the cloud instance is the ratio of the amount of resources included in the business resource pool of the cloud instance to the amount of downgraded resources. The downgrade information may be determined by the cloud management platform. Alternatively, the downgrade information may be configured by the tenant.

[0163] In some embodiments, the cloud management platform may determine the amount of resources to be downgraded for each cloud instance based on the minimum downgrading ratio, the amount of resources included in each cloud instance, and the amount of resources included in the disaster recovery resource pool.

[0164] For example, assume that cloud instances 1 to 6 all include 4U8G resources in the business resource pool and 12U24G resources in the disaster recovery resource pool. If the minimum downsizing ratios of cloud instance 1 and cloud instance 2 are both 1:1, the cloud management platform can determine that the downsizing resources of cloud instance 1 and cloud instance 2 are 4U8G respectively based on the minimum downsizing ratio, the amount of resources included in the business resource pool of cloud instance 1 and cloud instance 2, and the amount of resources included in the disaster recovery resource pool. The downsizing ratios of cloud instance 1 and cloud instance 2 are 1:1, and the downsizing ratio of cloud instance 1 is greater than or equal to the minimum downsizing ratio of cloud instance 1, and the downsizing ratio of cloud instance 2 is greater than or equal to the minimum downsizing ratio of cloud instance 2. Assuming that cloud instance 3 to cloud instance 6 are not configured with a minimum downgrading ratio, the cloud management platform can also determine the downgrading amount of resources for cloud instance 3 to cloud instance 6 as (12U24G-4U8G-4U8G) / 4=1U2G based on the remaining allocatable resources in the disaster recovery resource pool and the resources included in cloud instance 3 to cloud instance 6.

[0165] In some embodiments, the cloud management platform may determine the amount of resources to be downgraded for each cloud instance based on the minimum resource amount information, the amount of resources included in each cloud instance, and the amount of resources included in the disaster recovery resource pool.

[0166] For example, assume that cloud instances 1 to 6 all include 4U8G resources in the business resource pool and 12U24G resources in the disaster recovery resource pool. If the minimum resource amount included in cloud instance 1 and cloud instance 2 is 4U8G, the cloud management platform can determine that the reduced resource amount of cloud instance 1 and cloud instance 2 is 4U8G based on the minimum resource amount included in cloud instance 1 and cloud instance 2 and the resource amount included in the disaster recovery resource pool. Assuming that cloud instances 3 to 6 are not configured with the minimum resource amount, the cloud management platform can determine that the reduced resource amount of cloud instances 3 to 6 is (12U24G-4U8G-4U8G) / 4=1U2G based on the remaining allocatable resources in the disaster recovery resource pool and the resource amount included in cloud instances 3 to 6.

[0167] Optionally, the cloud management platform may provide a fourth graphical interface to the tenant, so that the tenant can select or upload the downgrade information on the fourth graphical interface. The embodiment of the present application does not limit the specific form of the fourth graphical interface.

[0168] Optionally, the cloud management platform may determine the disaster recovery priority of at least one cloud instance according to the best matching strategy. The best matching strategy is used to indicate that the disaster recovery priority of the cloud instance is determined according to the resource type included in the cloud instance. For example, the cloud management platform may determine the resources matched by each cloud instance according to the resource type included in each cloud instance that fails or is being upgraded and the resource type included in the disaster recovery resource pool, and run the backup of each cloud instance in the disaster recovery resource pool according to the best matching strategy and the resources matched by each cloud instance.

[0169] For example, assume that cloud instance 1 includes 4U8G graphics processing unit (GPU) computing resources and fourth-generation dynamic random access memory (double data rate 4, DDR4) storage resources in the business resource pool, and cloud instance 2 includes 4U6G central processing unit (CPU) computing resources and third-generation dynamic random access memory (double data rate 3, DDR3) storage resources in the business resource pool. Assuming that both cloud instance 1 and cloud instance 2 fail, and the disaster recovery resource pool includes 4U10G GPU computing resources and DDR4 storage resources, and 4U6G CPU computing resources and DDR3 storage resources, the cloud management platform can determine the resources in the disaster recovery resource pool that match the resource types included in the business resource pool of cloud instance 1 and cloud instance 2, respectively, so as to allocate 4U8G GPU computing resources and DDR4 storage resources in the disaster recovery resource pool for the backup of cloud instance 1, and allocate 4U6G CPU computing resources and DDR3 storage resources in the disaster recovery resource pool for the backup of cloud instance 2. The cloud management platform may also run the backup of cloud instance 1 in the resources to which the backup of cloud instance 1 is allocated, and run the backup of cloud instance 2 in the resources to which the backup of cloud instance 2 is allocated.

[0170] In some embodiments, the cloud management platform can determine the priority of each resource based on the resource priority information, thereby determining the resources that match each cloud instance according to the resource priority information, the resource type of each cloud instance, and the resource type included in the disaster recovery resource pool in descending order of resource priority. The resource priority information is used to indicate the priority of each resource included in the cloud instance. The resource priority information can be determined by the cloud management platform itself. Alternatively, it can be configured by the tenant.

[0171] For example, assume that cloud instance 1 includes 4U8G of GPU computing resources and DDR4 storage resources in the business resource pool, cloud instance 2 includes 4U8G of CPU computing resources and DDR4 storage resources in the business resource pool, and cloud instance 3 includes 4U8G of CPU computing resources and DDR3 storage resources in the business resource pool. Cloud instance 1, cloud instance 2, and cloud instance 3 all fail. If the disaster recovery resource pool only includes 8U16G of GPU computing resources and DDR4 storage resources, and the resource priority information indicates that the priority of computing resources is greater than the priority of storage resources, the cloud management platform can prioritize cloud instance 1 as the cloud instance that matches the type of computing resources included in the disaster recovery resource pool, thereby allocating 4U8G of GPU computing resources and DDR4 storage resources to the backup of cloud instance 1 in the disaster recovery resource pool, and then running the backup of cloud instance 1. The cloud management platform can also determine that the cloud instance that matches the type of storage resources included in the remaining allocatable resources in the disaster recovery resource pool is cloud instance 2, thereby allocating 4U8G of GPU computing resources and DDR4 storage resources to the backup of cloud instance 2 in the disaster recovery resource pool, and then running the backup of cloud instance 2.

[0172] If the disaster recovery resource pool only includes 8U16G of GPU computing resources and DDR3 storage resources, and the resource priority information indicates that the priority of storage resources is greater than the priority of computing resources, the cloud management platform can preferentially determine that the cloud instance that matches the type of storage resources included in the disaster recovery resource pool is cloud instance 3, thereby allocating 4U8G of GPU computing resources and DDR3 storage resources to the backup of cloud instance 3 in the disaster recovery resource pool, and then running the backup of cloud instance 3. The cloud management platform can also determine that the cloud instance that matches the type of computing resources included in the remaining allocable resources in the disaster recovery resource pool is cloud instance 1, thereby allocating 4U8G of GPU computing resources and DDR3 storage resources to the backup of cloud instance 1 in the disaster recovery resource pool, and then running the backup of cloud instance 1.

[0173] Optionally, the cloud management platform may provide a fifth graphical interface to the tenant, so that the tenant may select or upload the resource priority information on the fifth graphical interface. The embodiment of the present application does not limit the specific form of the fifth graphical interface.

[0174] Optionally, the cloud management platform may determine the disaster recovery priority of at least one cloud instance according to a sequential disaster recovery strategy. The sequential disaster recovery strategy is used to indicate that the disaster recovery priority of the cloud instances is determined according to the time sequence in which the cloud instances fail or are upgraded. For example, assuming that the time when cloud instance 1 fails is earlier than the time when cloud instance 2 fails, the cloud management platform may determine that the disaster recovery priority of cloud instance 1 is higher than the disaster recovery priority of cloud instance 2.

[0175] When the disaster recovery strategy configuration information includes multiple disaster recovery strategies, the cloud management platform may determine the disaster recovery priority of at least one cloud instance that fails or is being upgraded based on the multiple disaster recovery strategies.

[0176] For example, assuming that the disaster recovery strategy configuration information includes a priority strategy and a preemption strategy, when the disaster recovery resource pool includes unallocated resources or there are more unallocated resources, the cloud management platform can determine the disaster recovery priority of at least one cloud instance that fails or is upgraded based on the priority strategy. When there are no unallocated resources or there are fewer unallocated resources in the disaster recovery resource pool, the cloud management platform can also replace the backup of the cloud instance with a lower priority running in the disaster recovery resource pool with the backup of the cloud instance with a higher priority based on the preemption strategy. The more unallocated resources means that the amount of unallocated resources is greater than a preset threshold, and the less unallocated resources means that the amount of unallocated resources is less than or equal to the preset threshold. The embodiment of the present application does not limit the specific size of the preset threshold.

[0177] For example, assuming that the disaster recovery policy configuration information includes a priority policy and a downgrade policy, the cloud management platform can determine the disaster recovery priority of each cloud instance according to the priority policy. If the sum of the resource amounts included in the cloud instances with higher priorities is greater than the resource amounts included in the disaster recovery resource pool, the cloud management platform can also determine the downgraded resource amount of each cloud instance with higher priorities according to the downgrade policy, thereby running the backup of each cloud instance with higher priorities in the disaster recovery resource pool. The resource amount included in the backup of each cloud instance with higher priorities in the disaster recovery resource pool is the downgraded resource amount of the cloud instance. The cloud instance with higher priority can be a cloud instance with a priority higher than the preset priority. If the sum of the resource amounts included in the cloud instances with higher priorities is less than the resource amount included in the disaster recovery resource pool, the cloud management platform can also determine the downgraded resource amount of at least one cloud instance with lower priority according to the downgrade policy, thereby running the backup of each cloud instance with higher priority and the backup of at least one cloud instance with lower priority in the disaster recovery resource pool. The resource amount included in the business resource pool of each cloud instance with higher priority and the resource amount included in the backup of the cloud instance with higher priority in the disaster recovery resource pool are the same. The amount of resources included in the disaster recovery resource pool for the backup of each cloud instance with a lower priority is the downgraded amount of resources of the cloud instance. The cloud instance with a lower priority may be a cloud instance with a priority lower than or equal to a preset priority.

[0178] For example, assuming that the disaster recovery policy configuration information includes a priority policy and a best match policy, the cloud management platform can determine the disaster recovery priority of each cloud instance according to the priority policy. The cloud management platform can also preferentially allocate resources matching the cloud instance to the backup of each cloud instance with a higher priority in the disaster recovery resource pool according to the best match policy, thereby running the backup of at least one cloud instance.

[0179] For example, assume that the disaster recovery policy configuration information includes a coercion policy and a downgrade policy. When replacing the backup of the second cloud instance in the disaster recovery resource pool with the backup of the first cloud instance, if the amount of resources included in the backup of the second cloud instance is less than the amount of resources included in the first cloud instance, the cloud management platform can determine the amount of downgraded resources of the first cloud instance according to the downgrade policy, thereby running the backup of the first cloud instance in the disaster recovery resource pool. The business priority of the second cloud instance is lower than the business priority of the first cloud instance. The downgraded amount of resources of the first cloud instance is less than or equal to the amount of resources included in the backup of the second cloud instance in the disaster recovery resource pool. Alternatively, the cloud management platform can first run the backup of at least one cloud instance in the disaster recovery resource pool according to the downgrade policy. After a new cloud instance that fails or is being upgraded appears, the cloud management platform can run the backup of one or more cloud instances in the disaster recovery resource pool according to the coercion policy.

[0180] For example, assuming that the disaster recovery policy configuration information includes a coercion policy and a best match policy, the cloud management platform can allocate matching resources to one or more backups of the first cloud instance in at least one first cloud instance when replacing the backup of at least one second cloud instance with the backup of at least one first cloud instance according to the coercion policy, thereby running the backup of the at least one first cloud instance. Alternatively, the cloud management platform can first determine the disaster recovery priority of at least one cloud instance according to the best match policy. When a new cloud instance that fails or is being upgraded appears, the cloud management platform can run the backup of one or more cloud instances in the disaster recovery resource pool according to the coercion policy.

[0181] For example, assuming that the disaster recovery policy configuration information includes downgrade policies and downgrade policies. The cloud management platform can allocate resources to the backup of the cloud instance that matches the resource type included in the disaster recovery resource pool in priority according to the downgraded resource amount of each cloud instance, thereby running the backup of at least one cloud instance. Alternatively, the cloud management platform can first determine one or more cloud instances that match the resource type included in the disaster recovery resource pool according to the best matching policy, and run the backup of the one or more cloud instances. Then, the cloud management platform can determine the downgraded resource amount of one or more cloud instances that do not match the resource type included in the disaster recovery resource pool according to the downgrade policy, thereby running the backup of the one or more cloud instances.

[0182] For example, assuming that the disaster recovery policy configuration information includes a priority policy, a coercion policy, and a downgrade policy. The cloud management platform can first determine the disaster recovery priority of at least one cloud instance according to the order of descending priority. When the resources in the disaster recovery resource pool are insufficient to continue to be allocated to the cloud instance, the cloud management platform can run the backup of at least one cloud instance in the disaster recovery resource pool according to the coercion policy and / or the downgrade policy.

[0183] For example, assume that the disaster recovery policy configuration information includes a priority policy, a coercion policy, and a best match policy. The cloud management platform can first determine the disaster recovery priority of at least one cloud instance according to the order of descending priority. The cloud management platform can also allocate resources of matching types to cloud instances with higher priorities according to the best match policy. When the resources in the disaster recovery resource pool are insufficient to continue to be allocated to the cloud instance, the cloud management platform can run a backup of at least one cloud instance in the disaster recovery resource pool according to the coercion policy.

[0184] When the cloud management platform determines the disaster recovery priority of at least one cloud instance according to multiple disaster recovery strategies and a contradiction or conflict occurs, the disaster recovery priority of the at least one cloud instance can be determined according to the strategy priority information and the multiple disaster recovery strategies. The strategy priority information is used to indicate the priority of each disaster recovery strategy in the at least one disaster recovery strategy. For example, the cloud management platform can determine the disaster recovery priority of the at least one cloud instance according to the strategy priority information and the multiple disaster recovery strategies in descending order of priority of the disaster recovery strategies.

[0185] In some embodiments, the cloud management platform may provide a sixth graphical interface for the tenant, so that the tenant may select or upload the policy priority information in the sixth graphical interface. The embodiment of the present application does not limit the specific form of the sixth graphical interface.

[0186] S820: Run backups of one or more cloud instances in a disaster recovery resource pool according to the disaster recovery priority of the at least one cloud instance.

[0187] After determining the disaster recovery priority of each cloud instance in the at least one cloud instance, the cloud management platform may determine one or more cloud instances to run backups in the disaster recovery resource pool. The cloud management platform may also allocate resources in the disaster recovery resource pool for the backup of each cloud instance in the one or more cloud instances, and run the backup of each cloud instance in the resources allocated to the backup of the cloud instance.

[0188] In an embodiment of the present application, when at least one cloud instance in a business resource pool fails or is upgraded, a backup of the failed or upgraded cloud instance can be run in the disaster recovery resource pool according to the disaster recovery strategy configured by the tenant, thereby reducing the impact on the tenant's business. The method in an embodiment of the present application can ensure that the tenant's important business can be restored first according to the disaster recovery strategy configured by the tenant, or when the resources in the disaster recovery resource pool are insufficient, appropriate resources can be allocated to the backup of each cloud instance, so as to run as many backups of cloud instances as possible in the disaster recovery resource pool, or the resource configuration of the backup of the cloud instance in the disaster recovery resource pool can be made as consistent as possible with the resource configuration of the cloud instance in the business resource pool, thereby reducing the impact on the tenant's business.

[0189] Fig.13It is a schematic structural diagram of the fault handling device provided in an embodiment of the present application. Fig.13 The fault handling device 1300 includes a receiving module 1310 and a processing module 1320. Fig.13 The fault handling device 1300 in the embodiment can be applied to a cloud management platform, for example Figure 1 Cloud management platform 110 or Figure 2 The cloud management platform 210 in.

[0190] The receiving module 1310 can be used to obtain a tenant's business resource pool creation request, and create a business resource pool for the tenant in the infrastructure according to the business resource pool creation request. The business resource pool includes M first physical servers, each of which is used to host one or more cloud instances of the tenant, and M is a positive integer greater than 0. The receiving module 1310 can also be used to obtain a tenant's disaster recovery resource pool creation request, and create a disaster recovery resource pool for the tenant in the infrastructure according to the disaster recovery resource pool creation request. The disaster recovery resource pool includes N second physical servers, and N is a positive integer greater than 0. The receiving module 1310 can also be used to receive a disaster recovery strategy configured by the tenant. The receiving module 1310 can be used to execute Figure 3 Steps S310, S320, and S330 in FIG.

[0191] The processing module 1320 may be used to run a backup of at least one cloud instance that has failed or is being upgraded in any number of the M first physical servers in accordance with the disaster recovery strategy in the N second physical servers when at least one cloud instance in any number of the M first physical servers fails or is being upgraded. The processing module 1320 may execute Figure 3 Step S340 in Figure 6 Steps S610, S620, Figure 8 Steps S810 and S820 in .

[0192] Among them, the receiving module 1310 and the processing module 1320 can be implemented by software or by hardware. Exemplarily, the implementation of the receiving module 1310 is introduced below by taking the receiving module 1310 as an example. Similarly, the implementation of the processing module 1320 can refer to the implementation of the receiving module 1310.

[0193] As an example of a software functional unit, the receiving module 1310 may include code running on a computing instance. Among them, the computing instance may include at least one of a physical host (computing device), a virtual machine, and a container. Further, the above-mentioned computing instance may be one or more. For example, the receiving module 1310 may include code running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers used to run the code may be distributed in the same region (region) or in different regions. Furthermore, the multiple hosts / virtual machines / containers used to run the code may be distributed in the same availability zone (AZ) or in different AZs, each AZ including a data center or multiple data centers with similar geographical locations. Among them, usually a region may include multiple AZs.

[0194] Similarly, multiple hosts / virtual machines / containers used to run the code can be distributed in the same VPC or in multiple VPCs. Usually, a VPC is set up in a region. For cross-region communication between two VPCs in the same region and between VPCs in different regions, a communication gateway needs to be set up in each VPC to achieve interconnection between VPCs through the communication gateway.

[0195] As an example of a hardware functional unit, the receiving module 1310 may include at least one computing device, such as a server, etc. Alternatively, the receiving module 1310 may also be a device implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD may be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof.

[0196] The multiple computing devices included in the receiving module 1310 can be distributed in the same region or in different regions. The multiple computing devices included in the receiving module 1310 can be distributed in the same AZ or in different AZs. Similarly, the multiple computing devices included in the receiving module 1310 can be distributed in the same VPC or in multiple VPCs. The multiple computing devices can be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.

[0197] Therefore, the modules of each example described in the embodiments of the present application can be implemented with electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present application.

[0198] It should be noted that: when the device provided in the above embodiment executes the above method, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. For example, the receiving module 1310 can be used to execute any step in the above method, and the processing module 1320 can be used to execute any step in the above method. The steps that the receiving module 1310 and the processing module 1320 are responsible for implementing can be specified as needed, and all the functions of the above device can be realized by respectively implementing different steps in the above method through the receiving module 1310 and the processing module 1320.

[0199] In addition, the device and method embodiments provided in the above embodiments belong to the same concept, and their specific implementation processes are detailed in the method embodiments above, which will not be repeated here.

[0200] The method provided in the embodiment of the present application can be performed by a computing device, which can also be referred to as a computer system. It includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a processing unit, a memory and a memory control unit, and then the function and structure of the hardware are described in detail. The operating system is any one or more computer operating systems that implement business processing through a process, for example, a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a windows operating system. The application layer includes applications such as a browser, an address book, a word processing software, and an instant messaging software. In addition, optionally, the computer system is a handheld device such as a smart phone, or a terminal device such as a personal computer, and the present application is not particularly limited, as long as the method provided by the embodiment of the present application can be used. The execution subject of the method provided in the embodiment of the present application can be a computing device, or a functional module in a computing device that can call a program and execute a program.

[0201] Fig.14 1 is a schematic structural block diagram of a computing device 1400 provided in an embodiment of the present application. The computing device 1400 may be a server or a computer or other device with computing capabilities. Fig.14 The computing device 1400 shown includes at least one processor 1410 and a memory 1420 .

[0202] It should be understood that the present application does not limit the number of processors and memories in the computing device 1400 .

[0203] The processor 1410 executes the instructions in the memory 1420, so that the computing device 1400 implements the method provided by the present application. Alternatively, the processor 1410 executes the instructions in the memory 1420, so that the computing device 1400 implements the functional modules provided by the present application, thereby implementing the method provided by the present application.

[0204] Optionally, the computing device 1400 further includes a communication interface 1430. The communication interface 1430 uses a transceiver module such as, but not limited to, a network interface card or a transceiver to implement communication between the computing device 1400 and other devices or a communication network.

[0205] Optionally, the computing device 1400 further includes a system bus 1440, wherein the processor 1410, the memory 1420 and the communication interface 1430 are respectively connected to the system bus 1440. The processor 1410 can access the memory 1420 through the system bus 1440. For example, the processor 1410 can read and write data or execute code in the memory 1420 through the system bus 1440. The system bus 1440 is a peripheral component interconnect express (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The system bus 1440 is divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.14 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0206] In a possible implementation, the function of the processor 1410 is mainly to interpret the instructions (or codes) of the computer program and process the data in the computer software. The instructions of the computer program and the data in the computer software can be stored in the memory 1420 or the cache of the processor 1410.

[0207] Optionally, the processor 1410 may be an integrated circuit chip with signal processing capabilities. As an example and not limitation, the processor 1410 is a general-purpose processor, a digital signal processor (DSP), an ASIC, an FPGA or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. Among them, the general-purpose processor is a microprocessor, etc. For example, the processor 1410 is a central processing unit (CPU).

[0208] The memory 1420 can provide a running space for the processes in the computing device 1400. For example, the computer program (specifically, the program code) used to generate the process is stored in the memory 1420. After the computer program is executed by the processor to generate the process, the processor allocates a corresponding storage space for the process in the memory 1420. Furthermore, the above storage space further includes a text segment, an initialized data segment, a bit initialized data segment, a stack segment, a heap segment, etc. The memory 1420 stores the data generated during the running of the process in the storage space corresponding to the above process, such as intermediate data, process data, etc.

[0209] Optionally, the storage is also called memory, which is used to temporarily store the calculation data in the processor 1410 and the data exchanged with the external storage such as the hard disk. As long as the computer is running, the processor 1410 will transfer the data to be calculated to the memory for calculation, and transmit the result after the calculation is completed.

[0210] As an example and not limitation, the memory 1420 is a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. The non-volatile storage medium may be, for example, a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory is a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct rambus DRAM (DRDRAM). It should be noted that the memory 1420 of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0211] The structure of the computing device 1400 listed above is only an example, and the present application is not limited thereto. The computing device 1400 of the embodiment of the present application includes various hardware in the computer system in the prior art. For example, the computing device 1400 also includes other memories besides the memory 1420, such as disk storage, etc. Those skilled in the art should understand that the computing device 1400 may also include other devices necessary for normal operation. At the same time, according to specific needs, those skilled in the art should understand that the above-mentioned computing device 1400 may also include hardware devices for implementing other additional functions. In addition, those skilled in the art should understand that the above-mentioned computing device 1400 may also include only the devices necessary to implement the embodiment of the present application, and does not necessarily include Fig.14 All devices shown in .

[0212] The embodiment of the present application also provides a computing device cluster. The computing device cluster includes at least one computing device. The computing device may be a server. In some embodiments, the computing device may also be a terminal device such as a desktop computer, a laptop computer, or a smart phone.

[0213] like Fig.15 As shown, the computing device cluster includes at least one computing device 1400. The memory 1420 in one or more computing devices 1400 in the computing device cluster may store the same instructions for executing the above method.

[0214] In some possible implementations, the memory 1420 in one or more computing devices 1400 in the computing device cluster may also store partial instructions for executing the above method. In other words, the combination of one or more computing devices 1400 may jointly execute the instructions of the above method.

[0215] It should be noted that the memory 1420 in different computing devices 1400 in the computing device cluster may store different instructions, which are respectively used to execute part of the functions of the above-mentioned apparatus. That is, the instructions stored in the memory 1420 in different computing devices 1400 may implement the functions of one or more modules in the above-mentioned apparatus.

[0216] In some possible implementations, one or more computing devices in the computing device cluster may be connected via a network, which may be a wide area network or a local area network. Fig.16 A possible implementation is shown. Fig.16 As shown, two computing devices 1400A and 1400B are connected via a network. Specifically, they are connected to the network via a communication interface in each computing device.

[0217] It should be understood that Fig.16The functionality of the computing device 1400A shown in FIG. 1400A may also be implemented by multiple computing devices 1400. Similarly, the functionality of the computing device 1400B may also be implemented by multiple computing devices 1400.

[0218] In this embodiment, a computer program product including instructions is also provided, and the computer program product may be software or a program product including instructions that can be run on a computing device or stored in any available medium. When the computer program product is run on a computing device, the computing device is caused to execute the method provided above, or the computing device is caused to implement the function of the apparatus provided above.

[0219] In this embodiment, a computer program product including instructions is also provided, and the computer program product may be software or a program product including instructions that can be run on a computing device cluster or stored in any available medium. When the computer program product is run by a computing device cluster, the computing device cluster executes the method provided above, or the computing device cluster implements the function of the apparatus provided above.

[0220] In this embodiment, a computer-readable storage medium is also provided, and the computer-readable storage medium can be any available medium that can be stored by a computing device or a data storage device such as a data center containing one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital video disc (DVD)), or a semiconductor medium (e.g., a solid-state hard disk), etc. The computer-readable storage medium includes instructions, and when the instructions in the computer-readable storage medium are executed on a computing device, the computing device executes the method provided above.

[0221] In this embodiment, a computer-readable storage medium is also provided, and the computer-readable storage medium can be any available medium that can be stored by a computing device or a data storage device such as a data center that includes one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk), etc. The computer-readable storage medium includes instructions, and when the instructions in the computer-readable storage medium are executed by a computing device cluster, the computing device cluster executes the method provided above.

[0222] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0223] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0224] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0225] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0226] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0227] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0228] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A fault handling method, characterized in that: The method is applied to a cloud management platform, the cloud management platform is used to manage infrastructure that provides cloud instances, the infrastructure includes at least one data center, and the method includes: Obtaining a business resource pool creation request of a tenant, and creating a business resource pool for the tenant in the infrastructure according to the business resource pool creation request, wherein the business resource pool includes M first physical servers, each of which is used to host one or more cloud instances of the tenant, and M is a positive integer greater than 0; Obtaining a disaster recovery resource pool creation request of the tenant, and creating a disaster recovery resource pool for the tenant in the infrastructure according to the disaster recovery resource pool creation request, wherein the disaster recovery resource pool includes N second physical servers, and when at least one cloud instance in any number of first physical servers among the M first physical servers fails or is upgraded, the N second physical servers are used to run a backup of at least one cloud instance that fails or is upgraded in the M first physical servers, where N is a positive integer greater than 0 and less than or equal to M; Receiving a disaster recovery policy configured by the tenant, where the disaster recovery policy is used to indicate a disaster recovery priority of a cloud instance running on the business resource pool; In the event that at least one cloud instance in any number of the M first physical servers fails or is being upgraded, a backup of at least one cloud instance that fails or is being upgraded in the M first physical servers is run in the N second physical servers according to the disaster recovery strategy.

2. The method according to claim 1, characterized in that The disaster recovery priority is determined according to at least one of the following: a service priority of the cloud instance, an amount of resources included in the cloud instance, or a type of resources included in the cloud instance.

3. The method according to claim 1 or 2, characterized in that: The disaster recovery strategy includes a priority strategy, where the priority strategy is used to indicate that the disaster recovery priority is determined according to the service priority of the cloud instance, and running a backup of at least one cloud instance that fails or is being upgraded in the M first physical servers in the N second physical servers according to the disaster recovery strategy includes: According to the priority policy, the backup of the at least one cloud instance is run in the N second physical servers in sequence in descending order of the disaster recovery priority.

4. The method according to any one of claims 1 to 3, characterized in that The disaster recovery strategy also includes a preemption strategy, wherein the preemption strategy is used to indicate that the disaster recovery priority of the first cloud instance is higher than the disaster recovery priority of the second cloud instance, the service priority of the first cloud instance is higher than the service priority of the second cloud instance, the backup of the first cloud instance is not running in the N second physical servers, the backup of the second cloud instance is running in the N second physical servers, and the first cloud instance and the second cloud instance are different cloud instances in the M first physical servers that have failed or are being upgraded. The step of running a backup of at least one cloud instance that fails or is being upgraded in the M first physical servers in the N second physical servers according to the disaster recovery strategy includes: According to the preemption policy, the backup of the second cloud instance running in the N second physical servers is replaced by the backup of the first cloud instance.

5. The method according to claim 4, characterized in that The service priority of the first cloud instance is higher than a preset priority, and the service priority of the second cloud instance is lower than or equal to the preset priority.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: Priority information configured by the tenant is received, where the priority information is used to indicate a service priority of a cloud instance running on the service resource pool.

7. The method according to any one of claims 1 to 6, characterized in that The disaster recovery strategy also includes a downgrade strategy, where the downgrade strategy is used to indicate that the disaster recovery priority is determined according to the amount of resources included in the cloud instance, and running a backup of at least one cloud instance that fails or is being upgraded in the M first physical servers in the N second physical servers according to the disaster recovery strategy includes: Determine, according to the amount of resources included in each cloud instance of the at least one cloud instance that fails or is being upgraded and the amount of resources included in the N second physical servers, the amount of resources to be downgraded for each cloud instance, wherein the amount of resources to be downgraded for each cloud instance is less than or equal to the amount of resources included in the service resource pool for each cloud instance; According to the downgrading strategy and the downgrading resource amount of each cloud instance, a backup of the at least one cloud instance is run in the N second physical servers.

8. The method according to claim 7, characterized in that The determining, according to the amount of resources included in each cloud instance in the at least one cloud instance that fails or is being upgraded and the amount of resources included in the N second physical servers, the amount of resources to be downgraded for each cloud instance comprises: Receive downgrade information configured by the tenant, the downgrade information including a minimum downgrade ratio and / or minimum resource quantity information, the minimum downgrade ratio is used to indicate a minimum ratio of the amount of resources included in the business resource pool of the cloud instance to the amount of downgraded resources, and the minimum resource quantity information is used to indicate the minimum amount of resources included in the cloud instance; The downgraded resource amount of each cloud instance is determined based on the downgrade information, the amount of resources included in each cloud instance, and the amount of resources included in the N second physical servers, the ratio of the amount of resources included in the business resource pool to the downgraded resource amount of each cloud instance is greater than or equal to the minimum downgrade ratio of each cloud instance, and / or the downgraded resource amount of each cloud instance is greater than or equal to the minimum resource amount of each cloud instance.

9. The method according to any one of claims 1 to 8, characterized in that The disaster recovery strategy also includes a best matching strategy, where the best matching strategy is used to indicate that the disaster recovery priority is determined according to the resource type included in the cloud instance, and running a backup of at least one cloud instance that fails or is being upgraded in the M first physical servers in the N second physical servers according to the disaster recovery strategy includes: Determining resources matched by each cloud instance according to the resource type included in each cloud instance in the at least one cloud instance and the resource type included in the N second physical servers; According to the best matching strategy and the resources matched by each cloud instance, a backup of the at least one cloud instance is run in the N second physical servers.

10. The method according to claim 9, characterized in that The determining, according to the resource type included in each cloud instance in the at least one cloud instance and the resource type included in the N second physical servers, the resources matched by each cloud instance includes: receiving resource priority information configured by the tenant, wherein the resource priority information is used to indicate the priority of each resource included in the cloud instance; According to the resource priority information, the resource types included in each cloud instance and the resource types included in the N second physical servers, the resources that match each cloud instance are determined in descending order of resource priority.

11. The method according to any one of claims 1 to 10, characterized in that The method further comprises: Predicting the disaster recovery reliability of the disaster recovery resource pool according to the business resource pool creation request, the disaster recovery resource pool creation request and the disaster recovery strategy, wherein the disaster recovery reliability is used to indicate the ability of the N second physical servers to run a backup of at least one cloud instance that fails or is being upgraded when at least one cloud instance in any number of the first physical servers among the M first physical servers fails or is being upgraded; The disaster recovery reliability is provided to the tenant.

12. A fault handling device, characterized in that: The device is applied to a cloud management platform, the cloud management platform is used to manage infrastructure that provides cloud instances, the infrastructure includes at least one data center, and the device includes: A receiving module, configured to obtain a business resource pool creation request of a tenant, and create a business resource pool for the tenant in the infrastructure according to the business resource pool creation request, wherein the business resource pool includes M first physical servers, each of which is used to host one or more cloud instances of the tenant, and M is a positive integer greater than 0; The receiving module is further used to obtain a disaster recovery resource pool creation request of the tenant, and create a disaster recovery resource pool for the tenant in the infrastructure according to the disaster recovery resource pool creation request, wherein the disaster recovery resource pool includes N second physical servers, and when at least one cloud instance in any number of first physical servers among the M first physical servers fails or is upgraded, the N second physical servers are used to run a backup of at least one cloud instance that fails or is upgraded in the M first physical servers, where N is a positive integer greater than 0 and less than or equal to M; The receiving module is further used to receive a disaster recovery strategy configured by the tenant, where the disaster recovery strategy is used to indicate a disaster recovery priority of a cloud instance running on the business resource pool; A processing module is used to run a backup of at least one cloud instance that fails or is being upgraded in the M first physical servers in the N second physical servers according to the disaster recovery strategy when at least one cloud instance in any number of the M first physical servers fails or is being upgraded.

13. The device according to claim 12, characterized in that The disaster recovery priority is determined according to at least one of the following: a service priority of the cloud instance, an amount of resources included in the cloud instance, or a type of resources included in the cloud instance.

14. The device according to claim 12 or 13, characterized in that The disaster recovery strategy includes a priority strategy, and the priority strategy is used to indicate that the disaster recovery priority is determined according to the business priority of the cloud instance. The processing module is specifically used to run the backup of the at least one cloud instance in the N second physical servers in descending order of the disaster recovery priority according to the priority strategy.

15. The device according to any one of claims 12 to 14, characterized in that The disaster recovery strategy also includes a preemption strategy, wherein the preemption strategy is used to indicate that the disaster recovery priority of the first cloud instance is higher than that of the second cloud instance, the business priority of the first cloud instance is higher than the business priority of the second cloud instance, the backup of the first cloud instance is not running in the N second physical servers, the backup of the second cloud instance is running in the N second physical servers, the first cloud instance and the second cloud instance are different cloud instances in the M first physical servers that fail or are being upgraded, and the processing module is specifically used to replace the backup of the second cloud instance running in the N second physical servers with the backup of the first cloud instance according to the preemption strategy.

16. The device according to claim 15, characterized in that The service priority of the first cloud instance is higher than a preset priority, and the service priority of the second cloud instance is lower than or equal to the preset priority.

17. The device according to any one of claims 12 to 16, characterized in that The receiving module is further used to receive priority information configured by the tenant, where the priority information is used to indicate the service priority of the cloud instance running on the service resource pool.

18. The device according to any one of claims 12 to 17, characterized in that The disaster recovery strategy further includes a downgrade strategy, and the downgrade strategy is used to indicate that the disaster recovery priority is determined according to the amount of resources included in the cloud instance. The processing module is specifically used to: Determine, according to the amount of resources included in each cloud instance of the at least one cloud instance that fails or is being upgraded and the amount of resources included in the N second physical servers, the amount of resources to be downgraded for each cloud instance, wherein the amount of resources to be downgraded for each cloud instance is less than or equal to the amount of resources included in the service resource pool for each cloud instance; According to the downgrading strategy and the downgrading resource amount of each cloud instance, a backup of the at least one cloud instance is run in the N second physical servers.

19. The device according to claim 18, characterized in that The receiving module is further used to receive downgrade information configured by the tenant, the downgrade information including a minimum downgrade ratio and / or minimum resource quantity information, the minimum downgrade ratio is used to indicate a minimum ratio of the amount of resources included in the business resource pool of the cloud instance to the amount of downgraded resources, and the minimum resource quantity information is used to indicate the minimum amount of resources included in the cloud instance; The processing module is specifically used to determine the downgraded resource amount of each cloud instance based on the downgrade information, the resource amount included in each cloud instance and the resource amount included in the N second physical servers, the ratio of the resource amount included in the business resource pool of each cloud instance to the downgraded resource amount is greater than or equal to the minimum downgrade ratio of each cloud instance, and / or the downgraded resource amount of each cloud instance is greater than or equal to the minimum resource amount of each cloud instance.

20. The device according to any one of claims 12 to 19, characterized in that The disaster recovery strategy also includes a best matching strategy, where the best matching strategy is used to indicate that the disaster recovery priority is determined according to the resource type included in the cloud instance. The processing module is specifically used to: Determining resources matched by each cloud instance according to resource types included in each cloud instance in the at least one cloud instance and resource types included in the N second physical servers; According to the best matching strategy and the resources matched by each cloud instance, a backup of the at least one cloud instance is run in the N second physical servers.

21. The device according to claim 20, characterized in that The receiving module is further used to receive resource priority information configured by the tenant, where the resource priority information is used to indicate the priority of each resource included in the cloud instance; The processing module is specifically used to determine the resources matching each cloud instance according to the resource priority information, the resource types included in each cloud instance and the resource types included in the N second physical servers, in descending order of resource priority.

22. The device according to any one of claims 12 to 21, characterized in that The processing module is further used for: Predicting the disaster recovery reliability of the disaster recovery resource pool according to the business resource pool creation request, the disaster recovery resource pool creation request and the disaster recovery strategy, wherein the disaster recovery reliability is used to indicate the ability of the N second physical servers to run a backup of at least one cloud instance that fails or is being upgraded when at least one cloud instance in any number of the first physical servers among the M first physical servers fails or is being upgraded; The disaster recovery reliability is provided to the tenant.

23. A computing device cluster, characterized in that: comprising at least one computing device, each computing device comprising a processor and a memory; The processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the method according to any one of claims 1 to 11.

24. A computer program product comprising instructions, characterized in that When the instructions are executed by a computing device cluster, the computing device cluster executes the method according to any one of claims 1 to 11.

25. A computer-readable storage medium, characterized in that: The method comprises computer program instructions, and when the computer program instructions are executed by a computing device cluster, the computing device cluster performs the method according to any one of claims 1 to 11.

Images