CN115048240B - Data processing method, system and medium based on Kubernetes - Google Patents
Data processing method, system and medium based on Kubernetes Download PDFInfo
- Publication number
- CN115048240B CN115048240B CN202210535155.XA CN202210535155A CN115048240B CN 115048240 B CN115048240 B CN 115048240B CN 202210535155 A CN202210535155 A CN 202210535155A CN 115048240 B CN115048240 B CN 115048240B
- Authority
- CN
- China
- Prior art keywords
- information
- backup
- kubernetes
- resource information
- resource
- 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
- 238000003672 processing method Methods 0.000 title claims abstract description 13
- 238000011084 recovery Methods 0.000 claims abstract description 38
- 238000000034 method Methods 0.000 claims description 32
- 238000003860 storage Methods 0.000 claims description 23
- 238000010367 cloning Methods 0.000 claims description 9
- 238000012163 sequencing technique Methods 0.000 claims description 7
- 238000004891 communication Methods 0.000 claims 1
- 230000002085 persistent effect Effects 0.000 abstract description 20
- 238000010586 diagram Methods 0.000 description 7
- 230000009286 beneficial effect Effects 0.000 description 6
- 238000004590 computer program Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 4
- 230000004044 response Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 125000004122 cyclic group Chemical group 0.000 description 1
- 230000007613 environmental effect Effects 0.000 description 1
- 230000002427 irreversible effect Effects 0.000 description 1
- 230000014759 maintenance of location Effects 0.000 description 1
- 230000002441 reversible effect Effects 0.000 description 1
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/1458—Management of the backup or restore process
- G06F11/1469—Backup restoration techniques
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)
- Retry When Errors Occur (AREA)
- Hardware Redundancy (AREA)
Abstract
The application discloses a data processing method, a system and a medium based on Kubernetes, comprising the following steps: acquiring a backup task created by a user; traversing all URLs in a Kubernetes API according to the backup task to obtain group information of resources corresponding to the backup task, determining list information according to the group information, and determining first resource information according to the list information; and storing the first resource information into an external memory. The embodiment of the application saves the persistent data through the external memory, reduces the possibility of loss of the persistent data and is convenient for the recovery of the persistent data in other clusters, and can be widely applied to the technical field of computers.
Description
Technical Field
The application relates to the technical field of computers, in particular to a data processing method, system and medium based on Kubernetes.
Background
The general kubernetes backup steps are: 1. backup metadata, 2, backup persistent data. The backed-up metadata can be backed up to a remote storage, while the persistent data is generally stored in a distributed storage, and in order to maintain consistency of the persistent data, snapshot processing needs to be performed on the underlying storage. The persistent data snapshot data is stored in the original distributed storage, and if irreversible errors occur in the distributed storage, the data of the application are likely to be permanently lost; at the same time, the application data in the snapshot cannot be restored to other clusters. The backup generally aims at a certain distributed storage snapshot, and different commands need to be called for snapshot for different storages, so that complexity is increased.
Disclosure of Invention
In view of the above, an object of the embodiments of the present application is to provide a data processing method, system and medium based on Kubernetes, which can save persistent data through an external memory, reduce the possibility of loss of the persistent data and facilitate recovery of the persistent data in other clusters.
In a first aspect, an embodiment of the present application provides a Kubernetes-based data processing method, including the following steps:
acquiring a backup task created by a user;
traversing all URLs in a Kubernetes API according to the backup task to obtain group information of resources corresponding to the backup task, determining list information according to the group information, and determining first resource information according to the list information;
and storing the first resource information into an external memory.
Optionally, the method further comprises:
acquiring a recovery task created by a user;
reading corresponding metadata backup information from the external memory according to the recovery task;
and carrying out resource sequencing on the metadata backup information, sending a resource creating request to the Kubernetes API according to the resource sequencing, and copying second resource information corresponding to the resource creating request from the external memory to the Kubernetes API.
Optionally, the backup task or the recovery task is acquired by:
receiving a backup task creating request or a recovery task creating request sent by a backup; and the backup task creating request or the recovery task creating request is determined by the backup according to the input request information of the user.
Optionally, the storing the first resource information specifically includes:
when the first resource information is of a PVC type, cloning a first PVC and starting a temporary pod for mounting the first PVC so as to store the first resource information of the PVC type;
otherwise, the resource information is copied for storage.
Optionally, the copying the second resource information corresponding to the resource request from the external memory to the Kubernetes API specifically includes:
when the second resource information is of a PVC type, starting a temporary pod for mounting and cloning a second PVC, and copying the second resource information from an external memory to the second PVC;
otherwise, the second resource information is copied to the Kubernetes API.
In a second aspect, an embodiment of the present application provides a Kubernetes-based data processing system, including:
the first module is used for acquiring a backup task created by a user;
the second module is used for traversing all URLs in the Kubernetes API according to the backup task to obtain group information of resources corresponding to the backup task, determining list information according to the group information, and determining first resource information according to the list information;
and the third module is used for storing the first resource information and storing the first resource information into an external memory.
In a third aspect, an embodiment of the present application provides a Kubernetes-based data processing system, including:
at least one processor;
at least one memory for storing at least one program;
the at least one program, when executed by the at least one processor, causes the at least one processor to implement the method described above.
In a fourth aspect, embodiments of the present application provide a storage medium having stored therein a processor-executable program for performing the above-described method when executed by a processor.
In a fifth aspect, an embodiment of the present application provides a Kubernetes-based data processing system, including Kubernetes and an external memory, where the Kubernetes includes a agent, and the Kubernetes and the external memory are all communicatively connected to the agent; wherein,,
the agent includes:
at least one processor;
at least one memory for storing at least one program;
the at least one program, when executed by the at least one processor, causes the at least one processor to implement the method as described above.
Optionally, the system further comprises a UI and a dackappd, wherein,
the UI is used for receiving input request information of a user and sending the input request information to the dackupd;
the dackeadded is configured to receive the input request information sent by the UI, generate a backup task creation request or a recovery task creation request according to the input request information, and send the backup task creation request or the recovery task creation request to the agent.
The embodiment of the application has the following beneficial effects: according to the embodiment, all URLs in the Kubernetes API are traversed according to the backup task created by the user to obtain group information, list information and first resource information of resources corresponding to the backup task, persistent data of the first resource information is stored in an external memory, the persistent data is stored through the external memory, the loss possibility of the persistent data is reduced, and recovery of the persistent data in other clusters is facilitated.
Drawings
FIG. 1 is a block diagram of a Kubernetes-based data processing system according to an embodiment of the present application;
fig. 2 is a schematic step flow diagram of a Kubernetes-based data processing method according to an embodiment of the present application;
FIG. 3 is a timing diagram of a data processing method based on Kubernetes according to an embodiment of the present application;
FIG. 4 is a schematic step flow diagram of another data processing method based on Kubernetes according to an embodiment of the present application;
FIG. 5 is a timing diagram of another data processing method based on Kubernetes according to an embodiment of the present application;
FIG. 6 is a block diagram of another Kubernetes-based data processing system provided by an embodiment of the present application;
FIG. 7 is a block diagram of another Kubernetes-based data processing system provided by an embodiment of the present application.
Detailed Description
The application will now be described in further detail with reference to the drawings and to specific examples. The step numbers in the following embodiments are set for convenience of illustration only, and the order between the steps is not limited in any way, and the execution order of the steps in the embodiments may be adaptively adjusted according to the understanding of those skilled in the art.
Referring to fig. 1, dbackup is an http service for interacting with a user, through which the user can initiate backup and restore; the agent is a service for actually executing backup or recovery and is deployed in kubernetes; the Kubernetes API is a Kubernetes system component, and the agent performs backup or recovery through an http interface; the relevant pod contains create, delete, attach or detach PVC (Persistent Volume Claim); app pod uses the created PVC; the external memory is used for providing a memory space.
As shown in fig. 2, the embodiment of the application provides a Kubernetes-based data processing method, which is applied to a agent and includes steps S100 to S300.
S100, acquiring a backup task created by a user.
It should be noted that, the method for acquiring the backup task created by the user is determined according to the actual application, and the embodiment is not particularly limited.
Optionally, the backup task is acquired by:
s110, receiving a backup task creation request sent by backup; and the backup task creating request is determined by the backup according to the input request information of the user.
And S200, traversing all URLs in the Kubernetes API according to the backup task to obtain group information of resources corresponding to the backup task, determining list information according to the group information, and determining first resource information according to the list information.
The group information, list information and specific resource information of the resources are sequentially and hierarchically traversed in a cyclic manner.
And S300, storing the first resource information and storing the first resource information into an external memory.
The first resource information is stored in the agent, and then the first resource information is stored in the external memory.
Optionally, the storing the first resource information specifically includes:
s310, when the first resource information is of a PVC type, cloning a first PVC and starting a temporary pod for mounting the first PVC so as to store the first resource information of the PVC type;
and S320, if not, copying the resource information to store.
Specifically, referring to fig. 3, kubernetes-based data backup includes three phases: creating a backup task, executing backup by the agent and restoring the environment. Creating a backup task stage: the user creates a backup task through the UI (the UI may be understood as a user input interface, such as a browser, etc.), the UI sends the create backup task to the backup, and the backup sends a create backup request to the agent according to the create backup task, and the agent feeds back a response request to the backup, and the backup feeds back a response request to the UI. The agent performs a backup phase: the agent traverses the api and the apis of the Kubernetes to obtain the group information returned by the Kubernetes; the agent traverses the acquired group information to acquire resource list information returned by the Kubernetes; the agent traverses the acquired resource list to acquire resource information returned by the Kubernetes; when the resource information is of a PVC type, cloning a request of the PVC to the Kubernetes, and storing the PVC to the agent; the agent sends a request to Kubernetes to initiate a temporary pod to mount the cloned PVC; the agent stores the resource information corresponding to the cloned PVC and the temporary pod of the PVC on which the clone is mounted in a storage (external memory). Environmental recovery: the agent makes a request to Kubernetes to delete cloned PVC and temporary pod.
It should be noted that, the backup is mainly interacted with http of the Kubernetes API through the agent to traverse all url, and the resource to be backed up is read according to the requirement; in the case where the resource being backed up is of the PVC type and is CSI (Container Storage Interface) based, cloning of the volume is performed. And restoring a new pod to mount the clone volume, scheduling the pod on the same physical machine as the agent pod (giving the agent sufficient authority), and copying the volume directory into a remote storage by the agent.
Referring to fig. 4, the Kubernetes-based data processing method further includes steps S400 to S600:
s400, acquiring a recovery task created by a user.
It should be noted that, the method for acquiring the recovery task created by the user is determined according to the actual application, and the embodiment is not particularly limited.
Optionally, the recovery task is obtained by:
s410, receiving a task creating and recovering request sent by backup; wherein the create recovery task request is determined by the backup according to user input request information.
S500, corresponding metadata backup information is read from the external memory according to the recovery task.
And S600, carrying out resource sequencing on the metadata backup information, sending a resource creating request to the Kubernetes API according to the resource sequencing, and copying second resource information corresponding to the resource creating request from the external memory to the Kubernetes API.
Optionally, the copying the second resource information corresponding to the resource request from the external memory to the Kubernetes API specifically includes:
s610, when the second resource information is of a PVC type, starting a temporary pod for mounting and cloning a second PVC, and copying the second resource information from an external memory to the second PVC;
and S620, if not, copying the second resource information to the Kubernetes API.
Specifically, referring to fig. 5, kubernetes-based data recovery includes three phases: the create recovery task and the agent perform recovery. Creating a recovery task stage: the user creates a recovery task through the UI (the UI can be understood as a user input interface such as a browser) and the UI sends the creation recovery task to the backup, and the backup creates a backup request according to the creation recovery task and sends the backup request to the agent, and the agent feeds back a response request to the backup and feeds back the response request to the UI. The agent performs a recovery phase: the agent sends a request to the storage to acquire backup information of metadata read according to the creation and recovery task, and after acquiring the metadata, the agent performs resource sequencing on the backup information of the metadata; the agent sends a request to Kubernetes to create resources in a certain order; when the resource is of the PVC type, the agent sends a request to the Kubernetes to start a temporary pod of the PVC on which the clone is mounted, and sends a request to the storage to copy the persistent volume of the resource information from the storage to the newly created PVC, and finally the temporary pod is deleted.
It should be noted that, the restoration is basically the reverse process of backup, and the restoration is performed according to the sequence of the resources, when the restored resources include PVC, the backup volume data at the storage end is restored to PVC after the restoration of the resources (temporary pod needs to be started).
The embodiment of the application has the following beneficial effects: according to the embodiment, all URLs in the Kubernetes API are traversed according to the backup task created by the user to obtain group information, list information and first resource information of resources corresponding to the backup task, persistent data of the first resource information is stored in an external memory, the persistent data is stored through the external memory, the loss possibility of the persistent data is reduced, and recovery of the persistent data in other clusters is facilitated.
Referring to fig. 6, an embodiment of the present application provides a Kubernetes-based data processing system, which is applied to a agent, and includes:
the first module is used for acquiring a backup task created by a user;
the second module is used for traversing all URLs in the Kubernetes API according to the backup task to obtain group information of resources corresponding to the backup task, determining list information according to the group information, and determining first resource information according to the list information;
and the third module is used for storing the first resource information and storing the first resource information into an external memory.
It should be noted that, the Kubernetes-based data processing system is applied to the agent, and further includes:
a fourth module, configured to obtain a recovery task created by a user;
a fifth module, configured to read corresponding metadata backup information from the external memory according to the recovery task;
and a sixth module, configured to perform resource ordering on the metadata backup information, send a resource creation request to the Kubernetes API according to the resource ordering, and copy second resource information corresponding to the resource creation request from the external memory to the Kubernetes API.
It can be seen that the content in the above method embodiment is applicable to the system embodiment, and the functions specifically implemented by the system embodiment are the same as those of the method embodiment, and the beneficial effects achieved by the method embodiment are the same as those achieved by the method embodiment.
Referring to fig. 7, an embodiment of the present application provides a Kubernetes-based data processing system, which is applied to a agent, and includes:
at least one processor;
at least one memory for storing at least one program;
the at least one program, when executed by the at least one processor, causes the at least one processor to implement the method described above.
It can be seen that the content in the above method embodiment is applicable to the system embodiment, and the functions specifically implemented by the system embodiment are the same as those of the method embodiment, and the beneficial effects achieved by the method embodiment are the same as those achieved by the method embodiment.
Furthermore, the embodiment of the application also discloses a computer program product or a computer program, and the computer program product or the computer program is stored in a computer readable storage medium. The computer program may be read from a computer readable storage medium by a processor of a computer device, the processor executing the computer program causing the computer device to perform the method as described above. Similarly, the content in the above method embodiment is applicable to the present storage medium embodiment, and the specific functions of the present storage medium embodiment are the same as those of the above method embodiment, and the achieved beneficial effects are the same as those of the above method embodiment.
Referring to fig. 1, an embodiment of the present application provides a data processing system based on Kubernetes, including Kubernetes and an external memory, where the Kubernetes includes a agent, and the Kubernetes and the external memory are all communicatively connected with the agent; wherein,,
the agent includes:
at least one processor;
at least one memory for storing at least one program;
the at least one program, when executed by the at least one processor, causes the at least one processor to implement the method as described above.
It can be seen that the content in the above method embodiment is applicable to the system embodiment, and the functions specifically implemented by the system embodiment are the same as those of the method embodiment, and the beneficial effects achieved by the method embodiment are the same as those achieved by the method embodiment.
Referring to fig. 1, optionally, the system further comprises a UI and a dackappd, wherein,
the UI is used for receiving input request information of a user and sending the input request information to the dackupd;
the dackeadded is configured to receive the input request information sent by the UI, generate a backup task creation request or a recovery task creation request according to the input request information, and send the backup task creation request or the recovery task creation request to the agent.
While the preferred embodiment of the present application has been described in detail, the application is not limited to the embodiment, and various equivalent modifications and substitutions can be made by those skilled in the art without departing from the spirit of the application, and these equivalent modifications and substitutions are intended to be included in the scope of the present application as defined in the appended claims.
Claims (9)
1. A Kubernetes-based data processing method, comprising:
acquiring a backup task created by a user;
traversing all URLs in a Kubernetes API according to the backup task to obtain group information of resources corresponding to the backup task, determining list information according to the group information, and determining first resource information according to the list information;
storing the first resource information and storing the first resource information into an external memory; the storing the first resource information specifically includes: when the first resource information is of a PVC type, cloning a first PVC, starting a temporary pod for mounting the first PVC, and storing the resource information corresponding to the clone volume of the first PVC and the temporary pod into an external memory; otherwise, the resource information is copied for storage.
2. The method according to claim 1, wherein the method further comprises:
acquiring a recovery task created by a user;
reading corresponding metadata backup information from the external memory according to the recovery task;
and carrying out resource sequencing on the metadata backup information, sending a resource creating request to the Kubernetes API according to the resource sequencing, and copying second resource information corresponding to the resource creating request from the external memory to the Kubernetes API.
3. Method according to any of claims 1 or 2, characterized in that the backup task or the restore task is obtained by:
receiving a backup task creating request or a recovery task creating request sent by a backup; and the backup task creating request or the recovery task creating request is determined by the backup according to the input request information of the user.
4. The method according to claim 2, wherein the copying the second resource information corresponding to the create resource request from the external memory to the Kubernetes API specifically includes:
when the second resource information is of a PVC type, starting a temporary pod for mounting and cloning a second PVC, and copying the second resource information from an external memory to the second PVC;
otherwise, the second resource information is copied to the Kubernetes API.
5. A Kubernetes-based data processing system, comprising:
the first module is used for acquiring a backup task created by a user;
the second module is used for traversing all URLs in the Kubernetes API according to the backup task to obtain group information of resources corresponding to the backup task, determining list information according to the group information, and determining first resource information according to the list information;
a third module, configured to store the first resource information, and store the first resource information to an external memory; the storing the first resource information specifically includes: when the first resource information is of a PVC type, cloning a first PVC, starting a temporary pod for mounting the first PVC, and storing the resource information corresponding to the clone volume of the first PVC and the temporary pod into an external memory; otherwise, copying the resource information for storage.
6. A Kubernetes-based data processing system, comprising:
at least one processor;
at least one memory for storing at least one program;
the at least one program, when executed by the at least one processor, causes the at least one processor to implement the method of any of claims 1-4.
7. A storage medium having stored therein a processor executable program, which when executed by a processor is adapted to carry out the method of any one of claims 1-4.
8. A data processing system based on Kubernetes, comprising Kubernetes and an external memory, wherein the Kubernetes comprise agents, and the Kubernetes and the external memory are both in communication connection with the agents; wherein,,
the agent includes:
at least one processor;
at least one memory for storing at least one program;
the at least one program, when executed by the at least one processor, causes the at least one processor to implement the method of any of claims 1-4.
9. The system of claim 8, further comprising a UI and a backup, wherein,
the UI is used for receiving input request information of a user and sending the input request information to the backup;
the backup is configured to receive the input request information sent by the UI, generate a backup task creation request or a recovery task creation request according to the input request information, and send the backup task creation request or the recovery task creation request to the agent.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210535155.XA CN115048240B (en) | 2022-05-17 | 2022-05-17 | Data processing method, system and medium based on Kubernetes |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210535155.XA CN115048240B (en) | 2022-05-17 | 2022-05-17 | Data processing method, system and medium based on Kubernetes |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115048240A CN115048240A (en) | 2022-09-13 |
| CN115048240B true CN115048240B (en) | 2023-08-29 |
Family
ID=83158667
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210535155.XA Active CN115048240B (en) | 2022-05-17 | 2022-05-17 | Data processing method, system and medium based on Kubernetes |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115048240B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117472573B (en) * | 2023-11-02 | 2024-05-24 | 广州鼎甲计算机科技有限公司 | Data processing method, device and computer equipment |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108958976A (en) * | 2018-07-02 | 2018-12-07 | 山东汇贸电子口岸有限公司 | A kind of PV snapshot restores distributed data base data method and system |
| CN111273871A (en) * | 2020-01-19 | 2020-06-12 | 星辰天合（北京）数据科技有限公司 | Method and device for dynamically allocating storage resources on container platform |
| CN112035062A (en) * | 2020-08-19 | 2020-12-04 | 星环信息科技（上海）有限公司 | Migration method of local storage of cloud computing, computer equipment and storage medium |
| CN113656149A (en) * | 2021-08-20 | 2021-11-16 | 深信服科技股份有限公司 | Application processing method and device and related equipment |
| CN114138549A (en) * | 2021-10-29 | 2022-03-04 | 苏州浪潮智能科技有限公司 | Data backup and recovery method based on kubernets system |
| CN114443356A (en) * | 2021-12-22 | 2022-05-06 | 航天信息股份有限公司 | Container cluster processing method and system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11455215B2 (en) * | 2018-04-30 | 2022-09-27 | Nutanix Inc. | Context-based disaster recovery |
-
2022
- 2022-05-17 CN CN202210535155.XA patent/CN115048240B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108958976A (en) * | 2018-07-02 | 2018-12-07 | 山东汇贸电子口岸有限公司 | A kind of PV snapshot restores distributed data base data method and system |
| CN111273871A (en) * | 2020-01-19 | 2020-06-12 | 星辰天合（北京）数据科技有限公司 | Method and device for dynamically allocating storage resources on container platform |
| CN112035062A (en) * | 2020-08-19 | 2020-12-04 | 星环信息科技（上海）有限公司 | Migration method of local storage of cloud computing, computer equipment and storage medium |
| CN113656149A (en) * | 2021-08-20 | 2021-11-16 | 深信服科技股份有限公司 | Application processing method and device and related equipment |
| CN114138549A (en) * | 2021-10-29 | 2022-03-04 | 苏州浪潮智能科技有限公司 | Data backup and recovery method based on kubernets system |
| CN114443356A (en) * | 2021-12-22 | 2022-05-06 | 航天信息股份有限公司 | Container cluster processing method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115048240A (en) | 2022-09-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109117425B (en) | Method, system, and medium for digital asset synchronization | |
| US10049018B2 (en) | Data backup using metadata mapping | |
| CN109634774B (en) | Data backup and recovery method and device | |
| US8924355B1 (en) | Checkpoint restart | |
| US8078580B2 (en) | Hybrid data archival method and system thereof | |
| US10929350B2 (en) | Enhanced techniques for copying cloud stored files | |
| EP3046026A1 (en) | Software upgrade method and system for mobile terminal | |
| US11237911B2 (en) | Object store for database backups | |
| WO2004100020A2 (en) | Flashback database | |
| CN104182294A (en) | Method and device for backing up and recovering file | |
| WO2013044794A1 (en) | Terminal backup and recovery method | |
| JP2008305404A (en) | System, method and program product for backing up data | |
| US8943026B2 (en) | Visual representation of a local backup | |
| CN115048240B (en) | Data processing method, system and medium based on Kubernetes | |
| US20110282843A1 (en) | Method and system for data backup and replication | |
| US9665594B2 (en) | Local backup | |
| CN112800019A (en) | Data backup method and system based on Hadoop distributed file system | |
| CN108572888B (en) | Disk snapshot creating method and disk snapshot creating device | |
| CN112130959A (en) | Virtual machine protection system and method | |
| US20100017863A1 (en) | Portable storage apparatus for providing working environment migration service and method thereof | |
| CN109558270B (en) | Data backup method and device and data restoration method and device | |
| CN116955006A (en) | Data backup method, export method, recovery method, device, equipment and medium | |
| CN108121514B (en) | Meta information updating method and device, computing equipment and computer storage medium | |
| CN102346696A (en) | Method and device for recovering files | |
| CN115586872A (en) | Container mirror image management method, device, equipment and storage medium |
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 |