Cloud desktop disaster recovery method, device and equipment and computer readable medium

Abstract

The invention discloses a cloud desktop disaster recovery method, device and equipment and a computer readable storage medium, and relates to the technical field of cloud desktops, and the cloud desktop disaster recovery method comprises the following steps: creating a disaster recovery desktop group on a pair of servers; data synchronization is conducted on a disaster recovery main desktop pool and a disaster recovery backup desktop pool in the disaster recovery desktop group, and the disaster recovery main desktop pool and the disaster recovery backup desktop pool are arranged on the two servers of the pair of servers respectively; and if the damaged desktop exists in the disaster recovery main desktop pool, starting the disaster recovery backup desktop pool. According to the method and the device, the disaster recovery service is configured according to the granularity of the desktop pool, when the cloud desktop has an obstacle, only the standby desktop pool needs to be used for the desktop pool, and the server does not need to be integrally switched, so that the resource waste of the cloud desktop server is reduced.

Description

Technical Field

[0001] The present application relates to the field of cloud desktop technology, and in particular to a cloud desktop disaster recovery method, device, equipment and computer-readable storage medium. Background Art

[0002] Cloud desktop, also known as desktop virtualization or cloud computer, is a new model that replaces traditional computers. After adopting cloud desktop, users can access the virtual machine host on the backend server through a unique communication protocol to achieve interactive operations and achieve the same experience as a computer. Cloud desktop disaster recovery means that when the computer providing the cloud desktop suffers from an irresistible natural disaster or man-made disaster, it guarantees the security of user data and provides uninterrupted application services.

[0003] At present, disaster recovery is mainly achieved by setting up backup servers. When the main server needs disaster recovery, the backup server is controlled and enabled to work. When using this disaster recovery method for cloud desktop disaster recovery, the backup server needs to be enabled. In fact, only part of the cloud desktop may be damaged. At this time, switching between the main server and the backup server will lead to a waste of cloud desktop server resources. Summary of the invention

[0004] The main purpose of this application is to provide a cloud desktop disaster recovery method, device, equipment and computer-readable storage medium, aiming to configure disaster recovery services at the desktop pool granularity to reduce resource waste of cloud desktop servers.

[0005] To achieve the above object, an embodiment of the present application provides a cloud desktop disaster recovery method, which includes the following steps:

[0006] Create a disaster recovery desktop group on a pair of servers;

[0007] Synchronizing data on a disaster recovery primary desktop pool and a disaster recovery backup desktop pool in the disaster recovery desktop group, wherein the disaster recovery primary desktop pool and the disaster recovery backup desktop pool are respectively set on two servers of the pair of servers;

[0008] If there is a damaged desktop in the disaster recovery primary desktop pool, the disaster recovery backup desktop pool is enabled.

[0009] Exemplarily, the step of enabling the disaster recovery desktop pool includes:

[0010] After shutting down all the desktops in the disaster recovery primary desktop pool, the management attributes of the disaster recovery backup desktop pool are determined as the management attributes of the new disaster recovery primary desktop pool, and the management attributes of the disaster recovery primary desktop pool are determined as the management attributes of the new disaster recovery backup desktop pool, wherein the management attributes include basic information characterizing the identity of the desktop pool, the configuration policy of the desktop pool, and the configuration storage;

[0011] The backup storage volume corresponding to the disaster recovery backup desktop pool is determined as a new primary storage volume, and the primary storage volume corresponding to the disaster recovery primary desktop pool is determined as a new backup storage volume, wherein the storage volume stores the data of the desktops under the pool managed by the desktop pool.

[0012] Exemplarily, after the step of enabling the disaster recovery desktop pool, the step further includes:

[0013] Synchronize the management properties of the new disaster recovery primary desktop pool after activation to the new disaster recovery backup desktop pool;

[0014] Synchronize the newly added data in the new primary storage volume to the new backup storage volume, wherein the newly added data is data generated by the desktops under the pool managed by the new disaster recovery primary desktop pool after the new disaster recovery primary desktop pool is enabled.

[0015] Exemplarily, the step of synchronizing the newly added data in the new primary storage volume to the new backup storage volume includes:

[0016] If the communication link between the new primary storage volume and the new backup storage volume is normal, synchronizing the newly added data in the new primary storage volume to the new backup storage volume;

[0017] If the communication link between the new primary storage volume and the new stored volume is abnormal, after synchronizing the existing data of the new primary storage volume to the new backup storage volume before the new disaster recovery primary desktop pool is enabled, the newly added data in the new primary storage volume will be synchronized to the new backup storage volume.

[0018] Exemplarily, the step of creating a disaster recovery desktop group on a pair of servers includes:

[0019] According to the received resource pairing relationship, configuring the first server and the second server as a pair of servers;

[0020] Creating a disaster recovery master template on the first server, and creating a disaster recovery master desktop pool on the first server based on the disaster recovery master template;

[0021] A disaster recovery template is created on the second server, and a disaster recovery desktop pool is created on the second server based on the disaster recovery template, wherein the disaster recovery master template and the disaster recovery template are virtual machine templates that support disaster recovery function.

[0022] Exemplarily, the step of synchronizing data between the disaster recovery primary desktop pool and the disaster recovery backup desktop pool in the disaster recovery desktop group includes:

[0023] Synchronize the management attributes of the disaster recovery primary desktop pool to the disaster recovery backup desktop pool;

[0024] Create the desktops under the pool of the disaster recovery desktop pool according to the desktops under the pool of the disaster recovery primary desktop pool, and synchronize the data of the storage volumes corresponding to the desktops under the pool managed by the disaster recovery primary desktop pool to the storage volumes corresponding to the desktops under the pool managed by the disaster recovery desktop pool.

[0025] Exemplarily, after the step of enabling the disaster recovery desktop pool, the step further includes:

