WO2017215502A1 - Procédé de reprise après problème grave de bureau en nuage, client, serveur, système de reprise après problème grave de bureau en nuage et support d'informations - Google Patents

Procédé de reprise après problème grave de bureau en nuage, client, serveur, système de reprise après problème grave de bureau en nuage et support d'informations Download PDF

Info

Publication number
WO2017215502A1
WO2017215502A1 PCT/CN2017/087463 CN2017087463W WO2017215502A1 WO 2017215502 A1 WO2017215502 A1 WO 2017215502A1 CN 2017087463 W CN2017087463 W CN 2017087463W WO 2017215502 A1 WO2017215502 A1 WO 2017215502A1
Authority
WO
WIPO (PCT)
Prior art keywords
cloud desktop
server
client
image file
cloud
Prior art date
Application number
PCT/CN2017/087463
Other languages
English (en)
Chinese (zh)
Inventor
邱海军
沈松
宋伊漠
李锴
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2017215502A1 publication Critical patent/WO2017215502A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/131—Protocols for games, networked simulations or virtual reality

Definitions

  • 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.
  • Virtual cloud desktops use the computing resources of remote servers as much as possible in the case of weakening user terminals.
  • 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.
  • 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.
  • the disaster recovery solution for the virtual cloud desktop storage generally sets the standby resources on the server side.
  • 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.
  • 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.
  • the related art 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.
  • the cost requirement of the disaster recovery solution by setting up the backup storage device is relatively high.
  • 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.
  • an alternate storage device is set on the cloud server side, there are still other problems.
  • 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.
  • the cloud desktop disaster recovery method, the client, the server, the cloud desktop disaster recovery system, and the storage medium 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.
  • the embodiment of the present disclosure provides a cloud desktop disaster recovery method, including:
  • 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:
  • 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.
  • 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.
  • FIG. 1 is a flowchart of a cloud desktop disaster recovery method according to Embodiment 1 of the present disclosure
  • FIG. 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
  • FIG. 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.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • the present embodiment proposes a cloud desktop capacity. Disaster method.
  • the client invokes the cloud desktop image file stored in the terminal to provide the cloud desktop service to the user.
  • 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:
  • the network connection between the server and the client is interrupted.
  • 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.
  • the preset condition should include other faults, such as a power outage at the server end.
  • 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:
  • 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.
  • 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.
  • 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.
  • the primary storage device is in a working state to provide a cloud desktop service.
  • 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.
  • 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.
  • the terminal is required to reserve a certain space for storing the cloud desktop image file that it needs.
  • 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.
  • the cloud desktop image file before the cloud desktop image file is cached, the cloud desktop image file needs to be occupied by the cloud desktop image file.
  • 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.
  • 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.
  • 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.
  • the client invokes the cloud desktop image file stored in the terminal to provide the cloud desktop service to the user.
  • 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.
  • 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.
  • the client modifies system boot information.
  • 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.
  • MBR Master Boot Record
  • 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.
  • the MBR and other related information is modified.
  • 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.
  • 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.
  • 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 is a diagrammatic representation of Embodiment 1:
  • the client 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.
  • the cloud desktop disaster recovery method provided in this embodiment can provide another solution. Please refer to FIG. 3:
  • the cloud desktop image file required by the client is extracted from the server and stored in the terminal.
  • the server invokes a cloud desktop image file stored in the terminal to provide a cloud desktop service for the user.
  • 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:
  • 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.
  • 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.
  • 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.
  • this solution has the advantages that the solution of the first embodiment does not have.
  • the user 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the client caches the cloud desktop image file
  • the cache is used as the secondary process
  • the synchronization process is used as the main process, which can preferentially enjoy the network bandwidth and disk read.
  • Write resources such as functions.
  • 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.
  • the flow of S306 and S308 is also applicable in the first embodiment.
  • the system 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.
  • 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.
  • 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.
  • the user 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.
  • the cloud desktop disaster recovery method provided in this embodiment is mainly directed to a storage accident in the server.
  • 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.
  • the client 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.
  • 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 is a diagrammatic representation of Embodiment 3
  • 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 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.
  • the cloud desktop image file is cached to the terminal.
  • 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.
  • 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.
  • 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.
  • the primary storage device is in a working state to provide a cloud desktop service.
  • 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.
  • 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.
  • the client End 50 also includes a first cache module 504.
  • 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.
  • the cloud desktop image file requires a certain storage space
  • a certain space is reserved in the terminal for storing the required cloud desktop image file.
  • 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.
  • the cloud desktop disaster recovery system provided in this embodiment implements optimal configuration of resources.
  • 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.
  • the priority is given.
  • 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.
  • the local calling module 502 calls the cloud desktop image stored in the terminal.
  • the file provides the user with a cloud desktop service.
  • 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:
  • the network connection between the server and the client 50 is interrupted.
  • 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.
  • 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.
  • 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.
  • MBR Master Boot Record
  • 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.
  • 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.
  • the MBR and other related information is modified.
  • 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.
  • the terminal device restarts. After the restart, the terminal device is booted into the system corresponding to the cloud desktop image file.
  • 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.
  • 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.
  • 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.
  • 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 is a diagrammatic representation of Embodiment 4:
  • This embodiment provides a server and a client that are different from the embodiment.
  • the client caches the cloud desktop image file that the user needs in the terminal.
  • 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.
  • FIG. 7 is a schematic structural diagram of a client provided in this embodiment
  • 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.
  • the client 70 does not include the local calling module, but the remote calling module 802 is set in the server 80.
  • the remote calling module 802 calls the cloud desktop image file stored in the terminal to provide the cloud desktop service for the client.
  • 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.
  • 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.
  • 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.
  • the cloud desktop disaster recovery system 9 includes the server 80 and at least one client 70 provided in this 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.
  • the server 80 can smoothly obtain the cloud desktop image file from the client 70 through the network.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the second synchronization module 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 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.
  • 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.
  • 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.
  • the priority principle may affect the user experience.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the user 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the client when the client uses the cloud desktop image file stored by the terminal, the client can modify the image file.
  • 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 is a diagrammatic representation of Embodiment 5:
  • Embodiments of the present disclosure also provide a storage medium.
  • the foregoing storage medium may be configured to store program code for performing the following steps:
  • the storage medium is further arranged to store program code for performing the following steps:
  • the cloud desktop image file is invoked through the network to continue providing the cloud desktop service to the user.
  • the storage medium is further arranged to store program code for performing the following steps:
  • the client invokes the cloud desktop image file stored in the terminal to provide the cloud desktop service to the user.
  • the storage medium is further arranged to store program code for performing the following steps:
  • the client extracts the required cloud desktop image file from the server and stores it locally.
  • the storage medium is further arranged to store program code for performing the following steps:
  • the client performs format processing on the cloud desktop image file.
  • 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.
  • the storage medium is further arranged to store program code for performing the following steps:
  • the client synchronizes the modification record to the server.
  • 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.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • a mobile hard disk e.g., a hard disk
  • magnetic memory e.g., a hard disk
  • the processor executes the method steps described in the foregoing embodiments according to the stored program code in the storage medium.
  • 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.
  • 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
  • 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 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

