WO2017215502A1

WO2017215502A1 - Cloud-desktop disaster recovery method, client, server, cloud-desktop disaster recovery system, and storage medium

Info

Publication number: WO2017215502A1
Application number: PCT/CN2017/087463
Authority: WO
Inventors: 邱海军; 沈松; 宋伊漠; 李锴
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-06-17
Filing date: 2017-06-07
Publication date: 2017-12-21
Also published as: CN107517192A

Abstract

The embodiments of the present disclosure provide a cloud-desktop disaster recovery method, client, server, cloud-desktop disaster recovery system, and storage medium; pre-storing on a terminal an image file of the cloud desktop; when preset conditions are satisfied, providing a cloud-desktop service to a user by means of invoking the cloud-desktop image stored on the terminal. The cloud-desktop disaster recovery solution provided by the embodiments of the present disclosure is such that not only is it unnecessary for the cloud-desktop service to rely on a backup resource on a server, but since the cloud-desktop image file is stored on the client side, it is possible to ensure that the client may use normally the service provided on the basis of the cloud-desktop image file stored on the terminal, regardless of whether there is a failure on the server storage device or a network disruption between the server and the client; in comparison with related disaster recovery solutions, the present solution has enhanced reliability and improved disaster recovery performance and user experience.

Description

Cloud desktop disaster recovery method, client, server, cloud desktop disaster recovery system, and storage medium

Technical field

The present disclosure relates to the field of cloud computing technologies, and in particular, to a cloud desktop disaster recovery method, a client, a server, a cloud desktop disaster recovery system, and a storage medium.

Background technique

With the continuous development of cloud computing technology, virtual cloud desktops are more and more widely used in various industries. Virtual cloud desktops use the computing resources of remote servers as much as possible in the case of weakening user terminals. A virtual cloud computing technology for users and integrated management. The virtual cloud desktop requires the server side to supply core resources such as memory, storage, and CPU, and is supported by an excellent network architecture.

The virtual cloud surface technology can realize the separation of the desktop (including the system, the application, the data) and the device, and the management of the desktop is completely centralized to the server, thereby realizing the centralized management of the desktop system and greatly reducing the workload of the operation and maintenance. At the same time, the data security of the terminal is guaranteed, and the user can realize personal desktop access anytime and anywhere. Therefore, compared with traditional desktop management, the virtual cloud desktop not only has the advantages of convenient deployment, unified operation and maintenance management, high information security, but also benefits terminal energy saving, lower terminal cost, and remote office.

However, due to the dependence of the virtual cloud desktop service on the server resources, when the cloud server has abnormal storage resources and network interruption, the user side cannot use the virtual cloud desktop. At present, the disaster recovery solution for the virtual cloud desktop storage generally sets the standby resources on the server side. For example, in order to prevent the failure of the storage device on the cloud server side or the failure of the cloud server host to connect to the primary storage device, a backup storage device is usually set on the server side, and the backup storage device is the same as the primary storage device. It is also configured to store the user's virtual cloud desktop resources. When the cloud server host fails to use the primary storage device, the cloud server can continue to provide virtual cloud desktop services to the user by using the cloud desktop resources on the standby storage device. Similarly, in order to avoid the failure caused by the network interruption between the terminal device and the server side, the related art generally also sets a special backup on the server side. If the network port is faulty, you can switch to the backup network port. The backup network port takes over the active network port.

It is not difficult to see that there are many defects in the disaster recovery solution in the related technologies. For example, the cost requirement of the disaster recovery solution by setting up the backup storage device is relatively high. Usually, few device manufacturers set up the backup storage on the service side device. Equipment, if deployed by the cloud desktop service provider itself, will cost a lot of money. In addition, even if an alternate storage device is set on the cloud server side, there are still other problems. For example, since the primary storage device fails, the usage of the backup storage device is relatively low, most of the time. The backup storage device is in an idle or even unmanaged state. Therefore, when the primary storage device has a problem, it is difficult to ensure that the backup storage device is in a normal state. For the disaster recovery solution of the network fault, there is also a problem: those skilled in the art should know that when the user cannot use the virtual cloud desktop resource due to the network failure, it is not necessarily caused by the failure of the network port on the server side. It is also very likely that the network provided by the operator itself has problems, so in this case, even if there are more network ports on the server side, it will not help.

In summary, there are many unreasonable or incomplete disaster recovery solutions for virtual cloud desktops in related technologies. As a result, the disaster recovery effect of related disaster recovery solutions is not good. In order to enable users to use virtual cloud desktop services more confidently, now 亟A reasonable disaster recovery plan is needed.

Summary of the invention

The cloud desktop disaster recovery method, the client, the server, the cloud desktop disaster recovery system, and the storage medium provided by the embodiments of the present disclosure mainly provide a cloud desktop disaster recovery that does not need to depend on the standby resources on the server side. The solution is to solve the problem that the DR solution in the related technology depends on the backup resources on the server side and the disaster recovery effect is poor and the solution is unreasonable.

To solve the above technical problem, the embodiment of the present disclosure provides a cloud desktop disaster recovery method, including:

When the preset condition is met, the server invokes the cloud desktop image file stored in the terminal to provide the cloud desktop service to the user.

The embodiment of the present disclosure further provides a cloud desktop disaster recovery method, including:

When the preset condition is met, the client invokes the cloud desktop image file stored in the terminal to provide the cloud desktop service to the user.

The embodiment of the present disclosure further provides a client, including:

The local calling module is set to invoke the cloud desktop image file stored in the terminal to provide the cloud desktop service to the user when the preset condition is met.

The embodiment of the present disclosure further provides a server, including:

The remote calling module is configured to invoke a cloud desktop image file stored in the terminal to provide a cloud desktop service to the user when the preset condition is met.