[0026] Receive the login authentication request sent by the client;

[0027] After authentication is passed, the enabled disaster recovery desktop pool is returned to the client based on the user information carried in the login authentication request.

[0028] To achieve the above object, the embodiment of the present application further provides a cloud desktop disaster recovery device, the cloud desktop disaster recovery device comprising:

[0029] A creation module is used to create a disaster recovery desktop group on a pair of servers;

[0030] A synchronization module, used for synchronizing data between a disaster recovery primary desktop pool and a disaster recovery backup desktop pool in the disaster recovery desktop group, wherein the disaster recovery primary desktop pool and the disaster recovery backup desktop pool are respectively arranged on two servers of the pair of servers;

[0031] The enabling module is used to enable the disaster recovery desktop pool if there is a damaged desktop in the disaster recovery primary desktop pool.

[0032] To achieve the above-mentioned purpose, an embodiment of the present application also provides a cloud desktop disaster recovery device, which includes: a memory, a processor, and a cloud desktop disaster recovery program stored in the memory and executable on the processor. When the cloud desktop disaster recovery program is executed by the processor, the steps of the cloud desktop disaster recovery method described above are implemented.

[0033] To achieve the above objectives, the present application also proposes a computer-readable storage medium, on which a cloud desktop disaster recovery program is stored. When the cloud desktop disaster recovery program is executed by a processor, the steps of the cloud desktop disaster recovery method described above are implemented.

[0034] In an embodiment of the present application, a cloud desktop disaster recovery method, apparatus, device and computer-readable storage medium are provided. The cloud desktop disaster recovery method includes: creating a disaster recovery desktop group on a pair of servers; synchronizing data between a disaster recovery primary desktop pool and a disaster recovery backup desktop pool in the disaster recovery desktop group, wherein the disaster recovery primary desktop pool and the disaster recovery backup desktop pool are respectively set on two servers of a pair of servers; if there is a damaged desktop in the disaster recovery primary desktop pool, the disaster recovery backup desktop pool is enabled.

[0035] The embodiment of the present application configures the disaster recovery service at the desktop pool granularity. When a cloud desktop fails, only the backup desktop pool needs to be enabled for the desktop pool without switching the entire server, thereby reducing the waste of cloud desktop server resources.

[0036] Compared with server-level disaster recovery, disaster recovery at the desktop pool level has a smaller impact range and faster response speed, which can improve the user experience of using the cloud desktop. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 A schematic diagram of the structure of a cloud desktop disaster recovery device involved in an embodiment of the present application;

[0038] Figure 2 This is a flow chart of an embodiment of a cloud desktop disaster recovery method of the present application;

[0039] Figure 3 This is a flow chart of an implementation method of a cloud desktop disaster recovery method of the present application;

[0040] Figure 4 This is a flow chart of an embodiment of a cloud desktop disaster recovery method of the present application;

[0041] Figure 5 This is a flow chart of an embodiment of a cloud desktop disaster recovery method of the present application;

[0042] Figure 6 This is a flow chart of an implementation method of a cloud desktop disaster recovery method of the present application;

[0043] Figure 7 A schematic diagram of a cloud desktop management structure involved in an implementation method of a cloud desktop disaster recovery method of the present application;

[0044] Figure 8 This is a schematic diagram of a cloud desktop disaster recovery device involved in an embodiment of the present application.

[0045] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0046] It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0047] Reference Figure 1 , Figure 1 This is a schematic diagram of the structure of a cloud desktop disaster recovery device involved in an embodiment of the present application.

[0048] like Figure 1As shown, the cloud desktop disaster recovery device may include: a processor 1001, such as a central processing unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Among them, the communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may include a display screen (Display), an input unit such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a wireless fidelity (WIreless-FIdelity, WI-FI) interface). The memory 1005 may be a high-speed random access memory (Random Access Memory, RAM) memory, or a stable non-volatile memory (Non-Volatile Memory, NVM), such as a disk memory. The memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0049] Those skilled in the art will understand that Figure 1 The structure shown in the figure does not constitute a limitation on the operating device, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.

[0050] like Figure 1 As shown, the memory 1005 as a storage medium may include an operating system, a data storage module, a network communication module, a user interface module and a computer program.

[0051] exist Figure 1 In the running device shown, the network interface 1004 is mainly used for data communication with other devices; the user interface 1003 is mainly used for data interaction with the user; the processor 1001 and the memory 1005 in the running device of the present application can be set in the running device, and the running device calls the computer program stored in the memory 1005 through the processor 1001, and performs the following operations:

[0052] Create a disaster recovery desktop group on a pair of servers;

[0053] Synchronizing data on a disaster recovery primary desktop pool and a disaster recovery backup desktop pool in the disaster recovery desktop group, wherein the disaster recovery primary desktop pool and the disaster recovery backup desktop pool are respectively set on two servers of the pair of servers;

[0054] If there is a damaged desktop in the disaster recovery primary desktop pool, the disaster recovery backup desktop pool is enabled.

[0055] Exemplarily, the operation of enabling the disaster recovery desktop pool includes:

[0056] After shutting down all the desktops in the disaster recovery primary desktop pool, the management attributes of the disaster recovery backup desktop pool are determined as the management attributes of the new disaster recovery primary desktop pool, and the management attributes of the disaster recovery primary desktop pool are determined as the management attributes of the new disaster recovery backup desktop pool, wherein the management attributes include basic information characterizing the identity of the desktop pool, the configuration policy of the desktop pool, and the configuration storage;

[0057] The backup storage volume corresponding to the disaster recovery backup desktop pool is determined as a new primary storage volume, and the primary storage volume corresponding to the disaster recovery primary desktop pool is determined as a new backup storage volume, wherein the storage volume stores the data of the desktops under the pool managed by the desktop pool.