La présente invention concerne, selon des modes de réalisation, un procédé de reprise après problème grave de bureau en nuage, un client, un serveur, un système de reprise après problème grave de bureau en nuage et un support d'informations, consistant à pré-stocker sur un terminal un fichier image du bureau en nuage ; lorsque des conditions prédéterminées sont satisfaites, à fournir un service de bureau en nuage à un utilisateur au moyen de l'appel de l'image de bureau en nuage stockée sur le terminal. La solution de reprise après problème grave de bureau en nuage fournie par les modes de réalisation de la présente invention est telle que non seulement il n'est pas nécessaire que le service de bureau en nuage dépende d'une ressource de sauvegarde sur un serveur, mais étant donné que le fichier image de bureau en nuage est stocké côté client, il est possible de s'assurer que le client peut utiliser normalement le service fourni sur la base du fichier image de bureau en nuage stocké sur le terminal, indépendamment du fait qu'il existe une défaillance sur le dispositif de stockage de serveur ou une interruption de réseau entre le serveur et le client ; en comparaison avec des solutions de reprise après problème grave associées, la présente solution présente une fiabilité, des performances de reprise après problème grave et une expérience d'utilisateur améliorées.
PCT/CN2017/087463 2016-06-17 2017-06-07 Procédé de reprise après problème grave de bureau en nuage, client, serveur, système de reprise après problème grave de bureau en nuage et support d'informations WO2017215502A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610439102.2 2016-06-17
CN201610439102.2A CN107517192A (zh) 2016-06-17 2016-06-17 云桌面容灾方法、客户端、服务端及云桌面容灾系统

Publications (1)

Publication Number Publication Date
WO2017215502A1 true WO2017215502A1 (fr) 2017-12-21

Family

ID=60663195

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/087463 WO2017215502A1 (fr) 2016-06-17 2017-06-07 Procédé de reprise après problème grave de bureau en nuage, client, serveur, système de reprise après problème grave de bureau en nuage et support d'informations

Country Status (2)

