Virtualized desktop data rollback control method and device, equipment and storage medium

Abstract

A virtualized desktop data rollback control method, apparatus and device, and a storage medium, relating to the field of virtualized desktop control, comprising: controlling a virtualized desktop client to store target desktop data including historical desktop information and historical personalized information corresponding to a historical virtualized desktop to a local target storage area; when the to-be-virtualized desktop client receives new desktop information issued by the virtualized desktop server, the virtualized desktop client is controlled to store the new desktop information to a local target storage area, so that the virtualized desktop client performs desktop updating based on the new desktop information; when the desktop data rollback requirement exists, the virtual desktop client is controlled to delete the new desktop information in the local target storage area and is controlled to update the desktop based on the target desktop data, so that the desktop data rollback is realized, and the user experience is improved; wherein in the whole desktop updating period, the historical mirror image file corresponding to the historical desktop information is in an undeleted state.

Description

Technical Field

[0001] The present application relates to the technical field of virtualized desktop control, and in particular to a virtualized desktop data rollback control method, device, equipment and storage medium. Background Art

[0002] When using qcow2 (QEMUCopy On Write version 2, a high-efficiency disk image format) as the image file format of the virtualized desktop, an incremental image will be generated based on the copy-on-write (COW) feature of qcow2. The administrator can modify the desktop data on the virtualized desktop server and then send incremental data to the virtualized desktop client. After the incremental data is sent, the qcow2 image file on the client that contains the personalized data generated when the user previously used the desktop will be replaced by the newly sent incremental qcow2 image file. At this time, the desktop on the client will be completely consistent with the desktop template uniformly stored on the server.

[0003] In the above-mentioned desktop update scheme, there are often the following two problems that greatly affect the user experience: (1) Once the server modifies the desktop data improperly, the desktop will not be able to be accessed normally, and the desktop on the client will naturally also be unable to be accessed normally. At this time, if you want to repair the desktop, you need to first feedback to the administrator through the user, and the administrator will then return to the management desk to modify the desktop template and then re-issue the updated desktop to the client. It can be seen that this processing path is not only cumbersome and time-consuming, but also has a great impact on the user experience for user scenarios that require timely use. (2) The desktop on the client may actually contain personalized data generated by the user when using it. If the administrator does not notify the relevant users before issuing the updated desktop, so that personal data cannot be backed up in time, then once the updated desktop is issued, the personalized data that the user needs to keep will be lost, and then the user's personalized data will be almost difficult to retrieve, thereby affecting the user experience.

[0004] Therefore, how to improve the efficiency of virtualized desktop data rollback while ensuring that personalized data is not lost is an issue that needs to be addressed urgently. Summary of the invention

[0005] The present application provides a virtualized desktop data rollback control method, device, equipment and storage medium, which can effectively implement the rollback of virtualized desktop data to improve the rollback efficiency and ensure that personalized data will not be lost, thereby improving the user experience.

[0006] In a first aspect, an embodiment of the present application provides a virtualized desktop data rollback control method, the virtualized desktop data rollback control method comprising:

[0007] Controlling the virtualized desktop client to store target desktop data in a local target storage area, wherein the target desktop data includes historical desktop information sent by the virtualized desktop server and historical personalized information generated during the use of the historical virtualized desktop;

[0008] When the virtualized desktop client receives the new desktop information sent by the virtualized desktop server, the virtualized desktop client is controlled to store the new desktop information in a local target storage area, so that the virtualized desktop client can perform desktop update based on the new desktop information;

[0009] When a desktop data rollback requirement is detected, the virtualized desktop client is controlled to delete the new desktop information in the local target storage area, and the virtualized desktop client is controlled to perform a desktop update based on the target desktop data to implement desktop data rollback;

[0010] In the entire desktop update cycle, the historical image file corresponding to the historical desktop information is controlled to be in an undeleted state.

[0011] In combination with the first aspect, in one implementation, the virtualized desktop client is any one of a VOI client, an IDV client, and a VDI client.

[0012] In combination with the first aspect, in one implementation, controlling the historical image file corresponding to the historical desktop information to be in an undeleted state includes:

[0013] If the virtualized desktop client is a VOI client or an IDV client, the historical image file corresponding to the target desktop data is controlled to be retained locally so that the historical image file is in an undeleted state;