[0058] Exemplarily, after the operation of enabling the disaster recovery desktop pool, the process further includes:

[0059] Synchronize the management properties of the new disaster recovery primary desktop pool after activation to the new disaster recovery backup desktop pool;

[0060] Synchronize the newly added data in the new primary storage volume to the new backup storage volume, wherein the newly added data is data generated by the desktops under the pool managed by the new disaster recovery primary desktop pool after the new disaster recovery primary desktop pool is enabled.

[0061] Exemplarily, the operation of synchronizing the newly added data in the new primary storage volume to the new backup storage volume includes:

[0062] If the communication link between the new primary storage volume and the new backup storage volume is normal, synchronizing the newly added data in the new primary storage volume to the new backup storage volume;

[0063] If the communication link between the new primary storage volume and the new stored volume is abnormal, after synchronizing the existing data of the new primary storage volume to the new backup storage volume before the new disaster recovery primary desktop pool is enabled, the newly added data in the new primary storage volume will be synchronized to the new backup storage volume.

[0064] Exemplarily, the operation of creating a disaster recovery desktop group on a pair of servers includes:

[0065] According to the received resource pairing relationship, configuring the first server and the second server as a pair of servers;

[0066] Creating a disaster recovery master template on the first server, and creating a disaster recovery master desktop pool on the first server based on the disaster recovery master template;

[0067] A disaster recovery template is created on the second server, and a disaster recovery desktop pool is created on the second server based on the disaster recovery template, wherein the disaster recovery master template and the disaster recovery template are virtual machine templates that support disaster recovery function.

[0068] Exemplarily, the operation of synchronizing data between the disaster recovery primary desktop pool and the disaster recovery backup desktop pool in the disaster recovery desktop group includes:

[0069] Synchronize the management attributes of the disaster recovery primary desktop pool to the disaster recovery backup desktop pool;

[0070] Create the desktops under the pool of the disaster recovery desktop pool according to the desktops under the pool of the disaster recovery primary desktop pool, and synchronize the data of the storage volumes corresponding to the desktops under the pool managed by the disaster recovery primary desktop pool to the storage volumes corresponding to the desktops under the pool managed by the disaster recovery desktop pool.

[0071] Exemplarily, after the operation of enabling the disaster recovery desktop pool, the process further includes:

[0072] Receive the login authentication request sent by the client;

[0073] After authentication is passed, the enabled disaster recovery desktop pool is returned to the client based on the user information carried in the login authentication request.

[0074] Based on the above structure, various embodiments of the cloud desktop disaster recovery method are proposed.

[0075] Reference Figure 2 , Figure 2 This is a flow chart of the first embodiment of the cloud desktop disaster recovery method of the present application. The embodiment of the present application provides an embodiment of the cloud desktop disaster recovery method. It should be noted that although the logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in an order different from that here. The execution subject of the cloud desktop disaster recovery method in this embodiment may be a unified management platform of the cloud desktop site, such as a server, a network element device, and the like. For ease of description, the following description of each embodiment by the execution subject is omitted. In this embodiment, the cloud desktop disaster recovery method includes:

[0076] Step S10, creating a disaster recovery desktop group on a pair of servers;

[0077] Cloud desktop is also called desktop virtualization. A cloud desktop is a virtual machine. A desktop pool consists of a group of cloud desktops with the same specifications created based on the same virtual machine template. The individual cloud desktops that make up the desktop pool are referred to as pooled desktops below. The desktop pool can manage its own pooled desktops, such as policy configuration and desktop properties of pooled desktops. During the use of the cloud desktop, the cloud desktop may be damaged due to force majeure natural disasters or man-made disasters. In this case, in order to ensure the security of user data and provide uninterrupted application services, it is necessary to perform disaster recovery on the damaged cloud desktop (hereinafter referred to as the damaged desktop), that is, to enable the backup desktop of the damaged desktop.

[0078] In this embodiment, a group of desktop pools supporting disaster recovery function is created on a pair of servers, hereinafter referred to as a disaster recovery desktop group, wherein the desktop pool of the disaster recovery desktop group supports providing data synchronization function. The disaster recovery desktop group includes a disaster recovery main desktop pool and a disaster recovery backup desktop pool, and the disaster recovery main desktop pool and the disaster recovery backup desktop pool are respectively set on two servers of a pair of servers.

[0079] In this embodiment, resources on a pair of servers are synchronized with each other, that is, any server in a pair of servers can provide data backup function for the paired server. When the cloud desktop needs disaster recovery, the server that saves the backup data can replace the other server to provide cloud desktop services to achieve disaster recovery operation. In a feasible implementation, one of the servers in a pair of servers can be used as a backup server of the other server to provide disaster recovery function, that is, one of the servers is used to back up the data of the other server; in another feasible implementation, any server can provide data backup function for the paired server while also serving as a production server to provide regular production services. Compared with using one of the servers as a backup server, this implementation enables the server to provide production services when disaster recovery is not needed, improves the utilization rate of server resources, and reduces the waste of server resources.

[0080] In this embodiment, a group of desktop pools supporting disaster recovery is created on a pair of servers, which is hereinafter referred to as a disaster recovery desktop group for distinction. The disaster recovery desktop group includes two desktop pools, namely, a disaster recovery primary desktop pool and a disaster recovery backup desktop pool, which are respectively set on two servers of a pair of servers.

[0081] Step S20, synchronizing data on a disaster recovery primary desktop pool and a disaster recovery backup desktop pool in the disaster recovery desktop group, wherein the disaster recovery primary desktop pool and the disaster recovery backup desktop pool are respectively set on two servers of the pair of servers;

