WO2016054886A1 - Procédé et appareil de mise à niveau de logiciel, dispositif électronique et support d'enregistrement - Google Patents
Procédé et appareil de mise à niveau de logiciel, dispositif électronique et support d'enregistrement Download PDFInfo
- Publication number
- WO2016054886A1 WO2016054886A1 PCT/CN2015/072807 CN2015072807W WO2016054886A1 WO 2016054886 A1 WO2016054886 A1 WO 2016054886A1 CN 2015072807 W CN2015072807 W CN 2015072807W WO 2016054886 A1 WO2016054886 A1 WO 2016054886A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- patch
- client
- electronic device
- request
- upgrade
- Prior art date
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/445—Program loading or initiating
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Definitions
- the present invention relates to computer technology, and in particular, to a software upgrade method, apparatus, and electronic device and storage medium.
- a hot patch upgrade is a code segment replacement.
- a cold patch upgrade refers to the replacement of an executable body (that is, a process) itself.
- the patch is a program that solves the problem developed by the problem exposed during the use of the software.
- the hot patch upgrade can implement partial software modification in a timely manner without interrupting the operation of the business, reducing the number of software upgrades.
- the hot patch upgrade has the following limitations and disadvantages: First, the macro value, the original structure and the variables, and the number of parameters of the function cannot be modified. Second, the hot patches have complex dependencies on each other, and subsequent maintenance and management. It is more difficult and may even cause hot patches to be unavailable.
- Cold patch upgrades are a thorough and pure fix, and there are no restrictions on the above hot patch upgrades.
- the repair of the critical process requires the re-allocation of some of the underlying resources, the device needs to be reset after the cold patch upgrade, which has a long service interruption time and affects the normal operation of the service.
- embodiments of the present invention are expected to provide a software upgrade method, apparatus, and electronic device and storage medium.
- a software upgrade method provided by an embodiment of the present invention is applied to a server end of an electronic device,
- the electronic device is installed with software, and the method includes:
- the first patch and the second patch specified by the patch adding request are added at the same time, the first patch is used for hot patch upgrade, and the second patch is used for cold patch upgrade;
- the software upgrade method provided by the embodiment of the present invention is applied to an electronic device installed with software, where the electronic device includes a server and a client, and the method includes:
- the server receives a patch addition request
- the server adds the first patch and the second patch specified by the patch adding request to the electronic device, where the first patch is used for hot patch upgrade, and the second patch is used for cold patch upgrade. Notifying the client to apply the first patch to the instant application, and notifying the client to apply the second patch when the electronic device is restarted;
- the client applies the first patch or the second patch according to the notification of the server.
- a software upgrade device is provided in an embodiment of the present invention.
- the device is installed in an electronic device, where the electronic device is installed with software, and the device includes:
- the patch adding unit is configured to receive a patch adding request, and the first patch and the second patch specified by the patch adding request are simultaneously added, where the first patch is used for hot patch upgrade, and the second patch is used for cold Patch upgrade;
- the notification unit is configured to notify the client to apply the first patch to the instant application, and notify the client to apply the second patch when the electronic device is restarted.
- An electronic device is provided by the embodiment of the present invention, where the electronic device is installed with software, and the electronic device includes: a server and a client, where
- the server is configured to receive a patch addition request, and add the patch addition request
- the first patch and the second patch are added simultaneously, the first patch is used for hot patch upgrade, the second patch is used for cold patch upgrade, and configured to notify the client to perform the first patch.
- Instant application and when the electronic device is restarted, notifying the client to apply the second patch;
- the client is configured to apply the first patch or the second patch according to the notification of the server.
- the embodiment of the invention further provides a computer storage medium, wherein a computer program is stored, which is used to execute the software upgrade method applied to the server of the electronic device.
- the technical solution of the embodiment of the present invention adds a cold patch while adding a hot patch.
- Hot patches are applied immediately, but cold patches are not applied immediately, but are applied when a reset is performed on the electronic device due to system maintenance. In this way, you can use the hot patch to fix the problem.
- the cold patch When the device is restarted at the appropriate time, use the cold patch to avoid restarting the device due to the cold upgrade and ensure the normal operation. And you can delete the hot patches that are no longer needed, so as to avoid the adverse effects caused by too many hot patches.
- FIG. 1 is a schematic flowchart of a first embodiment of a software upgrade method according to the present invention
- FIG. 2 is a schematic flowchart of a second embodiment of a software upgrade method according to the present invention.
- FIG. 3 is a schematic flowchart of a first embodiment of another software upgrade method according to the present invention.
- FIG. 4 is a schematic flowchart diagram of a second embodiment of another software upgrade method according to the present invention.
- FIG. 5 is a schematic structural diagram of an embodiment of a software upgrading apparatus according to the present invention.
- FIG. 6 is a schematic structural diagram of an embodiment of an electronic device according to the present invention.
- FIG. 7 is a schematic structural diagram of another embodiment of an electronic device according to the present invention.
- FIG. 8 is a schematic flowchart of an application scenario of a software upgrade method according to the present invention.
- FIG. 9 is a schematic flowchart of a patch addition according to an embodiment of the present invention.
- FIG. 10 is a schematic flowchart of a patch application according to an embodiment of the present disclosure.
- FIG. 11 is a schematic flowchart of a patch deletion according to an embodiment of the present invention.
- FIG. 12 is a schematic flowchart of a patch information query according to an embodiment of the present disclosure.
- FIG. 13 is a schematic flowchart of a patch application status query according to an embodiment of the present invention.
- the first embodiment of the software upgrade method provided by the present invention is applied to a server of an electronic device, and the electronic device is installed with software. As shown in FIG. 1 , the method includes:
- Step 101 Receive a patch addition request.
- Step 102 The first patch and the second patch specified by the patch adding request are added at the same time, where the first patch is used for hot patch upgrade, and the second patch is used for cold patch upgrade.
- the first patch may be one or more, and the second patch is capable of repairing a problem that is addressed by multiple first patches that have been added or applied.
- first patch and the second patch may be set in one upgrade package, or may be set in two independent upgrade packages.
- the first patch and the second patch respectively include program information and configuration information, where the configuration information may include information of the patch itself and information of the patch repair object, where the information of the patch itself may include a patch.
- Information such as size, name, status (if applied), version number, file name, and so on.
- the configuration information of the first patch and the second patch is stored in a volatile memory, and the first patch and the second patch are stored in a non-volatile memory.
- the volatile memory may be a memory
- the non-volatile memory may be a hard disk.
- Step 103 The control client applies the first patch to the instant application, and when the electronic device restarts, controls the client to apply the second patch.
- the second embodiment of the software upgrade method provided by the present invention is applied to a server of an electronic device, and the electronic device is installed with software. As shown in FIG. 2, the method includes:
- Step 201 Receive a patch addition request.
- Step 202 Add the first patch and the second patch that are specified by the patch adding request, where the first patch is used for hot patch upgrade, and the second patch is used for cold patch upgrade.
- the first patch may be one or more, and the second patch is capable of repairing a problem that is addressed by multiple first patches that have been added or applied.
- first patch and the second patch may be set in one upgrade package, or may be set in two independent upgrade packages.
- the first patch and the second patch respectively include program information and configuration information, where the configuration information may include information of the patch itself and information of the patch repair object, where the information of the patch itself may include a patch.
- Information such as size, name, status (if applied), version number, file name, and so on.
- the configuration information of the first patch and the second patch is stored in a volatile memory, and the first patch and the second patch are stored in a non-volatile memory.
- the volatile memory may be a memory
- the non-volatile memory may be a hard disk.
- Step 203 The control client applies the first patch to the instant application, and when the electronic device restarts, controls the client to apply the second patch.
- Step 204 Receive a patch deletion request.
- Step 205 Delete the first patch specified by the patch deletion request.
- the deleting the first patch specified by the patch deletion request may include:
- the method may further include:
- the method further includes:
- the server receives a patch information query request
- the server obtains and outputs the configuration information specified by the patch information query request from the volatile memory according to the patch information query request.
- the method further includes:
- the configuration information corresponding to the first patch or the second patch is modified.
- the first embodiment of the software upgrade method provided by the present invention is applied to an electronic device installed with software.
- the electronic device includes a server and a client. As shown in FIG. 3, the method includes:
- Step 301 The server receives a patch addition request.
- Step 302 The server adds the first patch and the second patch specified by the patch adding request to the electronic device, where the first patch is used for hot patch upgrade, and the second patch is used for Cold patch upgrade;
- the first patch may be one or more, and the second patch is capable of repairing a problem that is addressed by multiple first patches that have been added or applied.
- first patch and the second patch may be set in one upgrade package, or may be set in two independent upgrade packages.
- the first patch and the second patch respectively include program information and configuration information
- the configuration information may include information of the patch itself and information of the patch repair object, where the information of the patch itself may include information such as a size, a name, a status (such as whether it has been applied), a version number, a file name, and the like.
- the configuration information of the first patch and the second patch is stored in a volatile memory, and the first patch and the second patch are stored in a non-volatile memory.
- the volatile memory may be a memory
- the non-volatile memory may be a hard disk.
- Step 303 The client is notified to apply the first patch to the instant application, and when the electronic device is restarted, notify the client to apply the second patch.
- Step 304 The client applies the first patch or the second patch according to the notification of the server.
- the second embodiment of the software upgrade method provided by the present invention is applied to an electronic device installed with software.
- the electronic device includes a server and a client. As shown in FIG. 4, the method includes:
- Step 401 The server receives a patch addition request.
- Step 402 The server adds the first patch and the second patch specified by the patch adding request to the electronic device, where the first patch is used for hot patch upgrade, and the second patch is used for Cold patch upgrade;
- the first patch may be one or more, and the second patch is capable of repairing a problem that is addressed by multiple first patches that have been added or applied.
- first patch and the second patch may be set in one upgrade package, or may be set in two independent upgrade packages.
- the first patch and the second patch respectively include program information and configuration information
- the configuration information may include information of the patch itself and information of the patch repair object, where the information of the patch itself may include information such as a size, a name, a status (such as whether it has been applied), a version number, a file name, and the like.
- the configuration information of the first patch and the second patch is stored in a volatile memory, and the first patch and the second patch are stored in a non-volatile memory.
- the volatile memory may be a memory
- the non-volatile memory may be a hard disk.
- Step 403 The client is notified to apply the first patch to the instant application, and when the electronic device is restarted, notify the client to apply the second patch.
- Step 404 The client applies the first patch or the second patch according to the notification of the server.
- Step 405 The server receives a patch deletion request.
- Step 406 The server deletes the first patch specified by the patch deletion request.
- the method may further include:
- the server receives a patch status query request
- the server sends the patch status query request to the client
- the client obtains patch status information by querying according to the received patch status query request;
- the server receives and outputs patch status information fed back by the client.
- the method further includes:
- the server receives a patch information query request
- the server obtains and outputs the configuration information specified by the patch information query request from the volatile memory according to the patch information query request.
- the method further includes:
- the configuration information corresponding to the first patch or the second patch is modified.
- the apparatus is disposed in an electronic device, and the electronic device is installed with software.
- the software upgrading device may be a server end of the electronic device, as shown in the figure. As shown in Figure 5, the device comprises:
- the patch adding unit 501 is configured to receive a patch adding request, and the first patch and the second patch specified by the patch adding request are simultaneously added, where the first patch is used for hot patch upgrade, and the second patch is used for Cold patch upgrade;
- the first patch may be one or more, and the second patch is capable of repairing a problem that is addressed by multiple first patches that have been added or applied.
- first patch and the second patch may be set in one upgrade package, or may be set in two independent upgrade packages.
- the first patch and the second patch respectively include program information and configuration information, where the configuration information may include information of the patch itself and information of the patch repair object, where the information of the patch itself may include a patch.
- Information such as size, name, status (if applied), version number, file name, and so on.
- the patch adding unit 501 is specifically configured to store configuration information of the first patch and the second patch into a volatile memory, and store the first patch and the second patch into a non-volatile memory.
- the volatile memory may be a memory
- the non-volatile memory may be a hard disk.
- the notification unit 502 is configured to notify the client to apply the first patch to the instant application, and notify the client to apply the second patch when the electronic device is restarted.
- the apparatus further includes:
- the patch deleting unit 503 is configured to receive a patch deletion request, and delete the first patch specified by the patch deletion request.
- the patch deleting unit is specifically configured to delete the configuration information of the first patch from the volatile memory, and delete the first patch from the non-volatile memory.
- the apparatus further includes:
- the patch status query unit 504 is configured to receive a patch status query request, send the patch status query request to the client, and receive and output patch status information fed back by the client, where the patch status information is the client The terminal obtains the query according to the received patch status query request.
- the apparatus further includes:
- the patch information querying unit is configured to receive the patch information query request, and obtain and output the configuration information specified by the patch information query request from the volatile memory according to the patch information query request.
- the configuration information corresponding to the first patch or the second patch is modified.
- An embodiment of an electronic device is provided.
- the electronic device is installed with software.
- the electronic device includes: a server 601 and a client 602, where
- the server 601 is configured to receive a patch addition request, and add the first patch and the second patch specified by the patch addition request at the same time, where the first patch is used for hot patch upgrade, and the second patch is used. For the cold patch upgrade; and configured to notify the client to apply the first patch to the instant application, and notify the client to apply the second patch when the electronic device is restarted;
- the client 602 is configured to apply the first patch or the second patch according to the notification of the server.
- the first patch may be one or more, and the second patch.
- first patch and the second patch may be set in one upgrade package, or may be set in two independent upgrade packages.
- the first patch and the second patch respectively include program information and configuration information, where the configuration information may include information of the patch itself and information of the patch repair object, where the information of the patch itself may include a patch.
- Information such as size, name, status (if applied), version number, file name, and so on.
- the server 601 is specifically configured to store configuration information of the first patch and the second patch into a volatile memory, and store the first patch and the second patch into a non-volatile memory.
- the volatile memory may be a memory
- the non-volatile memory may be a hard disk.
- the server 601 is further configured to receive a patch deletion request, and delete the first patch specified by the patch deletion request.
- the server 601 is further configured to receive a patch information query request, and obtain, according to the patch information query request, the configuration information specified by the patch information query request from the volatile memory.
- the configuration information corresponding to the first patch or the second patch is modified.
- the electronic device provided by the embodiment of the present invention is applicable to both the stand-alone mode and the distributed mode, as shown in FIG. 7.
- the server manages all the patch information, such as the added patch information and the patch information of the application. It is responsible for handling the addition, application, deletion, and status query operations of the patch. When the patch information changes, it determines whether to notify the client according to the configuration.
- the client is responsible for the execution of the patch application; actively requests information from the server, or passively accepts the patch change notification of the server.
- the server can also be called the patch management server, and the client can also be called the patch management client.
- the method includes:
- the cold patch contains a fix for the previous hot patch.
- the cold patches and hot patches are not limited here. They must be in an upgrade package and can be made separately.
- the hot patch is applied immediately, and the cold patch is not applied immediately. If the device restarts abnormally, the cold patch will take effect after the restart.
- S901 The server receives an external patch service request.
- the server adds the patch package and its information, and records the patch information to the in-memory database.
- the patch package can be stored in a permanent medium such as a hard disk or a flash of an electronic device for use when the electronic device is booted.
- the patch information may refer to the configuration information in the above.
- S1001 The server receives an external application patch package request.
- S1002 The server records the patch information to the in-memory database. If it does not need to take effect immediately, go directly to S1007; if it needs to take effect immediately, go to S1003.
- the hot patch is configured to take effect immediately, and the hot patch is configured to take effect immediately.
- S1003 The server notifies the client of the patch information.
- the client responds to the server.
- S1007 The server responds to the external application patch package.
- S1101 The server receives an external removal patch request.
- the server deletes the patch package and its information, and deletes the patch information record from the in-memory database, and the patch package is permanently deleted.
- FIG. 12 it is a process of querying the patch information, and querying the patch information of the added or applied patch.
- the detailed steps are as follows:
- S1201 The server receives an external patch information query request.
- S1202 The server queries the patch information record from the in-memory database.
- S1301 The server receives an external patch application status query request.
- the server sends an application status query request to the client.
- S1305 The server applies a status query response to the external patch.
- embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may employ hardware embodiments, software embodiments, or junctions. In the form of an embodiment of the software and hardware aspects. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.
- the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
- the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
- These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
- the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
- the embodiment of the present invention further provides a computer storage medium, wherein a computer program is stored, and the computer program is used to execute a software upgrade method applied to a server of an electronic device according to an embodiment of the present invention.
- the server adds a hot patch to the client and adds a cold patch, and the hot patch is applied immediately, but the cold patch is not applied immediately, but is applied when the electronic device is reset due to system maintenance. .
- the cold patch When the device is restarted at the appropriate time, use the cold patch to avoid restarting the device due to the cold upgrade and ensure the normal operation. And you can delete the hot patches that are no longer needed, so as to avoid the adverse effects caused by too many hot patches.
Abstract
La présente invention concerne un procédé et un appareil de mise à niveau de logiciel, un dispositif électronique et un support d'enregistrement. Le procédé comprend les étapes consistant à : (101) recevoir une requête d'ajout de correctif ; (102) ajouter simultanément un premier correctif et un second correctif qui sont spécifiés dans la requête d'ajout de correctif, le premier correctif étant utilisé pour une mise à niveau de correctif à chaud et le second correctif étant utilisé pour une mise à niveau de correctif à froid ; et (103) commander à un client d'appliquer le premier correctif immédiatement et commander au client d'appliquer le second correctif quand un dispositif électronique est redémarré.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201410528297.9 | 2014-10-09 | ||
CN201410528297.9A CN105573766A (zh) | 2014-10-09 | 2014-10-09 | 一种软件升级方法、装置和电子设备 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016054886A1 true WO2016054886A1 (fr) | 2016-04-14 |
Family
ID=55652528
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2015/072807 WO2016054886A1 (fr) | 2014-10-09 | 2015-02-11 | Procédé et appareil de mise à niveau de logiciel, dispositif électronique et support d'enregistrement |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN105573766A (fr) |
WO (1) | WO2016054886A1 (fr) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111949292A (zh) * | 2020-07-30 | 2020-11-17 | 锐捷网络股份有限公司 | 一种热补丁装载方法、装置、电子设备及存储介质 |
CN112906008A (zh) * | 2018-11-15 | 2021-06-04 | 百度在线网络技术(北京)有限公司 | 内核漏洞修复方法、装置、服务器及系统 |
CN113312079A (zh) * | 2020-11-20 | 2021-08-27 | 锐捷网络股份有限公司 | 一种热补丁升级方法、装置、电子设备及存储介质 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1464386A (zh) * | 2002-06-25 | 2003-12-31 | 联想(北京)有限公司 | 嵌入式系统中固件程序在线升级的实现方法 |
CN101008899A (zh) * | 2007-01-26 | 2007-08-01 | 上海华为技术有限公司 | 通信设备中软件版本升级的方法及装置 |
CN101137177A (zh) * | 2007-10-10 | 2008-03-05 | 中兴通讯股份有限公司 | 一种无线通信系统中管理软件补丁的方法 |
CN101192157A (zh) * | 2006-11-22 | 2008-06-04 | 乐金电子(昆山)电脑有限公司 | 家庭网络系统的软件升级方法 |
US20130007733A1 (en) * | 2011-06-29 | 2013-01-03 | Microsoft Corporation | Virtual machine block substitution |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
NO20021247D0 (no) * | 2002-03-13 | 2002-03-13 | Ericsson Telefon Ab L M | Fremgangsmåte og system for oppgradering av programvare |
CN100366116C (zh) * | 2004-08-29 | 2008-01-30 | 华为技术有限公司 | 通信设备子系统升级方法 |
CN102609290B (zh) * | 2012-02-17 | 2016-06-15 | 青岛海信电器股份有限公司 | 电子产品的软件升级方法 |
-
2014
- 2014-10-09 CN CN201410528297.9A patent/CN105573766A/zh active Pending
-
2015
- 2015-02-11 WO PCT/CN2015/072807 patent/WO2016054886A1/fr active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1464386A (zh) * | 2002-06-25 | 2003-12-31 | 联想(北京)有限公司 | 嵌入式系统中固件程序在线升级的实现方法 |
CN101192157A (zh) * | 2006-11-22 | 2008-06-04 | 乐金电子(昆山)电脑有限公司 | 家庭网络系统的软件升级方法 |
CN101008899A (zh) * | 2007-01-26 | 2007-08-01 | 上海华为技术有限公司 | 通信设备中软件版本升级的方法及装置 |
CN101137177A (zh) * | 2007-10-10 | 2008-03-05 | 中兴通讯股份有限公司 | 一种无线通信系统中管理软件补丁的方法 |
US20130007733A1 (en) * | 2011-06-29 | 2013-01-03 | Microsoft Corporation | Virtual machine block substitution |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112906008A (zh) * | 2018-11-15 | 2021-06-04 | 百度在线网络技术(北京)有限公司 | 内核漏洞修复方法、装置、服务器及系统 |
CN111949292A (zh) * | 2020-07-30 | 2020-11-17 | 锐捷网络股份有限公司 | 一种热补丁装载方法、装置、电子设备及存储介质 |
CN111949292B (zh) * | 2020-07-30 | 2023-03-21 | 锐捷网络股份有限公司 | 一种热补丁装载方法、装置、电子设备及存储介质 |
CN113312079A (zh) * | 2020-11-20 | 2021-08-27 | 锐捷网络股份有限公司 | 一种热补丁升级方法、装置、电子设备及存储介质 |
Also Published As
Publication number | Publication date |
---|---|
CN105573766A (zh) | 2016-05-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10268472B2 (en) | Upgrading systems with replicated data | |
US9436556B2 (en) | Customizable storage system for virtual databases | |
CN107870968B (zh) | 对文件系统卷执行实时更新 | |
US10445186B1 (en) | Associating a guest application within a virtual machine to create dependencies in backup/restore policy | |
US10956374B2 (en) | Data recovery method, apparatus, and system | |
US10684791B2 (en) | System and method for environment aware backup and restoration | |
US10572350B1 (en) | System and method for improved application consistency in a distributed environment | |
US11231919B2 (en) | Live updates of stateful components | |
US11500812B2 (en) | Intermediate file processing method, client, server, and system | |
WO2016054886A1 (fr) | Procédé et appareil de mise à niveau de logiciel, dispositif électronique et support d'enregistrement | |
US20200089587A1 (en) | Disaster recovery specific configurations, management, and application | |
US10572349B2 (en) | System and method for backup in a virtualized environment | |
US11126507B2 (en) | System and method for data-less backups modification during checkpoint merging | |
US20140297594A1 (en) | Restarting a Batch Process From an Execution Point | |
US11288140B2 (en) | Point in time blob restore | |
US10976952B2 (en) | System and method for orchestrated application protection | |
US10713218B2 (en) | System and method to optimally apply local retention in a remote repository | |
US10268698B2 (en) | Synchronizing different representations of content | |
EP3591531B1 (fr) | Restauration instantanée et l'accès instantané de vms hyper-v et applications fonctionnant à l'intérieur d'un vms utilisant des boostfs de domaine de données | |
US11782796B2 (en) | Method and system for virtual machine protection | |
US10936429B2 (en) | System and method for a fast backup operation remediation during a network disruption using a helper virtual machine | |
US11288137B2 (en) | Restorations of virtual machines in virtual systems using a restoration policy | |
US20220229659A1 (en) | Pull based inner-loop code deployment | |
US9268576B1 (en) | Physical replica utilizing replica virtual storage for computer system | |
US11381662B2 (en) | Transition of business-object based application architecture via dynamic feature check |
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: 15849515 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: 15849515 Country of ref document: EP Kind code of ref document: A1 |