[0014] If the virtualized desktop client is a VDI client, the historical image file corresponding to the target desktop data is controlled to be retained in the virtualized desktop server, so that the historical image file is in an undeleted state.

[0015] In combination with the first aspect, in an implementation manner, after the step of waiting for the virtualized desktop client to receive the new desktop information sent by the virtualized desktop server, the method further includes:

[0016] The virtualized desktop client is controlled to migrate the target desktop data in the local target storage area to the local backup storage area for storage.

[0017] In combination with the first aspect, in one implementation, controlling the virtualized desktop client to delete the new desktop information in the local target storage area includes:

[0018] The virtualized desktop client is controlled to migrate the target desktop data in the local backup storage area to the local target storage area to cover the new desktop information, thereby deleting the new desktop information.

[0019] In combination with the first aspect, in one implementation, the historical desktop information includes a historical desktop unique identifier and historical image file information, and the new desktop information includes a new desktop unique identifier and new image file information, wherein the historical desktop unique identifier is the same as the new desktop unique identifier.

[0020] In a second aspect, an embodiment of the present application provides a virtualized desktop data rollback control device, the virtualized desktop data rollback control device comprising:

[0021] A first control module, which is used to control the virtualized desktop client to store target desktop data in a local target storage area, wherein the target desktop data includes historical desktop information sent by the virtualized desktop server and historical personalized information generated during the use of the historical virtualized desktop;

[0022] A second control module, which is used to control the virtualized desktop client to store the new desktop information in a local target storage area when the virtualized desktop client receives the new desktop information sent by the virtualized desktop server, so that the virtualized desktop client can perform desktop update based on the new desktop information;

[0023] A third control module is used to control the virtualized desktop client to delete the new desktop information in the local target storage area when a desktop data rollback requirement is detected, and to control the virtualized desktop client to perform desktop update based on the target desktop data to implement desktop data rollback;

[0024] In the entire desktop update cycle, the second control module is also used to control the historical image file corresponding to the historical desktop information to be in an undeleted state.

[0025] In combination with the second aspect, in one implementation, the virtualized desktop client is any one of a VOI client, an IDV client, and a VDI client.

[0026] In conjunction with the second aspect, in one implementation, the second control module is specifically configured to:

[0027] If the virtualized desktop client is a VOI client or an IDV client, the historical image file corresponding to the target desktop data is controlled to be retained locally so that the historical image file is in an undeleted state;

[0028] If the virtualized desktop client is a VDI client, the historical image file corresponding to the target desktop data is controlled to be retained in the virtualized desktop server, so that the historical image file is in an undeleted state.

[0029] In combination with the second aspect, in one implementation, the second control module is further used to: control the virtualized desktop client to migrate the target desktop data in the local target storage area to the local backup storage area for storage.

[0030] In combination with the second aspect, in one implementation, the third control module is specifically used to: control the virtualized desktop client to migrate the target desktop data in the local backup storage area to the local target storage area to overwrite the new desktop information, thereby deleting the new desktop information.

[0031] In combination with the second aspect, in one implementation, the historical desktop information includes a historical desktop unique identifier and historical image file information, and the new desktop information includes a new desktop unique identifier and new image file information, wherein the historical desktop unique identifier is the same as the new desktop unique identifier.

[0032] In a third aspect, an embodiment of the present application provides a virtualized desktop data rollback control device, wherein the virtualized desktop data rollback control device comprises a processor, a memory, and a virtualized desktop data rollback control program stored in the memory and executable by the processor, wherein when the virtualized desktop data rollback control program is executed by the processor, the steps of the aforementioned virtualized desktop data rollback control method are implemented.

[0033] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a virtualized desktop data rollback control program is stored, wherein when the virtualized desktop data rollback control program is executed by a processor, the steps of the aforementioned virtualized desktop data rollback control method are implemented.

[0034] The beneficial effects brought by the technical solution provided in the embodiments of the present application include:

[0035] The target desktop data including the historical desktop information sent by the virtual desktop server and the historical personalized information generated during the use of the historical virtual desktop are stored in the local target storage area by controlling the virtualized desktop client to provide a data basis for subsequent rollback; when the virtualized desktop client receives the new desktop information sent by the virtualized desktop server, it indicates that the user needs to update the entire virtualized desktop, so the virtualized desktop client is controlled to store the new desktop information in the local target storage area, so that the virtualized desktop client can perform desktop updates based on the new desktop information; wherein, during the entire desktop update cycle, the historical image file corresponding to the historical desktop information is controlled to be in an undeleted state, that is, the historical image file needs to be retained to provide a data basis for subsequent rollback; when a desktop data rollback requirement is detected, it indicates that there may be a problem with the new desktop or the user wants to retrieve the historical user data before the new desktop is sent, then the virtualized desktop client is controlled to delete the new desktop information in the local target storage area, and the virtualized desktop client is controlled to perform desktop updates based on the target desktop data to achieve desktop data rollback. It can be seen that through this application, the rollback of virtualized desktop data can be effectively realized without the need for management personnel to manage data and notify relevant personnel to back up data, so as to improve the rollback efficiency and ensure that personalized data will not be lost, thereby improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 This is a flow chart of an embodiment of a virtual desktop data rollback control method of the present application;

[0037] Figure 2 This is a schematic diagram of the hardware structure of a virtualized desktop data rollback control device involved in an embodiment of the present application. DETAILED DESCRIPTION

[0038] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0039] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0040] In a first aspect, an embodiment of the present application provides a virtualized desktop data rollback control method.

[0041] In one embodiment, referring to Figure 1 , Figure 1This is a flow chart of an embodiment of the virtual desktop data rollback control method of the present application. Figure 1 As shown, the virtualized desktop data rollback control method includes:

[0042] Step S10: Control the virtualized desktop client to store the target desktop data in the local target storage area, wherein the target desktop data includes the historical desktop information issued by the virtualized desktop server and the historical personalized information generated during the use of the historical virtualized desktop; wherein the historical desktop information includes the historical desktop unique identifier and the historical image file information.

[0043] Exemplarily, it should be noted that historical desktop information refers to desktop information sent by the virtualized desktop server during the historical update of the desktop. For example, if the second desktop update is required, the desktop information sent by the virtualized desktop server to the virtualized desktop client when the user performs the first desktop update is the historical desktop information, and the desktop updated based on the historical desktop information is the historical virtualized desktop; it can be understood that before the second desktop update, the historical virtualized desktop is the current virtualized desktop formed after the first desktop update, and the personalized data generated by the use of the historical virtualized desktop in the past time period is the historical personalized information; wherein, the desktop information includes but is not limited to the GUID used as the unique identifier of the desktop and the image file information, and the image file information includes but is not limited to the image file name and link relationship contained in the virtualized desktop; therefore, the historical desktop information includes the historical desktop GUID and historical image file information corresponding to the historical virtualized desktop. It can be seen that the target desktop data in this embodiment includes the historical desktop information sent by the virtualized desktop server and the historical personalized information generated during the use of the historical virtualized desktop.

[0044] Since the methods and principles of any desktop update and rollback are the same, for the sake of simplicity, the following embodiments will take the first desktop update as a historical desktop update and the second desktop update as a new desktop update as an example to illustrate the methods and principles of desktop update and rollback.

[0045] Based on this, the user will select the corresponding target virtualized desktop for the first time through the virtualized desktop server and send it to the virtualized desktop client, and the historical desktop information sent includes the GUID of the target virtualized desktop and the historical image file information contained in the target virtualized desktop; after the virtualized desktop client receives the command to send the desktop sent by the virtualized desktop server, that is, after obtaining the historical desktop data, it will implement the first desktop update based on the historical image file and historical desktop information, thereby generating a historical virtualized desktop; at the same time, the historical desktop information is stored in the local target storage area to realize the recording of the historical desktop information. At this point, the virtualized desktop client has a local copy of the historical desktop information. It should be noted that the local target storage area can be any customized storage area for storing data, which is not limited here.

[0046] In addition, when the user uses the historical virtualized desktop, the temporary image file information corresponding to the user data generated by the user (ie, the historical personalized information) will also be updated and recorded in the local historical desktop information to form the target desktop data.

[0047] Furthermore, in one embodiment, the virtualized desktop client is any one of a VOI client, an IDV client and a VDI client.

[0048] By way of example, in this embodiment, the virtualized desktop can be a VOI (Virtual Operating Infrastructure) desktop, an IDV (Intelligent Desktop Virtualization) desktop, or a VDI (Virtual Desktop Infrastructure) desktop, without limitation herein; based on this, the virtualized desktop clients correspond to VOI clients, IDV clients, and VDI clients, respectively, and the above-mentioned various types of clients can provide a data basis for subsequent desktop data rollback based on the desktop data storage solution provided in this embodiment, so as to realize data rollback of different types of desktops.

[0049] Step S20: When the virtualized desktop client receives the new desktop information sent by the virtualized desktop server, the virtualized desktop client is controlled to store the new desktop information in the local target storage area so that the virtualized desktop client can perform desktop update based on the new desktop information; wherein, during the entire desktop update cycle, the historical image file corresponding to the historical desktop information is controlled to be in an undeleted state; the new desktop information includes a new desktop unique identifier and new image file information, and the historical desktop unique identifier is the same as the new desktop unique identifier.

[0050] Exemplarily, in this embodiment, when the user needs to re-update the entire virtualized desktop (i.e., perform a second desktop update), the virtualized desktop server will send a new desktop update to the virtualized desktop client. At this time, the new desktop GUID contained in the new desktop information sent is the same as the historical desktop GUID, that is, the desktop GUID remains unchanged, but the new image file information contained therein is different from the historical image file information, that is, the new image file information will change. After the virtualized desktop client receives the command to send the desktop sent by the virtualization server, it will implement the second desktop update according to the new image file and the new desktop information, thereby generating the current virtualized desktop; at the same time, the new desktop information is stored in the local target storage area to record the new desktop information, so that the virtualized desktop client has a new desktop information locally. In addition, a rollback operation corresponding to the historical virtualized desktop may be required for various reasons later. Therefore, in order to ensure that the rollback operation corresponding to the historical virtualized desktop can be successfully executed, this embodiment will retain the historical image file during the entire desktop update cycle, that is, the historical image file will not be deleted, even if the historical image file is in an undeleted state.

[0051] Further, in one embodiment, the controlling the historical image file corresponding to the historical desktop information to be in an undeleted state includes:

[0052] If the virtualized desktop client is a VOI client or an IDV client, the historical image file corresponding to the target desktop data is controlled to be retained locally so that the historical image file is in an undeleted state;

[0053] If the virtualized desktop client is a VDI client, the historical image file corresponding to the target desktop data is controlled to be retained in the virtualized desktop server, so that the historical image file is in an undeleted state.

[0054] Exemplarily, in this embodiment, for a VOI client or IDV client, it can download the historical image file corresponding to the historical image file information to the local computer through BT (a file distribution protocol based on peer-to-peer technology) or broadcast, and then implement desktop update based on the historical image file; it should be understood that when the desktop is updated based on the new image file, the historical image file will always be retained locally, that is, it is always in an undeleted state. Therefore, once a rollback operation is performed, the desktop data rollback can be implemented based on the historical image file and historical desktop information stored locally.

[0055] For the VDI client, it directly implements desktop updates through the historical image files stored in the VDI server. Therefore, when the user needs to update the desktop for the second time, the VDI server will retain the historical image files, that is, the VDI server will control the historical image files to remain in an undeleted state, so when generating new desktop information, it will not delete the historical image files. Therefore, once a rollback operation is performed, the desktop can be rolled back based on the historical image files stored in the VDI server and the historical desktop information stored locally.

[0056] Furthermore, in one embodiment, after the step of waiting for the virtualized desktop client to receive the new desktop information sent by the virtualized desktop server, the step further includes:

[0057] The virtualized desktop client is controlled to migrate the target desktop data in the local target storage area to the local backup storage area for storage.

[0058] Exemplarily, in this embodiment, in order to facilitate data management and maintenance, the new and old desktop data can be partitioned and stored. Specifically, after the virtualized desktop client receives the command to send the desktop sent by the virtualized server, it will find the target desktop data containing the historical desktop information from the local target storage area according to the desktop GUID in the new desktop information, and migrate the target desktop data to the local backup storage area for storage, so as to realize the backup of the historical desktop information and the historical personalized information; at the same time, the new desktop information is stored in the local target storage area to realize the recording of the new desktop information; it should be noted that the local backup storage area can be any customized storage area for storing data, which is not limited here, as long as the local backup storage area is used to store historical data and the local target storage area is used to store new data. It can be seen that for the virtualized desktop client, two copies of the new and old desktop information will be stored locally at the same time, wherein the new desktop information is used to update the current desktop, and the old desktop information is used to roll back the historical desktop.

[0059] Step S30: When a desktop data rollback requirement is detected, the virtualized desktop client is controlled to delete the new desktop information in the local target storage area, and the virtualized desktop client is controlled to perform a desktop update based on the target desktop data to implement desktop data rollback.

[0060] Exemplarily, in this embodiment, when the user finds that there is a problem with the newly issued desktop or simply wants to retrieve the user data before the new desktop is issued, the user can use the "rollback" function of the virtualized desktop client to indicate the existence of a desktop data rollback requirement; in other words, when the user executes the "rollback" function, it indicates that there is a desktop data rollback requirement, that is, there may be a problem with the new desktop or the user wants to retrieve the historical user data before the new desktop is issued. In this case, the desktop data needs to be rolled back, that is, the virtualized desktop client will find the previously backed up target desktop data corresponding to the desktop GUID to be executed, and delete the new desktop information stored in the local target storage area to update the desktop based on the target desktop data, thereby implementing desktop data rollback. After the user re-enters the desktop, the desktop will be written back to the state before the new desktop information was issued. It can be seen that this embodiment can effectively implement the rollback of virtualized desktop data without the need for data management by management personnel or notifying relevant personnel to perform data backup, so as to improve the rollback efficiency and ensure that personalized data will not be lost, thereby improving the user experience.

[0061] Further, in one embodiment, the controlling the virtualized desktop client to delete the new desktop information in the local target storage area includes:

[0062] The virtualized desktop client is controlled to migrate the target desktop data in the local backup storage area to the local target storage area to cover the new desktop information, thereby deleting the new desktop information.

[0063] Exemplarily, in this embodiment, for the scenario of executing partitioned storage of old and new data, when performing desktop data rollback, the corresponding target desktop data can be found from the local backup storage area according to the desktop GUID to be executed, and then the target desktop data can be migrated to the local target storage area to overwrite the new desktop information, thereby achieving the deletion of the new desktop information; it should be noted that for the VOI client or IDV client, when overwriting the target desktop data with the new desktop information, it may preferably clear the local image files that do not belong to this historical virtual desktop, that is, delete the new image files from the local; and for the VDI client, when updating the desktop based on the target desktop data, the VDI server may preferably delete the new image files it has saved to avoid unnecessary or problematic image files occupying memory space.

[0064] In summary, this embodiment provides a method for rolling back the desktop data state to the state before the update to fundamentally solve the problem, that is, when the user sends an update to the existing virtualized desktop through the virtualized desktop server, the virtualized desktop client will record the historical desktop information and historical personalized information before the issuance, and back them up to a specific area, while retaining the relevant historical image files so that they are not overwritten by the data after the issuance, and after the issuance is completed, the new desktop information will also be recorded at the same time, so that there are two copies of desktop information for one desktop at the same time and they can be stored in different areas respectively; the user can use the new desktop information and the corresponding image file when using the desktop normally, and when the user wants to restore to the desktop data state before the issuance, the virtualized desktop client can overwrite the previously backed up historical desktop information to the area of ​​the current desktop information, and the corresponding desktop image file is also the previous one; therefore, when the user enters the virtualized desktop again, the desktop data state is the state before the update is issued, so that the purpose of desktop data rollback can be effectively achieved.

[0065] In a second aspect, an embodiment of the present application also provides a virtualized desktop data rollback control device.

[0066] In one embodiment, the virtualized desktop data rollback control device includes:

[0067] A first control module, which is used to control the virtualized desktop client to store target desktop data in a local target storage area, wherein the target desktop data includes historical desktop information sent by the virtualized desktop server and historical personalized information generated during the use of the historical virtualized desktop;

[0068] A second control module, which is used to control the virtualized desktop client to store the new desktop information in a local target storage area when the virtualized desktop client receives the new desktop information sent by the virtualized desktop server, so that the virtualized desktop client can perform desktop update based on the new desktop information;

[0069] A third control module is used to control the virtualized desktop client to delete the new desktop information in the local target storage area when a desktop data rollback requirement is detected, and to control the virtualized desktop client to perform desktop update based on the target desktop data to implement desktop data rollback;