[0082] In this embodiment, after creating a disaster recovery desktop group, data synchronization is performed on the disaster recovery primary desktop pool and the disaster recovery backup desktop pool in the disaster recovery desktop group to make the data of the disaster recovery primary desktop pool and the disaster recovery backup desktop pool consistent, so that the user experience will not be affected when using the disaster recovery backup desktop pool for disaster recovery.

[0083] Exemplarily, the data synchronization between the disaster recovery main desktop pool and the disaster recovery backup desktop pool can be achieved through mirror synchronization technology. In the data synchronization process, asynchronous replication or synchronous replication can be adopted, which is not limited here.

[0084] Step S30: If there is a damaged desktop in the disaster recovery primary desktop pool, the disaster recovery backup desktop pool is enabled.

[0085] If there is a damaged desktop in the disaster recovery primary desktop pool, the disaster recovery backup desktop pool is enabled. The damaged desktop in the disaster recovery primary desktop pool may be caused by a damaged desktop in one of the pools of the disaster recovery primary desktop pool, or by all the desktops in the pools of the disaster recovery primary desktop pool.

[0086] In one feasible implementation, the process of enabling a disaster recovery desktop pool can be: shutting down all desktops under the disaster recovery primary desktop pool (hereinafter referred to as the disaster recovery primary desktop for distinction); disabling the disaster recovery primary desktop pool and the disaster recovery primary desktop; determining the disaster recovery primary desktop pool as a new disaster recovery desktop pool, determining the disaster recovery primary template as a new disaster recovery template, and determining the disaster recovery primary desktop as a desktop under the new disaster recovery desktop pool (hereinafter referred to as the disaster recovery desktop for distinction); determining the disaster recovery desktop pool as a new disaster recovery primary and backup desktop pool, determining the disaster recovery template as a new disaster recovery primary template, and determining the disaster recovery desktop as a new disaster recovery primary desktop.

[0087] In the process of enabling the disaster recovery desktop pool, since shutting down the disaster recovery main desktop pool takes up most of the disaster recovery time, affecting the user experience, therefore, in a feasible implementation, the user is provided with the option to manually shut down the disaster recovery main desktop pool and all disaster recovery main desktops, and after confirming that the disaster recovery main desktop pool and the disaster recovery main desktops are all shut down, the disaster recovery desktop pool is enabled to reduce the time taken to enable the disaster recovery desktop pool, improve disaster recovery efficiency, and improve the user experience. In this implementation, reference Figure 3The disaster recovery process can be: 1) manually shut down the disaster recovery main desktop; 2) determine whether all desktops under the disaster recovery main desktop pool (that is, the disaster recovery main desktop) are shut down; if so, go to step 3; if not, return to step 1; 3) disable the disaster recovery main desktop pool and the desktops under the pool; 4) switch the disaster recovery main desktop pool to a disaster recovery backup desktop pool (that is, determine the disaster recovery main desktop pool as the new disaster recovery backup desktop pool); 5) switch the disaster recovery main template to a disaster recovery backup template (that is, determine the disaster recovery main template as the new disaster recovery backup template); 6) switch the disaster recovery main desktop under the pool to a disaster recovery backup Desktop (that is, the disaster recovery main desktop is determined as the new disaster recovery backup desktop); 7) Switch the disaster recovery backup template to the disaster recovery main template (that is, determine the disaster recovery backup desktop pool as the new disaster recovery main and backup desktop pool); 8) Switch the disaster recovery backup desktop under the pool to the disaster recovery main desktop (that is, determine the disaster recovery backup template as the new disaster recovery main template); 9) Switch the disaster recovery backup desktop pool under the pool to the disaster recovery main desktop pool (that is, determine the disaster recovery backup desktop as the new disaster recovery main desktop); 10) Enable the disaster recovery main desktop pool (that is, the new disaster recovery main desktop pool) and the desktop under the pool (that is, the new disaster recovery main desktop).

[0088] Exemplarily, in one feasible implementation, before creating a disaster recovery desktop group, administrator instructions are received to create a storage server, port group, and IP pool; and administrator instructions are received to open user accounts; administrator instructions are received to create a desktop pool, create a desktop and configure a license, and configure the association between the user and the desktop pool.

[0089] In this embodiment, a disaster recovery desktop group is created on a pair of servers; data is synchronized between the disaster recovery primary desktop pool and the disaster recovery backup desktop pool in the disaster recovery desktop group, wherein the disaster recovery primary desktop pool and the disaster recovery backup desktop pool are respectively set on two servers of a pair of servers; if there is a damaged desktop in the disaster recovery primary desktop pool, the disaster recovery backup desktop pool is enabled.

[0090] This example configures the disaster recovery service at the desktop pool granularity. When a cloud desktop fails, only the backup desktop pool needs to be enabled for the desktop pool, without switching the entire server, thereby reducing the waste of cloud desktop server resources. Compared with server granularity disaster recovery, disaster recovery at the desktop pool granularity has a smaller impact range and faster response speed, which can improve the user experience of using the cloud desktop.

[0091] Based on the above first embodiment, a second embodiment of the cloud desktop disaster recovery method of the present application is proposed. In this embodiment, referring to Figure 4 Step S30: activating the disaster recovery desktop pool, including:

[0092] Step S301, after closing all the desktops in the disaster recovery main desktop pool, determine the management attributes of the disaster recovery backup desktop pool as the management attributes of the new disaster recovery main desktop pool, and determine the management attributes of the disaster recovery main desktop pool as the management attributes of the new disaster recovery backup desktop pool, wherein the management attributes include basic information characterizing the identity of the desktop pool, the configuration policy of the desktop pool, and the configuration storage;

