CN111708660B - Backup system, recovery system and method based on container sandbox - Google Patents
Backup system, recovery system and method based on container sandbox Download PDFInfo
- Publication number
- CN111708660B CN111708660B CN202010554381.3A CN202010554381A CN111708660B CN 111708660 B CN111708660 B CN 111708660B CN 202010554381 A CN202010554381 A CN 202010554381A CN 111708660 B CN111708660 B CN 111708660B
- Authority
- CN
- China
- Prior art keywords
- container
- layer
- backup
- sandbox
- application
- 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.)
- Active
Links
Classifications
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a backup system, a recovery system and a method based on a container sandbox, which belong to the field of linux system development and application and comprise a kernel driving layer, a customized desktop layer, a data storage layer and an application center layer which are arranged in the container sandbox; the system is started based on container sandboxes in a layered mode, and after the system is started, basic system files are loaded to serve as bottom container sandboxes; by executing persistence operation on the started system, the system automatically solidifies and modifies the command to generate a new container layer; starting a basic file and a modified new container layer when starting next time; the system backup is realized by integrally backing up the container sandbox to the external equipment, and the system is restored to the designated position by using the external equipment of the container sandbox carrying the system backup; the system backup and recovery are realized quickly, and the safety of the system is ensured.
Description
Technical Field
The disclosure relates to the field of linux system development and application, in particular to a backup system, a recovery system and a method based on a container sandbox.
Background
The statements in this section merely provide background information related to the present disclosure and may not necessarily constitute prior art.
While an application cannot crash a normal modern operating system, it can cause significant human damage to the operating system's operating environment. From a resource utilization perspective, how to limit the resources that a process or a group of processes can use is also a problem to be solved. The concept of sandboxes (i.e., sandbox) is thus devised to isolate an application or group of applications in a restricted environment from escaping. For sandboxes, it is a process rather than a thread, however Linux schedules by default a thread rather than scheduling a process first and then a thread, and in the kernel, the CPU resources between the sandboxes of the process are inherently shared rather than isolated.
The backup and restore system takes on the roles of backup in advance and restoration in advance. In the current network environment with high development speed, as long as a network exists, various security threats from the network exist, and security events caused by network intrusion are increasing year by year. Under the condition, the absolute safety of a key system in the network is difficult to ensure, so that a backup and recovery technology is needed to ensure that data can be recovered as soon as possible when accidental loss occurs, and the loss of a user is reduced to the minimum point.
The inventor discovers that the existing system backup and recovery methods are mostly slower in speed, and the accuracy, instantaneity and self-defined backup of the backup cannot be realized; because the system backup is a modification of the basic system, the prior art is a backup of the modifications, namely, an incremental backup of the whole system level is performed every time, and the backup is only for the current version of the system, the system backup is not compatible after the basic system is replaced, which causes two problems: (1) For example, three times of backup are carried out on the system, wherein the first backup is A, the second backup is B, the third backup is C, the C contains modification of B, the B contains modification of A, the backup file is larger and larger, and if the backup file is not cleaned timely, the backup speed is slower after the backup file is moved; (2) Only incremental backups of the whole system can be made, and no backup can be made for a specified module or a specified layer of the system.
Disclosure of Invention
In order to solve the defects of the prior art, the present disclosure provides a backup system, a recovery system and a method based on a container sandbox, which realize rapid system backup and recovery and ensure the security of the system.
In order to achieve the above purpose, the present disclosure adopts the following technical scheme:
a first aspect of the present disclosure provides a container sandbox-based backup system.
The backup system based on the container sandbox is characterized by comprising a plurality of working layers arranged in the container sandbox, wherein the system is started based on the container sandbox in a layered manner, and after the system is started, a basic system file is loaded as a bottom container sandbox;
and executing persistence operation on the started system, automatically solidifying the modification command by the system to generate a new container layer, starting the basic file and the modified new container layer when starting next time, and realizing system backup by integrally backing up the container sandbox to external equipment.
The new container layer is loaded on the previous layer, and the previous layer is loaded at the next starting time; the modified container layer may be a custom desktop layer or a data storage layer or an application center layer, and the kernel layer does not allow modification.
A second aspect of the present disclosure provides a container sandbox-based backup method.
The container sandbox-based backup method comprises the following steps of: starting external equipment, and starting to a Shell state according to a linuxrecue mode; a data disk for backup is hung; a backup system; disconnecting the external device.
As some possible implementation manners, the process of backing up the container sandboxes is specifically:
checking a container list to be backed up;
after finding the container to be backed up, creating a snapshot of the container, and generating a container snapshot serving as a mirror image, wherein the snapshot comprises the ID of the container to be backed up and a new mirror image name;
taking the obtained snapshot as a mirror image to be saved, and for backing up the snapshot, running a login command to log in a registration center and pushing the mirror image to a memory;
before uploading, firstly labeling the mirror image, wherein the parameters of the label comprise the mirror image name and a new label name;
after the labeling is completed, a save operation is performed.
As some possible implementation manners, the process of backing up the container sandboxes is specifically:
checking a container list to be backed up;
after finding the container to be backed up, creating a snapshot of the container, and generating a container snapshot serving as a mirror image, wherein the snapshot comprises the ID of the container to be backed up and a new mirror image name;
and storing the obtained snapshot as a mirror image, and for backing up the snapshot, packing the mirror image into a tar package to be backed up locally.
A third aspect of the present disclosure provides a container sandbox-based restoration system.
A recovery system based on container sandboxes comprises a memory, wherein the memory stores the backed-up container sandboxes;
the container sandbox comprises a plurality of working layers, the system is started based on the container sandbox in a layered mode, and after the system is started, a basic system file is loaded to serve as a bottom container sandbox
By executing persistence operation on the started system, the system automatically solidifies the modification command to generate a new container layer, and the base file and the modified new container layer are started when the system is started next time;
and directly restoring the container sandboxes stored in the backup storage to the preset positions.
A fourth aspect of the present disclosure provides a container sandbox-based restoration method.
A container sandbox-based recovery method, comprising the container sandbox-based recovery system of the third aspect of the present disclosure, comprising the steps of: restoring the hardware to a normal state; starting external equipment, and starting to a Shell state according to a linuxrecue mode; a data disk for backup is hung; restoring the system; disconnecting the external device.
As some possible implementation manners, the external equipment of the container sandbox carrying the system backup is utilized to restore the system to a specified position, which comprises a container restoration process, specifically, a container is restored through pull, and the mirror image pushed by the registry is dragged back and directly operated.
As some possible implementation manners, if the image is backed up to the local as a tar package file, the image is loaded from the local, and after the success of loading the image is confirmed, the container sandbox is operated.
A fifth aspect of the present disclosure provides an electronic device comprising the container sandbox-based backup system of the first aspect of the present disclosure and/or the recovery system of the third aspect.
Compared with the prior art, the beneficial effects of the present disclosure are:
1. according to the system, the operating systems are arranged in the container sandboxes, so that the backup and recovery of the systems can be realized rapidly, and meanwhile, the starting speed is improved and the starting safety of the systems is ensured by the layer-by-layer starting mode of the container sandboxes.
2. According to the system backup method, the system backup is realized by integrally backing up the container sandbox to the external equipment, the external equipment of the container sandbox carrying the system backup is utilized to restore the system to the designated position, and only the backup and the restoration of the container sandbox are needed, so that the convenience of the backup and the restoration is greatly improved.
3. With an open-source application container engine, developers can package their applications and rely on packages into a portable container and then release onto any popular Linux machine. The containers are completely sandboxed, have no interfaces with each other and little performance overhead, can be easily run in machines and data centers, are independent of any language, framework or packaging system, are easy to backup and restore containers, and are beneficial to help restore containers and images.
4. According to the content disclosed by the disclosure, the backup from the system to the external equipment is realized through the mirror image operation of the container sandbox, and the mirror image backup operation is only needed to be carried out on the container sandbox, so that the accuracy and convenience of the backup are greatly improved.
5. According to the content disclosed by the disclosure, the mirror image pushed by the registry is dragged back and directly operated through the pull recovery container, so that the rapidness of system recovery is greatly improved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the disclosure, illustrate embodiments of the disclosure and together with the description serve to explain the disclosure and do not constitute an undue limitation on the disclosure.
FIG. 1 is a general architecture diagram of a container sandbox-based backup or restore system provided by the disclosed embodiments.
Fig. 2 is a schematic diagram of a startup flow of a container sandbox-based backup or restore system provided in the disclosed embodiments.
Fig. 3 is a flow chart of a system backup method based on a container sandbox provided in the disclosure embodiment 2.
Fig. 4 is a flow chart of a system recovery method based on a container sandbox provided in the disclosure embodiment 3.
Detailed Description
The disclosure is further described below with reference to the drawings and examples.
It should be noted that the following detailed description is illustrative and is intended to provide further explanation of the present disclosure. Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.
It is noted that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of exemplary embodiments in accordance with the present disclosure. As used herein, the singular is also intended to include the plural unless the context clearly indicates otherwise, and furthermore, it is to be understood that the terms "comprises" and/or "comprising" when used in this specification are taken to specify the presence of stated features, steps, operations, devices, components, and/or combinations thereof.
Embodiments of the present disclosure and features of embodiments may be combined with each other without conflict.
Example 1:
as shown in fig. 1, embodiment 1 of the present disclosure provides a backup system based on a container sandbox, where the entire system adopts a four-layer architecture: the system comprises a kernel driving layer, a customized desktop layer, a data storage layer and an application center layer.
The system is based on container layering initiation; the system is just a few packaged files (basic system files and kernel); after the system is started, a basic system file is loaded and used as a bottom container sandbox; the user's actions on the started system are not persisted, i.e., restored after a reboot.
The user may perform a persistence operation (using built-in commands) on the launched system, which automatically solidifies the user's modifications to create a new container. The next time the user starts, a new container layer of base files and user modifications will be started. The user may have a one-touch backup system and a one-touch restore system.
The kernel driving layer is mainly configured to drive hardware, except a CPU, a memory and a magnetic disk, and is mainly widely compatible with hardware devices such as different network cards, display cards, sound cards, peripherals and the like.
The customized desktop layer mainly aims at customizing xserver, customizing xfce desktop in a personalized mode and customizing GUI (Graphical User Interface ) of a user operating system.
The data storage layer is mainly used for dividing a storage area aiming at the protection of a system and comprises a read-only system area, a system personalized configuration persistent area and an application data storage area.
The read-only system area stores a basic operating system in the read-only system area, and ensures that the system can still robustly run the baseline mirror image when the system is subjected to non-physical damage.
The system personalized configuration persistent area stores information such as system password modification, default service configuration modification and the like which are specially customized and modified by a storage user aiming at the system, and the information is stored in the layer.
The application data storage area is a partition where the user-defined program is stored, for example, three-party applications are installed, etc. are stored.
The application center mainly provides operations such as software installation, uninstallation, upgrading and the like of the system, ensures that a user can safely and conveniently manage the software, and divides the application into: an optional system application, and a user-defined application.
The optional system application generally refers to an authorized activation application, a status collection application, and the like.
The optional system application generally refers to installing a reinforcement application, a serial port debug tool, a network analysis tool, and the like.
The user-defined application may be a traveling wave application, an electric energy quality application, a recorder application, a low current application, a message analysis application, etc. for the present company industry project.
With the system with the backup and restore method based on the container sandbox, the system is started based on the container layering, and the system is a plurality of packaged files (basic system files and kernels), as shown in fig. 2, is a system starting flow diagram based on the container sandbox.
As shown in fig. 2, the specific workflow is:
s1: after the system starts to start, the basic system file is first loaded as the underlying container sandbox.
S2: the user executes persistence operation on the started system by utilizing the built-in command, and the system automatically solidifies modification of the user to generate a layer of new container;
specifically, a persistence operation is performed on the started system, a user performs a series of modifications on the system, the user uses a persistence backup tool built in the system to perform a backup operation, the system packages the modification just before into a new modification layer according to the requirement of a command, the hierarchical relationship is recorded in the system, and the system is started according to the hierarchical relationship when the system is started next time.
S3: the user's operations on the started system will not be persisted, i.e., will be restored after a reboot, and the next time the user starts will start the base file and the new container layer that the user modified.
S4: a user can backup the system to a designated device by one key; once the system is restored due to a disaster (hardware failure or human error), the process of restoring the system from the designated device is completed by one key.
Example 2:
embodiment 2 of the present disclosure provides a system backup method based on a container sandbox, as shown in fig. 3.
Assuming that the system disk is the first SCSI disk, the device name is/dev/sda [1,2,3,4,5,6,7], the system also has a data SCSI disk, the device name is/dev/sdb 1, and the file system is ext3.
The user can one-touch back up the system to the designated device:
s41: starting the optical disk, and starting the optical disk to a Shell state according to a linux rescue mode;
s42: a data disk for backup is hung;
s43: a backup system;
s44: and (5) popping up the optical area and restarting the system.
In step S43, the method further comprises a backup container, and the container is backed up:
s431: first, to backup a container, a list of containers to be backed up may be first reviewed.
S432: after the container to be backed up is found, a snapshot of the container is created, and a snapshot of the container is generated as a mirror image, wherein the parameters include the ID of the container to be backed up and the new mirror name.
S433: the above snapshot has been saved as a mirror image. For backing up the snapshot, there are two options, one is to log in to the registry and push the mirror image to its own repositiories; another option is that the image may be packaged as a tar package backup to the local.
S434: the operation of selecting is to save the mirror image in the registry; a log command needs to be run to log into the registry and then push the required mirror.
S435: firstly, the user must log in the account, fill in the user name and password, and log in successfully.
S436: before uploading, adding tags to the mirror image; the tag parameter comprises a mirror name and a new tag name.
S437: after the tag is added, a save operation is executed, and the save operation is waited for.
Example 3:
the embodiment 3 of the disclosure provides a system recovery system based on a container sandbox, which comprises a memory, wherein the memory stores a backed-up container sandbox;
the container sandbox at least comprises a kernel driving layer, a customized desktop layer, a data storage layer and an application layer;
the kernel driving layer is configured to drive and be compatible with each hardware device, and the customized desktop layer is configured to customize a graphical user interface of an operating system; the data storage layer divides a storage area for the protection of an operating system and is configured to store different types of data; the application layer is configured to provide software management services of the system;
the system is started based on container sandboxes in a layered mode, and after the system is started, basic system files are loaded to serve as bottom container sandboxes; by executing persistence operation on the started system, the system automatically solidifies the modification command to generate a new container layer, and the base file and the modified new container layer are started when the system is started next time;
and directly restoring the container sandboxes stored in the backup storage to the preset positions.
The details are the same as those of embodiment 1, and will not be described again here.
Example 4:
embodiment 4 of the present disclosure provides a system recovery method based on a container sandbox, and the recovery system described in embodiment 3 is shown in fig. 4.
S5: once the system needs to be restored due to a disaster (hardware failure or human error), the process of restoring the system from the designated device by one key:
s51: restoring the hardware to a normal state (the swap of the swap);
s52: starting a CD to insert CD, and starting to a Shell state according to a linux rescue mode;
s53: a data disk for backup is hung;
s54: restoring the system;
s55: and (5) popping up the optical area and restarting the system.
Wherein step S54 further comprises a container recovery step of:
after a container is successfully backed up, the container can be restored by pull. If the images have been pushed at the registry, then that image is dragged back and run directly.
If the images are backed up locally as tar package files, the images can be loaded by adding the backup path of the tar package to the load command.
Ensuring that these image loads are successful, the loaded image is used to run the container.
The embodiment realizes a set of simple backup and recovery mechanism through the system. This mechanism allows a user to conveniently backup and restore the system. The system can automatically backup the system at regular intervals according to user setting, for example, the system recovery disk is made, and mirror image cloning of the system is realized; allowing the user to resume one-touch when an anomaly occurs.
The system and the method described in the embodiment realize a set of simple backup and recovery mechanism which allows a user to conveniently backup and recover the system; mirror image cloning of the slave system is realized, namely, a system is directly copied from the system to the U disk to be made into a system recovery disk; self-recovery at system crash (automatic backup at system regular, allowing user to select recovery at abnormal) is realized.
Example 5:
embodiment 5 of the present disclosure provides an electronic device, including the container sandbox-based backup system of embodiment 1 of the present disclosure and/or the restoration system of embodiment 3.
It will be apparent to those skilled in the art that embodiments of the present disclosure may be provided as a method, system, or computer program product. Accordingly, the present disclosure may take the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present disclosure may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, magnetic disk storage, optical storage, and the like) having computer-usable program code embodied therein.
The present disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the disclosure. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Those skilled in the art will appreciate that implementing all or part of the above-described methods in accordance with the embodiments may be accomplished by way of a computer program stored on a computer readable storage medium, which when executed may comprise the steps of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random access Memory (Random AccessMemory, RAM), or the like.
The foregoing is merely a preferred embodiment of the present disclosure and is not configured to limit the disclosure, and various modifications and changes may be made to the present disclosure by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present disclosure should be included in the protection scope of the present disclosure.
Claims (10)
1. The backup system based on the container sandbox is characterized by comprising a plurality of system working layers arranged in the container sandbox, wherein the system is started based on the container sandbox in a layered manner, and after the system is started, a basic system file is loaded as a bottom container sandbox; the working layer at least comprises a kernel driving layer, a customized desktop layer, a data storage layer and an application layer; the storage area of the data storage layer at least comprises a read-only system area, a system personalized configuration persistent area and an application data storage area; executing persistence operation on the started system, carrying out custom modification on the system, executing backup operation by adopting a persistence backup tool built in the system, packing the content of the custom modification into a new modification layer according to the requirement of a command, recording the hierarchical relationship in the system, and starting the system according to the new hierarchical relationship when the system is started next time;
by executing persistence operation on the started system, the system automatically solidifies and modifies the command to generate a new container layer, and the basic system file and the modified new container layer are started when the system is started next time; the new container layer is loaded on the previous layer, and the previous layer is loaded at the next starting time; the modified container layer can be a customized desktop layer or a data storage layer or an application center layer, and the kernel layer does not allow modification;
and the system backup is realized by integrally storing the container sandbox with the modified container layer into a storage module.
2. The container sandbox based backup system of claim 1, wherein the kernel driver layer is configured to drive and be compatible with individual hardware devices, the custom desktop layer being configured to make a custom of a graphical user interface of an operating system; the data storage layer divides a storage area for the protection of an operating system and is configured to store different types of data; the application layer is configured to provide software management services of the system.
3. The container sandbox based backup system of claim 1,
the read-only system region is configured to store base operating system storage such that the system can still robustly run a baseline image when subject to non-physical disruption; the system personalized configuration persistence configured to store specific custom modifications of a user to the system; the application data storage area is configured to store a user-defined program;
or alternatively, the process may be performed,
the application layer at least comprises a necessary system application, an optional system application and a user-defined application;
the necessary system application is an authorized activation application and a state acquisition application; the optional system application is an installation reinforcement application, a serial port debugging tool and a network analysis tool; the user-defined applications include, but are not limited to, traveling wave applications, power quality applications, recorder applications, low current applications, and message analysis applications.
4. A container sandbox based backup method comprising the container sandbox based backup system of any of claims 1-2, comprising the steps of: starting external equipment, and starting to a Shell state according to a linux rescue mode; a data disk for backup is hung; a backup system; disconnecting the external device.
5. The container sandbox-based backup method of claim 4, wherein the process of backing up the container sandbox comprises the following steps:
checking a container list to be backed up;
after finding the container to be backed up, creating a snapshot of the container, and generating a container snapshot serving as a mirror image, wherein the snapshot comprises the ID of the container to be backed up and a new mirror image name;
taking the obtained snapshot as a mirror image to be saved, and for backing up the snapshot, running a login command to log in a registration center and pushing the mirror image to a memory;
before uploading, firstly labeling the mirror image, wherein the parameters of the label comprise the mirror image name and a new label name;
after the labeling is finished, executing a saving operation;
or alternatively, the process may be performed,
the process of backing up the container sandbox comprises the following steps:
checking a container list to be backed up;
after finding the container to be backed up, creating a snapshot of the container, and generating a container snapshot serving as a mirror image, wherein the snapshot comprises the ID of the container to be backed up and a new mirror image name;
and storing the obtained snapshot as a mirror image, and for backing up the snapshot, packing the mirror image into a tar package to be backed up locally.
6. The recovery system based on the container sandboxes is characterized by comprising a memory, wherein the memory stores the backed-up container sandboxes, and the backed-up container sandboxes are directly recovered to a preset position;
the container sandbox comprises a plurality of system working layers, the system is started based on the container sandbox in a layered mode, and after the system is started, basic system files are loaded to serve as bottom container sandboxes; the working layer at least comprises a kernel driving layer, a customized desktop layer, a data storage layer and an application layer; the storage area of the data storage layer comprises a read-only system area, a system personalized configuration persistent area and an application data storage area; executing persistence operation on the started system, carrying out custom modification on the system, executing backup operation by adopting a persistence backup tool built in the system, packing the content of the custom modification into a new modification layer according to the requirement of a command, recording the hierarchical relationship in the system, and starting the system according to the new hierarchical relationship when the system is started next time;
by executing persistence operation on the started system, the system automatically solidifies the modification command to generate a new container layer, and the base file and the modified new container layer are started when the system is started next time; the new container layer is loaded on the previous layer, and the previous layer is loaded at the next starting time; the modified container layer may be a custom desktop layer or a data storage layer or an application center layer, and the kernel layer does not allow modification.
7. The container sandbox based recovery system of claim 6, wherein the kernel driver layer is configured to drive and be compatible with individual hardware devices, the custom desktop layer being configured to make a custom of the graphical user interface of the operating system; the data storage layer divides a storage area for the protection of an operating system and is configured to store different types of data; the application layer is configured to provide software management services of the system.
8. The container sandbox based restoration system as claimed in claim 7,
the read-only system region is configured to store base operating system storage such that the system can still run a baseline image when subject to non-physical disruption; the system personalized configuration persistence configured to store specific custom modifications of a user to the system; the application data store is configured to store a user-defined program.
9. A container sandbox-based restoration method comprising the container sandbox-based backup and restoration system of any of claims 6 to 7, comprising the steps of: restoring the hardware to a normal state; starting external equipment, and starting to a Shell state according to a linuxrecue mode; a data disk for backup is hung; restoring the system; disconnecting the external equipment;
the method comprises the following steps:
restoring the system to a specified position by using external equipment of a container sandbox carrying the system backup;
the method comprises a container sandbox recovery process, specifically, pulling back and directly operating the mirror image pushed by the registry through a pull recovery container; if the mirror image is backed up to the local as the tar package file, the mirror image is loaded from the local, and the container sandbox is operated after the success of loading the mirror image is confirmed.
10. An electronic device comprising the container sandbox-based backup system of any of claims 1 to 3 and/or the container sandbox-based restoration system of any of claims 6 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010554381.3A CN111708660B (en) | 2020-06-17 | 2020-06-17 | Backup system, recovery system and method based on container sandbox |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010554381.3A CN111708660B (en) | 2020-06-17 | 2020-06-17 | Backup system, recovery system and method based on container sandbox |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111708660A CN111708660A (en) | 2020-09-25 |
| CN111708660B true CN111708660B (en) | 2023-09-15 |
Family
ID=72540771
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010554381.3A Active CN111708660B (en) | 2020-06-17 | 2020-06-17 | Backup system, recovery system and method based on container sandbox |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111708660B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112241309B (en) * | 2020-10-21 | 2022-04-01 | 海光信息技术股份有限公司 | Data security method and device, CPU, chip and computer equipment |
| CN113688035B (en) * | 2021-08-06 | 2023-12-05 | 卢知白 | Database dual-activity center verification method and system based on sandbox environment |
| CN116028277B (en) * | 2023-03-27 | 2023-07-28 | 广州智算信息技术有限公司 | Database backup method and system based on CDC mode |
| CN116560801B (en) * | 2023-06-29 | 2023-09-22 | 中电长城(长沙)信息技术有限公司 | Cross-container counter system credit migration method and equipment |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102591982A (en) * | 2011-01-07 | 2012-07-18 | 赛门铁克公司 | Method and system of performing incremental sql server database backups |
| CN103778032A (en) * | 2014-01-26 | 2014-05-07 | 宝龙计算机系统（湖南）有限公司 | Unix-like operating system backup method and device |
-
2020
- 2020-06-17 CN CN202010554381.3A patent/CN111708660B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102591982A (en) * | 2011-01-07 | 2012-07-18 | 赛门铁克公司 | Method and system of performing incremental sql server database backups |
| CN103778032A (en) * | 2014-01-26 | 2014-05-07 | 宝龙计算机系统（湖南）有限公司 | Unix-like operating system backup method and device |
Non-Patent Citations (2)
| Title |
|---|
| "基于Android沙箱的软件动态行为检测系统的设计与实现";刘丽华;《中国优秀硕士学位论文全文数据库•信息科技辑》;第6-22页 * |
| 蔣迪."KVM是由云架构设计与实践".《KVM是由云架构设计与实践》.上海交通大学出版社,2017, * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111708660A (en) | 2020-09-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111708660B (en) | Backup system, recovery system and method based on container sandbox | |
| US11762740B2 (en) | Systems and methods for efficient backup restoration | |
| JP5367074B2 (en) | Virtual machine and application life cycle synchronization | |
| US7392374B2 (en) | Moving kernel configurations | |
| US10067835B2 (en) | System reset | |
| US8140905B2 (en) | Incremental problem determination and resolution in cloud environments | |
| KR101432463B1 (en) | Creating host-level application-consistent backups of virtual machines | |
| US8484431B1 (en) | Method and apparatus for synchronizing a physical machine with a virtual machine while the virtual machine is operational | |
| WO2021097397A1 (en) | Container-based application data protection method and system | |
| KR20110086732A (en) | Application restore points | |
| WO2015038481A1 (en) | Systems and methods for protecting virtual machine data | |
| CN103988181A (en) | Method and system for patching a virtual image | |
| US20160110210A1 (en) | Application migration in a process virtual machine environment | |
| KR20160059181A (en) | Apparatus and method for controlling updating software of AVN system in vehicle | |
| CN112068846B (en) | Application distribution method, device and medium based on dual systems | |
| CN112214323B (en) | Resource recovery method and device and computer readable storage medium | |
| Patrão | Virtual Machine Snapshots | |
| CN117492914A (en) | Virtual machine data disaster recovery backup method, device and medium | |
| CN117075937A (en) | Upgrade service recovery method and computing device | |
| CN116339788A (en) | System updating method, device, equipment and storage medium of big data platform | |
| CN117492920A (en) | Control method, device, equipment and medium of cloud platform | |
| JP2010225023A (en) | System environment change/restoration/correction history management method | |
| KR20120057738A (en) | method for automatically restoring system software of dedicated computer |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |