WO2014127610A1 - Method and device for cloud application data processing - Google Patents

Method and device for cloud application data processing Download PDF

Info

Publication number
WO2014127610A1
WO2014127610A1 PCT/CN2013/081591 CN2013081591W WO2014127610A1 WO 2014127610 A1 WO2014127610 A1 WO 2014127610A1 CN 2013081591 W CN2013081591 W CN 2013081591W WO 2014127610 A1 WO2014127610 A1 WO 2014127610A1
Authority
WO
WIPO (PCT)
Prior art keywords
data processing
cloud
recovery
processing
instruction
Prior art date
Application number
PCT/CN2013/081591
Other languages
French (fr)
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 WO2014127610A1 publication Critical patent/WO2014127610A1/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0793Remedial or corrective actions

Definitions

  • the present invention relates to the field of communications, and in particular to a cloud application data processing method and apparatus.
  • BACKGROUND With the rapid development of cloud computing technologies, cloud desktop applications are more and more widely used, and personalized use of desktop clouds is also increasing. Therefore, cloud desktop backup and recovery is an important function for protecting user data. .
  • the backup of the desktop cloud system is a relatively complicated process, and the hardware of the cloud equipment of each manufacturer is also good or bad, and today, when the user is king, while developing the cloud backup and restore module, it must be considered at the same time. The ease of use of this functional module.
  • the shutdown and recovery time of the cloud device cannot be dynamically set and managed according to the specific performance of each hardware, which will cause the same shutdown or data recovery. Such operations are performed very quickly on devices with good performance, but poor hardware devices may cause waiting time to be too long, so that the foreground cannot capture relevant information in time.
  • the recovery of cloud management is relatively complicated. The process is too complicated for ordinary users to operate. Due to the current problems, the recovery system of the cloud application is not flexible and efficient. For the problem that the recovery system of the cloud application in the related art is not flexible enough and the efficiency is low, an effective solution has not been proposed yet.
  • a cloud application data processing method including: receiving a data processing instruction input by a user; responding to a data processing instruction, using a name of a cloud device that needs to perform data processing through a system external interface (Web Service)
  • Web Service system external interface
  • the information is sent to the interface machine for processing, and when the data processing fails, receiving the failure information from the interface machine prompting the user to perform the manual operation.
  • the data processing instruction comprises: a cloud device shutdown instruction or a data recovery instruction.
  • the name information of the cloud device that needs to be processed by the system is sent to the interface device for processing, including: sending, by the cloud device shutdown command, the first name information of the cloud device that needs to be closed to
  • the interface device performs the shutdown operation on the cloud device that needs to be shut down, it determines whether there is a cloud device that has not been shut down in the cloud device that needs to be shut down within a predetermined period of time. If the determination result is negative, the interface determines. The shutdown operation succeeds, otherwise it determines that the shutdown operation failed.
  • the name information of the cloud device that needs to perform data processing is sent to the interface device for processing by the system external interface (Web Service), including: for the data recovery instruction, a recovery state value (Recoveryflag) value used to indicate the data recovery state
  • the first state value is set to be the first state value, and the first state value is used for the recovery
  • the second name information of the cloud device that needs to recover the data is sent to the interface device for processing by the external interface web service, and in the case that the data recovery is successful,
  • the Recoveryflag value is set to a second state value, wherein the second state value indicates that the recovery is successful.
  • a cloud application data processing apparatus including: a receiving module, configured to receive a data processing instruction input by a user; and a processing module configured to respond to the data processing instruction by using a system external interface (Web Service) Sending the name information of the cloud device that needs to be processed to the interface device for processing.
  • a system external interface Web Service
  • the data processing instruction comprises: a cloud device shutdown instruction or a data recovery instruction.
  • the device further includes: a query module, configured to: after the processing module starts to perform the data processing operation, periodically query the process of the processing operation, and determine that the occurrence occurs when the number of queries exceeds a predetermined number of times or the query interval exceeds a predetermined time interval An abnormal situation prompts the user to perform manual processing.
  • the predetermined number of times and the predetermined time interval are all set according to the configuration of the system equipment provided by different vendors.
  • the invention solves the problem that the name information of the cloud device that needs to be processed by the external interface Web Service is sent to the interface machine for processing by the system after the response to the data processing instruction, and the related art is solved.
  • the problem that the recovery system of the cloud application is not flexible enough and the efficiency is low, so that the ordinary user can conveniently perform data processing of the cloud application, and the processing efficiency is improved.
  • FIG. 1 is a flow chart of a cloud application data processing method according to an embodiment of the present invention
  • FIG. 2 is a flow chart of foreground management in a cloud application data processing method according to a preferred embodiment of the present invention
  • FIG. 4 is a structural block diagram of a cloud application data processing apparatus according to an embodiment of the present invention.
  • FIG. 5 is a cloud application data processing apparatus according to a preferred embodiment of the present invention.
  • BEST MODE FOR CARRYING OUT THE INVENTION BEST MODE FOR CARRYING OUT THE INVENTION
  • FIG. 1 is a flowchart of a cloud application data processing method according to an embodiment of the present invention. As shown in FIG. 1, the method mainly includes the following steps (step S102 - step S104): Step S102, receiving a data processing instruction input by a user.
  • step S104 in response to the data processing instruction, the name information of the cloud device that needs to perform data processing is sent to the interface device for processing by the external interface (Web Service), and when the data processing fails, the user is prompted to perform manual operation from the interface device. Failure information.
  • the data processing instruction may include: a cloud device shutdown instruction or a data recovery instruction.
  • the following two methods may be adopted according to different situations of the data processing instruction.
  • the interface device Sending, to the interface device, the first name information of the cloud device to be shut down, including the name and address of the cloud device, for the cloud device shutdown command; after the interface device performs the underlying shutdown operation on the cloud device that needs to be shut down If the cloud device that needs to be shut down exists in the cloud device that needs to be shut down within a predetermined period of time, if the result of the determination is negative, it is determined that the shutdown operation is successful, otherwise it is determined that the shutdown operation fails.
  • the recovery state (Recoveryflag) value indicating the data recovery state is set to the first state value, wherein the first state value indicates that the recovery is in progress; and the external interface Web Service of the system needs to recover the data.
  • the second name information of the cloud device including the name and address of the cloud device, is sent to the interface device for processing.
  • the Recovery flag value is set to a second state value, where the second state value indicates recovery. success.
  • the process of the processing operation may be periodically queried, and when the number of queries exceeds a predetermined number of times or the query interval exceeds a predetermined time interval, an abnormal situation is determined. , prompt the user to do manual processing.
  • the predetermined number of times and the predetermined time interval are all set according to the configuration of the system device provided by different vendors.
  • the implementation of the preferred embodiment is briefly introduced:
  • the user In the front user display, the user is provided with a one-click management mechanism, which is convenient and intuitive; Three parts: (1) The shutdown or data recovery execution is sent in the background; (2) The loop query is turned off, and the time and number of times that the loop query is supported can be dynamically configured, which fully takes into account the different processing time of different performance machines; 3) Perform a recovery operation or prompt the user for manual processing based on the information fed back by each machine.
  • a separate configuration page may be provided in the configuration of the status query time and the number of times, so that the user can configure a single status query time and a total number of queries according to different device performance.
  • FIG. 2 is a flow chart of foreground management in a cloud application data processing method according to a preferred embodiment of the present invention.
  • the MySQL connection is first used to set the recovery state.
  • the recoveryflag value is used to indicate the recovery state, 1 is the recovery success (equivalent to the above second state value), 0 means recovery (equivalent to the above first state value), and the interface will produce the weaving layer), also That is, the recoveryflag can control whether the web foreground has a weaving layer; when the recoveryflag is set to 0 (here, 0 is only a specific value of the first state value mentioned above, of course, other values can also be used), the webservice interface is called, and the relevant The device information (source address and path, destination address and path to be restored) is placed in the xml format to the interface machine; the message returned from the webservice is collected.
  • the foreground management process includes the following steps: Step S202: Receive a piece of recovery instruction of the Web.
  • step S204 the recoveryflag is set to 0, and processing is awaited.
  • step S206 the interface ejects the weaving layer, and prompts that the recovery process is in progress.
  • step S208 the background service starts processing. If the processing is successful, step S210 is performed. If the processing fails, step S214 is performed.
  • step S210 the recoveryflag is set to 1, and the single machine is successfully restored.
  • step S212 the interface cancels the weaving layer and prompts that the data recovery is successful.
  • step S214 prompting the user to manually process.
  • step S216 the interface cancels the weaving layer and prompts that the data recovery fails.
  • 3 is a flowchart of a background management in a cloud application data processing method according to a preferred embodiment of the present invention. In the background management process, when the flag recoveryflag is set to 0 (that is, after being restored), the background call is started.
  • Three interfaces (two of which are webservice interfaces, and the other one is Java directly calling the back-end shell) for background management operations:
  • a shutdown command which will be the name of the cloud device (multiple device names, The splitter is separated), and the shutdown command VM ShutdownVM is sent to the distribution interface machine (the universal interface machine providing the unified service), and the xml content is Module (the module number corresponding to the cloud device) and B vm id list (related The closed virtual machine name combination), after receiving the message, the distribution interface opportunity sends a message management instruction to the service interface, and converts the xml message into a format required by the service interface machine, and performs the underlying shutdown operation.
  • a shutdown command which will be the name of the cloud device (multiple device names, The splitter is separated)
  • the shutdown command VM ShutdownVM is sent to the distribution interface machine (the universal interface machine providing the unified service)
  • the xml content is Module (the module number corresponding to the cloud device) and B
  • the web cyclically sends a query instruction VM_GetVMStatus to the distribution interface machine, and the xml content is Module (module number corresponding to the cloud device) and B vm_id_list (combination of virtual machine names of all queries).
  • the service interface opportunity to query the current cloud application shutdown state if all the devices are in the off state, it will return a success message of a specific flag bit (ie, the above flag flag recoveryflag, for example, 4 0). If it fails, it will return the failure code to the front desk. It also includes the exception handling part.
  • the total number of queries and the query interval are determined by dynamically reading the data in Table 2.
  • Step S302 Receive a piece of recovery instruction of the Web.
  • step S304 the web initiates a shutdown instruction.
  • step S306 after the distribution interface machine receives the shutdown instruction, sends a message management instruction.
  • Step S308 the service interface machine performs an underlying shutdown operation.
  • Step S310 initiating a shutdown status query, determining whether the number of queries and the single query time exceed a predetermined number of times and time.
  • Step S312 the distribution interface machine receives the query instruction and forwards it.
  • Step S316 parsing the feedback result, prompting the user to fail to shut down.
  • Table 1 is a list of basic information, source address, destination address, configuration path, and recovery flag of the configured cloud application.
  • IP address varchar cloud application source address
  • IP address Desaddress varchar cloud application backup address
  • Table 2 is a list of the total number of queries and interval query time used in the loop query and configured according to the quality of each vendor's system equipment. Table 2
  • the cloud application data processing method provided by the foregoing embodiment is used to send the name information of the cloud device that needs to perform data processing to the interface device for processing by the external interface Web service, and the working state of the recovery system of the cloud application in the related technology is not flexible enough.
  • the problem of low efficiency in turn, enables the ordinary user to conveniently perform data processing of the cloud application, thereby improving the processing efficiency.
  • 4 is a structural block diagram of a cloud application data processing apparatus according to an embodiment of the present invention.
  • the apparatus is used to implement the cloud application data processing method provided by the foregoing embodiment. As shown in FIG. 4, the apparatus mainly includes: a receiving module 10 and Processing module 20.
  • the receiving module 10 is configured to receive a data processing instruction input by the user; the processing module 20 is connected to the receiving module 10, and configured to respond to the data processing instruction, and the name information of the cloud device that needs to perform data processing by the external interface Web Service of the system It is sent to the interface machine for processing. When the data processing fails, it receives the failure information from the interface machine prompting the user to perform manual operation.
  • the data processing instruction may include: a cloud device shutdown instruction or a data recovery instruction.
  • FIG. 5 is a structural block diagram of a cloud application data processing apparatus according to a preferred embodiment of the present invention. As shown in FIG. 5, in the preferred embodiment, the cloud application data processing apparatus further includes: a query module 30, configured to be in the processing module.
  • the process of the timing query processing operation determines that an abnormal situation occurs when the number of queries exceeds a predetermined number of times or the query time interval exceeds a predetermined time interval, and prompts the user to perform manual processing.
  • the predetermined number of times and the predetermined time interval are both set according to the configuration of the system devices provided by different vendors.
  • the cloud application data processing device provided by the foregoing embodiment sends the name information of the cloud device that needs to perform data processing to the interface device for processing by the external interface Web service, and solves the problem that the recovery state of the cloud application in the related technology is not flexible. The problem of low efficiency, in turn, enables the ordinary user to conveniently perform data processing of the cloud application, thereby improving the processing efficiency.
  • the present invention achieves the following technical effects: Mainly from three aspects, one is the friendliness of the interface, the user can use it very conveniently, and is intuitive and simple; Implementation, reliability and integrity, while considering the exception handling mechanism; Third, according to the different hardware used by each application vendor (that is, performance is good or bad), configurable flexible time and number of queries (dynamic configuration user recovery) Some data in the system).
  • the invention can make the management and recovery of the cloud desktop more flexible and simple, and provide a dynamic configurable recovery waiting time according to different hardware devices of the vendors, which can solve the problem that the recovery system of the cloud application in the related technology is not flexible enough.
  • modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.

