Fault processing method and related device

Abstract

The present application provides a fault processing method and a related device. The method is applied to a cloud management platform. The method comprises: obtaining a service resource pool creation request and a disaster recovery resource pool creation request of a tenant, and creating a service 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 when at least one cloud instance in any number of first physical servers among the M first physical servers fails or is upgraded, running, in the N second physical servers, on the basis of the disaster recovery strategy, a backup of the at least one failed or upgraded cloud instance in the M first physical servers. According to the method, when a cloud instance in a service resource pool fails or is upgraded, a backup of the cloud instance can be run in a disaster recovery resource pool on the basis of a disaster recovery strategy configured by a tenant, reducing the impact on the service of the tenant.

Description

A fault handling method and related equipment

[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 invention name “A fault handling method and related equipment”, and priority to the Chinese patent application filed with the State Intellectual Property Office of China on December 26, 2023, with application number 202311813128.5 and invention name “A fault handling method and related equipment”, the entire contents of which are incorporated by reference into 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 like 5G and the Internet of Things (IoT), and the booming development of live streaming, online education, augmented reality (AR) / virtual reality (VR), and enterprise digital transformation, cloud resources have become a preferred choice for business development across various industries. However, due to tenants' demands for data security and business independence, cloud vendors need to build independent, dedicated small resource pools for tenants. For example, they can build independent, dedicated resources or dedicated edge nodes within the public cloud. To provide tenants with highly reliable cloud services, cloud vendors typically recommend that tenants purchase a disaster recovery resource pool when they purchase a dedicated business resource pool. Both the business resource pool and the disaster recovery resource pool can include at least one physical server, each hosting one or more cloud instances for a tenant, and each cloud instance running the tenant's business. When a cloud instance running in a business resource pool fails or undergoes an upgrade, the cloud vendor will run backups of the failed or upgraded cloud instances in the disaster recovery resource pool in the order in which they occurred to ensure business reliability. The cloud instance can include virtual machines (VMs), containers, and the like. The types of resources included in the disaster recovery resource pool generally need to be consistent with those in the business resource pool, but the number of resources may differ. However, running backups of cloud instances based on the chronological order of cloud instance failures or upgrades can make it difficult to ensure timely recovery of tenants' critical services. Furthermore, if the disaster recovery resource pool contains fewer resources and the business resource pool has a large number of cloud instances experiencing failures or upgrades, tenants' services can be easily interrupted and difficult to recover.

[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.

[0005] Summary of the Invention

[0006] 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.

[0007] In a first aspect, a fault handling method is provided, which is applied to a cloud management platform for managing an infrastructure providing cloud instances, the infrastructure including at least one data center. The method includes: obtaining a business resource pool creation request from a tenant, creating a business resource pool for the tenant in an infrastructure according to the business resource pool creation request, wherein the business resource pool includes M first physical servers, each first physical server is used to carry 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 from the tenant, 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 the M first physical servers fails or is upgraded, the N second physical servers are used to run a backup of the at least one cloud instance that fails or is upgraded in the M first physical servers, 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 the disaster recovery priority of the cloud instances running on the business resource pool; when at least one cloud instance in any number of the M first physical servers fails or is upgraded, running a backup of the at least one cloud instance that fails or is upgraded in the M first physical servers in accordance with the disaster recovery policy.

[0008] 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.

[0009] 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.

[0010] In embodiments of the present application, based on the disaster recovery policy configured by the tenant, it is possible to prioritize the recovery of the tenant's critical services. Alternatively, when resources in the disaster recovery resource pool are insufficient, appropriate resources can be allocated to each cloud instance backup, thereby ensuring that as many cloud instance backups as possible are running in the disaster recovery resource pool. Alternatively, the resource configuration of the cloud instance backups in the disaster recovery resource pool can be kept consistent with the resource configuration of the cloud instance in the service resource pool, thereby minimizing the impact on the tenant's services.

[0011] In combination with the first aspect, in certain implementations of the first aspect, the disaster recovery strategy includes a priority strategy, 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 strategy, backups of at least one cloud instance are run in N second physical servers in descending order of disaster recovery priority.

[0012] In an embodiment of the present application, the cloud management platform can run a backup of at least one cloud instance in the 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.

[0013] 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 services, the backup of the second cloud instance is already 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 with the backup of the first cloud instance.

[0014] 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 lower priority to run the backup of the cloud instance with higher priority in the disaster recovery resource pool, thereby ensuring that the tenant's important business can be restored first.

[0015] 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.

[0016] 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.

[0017] 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.

[0018] 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 undergoing an upgrade based on the business priority of the cloud instance.

[0019] In combination with the first aspect, in certain implementations of the first aspect, the disaster recovery strategy also includes a downgrade strategy, which is used to indicate that the disaster recovery priority is determined based on the amount of resources included in the cloud instance, and the downgraded resource amount of each cloud instance is determined based on the amount of resources included 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; based on the downgrade 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.

[0020] 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.

[0021] In combination with the first aspect, in certain implementations of the first aspect, tenant-configured downgrade information is received, the downgrade information including a minimum downgrade ratio and / or minimum resource quantity information; and 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.

[0022] The minimum downsizing ratio indicates the minimum ratio between the amount of resources in a cloud instance's service resource pool and the amount of downgraded resources. The minimum resource quantity information indicates the minimum amount of resources in a cloud instance. The ratio of the amount of resources in the service resource pool for each cloud instance to the amount of downgraded resources is greater than or equal to the minimum downsizing ratio for each cloud instance, and / or the downgraded resource quantity for each cloud instance is greater than or equal to the minimum resource quantity for each cloud instance.

[0023] In an embodiment of the present application, tenants can configure the minimum downsizing 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 backup of the cloud instance being unable to run.

[0024] In combination with the first aspect, in certain implementations of the first aspect, the disaster recovery strategy also includes a best match strategy, which is used to indicate that the disaster recovery priority is determined based on the resource type included in the cloud instance, and the resources matching each cloud instance are determined based on 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 match strategy and the resources matching each cloud instance, a backup of at least one cloud instance is run on the N second physical servers.

[0025] 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 remain consistent, thereby avoiding affecting the operation of the backup of the cloud instance and reducing the impact on the tenant's business.

[0026] 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.

[0027] In an embodiment of the present application, tenants 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 resources, thereby further reducing the impact on the tenant's business.

[0028] 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. 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.

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

[0030] 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 tenant.

[0031] 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.

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

[0033] 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.

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

[0035] In a fifth aspect, the present application provides a computer-readable storage medium comprising 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 methods of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] FIG1 is a schematic structural diagram of a fault handling system according to an embodiment of the present application.

[0037] FIG2 is a schematic structural diagram of a fault handling system according to another embodiment of the present application.

[0038] FIG3 is a schematic flowchart of a fault handling method according to an embodiment of the present application.

[0039] FIG4 is a schematic diagram of a service resource pool and a disaster recovery resource pool according to an embodiment of the present application.

[0040] FIG5 is a schematic diagram of a first graphical interface according to an embodiment of the present application.

[0041] FIG6 is a schematic flowchart 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.

[0042] FIG7 is a schematic diagram of a second graphical interface according to an embodiment of the present application.

[0043] FIG8 is a schematic flowchart of a fault handling method according to another embodiment of the present application.

[0044] FIG9 is a schematic diagram of determining the disaster recovery priority of a cloud instance according to a priority policy according to an embodiment of the present application.

[0045] FIG10 is a schematic diagram of a third graphical interface according to an embodiment of the present application.

[0046] FIG11 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.

[0047] FIG12 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.

[0048] FIG13 is a schematic structural diagram of a fault handling device according to an embodiment of the present application.

[0049] FIG14 is a schematic structural diagram of a computing device according to an embodiment of the present application.

[0050] FIG15 is a schematic structural diagram of a computing device cluster according to an embodiment of the present application.

[0051] FIG16 is a schematic diagram illustrating a connection between computing devices 1400A and 1400B via a network according to one embodiment of the present application. DETAILED DESCRIPTION

[0052] The technical solution in this application will be described below with reference to the accompanying drawings.

[0053] 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 of the devices, components, modules, etc. discussed in conjunction with the figures. Furthermore, combinations of these solutions may also be used.

[0054] Additionally, in the embodiments of this application, words such as "exemplary" and "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" in the embodiments of this application should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of the word "exemplary" is intended to present concepts in a concrete manner.

[0055] 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 will 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.

[0056] References to "one embodiment" or "some embodiments" in this specification mean that a particular feature, structure, or characteristic described in conjunction with that embodiment is included in one or more embodiments of the present application. Thus, phrases such as "in one embodiment," "in some embodiments," "in other embodiments," and "in yet other embodiments" appearing in various places in this specification do not necessarily refer to the same embodiment, but rather mean "one or more but not all embodiments," unless otherwise specifically emphasized. The terms "including," "comprising," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0057] In the embodiments of the present application, "at least one" refers to one or more, and "more" 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 represent: 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 next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple.