The embodiment of the present disclosure further provides a cloud desktop disaster recovery system, including a server and a client as described above; or a client and a server as described above.

The embodiment of the present disclosure further provides a storage medium having stored therein computer executable instructions, the computer executable instructions being configured to perform the cloud desktop disaster tolerance method of any of the foregoing.

The cloud desktop disaster recovery method, the client, the server, the cloud desktop disaster recovery system, and the storage medium provided by the embodiments of the present disclosure pre-store the cloud desktop image file in the terminal, and when the preset condition is met, the storage is invoked. The cloud desktop image of the terminal provides the user with a cloud desktop service. The cloud desktop disaster recovery method, the client, the server, the cloud desktop disaster recovery system, and the storage medium provided by the embodiments of the present disclosure not only make the disaster recovery for the cloud desktop service depend on the standby resources set by the server, such as the backup storage device. Or the backup network port, etc., and because the cloud desktop image file is stored on the client side, the client can be used normally regardless of the failure of the server storage device or the network interruption between the server and the client. Compared with the related disaster recovery solution, the service provided by the cloud desktop image file of the terminal storage enhances the reliability of the disaster recovery solution and improves the disaster recovery effect and user experience.

DRAWINGS

FIG. 1 is a flowchart of a cloud desktop disaster recovery method according to Embodiment 1 of the present disclosure;

2 is a flowchart of providing a cloud desktop service by a cloud desktop image file stored by a client in a terminal according to Embodiment 1 of the present disclosure;

FIG. 3 is a flowchart of a cloud desktop disaster recovery method according to Embodiment 2 of the present disclosure;

4 is a flowchart of providing a cloud desktop service by using a cloud desktop image file stored by a server end calling terminal in the second embodiment of the present disclosure;

FIG. 5 is a schematic structural diagram of a client according to Embodiment 3 of the present disclosure;

FIG. 6 is another schematic structural diagram of a client according to Embodiment 3 of the present disclosure;

FIG. 7 is a schematic structural diagram of a client according to Embodiment 4 of the present disclosure;

FIG. 8 is a schematic structural diagram of a server provided by Embodiment 4 of the present disclosure;

FIG. 9 is a schematic structural diagram of a cloud desktop disaster recovery system according to Embodiment 4 of the present disclosure;

FIG. 10 is another schematic structural diagram of a client according to Embodiment 4 of the present disclosure;

FIG. 11 is still another schematic structural diagram of a client according to Embodiment 3 of the present disclosure.

detailed description

The embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings.

Embodiment 1:

Because the disaster recovery solution in the related art relies on the backup resource on the server side, there is a technical problem that the disaster tolerance effect is not good due to the unreasonable disaster recovery solution. For this problem, the present embodiment proposes a cloud desktop capacity. Disaster method.

In fact, the situation that meets the preset conditions is that the client cannot enjoy the cloud desktop service provided by the server in the normal way. The preset condition in this embodiment may be at least one of the following two types, and of course, two conditions may be simultaneously satisfied:

First, the network connection between the server and the client is interrupted.

Second, the cloud server host cannot be mounted to the storage device on the server side. That is, the cloud server cannot obtain the cloud desktop resources required by the client from the server side.

It can be understood that, in addition to the network failure between the server and the client or the storage failure on the server side, the preset condition should include other faults, such as a power outage at the server end.

It can be understood by those skilled in the art that the cloud desktop image file should be pre-stored in the terminal. In this embodiment, the client can cache the cloud desktop image file from the server when the cloud desktop service provided by the server can be used normally. To the terminal. See Figure 1:

S102. When the cloud desktop service provided by the server is used normally, the client extracts the required cloud desktop image file from the server and stores it in the terminal.

The server usually includes a cloud server host and a storage device. In a cloud desktop system, there may be multiple clients. Therefore, the cloud desktop image file of multiple clients should be stored on the storage device. This requires high storage space on the server. In this embodiment, the storage device may be a RAID (Redundant Arrays of Independent Disks) or a MAID (massive array of idle disks) composed of RAID. The cloud desktop image file of each client exists in the form of a separate file on the storage device of the server. The format can be VHD (Virtual Hard Disk format) format.

The storage device on the server can be divided into a primary storage device and a backup storage device. In most cases, the primary storage device is in a working state to provide a cloud desktop service. When the server provides the cloud desktop service to the client, the cloud server host is mounted on the active storage device, and the virtual machine processes the related mirror data of the client in the active storage device and continuously uses the network provided by the operator. The related image and the user operation information are presented to the client in the form of a window.

As can be seen from the above process, the client must use the cloud desktop service to meet at least two conditions: First, the cloud server host can be mounted to the primary storage device, that is, the cloud server host and the primary storage device. There can be no broken links between them. On the other hand, service The network between the terminal and the client must be kept clear, and the network interruption cannot occur. The network interruption includes the network interruption caused by the failure of the server network port and the failure caused by the problem of the network itself provided by the operator.

The client can still use the cloud desktop image file in the case of a network fault between the client and the server. Therefore, in this embodiment, when the server provides the cloud desktop service normally. The cloud desktop image file required by the client in the server can be extracted and cached in the terminal.

It can be understood that, because the cached cloud desktop image file requires a certain storage space, in this embodiment, the terminal is required to reserve a certain space for storing the cloud desktop image file that it needs. However, this requirement is not very difficult for the client, because in terms of various terminals, there are usually dozens or even hundreds of GB of storage space in an idle state. Therefore, in this embodiment, the cloud desktop image file is cached to the client, and the idle resource is effectively utilized, thereby improving the resource utilization of the client device, and avoiding the capital consumption necessary for setting the standby resource on the server. The cloud desktop disaster recovery method provided in this embodiment implements optimal configuration of resources.

