CN110795389A - Storage snapshot based copying method, user equipment, storage medium and device - Google Patents
Storage snapshot based copying method, user equipment, storage medium and device Download PDFInfo
- Publication number
- CN110795389A CN110795389A CN201911034031.8A CN201911034031A CN110795389A CN 110795389 A CN110795389 A CN 110795389A CN 201911034031 A CN201911034031 A CN 201911034031A CN 110795389 A CN110795389 A CN 110795389A
- Authority
- CN
- China
- Prior art keywords
- file
- data
- snapshot
- request
- processed
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/11—File system administration, e.g. details of archiving or snapshots
- G06F16/128—Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion
-
- 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
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/11—File system administration, e.g. details of archiving or snapshots
- G06F16/119—Details of migration of file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/84—Using snapshots, i.e. a logical point-in-time copy of the data
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Quality & Reliability (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to the technical field of data processing, and discloses a copy method based on a storage snapshot, user equipment, a storage medium and a device. If a data copying request corresponding to a file to be processed is received, acquiring a first ROW snapshot associated with the file to be processed; creating a preset file node associated with the first ROW snapshot, and creating a link clone file associated with the preset file node; and if a data read-write request of the file to be processed or the link clone file is received, responding to the data read-write request, and simultaneously executing data migration operation corresponding to the data copy request. Obviously, by redesigning the data copy operation corresponding to the data copy request, the data read-write request can be responded without waiting for the end of the data migration operation, so that the waiting time for re-editing is greatly reduced, and the technical problem of long waiting time during file copying is solved.
Description
Technical Field
The present invention relates to the field of data processing technologies, and in particular, to a storage snapshot based copy method, a user equipment, a storage medium, and an apparatus.
Background
In a file copying scenario of a storage system, if a user wants to copy a certain file, the copied original file can be recorded as a file X, and a new file generated after copying is recorded as a file Y.
It is obvious that the user cannot use the original file or the new file in time, and needs to wait for a period of time.
Therefore, it is considered that there is a technical problem that the waiting time is long when the file is copied.
The above is only for the purpose of assisting understanding of the technical aspects of the present invention, and does not represent an admission that the above is prior art.
Disclosure of Invention
The invention mainly aims to provide a copying method, user equipment, a storage medium and a device based on a storage snapshot, and aims to solve the technical problem of long waiting time during file copying.
In order to achieve the above object, the present invention provides a storage snapshot based copy method, which includes the following steps:
if a data copy request corresponding to a file to be processed is received, acquiring a first write-time redirection ROW snapshot associated with the file to be processed;
creating a preset file node associated with the first ROW snapshot, and creating a link clone file associated with the preset file node, wherein the link clone file is a link clone file of the file to be processed;
and if a data read-write request for the file to be processed or the link clone file is received, responding to the data read-write request, and simultaneously executing data migration operation corresponding to the data copy request.
Preferably, before the step of obtaining the first re-write time ROW snapshot associated with the file to be processed if the data copy request corresponding to the file to be processed is received, the copy method based on the storage snapshot further includes:
acquiring a file to be processed;
and carrying out snapshot processing on the file to be processed based on an ROW technology so as to obtain a first ROW snapshot associated with the file to be processed.
Preferably, if a data read-write request for the file to be processed or the link clone file is received, responding to the data read-write request, and simultaneously executing a data migration operation corresponding to the data copy request, specifically including:
if a first data writing request corresponding to the file to be processed is received, determining first data to be written corresponding to the first data writing request, and simultaneously executing data migration operation corresponding to the data copying request;
and performing snapshot processing on the first ROW snapshot based on an ROW technology to obtain a second ROW snapshot associated with the first ROW snapshot, and writing the first data to be written into the second ROW snapshot.
Preferably, if a data read-write request for the file to be processed or the link clone file is received, responding to the data read-write request, and simultaneously executing a data migration operation corresponding to the data copy request, specifically including:
if a second data writing request corresponding to the link clone file is received, determining second data to be written corresponding to the second data writing request, and simultaneously executing data migration operation corresponding to the data copying request;
and performing snapshot processing on the chained clone file based on an ROW technology to obtain an ROW snapshot associated with the chained clone file, and writing the second data to be written into the ROW snapshot associated with the chained clone file.
Preferably, if a data read-write request for the file to be processed or the link clone file is received, responding to the data read-write request, and simultaneously executing a data migration operation corresponding to the data copy request, specifically including:
and if a data read-write request for the file to be processed or the link clone file is received, responding to the data read-write request, and asynchronously copying the first ROW snapshot and the file to be processed into the link clone file to obtain a target file.
Preferably, after receiving a data read-write request for the file to be processed or the chained clone file, responding to the data read-write request, and asynchronously copying the first ROW snapshot and the file to be processed to the chained clone file to obtain a target file, the storage snapshot based copy method further includes:
and if the ROW snapshot associated with the chained clone file exists, merging the ROW snapshot associated with the chained clone file into the target file, and deleting the ROW snapshot associated with the chained clone file.
Preferably, if a data read-write request for the file to be processed or the link clone file is received, responding to the data read-write request, and simultaneously executing a data migration operation corresponding to the data copy request, specifically including:
if a data reading request is received, backtracking the link clone file to determine the preset file node associated with the link clone file, and simultaneously executing data migration operation corresponding to the data copying request;
performing backtracking operation on the preset file node to determine the first ROW snapshot associated with the preset file node;
and if the data reading request points to the first ROW snapshot, reading data to be read from the first ROW snapshot.
In addition, to achieve the above object, the present invention further provides a user equipment, where the user equipment includes a memory, a processor, and a storage snapshot based copy program stored in the memory and executable on the processor, and the storage snapshot based copy program is configured to implement the steps of the storage snapshot based copy method as described above.
In addition, to achieve the above object, the present invention further provides a storage medium, on which a storage snapshot based copy program is stored, and the storage snapshot based copy program implements the steps of the storage snapshot based copy method as described above when executed by a processor.
In addition, in order to achieve the above object, the present invention further provides a storage snapshot based copy apparatus, including:
the system comprises a snapshot determining module, a first read-time Redirection (ROW) snapshot and a second ROW snapshot, wherein the snapshot determining module is used for acquiring a first ROW snapshot associated with a file to be processed if a data copy request corresponding to the file to be processed is received;
the link clone module is used for creating a preset file node associated with the first ROW snapshot and creating a link clone file associated with the preset file node, wherein the link clone file is a link clone file of the file to be processed;
and the data reading and writing module is used for responding to the data reading and writing request and simultaneously executing data migration operation corresponding to the data copying request if the data reading and writing request for the file to be processed or the link clone file is received.
If a data copying request corresponding to a file to be processed is received, acquiring a first ROW snapshot associated with the file to be processed; creating a preset file node associated with the first ROW snapshot, and creating a link clone file associated with the preset file node, wherein the link clone file is a link clone file of a file to be processed; and if a data read-write request of the file to be processed or the link clone file is received, responding to the data read-write request, and simultaneously executing data migration operation corresponding to the data copy request. Obviously, by redesigning the data copy operation corresponding to the data copy request, the data read-write request can be responded without waiting for the end of the data migration operation, so that the waiting time for re-editing is greatly reduced, and the technical problem of long waiting time during file copying is solved.
Drawings
FIG. 1 is a schematic diagram of a user equipment architecture of a hardware operating environment according to an embodiment of the present invention;
FIG. 2 is a flow chart of a storage snapshot based copy method according to the present invention;
FIG. 3 is a schematic flow chart of a storage snapshot based copy method according to the present invention;
FIG. 4 is a schematic diagram of a snapshot chain of a storage snapshot based copy method according to the present invention;
FIG. 5 is a schematic diagram of another process of the storage snapshot based copy method according to the present invention;
FIG. 6 is a schematic diagram of a copy flow of the storage snapshot based copy method according to the present invention;
fig. 7 is a block diagram of a copy apparatus based on storage snapshot according to the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Referring to fig. 1, fig. 1 is a schematic structural diagram of a user equipment in a hardware operating environment according to an embodiment of the present invention.
As shown in fig. 1, the user equipment may include: a processor 1001, such as a Central Processing Unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display screen (Display), the optional user interface 1003 may also include a standard wired interface and a wireless interface, and the wired interface of the user interface 1003 may be a Universal Serial Bus (USB) interface in the present invention. The network interface 1004 may optionally include a standard wired interface as well as a wireless interface (e.g., WI-FI interface). The Memory 1005 may be a high speed Random Access Memory (RAM); or a stable Memory, such as a Non-volatile Memory (Non-volatile Memory), and may be a disk Memory. The memory 1005 may alternatively be a storage device separate from the processor 1001.
Those skilled in the art will appreciate that the architecture shown in fig. 1 does not constitute a limitation of the user equipment and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
As shown in fig. 1, a memory 1005, which is a kind of computer storage medium, may include therein an operating system, a network communication module, a user interface module, and a storage snapshot based copy program.
In the user equipment shown in fig. 1, the network interface 1004 is mainly used for connecting to a backend server and performing data communication with the backend server; the user interface 1003 is mainly used for connecting peripheral equipment; the user equipment calls the copy program based on the storage snapshot stored in the memory 1005 through the processor 1001 and performs the following operations:
if a data copy request corresponding to a file to be processed is received, acquiring a first write-time redirection ROW snapshot associated with the file to be processed;
creating a preset file node associated with the first ROW snapshot, and creating a link clone file associated with the preset file node, wherein the link clone file is a link clone file of the file to be processed;
and if a data read-write request for the file to be processed or the link clone file is received, responding to the data read-write request, and simultaneously executing data migration operation corresponding to the data copy request.
Further, the processor 1001 may call the storage snapshot based copy program stored in the memory 1005, and further perform the following operations:
acquiring a file to be processed;
and carrying out snapshot processing on the file to be processed based on an ROW technology so as to obtain a first ROW snapshot associated with the file to be processed.
Further, the processor 1001 may call the storage snapshot based copy program stored in the memory 1005, and further perform the following operations:
if a first data writing request corresponding to the file to be processed is received, determining first data to be written corresponding to the first data writing request, and simultaneously executing data migration operation corresponding to the data copying request;
and performing snapshot processing on the first ROW snapshot based on an ROW technology to obtain a second ROW snapshot associated with the first ROW snapshot, and writing the first data to be written into the second ROW snapshot.
Further, the processor 1001 may call the storage snapshot based copy program stored in the memory 1005, and further perform the following operations:
if a second data writing request corresponding to the link clone file is received, determining second data to be written corresponding to the second data writing request, and simultaneously executing data migration operation corresponding to the data copying request;
and performing snapshot processing on the chained clone file based on an ROW technology to obtain an ROW snapshot associated with the chained clone file, and writing the second data to be written into the ROW snapshot associated with the chained clone file.
Further, the processor 1001 may call the storage snapshot based copy program stored in the memory 1005, and further perform the following operations:
and if a data read-write request for the file to be processed or the link clone file is received, responding to the data read-write request, and asynchronously copying the first ROW snapshot and the file to be processed into the link clone file to obtain a target file.
Further, the processor 1001 may call the storage snapshot based copy program stored in the memory 1005, and further perform the following operations:
and if the ROW snapshot associated with the chained clone file exists, merging the ROW snapshot associated with the chained clone file into the target file, and deleting the ROW snapshot associated with the chained clone file.
Further, the processor 1001 may call the storage snapshot based copy program stored in the memory 1005, and further perform the following operations:
if a data reading request is received, backtracking the link clone file to determine the preset file node associated with the link clone file, and simultaneously executing data migration operation corresponding to the data copying request;
performing backtracking operation on the preset file node to determine the first ROW snapshot associated with the preset file node;
and if the data reading request points to the first ROW snapshot, reading data to be read from the first ROW snapshot.
In the embodiment, if a data copy request corresponding to a file to be processed is received, a first ROW snapshot associated with the file to be processed is obtained; creating a preset file node associated with the first ROW snapshot, and creating a link clone file associated with the preset file node, wherein the link clone file is a link clone file of a file to be processed; and if a data read-write request of the file to be processed or the link clone file is received, responding to the data read-write request, and simultaneously executing data migration operation corresponding to the data copy request. Obviously, in the embodiment, by redesigning the data copy operation corresponding to the data copy request, the data read-write request can be responded without waiting for the end of the data migration operation, so that the waiting time for re-editing is greatly reduced, and the technical problem of long waiting time during file copy is solved.
Based on the above hardware structure, the embodiment of the copy method based on the storage snapshot is provided.
Referring to fig. 2, fig. 2 is a flow chart of the storage snapshot based copy method according to the present invention.
In this embodiment, the storage snapshot based copy method includes the following steps:
step S10: and if a data copy request corresponding to the file to be processed is received, acquiring a first re-oriented ROW snapshot associated with the file to be processed during writing.
In a specific implementation, the execution subject of this embodiment is a user device, and the user device may be a server or a server cluster. The user equipment is suitable for a distributed file storage system and can also be used for other types of storage systems.
It can be understood that, if a user wants to copy an original file, i.e., a file to be processed, or the system automatically copies the file to be processed, a data copy request corresponding to the file to be processed is triggered. The file to be processed may be denoted as file a, and the new file obtained after copying file a may be denoted as file B.
It should be appreciated that there is a long wait time since neither file a nor file B is generally available until the copying task begins but does not end, so that the user cannot use the original file or the new file in a timely manner. In order to shorten this waiting time, so that the user can quickly perform subsequent operations on the original file or the new file, for example, data can be read from or written to the original file or the new file, the embodiment will perform a copy operation by combining the snapshot and the linked clone.
Further, before obtaining a first Redirect-on-write (ROW) snapshot associated with the file to be processed if a data copy request corresponding to the file to be processed is received, the copy method based on the storage snapshot further includes:
acquiring a file to be processed;
and carrying out snapshot processing on the file to be processed based on an ROW technology so as to obtain a first ROW snapshot associated with the file to be processed.
In a specific implementation, a data update may be processed by using the ROW technology, for example, if there is a data update in the file a, the file a is not directly updated, a new snapshot is created by using the ROW technology and is recorded as a first ROW snapshot, and the update data at this time is written into the first ROW snapshot.
It can be understood that, in this embodiment, the data copy operation is redesigned, and if the data copy operation is to be performed on the file a, the actual data migration operation is not performed, but instead, the preset file node and the link clone file are created, for the user at the upper layer, the link clone file is the file B, and the user can directly operate the link clone file without waiting for the end of the data migration operation.
The data migration operation refers to an operation of copying data of the file a and obtaining the file B already provided with the data of the file a, and the link clone file in the embodiment does not have the data of the file a, so that the waiting time is reduced.
It can be seen that in this embodiment, the data copy operation is divided into two types of operations of asynchronous processing, where the first type of operation is to obtain a preset file node and a link clone file, and the second type of operation is to actually perform data migration operation to copy data, and the first type of operation is performed first, and then the second type of operation is performed. The user can re-edit the file without performing the second type of operation after performing the first type of operation.
Step S20: and creating a preset file node associated with the first ROW snapshot and creating a link clone file associated with the preset file node, wherein the link clone file is a link clone file of the file to be processed.
It will be appreciated that file a is associated with a first ROW snapshot, which in turn is associated with a preset file node, which in turn is associated with a linked clone file. For the upper layer user, the link clone file can be regarded as a new file obtained after the file a is copied, and the link clone file can be directly operated, but the link clone file does not actually contain the data of the file a.
The preset file node is used for recording file references, for example, "the first ROW snapshot is associated with the preset file node, and the preset file node is associated with the chained clone file" is recorded in the preset file node.
Step S30: and if a data read-write request for the file to be processed or the link clone file is received, responding to the data read-write request, and simultaneously executing data migration operation corresponding to the data copy request.
It should be understood that after obtaining the preset file node and the link clone file, the file a or the link clone file is already available, and may respond to a data read-write request of a user or a system for the file a or the link clone file, such as reading the file a or the link clone file. At this time, the data migration operation may not be ended, and therefore, the data migration operation may be performed at the same time.
Of course, if a data read-write request for the to-be-processed file or the link clone file is not received, the data migration operation corresponding to the data copy request is also executed.
In the embodiment, if a data copy request corresponding to a file to be processed is received, a first ROW snapshot associated with the file to be processed is obtained; creating a preset file node associated with the first ROW snapshot, and creating a link clone file associated with the preset file node, wherein the link clone file is a link clone file of a file to be processed; and if a data read-write request of the file to be processed or the link clone file is received, responding to the data read-write request, and simultaneously executing data migration operation corresponding to the data copy request. Obviously, in the embodiment, by redesigning the data copy operation corresponding to the data copy request, the data read-write request can be responded without waiting for the end of the data migration operation, so that the waiting time for re-editing is greatly reduced, and the technical problem of long waiting time during file copy is solved.
Referring to fig. 3, fig. 3 is a schematic flowchart of another embodiment of the storage snapshot based copy method according to the present invention, and based on the embodiment shown in fig. 2, another embodiment of the storage snapshot based copy method according to the present invention is provided.
In this embodiment, the step S30 specifically includes:
step S301: and if a first data writing request corresponding to the file to be processed is received, determining first data to be written corresponding to the first data writing request, and simultaneously executing data migration operation corresponding to the data copying request.
It can be understood that before the data migration operation is not completed, the present embodiment may respond to the data read/write request for the file a or the link clone file while performing the data migration operation corresponding to the data copy request, for example, if a first data write request for the file a is received, the data to be written, that is, the first data to be written, may be obtained first.
Step S302: and performing snapshot processing on the first ROW snapshot based on an ROW technology to obtain a second ROW snapshot associated with the first ROW snapshot, and writing the first data to be written into the second ROW snapshot.
It should be understood that, since the present embodiment uses the chained clone file to serve as the file B with the data of the file a, if the first data to be written is directly written in the first ROW snapshot, modifying the first ROW snapshot may destroy the trace-back operation based on the snapshot chain, and the chained clone file cannot be read and written again normally based on the interconnection relationship described by the snapshot chain. Therefore, referring to the snapshot chain diagram shown in fig. 4, in this embodiment, a second ROW snapshot associated with the first ROW snapshot is additionally generated, and a write operation is performed on the second ROW snapshot instead, so that damage to the original snapshot chain is avoided.
Further, if a data read-write request for the file to be processed or the link clone file is received, responding to the data read-write request, and simultaneously executing a data migration operation corresponding to the data copy request, specifically including:
if a second data writing request corresponding to the link clone file is received, determining second data to be written corresponding to the second data writing request, and simultaneously executing data migration operation corresponding to the data copying request;
and performing snapshot processing on the chained clone file based on an ROW technology to obtain an ROW snapshot associated with the chained clone file, and writing the second data to be written into the ROW snapshot associated with the chained clone file.
It can be understood that, similarly, before the data migration operation is not finished, the present embodiment may respond to the data read/write request for the link clone file while executing the data migration operation corresponding to the data copy request, for example, if a second data write request for the link clone file is received, the data to be written, that is, the second data to be written, may be acquired first.
It should be noted that, for the upper layer user, the link clone file operated at this time is regarded as the file B of the file a data that has been successfully copied by the user, but the copy has not been successfully copied in practice.
In a specific implementation, referring to the snapshot chain diagram shown in fig. 4, in this embodiment, an additional ROW snapshot associated with the chained clone file is generated, the ROW snapshot associated with the chained clone file may be recorded as a fourth ROW snapshot, and a write operation is performed on the fourth ROW snapshot.
Of course, a fifth ROW snapshot associated with the fourth ROW snapshot may also be created, and the fourth ROW snapshot is not written, but instead the fifth ROW snapshot is written.
In this embodiment, the data migration operation corresponding to the data copy request may still be executed before the data migration operation is not completed; moreover, regarding the first data write request for the file a, a second ROW snapshot associated with the first ROW snapshot is additionally generated, and the second ROW snapshot is not written into the file a or the first ROW snapshot but is written into the file a or the first ROW snapshot, so that the original snapshot chain is prevented from being damaged. After all, the first ROW snapshot is associated with the preset file node, the preset file node is associated with the chained clone file, and the like, and the change of the first ROW snapshot can result in that backtracking operation cannot be performed.
Referring to fig. 5, fig. 5 is a schematic flow chart of a copy method based on a storage snapshot according to another embodiment of the present invention, which is provided based on the embodiment shown in fig. 2.
In this embodiment, the embodiment shown in fig. 3 discusses that the data read/write request can be responded while the data migration operation corresponding to the data copy request is executed, but in addition, the data read/write request can be responded after the data migration operation is finished.
It can be understood that, for a data write request corresponding to a to-be-processed file, after receiving a data read/write request for the to-be-processed file or the chained clone file, responding to the data read/write request and simultaneously performing a data migration operation corresponding to the data copy request, the storage snapshot based copy method further includes:
if a third data writing request corresponding to the file to be processed is received, determining third data to be written corresponding to the third data writing request;
and performing snapshot processing on the first ROW snapshot based on an ROW technology to obtain a second ROW snapshot related to the first ROW snapshot, and writing the third data to be written into the second ROW snapshot.
It can be understood that, for a data write request corresponding to a link clone file, after receiving a data read/write request for the file to be processed or the link clone file, responding to the data read/write request and simultaneously performing a data migration operation corresponding to the data copy request, the storage snapshot based copy method further includes:
if a fourth data writing request corresponding to the link clone file is received, determining fourth data to be written corresponding to the fourth data writing request;
and performing snapshot processing on the chained clone file based on an ROW technology to obtain an ROW snapshot associated with the chained clone file, and writing the fourth to-be-written data into the ROW snapshot associated with the chained clone file.
It should be understood that, regarding the data write request corresponding to the pending file and the data write request corresponding to the linked clone file, the implementation flow may be according to the embodiment shown in fig. 3, except that the embodiment shown in fig. 3 simultaneously performs the data migration operation corresponding to the data copy request, and the embodiment is after the data migration operation is finished.
Further, the step S30 specifically includes:
step S303: and if a data read-write request for the file to be processed or the link clone file is received, responding to the data read-write request, and asynchronously copying the first ROW snapshot and the file to be processed into the link clone file to obtain a target file.
In a specific implementation, for performing a data migration operation corresponding to the data copy request, specifically, referring to the second stage from left to right in the copy flow diagram shown in fig. 6, the first ROW snapshot and the file a may be asynchronously copied to the clone-linked file, and the copied clone-linked file may be marked as a target file. The target file at this time is a new file obtained after the file a is copied, i.e., a file B. After the target file is obtained, the data migration operation is finished, and a Full clone (Full Clones) operation is realized.
It can be understood that it is characterized by performing a data migration operation corresponding to the data copy request, specifically, asynchronously copying the first ROW snapshot and the file to be processed into the chained clone file to obtain a target file.
Further, after the step S303, the storage snapshot based copy method further includes:
step S304: and if the ROW snapshot associated with the chained clone file exists, merging the ROW snapshot associated with the chained clone file into the target file, and deleting the ROW snapshot associated with the chained clone file.
In a specific implementation, in view of the fact that snapshots affect the running performance, the ROW snapshot associated with the chained clone file, i.e., the fourth ROW snapshot, may also be written into the target file, and the fourth ROW snapshot is deleted.
Further, after step S303, the storage snapshot based copy method further includes: and disconnecting the link between the file to be processed and the target file, and then executing the step S304.
It can be understood that, since the target file already contains the file data of the file to be processed, referring to the third stage from left to right in the copy flow diagram shown in fig. 6, i.e. the last stage, the link caused by the linked clone can be broken. The backtracking operation through the link is a great characteristic of link cloning, but the running performance is reduced due to a large amount of backtracking operations, the link is disconnected, the backtracking operation is avoided, and the performance can be improved.
Further, if a data read-write request for the file to be processed or the link clone file is received, responding to the data read-write request, and simultaneously executing a data migration operation corresponding to the data copy request, specifically including:
if a data reading request is received, backtracking the link clone file to determine the preset file node associated with the link clone file, and simultaneously executing data migration operation corresponding to the data copying request;
performing backtracking operation on the preset file node to determine the first ROW snapshot associated with the preset file node;
and if the data reading request points to the first ROW snapshot, reading data to be read from the first ROW snapshot.
It is understood that the data read/write request includes a data write request and a data read request, and if the data read request is received, the data read request is responded.
In particular implementations, with respect to the response process, backtracking may be based on a snapshot chain. For example, for a ROW snapshot, if there is no data to be acquired, the previous ROW snapshot of the ROW snapshot is traced back, and then whether there is data to be acquired in the previous ROW snapshot is determined until the original file is reached. For example, referring to fig. 4, a trace back operation is performed on the chained clone file, and then the chained clone file is traced back to the associated preset file node, and further traced back to the associated first ROW snapshot. If the data to be read is in the first ROW snapshot, reading the data to be read from the first ROW snapshot; if not, the associated file A is traced back, and if the data to be read is in the file A, the data to be read is read from the file A.
Further, it is discussed herein that the data read request may be responded to while the data migration operation corresponding to the data copy request is performed, but in addition to this, the data read request may also be responded to after the data migration operation is ended.
It can be understood that, for a data write request corresponding to a to-be-processed file, after receiving a data read/write request for the to-be-processed file or the chained clone file, responding to the data read/write request and simultaneously performing a data migration operation corresponding to the data copy request, the storage snapshot based copy method further includes:
if a data reading request is received, backtracking the link clone file to determine the preset file node associated with the link clone file;
performing backtracking operation on the preset file node to determine the first ROW snapshot associated with the preset file node;
and if the data reading request points to the first ROW snapshot, reading data to be read from the first ROW snapshot.
It should be noted that the backtracking operation may be performed until the link between the file to be processed and the target file is disconnected.
In the embodiment, the running performance can be improved by deleting the snapshot.
In addition, an embodiment of the present invention further provides a storage medium, where a storage snapshot based copy program is stored on the storage medium, and when executed by a processor, the storage snapshot based copy program implements the following operations:
if a data copy request corresponding to a file to be processed is received, acquiring a first write-time redirection ROW snapshot associated with the file to be processed;
creating a preset file node associated with the first ROW snapshot, and creating a link clone file associated with the preset file node, wherein the link clone file is a link clone file of the file to be processed;
and if a data read-write request for the file to be processed or the link clone file is received, responding to the data read-write request, and simultaneously executing data migration operation corresponding to the data copy request.
Further, when executed by the processor, the storage snapshot based copy program further implements the following operations:
acquiring a file to be processed;
and carrying out snapshot processing on the file to be processed based on an ROW technology so as to obtain a first ROW snapshot associated with the file to be processed.
Further, when executed by the processor, the storage snapshot based copy program further implements the following operations:
if a first data writing request corresponding to the file to be processed is received, determining first data to be written corresponding to the first data writing request, and simultaneously executing data migration operation corresponding to the data copying request;
and performing snapshot processing on the first ROW snapshot based on an ROW technology to obtain a second ROW snapshot associated with the first ROW snapshot, and writing the first data to be written into the second ROW snapshot.
Further, when executed by the processor, the storage snapshot based copy program further implements the following operations:
if a second data writing request corresponding to the link clone file is received, determining second data to be written corresponding to the second data writing request, and simultaneously executing data migration operation corresponding to the data copying request;
and performing snapshot processing on the chained clone file based on an ROW technology to obtain an ROW snapshot associated with the chained clone file, and writing the second data to be written into the ROW snapshot associated with the chained clone file.
Further, when executed by the processor, the storage snapshot based copy program further implements the following operations:
and if a data read-write request for the file to be processed or the link clone file is received, responding to the data read-write request, and asynchronously copying the first ROW snapshot and the file to be processed into the link clone file to obtain a target file.
Further, when executed by the processor, the storage snapshot based copy program further implements the following operations:
and if the ROW snapshot associated with the chained clone file exists, merging the ROW snapshot associated with the chained clone file into the target file, and deleting the ROW snapshot associated with the chained clone file.
Further, when executed by the processor, the storage snapshot based copy program further implements the following operations:
if a data reading request is received, backtracking the link clone file to determine the preset file node associated with the link clone file, and simultaneously executing data migration operation corresponding to the data copying request;
performing backtracking operation on the preset file node to determine the first ROW snapshot associated with the preset file node;
and if the data reading request points to the first ROW snapshot, reading data to be read from the first ROW snapshot.
In the embodiment, if a data copy request corresponding to a file to be processed is received, a first ROW snapshot associated with the file to be processed is obtained; creating a preset file node associated with the first ROW snapshot, and creating a link clone file associated with the preset file node, wherein the link clone file is a link clone file of a file to be processed; and if a data read-write request of the file to be processed or the link clone file is received, responding to the data read-write request, and simultaneously executing data migration operation corresponding to the data copy request. Obviously, in the embodiment, by redesigning the data copy operation corresponding to the data copy request, the data read-write request can be responded without waiting for the end of the data migration operation, so that the waiting time for re-editing is greatly reduced, and the technical problem of long waiting time during file copy is solved.
In addition, referring to fig. 7, an embodiment of the present invention further provides a storage snapshot based copy apparatus, where the storage snapshot based copy apparatus includes:
the snapshot determining module 10 is configured to, if a data copy request corresponding to a file to be processed is received, obtain a first write-time redirection ROW snapshot associated with the file to be processed.
It can be understood that, if a user wants to copy an original file, i.e., a file to be processed, or the system automatically copies the file to be processed, a data copy request corresponding to the file to be processed is triggered. The file to be processed may be denoted as file a, and the new file obtained after copying file a may be denoted as file B.
It should be appreciated that there is a long wait time since neither file a nor file B is generally available until the copying task begins but does not end, so that the user cannot use the original file or the new file in a timely manner. In order to shorten this waiting time, so that the user can quickly perform subsequent operations on the original file or the new file, for example, data can be read from or written to the original file or the new file, the embodiment will perform a copy operation by combining the snapshot and the linked clone.
Further, the storage snapshot based copying apparatus further includes:
the first snapshot generating module is used for acquiring a file to be processed; and carrying out snapshot processing on the file to be processed based on an ROW technology so as to obtain a first ROW snapshot associated with the file to be processed.
In a specific implementation, a data update may be processed by using the ROW technology, for example, if there is a data update in the file a, the file a is not directly updated, a new snapshot is created by using the ROW technology and is recorded as a first ROW snapshot, and the update data at this time is written into the first ROW snapshot.
It can be understood that, in this embodiment, the data copy operation is redesigned, and if the data copy operation is to be performed on the file a, the actual data migration operation is not performed, but instead, the preset file node and the link clone file are created, for the user at the upper layer, the link clone file is the file B, and the user can directly operate the link clone file without waiting for the end of the data migration operation.
The data migration operation refers to an operation of copying data of the file a and obtaining the file B already provided with the data of the file a, and the link clone file in the embodiment does not have the data of the file a, so that the waiting time is reduced.
It can be seen that in this embodiment, the data copy operation is divided into two types of operations of asynchronous processing, where the first type of operation is to obtain a preset file node and a link clone file, and the second type of operation is to actually perform data migration operation to copy data, and the first type of operation is performed first, and then the second type of operation is performed. The user can re-edit the file without performing the second type of operation after performing the first type of operation.
And the link clone module 20 is configured to create a preset file node associated with the first ROW snapshot, and create a link clone file associated with the preset file node, where the link clone file is a link clone file of the file to be processed.
It will be appreciated that file a is associated with a first ROW snapshot, which in turn is associated with a preset file node, which in turn is associated with a linked clone file. For the upper layer user, the link clone file can be regarded as a new file obtained after the file a is copied, and the link clone file can be directly operated, but the link clone file does not actually contain the data of the file a.
The preset file node is used for recording file references, for example, "the first ROW snapshot is associated with the preset file node, and the preset file node is associated with the chained clone file" is recorded in the preset file node.
And the data reading and writing module 30 is configured to respond to the data reading and writing request and execute a data migration operation corresponding to the data copy request at the same time if the data reading and writing request for the file to be processed or the link clone file is received.
It should be understood that after obtaining the preset file node and the link clone file, the file a or the link clone file is already available, and may respond to a data read-write request of a user or a system for the file a or the link clone file, such as reading the file a or the link clone file. At this time, the data migration operation may not be ended, and therefore, the data migration operation may be performed at the same time.
Of course, if a data read-write request for the to-be-processed file or the link clone file is not received, the data migration operation corresponding to the data copy request is also executed.
In the embodiment, if a data copy request corresponding to a file to be processed is received, a first ROW snapshot associated with the file to be processed is obtained; creating a preset file node associated with the first ROW snapshot, and creating a link clone file associated with the preset file node, wherein the link clone file is a link clone file of a file to be processed; and if a data read-write request of the file to be processed or the link clone file is received, responding to the data read-write request, and simultaneously executing data migration operation corresponding to the data copy request. Obviously, in the embodiment, by redesigning the data copy operation corresponding to the data copy request, the data read-write request can be responded without waiting for the end of the data migration operation, so that the waiting time for re-editing is greatly reduced, and the technical problem of long waiting time during file copy is solved.
In an embodiment, the data reading and writing module 30 is further configured to determine, if a first data writing request corresponding to the file to be processed is received, first data to be written corresponding to the first data writing request, and simultaneously perform a data migration operation corresponding to the data copying request; and performing snapshot processing on the first ROW snapshot based on an ROW technology to obtain a second ROW snapshot associated with the first ROW snapshot, and writing the first data to be written into the second ROW snapshot.
In an embodiment, the data reading and writing module 30 is further configured to determine, if a second data writing request corresponding to the link clone file is received, second data to be written corresponding to the second data writing request, and simultaneously execute a data migration operation corresponding to the data copy request; and performing snapshot processing on the chained clone file based on an ROW technology to obtain an ROW snapshot associated with the chained clone file, and writing the second data to be written into the ROW snapshot associated with the chained clone file.
In an embodiment, the data reading and writing module 30 is further configured to respond to a data reading and writing request for the to-be-processed file or the chained clone file if the data reading and writing request is received, and asynchronously copy the first ROW snapshot and the to-be-processed file to the chained clone file to obtain a target file.
In an embodiment, the storage snapshot based copy apparatus further includes:
and the link deletion module is used for merging the ROW snapshot associated with the link clone file into the target file and deleting the ROW snapshot associated with the link clone file if the ROW snapshot associated with the link clone file exists.
In an embodiment, the data reading and writing module 30 is further configured to, if a data reading request is received, perform a backtracking operation on the chained clone file to determine the preset file node associated with the chained clone file, and simultaneously perform a data migration operation corresponding to the data copy request;
performing backtracking operation on the preset file node to determine the first ROW snapshot associated with the preset file node;
and if the data reading request points to the first ROW snapshot, reading data to be read from the first ROW snapshot.
Other embodiments or specific implementation manners of the storage snapshot based copy apparatus according to the present invention may refer to the above method embodiments, and are not described herein again.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system 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 system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The use of the words first, second, third, etc. do not denote any order, but rather the words first, second, third, etc. are to be interpreted as names.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as a read-only memory, a RAM, a magnetic disk, and an optical disk), and includes instructions for enabling a terminal device (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. A storage snapshot based copy method is characterized in that the storage snapshot based copy method comprises the following steps:
if a data copy request corresponding to a file to be processed is received, acquiring a first write-time redirection ROW snapshot associated with the file to be processed;
creating a preset file node associated with the first ROW snapshot, and creating a link clone file associated with the preset file node, wherein the link clone file is a link clone file of the file to be processed;
and if a data read-write request for the file to be processed or the link clone file is received, responding to the data read-write request, and simultaneously executing data migration operation corresponding to the data copy request.
2. The storage snapshot based copy method according to claim 1, wherein before the step of obtaining the first write-time redirection ROW snapshot associated with the file to be processed if the data copy request corresponding to the file to be processed is received, the storage snapshot based copy method further comprises:
acquiring a file to be processed;
and carrying out snapshot processing on the file to be processed based on an ROW technology so as to obtain a first ROW snapshot associated with the file to be processed.
3. The storage snapshot based copy method according to claim 1 or 2, wherein if a data read/write request for the file to be processed or the link clone file is received, responding to the data read/write request, and executing a data migration operation corresponding to the data copy request at the same time specifically includes:
if a first data writing request corresponding to the file to be processed is received, determining first data to be written corresponding to the first data writing request, and simultaneously executing data migration operation corresponding to the data copying request;
and performing snapshot processing on the first ROW snapshot based on an ROW technology to obtain a second ROW snapshot associated with the first ROW snapshot, and writing the first data to be written into the second ROW snapshot.
4. The storage snapshot based copy method according to claim 1 or 2, wherein if a data read/write request for the file to be processed or the link clone file is received, responding to the data read/write request, and executing a data migration operation corresponding to the data copy request at the same time specifically includes:
if a second data writing request corresponding to the link clone file is received, determining second data to be written corresponding to the second data writing request, and simultaneously executing data migration operation corresponding to the data copying request;
and performing snapshot processing on the chained clone file based on an ROW technology to obtain an ROW snapshot associated with the chained clone file, and writing the second data to be written into the ROW snapshot associated with the chained clone file.
5. The storage snapshot based copy method according to claim 1 or 2, wherein if a data read/write request for the file to be processed or the link clone file is received, responding to the data read/write request, and executing a data migration operation corresponding to the data copy request at the same time specifically includes:
and if a data read-write request for the file to be processed or the link clone file is received, responding to the data read-write request, and asynchronously copying the first ROW snapshot and the file to be processed into the link clone file to obtain a target file.
6. The storage snapshot based copy method according to claim 5, wherein after receiving a data read/write request for the to-be-processed file or the chained clone file, responding to the data read/write request, and asynchronously copying the first ROW snapshot and the to-be-processed file to the chained clone file to obtain a target file, the storage snapshot based copy method further comprises:
and if the ROW snapshot associated with the chained clone file exists, merging the ROW snapshot associated with the chained clone file into the target file, and deleting the ROW snapshot associated with the chained clone file.
7. The storage snapshot based copy method according to claim 1 or 2, wherein if a data read/write request for the file to be processed or the link clone file is received, responding to the data read/write request, and executing a data migration operation corresponding to the data copy request at the same time specifically includes:
if a data reading request is received, backtracking the link clone file to determine the preset file node associated with the link clone file, and simultaneously executing data migration operation corresponding to the data copying request;
performing backtracking operation on the preset file node to determine the first ROW snapshot associated with the preset file node;
and if the data reading request points to the first ROW snapshot, reading data to be read from the first ROW snapshot.
8. A user equipment, the user equipment comprising: memory, a processor and a storage snapshot based copy program stored on the memory and executable on the processor, the storage snapshot based copy program when executed by the processor implementing the steps of the storage snapshot based copy method according to any one of claims 1 to 7.
9. A storage medium, characterized in that the storage medium has stored thereon a storage snapshot based copy program, which when executed by a processor implements the steps of the storage snapshot based copy method according to any one of claims 1 to 7.
10. A storage snapshot based copying apparatus, wherein the storage snapshot based copying apparatus comprises:
the system comprises a snapshot determining module, a first read-time Redirection (ROW) snapshot and a second ROW snapshot, wherein the snapshot determining module is used for acquiring a first ROW snapshot associated with a file to be processed if a data copy request corresponding to the file to be processed is received;
the link clone module is used for creating a preset file node associated with the first ROW snapshot and creating a link clone file associated with the preset file node, wherein the link clone file is a link clone file of the file to be processed;
and the data reading and writing module is used for responding to the data reading and writing request and simultaneously executing data migration operation corresponding to the data copying request if the data reading and writing request for the file to be processed or the link clone file is received.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911034031.8A CN110795389B (en) | 2019-10-28 | 2019-10-28 | Storage snapshot based copying method, user equipment, storage medium and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911034031.8A CN110795389B (en) | 2019-10-28 | 2019-10-28 | Storage snapshot based copying method, user equipment, storage medium and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110795389A true CN110795389A (en) | 2020-02-14 |
| CN110795389B CN110795389B (en) | 2022-09-30 |
Family
ID=69441667
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911034031.8A Active CN110795389B (en) | 2019-10-28 | 2019-10-28 | Storage snapshot based copying method, user equipment, storage medium and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110795389B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111737223A (en) * | 2020-06-28 | 2020-10-02 | 浪潮电子信息产业股份有限公司 | File copying method, device, equipment and storage medium |
Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101183383A (en) * | 2007-12-17 | 2008-05-21 | 中国科学院计算技术研究所 | Snapshot system and method of use thereof |
| US20080214309A1 (en) * | 2003-03-10 | 2008-09-04 | Cyberview Technology, Inc. | Dynamic configuration of a gaming system |
| CN101840362A (en) * | 2009-10-28 | 2010-09-22 | 创新科存储技术有限公司 | Method and device for achieving copy-on-write snapshot |
| CN102378969A (en) * | 2009-03-30 | 2012-03-14 | 惠普开发有限公司 | Deduplication of data stored in a copy volume |
| CN103617097A (en) * | 2013-11-19 | 2014-03-05 | 华为技术有限公司 | File recovery method and file recovery device |
| CN103645970A (en) * | 2013-12-13 | 2014-03-19 | 华为技术有限公司 | Realizing method and device for de-weighting increments among multiple snapshots for remote copy |
| CN103838647A (en) * | 2014-02-17 | 2014-06-04 | 中国科学院计算技术研究所 | Data state transition method and system based on snapshot remapping |
| CN104156367A (en) * | 2013-05-14 | 2014-11-19 | 阿里巴巴集团控股有限公司 | Search engine capacity expansion method and search service system |
| CN107015761A (en) * | 2015-10-12 | 2017-08-04 | 国际商业机器公司 | The time point cloned using chain is copied |
| CN107798130A (en) * | 2017-11-17 | 2018-03-13 | 广西广播电视信息网络股份有限公司 | A kind of Snapshot Method of distributed storage |
| CN107924293A (en) * | 2015-09-21 | 2018-04-17 | 国际商业机器公司 | Copy on write redirects |
| CN108376109A (en) * | 2017-01-31 | 2018-08-07 | 慧与发展有限责任合伙企业 | Volume and snapshot |
| CN109598156A (en) * | 2018-11-19 | 2019-04-09 | 杭州信核数据科技股份有限公司 | Engine snapshot stream method is redirected when one kind is write |
| CN109597707A (en) * | 2018-10-25 | 2019-04-09 | 平安科技（深圳）有限公司 | Clone volume data copying method, device and computer readable storage medium |
-
2019
- 2019-10-28 CN CN201911034031.8A patent/CN110795389B/en active Active
Patent Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080214309A1 (en) * | 2003-03-10 | 2008-09-04 | Cyberview Technology, Inc. | Dynamic configuration of a gaming system |
| CN101183383A (en) * | 2007-12-17 | 2008-05-21 | 中国科学院计算技术研究所 | Snapshot system and method of use thereof |
| CN102378969A (en) * | 2009-03-30 | 2012-03-14 | 惠普开发有限公司 | Deduplication of data stored in a copy volume |
| CN101840362A (en) * | 2009-10-28 | 2010-09-22 | 创新科存储技术有限公司 | Method and device for achieving copy-on-write snapshot |
| CN104156367A (en) * | 2013-05-14 | 2014-11-19 | 阿里巴巴集团控股有限公司 | Search engine capacity expansion method and search service system |
| CN103617097A (en) * | 2013-11-19 | 2014-03-05 | 华为技术有限公司 | File recovery method and file recovery device |
| CN103645970A (en) * | 2013-12-13 | 2014-03-19 | 华为技术有限公司 | Realizing method and device for de-weighting increments among multiple snapshots for remote copy |
| CN103838647A (en) * | 2014-02-17 | 2014-06-04 | 中国科学院计算技术研究所 | Data state transition method and system based on snapshot remapping |
| CN107924293A (en) * | 2015-09-21 | 2018-04-17 | 国际商业机器公司 | Copy on write redirects |
| CN107015761A (en) * | 2015-10-12 | 2017-08-04 | 国际商业机器公司 | The time point cloned using chain is copied |
| CN108376109A (en) * | 2017-01-31 | 2018-08-07 | 慧与发展有限责任合伙企业 | Volume and snapshot |
| CN107798130A (en) * | 2017-11-17 | 2018-03-13 | 广西广播电视信息网络股份有限公司 | A kind of Snapshot Method of distributed storage |
| CN109597707A (en) * | 2018-10-25 | 2019-04-09 | 平安科技（深圳）有限公司 | Clone volume data copying method, device and computer readable storage medium |
| CN109598156A (en) * | 2018-11-19 | 2019-04-09 | 杭州信核数据科技股份有限公司 | Engine snapshot stream method is redirected when one kind is write |
Non-Patent Citations (1)
| Title |
|---|
| 周煜: "一种基于过滤驱动的写时拷贝快照方法", 《四川大学学报（自然科学版）》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111737223A (en) * | 2020-06-28 | 2020-10-02 | 浪潮电子信息产业股份有限公司 | File copying method, device, equipment and storage medium |
| CN111737223B (en) * | 2020-06-28 | 2023-02-28 | 浪潮电子信息产业股份有限公司 | File copying method, device, equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110795389B (en) | 2022-09-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20150032690A1 (en) | Virtual synchronization with on-demand data delivery | |
| CN109359091B (en) | File management method, device, terminal and computer readable storage medium | |
| CN111414362B (en) | Data reading method, device, equipment and storage medium | |
| CN106547580B (en) | Method and device for hooking function, mobile terminal and storage medium | |
| CN110347341B (en) | Data clearing method and control equipment | |
| US11232066B2 (en) | Method for data migration and terminal | |
| CN105320578A (en) | Method and apparatus for backing up and recovering APP | |
| WO2017173922A1 (en) | Method and apparatus for upgrading virtual machine | |
| CN106484779B (en) | File operation method and device | |
| CN113282580A (en) | Method, storage medium and server for executing timed task | |
| CN110795389B (en) | Storage snapshot based copying method, user equipment, storage medium and device | |
| CN111090701B (en) | Service request processing method, device, readable storage medium and computer equipment | |
| CN106775445B (en) | Data migration method and device | |
| CN112433669A (en) | Method, system, equipment and medium for online migration of distributed storage volume | |
| CN105511904A (en) | Method and apparatus for automatically updating shortcut window | |
| CN114443216A (en) | Cloud platform mirror image management method and management system | |
| CN110221952B (en) | Service data processing method and device and service data processing system | |
| CN109347896B (en) | Information processing method, equipment and computer readable storage medium | |
| CN109446462B (en) | Page-based data monitoring processing method, device, equipment and storage medium | |
| CN114968297A (en) | OTA (over the air) upgrading method, electronic equipment and chip system | |
| CN112596954A (en) | Data backup and reconstruction method, device, equipment and storage medium | |
| CN112632032A (en) | Data migration method and device, storage medium and terminal equipment | |
| CN111625500A (en) | File snapshot method and device, electronic equipment and storage medium | |
| US7702890B2 (en) | Information processing apparatus and program | |
| CN112506592A (en) | Method, device, equipment and storage medium for determining page loading duration |
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 |