[0070] In the entire desktop update cycle, the second control module is also used to control the historical image file corresponding to the historical desktop information to be in an undeleted state.

[0071] Furthermore, in one embodiment, the virtualized desktop client is any one of a VOI client, an IDV client and a VDI client.

[0072] Furthermore, in one embodiment, the second control module is specifically configured to:

[0073] If the virtualized desktop client is a VOI client or an IDV client, the historical image file corresponding to the target desktop data is controlled to be retained locally so that the historical image file is in an undeleted state;

[0074] If the virtualized desktop client is a VDI client, the historical image file corresponding to the target desktop data is controlled to be retained in the virtualized desktop server, so that the historical image file is in an undeleted state.

[0075] Furthermore, in one embodiment, the second control module is further used to: control the virtualized desktop client to migrate the target desktop data in the local target storage area to the local backup storage area for storage.

[0076] Furthermore, in one embodiment, the third control module is specifically used to control the virtualized desktop client to migrate the target desktop data in the local backup storage area to the local target storage area to overwrite the new desktop information, thereby deleting the new desktop information.

[0077] Furthermore, in one embodiment, the historical desktop information includes a historical desktop unique identifier and historical image file information, and the new desktop information includes a new desktop unique identifier and new image file information, wherein the historical desktop unique identifier is the same as the new desktop unique identifier.

[0078] Among them, the functional implementation of each module in the above-mentioned virtualized desktop data rollback control device corresponds to the various steps in the above-mentioned virtualized desktop data rollback control method embodiment, and its functions and implementation processes are no longer repeated here.

[0079] In a third aspect, an embodiment of the present application provides a virtualized desktop data rollback control device, which may be a personal computer (PC), a laptop computer, a server, or other device having a data processing function.

[0080] Reference Figure 2 , Figure 2 Schematic diagram of the hardware structure of the virtualized desktop data rollback control device involved in the embodiment of the present application. In the embodiment of the present application, the virtualized desktop data rollback control device may include a processor, a memory, a communication interface and a communication bus.

[0081] The communication bus may be of any type and is used to interconnect the processor, the memory, and the communication interface.

[0082] The communication interface includes an input / output (I / O) interface, a physical interface, and a logical interface, etc., which are used to interconnect the devices inside the virtualized desktop data rollback control device, and an interface used to interconnect the virtualized desktop data rollback control device with other devices (such as other computing devices or user devices). The physical interface can be an Ethernet interface, a fiber optic interface, an ATM interface, etc.; the user device can be a display, a keyboard, etc.

[0083] The memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical storage, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.

[0084] The processor may be a general-purpose processor, and the general-purpose processor may call the virtualized desktop data rollback control program stored in the memory and execute the virtualized desktop data rollback control method provided in the embodiment of the present application. For example, the general-purpose processor may be a central processing unit (CPU). The method executed when the virtualized desktop data rollback control program is called may refer to the various embodiments of the virtualized desktop data rollback control method of the present application, and will not be described in detail here.

[0085] Those skilled in the art will understand that Figure 2 The hardware structure shown in the figure does not constitute a limitation on the present application, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.

[0086] In a fourth aspect, an embodiment of the present application also provides a computer-readable storage medium.

[0087] A virtualized desktop data rollback control program is stored on a readable storage medium of the present application, wherein when the virtualized desktop data rollback control program is executed by a processor, the steps of the virtualized desktop data rollback control method as described above are implemented.

[0088] Among them, the method implemented when the virtualized desktop data rollback control program is executed can refer to the various embodiments of the virtualized desktop data rollback control method of the present application, and will not be repeated here.

[0089] It should be noted that the serial numbers of the above-mentioned embodiments of the present application are only for description and do not represent the advantages or disadvantages of the embodiments.

[0090] The terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices. The terms "first", "second" and "third" are used to distinguish different objects, etc., and do not represent a sequence, nor do they limit "first", "second" and "third" to different types.

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

[0092] In the description of the embodiments of the present application, unless otherwise specified, “ / ” means or, for example, A / B can mean A or B; the “and / or” in the text is merely a description of the association relationship of associated objects, indicating that three relationships may exist, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, “multiple” refers to two or more than two.

[0093] In some processes described in the embodiments of the present application, multiple operations or steps that appear in a specific order are included, but it should be understood that these operations or steps may not be executed in the order in which they appear in the embodiments of the present application or in parallel, and the sequence number of the operation is only used to distinguish the different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed in sequence or in parallel, and these operations or steps may be combined.