[0093] In this embodiment, after closing all the desktops under the disaster recovery main desktop pool, the management properties of the disaster recovery desktop pool are determined as the management properties of the new disaster recovery main desktop pool, and the management properties of the disaster recovery main desktop pool are determined as the management properties of the new disaster recovery desktop pool, where the management properties include basic information characterizing the identity of the desktop pool, the configuration policy of the desktop pool, and the configuration storage.

[0094] The basic information may include: the description information of the desktop pool and the desktop pool management information, among which the description information is the information describing the identity of the desktop pool, and may include the name of the desktop pool, etc. The desktop pool management information may include the number of desktops in the pool, the memory of the desktops in the pool, the number of cores of the desktops in the pool, the modification of the desktops in the pool, the virtual machine template information, etc. The configuration policy of the desktop pool may include: the maximum number of virtual machines to be created, the number of pre-created virtual machines, the desktop pool type, and the recycling policy and reallocation policy of the desktops in the pool, etc. The configuration storage of the desktop pool is the data disk for the desktop configuration in the pool.

[0095] Step S302, determine the backup storage volume corresponding to the disaster recovery backup desktop pool as a new primary storage volume, and determine the primary storage volume corresponding to the disaster recovery primary desktop pool as a new backup storage volume, wherein the storage volume stores the data of the desktops under the pool managed by the desktop pool.

[0096] In this embodiment, the process of enabling the disaster recovery desktop pool also requires switching the cloud desktop and the virtual machine template. The cloud desktop and the virtual machine template are essentially virtual machines. Switching the cloud desktop and the virtual machine template means switching the storage volume corresponding to the virtual machine.

[0097] In this embodiment, the storage volume corresponding to the disaster recovery desktop pool is called the backup storage volume, and the storage volume corresponding to the disaster recovery main desktop pool is called the primary storage volume. The backup storage volume corresponding to the disaster recovery desktop pool is determined as the new primary storage volume, and the primary storage volume corresponding to the disaster recovery main desktop pool is determined as the new backup storage volume, wherein the storage volume stores the data of the desktops under the pool managed by the desktop pool.

[0098] Exemplarily, in a feasible implementation manner, after step S302: enabling the disaster recovery desktop pool, the method further includes:

[0099] Step S303, synchronizing the management properties of the new disaster recovery primary desktop pool after activation to the new disaster recovery backup desktop pool;

[0100] In this embodiment, after the disaster recovery desktop pool is enabled, the data of the new disaster recovery primary desktop pool is synchronized to the new disaster recovery primary desktop pool, so that the data of the new disaster recovery primary desktop pool and the new disaster recovery desktop pool are consistent, so that the user experience is not affected when the new disaster recovery desktop pool is used for disaster recovery. Specifically, the management properties of the new disaster recovery primary desktop pool after it is enabled are synchronized to the new disaster recovery desktop pool.

[0101] Step S304, synchronizing the newly added data in the new primary storage volume to the new backup storage volume, wherein the newly added data is data generated by the desktops under the pool managed by the new disaster recovery primary desktop pool after the new disaster recovery primary desktop pool is enabled.

[0102] Synchronize the newly added data in the new primary storage volume to the new backup storage volume, where the newly added data is the data generated by the desktops under the pool managed by the new disaster recovery primary desktop pool after the new disaster recovery primary desktop pool is enabled.

[0103] Exemplarily, in a feasible implementation manner, step S304: synchronizing the newly added data in the new primary storage volume to the new backup storage volume includes:

[0104] Step S3041: If the communication link between the new primary storage volume and the new backup storage volume is normal, synchronizing the newly added data in the new primary storage volume to the new backup storage volume;

[0105] In this implementation, different data synchronization schemes are adopted according to the connection status of the communication link between the new primary storage volume and the new backup storage volume.

[0106] Specifically, if the communication link between the new primary storage volume and the new backup storage volume is normal, it is considered that no transmission interruption occurs during the process of synchronizing data from the primary storage volume to the backup storage volume, that is, the data on the new primary storage volume and the new backup storage volume are the same. At this time, the newly added data in the new primary storage volume is synchronized to the new backup storage volume to reduce data transmission content and avoid ineffective consumption of server resources.

[0107] Step S3042, if the communication link between the new primary storage volume and the new stored volume is abnormal, then after synchronizing the existing data of the new primary storage volume to the new backup storage volume before the new disaster recovery primary desktop pool is enabled, the newly added data in the new primary storage volume is synchronized to the new backup storage volume.

[0108] If the communication link between the new primary storage volume and the new stored volume is abnormal, it is considered that a transmission interruption may occur during the process of synchronizing data from the primary storage volume to the backup storage volume. At this time, the storage data of the new primary storage volume and the new backup storage volume may be different. Therefore, it is necessary to first synchronize the existing data of the new primary storage volume to the new backup storage volume before the new disaster recovery primary desktop pool is enabled, and then synchronize the newly added data in the new primary storage volume to the new backup storage volume to ensure that the storage data of the new primary storage volume and the new backup storage volume are consistent, so that the user experience will not be affected when using the new disaster recovery backup desktop pool for disaster recovery.

[0109] In this embodiment, after closing all the desktops in the disaster recovery main desktop pool, the management properties of the disaster recovery backup desktop pool are determined as the management properties of the new disaster recovery main desktop pool, and the management properties of the disaster recovery main desktop pool are determined as the management properties of the new disaster recovery backup desktop pool, wherein the management properties include basic information characterizing the identity of the desktop pool, the configuration policy of the desktop pool, and the configuration storage; the backup storage volume corresponding to the disaster recovery backup desktop pool is determined as the new primary storage volume, and the primary storage volume corresponding to the disaster recovery main desktop pool is determined as the new backup storage volume, wherein the storage volume stores the data of the desktops in the pool managed by the desktop pool.

[0110] This embodiment implements disaster recovery service configuration at the desktop pool granularity. When a cloud desktop fails, only the backup desktop pool needs to be enabled for the desktop pool without switching the entire server, thereby reducing the waste of cloud desktop server resources.