[0058] The methods in the embodiments 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 of computing resources, storage resources, or network resources.

[0059] Figure 1 is a schematic structural diagram of a fault handling system 100 provided in an embodiment of the present application. The fault handling system 100 in Figure 1 includes a cloud management platform 110. The cloud management platform 110 can be used to manage the infrastructure that provides 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 of computing resources, storage resources, and network resources. A tenant can apply to use the resources in the data center 140 through the cloud management platform 110. The tenant is a tenant of a public cloud that has registered a public cloud account and purchased public cloud resources.

[0060] 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 based on 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, where 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.

[0061] 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 being different means that the two first physical servers differ in at least one of the following: 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.

[0062] The cloud management platform 110 can obtain a tenant's request to create a disaster recovery resource pool and, based on the request, create a disaster recovery resource pool 130 for the tenant in the infrastructure. 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 M first physical servers fails or undergoes an upgrade, the N second physical servers are used to run a backup of the at least one cloud instance in the M first physical servers that failed or is undergoing an upgrade, where N is a positive integer greater than 0 and less than or equal to M.

[0063] In some embodiments, the cloud instance failure or upgrade may be caused by the cloud instance itself failing or being upgraded. Alternatively, the cloud instance failure or upgrade may be caused by the first physical server where the cloud instance is located failing or being upgraded.

[0064] 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). 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 resume operation, thereby reducing the impact on the tenant's business.

[0065] 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 service 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.

[0066] When the cloud instances in business resource pool 120 are not failing or being upgraded, the N second physical servers in disaster recovery resource pool 130 may not be running. Therefore, tenants are generally configured so that the amount of resources included in disaster recovery resource pool 130 is less than the amount of resources included in business resource pool 120. However, if a cloud instance in business resource pool 120 fails or is upgraded, if the amount of resources included in disaster recovery resource pool 130 is less than the amount of resources included in the failed or upgraded cloud instance in business resource pool 120, the backups of some of the tenant's cloud instances will not be able to run in disaster recovery resource pool 130, which may easily cause a significant impact on the tenant's business. Therefore, cloud management platform 110 can provide tenants with at least one disaster recovery policy, so that according to the tenant's configured disaster recovery policy, a backup of at least one cloud instance can be run on 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 ensuring that the resources allocated to cloud instances before and after migration remain consistent as much as possible, thereby reducing the impact on the tenant's business.

[0067] The cloud management platform 110 may receive a disaster recovery policy configured by a tenant, which indicates the disaster recovery priority of the cloud instances running on the service resource pool 120. If at least one cloud instance in any number of the M first physical servers fails or is undergoing an upgrade, a backup of the at least one cloud instance in the M first physical servers that has failed or is undergoing an upgrade is run on the N second physical servers according to the disaster recovery policy.

[0068] 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.

[0069] 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.

[0070] Optionally, the cloud management platform 110 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 policy. This disaster recovery reliability indicates the ability of the N second physical servers to run a backup of the at least one failed or upgraded cloud instance if at least one cloud instance in any number of the M first physical servers fails or undergoes an upgrade. The cloud management platform 110 can also provide this disaster recovery reliability to tenants, thereby providing guidance for them in configuring resources and disaster recovery policies included in the disaster recovery resource pool.