Abstract

Disclosed are a method and a device for cloud application data processing. The method comprises: receiving a data processing instruction input by a user; and in response to the data processing instruction, sending, through a system external interface (WebService), name information of a cloud device requiring data processing to an interface machine for processing, and when the data processing fails, receiving, from the interface machine, failure information that prompts the user to perform manual operation. The present invention enables an ordinary user to perform cloud application data processing conveniently and improves processing efficiency.

Description

云应用数据处理方法及装置 技术领域 本发明涉及通信领域, 具体而言, 涉及一种云应用数据处理方法及装置。 背景技术 随着云计算技术的飞速发展, 云桌面的应用也越来越广泛, 对于桌面云的个性化 使用也越来越多, 因此, 云桌面的备份恢复是个很重要的保护用户数据的功能。 同时, 由于桌面云系统的备份是个相对复杂的过程, 而且各个厂商的云设备硬件 也有好有坏, 而且在用户为王的今天, 在进行云备份和还原模块开发的同时, 必须要 重点考虑到该功能模块的易用性。 对于现存的一些云应用的恢复系统, 主要有以下几个方面的问题: 首先, 不能根 据各个硬件具体的性能来动态设置和管理云设备的关机和恢复时间, 这样会造成相同 的关机或者数据恢复等操作在性能好的设备上面执行的很快, 但是差的硬件设备可能 会导致等待时间过长, 这样的话前台并不能及时地捕捉到相关信息; 第二, 由于云管 理的恢复是个相对复杂的过程, 对于普通用户操作起来过于复杂。 由于存在当前的这 些问题, 导致云应用的恢复系统工作状态不够灵活且效率较低。 针对相关技术中云应用的恢复系统工作状态不够灵活且效率较低的问题, 目前尚 未提出有效的解决方案。 发明内容 本发明提供了一种云应用数据处理方法及装置, 以至少解决上述问题。 根据本发明的一个方面, 提供了一种云应用数据处理方法, 包括: 接收用户输入 的数据处理指令; 响应数据处理指令, 通过系统对外接口 (Web Service) 将需要进行 数据处理的云设备的名称信息发送给接口机进行处理, 在数据处理失败时, 接收来自 接口机的提示用户进行手动操作的失败信息。 优选地, 数据处理指令包括: 云设备关机指令或数据恢复指令。 优选地, 通过系统对外接口 (Web Service) 将需要进行数据处理的云设备的名称 信息发送给接口机进行处理, 包括: 对于云设备关机指令, 将需要关闭的云设备的第 一名称信息发送给接口机; 待接口机对需要关闭的云设备进行底层的关机操作后, 在 预定的时间段内判断需要关闭的云设备中是否存在尚未关闭的云设备, 在判断结果为 否的情况下, 确定关闭操作成功, 否则确定关闭操作失败。 优选地, 通过系统对外接口 (Web Service) 将需要进行数据处理的云设备的名称 信息发送给接口机进行处理, 包括: 对于数据恢复指令, 将用于指示数据恢复状态的 恢复状态(Recoveryflag)值置为第一状态值, 其中, 第一状态值表示恢复中; 通过系 统对外接口 Web Service将需要恢复数据的云设备的第二名称信息发送给接口机进行 处理, 在数据恢复成功的情况下, 将 Recoveryflag值置为第二状态值, 其中, 第二状 态值表示恢复成功。 优选地, 在开始执行数据处理操作或云设备关机操作后, 定时查询处理操作的进 程, 在查询次数超过预定次数或查询时间间隔超过预定时间间隔的情况下, 确定发生 异常情况, 提示用户进行手动处理。 优选地, 预定次数和预定时间间隔均是根据不同厂商提供的系统设备的配置设定 的。 根据本发明的另一方面, 提供了一种云应用数据处理装置, 包括: 接收模块, 设 置为接收用户输入的数据处理指令; 处理模块, 设置为响应数据处理指令, 通过系统 对外接口 (Web Service) 将需要进行数据处理的云设备的名称信息发送给接口机进行 处理, 在数据处理失败时, 接收来自接口机的提示用户进行手动操作的失败信息。 优选地, 数据处理指令包括: 云设备关机指令或数据恢复指令。 优选地, 该装置还包括: 查询模块, 设置为在处理模块开始执行数据处理操作后, 定时查询处理操作的进程, 在查询次数超过预定次数或查询时间间隔超过预定时间间 隔的情况下, 确定发生异常情况, 提示用户进行手动处理。 优选地, 预定次数和预定时间间隔均是根据不同厂商提供的系统设备的配置设定 的。 通过本发明,采用在响应数据处理指令后,通过系统对外接口 Web Service将需要 进行数据处理的云设备的名称信息发送给接口机进行处理的方式, 解决了相关技术中 云应用的恢复系统工作状态不够灵活且效率较低的问题, 进而达到了使普通用户方便 地进行云应用的数据处理, 提高了处理效率的效果。 附图说明 此处所说明的附图用来提供对本发明的进一步理解, 构成本申请的一部分, 本发 明的示意性实施例及其说明用于解释本发明, 并不构成对本发明的不当限定。 在附图 中- 图 1是根据本发明实施例的云应用数据处理方法流程图; 图 2是根据本发明优选实施例的云应用数据处理方法中的前台管理流程图; 图 3是根据本发明优选实施例的云应用数据处理方法中的后台管理流程图; 图 4是根据本发明实施例的云应用数据处理装置的结构框图; 以及 图 5是根据本发明优选实施例的云应用数据处理装置的结构框图。 具体实施方式 下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是, 在不冲突的 情况下, 本申请中的实施例及实施例中的特征可以相互组合。 图 1是根据本发明实施例的云应用数据处理方法流程图, 如图 1所示, 该方法主 要包括以下步骤 (步骤 S102-步骤 S104): 步骤 S102, 接收用户输入的数据处理指令。 步骤 S104, 响应数据处理指令, 通过系统对外接口 (Web Service)将需要进行数 据处理的云设备的名称信息发送给接口机进行处理, 在数据处理失败时, 接收来自接 口机的提示用户进行手动操作的失败信息。 在本实施例中, 数据处理指令可以包括: 云设备关机指令或数据恢复指令。 在本实施例中, 在通过系统对外接口 (Web Service) 将需要进行数据处理的云设 备的名称信息发送给接口机进行处理的过程中, 可以根据数据处理指令的不同情况分 别采用以下两种方式实现: ( 1 )对于云设备关机指令, 将需要关闭的云设备的第一名称信息(包括该云设备 的名称和地址)发送给接口机; 待接口机对需要关闭的云设备进行底层的关机操作后, 在预定的时间段内判断需要关闭的云设备中是否存在尚未关闭的云设备, 在判断结果 为否的情况下, 确定关闭操作成功, 否则确定关闭操作失败。 (2) 对于数据恢复指令, 将用于指示数据恢复状态的恢复状态 (Recoveryflag) 值置为第一状态值, 其中, 第一状态值表示恢复中; 通过系统对外接口 Web Service 将需要恢复数据的云设备的第二名称信息 (包括该云设备的名称和地址) 发送给接口 机进行处理, 在数据恢复成功的情况下, 将 Recoveryflag值置为第二状态值, 其中, 第二状态值表示恢复成功。 在本实施例中, 在开始执行数据处理操作或云设备关机操作后, 还可以定时查询 处理操作的进程, 在查询次数超过预定次数或查询时间间隔超过预定时间间隔的情况 下, 确定发生异常情况, 提示用户进行手动处理。 在本实施例中, 预定次数和预定时间间隔均是根据不同厂商提供的系统设备的配 置设定的。 下面结合图 2、 图 3 以及优选实施例对上述实施例提供的云应用数据处理方法进 行更加详细的说明。 在对该优选实例进行详细描述之前, 首先对该优选实施例的实施思路进行简要介 绍: 在前台的用户展示方面, 提供给用户一键式的管理机制, 方便直观; 在后台的逻 辑处理分为三部分: (1 ) 关机或者数据恢复的执行发送于后台执行; (2) 循环查询关 机状态, 同时支持循环查询的时间和次数可以动态配置, 这样充分考虑到了不同性能 机器的处理时间不同; (3 ) 根据各个机器反馈的信息, 执行恢复操作或者提示用户来 进行手动处理。 需要说明的是, 在实际应用过程中, 在状态查询时间和次数配置方面可以提供单 独的配置页面, 这样用户可以根据设备性能的不同来配置单个的状态查询时间和总的 查询次数。 尤其是, 在当前的云管理系统中, 通常将大数据量的用户数据和系统配置 备份文件都单独放在单独的云盘里, 这对于处于恢复数据也就是进行云盘切换拷贝的 时候所用的时间和机器的性能关联很大。 基于这几个方面的实现, 该优选实施例可以 很好地根据硬件性能的不同来设置恢复等待时间和次数, 且能够适应各个厂商提供的 性能不同的系统。 图 2是根据本发明优选实施例的云应用数据处理方法中的前台管理流程图, 在该 前台管理流程中, 当 web前台发起一键恢复指令时, 首先通过 JDBC连接, 将恢复状 态的表置 0 (其中 recoveryflag值用于指示恢复状态, 1为恢复成功 (相当于上述第二 状态值), 0表示恢复中 (相当于上述第一状态值), 且此时界面会产生织造层), 也就 是说, recoveryflag能够控制 web前台是否有织造层; 在 recoveryflag置 0 (这里, 0 仅为上述第一状态值的一个特定值, 当然, 还可以采用其他值) 后, 调用 webservice 接口, 将相关的设备信息 (源地址和路径, 要恢复的目的地址和路径) 以 xml的格式 放给接口机; 收集从 webservice返回的消息, 若一键恢复成功, 则标志位 recoveryflag 置 1 (这里, 0仅为上述第一状态值的一个特定值, 当然, 还可以采用其他值), 一键 恢复数据成功, 否则, 一键恢复失败, 提醒用户手动操作。 如图 2所示, 该前台管理流程包括以下步骤: 步骤 S202, 接收到 Web的一件恢复指令。 步骤 S204, 将 recoveryflag置为 0, 等待处理。 步骤 S206, 界面弹出织造层, 并提示恢复处理进行中。 步骤 S208, 后台业务开始处理, 如果处理成功, 执行步骤 S210, 如果处理失败, 执行步骤 S214。 步骤 S210, 将 recoveryflag置为 1, 单个机器恢复成功。 步骤 S212, 界面取消织造层, 并提示恢复数据成功。 步骤 S214, 提示用户手动处理。 步骤 S216, 界面取消织造层, 并提示恢复数据失败。 图 3是根据本发明优选实施例的云应用数据处理方法中的后台管理流程图, 在该 后台管理流程中, 当标志位 recoveryflag置 0时 (也就处于待恢复状态后), 开始调用 后台的三个接口 (其中两个接口为 webservice接口, 另外一个为 Java直接调用后台的 Shell) 以进行后台管理操作: 首先, web发起关机指令, 将所要关云设备名字 (多个设备名字的话, 以一定的 分割符区分开), 向分发接口机 (提供统一服务的通用接口机) 发送关机指令 VM ShutdownVM, xml内容为 Module (云设备对应的模块号)禾 B vm id list (所有关 闭的虚拟机名字组合), 收到消息后, 分发接口机会向业务接口发送消息管理指令, 并 将 xml消息转为为业务接口机需要的格式, 执行底层的关机操作。 接着, 在关机指令执行完之后, web 向分发接口机循环发送查询指令 VM_GetVMStatus, xml内容为 Module (云设备对应的模块号)禾 B vm_id_list (所有查 询的虚拟机名字组合)。 收到消息后, 业务接口机会去查询现在的云应用关闭状态, 若 所有的设备都处于关闭状态时, 会返回一个特定的标志位 (即上述的标志位 recoveryflag, 例如 4个 0) 的成功消息, 若是失败的话, 会给前台返回失败码, 这里 还包括异常处理部分,查询的总次数和查询时间间隔是动态读取表 2中的数据确定的, 如果超过总的查询时间的时候(掉电等异常情况),会自动按照异常情况提示用户手动 处理。 最后, 当界面收到返回的消息为四个 0时,可以通过 java直接调用恢复 shell的脚 本, 完成对单个云应用的恢复操作。 若失败时, 提供失败信息, 提示用户手动恢复。 如图 3所示, 该前台管理流程包括以下步骤: 步骤 S302, 接收到 Web的一件恢复指令。 步骤 S304, Web发起关机指令。 步骤 S306, 分发接口机接收关机指令后, 发送消息管理指令。 步骤 S308, 业务接口机执行底层的关机操作。 步骤 S310,发起关机状态查询, 判断查询次数和单次查询时间是否超出预定次数 和时间。 步骤 S312, 分发接口机接收查询指令并转发。 步骤 S314, 业务接口机查询云设备的状态。 步骤 S316, 解析反馈结果, 提示用户关机失败。 步骤 S318, 执行恢复的 SHELL脚本。 为了更好的理解该优选实施例, 请同时参考表 1和表 2, 表 1为配置的云应用的 基本信息、 源地址、 目的地址、 配置路径以及恢复标志的列表。 表 1 云恢复信息表结构设计 The present invention relates to the field of communications, and in particular to a cloud application data processing method and apparatus. BACKGROUND With the rapid development of cloud computing technologies, cloud desktop applications are more and more widely used, and personalized use of desktop clouds is also increasing. Therefore, cloud desktop backup and recovery is an important function for protecting user data. . At the same time, because the backup of the desktop cloud system is a relatively complicated process, and the hardware of the cloud equipment of each manufacturer is also good or bad, and today, when the user is king, while developing the cloud backup and restore module, it must be considered at the same time. The ease of use of this functional module. For some existing cloud application recovery systems, there are mainly the following problems: First, the shutdown and recovery time of the cloud device cannot be dynamically set and managed according to the specific performance of each hardware, which will cause the same shutdown or data recovery. Such operations are performed very quickly on devices with good performance, but poor hardware devices may cause waiting time to be too long, so that the foreground cannot capture relevant information in time. Second, the recovery of cloud management is relatively complicated. The process is too complicated for ordinary users to operate. Due to the current problems, the recovery system of the cloud application is not flexible and efficient. For the problem that the recovery system of the cloud application in the related art is not flexible enough and the efficiency is low, an effective solution has not been proposed yet. SUMMARY OF THE INVENTION The present invention provides a cloud application data processing method and apparatus to solve at least the above problems. According to an aspect of the present invention, a cloud application data processing method is provided, including: receiving a data processing instruction input by a user; responding to a data processing instruction, using a name of a cloud device that needs to perform data processing through a system external interface (Web Service) The information is sent to the interface machine for processing, and when the data processing fails, receiving the failure information from the interface machine prompting the user to perform the manual operation. Preferably, the data processing instruction comprises: a cloud device shutdown instruction or a data recovery instruction. Preferably, the name information of the cloud device that needs to be processed by the system is sent to the interface device for processing, including: sending, by the cloud device shutdown command, the first name information of the cloud device that needs to be closed to After the interface device performs the shutdown operation on the cloud device that needs to be shut down, it determines whether there is a cloud device that has not been shut down in the cloud device that needs to be shut down within a predetermined period of time. If the determination result is negative, the interface determines. The shutdown operation succeeds, otherwise it determines that the shutdown operation failed. Preferably, the name information of the cloud device that needs to perform data processing is sent to the interface device for processing by the system external interface (Web Service), including: for the data recovery instruction, a recovery state value (Recoveryflag) value used to indicate the data recovery state The first state value is set to be the first state value, and the first state value is used for the recovery; the second name information of the cloud device that needs to recover the data is sent to the interface device for processing by the external interface web service, and in the case that the data recovery is successful, The Recoveryflag value is set to a second state value, wherein the second state value indicates that the recovery is successful. Preferably, after the data processing operation or the cloud device shutdown operation is started, the process of the timing query processing operation determines that an abnormal situation occurs when the number of queries exceeds a predetermined number of times or the query interval exceeds a predetermined time interval, and prompts the user to manually deal with. Preferably, the predetermined number of times and the predetermined time interval are all set according to the configuration of the system equipment provided by different vendors. According to another aspect of the present invention, a cloud application data processing apparatus is provided, including: a receiving module, configured to receive a data processing instruction input by a user; and a processing module configured to respond to the data processing instruction by using a system external interface (Web Service) Sending the name information of the cloud device that needs to be processed to the interface device for processing. When the data processing fails, receiving the failure information from the interface device prompting the user to perform the manual operation. Preferably, the data processing instruction comprises: a cloud device shutdown instruction or a data recovery instruction. Preferably, the device further includes: a query module, configured to: after the processing module starts to perform the data processing operation, periodically query the process of the processing operation, and determine that the occurrence occurs when the number of queries exceeds a predetermined number of times or the query interval exceeds a predetermined time interval An abnormal situation prompts the user to perform manual processing. Preferably, the predetermined number of times and the predetermined time interval are all set according to the configuration of the system equipment provided by different vendors. The invention solves the problem that the name information of the cloud device that needs to be processed by the external interface Web Service is sent to the interface machine for processing by the system after the response to the data processing instruction, and the related art is solved. The problem that the recovery system of the cloud application is not flexible enough and the efficiency is low, so that the ordinary user can conveniently perform data processing of the cloud application, and the processing efficiency is improved. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, 1 is a flow chart of a cloud application data processing method according to an embodiment of the present invention; FIG. 2 is a flow chart of foreground management in a cloud application data processing method according to a preferred embodiment of the present invention; FIG. 4 is a structural block diagram of a cloud application data processing apparatus according to an embodiment of the present invention; and FIG. 5 is a cloud application data processing apparatus according to a preferred embodiment of the present invention; Block diagram of the structure. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. 1 is a flowchart of a cloud application data processing method according to an embodiment of the present invention. As shown in FIG. 1, the method mainly includes the following steps (step S102 - step S104): Step S102, receiving a data processing instruction input by a user. In step S104, in response to the data processing instruction, the name information of the cloud device that needs to perform data processing is sent to the interface device for processing by the external interface (Web Service), and when the data processing fails, the user is prompted to perform manual operation from the interface device. Failure information. In this embodiment, the data processing instruction may include: a cloud device shutdown instruction or a data recovery instruction. In this embodiment, in the process of transmitting the name information of the cloud device that needs to perform data processing to the interface device through the system external interface (Web Service), the following two methods may be adopted according to different situations of the data processing instruction. achieve: (1) Sending, to the interface device, the first name information of the cloud device to be shut down, including the name and address of the cloud device, for the cloud device shutdown command; after the interface device performs the underlying shutdown operation on the cloud device that needs to be shut down If the cloud device that needs to be shut down exists in the cloud device that needs to be shut down within a predetermined period of time, if the result of the determination is negative, it is determined that the shutdown operation is successful, otherwise it is determined that the shutdown operation fails. (2) For the data recovery instruction, the recovery state (Recoveryflag) value indicating the data recovery state is set to the first state value, wherein the first state value indicates that the recovery is in progress; and the external interface Web Service of the system needs to recover the data. The second name information of the cloud device, including the name and address of the cloud device, is sent to the interface device for processing. When the data recovery is successful, the Recovery flag value is set to a second state value, where the second state value indicates recovery. success. In this embodiment, after the data processing operation or the cloud device shutdown operation is started, the process of the processing operation may be periodically queried, and when the number of queries exceeds a predetermined number of times or the query interval exceeds a predetermined time interval, an abnormal situation is determined. , prompt the user to do manual processing. In this embodiment, the predetermined number of times and the predetermined time interval are all set according to the configuration of the system device provided by different vendors. The cloud application data processing method provided by the foregoing embodiment is described in more detail below with reference to FIG. 2, FIG. 3 and the preferred embodiment. Before the detailed description of the preferred embodiment, the implementation of the preferred embodiment is briefly introduced: In the front user display, the user is provided with a one-click management mechanism, which is convenient and intuitive; Three parts: (1) The shutdown or data recovery execution is sent in the background; (2) The loop query is turned off, and the time and number of times that the loop query is supported can be dynamically configured, which fully takes into account the different processing time of different performance machines; 3) Perform a recovery operation or prompt the user for manual processing based on the information fed back by each machine. It should be noted that, in the actual application process, a separate configuration page may be provided in the configuration of the status query time and the number of times, so that the user can configure a single status query time and a total number of queries according to different device performance. In particular, in the current cloud management system, a large amount of user data and a system configuration backup file are usually separately placed in a separate cloud disk, which is used when recovering data, that is, when the cloud disk is switched. Time is highly correlated with machine performance. Based on the implementation of these aspects, the preferred embodiment can well set the recovery latency and number of times according to different hardware performances, and can adapt to different performance systems provided by various vendors. 2 is a flow chart of foreground management in a cloud application data processing method according to a preferred embodiment of the present invention. In the foreground management process, when a web page initiates a key recovery instruction, the MySQL connection is first used to set the recovery state. 0 (where the recoveryflag value is used to indicate the recovery state, 1 is the recovery success (equivalent to the above second state value), 0 means recovery (equivalent to the above first state value), and the interface will produce the weaving layer), also That is, the recoveryflag can control whether the web foreground has a weaving layer; when the recoveryflag is set to 0 (here, 0 is only a specific value of the first state value mentioned above, of course, other values can also be used), the webservice interface is called, and the relevant The device information (source address and path, destination address and path to be restored) is placed in the xml format to the interface machine; the message returned from the webservice is collected. If the key recovery is successful, the flag recoveryflag is set to 1 (here, 0 is only a specific value of the above first state value, of course, other values may also be used, one key to recover the data successfully, otherwise , One-click recovery failed, reminding the user to operate manually. As shown in FIG. 2, the foreground management process includes the following steps: Step S202: Receive a piece of recovery instruction of the Web. In step S204, the recoveryflag is set to 0, and processing is awaited. In step S206, the interface ejects the weaving layer, and prompts that the recovery process is in progress. In step S208, the background service starts processing. If the processing is successful, step S210 is performed. If the processing fails, step S214 is performed. In step S210, the recoveryflag is set to 1, and the single machine is successfully restored. In step S212, the interface cancels the weaving layer and prompts that the data recovery is successful. Step S214, prompting the user to manually process. In step S216, the interface cancels the weaving layer and prompts that the data recovery fails. 3 is a flowchart of a background management in a cloud application data processing method according to a preferred embodiment of the present invention. In the background management process, when the flag recoveryflag is set to 0 (that is, after being restored), the background call is started. Three interfaces (two of which are webservice interfaces, and the other one is Java directly calling the back-end shell) for background management operations: First, the web initiates a shutdown command, which will be the name of the cloud device (multiple device names, The splitter is separated), and the shutdown command VM ShutdownVM is sent to the distribution interface machine (the universal interface machine providing the unified service), and the xml content is Module (the module number corresponding to the cloud device) and B vm id list (related The closed virtual machine name combination), after receiving the message, the distribution interface opportunity sends a message management instruction to the service interface, and converts the xml message into a format required by the service interface machine, and performs the underlying shutdown operation. Then, after the shutdown command is executed, the web cyclically sends a query instruction VM_GetVMStatus to the distribution interface machine, and the xml content is Module (module number corresponding to the cloud device) and B vm_id_list (combination of virtual machine names of all queries). After receiving the message, the service interface opportunity to query the current cloud application shutdown state, if all the devices are in the off state, it will return a success message of a specific flag bit (ie, the above flag flag recoveryflag, for example, 4 0). If it fails, it will return the failure code to the front desk. It also includes the exception handling part. The total number of queries and the query interval are determined by dynamically reading the data in Table 2. If the total query time is exceeded (power down) If the exception is abnormal, the user will be prompted to manually process according to the abnormal situation. Finally, when the interface receives the returned message as four zeros, the script of the recovery shell can be directly invoked through java to complete the recovery operation of the single cloud application. If it fails, it provides a failure message and prompts the user to manually recover. As shown in FIG. 3, the foreground management process includes the following steps: Step S302: Receive a piece of recovery instruction of the Web. In step S304, the web initiates a shutdown instruction. Step S306, after the distribution interface machine receives the shutdown instruction, sends a message management instruction. Step S308, the service interface machine performs an underlying shutdown operation. Step S310, initiating a shutdown status query, determining whether the number of queries and the single query time exceed a predetermined number of times and time. Step S312, the distribution interface machine receives the query instruction and forwards it. Step S314, the service interface machine queries the status of the cloud device. Step S316, parsing the feedback result, prompting the user to fail to shut down. Step S318, executing the restored SHELL script. For a better understanding of the preferred embodiment, please refer to Table 1 and Table 2 at the same time. Table 1 is a list of basic information, source address, destination address, configuration path, and recovery flag of the configured cloud application. Table 1 Cloud recovery information table structure design
列名 类型 描述  Column Name Type Description
srcaddress varchar 云应用源地址 (IP地址)  Srcaddress varchar cloud application source address (IP address)
desaddress varchar 云应用备份地址 (IP地址)  Desaddress varchar cloud application backup address (IP address)
srclocation varchar 云应用源文件保存路径  Srclocation varchar cloud application source file save path
dislocation varchar 云应用备份文件保存路径  Dislocation varchar cloud application backup file save path
recovery flag varchar 恢复标志 0恢复中 1恢复成功 表 2为循环查询的时候所使用的且根据各个厂商系统设备的优劣配置总的查询次 数和间隔查询时间的列表。 表 2  Recovery flag varchar recovery flag 0 recovery 1 recovery success Table 2 is a list of the total number of queries and interval query time used in the loop query and configured according to the quality of each vendor's system equipment. Table 2
Figure imgf000008_0001
Figure imgf000008_0001
采用上述实施例提供的云应用数据处理方法,通过系统对外接口 Web Service将需 要进行数据处理的云设备的名称信息发送给接口机进行处理, 解决了相关技术中云应 用的恢复系统工作状态不够灵活且效率较低的问题, 进而达到了使普通用户方便地进 行云应用的数据处理, 提高了处理效率的效果。 图 4是根据本发明实施例的云应用数据处理装置的结构框图,,该装置用以实现上 述实施例提供的云应用数据处理方法, 如图 4 所示, 该装置主要包括: 接收模块 10 和处理模块 20。 其中, 接收模块 10, 设置为接收用户输入的数据处理指令; 处理模块 20, 连接至接收模块 10, 设置为响应数据处理指令, 通过系统对外接口 Web Service 将需要进行数据处理的云设备的名称信息发送给接口机进行处理,在数据处理失败时, 接收来自接口机的提示用户进行手动操作的失败信息。 在本实施例中, 数据处理指令可以包括: 云设备关机指令或数据恢复指令。 图 5是根据本发明优选实施例的云应用数据处理装置的结构框图, 如图 5所示, 在该优选实施例中, 该云应用数据处理装置还包括: 查询模块 30, 设置为在处理模块 20开始执行数据处理操作后, 定时查询处理操作的进程, 在查询次数超过预定次数或 查询时间间隔超过预定时间间隔的情况下, 确定发生异常情况, 提示用户进行手动处 理。 在本优选实施例中, 预定次数和预定时间间隔均是根据不同厂商提供的系统设备 的配置设定的。 采用上述实施例提供的云应用数据处理装置,通过系统对外接口 Web Service将需 要进行数据处理的云设备的名称信息发送给接口机进行处理, 解决了相关技术中云应 用的恢复系统工作状态不够灵活且效率较低的问题, 进而达到了使普通用户方便地进 行云应用的数据处理, 提高了处理效率的效果。 从以上的描述中, 可以看出, 本发明实现了如下技术效果: 主要从三个方面着手, 一是界面使用的友好性, 用户可以非常方便的使用, 并且直观简便; 二是后台方案的 可实现性, 可靠性和完整性, 同时考虑异常处理机制; 三是根据各个应用厂商所采用 的设备硬件不同(即性能有好有坏), 可配置灵活的时间和查询次数(动态的配置用户 恢复系统中的一些数据)。 本发明能够使云桌面的管理恢复更加的灵活、 简便, 同时根据各个厂商硬件设备 的不同提供一种动态的可以配置的恢复等待时间, 能够解决相关技术中云应用的恢复 系统工作状态不够灵活且效率较低的问题, 进而达到了使普通用户方便地进行云应用 的数据处理, 提高了处理效率的效果。 显然, 本领域的技术人员应该明白, 上述的本发明的各模块或各步骤可以用通用 的计算装置来实现, 它们可以集中在单个的计算装置上, 或者分布在多个计算装置所 组成的网络上, 可选地, 它们可以用计算装置可执行的程序代码来实现, 从而, 可以 将它们存储在存储装置中由计算装置来执行, 并且在某些情况下, 可以以不同于此处 的顺序执行所示出或描述的步骤, 或者将它们分别制作成各个集成电路模块, 或者将 它们中的多个模块或步骤制作成单个集成电路模块来实现。 这样, 本发明不限制于任 何特定的硬件和软件结合。 以上所述仅为本发明的优选实施例而已, 并不用于限制本发明, 对于本领域的技 术人员来说, 本发明可以有各种更改和变化。 凡在本发明的精神和原则之内, 所作的 任何修改、 等同替换、 改进等, 均应包含在本发明的保护范围之内。 The cloud application data processing method provided by the foregoing embodiment is used to send the name information of the cloud device that needs to perform data processing to the interface device for processing by the external interface Web service, and the working state of the recovery system of the cloud application in the related technology is not flexible enough. The problem of low efficiency, in turn, enables the ordinary user to conveniently perform data processing of the cloud application, thereby improving the processing efficiency. 4 is a structural block diagram of a cloud application data processing apparatus according to an embodiment of the present invention. The apparatus is used to implement the cloud application data processing method provided by the foregoing embodiment. As shown in FIG. 4, the apparatus mainly includes: a receiving module 10 and Processing module 20. The receiving module 10 is configured to receive a data processing instruction input by the user; the processing module 20 is connected to the receiving module 10, and configured to respond to the data processing instruction, and the name information of the cloud device that needs to perform data processing by the external interface Web Service of the system It is sent to the interface machine for processing. When the data processing fails, it receives the failure information from the interface machine prompting the user to perform manual operation. In this embodiment, the data processing instruction may include: a cloud device shutdown instruction or a data recovery instruction. FIG. 5 is a structural block diagram of a cloud application data processing apparatus according to a preferred embodiment of the present invention. As shown in FIG. 5, in the preferred embodiment, the cloud application data processing apparatus further includes: a query module 30, configured to be in the processing module. After the data processing operation is started, the process of the timing query processing operation determines that an abnormal situation occurs when the number of queries exceeds a predetermined number of times or the query time interval exceeds a predetermined time interval, and prompts the user to perform manual processing. In the preferred embodiment, the predetermined number of times and the predetermined time interval are both set according to the configuration of the system devices provided by different vendors. The cloud application data processing device provided by the foregoing embodiment sends the name information of the cloud device that needs to perform data processing to the interface device for processing by the external interface Web service, and solves the problem that the recovery state of the cloud application in the related technology is not flexible. The problem of low efficiency, in turn, enables the ordinary user to conveniently perform data processing of the cloud application, thereby improving the processing efficiency. From the above description, it can be seen that the present invention achieves the following technical effects: Mainly from three aspects, one is the friendliness of the interface, the user can use it very conveniently, and is intuitive and simple; Implementation, reliability and integrity, while considering the exception handling mechanism; Third, according to the different hardware used by each application vendor (that is, performance is good or bad), configurable flexible time and number of queries (dynamic configuration user recovery) Some data in the system). The invention can make the management and recovery of the cloud desktop more flexible and simple, and provide a dynamic configurable recovery waiting time according to different hardware devices of the vendors, which can solve the problem that the recovery system of the cloud application in the related technology is not flexible enough. The problem of low efficiency, in turn, enables ordinary users to conveniently perform data processing of cloud applications, thereby improving the efficiency of processing. Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

权 利 要 求 书 Claim
1. 一种云应用数据处理方法, 包括: A cloud application data processing method, comprising:
接收用户输入的数据处理指令;  Receiving a data processing instruction input by a user;
响应所述数据处理指令, 通过系统对外接口 Web Service将需要进行数据 处理的云设备的名称信息发送给接口机进行处理, 在数据处理失败时, 接收来 自所述接口机的提示用户进行手动操作的失败信息。  Responding to the data processing instruction, the system external network service sends the name information of the cloud device that needs to perform data processing to the interface device for processing, and when the data processing fails, receiving the prompting user from the interface device to perform manual operation. Failure information.
2. 根据权利要求 1所述的方法, 其中, 所述数据处理指令包括: 云设备关机指令 或数据恢复指令。 2. The method according to claim 1, wherein the data processing instruction comprises: a cloud device shutdown instruction or a data recovery instruction.
3. 根据权利要求 2所述的方法, 其中, 通过系统对外接口 Web Service将需要进 行数据处理的云设备的名称信息发送给接口机进行处理, 包括: The method according to claim 2, wherein the name information of the cloud device that needs to perform data processing is sent to the interface device for processing by the system external interface Web service, including:
对于云设备关机指令, 将需要关闭的云设备的第一名称信息发送给所述接 口机;  For the cloud device shutdown command, sending the first name information of the cloud device that needs to be closed to the interface machine;
待所述接口机对所述需要关闭的云设备进行底层的关机操作后, 在预定的 时间段内判断所述需要关闭的云设备中是否存在尚未关闭的云设备, 在判断结 果为否的情况下, 确定关闭操作成功, 否则确定关闭操作失败。  After the interface device performs the underlying shutdown operation on the cloud device that needs to be shut down, it is determined whether there is a cloud device that has not been closed in the cloud device that needs to be shut down within a predetermined period of time, and the determination result is negative. Next, it is determined that the shutdown operation is successful, otherwise it is determined that the shutdown operation failed.
4. 根据权利要求 2所述的方法, 其中, 通过系统对外接口 Web Service将需要进 行数据处理的云设备的名称信息发送给接口机进行处理, 包括: The method according to claim 2, wherein the name information of the cloud device that needs to perform data processing is sent to the interface device for processing by the external interface Web service, including:
对于所述数据恢复指令,将用于指示数据恢复状态的恢复状态 Recoveryflag 值置为第一状态值, 其中, 所述第一状态值表示恢复中;  For the data recovery instruction, setting a recovery state Recoveryflag value for indicating a data recovery state to a first state value, wherein the first state value indicates recovery;
通过系统对外接口 Web Service将需要恢复数据的云设备的第二名称信息 发送给接口机进行处理, 在数据恢复成功的情况下, 将所述 Recoveryflag值置 为第二状态值, 其中, 所述第二状态值表示恢复成功。  The second name information of the cloud device that needs to recover the data is sent to the interface device for processing by the external interface web service, and the recovery flag value is set to the second state value when the data recovery is successful, where the A two-state value indicates that the recovery was successful.
5. 根据权利要求 3或 4所述的方法, 其中, 在开始执行数据处理操作或云设备关机操作后,定时查询处理操作的进程, 在查询次数超过预定次数或查询时间间隔超过预定时间间隔的情况下, 确定发 生异常情况, 提示用户进行手动处理。 The method according to claim 3 or 4, wherein, after the data processing operation or the cloud device shutdown operation is started, the process of the processing operation is periodically queried, when the number of queries exceeds a predetermined number of times or the query interval exceeds a predetermined time interval. In the case, it is determined that an abnormal situation has occurred, prompting the user to perform manual processing.
6. 根据权利要求 5所述的方法, 其中, 所述预定次数和所述预定时间间隔均是根 据不同厂商提供的系统设备的配置设定的。 6. The method according to claim 5, wherein the predetermined number of times and the predetermined time interval are both set according to configurations of system devices provided by different vendors.
7. 一种云应用数据处理装置, 包括: 7. A cloud application data processing apparatus, comprising:
接收模块, 设置为接收用户输入的数据处理指令;  a receiving module, configured to receive a data processing instruction input by a user;
处理模块, 设置为响应所述数据处理指令, 通过系统对外接口 Web Service 将需要进行数据处理的云设备的名称信息发送给接口机进行处理, 在数据处理 失败时, 接收来自所述接口机的提示用户进行手动操作的失败信息。  The processing module is configured to send, according to the data processing instruction, the name information of the cloud device that needs to perform data processing to the interface device for processing by the external interface web service, and receive the prompt from the interface device when the data processing fails. User failure information for manual operation.
8. 根据权利要求 7所述的装置, 其中, 所述数据处理指令包括: 云设备关机指令 或数据恢复指令。 8. The apparatus according to claim 7, wherein the data processing instruction comprises: a cloud device shutdown instruction or a data recovery instruction.
9. 根据权利要求 7或 8所述的装置, 其中, 所述装置还包括: The device according to claim 7 or 8, wherein the device further comprises:
查询模块, 设置为在所述处理模块开始执行数据处理操作后, 定时查询处 理操作的进程, 在查询次数超过预定次数或查询时间间隔超过预定时间间隔的 情况下, 确定发生异常情况, 提示用户进行手动处理。  The query module is configured to, after the processing module starts to perform the data processing operation, periodically query the process of the processing operation, and if the number of queries exceeds a predetermined number of times or the query time interval exceeds a predetermined time interval, determine that an abnormal situation occurs, prompting the user to perform Handle it manually.
10. 根据权利要求 9所述的装置, 其中, 所述预定次数和所述预定时间间隔均是根 据不同厂商提供的系统设备的配置设定的。 10. The apparatus according to claim 9, wherein the predetermined number of times and the predetermined time interval are both set according to configurations of system devices provided by different vendors.
PCT/CN2013/081591 2013-02-22 2013-08-15 Method and device for cloud application data processing WO2014127610A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310057192.5A CN104008026A (en) 2013-02-22 2013-02-22 Cloud application data processing method and device
CN201310057192.5 2013-02-22