Country Link
CN (1) CN107517192A (fr)
WO (1) WO2017215502A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110990124A (zh) * 2019-12-10 2020-04-10 北京京东尚科信息技术有限公司 云主机恢复方法和装置
CN114253651A (zh) * 2021-12-29 2022-03-29 南京机敏软件科技有限公司 一种云桌面客户端远程运维的方法、存储介质及处理器

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107995318A (zh) * 2018-01-04 2018-05-04 西安雷风电子科技有限公司 一种网络云盘的高可用系统
CN110808943B (zh) * 2018-08-06 2022-04-29 中兴通讯股份有限公司 客户端连接应急管理方法、客户端及计算机可读存储介质
CN110928624A (zh) * 2019-11-15 2020-03-27 联思智云(北京)科技有限公司 用于用户终端的云桌面调用方法、装置及终端
CN111031098B (zh) * 2019-11-20 2022-04-26 西安雷风电子科技有限公司 一种vdi云桌面应急维护系统及方法
CN112486608A (zh) * 2020-11-25 2021-03-12 北京和信创天科技股份有限公司 一种云桌面硬盘、网络双待机实现方法
CN114257585A (zh) * 2021-12-22 2022-03-29 天翼云科技有限公司 一种网络访问方法、装置、设备及介质
CN116841660A (zh) * 2022-03-23 2023-10-03 中兴通讯股份有限公司 数据传输方法、云桌面虚拟机、云终端及可读存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103593227A (zh) * 2013-11-08 2014-02-19 何钦淋 在客户端运行桌面虚拟系统的方法及客户端
CN103747095A (zh) * 2014-01-21 2014-04-23 上海江南长兴重工有限责任公司 一种虚拟桌面系统及方法
US20140188982A1 (en) * 2012-12-29 2014-07-03 Futurewei Technologies, Inc. Virtual Desktop Infrastructure (VDI) Login Acceleration
CN104158833A (zh) * 2013-05-14 2014-11-19 上海国富光启云计算科技有限公司 一种智能桌面系统的构建方法
US20150304433A1 (en) * 2014-04-18 2015-10-22 Vmware, Inc. Gesture based switching of virtual desktop clients

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103218248B (zh) * 2013-03-25 2016-12-28 华为技术有限公司 一种虚拟机镜像的更新方法、服务器和桌面云系统
CN104580399B (zh) * 2014-12-19 2018-04-27 华南理工大学 一种基于OpenStack和Spice的云桌面实现方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140188982A1 (en) * 2012-12-29 2014-07-03 Futurewei Technologies, Inc. Virtual Desktop Infrastructure (VDI) Login Acceleration
CN104158833A (zh) * 2013-05-14 2014-11-19 上海国富光启云计算科技有限公司 一种智能桌面系统的构建方法
CN103593227A (zh) * 2013-11-08 2014-02-19 何钦淋 在客户端运行桌面虚拟系统的方法及客户端
CN103747095A (zh) * 2014-01-21 2014-04-23 上海江南长兴重工有限责任公司 一种虚拟桌面系统及方法
US20150304433A1 (en) * 2014-04-18 2015-10-22 Vmware, Inc. Gesture based switching of virtual desktop clients

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110990124A (zh) * 2019-12-10 2020-04-10 北京京东尚科信息技术有限公司 云主机恢复方法和装置
CN110990124B (zh) * 2019-12-10 2024-04-12 北京京东尚科信息技术有限公司 云主机恢复方法和装置
CN114253651A (zh) * 2021-12-29 2022-03-29 南京机敏软件科技有限公司 一种云桌面客户端远程运维的方法、存储介质及处理器

Also Published As

Publication number Publication date
CN107517192A (zh) 2017-12-26

Similar Documents

Publication Publication Date Title
WO2017215502A1 (fr) Procédé de reprise après problème grave de bureau en nuage, client, serveur, système de reprise après problème grave de bureau en nuage et support d'informations
US10735509B2 (en) Systems and methods for synchronizing microservice data stores
US10983880B2 (en) Role designation in a high availability node
US20190235979A1 (en) Systems and methods for performing computing cluster node switchover
EP2816467B1 (fr) Procédé et dispositif destinés au point de contrôle et à la reprise de l'état d'un contenant
CN111338854B (zh) 基于Kubernetes集群快速恢复数据的方法及系统
CN109151045B (zh) 一种分布式云系统及监控方法
KR101868489B1 (ko) 컴퓨팅 세션의 관리
KR101840222B1 (ko) 컴퓨팅 세션의 관리
KR20180135124A (ko) 컴퓨팅 세션의 관리
CN111130835A (zh) 数据中心双活系统、切换方法、装置、设备及介质
JP2016525244A (ja) コンピューティングセッションの管理
US9471137B2 (en) Managing power savings in a high availability system at a redundant component level of granularity
WO2020001354A1 (fr) Commutateur de système de conteneur maître/de veille
JP2008305070A (ja) 情報処理装置および情報処理装置システム
US11403319B2 (en) High-availability network device database synchronization
WO2012097588A1 (fr) Procédé, appareil et système de stockage de données
CN109254876A (zh) 云计算系统中数据库的管理方法和装置
CN115878384A (zh) 一种基于备份容灾系统的分布式集群及构建方法
JP2009223368A (ja) クラスタリング制御装置、制御システム、制御方法及び制御プログラム
CN115766405B (zh) 一种故障处理方法、装置、设备和存储介质
CN101145955A (zh) 网管软件热备份的方法、网管及网管系统
CN113609232B (zh) 数据管理方法、数据管理系统和计算机可读存储介质
JP6822706B1 (ja) クラスタシステム、サーバ装置、引継ぎ方法、及びプログラム
CN107783855B (zh) 虚拟网元的故障自愈控制装置及方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17812613

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17812613

Country of ref document: EP

Kind code of ref document: A1