In the embodiment, before the cloud desktop image file is cached, the cloud desktop image file needs to be occupied by the cloud desktop image file. First determine whether the client has idle resources, and when it is, cache the cloud desktop image file. In this embodiment, the priority of the process of caching the cloud desktop image file may also be set to secondary, that is, the cache process is regarded as a secondary process, and the current operation of the user needs to occupy network bandwidth or be used locally. When the disk is read or written, the user's current operation task is prioritized. The cloud desktop image file can continue to be cached when there is remaining bandwidth or disk read/write capability. After the cache task ends, the cached result can be notified to at least one of the server or the client. Preferably, the cached result is simultaneously notified to the client and the server.

S104. When the preset condition is met, the client invokes the cloud desktop image file stored in the terminal to provide the cloud desktop service to the user.

For the problem that the client cannot use the cloud desktop service provided by the server in the normal manner, the solution is to provide the cloud desktop service file for the user by calling the cloud desktop image file stored in the terminal. Please refer to FIG. 2. FIG. 2 is a flow chart of the client calling the cloud desktop image file stored in the terminal to provide the cloud desktop service to the user:

S202: The client processes the format of the cloud desktop image file.

The client can process the cloud desktop image file cached to the terminal when the cloud desktop image file is just cached, or when the cloud desktop image file stored by the terminal is used. In this embodiment, in order to enable the client to switch to the cloud desktop image file stored in the terminal without using the cloud desktop service provided by the server in the normal manner, without affecting the normal work of the user, the process may be performed. After the cloud desktop image file cache is completed, this can reduce the user's waiting time and improve the user experience.

The processing of the cloud desktop image file is mainly the process of recompiling the image file. Since the storage device on the server before the cloud desktop image file is in the VHD format, it needs to be used as the operating system, so it must be formatted. Process, re-encode, so that the client device can recognize that it is the operating system.

S204. The client modifies system boot information.

In this case, the client device needs to be enabled with different operating systems. Therefore, you need to modify the system boot information of the terminal device, that is, you need to modify the MBR (Master Boot Record) of the original operating system. Information, this modification will take effect after the device is restarted. Understandably, it is possible that the user does not currently need to use the cloud desktop image file very much, so even if the client cannot currently use the cloud desktop service provided by the server in the normal way, it does not matter, so in this case, The user may not need to enable the cloud desktop image stored by the terminal, but prefers to wait for the network to be normal or the cloud server host and the storage device to resume normal. Therefore, in order to fully maintain the user's will, after the network connection is interrupted or the storage is broken, and the system boot information is modified, a prompt message is sent to the user to ask whether the user wants to use the cloud desktop image file cached by the local machine. When the user chooses yes, the MBR and other related information is modified. In a better example of this embodiment, it can also be used according to The user's instructions enable the cloud desktop image file of the terminal cache at any time, that is, the user inputs a specific instruction when needed, and then the system boot program is modified, which greatly improves the user's autonomy.

S206: The client loads the processed cloud desktop image file according to the modified system boot information, and obtains a cloud desktop system for providing a cloud desktop service for the user.

After the system boot information is modified, the client device restarts. After the restart, the terminal device is booted into the system corresponding to the cloud desktop image file. At this time, the user can use the service provided by the cloud desktop image file again, but at this time the service provider is no longer the server, but the client itself. And in this case, almost no server involvement is required.

The cloud desktop disaster recovery method provided by the embodiment of the present disclosure can store the cloud desktop image file required by the client on the client, so that the client can be based on the cloud desktop stored in the terminal when the network is faulty or the server is faulty. The image file provides the cloud desktop service for users, which enhances the reliability of the disaster recovery solution and improves the disaster recovery effect and user experience. Moreover, in this embodiment, the cloud desktop disaster recovery method of the embodiment is more user-friendly and conforms to the user, before the cloud desktop image cache and the cloud desktop image file of the terminal storage are enabled, and the user's current needs and wishes are fully considered. Willingness.

Embodiment 2:

In the first embodiment, when the storage fault occurs on the server, the client continues to provide the cloud desktop service by enabling the cloud desktop image file stored in the terminal, and the client cannot use the server to provide the storage terminal due to the storage disconnection. In the case of the cloud desktop service, the cloud desktop disaster recovery method provided in this embodiment can provide another solution. Please refer to FIG. 3:

S302. When the client can use the cloud desktop service provided by the server, the cloud desktop image file required by the client is extracted from the server and stored in the terminal.

For the process of caching the cloud desktop image file in this embodiment, refer to the process in the first embodiment, and details are not described herein again.

S304. The server invokes a cloud desktop image file stored in the terminal to provide a cloud desktop service for the user.

Although the cloud server host cannot obtain the cloud desktop image file required by the client from the storage device of the server at this time, since the network connection between the server and the client is still intact, the cloud server host can hang through the network. It is loaded on the cloud desktop image file stored on the client and continues to provide cloud desktop services to users. The process in which the server invokes the cloud desktop image file stored in the terminal to provide the user with the cloud desktop service is as shown in FIG. 4:

S402: The server host is mounted to a storage directory of the terminal storage cloud desktop image file.

The server host mentioned here is the cloud server host. Mounting refers to attaching a device to an existing directory. Then, the device can access the directory to access the device where the directory is located. In this embodiment, the cloud server host is connected to the storage cloud desktop image file in the storage directory of the storage cloud desktop image file, and then accesses the storage cloud desktop image file storage device. The device obtains the cloud desktop image file.

S404: The host of the server calls the cloud desktop image file to continue to provide the cloud desktop service to the user.

Compared with the solution of loading the cloud desktop image file stored in the terminal by the client in the first embodiment, the requirement of the network may be slightly higher in the solution of the embodiment, because not only the user can be guaranteed at this time. The cloud desktop service provided by the server is normally used, and the server can also smoothly obtain the cloud desktop image file from the terminal through the network.