Publications (1)

Publication Number Publication Date
WO2014127610A1 true WO2014127610A1 (en) 2014-08-28

Family

ID=51368687

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/081591 WO2014127610A1 (en) 2013-02-22 2013-08-15 Method and device for cloud application data processing

Country Status (2)

Country Link
CN (1) CN104008026A (en)
WO (1) WO2014127610A1 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3816804A4 (en) * 2018-07-20 2021-09-01 Huawei Technologies Co., Ltd. System recovery method and device

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102158535A (en) * 2011-02-10 2011-08-17 浪潮(北京)电子信息产业有限公司 Cloud computing operating system
CN102291445A (en) * 2011-08-04 2011-12-21 上海龙照电子有限公司 Cloud computing management system based on virtual resources
CN102546730A (en) * 2010-12-30 2012-07-04 中国移动通信集团公司 Data processing method, device and system

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8555187B2 (en) * 2010-02-16 2013-10-08 Google Inc. Server-based data sharing in computer applications using a clipboard
CN101854392B (en) * 2010-05-20 2012-11-14 清华大学 Personal data management method based on cloud computing environment
CN102202044A (en) * 2011-02-25 2011-09-28 北京兴宇中科科技开发股份有限公司 Portable cloud storage method and device
CN102882968B (en) * 2012-09-27 2014-12-10 广东电子工业研究院有限公司 Method for dynamically distributing cloud desktops
CN102868763B (en) * 2012-10-08 2015-12-09 山东省计算中心 The dynamic adjusting method that under a kind of cloud computing environment, virtual web application cluster is energy-conservation

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102546730A (en) * 2010-12-30 2012-07-04 中国移动通信集团公司 Data processing method, device and system
CN102158535A (en) * 2011-02-10 2011-08-17 浪潮(北京)电子信息产业有限公司 Cloud computing operating system
CN102291445A (en) * 2011-08-04 2011-12-21 上海龙照电子有限公司 Cloud computing management system based on virtual resources