[0071] Figure 2 is another schematic structural diagram of the fault handling system provided in an embodiment of the present application. The fault handling system 200 in Figure 2 includes a cloud management platform 210. The cloud management platform 210 can manage the infrastructure for providing cloud instances, which infrastructure includes at least one data center (for example, a 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 based on the tenant's request. The business resource pool 220 is similar to the business resource pool 120 in Figure 1, and the disaster recovery resource pool 230 is similar to the disaster recovery resource pool 130 in Figure 1, which will not be repeated here. The cloud management platform 210 may include a disaster recovery policy 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.

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

[0073] In some embodiments, the disaster recovery priority is determined based on 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.

[0074] 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 .

[0075] In some embodiments, the disaster recovery strategy configuration component 211 may also receive downgrade information configured by the tenant, which includes a minimum downgrade ratio and / or minimum resource quantity information. The minimum downgrade ratio indicates the minimum ratio between the amount of resources included in the service resource pool 220 of the cloud instance and the amount of downgraded resources. The minimum resource quantity information indicates the minimum amount of resources included in the cloud instance.

[0076] 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.

[0077] 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.

[0078] In some embodiments, the disaster recovery pool selection component 212 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 policy configured by the tenant. This disaster recovery reliability is used to indicate the ability of the N second physical servers to run a backup of the at least one cloud instance that failed or was upgraded in the event that 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 this disaster recovery reliability to the tenant, thereby assisting the tenant in creating a disaster recovery resource pool 230 with appropriate resources and configuring an appropriate disaster recovery policy.

[0079] Disaster recovery resource monitoring component 213 can monitor the operation of the first physical server in business resource pool 220 and can also monitor the usage of resources in business resource pool 220 and / or disaster recovery resource pool 230. The resource usage can include the resource's used capacity and / or remaining capacity. Disaster recovery resource monitoring component 213 can also notify disaster recovery scheduling component 214 when it detects that at least one cloud instance in business resource pool 220 has failed or is undergoing an upgrade.

[0080] When the disaster recovery resource monitoring component 213 detects that at least one cloud instance in the service resource pool 220 has failed or is undergoing an upgrade, the disaster recovery scheduling component 214 can determine the disaster recovery priority of each cloud instance in the at least one cloud instance in the service resource pool 220 that has failed or is undergoing an upgrade based on the disaster recovery policy 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.

[0081] 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.

[0082] 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.

[0083] 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 service resource pool 220 and interrupt the backup operation of the at least one cloud instance in the N second physical servers.

[0084] When at least one cloud instance in the business resource pool fails or undergoes an upgrade, the fault handling system in Figures 1 and 2 can, based on the disaster recovery policy configured by the tenant, run a backup of the failed or upgraded cloud instance in the disaster recovery resource pool, thereby reducing the impact on the tenant's business. The fault handling system can ensure that the tenant's important business is restored first based on the disaster recovery policy configured by the tenant, or, when resources in the disaster recovery resource pool are insufficient, allocate appropriate resources to each backup of a cloud instance, thereby running as many backups of cloud instances as possible in the disaster recovery resource pool, or ensure that the resource configuration of the cloud instance backups in the disaster recovery resource pool is 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.

[0085] Figure 3 is a schematic flow chart of a fault handling method provided in an embodiment of the present application. The method in Figure 3 can be executed by the cloud management platform in Figure 1 or Figure 2. The method in Figure 3 includes the following steps.

[0086] S310 , obtaining a business resource pool creation request from a tenant, and creating a business resource pool for the tenant in the infrastructure according to the business resource pool creation request.

[0087] The cloud management platform can receive a tenant's service resource pool creation request, which is used to request the creation of a service resource pool. Based on the service resource pool request, the cloud management platform can also create a service resource pool for the tenant in an infrastructure managed by the cloud management platform. The infrastructure may include at least one data center.

[0088] 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 resource type includes at least one of the following: computing resources, storage resources, and network resources.

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

[0090] 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.

[0091] Optionally, the cloud management platform can create a service resource pool for a tenant that includes M first physical servers, 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 instances can be virtual machines or containers, etc. Each cloud instance can be used to run at least one service of the tenant.

[0092] S320: Obtain a disaster recovery resource pool creation request from the tenant, and create a disaster recovery resource pool for the tenant in the infrastructure according to the disaster recovery resource pool creation request.

[0093] The cloud management platform can obtain a 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 based on the disaster recovery resource pool request.

[0094] 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 resource type includes at least one of the following: computing resources, storage resources, and network resources.

[0095] Optionally, the tenant may determine the quantity and / or type of resources required in the disaster recovery resource pool based on the operational requirements of the tenant's business and the costs required for various resources.

[0096] 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.

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

[0098] For example, the resources included in the disaster recovery resource pool requested by the tenant can be as shown in Figure 4. Figure 4 is a schematic diagram of the business resource pool and disaster recovery resource pool requested by the tenant provided in an embodiment of the present application. As shown in Figure 4, the tenant can create a business resource pool 410 including four physical servers according to business needs, 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 means that the type and quantity of the resources are the same. Different resources means that the type and / or quantity of the 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.

[0099] As shown in Figure 4, based on the resources included in business resource pool 410, the disaster recovery resource pool requested by a tenant can be any of disaster recovery resource pools 420, 430, or 440. 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 disaster recovery resource pool 420 are the same as those included in business resource pool 410. Even if all cloud instances running in business resource pool 410 fail or are undergoing an upgrade, disaster recovery resource pool 420 can still run backups of all cloud instances. However, disaster recovery resource pool 420 is expensive, and if no cloud instances running in business resource pool 410 fail or are not undergoing an upgrade, or if only a few cloud instances fail or are undergoing an upgrade, resource waste can occur. Disaster recovery resource pool 430 includes Type A and Type B physical servers, while disaster recovery resource pool 440 includes only Type A physical servers. That is, the amount of resources included in disaster recovery resource pool 430 and disaster recovery resource pool 440 is less than the amount of resources included in business resource pool 410. Disaster recovery resource pool 430 or disaster recovery resource pool 440 requires a lower cost, but if a large number of cloud instances in business resource pool 410 have failed or are undergoing upgrades, it may not be possible to run backups of all failed or upgraded cloud instances in the disaster recovery resource pool, or the amount of resources included in some cloud instances may need to be reduced to ensure that business is not interrupted.

[0100] S330: Receive the disaster recovery policy configured by the tenant.

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

[0102] In some embodiments, the disaster recovery priority is determined based on 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.

[0103] 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.

[0104] 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 policy configuration information on the first graphical interface.

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

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

[0107] It should be understood that the first graphical interface is only an example, and the cloud management platform may provide tenants with other graphical interfaces so that tenants can select or upload disaster recovery strategy configuration information in the graphical interface.

[0108] When tenants need to prioritize the recovery of critical services, they can select a priority policy and / or a preemption policy. The priority policy indicates that the disaster recovery priority of a cloud instance is determined based on its service priority. When the service priority of a cloud instance is high, the disaster recovery priority of that cloud instance is high. When the service priority of a cloud instance is low, the disaster recovery priority of that cloud instance is low. Based on the priority policy, the cloud management platform can sequentially run backups of at least one cloud instance that has failed or is undergoing an upgrade in the disaster recovery resource pool, in descending order of disaster recovery priority.

[0109] 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 that the service 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 on the N second physical servers, while the backup of the second cloud instance is running on 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 have experienced failures or are undergoing upgrades. Based on 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.

[0110] In some embodiments, the priority of the first cloud instance can be higher than a preset priority, while the priority of the second cloud instance can be lower than or equal to the preset priority. That is, cloud instances with higher priorities can forcibly occupy resources from cloud instances with lower priorities, thereby allowing backups of higher-priority cloud instances to run preferentially in the disaster recovery resource pool. The preset priority can be determined by the cloud management platform or configured by the tenant.

[0111] When a tenant needs to ensure that as many services as possible are restored, the tenant can choose a downgrade strategy. This downgrade strategy is used to indicate that the disaster recovery priority of a cloud instance is determined based on the amount of resources included in the cloud instance. For example, the cloud management platform can determine the amount of downgraded resources for each cloud instance based on the amount of resources included in each cloud instance that has failed or is undergoing an upgrade and the amount of resources included in the disaster recovery resource pool. Based on the downgrade strategy and the amount of downgraded resources for each cloud instance, the tenant can run a backup of at least one cloud instance in the disaster recovery resource pool. The downgraded amount of resources for each cloud instance is less than or equal to the amount of resources included in the business resource pool for each cloud instance. In other words, 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.

[0112] In some embodiments, the cloud management platform can 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 of the cloud instance 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. 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 can be determined by the cloud management platform itself, or can be configured by the tenant.

[0113] When a tenant needs to ensure that the resource configuration of the cloud instance where the business is located remains 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 types 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, and thus run the backup of at least one cloud instance in the disaster recovery resource pool based on the best matching strategy and the resources matched to 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 cloud instance backup 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.

[0114] In some embodiments, the cloud management platform can determine the resource types that are prioritized based on resource priorities, thereby determining the resources 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. The resource priority can be determined by the cloud management platform itself or configured by the tenant.

[0115] When tenants need to quickly recover services after a failure or upgrade, they can choose a sequential disaster recovery strategy. This strategy prioritizes the recovery of cloud instances based on the order in which they fail or are upgraded. For example, the cloud management platform might prioritize backups of cloud instances that fail or are upgraded first in the disaster recovery resource pool, while backups of cloud instances that fail or are upgraded later are prioritized in the disaster recovery resource pool.

[0116] 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 policy configured by the tenant. This disaster recovery reliability indicates the ability of the N second physical servers to run a backup of the at least one failed or upgraded cloud instance if at least one cloud instance in any number of the M first physical servers fails or undergoes an upgrade. The cloud management platform can also provide this disaster recovery reliability to tenants, thereby assisting them in creating a disaster recovery resource pool with appropriate resources and configuring an appropriate disaster recovery policy.

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

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

[0119] Optionally, the cloud management platform may determine, based on the disaster recovery policy, a disaster recovery priority for each of the at least one cloud instance experiencing a failure or undergoing an upgrade. The cloud management platform may also sequentially run a backup of the at least one cloud instance on the N second physical servers based on the disaster recovery priority of each cloud instance.

[0120] 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, thereby running the backup of each cloud instance in the resources allocated to the backup of the cloud instance.

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

[0122] In some embodiments, the resource configuration of a cloud instance experiencing a failure or undergoing an upgrade in the service resource pool may differ from the resource configuration of its backup in the disaster recovery resource pool. However, after the cloud instance recovers or completes the upgrade, the resource configuration of the cloud instance in the service resource pool remains the same as it was before the failure or upgrade. This resource configuration includes the type and quantity of resources.

[0123] In an embodiment of the present application, when at least one cloud instance in a business resource pool fails or is being upgraded, a backup of the failed or upgraded cloud instance can be run in the disaster recovery resource pool according to the disaster recovery policy 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 policy 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, thereby running 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.

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

[0125] 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 policy.

[0126] The disaster recovery reliability of the disaster recovery resource pool indicates the ability of the disaster recovery resource pool to run a backup of at least one cloud instance that failed or was undergoing an upgrade, if at least one cloud instance on any number of first physical servers in the business resource pool fails or is undergoing an upgrade. 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 also includes N second physical servers.

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

[0128] Optionally, the cloud management platform can input the resources included in the business resource pool and disaster recovery resource pool requested by the tenant, as well as the disaster recovery policy configured by the tenant, into a reliability prediction model to predict the disaster recovery reliability of the disaster recovery resource pool. This reliability prediction model can be used to predict the duration required to run a backup of at least one cloud instance in the disaster recovery resource pool when the at least one cloud instance running in the business resource pool fails or undergoes an upgrade.

[0129] 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 backups of cloud instances in the disaster recovery resource pool according to the disaster recovery policy, the more backups of cloud instances that can be run, the stronger the disaster recovery reliability of the disaster recovery resource pool. When running backups of cloud instances in the disaster recovery resource pool according to the disaster recovery policy, the fewer backups of cloud instances that can be run, the weaker the disaster recovery reliability of the disaster recovery resource pool.

[0130] Optionally, the cloud management platform may provide the tenant with a second graphical interface, 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 policy.

[0131] For example, the second graphical interface that the cloud management platform can provide is shown in Figure 7. Figure 7 is a schematic diagram of the second graphical interface 700 provided in an embodiment of the present application. As shown in the second graphical interface 700 in Figure 7, 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 device 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 device 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".

[0132] As shown in the second graphical interface 700 in FIG7 , 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 device that carries the resources in the selection box or input box corresponding to "Type" in the "Disaster Recovery Resource Pool Resource Configuration" section. The tenant can also select or enter the quantity of each resource or each device included in the disaster recovery resource pool requested to be created in the selection box or input box corresponding to "Purchase Quantity" in the "Disaster Recovery Resource Pool Resource Configuration" section.

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

[0134] For example, 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.

[0135] For example, the tenant may also select or upload a disaster recovery strategy in the second graphical interface 700. The operations for 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 here.

[0136] S620: Provide disaster recovery reliability to the tenant to assist the tenant in determining a disaster recovery strategy and resources included in a disaster recovery resource pool.

[0137] The cloud management platform can predict the disaster recovery reliability of the disaster recovery resource pool and provide this reliability to the tenant in real time. For example, the cloud management platform can display the disaster recovery reliability of the disaster recovery resource pool as 99.9% in real time in the second graphical interface 700. The tenant can adjust the resource configuration and / or disaster recovery strategy of the disaster recovery resource pool based on the disaster recovery reliability provided by the cloud management platform to determine a disaster recovery resource pool containing appropriate resources and / or an appropriate disaster recovery strategy.

[0138] 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.

[0139] Figure 8 is a schematic flow chart of a fault handling method provided by an embodiment of the present application. The method in Figure 8 can be executed by the cloud management platform in Figure 1 or Figure 2. Figure 8 includes the following steps.

[0140] S810: Determine a disaster recovery priority of at least one cloud instance according to at least one of a priority policy, a preemption policy, a downgrade policy, a best match policy, and a sequential disaster recovery policy.

[0141] Optionally, the cloud management platform can determine the disaster recovery priority of at least one cloud instance based on a priority policy. The priority policy is used to indicate that the disaster recovery priority of a cloud instance is determined based on the service priority of the cloud instance. For example, the cloud management platform can determine that 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 the cloud instance is lower, the disaster recovery priority of the cloud instance is lower, as shown in Figure 9.

[0142] Figure 9 is a schematic diagram of determining the disaster recovery priority of a cloud instance according to a priority policy provided in accordance with an embodiment of the present application. The business resource pool 910 in Figure 9 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 priority of cloud instance 1, cloud instance 2, and cloud instance 4 is high, and the business priority of cloud instance 3, cloud instance 5, and cloud instance 6 is 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 the disaster recovery priority of cloud instance 3, cloud instance 5, and cloud instance 6.

[0143] Assuming that disaster recovery resource pool 920 in FIG9 includes only one second physical server 921, and the resources in second physical server 921 can only host three cloud instances, the cloud management platform can run backups of cloud instances 1, 2, and 4 on second physical server 921. The amount of resources included in the backup of cloud instance 1 on second physical server 921 is the same as the amount of resources included in first physical server 911, and / or the types of resources included in the backup of cloud instance 1 on second physical server 921 are the same as the types of resources included in first physical server 911. Similarly, the amount of resources included in the backup of cloud instance 2 on second physical server 921 is the same as the amount of resources included in first physical server 911, and / or the types of resources included in the backup of cloud instance 2 on second physical server 921 are the same as the types of resources included in 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.

[0144] Optionally, the cloud management platform can receive tenant-configured priority information. This priority information is used to indicate the service priority of the cloud instance running on the service resource pool. Alternatively, this priority information can be used to indicate the priority of each of one or more services of the tenant. The priority of each cloud instance can be determined based on the priority of at least one service running in each cloud instance.

[0145] 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.

[0146] For example, the third graphical interface that the cloud management platform may provide is shown in Figure 10. Figure 10 is a schematic diagram of the third graphical interface provided in an embodiment of the present application. Figure 10 includes a third graphical interface 1010 and a third graphical interface 1020.

[0147] As shown in third graphical interface 1010 in Figure 10 , tenants can select and enter "Cloud Instance ID" and "Priority" in this third graphical interface 1010 to determine the service priority of each cloud instance. In the selection box or input box corresponding to "Cloud Instance ID," you can select or enter the cloud instance's identification information, and in the selection box or input box corresponding to "Priority," you can select or enter the service priority of the corresponding cloud instance. A tenant can configure the service priority of cloud instance 1 to be high and the service priority of cloud instance 3 to be low.

[0148] As shown in the third graphical interface 1020 in Figure 10, tenants can select and input the three items "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 "Business ID", the identification information of the business can be selected or input. In the selection box or input box corresponding to "Cloud Instance ID", the identification information of the cloud instance where each business is located can be selected or input. In the selection box or input box corresponding to "Priority", the priority of each business can be selected or input. The tenant can configure the priority of business 1 to be high and the priority of business 2 to be low.

[0149] When only one service is running in a cloud instance, the priority of the cloud instance can be determined based on 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.

[0150] For example, suppose cloud instance 1 runs services 1, 2, and 3, with service 1 having a high priority and services 2 and 3 having a low priority. The service priority of cloud instance 1 can be the highest among the priorities of services 1, 2, and 3, that is, the service priority of cloud instance 1 can be high. Alternatively, the service priority of cloud instance 1 can be the highest among the priorities of services 1, 2, and 3, that is, the service priority of cloud instance 1 can be low.

[0151] Optionally, the cloud management platform can 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 according to 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 the disaster recovery priority 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, and the backup of the second cloud instance is already running in the disaster recovery resource pool. 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 can 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, as shown in Figure 11.

[0152] Figure 11 is a schematic diagram of determining the disaster recovery priority of a cloud instance according to a coercive strategy provided in accordance with an embodiment of the present application. Figure 11 includes a business resource pool 910 and a disaster recovery resource pool 920, and the business resource pool 910 and the disaster recovery resource pool 920 are configured the same as in Figure 9. After cloud instance 1, cloud instance 2, and cloud instance 3 in the 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 the disaster recovery resource pool 920. After the backups of cloud instance 1, cloud instance 2, and cloud instance 3 run in the disaster recovery resource pool 920, if cloud instance 4, cloud instance 5, and cloud instance 6 also fail. Since the business priority of cloud instance 1, cloud instance 2, and cloud instance 4 is high, the business priority of cloud instance 3, cloud instance 5, and cloud instance 6 is 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 that of cloud instance 3, and thus replace the backup of cloud instance 3 running in disaster recovery resource pool 920 with the backup of cloud instance 4. In other words, 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 on the second physical server 921.

[0153] 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 the cloud instance can continue to run its business when it resumes operation in the business resource pool.

[0154] 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.

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

[0156] When the tenant does not configure a priority for a service or cloud instance, the tenant can configure a preemption flag for the service and / or cloud instance. When the tenant configures a preemption flag for a service, the cloud instance running the service can also be configured with a preemption 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 preemption flag and the preemption policy. The third cloud instance does not have a preemption flag, or each service running in the third cloud instance does not have a preemption flag. The fourth cloud instance is configured with a preemption flag, or at least one service running in the fourth cloud instance is configured with a preemption flag. The third cloud instance and the fourth cloud instance are different cloud instances in the service resource pool that have experienced a failure or are undergoing an upgrade.

[0157] Optionally, the cloud management platform can determine the disaster recovery priority of at least one cloud instance based on a downsizing policy. The downsizing policy indicates that the disaster recovery priority of a cloud instance is determined based on the resource volume of the cloud instance. For example, the cloud management platform can determine the downgraded resource volume for each cloud instance based on the resource volume of each cloud instance that has experienced a failure or is undergoing an upgrade and the resource volume in the disaster recovery resource pool. Based on the downsizing policy and the downgraded resource volume of each cloud instance, the cloud management platform runs a backup of each cloud instance in the disaster recovery resource pool, as shown in Figure 12. The downgraded resource volume of each cloud instance is less than or equal to the resource volume of each cloud instance in the service resource pool.

[0158] In some embodiments, the ratio of the amount of resources included in the service resource pool to the amount of deprovisioned resources for each cloud instance in the multiple cloud instances may be the same or different.

[0159] Figure 12 is a schematic diagram of determining the disaster recovery priority of a cloud instance according to a downgrade strategy provided in accordance with an embodiment of the present application. Figure 12 includes a business resource pool 910 and a disaster recovery resource pool 920, and the business resource pool 910 and the disaster recovery resource pool 920 are configured the same as in Figure 9. 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 through 6 in service resource pool 910 fail, the cloud management platform can determine, based on the resource allocations of cloud instances 1 through 6 and the resource allocations of second physical server 921, that the amount of resources to be reduced for each cloud instance is 12U24G / 6 = 2U4G. That is, the cloud management platform can allocate 2U4G of resources from second physical server 921 to the backup of each cloud instance 1 through 6. The ratio of the amount of resources in the service resource pool to the amount of resources to be reduced for each cloud instance 1 through 6 is 4U8G:2U4G = 2:1. The cloud management platform can also run the backup of each cloud instance within the resources allocated to its backup. In other words, based on the reduction policy, the cloud management platform can determine to run the backup of each cloud instance 1 through 6 on second physical server 921, but the amount of resources included in the disaster recovery resource pool 920 for each cloud instance's backup is less than the amount of resources included in the service resource pool 910 for each cloud instance.

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

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

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

[0163] In some embodiments, the cloud management platform may determine the amount of resources to be downgraded 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 of the cloud instance 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. The downgrade ratio value of each cloud instance is greater than or equal to the minimum downgrade ratio value of each cloud instance, and / or the amount of resources to be downgraded for each cloud instance is greater than or equal to the minimum amount of resources for each cloud instance. The downgrade ratio value of a 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.

[0164] 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.

[0165] For example, assume that cloud instances 1 through 6 each include 4U8G resources in the service resource pool and 12U24G resources in the disaster recovery resource pool. If the minimum downsizing ratio for cloud instances 1 and 2 is 1:1, the cloud management platform can determine that the downsizing resources for cloud instances 1 and 2 are 4U8G, respectively, based on the minimum downsizing ratio, the resource amounts included in the service resource pool for cloud instances 1 and 2, and the resource amounts included in the disaster recovery resource pool. The downsizing ratio for cloud instances 1 and 2 is 1:1, and the downsizing ratio for cloud instance 1 is greater than or equal to the minimum downsizing ratio for cloud instance 1, and the downsizing ratio for cloud instance 2 is greater than or equal to the minimum downsizing ratio for cloud instance 2. Assuming that cloud instances 3 to 6 are not configured with a minimum downsizing ratio, the cloud management platform can also determine the downsizing resource amount of cloud instances 3 to 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 instances 3 to 6.

[0166] 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.

[0167] For example, assume that cloud instances 1 through 6 each include 4U8G of resources in the business resource pool and 12U24G of resources in the disaster recovery resource pool. If the minimum resource amount included in cloud instance 1 and cloud instance 2 is both 4U8G, the cloud management platform can determine that the reduced resource amount for cloud instance 1 and cloud instance 2 is both 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 through 6 are not configured with the minimum resource amount, the cloud management platform can determine that the reduced resource amount for cloud instances 3 through 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 through 6.

[0168] Optionally, the cloud management platform may provide the tenant with a fourth graphical interface, 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.

[0169] Optionally, the cloud management platform can determine the disaster recovery priority of at least one cloud instance based on a best-match strategy. The best-match strategy indicates that the disaster recovery priority of a cloud instance is determined based on the resource types included in the cloud instance. For example, the cloud management platform can determine the matching resources for each cloud instance based on the resource types included in each cloud instance that has experienced a failure or is undergoing an upgrade and the resource types included in the disaster recovery resource pool. Based on the best-match strategy and the matching resources for each cloud instance, the cloud management platform can run a backup of each cloud instance in the disaster recovery resource pool.

[0170] For example, assume that cloud instance 1 includes 4U8G of graphics processing unit (GPU) computing resources and fourth-generation dynamic random access memory (double data rate 4, DDR4) storage resources in its business resource pool, and cloud instance 2 includes 4U6G of central processing unit (CPU) computing resources and third-generation dynamic random access memory (double data rate 3, DDR3) storage resources in its business resource pool. Assuming that both cloud instance 1 and cloud instance 2 fail, and the disaster recovery resource pool includes 4U10G of GPU computing resources and DDR4 storage resources, and 4U6G of 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 pools of cloud instance 1 and cloud instance 2, respectively, and thus allocate 4U8G of GPU computing resources and DDR4 storage resources in the disaster recovery resource pool to the backup of cloud instance 1, and allocate 4U6G of CPU computing resources and DDR3 storage resources in the disaster recovery resource pool to 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.

[0171] In some embodiments, the cloud management platform can determine the priority of each resource based on resource priority information. Thus, the cloud management platform determines the resources that match each cloud instance based on the resource priority information, the resource type of each cloud instance, and the resource types included in the disaster recovery resource pool, in descending order of resource priority. This resource priority information indicates the priority of each resource included in the cloud instance. This resource priority information can be determined independently by the cloud management platform or configured by the tenant.

[0172] For example, assume that cloud instance 1 includes 4U8G of GPU computing resources and DDR4 storage resources in its business resource pool, cloud instance 2 includes 4U8G of CPU computing resources and DDR4 storage resources in its business resource pool, and cloud instance 3 includes 4U8G of CPU computing resources and DDR3 storage resources in its 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 in the disaster recovery resource pool to the backup of cloud instance 1, 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 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.

[0173] 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 prioritize cloud instance 3 as the cloud instance that matches the type of storage resources included in the disaster recovery resource pool, thereby allocating 4U8G of GPU computing resources and DDR3 storage resources in the disaster recovery resource pool to the backup of cloud instance 3, 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 in the disaster recovery resource pool to the backup of cloud instance 1, and then running the backup of cloud instance 1.

[0174] Optionally, the cloud management platform may provide the tenant with a fifth graphical interface, so that the tenant can 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.

[0175] Optionally, the cloud management platform may determine the disaster recovery priority of at least one cloud instance based on a sequential disaster recovery policy. This sequential disaster recovery policy indicates that the disaster recovery priority of cloud instances is determined based on the chronological order in which cloud instance failures or upgrades occur. For example, if cloud instance 1 fails earlier than cloud instance 2, the cloud management platform may determine that the disaster recovery priority of cloud instance 1 is higher than that of cloud instance 2.

[0176] When the disaster recovery policy configuration information includes multiple disaster recovery policies, the cloud management platform may determine the disaster recovery priority of at least one cloud instance that has failed or is undergoing an upgrade based on the multiple disaster recovery policies.

[0177] For example, assuming that the disaster recovery policy configuration information includes a priority policy and a preemption policy, when the disaster recovery resource pool includes unallocated resources or a large number of unallocated resources, the cloud management platform can determine the disaster recovery priority of at least one cloud instance that has failed or is undergoing an upgrade based on the priority policy. When there are no unallocated resources or a small number of 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 policy. The large number of unallocated resources means that the amount of unallocated resources is greater than a preset threshold, and the small number of 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.

[0178] For example, assuming the disaster recovery policy configuration information includes a priority policy and a downsizing policy, the cloud management platform can determine the disaster recovery priority of each cloud instance based on the priority policy. If the sum of the resource amounts of the higher-priority cloud instances exceeds the resource amount in the disaster recovery resource pool, the cloud management platform can further determine the downsizing resource amount for each higher-priority cloud instance based on the downsizing policy, thereby running the backup of each higher-priority cloud instance in the disaster recovery resource pool. The resource amount included in the disaster recovery resource pool for the backup of each higher-priority cloud instance is the downsizing resource amount for that cloud instance. The higher-priority cloud instance can be a cloud instance with a priority higher than a preset priority. If the sum of the resource amounts of the higher-priority cloud instances is less than the resource amount in the disaster recovery resource pool, the cloud management platform can further determine the downsizing resource amount for at least one lower-priority cloud instance based on the downsizing policy, thereby running the backup of each higher-priority cloud instance and the backup of at least one lower-priority cloud instance in the disaster recovery resource pool. The resource amount included in the service resource pool for each higher-priority cloud instance and the resource amount included in the disaster recovery resource pool for its backup are the same. The amount of resources included in the disaster recovery resource pool for the backup of each lower-priority cloud instance is the reduced-configuration resource amount of the cloud instance. The lower-priority cloud instance may be a cloud instance with a priority lower than or equal to a preset priority.

[0179] For example, assuming 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 for each cloud instance based on the priority policy. Furthermore, based on the best-match policy, the cloud management platform can prioritize the allocation of resources matching the cloud instance in the disaster recovery resource pool to the backup of each cloud instance with a higher priority, thereby enabling the operation of at least one backup of the cloud instance.

[0180] 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 downgraded amount of resources for the first cloud instance based on 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 based on 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 based on the coercion policy.

[0181] For example, assuming the disaster recovery policy configuration information includes a preemption policy and a best match policy, the cloud management platform can, when replacing the backup of at least one second cloud instance with the backup of at least one first cloud instance according to the preemption policy, allocate matching resources to one or more backups of the first cloud instance in the at least one first cloud instance, 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 experiences a failure or undergoes an upgrade, the cloud management platform can, according to the preemption policy, run the backups of one or more cloud instances in the disaster recovery resource pool.

[0182] For example, assuming the disaster recovery policy configuration information includes a downgrade policy and a downgrade policy. The cloud management platform can prioritize allocating resources to backups of cloud instances that match the resource types included in the disaster recovery resource pool based on 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, based on the best match policy, one or more cloud instances that match the resource types included in the disaster recovery resource pool and run the backups of these one or more cloud instances. Then, based on the downgrade policy, the cloud management platform can determine the downgraded resource amount for one or more cloud instances that do not match the resource types included in the disaster recovery resource pool, thereby running the backups of these one or more cloud instances.

[0183] For example, assuming the disaster recovery policy configuration information includes a priority policy, a preemption policy, and a downgrade policy, the cloud management platform can first determine the disaster recovery priority of at least one cloud instance based on descending priority. If resources in the disaster recovery resource pool are insufficient to continue allocating to the cloud instance, the cloud management platform can run a backup of the at least one cloud instance in the disaster recovery resource pool based on the preemption policy and / or the downgrade policy.

[0184] For example, assume that the disaster recovery policy configuration information includes a priority policy, a preemption policy, and a best match policy. The cloud management platform can first determine the disaster recovery priority of at least one cloud instance based on descending priority. The cloud management platform can also allocate matching resources to higher-priority cloud instances based on the best match policy. If resources in the disaster recovery resource pool are insufficient to allocate to the cloud instance, the cloud management platform can use the preemption policy to run a backup of at least one cloud instance in the disaster recovery resource pool.

[0185] When a conflict or inconsistency occurs in the disaster recovery priorities of at least one cloud instance determined by the cloud management platform based on multiple disaster recovery policies, the cloud management platform can determine the disaster recovery priority of the at least one cloud instance based on the policy priority information and the multiple disaster recovery policies. The policy priority information indicates the priority of each of the at least one disaster recovery policies. For example, the cloud management platform can determine the disaster recovery priority of the at least one cloud instance based on the policy priority information and the multiple disaster recovery policies in descending order of priority.

[0186] In some embodiments, the cloud management platform may provide a sixth graphical interface for tenants, so that tenants 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.

[0187] 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.

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

[0189] In an embodiment of the present application, when at least one cloud instance in a business resource pool fails or is being upgraded, a backup of the failed or upgraded cloud instance can be run in the disaster recovery resource pool according to the disaster recovery policy 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 policy 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, thereby running 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.

[0190] FIG13 is a schematic diagram of a fault handling device according to an embodiment of the present application. The fault handling device 1300 in FIG13 includes a receiving module 1310 and a processing module 1320. The fault handling device 1300 in FIG13 can be applied to a cloud management platform, such as the cloud management platform 110 in FIG1 or the cloud management platform 210 in FIG2.

[0191] 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 based on the business resource pool creation request. The business resource pool includes M first physical servers, each first physical server 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 based on 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 policy configured by the tenant. The receiving module 1310 can be used to execute steps S310, S320, and S330 in Figure 3.

[0192] Processing module 1320 can be configured to, when at least one cloud instance in any number of the M first physical servers fails or undergoes an upgrade, run a backup of the at least one cloud instance in the M first physical servers that failed or is undergoing an upgrade on the N second physical servers according to a disaster recovery strategy. Processing module 1320 can execute step S340 in FIG. 3 , steps S610 and S620 in FIG. 6 , and steps S810 and S820 in FIG. 8 .

[0193] The receiving module 1310 and the processing module 1320 can be implemented by software or hardware. For example, the implementation of the receiving module 1310 will be described below using 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.

[0194] As an example of a software functional unit, the receiving module 1310 may include code running on a computing instance. The computing instance may include at least one of a physical host (computing device), a virtual machine, and a container. Furthermore, the 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 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 one data center or multiple geographically close data centers. Typically, a region may include multiple AZs.

[0195] Similarly, multiple hosts / virtual machines / containers running the code can be distributed within the same VPC or across multiple VPCs. Typically, a VPC is set up within a region. Cross-region communication between two VPCs within the same region, or between VPCs in different regions, requires a communication gateway within each VPC to interconnect the VPCs.

[0196] As an example of a hardware functional unit, receiving module 1310 may include at least one computing device, such as a server. Alternatively, receiving module 1310 may be 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.

[0197] 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 servers, ASICs, PLDs, CPLDs, FPGAs, GALs, and other computing devices.

[0198] Therefore, the modules of each example described in the embodiments of this 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. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0199] 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 application, 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 the full 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.

[0200] 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 and will not be repeated here.

[0201] 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 the function and structure of the hardware are subsequently 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. Furthermore, optionally, the computer system is a handheld device such as a smart phone, or a terminal device such as a personal computer, and this application is not particularly limited, as long as the method provided in 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.

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

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

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

[0205] 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.

[0206] 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, only one thick line is used in Figure 14, but this does not mean that there is only one bus or one type of bus.

[0207] In one possible implementation, the processor 1410 is primarily responsible for interpreting computer program instructions (or codes) and processing data in the computer software. The computer program instructions and the data in the computer software may be stored in the memory 1420 or the cache of the processor 1410.

[0208] Optionally, processor 1410 may be an integrated circuit chip with signal processing capabilities. By way of example and not limitation, 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. A general-purpose processor is a microprocessor, for example. For example, processor 1410 is a central processing unit (CPU).

[0209] Memory 1420 can provide runtime space for processes in computing device 1400. For example, memory 1420 stores computer programs (specifically, program code) used to generate processes. After the computer program is executed by the processor to generate a process, the processor allocates corresponding storage space for the process in memory 1420. Furthermore, the aforementioned storage space further includes a text segment, an initialized data segment, a bit-initialized data segment, a stack segment, a heap segment, and the like. Memory 1420 stores data generated during the execution of the aforementioned processes, such as intermediate data or process data, in the storage space corresponding to the aforementioned processes.

[0210] Alternatively, the memory is also referred to as the internal memory. It is used to temporarily store data being processed by the processor 1410, as well as data exchanged with external storage devices such as a hard disk. As long as the computer is running, the processor 1410 will load the data to be processed into the internal memory for processing, and then transmit the results after the calculations are completed.

[0211] By way of example and not limitation, memory 1420 is a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile storage medium may be, for example, a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (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.

[0212] 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 in addition to 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 to achieve 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 that implement 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 all the devices shown in Figure 14.

[0213] 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 smartphone.

[0214] As shown in Figure 15, 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.

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

[0216] It should be noted that the memory 1420 in different computing devices 1400 in the computing device cluster can store different instructions, each for performing part of the functions of the above-mentioned apparatus. In other words, the instructions stored in the memory 1420 in different computing devices 1400 can implement the functions of one or more modules in the above-mentioned apparatus.

[0217] In some possible implementations, one or more computing devices in a computing device cluster can be connected via a network. The network can be a wide area network (WAN) or a local area network (LAN), among others. FIG. 16 illustrates one possible implementation. As shown in FIG. 16 , two computing devices 1400A and 1400B are connected via a network. Specifically, each computing device is connected to the network via a communication interface within the computing device.

[0218] It should be understood that the functionality of the computing device 1400A shown in FIG16 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.

[0219] This embodiment also provides a computer program product including instructions. 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, it causes the computing device to perform the method provided above, or causes the computing device to implement the functions of the apparatus provided above.

[0220] This embodiment also provides a computer program product including instructions. The computer program product may be software or a program product including instructions that can be executed on a computing device cluster or stored in any available medium. When executed by a computing device cluster, the computer program product causes the computing device cluster to perform the above-mentioned method or implement the functions of the above-mentioned apparatus.

[0221] This embodiment also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium capable of storing data on 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, or a magnetic tape), an optical medium (e.g., a digital video disc (DVD)), or a semiconductor medium (e.g., a solid-state drive). The computer-readable storage medium includes instructions that, when executed on a computing device, cause the computing device to perform the method provided above.

[0222] This embodiment also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium capable of storing data on a computing device, or a data storage device such as a data center that contains one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, or a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive). The computer-readable storage medium includes instructions that, when executed by a computing device cluster, cause the computing device cluster to perform the method provided above.

[0223] Those skilled 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 beyond the scope of this application.

[0224] Those skilled in the art will 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.

[0225] In the several embodiments provided in this 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 merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, 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.

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

[0227] 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.

[0228] 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, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method 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.

[0229] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection 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 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.

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