CN110688199A - Data recovery method, system, electronic equipment and storage medium - Google Patents
Data recovery method, system, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN110688199A CN110688199A CN201910931257.1A CN201910931257A CN110688199A CN 110688199 A CN110688199 A CN 110688199A CN 201910931257 A CN201910931257 A CN 201910931257A CN 110688199 A CN110688199 A CN 110688199A
- Authority
- CN
- China
- Prior art keywords
- data
- target
- container
- docker container
- backup database
- Prior art date
- Legal status (The legal status 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 status listed.)
- Withdrawn
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1464—Management of the backup or restore process for networked environments
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45575—Starting, stopping, suspending or resuming virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Quality & Reliability (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses a data reduction method, which comprises the steps of receiving a reduction instruction of a target Docker container, and accessing a backup database according to the reduction instruction; the backup database comprises service data slices and configuration data slices of a Docker container; determining a container identifier of the target Docker container, and downloading target data corresponding to the container identifier in the backup database; and performing data reduction operation on the target Docker container by using the target data. The data recovery efficiency of the Docker container can be improved. The application also discloses a data recovery system, a storage medium and an electronic device, which have the beneficial effects.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a data restoring method and system, an electronic device, and a storage medium.
Background
A Docker container is an open source application container engine, and uses a sandbox mechanism, and there may be no interfaces between applications. The Docker container has a low performance overhead and can be easily run in machines and data centers.
At present, a Docker container is already adopted in a multi-device management system, but at present, the restoration operation corresponding to the Docker container is to restore data of the entire container. However, the entire reduction method has large reduction data, long reduction time, long recovery time, and a large amount of useless or redundant data in the reduction data, so the efficiency of the reduction operation of the Docker container in the above related art is low.
Therefore, how to improve the data reduction efficiency of the Docker container is a technical problem that needs to be solved by those skilled in the art.
Disclosure of Invention
The application aims to provide a data reduction method, a data reduction system, an electronic device and a storage medium, and the data reduction efficiency of a Docker container can be improved.
In order to solve the above technical problem, the present application provides a data reduction method, including:
receiving a restoring instruction of a target Docker container, and accessing a backup database according to the restoring instruction; the backup database comprises service data slices and configuration data slices of a Docker container;
determining a container identifier of the target Docker container, and downloading target data corresponding to the container identifier in the backup database;
and performing data reduction operation on the target Docker container by using the target data.
Optionally, the performing, by using the target data, a data reduction operation on the target Docker container includes:
inquiring the memory address of the target data in the target Docker container;
and covering the target data to a corresponding memory address so as to restore the target Docker container.
Optionally, downloading the target data corresponding to the container identifier in the backup database includes:
and setting a target service data slice and/or a target configuration data slice corresponding to the container identifier in the backup database as the target data, and downloading the target data.
Optionally, downloading the target data corresponding to the container identifier in the backup database includes:
and downloading the target data corresponding to the container identifier in the backup database to a temporary storage space of a host of the target Docker container.
Optionally, the method further includes:
querying a total data volume of the target data;
and when target data corresponding to the container identifier in the backup database is downloaded, calculating a data downloading progress according to the downloaded data volume and the total data volume.
Optionally, after performing a data restoring operation on the target Docker container by using the target data, the method further includes:
according to a preset period, slicing operation is carried out on the service data and the configuration data in the target Docker container to obtain a new service data slice and a new configuration data slice;
and uploading the new service data slice and the new configuration data slice to the backup database.
Optionally, the method further includes:
setting a first binding relationship between the new service data slice and the container identifier;
setting a second binding relationship between the new configuration data slice and the container identifier;
uploading the first binding relationship and the second binding relationship to the backup database.
The present application further provides a data restoring system, which includes:
the list query module is used for receiving a reduction instruction of a target Docker container and accessing a backup database according to the reduction instruction; the backup database comprises service data slices and configuration data slices of a Docker container;
the data downloading module is used for determining the container identifier of the target Docker container and downloading target data corresponding to the container identifier in the backup database;
and the restoring module is used for utilizing the target data to execute data restoring operation on the target Docker container.
The application also provides a storage medium, on which a computer program is stored, which when executed implements the steps performed by the above data restoring method.
The application also provides an electronic device, which comprises a memory and a processor, wherein the memory is stored with a computer program, and the processor realizes the steps executed by the data restoration method when calling the computer program in the memory.
The application provides a data reduction method which comprises the steps of receiving a reduction instruction of a target Docker container, and accessing a backup database according to the reduction instruction; the backup database comprises service data slices and configuration data slices of a Docker container; determining a container identifier of the target Docker container, and downloading target data corresponding to the container identifier in the backup database; and performing data reduction operation on the target Docker container by using the target data.
The method and the device query the backup database comprising the business data slices and the configuration data slices after receiving the reduction instruction, and further download the target data corresponding to the container identifications from the business data slices and the configuration data slices. For a user, if data restoration is required to be performed on the Docker container, only business data and configuration data may be concerned, and additional data such as Docker container process information and the like may not be required to be downloaded. According to the method and the device, the download amount of the backup data is reduced, and the data recovery efficiency of the Docker container can be improved. The application also provides a data recovery system, an electronic device and a storage medium, which have the beneficial effects and are not repeated herein.
Drawings
In order to more clearly illustrate the embodiments of the present application, the drawings needed for the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings can be obtained by those skilled in the art without inventive effort.
Fig. 1 is a flowchart of a data reduction method according to an embodiment of the present application;
fig. 2 is a flowchart of a data backup method according to an embodiment of the present application;
fig. 3 is a schematic diagram illustrating a principle of Docker container slice reduction in the multi-device management system according to the embodiment of the present application;
fig. 4 is a schematic structural diagram of a data restoring system according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1, fig. 1 is a flowchart of a data reduction method according to an embodiment of the present disclosure.
The specific steps may include:
s101: receiving a restoring instruction of a target Docker container, and accessing a backup database according to the restoring instruction;
the embodiment can be applied to a server, a server cluster or a multi-device management system provided with a Docker container. When a system problem such as system upgrade or misoperation occurs in the target Docker container, data in the target Docker container is lost, and at this time, data restoration operation needs to be performed on the target Docker container, so that the application in the target Docker container continues to provide services.
After receiving a restore instruction of the target Docker container, the backup database may be accessed according to the restore instruction. As a possible implementation manner, the backup database may have a slice list for displaying slice information of the stored data backup slices, and the present embodiment may determine the stored data backup slices in the backup database by acquiring the slice list. The backup data in this embodiment may be stored externally for the device, and the backup database may include a service data slice and a configuration data slice of the Docker container.
S102: determining a container identifier of the target Docker container, and downloading target data corresponding to the container identifier in the backup database;
in order to determine the backup data for restoring the target Docker container, the embodiment may first determine a container identifier of the target Docker container, and then download the corresponding target data based on the container identifier. As a possible implementation manner, the container identifier mentioned in this embodiment may be identification information, such as a container ID or a container number of the target Docker container, that uniquely corresponds to the target Docker container.
Before this step, there may be an operation of storing the data backup slices in the backup database, and when uploading the data backup slices, the correspondence between each data backup slice and the container identifier may be bound. Therefore, in this embodiment, the target data corresponding to the container identifier in the backup database may be downloaded according to the correspondence between each pre-stored data backup slice and the container identifier.
It should be noted that the target data mentioned in this embodiment may be a service data slice of a target Docker container, may also be a configuration data slice of the target Docker container, and may also be a service data slice and a configuration data slice. The embodiment may first present the backup data slice corresponding to the target Docker container in the backup database to the user, and determine the target data to be downloaded after receiving the selection information of the user. As a possible implementation manner, the process of downloading the target data in this step may be: and setting a target service data slice and/or a target configuration data slice corresponding to the container identifier in the backup database as the target data, and downloading the target data.
S103: and performing data reduction operation on the target Docker container by using the target data.
Based on the downloaded target data, the step may perform a data reduction operation on the target Docker container based on the target data.
As a possible implementation manner, the performing the data restoring operation by using the target data in this embodiment may include the following steps: inquiring the memory address of the target data in the target Docker container; and covering the target data to a corresponding memory address so as to restore the target Docker container. In this embodiment, the memory addresses in the Docker container may be recorded in the backup data slices stored in the backup database, so that the above embodiment may query the memory addresses of the target data in the target Docker container; and covering the target data to a corresponding memory address, thereby realizing the reduction of the target Docker container.
In this embodiment, after receiving the restore instruction, the backup database including the service data slice and the configuration data slice is queried, and then the target data corresponding to the container identifier is downloaded from the service data slice and the configuration data slice. For a user, if data restoration is required to be performed on the Docker container, only business data and configuration data may be concerned, and additional data such as Docker container process information and the like may not be required to be downloaded. According to the embodiment, the download amount of the backup data is reduced, and the data recovery efficiency of the Docker container can be improved.
As a further supplement to the embodiment corresponding to fig. 1, the operation of downloading the target data corresponding to the container identifier in the backup database in S102 may specifically be: and downloading the target data corresponding to the container identifier in the backup database to a temporary storage space of a host of the target Docker container. The host refers to a host where a target Docker container is located, and after target data are downloaded to a temporary storage space, the host can inquire the memory address of the target data in the target Docker container; and covering the target data to a corresponding memory address so as to restore the target Docker container.
As a further supplement to the corresponding embodiment in fig. 1, before performing a data restoring operation, this embodiment may also query a total data size of the target data; and when target data corresponding to the container identifier in the backup database is downloaded, calculating a data downloading progress according to the downloaded data volume and the total data volume.
Referring to fig. 2, fig. 2 is a flowchart of a data backup method provided in an embodiment of the present application, where this embodiment is a specific manner of backing up data in a target Docker container mentioned in the above embodiment, and embodiments corresponding to fig. 1 in this embodiment may be combined to obtain a more preferred embodiment, where this embodiment may include the following steps:
s201: according to a preset period, slicing operation is carried out on the service data and the configuration data in the target Docker container to obtain a new service data slice and a new configuration data slice;
s202: uploading the new business data slices and the new configuration data slices to the backup database;
s203: setting a first binding relationship between the new service data slice and the container identifier;
s204: setting a second binding relationship between the new configuration data slice and the container identifier;
s205: uploading the first binding relationship and the second binding relationship to the backup database.
The new service data slice and the new configuration data slice mentioned in this embodiment may be service data and configuration data newly generated in the target Docker container after the target Docker container is restored. When a new service data slice and a new configuration data slice are uploaded, the embodiment also uploads the binding relationship between the new service data slice and the new configuration data slice and the container identifier, so that when the memorable data of the new service data slice and the new configuration data slice is required to be used for reduction, the data required to be downloaded can be determined according to the container representation of the target Docker container.
The flow described in the above embodiment is explained below by an embodiment in practical use. Referring to fig. 3, fig. 3 is a schematic diagram illustrating a principle of Docker container slice reduction in a multi-device management system according to an embodiment of the present disclosure.
In this embodiment, a data slice list in an external storage (i.e., the backup database above) is first obtained, where the data slice list may include configuration data slices and service data slices; after the user selects the slice to be restored, the embodiment downloads the slice and transmits the slice to the position specified by the user, and the embodiment can display the specific restoration progress when executing the data restoration operation.
The above embodiment can be described by using Java language, the restore data (configuration data slice and service data slice) is stored in external storage, and the system provides the user with the list of slices to be restored. And after the user selects the slice to be restored, starting to restore the slice, and providing real-time restoration progress information.
Since the slice list is stored in the external storage, the user can view the slice list to be restored in the multi-device management system. The embodiment can download the slice data backed up in the external storage into the Docker container, and a user can check the download progress in real time by calculating the byte stream. The Docker slice data can be restored to the multi-device management system through memory addressing.
In the embodiment, the Docker container used by the multi-device management system is sliced, so that the user selects slice reduction and displays the reduction progress, directional reduction is realized, a large amount of reduction time is saved, and the data reduction efficiency of the Docker container is greatly improved
Referring to fig. 4, fig. 4 is a schematic structural diagram of a data recovery system according to an embodiment of the present disclosure;
the system may include:
the list query module 100 is configured to receive a restore instruction of a target Docker container, and access a backup database according to the restore instruction; the backup database comprises service data slices and configuration data slices of a Docker container;
a data downloading module 200, configured to determine a container identifier of the target Docker container, and download target data corresponding to the container identifier in the backup database;
a restoring module 300, configured to perform a data restoring operation on the target Docker container by using the target data.
In this embodiment, after receiving the restore instruction, the backup database including the service data slice and the configuration data slice is queried, and then the target data corresponding to the container identifier is downloaded from the service data slice and the configuration data slice. For a user, if data restoration is required to be performed on the Docker container, only business data and configuration data may be concerned, and additional data such as Docker container process information and the like may not be required to be downloaded. According to the embodiment, the download amount of the backup data is reduced, and the data recovery efficiency of the Docker container can be improved.
Further, the restoring module 300 includes:
a memory address query unit, configured to query a memory address of the target data in the target Docker container;
and the load unit is used for covering the target data to the corresponding memory address so as to restore the target Docker container.
Further, the data downloading module 200 includes:
an identifier determining unit for determining the container identifier of the target Docker container
And the downloading unit is used for setting a target service data slice and/or a target configuration data slice corresponding to the container identifier in the backup database as the target data and downloading the target data.
Further, the data downloading module 200 is specifically a module for downloading the target data corresponding to the container identifier in the backup database to a temporary storage space of a host of the target Docker container.
Further, the method also comprises the following steps:
a total amount determination unit, configured to query a total data amount of the target data;
and the download progress determining unit is used for calculating the data download progress according to the downloaded data volume and the total data volume when the target data corresponding to the container identifier in the backup database is downloaded.
Further, the method also comprises the following steps:
the backup data determining module is used for executing slicing operation on the service data and the configuration data in the target Docker container according to a preset period to obtain a new service data slice and a new configuration data slice;
and the data backup module is used for uploading the new service data slice and the new configuration data slice to the backup database.
Further, the method also comprises the following steps:
the first relation setting module is used for setting a first binding relation between the new service data slice and the container identifier;
a second relation setting module, configured to set a second binding relation between the new configuration data slice and the container identifier;
and the relationship uploading module is used for uploading the first binding relationship and the second binding relationship to the backup database.
Since the embodiment of the system part corresponds to the embodiment of the method part, the embodiment of the system part is described with reference to the embodiment of the method part, and is not repeated here.
The present application also provides a storage medium having a computer program stored thereon, which when executed, may implement the steps provided by the above-described embodiments. The storage medium may include: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The application further provides an electronic device, which may include a memory and a processor, where the memory stores a computer program, and the processor may implement the steps provided by the foregoing embodiments when calling the computer program in the memory. Of course, the electronic device may also include various network interfaces, power supplies, and the like.
The embodiments are described in a progressive manner in the specification, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. For the system disclosed by the embodiment, the description is relatively simple because the system corresponds to the method disclosed by the embodiment, and the relevant points can be referred to the method part for description. It should be noted that, for those skilled in the art, it is possible to make several improvements and modifications to the present application without departing from the principle of the present application, and such improvements and modifications also fall within the scope of the claims of the present application.
It is further noted that, in the present specification, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Claims (10)
1. A method of data reduction, comprising:
receiving a restoring instruction of a target Docker container, and accessing a backup database according to the restoring instruction; the backup database comprises service data slices and configuration data slices of a Docker container;
determining a container identifier of the target Docker container, and downloading target data corresponding to the container identifier in the backup database;
and performing data reduction operation on the target Docker container by using the target data.
2. The data reduction method of claim 1, wherein performing a data reduction operation on the target Docker container using the target data comprises:
inquiring the memory address of the target data in the target Docker container;
and covering the target data to a corresponding memory address so as to restore the target Docker container.
3. The data recovery method of claim 1, wherein downloading the target data in the backup database corresponding to the container identifier comprises:
and setting a target service data slice and/or a target configuration data slice corresponding to the container identifier in the backup database as the target data, and downloading the target data.
4. The data recovery method of claim 1, wherein downloading the target data in the backup database corresponding to the container identifier comprises:
and downloading the target data corresponding to the container identifier in the backup database to a temporary storage space of a host of the target Docker container.
5. The data reduction method according to claim 1, further comprising:
querying a total data volume of the target data;
and when target data corresponding to the container identifier in the backup database is downloaded, calculating a data downloading progress according to the downloaded data volume and the total data volume.
6. The data reduction method according to any one of claims 1 to 5, further comprising, after performing a data reduction operation on the target Docker container using the target data:
according to a preset period, slicing operation is carried out on the service data and the configuration data in the target Docker container to obtain a new service data slice and a new configuration data slice;
and uploading the new service data slice and the new configuration data slice to the backup database.
7. The data reduction method according to claim 6, further comprising:
setting a first binding relationship between the new service data slice and the container identifier;
setting a second binding relationship between the new configuration data slice and the container identifier;
uploading the first binding relationship and the second binding relationship to the backup database.
8. A method of data reduction, comprising:
the list query module is used for receiving a reduction instruction of a target Docker container and accessing a backup database according to the reduction instruction; the backup database comprises service data slices and configuration data slices of a Docker container;
the data downloading module is used for determining the container identifier of the target Docker container and downloading target data corresponding to the container identifier in the backup database;
and the restoring module is used for utilizing the target data to execute data restoring operation on the target Docker container.
9. An electronic device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the data restoration method according to any one of claims 1 to 7 when the processor calls the computer program in the memory.
10. A storage medium having stored thereon computer-executable instructions which, when loaded and executed by a processor, carry out the steps of a data reduction method as claimed in any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910931257.1A CN110688199A (en) | 2019-09-29 | 2019-09-29 | Data recovery method, system, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910931257.1A CN110688199A (en) | 2019-09-29 | 2019-09-29 | Data recovery method, system, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110688199A true CN110688199A (en) | 2020-01-14 |
Family
ID=69110978
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910931257.1A Withdrawn CN110688199A (en) | 2019-09-29 | 2019-09-29 | Data recovery method, system, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110688199A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111880896A (en) * | 2020-07-17 | 2020-11-03 | 山东迪特智联信息科技有限责任公司 | Method and device for rapidly restoring container and running state data |
| CN112214351A (en) * | 2020-10-12 | 2021-01-12 | 珠海格力电器股份有限公司 | Backup data recovery method and device, electronic equipment and storage medium |
| CN114328007A (en) * | 2021-11-19 | 2022-04-12 | 苏州浪潮智能科技有限公司 | Container backup and restoration method, device and medium thereof |
-
2019
- 2019-09-29 CN CN201910931257.1A patent/CN110688199A/en not_active Withdrawn
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111880896A (en) * | 2020-07-17 | 2020-11-03 | 山东迪特智联信息科技有限责任公司 | Method and device for rapidly restoring container and running state data |
| CN112214351A (en) * | 2020-10-12 | 2021-01-12 | 珠海格力电器股份有限公司 | Backup data recovery method and device, electronic equipment and storage medium |
| CN114328007A (en) * | 2021-11-19 | 2022-04-12 | 苏州浪潮智能科技有限公司 | Container backup and restoration method, device and medium thereof |
| CN114328007B (en) * | 2021-11-19 | 2024-03-22 | 苏州浪潮智能科技有限公司 | Container backup and restoration method, device and medium thereof |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110688199A (en) | Data recovery method, system, electronic equipment and storage medium | |
| CN105335187B (en) | Application processing method and device | |
| CN102520987B (en) | Online experience and installation method, device, server and management system of application program | |
| CN104461504B (en) | A kind of management method of end application | |
| CN108920212B (en) | Linux kernel-based product starting method and system and related components | |
| CN110971571A (en) | Website domain name verification method and related device | |
| CN104461505B (en) | A kind of terminal | |
| CN104932955A (en) | Method for backing up data during factory setting restoring of mobile terminal, and mobile terminal | |
| US9213561B2 (en) | Virtual appliance deployment | |
| CN111371645B (en) | Method, system, computer equipment and storage medium for testing service connectivity | |
| CN105119944A (en) | Application starting method and related device | |
| CN116450287A (en) | Method, device, equipment and readable medium for managing storage capacity of service container | |
| US7281165B2 (en) | System and method for performing product tests utilizing a single storage device | |
| US9501316B2 (en) | Instantiating virtual appliances of a storage array | |
| CN111026613B (en) | Log processing method and device | |
| CN110795674B (en) | Configuration updating method and device | |
| CN110795388B (en) | Binary file processing method, system, equipment and readable storage medium | |
| US9792130B2 (en) | Rebooting to a UEFI application from a UEFI supported system | |
| US20150081968A1 (en) | Decommissioning virtual appliances | |
| CN113268288B (en) | Shared file configuration method and device | |
| CN111880996B (en) | Bare metal data acquisition method, device, equipment and readable storage medium | |
| CN114116030A (en) | Operating system running method and device, electronic equipment and storage medium | |
| CN109413176B (en) | Report downloading method and device | |
| US10474535B2 (en) | Asset browsing and restoration over a network using on demand staging | |
| CN108197291B (en) | Operation execution method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20200114 |
|
| WW01 | Invention patent application withdrawn after publication |