On the other hand, this solution has the advantages that the solution of the first embodiment does not have. For example, in the user experience, in this embodiment, the user hardly perceives when using the cloud desktop service on the client side. The cloud desktop image file comes from the terminal. Because the cloud desktop service is still the server at this time, and the client only needs to accept the service, and does not need further processing. In this case, the storage device equivalent to the terminal acts as the “standby storage device” of the server, and for the client, whether the cloud desktop image file provides the server's primary storage device or the backup storage device has no effect. of. Therefore, the cloud desktop disaster recovery solution provided by this embodiment is more beneficial to the user experience.

S306. When the cloud desktop service file stored in the terminal is used to provide the cloud desktop service, save the modification record of the cloud desktop image file by the client.

Although the cloud desktop image file stored by the client terminal is used at this time, this is only a temporary process. After the cloud server host of the server and the storage device resume normal connection, the cloud server host will continue to use the server storage device. Cloud desktop image file. Therefore, in order to re-establish the record of the modification of the cloud desktop image file by the user when the cloud service host is connected to the local storage device again, a recording and modification mechanism is also provided in this embodiment. That is, when the cloud server host uses the cloud desktop image file stored by the client to provide the cloud desktop service to the client, the client changes the cloud desktop image file.

S308. When the user can use the cloud desktop service normally, the modification record is synchronized to the server.

When the storage link of the server is restored to normal, the previously recorded client-side modification of the cloud desktop image file is synchronized to the server. It can be understood that if the previous fault is only because the cloud server host cannot connect to its storage device, and the storage device itself is not faulty, the cloud desktop image file saved on it is still intact, then only the synchronization can be modified. Record, that is, the client's modification data to the cloud desktop image file, and if the previous failure is due to the server's storage device being broken, the cloud desktop image file stored on it is damaged, then the synchronization modification data mentioned here is not only The client only needs to modify the data of the cloud desktop image file in the process. In this case, the data of all the cloud desktop image files stored in the terminal may be synchronized to the server, including using the terminal cloud desktop image file. The cloud desktop service has modified data for the file and raw data of the previously cached cloud desktop image file. It should be understood that the purpose of the synchronization process is to make the server consistent with the cloud desktop image file corresponding to the client saved by the client.

In this embodiment, when the storage link of the server is back to normal, in order to allow the user to enjoy the cloud desktop service provided by the server in the normal manner as soon as possible, the modification of the cloud desktop image file by the client may be preferentially synchronized to the server. This process is the opposite of the client-cached cloud desktop image file. When the client caches the cloud desktop image file, the cache is used as the secondary process, and the synchronization process is used as the main process, which can preferentially enjoy the network bandwidth and disk read. Write resources such as functions. Of course, if the user is currently dealing with more important things, this priority principle may affect the user experience. Therefore, in this embodiment, it is possible to prioritize the synchronization of data. Ask the user. If the user agrees, the data of the client will be synchronized first. Otherwise, other processes will be allowed to occupy bandwidth and disk read and write, and data synchronization will be performed until there are remaining resources.

It can be understood that the flow of S306 and S308 is also applicable in the first embodiment. In the first embodiment, when it is known that the server can normally provide the cloud desktop service, the system can be switched in the system currently started by the client device, and the system boot program can be restored to the original desktop image stored by the client using the terminal. The previous version of the file, the MBR information is modified to the original MBR. Or make the relevant system boot information compatible with the original, that is, compatible with the original terminal operating system information in the relevant MBR information. At this time, the user can refer to the relevant boot of the original operating system after restarting, and enter the original operating system normally. After entering the original operating system, the user can choose to log in to the login interface of the original virtual cloud desktop.

After entering the original operating system, the user can enter the login interface of the virtual cloud desktop and enter the username and password of the virtual cloud desktop system for authentication. After the authentication is passed, the system determines that the cloud desktop image file cached by the client has data. Modify the record. At this time, the user can be prompted to synchronize the modified data about the cloud desktop image file to the server according to the user's selection. During the synchronization process, the system can prompt the user that data is currently being processed. After the synchronization is complete, the user can successfully log in to the server to perform normal operations in the cloud desktop system provided by the normal mode.

Undoubtedly, when users use the cloud desktop service again, they can use the free disk read and write capabilities and network bandwidth to synchronize the modifications made by the client to the server's cloud desktop image file to the terminal to deal with the next network. Interrupt or storage chain breakage.

The cloud desktop disaster recovery method provided in this embodiment is mainly directed to a storage accident in the server. When the cloud server host on the server cannot obtain the cloud desktop image file from the terminal to provide the cloud desktop service to the user, the cloud server host can By mounting to the terminal, the cloud desktop image file stored by the terminal is used to continue to provide the cloud desktop service to the user, and the solution can improve the user experience because the user is hardly perceived to change.

In this embodiment and the first embodiment, when the client uses the cloud desktop image file stored by the terminal, the client can record the modification of the image file, and the server can provide the cloud desktop normally. When the service is used, the client's modification of the cloud desktop image file is synchronized to the server, so that the image file data in the server is consistent with the image file in the client, so that the user is in the normal situation or in the normal situation. The same cloud desktop image file can be used after a network accident or a storage accident, minimizing the loss and inconvenience caused by the transition before and after the accident.

Embodiment 3:

This embodiment provides a client. Referring to FIG. 5, the client 50 includes a local calling module 502. The local calling module 502 is configured to invoke a cloud desktop image file stored in the terminal to provide a cloud to the user when the preset condition is met. Desktop service.

When the cloud desktop service is enabled on the server, the cloud desktop image file is cached to the terminal. When the server cannot provide the cloud desktop service, the cloud desktop image file stored in the terminal is used to provide the cloud desktop to the user. service.

The server usually includes a cloud server host and a storage device. In a cloud desktop disaster recovery system, there may be multiple clients 50. Therefore, the cloud desktop image file of multiple clients 50 should be stored on the storage device, which requires high storage space on the server. In this embodiment, the storage device may be a RAID (Redundant Arrays of Independent Disks) or a MAID (massive array of idle disks) composed of RAID. The cloud desktop image file of each client 50 exists in the form of a separate file on the storage device of the server. The format may be a VHD (Virtual Hard Disk Format) format.

The storage device on the server can be divided into a primary storage device and a backup storage device. In most cases, the primary storage device is in a working state to provide a cloud desktop service. When the server provides the cloud desktop service to the client 50, the cloud server host is mounted to the primary storage device, and the virtual mirror process is used to invoke the related image data of the client 50 in the storage device and continuously use the carrier. The provided network presents relevant images and user operational information to the client 50 in the form of a window.

As can be seen from the above process, the client 50 can normally use the cloud desktop service to meet at least two conditions: First, the cloud server host can be mounted on the primary storage device, That is to say, there is no possibility of a broken link between the cloud server host and the primary storage device. On the other hand, the network between the server and the client 50 must be kept clear, and no network interruption can occur. The network interruption includes network interruption caused by the failure of the server network port and problems caused by the network itself provided by the operator. failure.

As shown in FIG. 6, in order to ensure that a storage failure occurs on the server or a network failure occurs between the client 50 and the server, the user can still use the cloud desktop image file. Therefore, in an example of the embodiment, the client End 50 also includes a first cache module 504. When the cloud desktop service is normally provided by the server, the first cache module 504 may extract the cloud desktop image file required by the client in the server and cache the file to the terminal.

It can be understood that, because the cached cloud desktop image file requires a certain storage space, in this embodiment, a certain space is reserved in the terminal for storing the required cloud desktop image file. For the client 50, this requirement is not very difficult, because in terms of various terminals, there are generally dozens or even hundreds of GB of storage space in an idle state. Therefore, in this embodiment, the cloud desktop image file is cached to the client 50, and the idle resource is effectively utilized, thereby improving the resource utilization of the client device, and avoiding the capital consumption necessary for setting the standby resource on the server. In the above two aspects, the cloud desktop disaster recovery system provided in this embodiment implements optimal configuration of resources.

When the cloud desktop image file is cached, the network bandwidth and the local read/write port of the client 50 are required. In order to prevent the user from using the cloud desktop service provided by the server, the first cache module 504 may be used in this embodiment. The priority of the process of caching the cloud desktop image file is set to secondary. That is, the cache process is used as the secondary process. When the user's current operation needs to occupy network bandwidth or use the read/write capability of the local disk, the priority is given. Perform the user's current operational tasks. When there is remaining bandwidth or disk read/write capability, the first cache module 504 can continue to cache the cloud desktop image file. After the cache task ends, the first cache module 504 can notify the cache result to at least one of the server or the client 50. Preferably, the cached result is simultaneously notified to the client 50 and the server.

When the preset condition is met, the local calling module 502 calls the cloud desktop image stored in the terminal. The file provides the user with a cloud desktop service.

In fact, the situation that meets the preset conditions is that the client 50 cannot enjoy the cloud desktop service provided by the server through the normal manner. The preset condition in this embodiment may be at least one of the following two types, and of course, two conditions may be simultaneously satisfied:

First, the network connection between the server and the client 50 is interrupted.

Second, the cloud server host cannot be mounted to the storage device on the server side. That is, the cloud server cannot obtain the cloud desktop resources required by the client 50 from the server side.

For the problem that the client 50 cannot use the cloud desktop service provided by the server in the normal manner, the cloud desktop disaster recovery system in this embodiment proposes such a solution:

The local calling module 502 first performs format processing on the cached cloud desktop image file. This process can be done when the cloud desktop image file is just cached, or when the user needs to use the cloud desktop image file stored by the terminal. In this embodiment, in order to immediately switch to the cloud desktop image file stored by the terminal when the user cannot use the cloud desktop service provided by the server in the normal manner, without affecting the normal operation of the user, the local calling module 502 may The processing flow setting is completed after the cloud desktop image file cache is completed, which can reduce the user's waiting time and improve the user experience.

The processing of the cloud desktop image file by the local calling module 502 is mainly a process of recompiling the image file. Since the storage device on the server side of the cloud desktop image file is in the VHD format, and now needs to be used as an operating system, it is necessary to use it. It is formatted and re-encoded so that the client device can recognize that it is an operating system.

The local invocation module 502 also modifies the system boot information. In this case, the client device needs to be enabled with different operating systems. Therefore, you need to modify the system boot information of the terminal device, that is, you need to modify the MBR (Master Boot Record) of the original operating system. Information, this modification will take effect after the device is restarted. It can be understood that it is possible that the user does not currently need to use the cloud desktop image file very much, so even if the client 50 cannot currently use the cloud desktop service provided by the server in the normal way, it does not matter, so in this case, Under the user, the user may not need to enable the cloud desktop image stored by the terminal. It is more willing to wait for the network to be normal or the cloud server host and storage device to return to normal. Therefore, in order to fully maintain the user's will, the client 50 may send a prompt message to the user to use the cloud desktop image file cached by the local machine after the network connection is interrupted or the storage is broken, and the system boot information is modified. When the user chooses yes, the MBR and other related information is modified. In a preferred example of the embodiment, the local calling module 502 can also enable the cloud desktop image file cached by the client 50 terminal according to the user's instruction, that is, the user inputs a specific instruction when needed, and then The system boot program is modified, which greatly improves the user's autonomy.