Also Published As

Publication number Publication date
CN104008026A (en) 2014-08-27

Similar Documents

Publication Publication Date Title
EP2712119B1 (en) Abnormality handling method, device and client
US9529588B2 (en) Information processing apparatus and network system for updating firmware modules
WO2021129733A1 (en) Cloud operating system management method and apparatus, server, management system, and medium
US11144416B2 (en) Device fault processing method, apparatus, and system
CN104679530A (en) Server system and firmware updating method
EP3407187B1 (en) Optical line terminal, and method for upgrading master device and slave device
US8499202B2 (en) Method and system for recovery of a computing environment during pre-boot and runtime phases
TW200813837A (en) A chipset-independent method for locally and remotely updating and configuring system BIOS
CN108509215B (en) System software replacing method and device, terminal equipment and storage medium
CN105607972B (en) A kind of method and device repaired extremely
WO2012155412A1 (en) Firmware updating method and system under android system
JP2015507257A (en) Method and compute node for processing application data
WO2019100589A1 (en) Virtual machine rapid capacity expansion method, apparatus and device, and storage medium
US9319313B2 (en) System and method of forwarding IPMI message packets based on logical unit number (LUN)
WO2021169124A1 (en) Method and apparatus for installing software package to target host, and computer device
CN113391845A (en) Data interaction method and device and related components
US8719622B2 (en) Recording and preventing crash in an appliance
CN107623581B (en) Service list generation method, device and system, and acquisition and reporting method and device
CN107547277B (en) Method for realizing virtualization control board and network communication equipment
WO2024041283A1 (en) Client upgrading method and apparatus, terminal device, and storage medium
CN112631883B (en) PCIe data transmission pressure manufacturing method, system and electronic equipment
JP2018072944A (en) Program, system and information processing method
CN103870347A (en) System restoring method and device
CN108234174B (en) Management method and device of virtual network function
WO2014127610A1 (en) Method and device for cloud application data processing

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: 13875586

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: 13875586

Country of ref document: EP

Kind code of ref document: A1