[0111] Based on the above first and / or second embodiments, a third embodiment of the cloud desktop disaster recovery method of the present application is proposed. In this embodiment, referring to Figure 5 , Step S10: Creating a disaster recovery desktop group on a pair of servers, including:

[0112] Step S101, configuring a first server and a second server as a pair of servers according to the received resource pairing relationship;

[0113] In this embodiment, a creation instruction for creating a pair of servers sent by a manager is received, and the first server and the second server are configured as a pair of servers according to the resource pairing relationship indicated by the creation instruction.

[0114] Step S102, creating a disaster recovery master template on the first server, and creating a disaster recovery master desktop pool on the first server based on the disaster recovery master template;

[0115] In this embodiment, a disaster recovery master template is created on the first server, and a disaster recovery master desktop pool is created on the first server based on the disaster recovery master template, wherein the disaster recovery master template is a virtual machine template that supports disaster recovery function.

[0116] Step S103, creating a disaster recovery template on the second server, and creating a disaster recovery desktop pool on the second server based on the disaster recovery template, wherein the disaster recovery main template and the disaster recovery template are virtual machine templates supporting disaster recovery function.

[0117] A disaster recovery template is created on the second server, and a disaster recovery desktop pool is created on the second server based on the disaster recovery template, wherein the disaster recovery template is a virtual machine template that supports disaster recovery function, and the specifications of the disaster recovery template and the disaster recovery master template are the same.

[0118] For example, in one possible implementation, refer to Figure 6 , the process of creating a disaster recovery desktop group can be: 1) creating a resource pairing relationship between servers A and B (that is, configuring the first server and the second server as a pair of servers according to the received resource pairing relationship); 2) creating a disaster recovery main template on server A according to the pairing relationship (that is, creating a disaster recovery main template on the first server), and creating a disaster recovery backup template on server B at the same time (that is, creating a disaster recovery backup template on the second server); 3) selecting templates, storage and other configurations that support disaster recovery to create / modify a desktop pool; 4) determining whether the desktop pool and the desktops under the pool meet the disaster recovery requirements; if so, proceed to step 5; if not, return to step 3; 5) selecting the desktop pool as the disaster recovery main desktop pool, creating a disaster recovery group, and creating a disaster recovery backup desktop pool on server B at the same time (that is, creating a disaster recovery main desktop pool on the first server based on the disaster recovery main template, and creating a disaster recovery backup desktop pool on the second server based on the disaster recovery backup template).

[0119] Exemplarily, in a feasible implementation, step S20: synchronizing data between the disaster recovery primary desktop pool and the disaster recovery backup desktop pool in the disaster recovery desktop group includes:

[0120] Step S201, synchronizing the management attributes of the disaster recovery primary desktop pool to the disaster recovery backup desktop pool;

[0121] In this embodiment, after the disaster recovery desktop group is established, data synchronization is performed on the disaster recovery primary desktop pool and the disaster recovery backup desktop pool in the disaster recovery desktop group. Specifically, the management attributes of the disaster recovery primary desktop pool are synchronized to the disaster recovery backup desktop pool.

[0122] Step S201, create the desktops under the disaster recovery desktop pool according to the desktops under the disaster recovery primary desktop pool, and synchronize the data of the storage volumes corresponding to the desktops under the disaster recovery primary desktop pool to the storage volumes corresponding to the desktops under the disaster recovery desktop pool.

[0123] In this implementation, the desktops under the disaster recovery desktop pool are created according to the desktops under the disaster recovery primary desktop pool, and the data of the storage volumes corresponding to the desktops under the disaster recovery primary desktop pool are synchronized to the storage volumes corresponding to the desktops under the disaster recovery desktop pool. This implementation makes the data of the disaster recovery primary desktop pool and the disaster recovery desktop pool consistent, ensures the integrity of the data in the disaster recovery desktop pool, and ensures the disaster recovery effect and user experience during disaster recovery.

[0124] Exemplarily, in a feasible implementation, the specific process of data synchronization between the disaster recovery main desktop pool and the disaster recovery backup desktop pool in the disaster recovery desktop group can be: synchronizing the management properties of the disaster recovery main desktop pool to the disaster recovery backup desktop pool; modifying the desktops under the disaster recovery main desktop pool to be the disaster recovery main desktop; creating a disaster recovery backup desktop pool according to the management properties of the disaster recovery main desktop pool; synchronizing modification operations on the disaster recovery main desktop pool to the disaster recovery backup desktop pool, such as modifying configurations, binding user groups, and other operations (that is, synchronizing the management properties of the disaster recovery main desktop pool to the disaster recovery backup desktop pool); synchronizing configuration modification, user binding, policy binding, and other operations on the disaster recovery main desktop to the disaster recovery backup desktop; when users use the cloud desktop, the created files and folders will be synchronized to the disaster recovery backup desktop (that is, synchronizing the data of the primary storage volume corresponding to the disaster recovery main desktop to the backup storage volume of the disaster recovery backup desktop pool).

[0125] Exemplarily, in a feasible implementation, step S30: after enabling the disaster recovery desktop pool, includes:

[0126] Step S40, receiving a login authentication request sent by the client;

[0127] In this embodiment, after the disaster recovery desktop pool is enabled, when the user needs to use the cloud desktop, a login authentication request is sent through the client to request to return to the cloud desktop.

[0128] Step S50, after authentication is passed, based on the user information carried in the login authentication request, the enabled disaster recovery desktop pool is returned to the client.

[0129] After authentication is passed, the enabled disaster recovery desktop pool is returned to the client based on the user information carried in the login authentication request.