The local calling module 502 loads the processed cloud desktop image file according to the modified system boot information, and obtains a cloud desktop system for providing a cloud desktop service for the user. After the system boot information is modified, the terminal device restarts. After the restart, the terminal device is booted into the system corresponding to the cloud desktop image file. At this time, the user can use the service provided by the cloud desktop image file again, but at this time the service provider is no longer the server, but the client 50 itself. And in this case, almost no server involvement is required.

In this embodiment, the client 50 may be disposed on various types of terminal devices, such as a PC, a tablet, a phone, etc., wherein the first cache module 504 in the client 50 may be configured by a processor and a communication unit of the terminal. Together with the memory, the processor controls the communication unit to obtain the cloud desktop image file from the server and then stores it in the memory. The local calling module 502 can be implemented by an output interface of the memory, and the local calling module 502 can also be implemented by a processor. When a network failure or a storage failure occurs, the processor of the terminal reads from the memory through the output interface of the memory. The cloud desktop image file is processed and loaded by the cloud desktop image file to obtain the cloud desktop system, and the cloud desktop service is continuously provided for the user.

The embodiment further provides a cloud desktop disaster recovery system, which includes a server and at least one client 50.

The client 50 and the cloud desktop disaster recovery system provided by the embodiments of the present disclosure can store the cloud desktop image file required by the client in the terminal, so that the client 50 can be stored according to the terminal when the network is faulty or the server is faulty. Cloud desktop image file provides users with cloud desktop The service enhances the reliability of the disaster recovery system and improves the disaster tolerance effect and user experience. Moreover, in the embodiment, the client 50 takes into account the current needs and wishes of the user before performing the cloud desktop image caching and the cloud desktop image file of the terminal, so that the cloud desktop disaster recovery system of the embodiment is more human. In line with the wishes of users.

Embodiment 4:

This embodiment provides a server and a client that are different from the embodiment. When the user can use the cloud desktop service normally, the client caches the cloud desktop image file that the user needs in the terminal. When the cloud desktop image file is stored on the service side, the cloud desktop image file stored in the terminal can be used to continue to provide services for the user.

Please refer to FIG. 7 and FIG. 8. FIG. 7 is a schematic structural diagram of a client provided in this embodiment, and FIG. 7 is a schematic structural diagram of a server provided in this embodiment:

The client 70 includes a second cache module 702, and the server 80 includes a remote call module 802.

The second cache module 702 is configured to: when the user can normally use the cloud desktop service provided by the server, extract the cloud desktop image file required by the client from the server and store the file in the terminal.

For the process of caching the cloud desktop image file in the second cache module 702 in this embodiment, refer to the process of caching the image file by the first cache module in the third embodiment, and details are not described herein again.

Different from the third embodiment, in the embodiment, the client 70 does not include the local calling module, but the remote calling module 802 is set in the server 80. When the cloud server host in the server 80 cannot obtain the cloud desktop image file stored in the terminal, the remote calling module 802 calls the cloud desktop image file stored in the terminal to provide the cloud desktop service for the client.

Although the cloud server host cannot obtain the cloud desktop image file required by the client 70 from the storage device of the server 80 at this time, since the network connection between the server 80 and the client 70 is still intact, the cloud server is still available. The host can be mounted to the storage directory of the cloud desktop image file stored on the client 70 through the network, and the cloud desktop service is continuously provided to the user.

When a storage incident occurs in the server 80, the remote calling module 802 controls the server host to mount to the device in the terminal that stores the cloud desktop image file. Server host mentioned here It is the cloud server host. Mounting refers to attaching a device to an existing directory. Then, the device can access the directory to access the device where the directory is located. In this embodiment, the cloud server host is connected to the storage cloud desktop image file in the storage directory of the storage cloud desktop image file, and then accesses the storage cloud desktop image file storage device. The device obtains the cloud desktop image file.

The remote invocation module 802 then controls the server host to continue to provide the cloud desktop service to the user by calling the cloud desktop image file through the network.

This embodiment further provides a cloud desktop disaster recovery system. Referring to FIG. 9 , the cloud desktop disaster recovery system 9 includes the server 80 and at least one client 70 provided in this embodiment. In the cloud desktop disaster recovery system 9 of the embodiment, the requirement for the network may be slightly higher than that of the cloud desktop image file of the terminal in the third embodiment. To ensure that the client 70 can normally use the cloud desktop service provided by the server 80, it is also ensured that the server 80 can smoothly obtain the cloud desktop image file from the client 70 through the network.

On the other hand, the cloud desktop disaster recovery system 9 provided in this embodiment has the advantages that the cloud desktop disaster recovery system provided by the third embodiment does not have. For example, in the user experience, in this embodiment, the user When the cloud desktop service is used by the client, the cloud desktop image file is hardly perceived to come from the terminal. Because the cloud desktop service is still the server 80 at this time, and the client 70 only needs to accept the service, and does not need further processing. In this case, the storage device corresponding to the terminal acts as the "alternate storage device" of the server 80, and for the client 70, whether the cloud desktop image file is provided is the primary storage device of the server 80 or the backup storage. The device has no effect. Therefore, the cloud desktop disaster recovery system 9 provided in this embodiment is more advantageous to the user experience.

In another preferred example in this embodiment, as shown in FIG. 10, the client 70 includes a second recording module 704 and a second synchronization module 706 in addition to the second cache module 702, and the second record. The module 704 is configured to save the modification record of the cloud desktop image file of the client when the cloud desktop service file is provided by the cloud desktop image file stored in the calling terminal. The second synchronization module 706 is configured to synchronize the previously saved modification record to the server 80 when the storage link of the server 80 returns to normal.

Although the cloud desktop image file stored in the terminal is used at this time, this is only a temporary process. After the cloud server host of the server 80 and the storage device resume normal connection, the cloud server host will continue to use the server 80 for storage. Cloud desktop image file on the device. Therefore, in order to re-connect the cloud service host to the storage device of the terminal, the previous record of the modification of the cloud desktop image file is continued. Therefore, in this embodiment, the second recording module 704 uses the client on the cloud server host. When the cloud desktop image file stored on the end provides the cloud desktop service for the client, the user's modification of the cloud desktop image file is recorded.

It can be understood that if the previous fault is only because the cloud server host cannot connect to its storage device, and the storage device itself is not faulty, the cloud desktop image file saved thereon is still intact, then the second synchronization module is still intact. 706 can only synchronize the modification data of the cloud desktop image file by the client, and if the previous failure is due to the storage device of the server being broken, the cloud desktop image file stored thereon is damaged, then the second synchronization module 706 synchronously modifies the data. The time is not only the modification data of the cloud desktop image file by the client in the process. In this case, the second synchronization module 706 may need to synchronize the data of all the cloud desktop image files stored in the terminal to the server. 80. The use of the terminal cloud desktop image file to provide the modified data of the file and the original data of the previously cached cloud desktop image file during the cloud desktop service. It should be understood that the second synchronization module 706 synchronizes the data with the purpose of making the server consistent with the cloud desktop image file corresponding to the client saved by the client.

In this embodiment, when the storage link of the server is returned to the normal state, in order to allow the client 70 to enjoy the cloud desktop service provided by the server 80 in the normal manner as soon as possible, the second synchronization module 706 can preferentially mirror the cloud desktop of the client 70. The modification of the file is synchronized to the server 80. This process is the opposite of the client 70 cache cloud desktop image file. When the client 70 caches the cloud desktop image file, the cache is regarded as a secondary process, and the synchronization process is used as the main process, which can preferentially enjoy the network bandwidth and the disk. Resources such as read and write functions. Of course, if the user is currently processing a more important thing, the priority principle may affect the user experience. Therefore, in this embodiment, the second synchronization module 706 may first query the user before prioritizing the data, if the user If you agree, the client's data will be synchronized first. Otherwise, other processes will be allowed to occupy bandwidth and disk read and write, and data synchronization will be performed when there are remaining resources.

In this embodiment, the client 70 can be disposed on various types of terminal devices, such as a PC, a tablet, a phone, etc., wherein the second cache module 702 in the client 70 can be shared by the processor and the memory of the terminal. Implementation, the processor obtains the cloud desktop image file from the server, and then stores it in the memory.

The server 80 in this embodiment is mainly implemented by a server, wherein the remote calling module 802 can be implemented by a processor of the server. When a network failure or a storage failure occurs, the processor of the server passes through the output interface of the memory. The cloud desktop image file is read in the memory of the device, and the cloud desktop service is provided to the end user through the network.

It can be understood that the client 50 in the third embodiment can also implement the modification record of the image file and the effect of synchronizing the modification to the server. As shown in FIG. 11, the client 50 includes a local invocation module 502, a first caching module 504, a first recording module 506, and a first synchronization module 508. In the third embodiment, when it is known that the server can normally provide the cloud desktop service, the system can be switched in the system currently started by the client device, and the system boot program can be restored to the client 50 or the client 70 using the terminal. The version of the original desktop image file that was stored is changed to the original MBR. Or make the relevant system boot information compatible with the original, that is, compatible with the original terminal operating system information in the relevant MBR information. At this time, the user can refer to the relevant boot of the original operating system after restarting, and enter the original operating system normally. After entering the original operating system, the user can choose to log in to the login interface of the original virtual cloud desktop.

After entering the original operating system, the user can enter the login interface of the virtual cloud desktop and enter the username and password of the virtual cloud desktop system for authentication. After the authentication is passed, the first synchronization module 508 or the second synchronization module 706 determines the client. The cloud desktop image file cached by the terminal 50 or the client 70 has a data modification record. At this time, the first synchronization module 508 or the second synchronization module 706 may prompt the user to synchronize the modification data about the cloud desktop image file to the server according to the user's selection. During the synchronization process, the first synchronization module 508 or the second synchronization module 706 can prompt the user that data is currently being processed. After the synchronization is complete, the user can successfully log in to the server to perform normal operations in the cloud desktop system provided by the normal mode.

There is no doubt that when users use the cloud desktop service again, they can use it again. The free disk read and write capability and the network bandwidth synchronize the modification made by the client 50 or the client 70 to the server's cloud desktop image file to the terminal to cope with the next network interruption or storage disconnection accident.

The second recording module 704 of the client 70 in the embodiment and the first recording module 506 of the client 50 in the third embodiment may be implemented by the terminal device processor, and the functions of the first synchronization module 508 and the second synchronization module 706 It can be implemented by a processor and a communication unit in the terminal.

The cloud desktop disaster recovery system provided in this embodiment is mainly for the storage incident of the server 80. When the cloud server host of the server 80 cannot obtain the cloud desktop image file from the terminal to provide the cloud desktop service for the user, the cloud The server host can continue to provide the cloud desktop service to the user by using the cloud desktop image file stored in the terminal, and the solution can improve the user experience because the user hardly perceives the change.

In this embodiment and the third embodiment, when the client uses the cloud desktop image file stored by the terminal, the client can modify the image file. When the server can provide the cloud desktop service normally, the client pair is used. The modification of the cloud desktop image file is synchronized to the server, so that the image file data in the server is consistent with the image file in the client, so that the user can use it under normal circumstances or after a network accident or a storage accident. Go to the same cloud desktop image file to minimize the loss and inconvenience caused by the transition before and after the accident.

Embodiment 5:

Embodiments of the present disclosure also provide a storage medium. Optionally, in the embodiment, the foregoing storage medium may be configured to store program code for performing the following steps:

S1: When the preset condition is met, the server invokes the cloud desktop image file stored in the terminal to provide the cloud desktop service to the user.

Optionally, the storage medium is further arranged to store program code for performing the following steps:

S1, controlling the server host to be mounted to a storage directory of the cloud desktop image file of the terminal;

S2. The cloud desktop image file is invoked through the network to continue providing the cloud desktop service to the user.

S1. When the preset condition is met, the client invokes the cloud desktop image file stored in the terminal to provide the cloud desktop service to the user.

S1. When the cloud desktop service provided by the server is used normally, the client extracts the required cloud desktop image file from the server and stores it locally.

S1, the client performs format processing on the cloud desktop image file.

S2, the client modifies system boot information;

S3, the client loads the processed cloud desktop image file according to the modified system boot information, and obtains a cloud desktop system for providing a cloud desktop service for the user.

S1, when the cloud desktop image file stored in the terminal is used to provide a cloud desktop service to the user, the client saves the modification record of the cloud desktop image file;

S2. When the cloud desktop service can be used normally again, the client synchronizes the modification record to the server.

Optionally, in this embodiment, the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory. A variety of media that can store program code, such as a disc or a disc.

Optionally, in this embodiment, the processor executes the method steps described in the foregoing embodiments according to the stored program code in the storage medium.

For example, the examples in this embodiment may refer to the examples described in the foregoing embodiments and the optional embodiments, and details are not described herein again.

Obviously, those skilled in the art should understand that the modules or steps of the above embodiments of the present disclosure may be implemented by a general computing device, which may be concentrated on a single computing device or distributed among multiple computing devices. On the network, optionally, they may be implemented by program code executable by the computing device, such that they may be stored in a storage medium (ROM/RAM, disk, optical disk) by a computing device, and in some In this case, the steps shown or described may be performed in an order different from that herein, or they may be separately fabricated into individual integrated circuit modules, or a plurality of the modules or steps may be implemented as a single integrated circuit module. Therefore, the present disclosure is not limited to any specific combination of hardware and software.

The above is a detailed description of the embodiments of the present disclosure in connection with the alternative embodiments, and the implementation of the present disclosure is not limited to the description. It is to be understood by those skilled in the art that the present invention may be construed as being limited to the scope of the present disclosure.

Industrial applicability

In the embodiment of the present disclosure, the cloud desktop image file is stored in the terminal in advance, and when the preset condition is met, the cloud desktop service is provided to the user by calling the cloud desktop image stored in the terminal. The cloud desktop disaster recovery method, the client, the server, the cloud desktop disaster recovery system, and the storage medium provided by the embodiments of the present disclosure not only make the disaster recovery for the cloud desktop service depend on the standby resources set by the server, such as the backup storage device. Or the backup network port, etc., and because the cloud desktop image file is stored on the client side, the client can be used normally regardless of the failure of the server storage device or the network interruption between the server and the client. Compared with the related disaster recovery solution, the service provided by the cloud desktop image file of the terminal storage enhances the reliability of the disaster recovery solution and improves the disaster recovery effect and user experience.

Claims

A cloud desktop disaster recovery method includes:

When the preset condition is met, the server invokes the cloud desktop image file stored in the terminal to provide the cloud desktop service to the user.
The cloud desktop disaster recovery method according to claim 1, wherein the server invokes the cloud desktop image file stored in the terminal to provide a cloud desktop service to the user, including the following:

The server host cannot obtain the cloud desktop resources required by the client from the storage device local to the server.
The cloud desktop disaster recovery method according to claim 1 or 2, wherein the server calls the cloud desktop image file stored in the terminal to provide a cloud desktop service for the user, including:

Controlling that the server host is mounted to a storage directory of the cloud desktop image file of the terminal;

The cloud desktop image file is invoked through the network to continue to provide the cloud desktop service to the user.
A cloud desktop disaster recovery method includes:

When the preset condition is met, the client invokes the cloud desktop image file stored in the terminal to provide the cloud desktop service to the user.
The cloud desktop disaster recovery method according to claim 4, wherein the client further includes: before the cloud desktop image file stored in the terminal provides the cloud desktop service to the user:

When the cloud desktop service provided by the server is normally used, the client extracts the required cloud desktop image file from the server and stores it locally.
The cloud desktop disaster recovery method according to claim 4, wherein the client invokes the cloud desktop image file stored in the terminal when at least one of the following preset conditions is met Provide cloud desktop services:

The network connection between the client and the server is interrupted;

The server host on the server side cannot obtain the required cloud desktop resource from the storage device on the server side.
The cloud desktop disaster recovery method according to any one of claims 4-6, wherein the client invoking the cloud desktop image file stored in the terminal to provide a cloud desktop service to the user includes:

The client performs format processing on the cloud desktop image file;

The client modifies system boot information;

The client loads the processed cloud desktop image file according to the modified system boot information to obtain a cloud desktop system for providing a cloud desktop service for the user.
The cloud desktop disaster recovery method according to any one of claims 4-6, further comprising:

The client saves the modification record of the cloud desktop image file when the cloud desktop service file is provided to the user by using the cloud desktop image file stored in the terminal;

When the cloud desktop service can be used normally again, the client synchronizes the modification record to the server.
A client that includes:

The local calling module is set to invoke the cloud desktop image file stored in the terminal to provide the cloud desktop service to the user when the preset condition is met.
A server that includes:

The remote calling module is configured to invoke a cloud desktop image file stored in the terminal to provide a cloud desktop service to the user when the preset condition is met.
A cloud desktop disaster recovery system, comprising a server and a client according to claim 9; or comprising a client and the server according to claim 10.
A storage medium comprising a stored program, wherein the program is executed to perform the method of any one of the preceding claims 1 to 3 or 4 to 8.