[0094] 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 is essentially 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, disk, CD) as described above, and includes a number of instructions for a terminal device to execute the methods described in each embodiment of the present application.

[0095] 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 virtual desktop data rollback control method, characterized in that: The virtualized desktop data rollback control method includes: Controlling the virtualized desktop client to store target desktop data in a local target storage area, wherein the target desktop data includes historical desktop information sent by the virtualized desktop server and historical personalized information generated during the use of the historical virtualized desktop; When the virtualized desktop client receives the new desktop information sent by the virtualized desktop server, the virtualized desktop client is controlled to store the new desktop information in a local target storage area, so that the virtualized desktop client can perform desktop update based on the new desktop information; When a desktop data rollback requirement is detected, the virtualized desktop client is controlled to delete the new desktop information in the local target storage area, and the virtualized desktop client is controlled to perform a desktop update based on the target desktop data to implement desktop data rollback; In the entire desktop update cycle, the historical image file corresponding to the historical desktop information is controlled to be in an undeleted state.

2. The virtualized desktop data rollback control method according to claim 1, characterized in that: The virtualized desktop client is any one of a VOI client, an IDV client and a VDI client.

3. The virtualized desktop data rollback control method according to claim 2, characterized in that: The controlling the historical image file corresponding to the historical desktop information to be in an undeleted state includes: If the virtualized desktop client is a VOI client or an IDV client, the historical image file corresponding to the target desktop data is controlled to be retained locally so that the historical image file is in an undeleted state; If the virtualized desktop client is a VDI client, the historical image file corresponding to the target desktop data is controlled to be retained in the virtualized desktop server, so that the historical image file is in an undeleted state.

4. The virtualized desktop data rollback control method according to claim 1, characterized in that: After the step of waiting for the virtualized desktop client to receive the new desktop information sent by the virtualized desktop server, the method further includes: The virtualized desktop client is controlled to migrate the target desktop data in the local target storage area to the local backup storage area for storage.

5. The virtualized desktop data rollback control method according to claim 4, characterized in that: The controlling the virtualized desktop client to delete the new desktop information in the local target storage area includes: The virtualized desktop client is controlled to migrate the target desktop data in the local backup storage area to the local target storage area to cover the new desktop information, thereby deleting the new desktop information.

6. The virtualized desktop data rollback control method according to claim 1, characterized in that: The historical desktop information includes a historical desktop unique identifier and historical image file information, and the new desktop information includes a new desktop unique identifier and new image file information, wherein the historical desktop unique identifier is the same as the new desktop unique identifier.

7. A virtual desktop data rollback control device, characterized in that: The virtualized desktop data rollback control device comprises: A first control module, which is used to control the virtualized desktop client to store target desktop data in a local target storage area, wherein the target desktop data includes historical desktop information sent by the virtualized desktop server and historical personalized information generated during the use of the historical virtualized desktop; A second control module, which is used to control the virtualized desktop client to store the new desktop information in a local target storage area when the virtualized desktop client receives the new desktop information sent by the virtualized desktop server, so that the virtualized desktop client can perform desktop update based on the new desktop information; A third control module is used to control the virtualized desktop client to delete the new desktop information in the local target storage area when a desktop data rollback requirement is detected, and to control the virtualized desktop client to perform desktop update based on the target desktop data to implement desktop data rollback; In the entire desktop update cycle, the second control module is also used to control the historical image file corresponding to the historical desktop information to be in an undeleted state.

8. The virtual desktop data rollback control device according to claim 7, characterized in that: The virtualized desktop client is any one of a VOI client, an IDV client and a VDI client.

9. A virtualized desktop data rollback control device, characterized in that: The virtualized desktop data rollback control device includes a processor, a memory, and a virtualized desktop data rollback control program stored in the memory and executable by the processor, wherein when the virtualized desktop data rollback control program is executed by the processor, the steps of the virtualized desktop data rollback control method as described in any one of claims 1 to 6 are implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a virtualized desktop data rollback control program, wherein when the virtualized desktop data rollback control program is executed by a processor, the steps of the virtualized desktop data rollback control method according to any one of claims 1 to 6 are implemented.

Images