[0130] After the disaster recovery desktop pool is enabled, when a user needs to use the cloud desktop, the user needs to send a login authentication request through the client and obtain the enabled disaster recovery desktop pool after the authentication operation. This implementation ensures user data security and improves the security of the cloud desktop during use.

[0131] In this embodiment, according to the received resource pairing relationship, the first server and the second server are configured as a pair of servers; a disaster recovery master template is created on the first server, and a disaster recovery master desktop pool is created on the first server based on the disaster recovery master template; a disaster recovery backup template is created on the second server, and a disaster recovery backup desktop pool is created on the second server based on the disaster recovery backup template, wherein the disaster recovery master template and the disaster recovery backup template are virtual machine templates that support disaster recovery functions. In this embodiment, a disaster recovery master desktop pool and a disaster recovery backup desktop pool are created respectively by using a disaster recovery backup template and a disaster recovery master template with the same specifications. In this embodiment, the specifications of the disaster recovery master desktop pool and the disaster recovery backup desktop pool are the same, thereby ensuring the consistency of the data of the disaster recovery master desktop pool and the disaster recovery backup desktop pool, and ensuring the user experience during disaster recovery.

[0132] For example, in one possible implementation, referring to Figure 7 , a unified management platform manages multiple resource sites, such as Figure 7 The A site and the B site are shown in FIG. Each site includes a primary resource pool and a backup resource pool. The primary resource pool stores the primary storage volume of the disaster recovery primary desktop pool, for example Figure 7 The A0-A2 volumes in the primary resource pool at site A are stored in the table, and the B0-B2 volumes in the primary resource pool at site B are stored in the table. The backup resource pool stores the backup storage volumes of the disaster recovery desktop pool, for example Figure 7 As shown in the figure, volumes B0-B2 in the standby resource pool of site A store volumes, and volumes A0-A2 in the standby resource pool of site B store volumes.

[0133] Each resource site is configured with its own virtual machine management system to manage the site's storage data. After a disaster recovery desktop group is created on the server at site A and the server at site B, the data of the primary storage volume of the disaster recovery primary desktop pool at site A is synchronized to the backup storage volume of the disaster recovery backup desktop pool at site B through the virtual machine management system; the data of the primary storage volume of the disaster recovery primary desktop pool at site B is synchronized to the backup storage volume of the disaster recovery backup desktop pool at site A through the virtual machine management system.

[0134] In addition, refer to Figure 8 The embodiment of the present application further provides a cloud desktop disaster recovery device, the cloud desktop disaster recovery device comprising:

[0135] A creation module 10 is used to create a disaster recovery desktop group on a pair of servers;

[0136] A synchronization module 20 is used to synchronize data between a disaster recovery primary desktop pool and a disaster recovery backup desktop pool in the disaster recovery desktop group, wherein the disaster recovery primary desktop pool and the disaster recovery backup desktop pool are respectively arranged on two servers of the pair of servers;

[0137] The enabling module 30 is used to enable the disaster recovery desktop pool if there is a damaged desktop in the disaster recovery primary desktop pool.

[0138] Exemplarily, the enabling module 30 is further used for:

[0139] After shutting down all the desktops in the disaster recovery primary desktop pool, the management attributes of the disaster recovery backup desktop pool are determined as the management attributes of the new disaster recovery primary desktop pool, and the management attributes of the disaster recovery primary desktop pool are determined as the management attributes of the new disaster recovery backup desktop pool, wherein the management attributes include basic information characterizing the identity of the desktop pool, the configuration policy of the desktop pool, and the configuration storage;

[0140] The backup storage volume corresponding to the disaster recovery backup desktop pool is determined as a new primary storage volume, and the primary storage volume corresponding to the disaster recovery primary desktop pool is determined as a new backup storage volume, wherein the storage volume stores the data of the desktops under the pool managed by the desktop pool.

[0141] Exemplarily, the enabling module 30 is further used for:

[0142] Synchronize the management properties of the new disaster recovery primary desktop pool after activation to the new disaster recovery backup desktop pool;

[0143] Synchronize the newly added data in the new primary storage volume to the new backup storage volume, wherein the newly added data is data generated by the desktops under the pool managed by the new disaster recovery primary desktop pool after the new disaster recovery primary desktop pool is enabled.

[0144] Exemplarily, the enabling module 30 is further used for:

[0145] If the communication link between the new primary storage volume and the new backup storage volume is normal, synchronizing the newly added data in the new primary storage volume to the new backup storage volume;

[0146] If the communication link between the new primary storage volume and the new stored volume is abnormal, after synchronizing the existing data of the new primary storage volume to the new backup storage volume before the new disaster recovery primary desktop pool is enabled, the newly added data in the new primary storage volume will be synchronized to the new backup storage volume.

[0147] Exemplarily, the creation module 10 is further used for:

[0148] According to the received resource pairing relationship, configuring the first server and the second server as a pair of servers;

[0149] Creating a disaster recovery master template on the first server, and creating a disaster recovery master desktop pool on the first server based on the disaster recovery master template;

[0150] A disaster recovery template is created on the second server, and a disaster recovery desktop pool is created on the second server based on the disaster recovery template, wherein the disaster recovery master template and the disaster recovery template are virtual machine templates that support disaster recovery function.

[0151] Exemplarily, the synchronization module 20 is further used for:

[0152] Synchronize the management attributes of the disaster recovery primary desktop pool to the disaster recovery backup desktop pool;

[0153] Create the desktops under the pool of the disaster recovery desktop pool according to the desktops under the pool of the disaster recovery primary desktop pool, and synchronize the data of the storage volumes corresponding to the desktops under the pool managed by the disaster recovery primary desktop pool to the storage volumes corresponding to the desktops under the pool managed by the disaster recovery desktop pool.

[0154] Exemplarily, the cloud desktop disaster recovery device further includes an authentication module. After the disaster recovery desktop pool is enabled, the authentication module is used to:

[0155] Receive the login authentication request sent by the client;

[0156] After authentication is passed, the enabled disaster recovery desktop pool is returned to the client based on the user information carried in the login authentication request.

[0157] The present application also provides a computer-readable storage medium, on which a cloud desktop disaster recovery program is stored. When the cloud desktop disaster recovery program is executed by a processor, the steps of the cloud desktop disaster recovery method described in the above embodiments are implemented. Figure 7 In a specific implementation, a memory as a computer-readable storage medium can be connected to communicate with the processor via a communication bus.

[0158] The various embodiments of the cloud desktop disaster recovery device, equipment, and computer-readable storage medium of the present application can all refer to the various embodiments of the cloud desktop disaster recovery method of the present application, and will not be repeated here.

[0159] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0160] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0161] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0162] The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A cloud desktop disaster recovery method, characterized in that: The cloud desktop disaster recovery method includes: Create a disaster recovery desktop group on a pair of servers; Synchronizing data on a disaster recovery primary desktop pool and a disaster recovery backup desktop pool in the disaster recovery desktop group, wherein the disaster recovery primary desktop pool and the disaster recovery backup desktop pool are respectively set on two servers of the pair of servers; If there is a damaged desktop in the disaster recovery primary desktop pool, the disaster recovery backup desktop pool is enabled.

2. The cloud desktop disaster recovery method according to claim 1, characterized in that: The step of enabling the disaster recovery desktop pool includes: After shutting down all the desktops in the disaster recovery primary desktop pool, the management attributes of the disaster recovery backup desktop pool are determined as the management attributes of the new disaster recovery primary desktop pool, and the management attributes of the disaster recovery primary desktop pool are determined as the management attributes of the new disaster recovery backup desktop pool, wherein the management attributes include basic information characterizing the identity of the desktop pool, the configuration policy of the desktop pool, and the configuration storage; The backup storage volume corresponding to the disaster recovery backup desktop pool is determined as a new primary storage volume, and the primary storage volume corresponding to the disaster recovery primary desktop pool is determined as a new backup storage volume, wherein the storage volume stores the data of the desktops under the pool managed by the desktop pool.

3. The cloud desktop disaster recovery method according to claim 2, characterized in that: After the step of enabling the disaster recovery desktop pool, the method further includes: Synchronize the management properties of the new disaster recovery primary desktop pool after activation to the new disaster recovery backup desktop pool; Synchronize the newly added data in the new primary storage volume to the new backup storage volume, wherein the newly added data is data generated by the desktops under the pool managed by the new disaster recovery primary desktop pool after the new disaster recovery primary desktop pool is enabled.

4. The cloud desktop disaster recovery method according to claim 3, characterized in that: The step of synchronizing the newly added data in the new primary storage volume to the new backup storage volume includes: If the communication link between the new primary storage volume and the new backup storage volume is normal, synchronizing the newly added data in the new primary storage volume to the new backup storage volume; If the communication link between the new primary storage volume and the new stored volume is abnormal, after synchronizing the existing data of the new primary storage volume to the new backup storage volume before the new disaster recovery primary desktop pool is enabled, the newly added data in the new primary storage volume will be synchronized to the new backup storage volume.

5. The cloud desktop disaster recovery method according to claim 1, characterized in that: The steps of creating a disaster recovery desktop group on a pair of servers include: According to the received resource pairing relationship, configuring the first server and the second server as a pair of servers; Creating a disaster recovery master template on the first server, and creating a disaster recovery master desktop pool on the first server based on the disaster recovery master template; A disaster recovery template is created on the second server, and a disaster recovery desktop pool is created on the second server based on the disaster recovery template, wherein the disaster recovery master template and the disaster recovery template are virtual machine templates that support disaster recovery function.

6. The cloud desktop disaster recovery method according to claim 1, characterized in that: The step of synchronizing data between the disaster recovery primary desktop pool and the disaster recovery backup desktop pool in the disaster recovery desktop group includes: Synchronize the management attributes of the disaster recovery primary desktop pool to the disaster recovery backup desktop pool; Create the desktops under the pool of the disaster recovery desktop pool according to the desktops under the pool of the disaster recovery primary desktop pool, and synchronize the data of the storage volumes corresponding to the desktops under the pool managed by the disaster recovery primary desktop pool to the storage volumes corresponding to the desktops under the pool managed by the disaster recovery desktop pool.

7. The cloud desktop disaster recovery method according to any one of claims 1 to 6, characterized in that: After the step of enabling the disaster recovery desktop pool, the method further includes: Receive the login authentication request sent by the client; After authentication is passed, the enabled disaster recovery desktop pool is returned to the client based on the user information carried in the login authentication request.

8. A cloud desktop disaster recovery device, characterized in that: The cloud desktop disaster recovery device comprises: A creation module is used to create a disaster recovery desktop group on a pair of servers; A synchronization module, used for synchronizing data between a disaster recovery primary desktop pool and a disaster recovery backup desktop pool in the disaster recovery desktop group, wherein the disaster recovery primary desktop pool and the disaster recovery backup desktop pool are respectively arranged on two servers of the pair of servers; The enabling module is used to enable the disaster recovery desktop pool if there is a damaged desktop in the disaster recovery primary desktop pool.

9. A cloud desktop disaster recovery device, characterized in that: The cloud desktop disaster recovery device includes: a memory, a processor, and a cloud desktop disaster recovery program stored in the memory and executable on the processor. When the cloud desktop disaster recovery program is executed by the processor, the cloud desktop disaster recovery method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a cloud desktop disaster recovery program, and when the cloud desktop disaster recovery program is executed by the processor, the cloud desktop disaster recovery method according to any one of claims 1 to 7 is implemented.

Images