CN110515543A - Object bucket-based snapshot method, device and system - Google Patents
Object bucket-based snapshot method, device and system Download PDFInfo
- Publication number
- CN110515543A CN110515543A CN201910713323.8A CN201910713323A CN110515543A CN 110515543 A CN110515543 A CN 110515543A CN 201910713323 A CN201910713323 A CN 201910713323A CN 110515543 A CN110515543 A CN 110515543A
- Authority
- CN
- China
- Prior art keywords
- snapshot
- deleted
- metadata
- rollback
- sub
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0608—Saving storage space on storage systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0638—Organizing or formatting or addressing of data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
- G06F3/065—Replication mechanisms
Abstract
The invention discloses a snapshot method, a snapshot device and a snapshot system based on an object bucket. Wherein, the method comprises the following steps: after receiving an object to be written, determining a target snapshot, wherein the target snapshot is a snapshot generated at last; adding version information of the target snapshot to the object to obtain the object carrying the version information; writing an object carrying version information into an object storage system, and generating metadata of the object, wherein the metadata of the object indicates that the object data belongs to the target snapshot. The invention solves the technical problem that no high-performance snapshot scheme exists in the field of object storage in the prior art.
Description
Technical field
The present invention relates to field of data storage, in particular to a kind of Snapshot Method based on object bucket, device
And system.
Background technique
For snapshot for referring to a completely available copy about specified data acquisition system, which includes corresponding data at some
The image at time point (time point that copy starts).Fig. 1 a is the schematic diagram of snapping technique in the prior art, as shown in connection with fig. 1,
Direction along the time axis, brief snapshot operation may include: data write-in, creation snapshot T1, modification data, be rolled back to T1
Deng.
The implementation of snapshot mainly includes the following two kinds at present, and one is Copy on write, as COW (Copy On
Write), second is that writing redirection, as ROW (Redirect On Write).Fig. 1 b is the schematic diagram of COW, in conjunction with Fig. 1 b institute
Show, after creating snapshot, during write operation, if the data of source book are changed, fast photographic system can first will be original
(see the step 1) of Fig. 1 b, then source book is rewritten (see Fig. 1 b's again in corresponding data block in data copy to snapped volume
Step 2).In the operating process, one 2 times of write operation is at least caused to write amplification.During read operation, if necessary to read
Data in snapshot, then directly from snapshot read (see the step 3) of Fig. 1 b.Fig. 1 c is the schematic diagram that ROW reads data, figure
1d is the schematic diagram that ROW deletes data, and shown in set Fig. 1 c and 1d, in ROW model, delta file is written in snapshot
's.At the time of reading from snapshot reads incremental portion, unmodified part is read in source, it has been combined by the data segment (volume) in the two regions
Whole target data.
During the deletion of ROW model, due to containing increment information in snapshot, and the incremental data has uniquely
Property, therefore when deletion snapshot, it needs to carry out data backfill (as shown in Figure 1 d, the data B in snapshot is backfilled in source book), causes
Secondary write operation.
It can be seen that either Copy on write (COW) still writes redirection (ROW) and all there is respective disadvantage, but can not
It avoids being copied, if COW mode will carry out data copy when creating snapshot, ROW mode will carry out data when deleting and copy
Shellfish so that writing speed, reading speed or delete speed it is lower, therefore cause so that snapshot there are degraded performances.
Data Migration is all referred to for snapshot scheme in the prior art, so that writing speed, reading speed or deletion
Speed is lower, causes so that snapshot has degraded performance, currently no effective solution has been proposed.
Summary of the invention
The embodiment of the invention provides a kind of Snapshot Methods based on object bucket, device and system, at least to solve
The technical issues of object field of storage in the prior art is without high-performance snapshot scheme.
According to an aspect of an embodiment of the present invention, a kind of Snapshot Method based on object bucket, snapshot packet are provided
It includes: metadata and object data, wherein metadata is used to record the linking relationship between snapshot, and linking relationship includes sub- snapshot
To the dependence of father's snapshot, object data is for recording the object for belonging to snapshot, the Snapshot Method packet based on object bucket
It includes: after receiving object to be written, determining target snapshot, wherein target snapshot is the snapshot ultimately produced；For object addition
The version information of target snapshot obtains the object for carrying version information；The object for carrying version information write-in object is deposited
Storage system, and generate the metadata of object, wherein the metadata instruction object data of object belongs to target snapshot.
Further, if the corresponding object data of object is not present in target snapshot, version information will directly be carried
Object object storage system is written, and generate the metadata of object；If the corresponding object of existing object in target snapshot
Data replace already present object in object storage system using the object for carrying version information, and generate first number of object
According to.
Further, the above method further include: receive first and delete instruction, and deleted according to first and instruct determination to be deleted
Snapshot, wherein first delete instruction in include snapshot to be deleted identification information；Judge snapshot to be deleted whether by other
Snapshot reference；If snapshot to be deleted is quoted by other snapshots, the metadata of snapshot to be deleted is deleted, is retained to be deleted fast
According to object data；It is to delete by the metadata token of snapshot to be deleted if snapshot to be deleted is quoted by other snapshots.
Further, if snapshot to be deleted is quoted by other snapshots, by the metadata token of snapshot to be deleted
After deleting, father's snapshot of the sub- snapshot of snapshot to be deleted is changed to father's snapshot of snapshot to be deleted.
Further, the above method further include: receive second deleting instruction, wherein second deleting instruction belongs to for deleting
In the object to be deleted of any snapshot；Judge former snapshot belonging to object to be deleted whether cited in other snapshots；If former
Snapshot adds former snapshot cited in other snapshots, then in the invisible list object of object to be deleted；If former snapshot is not
Cited in other snapshots, then the object data of object to be deleted in former snapshot is deleted.
Further, the above method further include: receive rollback instruction, wherein rollback instruction include to rollback purpose it is fast
According to mark；Creation rollback snapshot is instructed according to rollback, and determines that rollback snapshot is the sub- snapshot of purpose snapshot.
Further, new snapshot is being created according to rollback instruction, and is determining that the new snapshot of creation is purpose snapshot
After sub- snapshot, receives the creation for creating snapshot and instruct；Whether there is object in detection rollback snapshot；If in rollback snapshot
Without object, then rollback snapshot is deleted, and is that father's snapshot creates sub- snapshot with the non-rollback snapshot being newly created；If rollback snapshot
In have object, then be that father's snapshot creates sub- snapshot with rollback snapshot.
Further, the above method further include: detect the creation time with two sub- snapshots of identical father's snapshot；If
The creation time of two sub- snapshots is less than preset time threshold, then merges to two sub- snapshots, and by two fast sighting targets of son
It is denoted as deletion, wherein disconnect the linking relationship of wherein any one sub- snapshot and father's snapshot, and will be switched off linking with father's snapshot
The sub- snapshot of relationship is connected to another sub- snapshot
According to an aspect of an embodiment of the present invention, a kind of fast photographing device based on object bucket, snapshot packet are provided
It includes: metadata and object data, wherein metadata is used to record the linking relationship between snapshot, and linking relationship includes sub- snapshot
To the dependence of father's snapshot, object data is for recording the object for belonging to snapshot, the fast photographing device packet based on object bucket
Include: determining module, for determining target snapshot after receiving object to be written, wherein target snapshot be ultimately produce it is fast
According to；Adding module obtains the object for carrying version information for adding the version information of target snapshot for object；Mould is written
Block, object storage system is written in the object for that will carry version information, and generates the metadata of object, wherein object
Metadata instruction object data belongs to target snapshot.
According to an aspect of an embodiment of the present invention, a kind of fast photographic system based on object bucket, system packet are provided
The object storage system and at least one snapshot for storage object are included, at least one snapshot includes: metadata, fast for recording
Linking relationship according between, linking relationship include dependence of the sub- snapshot to father's snapshot；Object data belongs to fastly for recording
According to object.
Further, above-mentioned metadata includes: the mark of father's snapshot identification, sub- snapshot identification and deleted father's snapshot.
According to an aspect of an embodiment of the present invention, a kind of storage medium is provided, storage medium includes the program of storage,
Wherein, when program is run, equipment where control storage medium executes the above-mentioned Snapshot Method based on object bucket.
According to an aspect of an embodiment of the present invention, a kind of processor is provided, processor is for running program, wherein
The perform claim above-mentioned Snapshot Method based on object bucket when program is run.
The embodiment of the present invention increases version information on the basis of ROW, to the object name of upload objects all under snapshot, comes
Progress object data is associated with snapshot, so that operation all after creation snapshot can carry version information at one
Object on carry out.That is, all data are all independent portions under each snapshot, all associations to the snapshot version
This.Above scheme also increases SNAPSHOT INFO the data structure of father's snapshot and sub- snapshot, so that reading some snapshot letter
When breath, splicing threading is carried out according to the linking relationship between snapshot, can therefrom extract each newest object in link, is realized
In the zero-copy bucket snapshot of object field of storage.By the ability, so that the space utilization of system maximizes, without any true
Real data copy, same data can only store portion, and data never need to migrate back and forth, and then solve the prior art
In object field of storage without high-performance snapshot scheme the technical issues of.
Detailed description of the invention
The drawings described herein are used to provide a further understanding of the present invention, constitutes part of this application, this hair
Bright illustrative embodiments and their description are used to explain the present invention, and are not constituted improper limitations of the present invention.In the accompanying drawings:
Fig. 1 a is the schematic diagram of snapping technique in the prior art；
Fig. 1 b is the schematic diagram of COW；
Fig. 1 c is the schematic diagram that ROW reads data；
Fig. 1 d is the schematic diagram that ROW deletes data；
Fig. 2 is a kind of flow chart of Snapshot Method based on object bucket according to an embodiment of the present invention；
Fig. 3 is a kind of schematic diagram of storage organization according to an embodiment of the present invention；
Fig. 4 is a kind of schematic diagram for deleting snapshot according to an embodiment of the present invention；
Fig. 5 is a kind of schematic diagram for deleting object according to an embodiment of the present invention；
Fig. 6 is that seed snapshot according to an embodiment of the present invention counts the schematic diagram being not zero；
Fig. 7 is a kind of schematic diagram of the visibility status of object OBJ according to an embodiment of the present invention；
Fig. 8 is a kind of schematic diagram of tree-shaped relationship according to an embodiment of the present invention；
Fig. 9 is the schematic diagram of a kind of creation snapshot according to an embodiment of the present invention and upload object；
Figure 10 is the schematic diagram that T2 is rolled back on the basis of Fig. 9；
Figure 11 is the schematic diagram of the upload object data in rollback snapshot；
Figure 12 is a kind of schematic diagram that snapshot is created after rollback snapshot according to an embodiment of the present invention；
Figure 13 is another schematic diagram that snapshot is created after rollback snapshot according to an embodiment of the present invention；
Figure 14 is the schematic diagram of the first list object according to embodiments of the present invention；
Figure 15 is the schematic diagram of the first fast photographing device based on object bucket according to embodiments of the present invention.
In the following, in order to make it easy to understand, carrying out description below explanation to the technical term that the application occurs:
Store snapshot: about a completely available copy of specified data set sum, which includes corresponding data at some
The image at time point (time point that copy starts).Snapshot can be a copy of the data represented by it, be also possible to count
According to a duplicate.
Bucket snapshot: Bucket Snapshot, the purpose of bucket be in object storage system object carry out logic every
From, bucket snapshot is a completely available copy for total data and index set generation to the target bucket a certain moment,
It can restore the ability of the target bucket time point of creation (snapshot) corresponding total data at some time point by the copy.
Snapshot bucket: Snapshot Bucket enables the object bucket (container) of bucket snapshot functions.
Snapshot rollback: Snapshot Rollback, snapshot rollback, which is commonly applied to data exception, faulty operation and business, to be needed
The scene for needing data-backoff such as seek.Whole metadata and object data after rollback will be updated to the shape of snapshot creation time point
The purpose of state, behaviour group is to provide the ability of data backtracking.Any upload, deletion can be implemented to any object in this state
Deng operation and new snapshot can be created save current state and be rolled back to any snapshot version herein.
It is visual: Visual, to any object created under snapshot bucket, with whether visually come characterize the object can be at certain
It is shown under one snapshot.Visibility status characterization object whether there is under some snapshot state and how exist.
Object version: Object Version distinguishes in difference the object uploaded into bucket with different versions
Period creation/update object of the same name.The upload of object can get pair of a matching snapshot version under each snapshot
As version.Object version is distinguished by prefix/infix/suffix.In the case where not creating new snapshot, object updates operation and contains use
There is the new object of same version identifier to be updated rather than generates the object of a new version.In other words, under each snapshot
Whole objects can all have an exclusive version, such as T1_ object A, T2_ object A, T3_ object A.
Read-only materialized view: read-only Snapshot, logic are return back under a certain target snapshot version.Under the state, under
Carry object obtain by be target snapshot version contents of object.
Bucket snapshot list object: it is clear to obtain object visual under target snapshot by Bucket Snapshot Object List
It is single.
Specific embodiment
In order to enable those skilled in the art to better understand the solution of the present invention, below in conjunction in the embodiment of the present invention
Attached drawing, technical scheme in the embodiment of the invention is clearly and completely described, it is clear that described embodiment is only
The embodiment of a part of the invention, instead of all the embodiments.Based on the embodiments of the present invention, ordinary skill people
The model that the present invention protects all should belong in member's every other embodiment obtained without making creative work
It encloses.
It should be noted that description and claims of this specification and term " first " in above-mentioned attached drawing, "
Two " etc. be to be used to distinguish similar objects, without being used to describe a particular order or precedence order.It should be understood that using in this way
Data be interchangeable under appropriate circumstances, so as to the embodiment of the present invention described herein can in addition to illustrating herein or
Sequence other than those of description is implemented.In addition, term " includes " and " having " and their any deformation, it is intended that cover
Cover it is non-exclusive include, for example, the process, method, system, product or equipment for containing a series of steps or units are not necessarily limited to
Step or unit those of is clearly listed, but may include be not clearly listed or for these process, methods, product
Or other step or units that equipment is intrinsic.
Embodiment 1
According to embodiments of the present invention, a kind of embodiment of Snapshot Method based on object bucket is provided, needs to illustrate
, step shown in the flowchart of the accompanying drawings can hold in a computer system such as a set of computer executable instructions
Row, although also, logical order is shown in flow charts, and it in some cases, can be to be different from sequence herein
Execute shown or described step.
Fig. 2 is a kind of flow chart of Snapshot Method based on object bucket according to an embodiment of the present invention, the snapshot
It include: metadata and object data, wherein metadata is used to record the linking relationship between snapshot, and linking relationship includes that son is fast
According to the dependence to father's snapshot, object data is for recording the object for belonging to snapshot, as shown in Fig. 2, this method includes as follows
Step:
Step S202 determines target snapshot after receiving object to be written, wherein each snapshot is fast as upper one
According to sub- snapshot creation, target snapshot is the snapshot ultimately produced.
The above-mentioned storage organization of the application is illustrated first.In the storage organization of the application, snapshot is that bucket is fast
According to snapshot constitutes the chain structure with set membership according to the time of generation.Fig. 3 is one kind according to an embodiment of the present invention
The schematic diagram of storage organization, as shown in connection with fig. 3, T1, T2, T3, T4 are sequentially generated according to the time, therefore the chain relation of its composition
For T1-- > T2-- > T3-- > T4.It further include the metadata having for recording linking relationship in snapshot other than object data,
As shown in connection with fig. 3, which can exist in the form of pointer, including following information: father's snapshot, sub- snapshot and delete
Attachment snapshot.Since complete snapshot is spliced by the pointer of metadata, each snapshot only saves the portion changed under snapshot
Point, to realize the low redundancy of metadata.
A upper snapshot for each snapshot is the snapshot generated before each snapshot, as shown in connection with fig. 3, upper one of T2
Snapshot is T1, and a upper snapshot of T3 is T2, and so on.
In above-mentioned storage organization, after receiving object to be written, determine that the snapshot ultimately produced is target snapshot,
As shown in figure 3, current target snapshot is snapshot T5, if snapshot T4 is target snapshot before snapshot T5 generation.
Step S104 adds the version information of target snapshot for object, obtains the object for carrying version information.
Specifically, the version information of above-mentioned target snapshot can be the snapshot identification of target snapshot.Still with shown in Fig. 3,
" T1 ", " T2 ", " T3 ", " T4 " are the mark of snapshot.
Version information is added for object, nominally addition prefix, suffix or the infix in object is can be, is also possible to
In the case where not changing object oriented, attribute information is added for object, which is the version for being used to indicate target snapshot
Information.
It in an alternative embodiment,, can be right at this in snapshot T1 when upload object OBJ still with shown in Fig. 3
As upper addition prefix T1, object T1-OBJ is obtained.Likewise, adding prefix on object when object OBJ is uploaded to snapshot T2
T2 obtains object T2-OBJ；When object OBJ is uploaded to snapshot T3, prefix T3 is added on object, obtains object T3-OBJ.
Above-mentioned T1, T2 and T3 are version information, and T1-OBJ, T2-OBJ and T3-OBJ are the object for carrying version information.
The object for carrying version information is written object storage system, and generates first number of the object by step S106
According to, wherein the metadata of the object indicates that the object data belongs to the target snapshot.
Still in the embodiment of above-mentioned Fig. 3, in snapshot T1 when upload object OBJ, prefix can be added on the object
T1 obtains object T1-OBJ, then object T1-OBJ is uploaded to object storage system, and generate the metadata of T1-OBJ, T1-
The metadata of OBJ is used to indicate T1-OBJ and belongs to snapshot T1.Likewise, adding on object when object OBJ is uploaded to snapshot T2
Prefixing T2 obtains object T2-OBJ, then object T2-OBJ is uploaded to object storage system, and generates first number of T2-OBJ
According to the metadata of T2-OBJ is used to indicate T2-OBJ and belongs to snapshot T2；When object OBJ is uploaded to snapshot T3, add on object
Prefixing T3 obtains object T3-OBJ, then object T3-OBJ is uploaded to object storage system, and generates first number of T3-OBJ
According to the metadata of T3-OBJ is used to indicate T3-OBJ and belongs to snapshot T3.Above-mentioned T1, T2 and T3 are version information, T1-OBJ,
T2-OBJ and T3-OBJ is the object for carrying version information.
Above-mentioned in snapshot by way of upload object, so that each object can only generate a version under each snapshot
This, what is stored in the last one snapshot is the latest edition of object, and under multiple snapshots, the same object may generate more
The data of a version.It, only need to be according to the linking relationship between snapshot from backward in reading object under such storage organization
Preceding lookup.It does not wherein include object OBJ in T4 for example, searching object OBJ in linking relationship T1-- > T2-- > T3-- > T4, because
This is searched in father's snapshot T3 from T4, include T3-OBJ in T3, therefore, T3-OBJ is obtained from T3 can be obtained and require to look up
Data.
The above embodiments of the present application increase version letter on the basis of ROW, to the object name of upload objects all under snapshot
Breath, Lai Jinhang object data are associated with snapshot, so that operation all after creation snapshot can carry version at one
It is carried out on the object of this information.That is, all data are all independent portions under each snapshot, all associations extremely should
Snapshot version.Above scheme also increases SNAPSHOT INFO the data structure of father's snapshot and sub- snapshot, so that reading some
When SNAPSHOT INFO, splicing threading is carried out according to the linking relationship between snapshot, it is each newest right in link therefrom to extract
As realizing the zero-copy bucket snapshot in object field of storage.By the ability, so that the space utilization of system maximizes,
No any truthful data copy, same data can only store portion, and data never need to migrate back and forth, and then solve
The technical issues of object field of storage in the prior art is without high-performance snapshot scheme.
As a kind of optional embodiment, object storage system is written into the object for carrying the version information, and raw
At the metadata of the object, comprising: if the corresponding object data of the object is not present in the target snapshot, directly will
The object write-in object storage system of version information is carried, and generates the metadata of the object；If the target snapshot
In the corresponding object data of the existing object, use the object for carrying the version information to replace object storage system
The already present object in system, and generate the metadata of the object.
Before generating next snapshot, an object may be uploaded repeatedly, therefore by way of covering, keep one
It only include a version of an object in a snapshot.Still with shown in Fig. 3, for example, needing upload object before T4 generation
OBJ obtains T3-OBJ before version information T3 is added to OBJ, and T3-OBJ is uploaded to object storage system, and T3-OBJ
Belong to T3.At this point, the T3 version of included OBJ in snapshot T3, if continuing to upload OBJ, the version information of the OBJ is still
T3-OBJ is covered already present T3-OBJ using new T3-OBJ, that is, may make stored in snapshot be object most
New version.
As a kind of optional embodiment, the above method further include: receive first and delete instruction, and delete and refer to according to first
It enables and determines snapshot to be deleted, wherein first deletes the identification information in instruction including snapshot to be deleted；Judge to be deleted fast
According to whether being quoted by other snapshots；If snapshot to be deleted is quoted by other snapshots, the metadata of snapshot to be deleted is deleted,
Retain the object data of snapshot to be deleted, wherein metadata is used to record the father's snapshot and sub- snapshot of snapshot；If to be deleted
Snapshot is not quoted by other snapshots, then is to delete by the metadata token of snapshot to be deleted.
Specifically, it is above-mentioned first delete instruction for deleting snapshot, whether snapshot is cited, can according to the snapshot whether
There is sub- snapshot to determine, if the snapshot includes the sub- snapshot dependent on it, cited in other snapshots, if the snapshot
It does not include the sub- snapshot dependent on it, then it is not cited in other snapshots.Whether relied on by other snapshots, it can be according to chain
Relationship is connect to determine.
Snapshot if necessary to deletion then cannot really delete the snapshot cited in other snapshots, and can only be to this
Snapshot carries out logic deletion, i.e., by the snapshot labeled as deleting, the snapshot if necessary to deletion is not cited in other snapshots, then
Object data in the snapshot can be deleted, the lookup without influencing data.
In an alternative embodiment, Fig. 4 is a kind of schematic diagram for deleting snapshot according to an embodiment of the present invention.In conjunction with
Shown in Fig. 4, snapshot T3 includes sub- snapshot T4, simultaneously the snapshot of non-orphaned, so if need to delete snapshot T3, then it can only be to T3
Metadata carry out logic deletion.That if necessary to deletion is snapshot T4, and due to snapshot T4 s.m.p snapshot, i.e., snapshot T4 is not by it
Cited in his snapshot, therefore the metadata and object data of snapshot T4 can be deleted.
It follows that the application above scheme does not need migrating data during the deletion of snapshot.Snapshot association letter
Breath only relies on metadata, as the mode that chained list wins a certain node extracts metadata.Such as: such as snapshot T1-T2-
T3-T4, a needs reconstruction index is T1-T2-(T3) T4 after extracing T3, therefore even if deleting snapshot, data
Still can be immediately readable/writeable, long-tail will not be caused to operate because of true IO.
As a kind of alternative embodiment, if snapshot to be deleted is quoted by other snapshots, will be described to be deleted fast
According to metadata token be delete after, the above method further include: more by the father node data of the sub- snapshot of snapshot to be deleted
It is changed to the father node of data to be deleted.
For deleted snapshot, sub- snapshot can not quote it, therefore change the adduction relationship of its sub- snapshot,
Its sub- snapshot is set to quote his father's snapshot, to make linking relationship be closed again.
Still with shown in Fig. 3, since snapshot T3 is deleted, corresponding modification, his father's snapshot are changed in the metadata of T4
For the father snapshot T2 of T3, and deletes in father's snapshot and be recorded as T3.It before T3 deletion, such as needs to retrieve object OBJ, then first from T4
Middle lookup, when reading OBJ, needs to read father's snapshot T3 of T4 due to the T4-OBJ in T4 for OBJ without latest edition
In T3-OBJ.After T3 deletion, by father's snapshot and father's snapshot is deleted and has been ranked up: T2-- > T3, recursive generation backward chain
Table T1-- > T2-- > T3-- > T4, since T3 has been deleted, searches " T2- for the object being not present under T4 from T2
The version of xxx " is then searched in T1 according to chained list as being not present in T2.
As a kind of optional embodiment, the above method further include: receive second deleting instruction, wherein the second deletion refers to
It enables for deleting the object to be deleted for belonging to any snapshot；Judge former snapshot belonging to object to be deleted whether by other snapshot institutes
Reference；If snapshot belonging to object to be deleted is cited in other snapshots, in the invisible list object of object to be deleted
The former snapshot of middle addition；If snapshot belonging to object to be deleted not cited in other snapshots, is deleted to be deleted in former snapshot
The object data of object.
Specifically, above-mentioned second deleting instruction is for deleting an object for belonging to snapshot, above-mentioned original snapshot is for indicating
Snapshot belonging to indicated object in second deleting instruction, above-mentioned invisible list are not visible for recording visibility status
Object, invisible list can be the data structures such as List, set, map, need to only be characterized in the snapshot for being arranged to deletion state
It is lower.
When deleting object, it is still necessary to determine whether original snapshot is reference, if unreferenced, illustrates second
Deleting the indicated object of instruction is to isolate, and can be deleted；If former snapshot is cited, illustrate second deleting instruction
Indicated object and non-orphaned, therefore logic deletion can only be carried out to it, add in the invisible list of deleted object
Add former snapshot.
Fig. 5 is a kind of schematic diagram for deleting object according to an embodiment of the present invention, as shown in connection with fig. 5, if pair deleted
As for T3, since T3 is quoted by T4, it is not 0 that the sub- snapshot of T3, which counts, if the object deleted is T4, since T4 s.m.p is fast
According to, therefore the sub- snapshot of T4 is counted as 0.
Fig. 6 is that seed snapshot according to an embodiment of the present invention counts the schematic diagram being not zero, and as shown in connection with fig. 6, T4 is
The rollback snapshot of T3, T6 are also the rollback snapshot of T3.The data link of snapshot T5 is T5 <-T4 <-T3 <-T2 <-T1.To delete
For T2-OBJ, and T4 be T3 sub- snapshot, therefore in the invisible list of OBJ include T4, therefore obtain it is shown in Fig. 7 right
It is as the visibility status of OBJ, i.e., visual in T1, T2, T3, deleted in T4, in T5 then without namely snapshot T5 forbid accessing OBJ.Snapshot
The data link of T6 is T6 <-T3 <-T2 <-T1.Due to do not include in the invisible list of object OBJ T6 link in appoint
Meaning node, therefore T2-OBJ is demonstrated.
Based on the link relationship between snapshot, all snapshot metadatas are established into tree-shaped relationship (as shown in Figure 8),
That is, each snapshot may be up to father's snapshot, several sub- snapshots.
As a kind of optional embodiment, the above method further include: receive rollback instruction, wherein rollback instruction include to
The mark of the purpose snapshot of rollback；Creation rollback snapshot is instructed according to rollback, and determines that the son that rollback snapshot is purpose snapshot is fast
According to.
Specifically, the new snapshot that above-mentioned rollback snapshot is creation is arranged in a snapshot on a timeline
Later, but its with common snapshot the difference is that, father's snapshot of rollback snapshot is the purpose snapshot of its rollback, and when not being
Between a upper snapshot on axis.
Fig. 9 is the schematic diagram of a kind of creation snapshot according to an embodiment of the present invention and upload object, as shown in connection with fig. 9, wound
Snapshot T1, T2, T3, T4 are built, same target OBJ is uploaded under each snapshot, and the mode of addition prefix carries version information, point
It does not name are as follows: T1_OBJ, T2_OBJ, T3_OBJ, T4_OBJ.Figure 10 is the schematic diagram that T2 is rolled back on the basis of Fig. 9, in conjunction with
Shown in Figure 10, if necessary to be rolled back to T2 from T4, then rollback snapshot T5 is automatically created, T5 quotes snapshot T2, i.e. T5 is the son of T2
Snapshot.
Figure 11 is the schematic diagram of the upload object data in rollback snapshot, in conjunction with shown in Figure 11, if into rollback snapshot
Upload object OBJ, then name can be T5-OBJ-A, and what suffix " A " can be used to indicate that the object in the snapshot is rollback
Object.
As a kind of optional embodiment, new snapshot is being created according to rollback instruction, and is determining the new snapshot of creation
After the sub- snapshot of purpose snapshot, the above method further include: receive the creation for creating snapshot and instruct；Detect rollback snapshot
In whether have object；If deleting rollback snapshot without object in rollback snapshot, and determine that the snapshot of creation is newly created
The sub- snapshot of non-rollback snapshot；If having object in rollback snapshot, it is determined that the snapshot of creation is the sub- snapshot of rollback snapshot.
In above-mentioned steps, continue to create new snapshot after rollback snapshot, be needed before creating new snapshot really
Father's snapshot of the fixed new snapshot created.If having object in rollback snapshot, created rollback snapshot as father's snapshot
It builds, if rollback snapshot can be deleted without object in rollback snapshot, and determines that the non-rollback snapshot being newly created is that father is fast
According to.
In an alternative embodiment, Figure 12 is that one kind according to an embodiment of the present invention creates snapshot after rollback snapshot
Schematic diagram, in conjunction with shown in Figure 12, T5 is the rollback snapshot for being rolled back to T2, uploads T5-OBJ in rollback snapshot T5, that is, returns
When having an object in rolling snapshot, therefore creating new new snapshot and T5 is as father's snapshot, obtains snapshot T6.Figure 13 is according to this
Another schematic diagram that snapshot is created after rollback snapshot of inventive embodiments, in conjunction with shown in Figure 13, the rollback again after T6
To T3, rollback snapshot T7 can be created, his father's snapshot is T3,, can be with if continuing to create snapshot after T7 without object in T7
T7 is deleted, directly the snapshot of creation and T3 as father's snapshot.
Still with shown in Figure 13, in reading object, association chained list: T1- > T2- > T3- > T7, wherein T3-T7 is first generated
Viewable objects T1_OBJ under viewable objects T2_OBJ, T1-T2 under lower no object, T2-T3, since T1_OBJ is legacy version
OBJ, T2_OBJ are the OBJ of new version, therefore viewable objects are T2_OBJ after rollback.Its list object can be as shown in figure 14, phase
Same object takes latest edition at the time of reading, therefore the object shown is OBJ (T3 version), i.e., the version of upload before the creation of T3 snapshot
This T2_OBJ.
As a kind of optional embodiment, after receiving the creation for creating snapshot and instructing, the above method further include:
Detect the creation time with two sub- snapshots of identical father's snapshot；If the creation time of two sub- snapshots is less than preset time
Threshold value then merges two sub- snapshots, and by two sub- snapshots labeled as deletion, wherein disconnects wherein any one height
The linking relationship of snapshot and father's snapshot, and will be switched off being connected to another sub- snapshot with the sub- snapshot of the linking relationship of father's snapshot.
Specifically, above-mentioned preset time threshold can be the time threshold of default, it is also possible to user according to actual needs
It is arranged.It, can be with when the merging of two sub- snapshots with father, above-mentioned snapshot can not only be carried out based on the judgement to the time
It carries out under the trigger of the user.
In above-mentioned steps, the merging of snapshot is based on data two and merger is divided to realize, for two or more snapshots are fast with father
According to snapshot merge, obtain a polymerization snapshot, and logic deletions are carried out to two sub- snapshots, after carrying out logic deletion,
Physical addressing mode is constant, and the object that logic deletes only no longer is shown to user.It, will when carrying out the merging of two snapshots
Any two disconnect linking for one of snapshot and his father's snapshot there are the snapshot of common parent snapshot, and link to another fast
According to child release as another snapshot.After merging two snapshots, aforesaid way can also be continued on and closed two-by-two
And until merging becomes a snapshot.By the merging of snapshot, to achieve the purpose that convenient for metadata management.
Embodiment 2
According to embodiments of the present invention, a kind of embodiment of fast photographing device based on object bucket is provided, Figure 15 is root
According to the schematic diagram of the first fast photographing device based on object bucket of the embodiment of the present invention, snapshot includes: metadata and number of objects
According to, wherein metadata is used to record the linking relationship between snapshot, and linking relationship is for indicating dependence of the sub- snapshot to father's snapshot
Relationship, object data is for recording the object for belonging to snapshot, and in conjunction with shown in Figure 15, which includes:
Determining module 150, for determining target snapshot, wherein target snapshot is last after receiving object to be written
The snapshot of generation.
Adding module 152 obtains pair for carrying version information for adding the version information of target snapshot for object
As.
Writing module 154, object storage system is written in the object for that will carry version information, and generates the object
Metadata, wherein the metadata of the object indicates that the object data belongs to the target snapshot.
As a kind of optional embodiment, writing module includes: write-in submodule, if be used in the target snapshot not
There are the corresponding object datas of the object, object storage system directly are written in the object for carrying version information, and generate
The metadata of the object；Submodule is replaced, if for the corresponding number of objects of the object existing in the target snapshot
According to replacing the already present object in the object storage system using the object for carrying the version information, and generate
The metadata of the object.
As a kind of optional embodiment, above-mentioned apparatus further include: the first receiving module refers to for receiving first and deleting
It enables, and deletes instruction according to first and determine snapshot to be deleted, wherein include the mark of snapshot to be deleted in the first deletion instruction
Information；First judgment module, for judging whether snapshot to be deleted is quoted by other snapshots；First removing module, for such as
Fruit snapshot to be deleted is quoted by other snapshots, then is to delete by the metadata token of the snapshot to be deleted；Second deletes mould
Block deletes the metadata and object data of snapshot to be deleted if do not quoted by other snapshots for snapshot to be deleted.
As a kind of optional embodiment, above-mentioned apparatus further include: change module, if for snapshot to be deleted by it
He quotes snapshot, then after being to delete by the metadata token of the snapshot to be deleted, by the sub- snapshot of snapshot to be deleted
Father's snapshot is changed to father's snapshot of snapshot to be deleted.
As a kind of optional embodiment, above-mentioned apparatus further include: the second receiving module refers to for receiving second and deleting
It enables, wherein the second deleting instruction is for deleting the object to be deleted for belonging to any snapshot；Second judgment module, for sentencing
Former snapshot belonging to object to be deleted break whether cited in other snapshots；Third removing module, if for former snapshot by it
Cited in his snapshot, then former snapshot is added in the invisible list object of object to be deleted；4th removing module, if for
Former snapshot then deletes the object data of object to be deleted in the former snapshot not cited in other snapshots.
As a kind of optional embodiment, above-mentioned apparatus further include: third receiving module, for receiving rollback instruction,
In, rollback instruction includes the mark of the purpose snapshot to rollback；Determining module, for instructing creation rollback snapshot according to rollback,
And determine that rollback snapshot is the sub- snapshot of purpose snapshot.
As a kind of optional embodiment, above-mentioned apparatus further include: creating new snapshot according to rollback instruction, and determining
The new snapshot of creation is the 4th receiving module, for receiving the creation for creating snapshot after the sub- snapshot of purpose snapshot
Instruction；First detection module, for detecting in rollback snapshot whether have object；First creation module, if being used for rollback snapshot
Middle no object then deletes rollback snapshot, and is that father's snapshot creates sub- snapshot with the non-rollback snapshot being newly created；Second creation mould
Block, if being that father's snapshot creates sub- snapshot with rollback snapshot for having object in rollback snapshot.
As a kind of optional embodiment, above-mentioned apparatus further include: the second detection module has identical father fast for detecting
According to two sub- snapshots creation time；Merging module, if the creation time for two sub- snapshots is less than preset time threshold
Value, then merge two sub- snapshots, and by two sub- snapshots labeled as deletion, wherein it is fast to disconnect wherein any one height
According to the linking relationship with father's snapshot, and will be switched off being connected to another sub- snapshot with the sub- snapshot of the linking relationship of father's snapshot.
Embodiment 3
According to embodiments of the present invention, a kind of embodiment of fast photographic system based on object bucket is provided, the system packet
The object storage system and at least one snapshot for storage object are included, at least one snapshot includes: metadata, fast for recording
Linking relationship according between, linking relationship include dependence of the sub- snapshot to father's snapshot；Object data belongs to fastly for recording
According to object.
As a kind of optional embodiment, metadata includes: father's snapshot identification, sub- snapshot identification and deleted father's snapshot
Mark.
The fast photographic system based on object bucket in the embodiment of the present application may include the snapshot in embodiment 1, specifically
Explanation in the visible embodiment 1 of embodiment, details are not described herein again.
The fast photographic system based on object bucket in the embodiment of the present application can execute the step in embodiment 1, herein
Also it repeats no more.
Embodiment 4
According to embodiments of the present invention, a kind of storage medium is provided, storage medium includes the program of storage, wherein in institute
Equipment where controlling the storage medium when stating program operation executes described in any one of embodiment 1 based on object bucket
Snapshot Method.
Embodiment 5
According to embodiments of the present invention, a kind of processor is provided, processor is for running program, wherein described program fortune
The Snapshot Method based on object bucket described in any one of embodiment 1 is executed when row.
The serial number of the above embodiments of the invention is only for description, does not represent the advantages or disadvantages of the embodiments.
In the above embodiment of the invention, it all emphasizes particularly on different fields to the description of each embodiment, does not have in some embodiment
The part of detailed description, reference can be made to the related descriptions of other embodiments.
In several embodiments provided herein, it should be understood that disclosed technology contents can pass through others
Mode is realized.Wherein, the apparatus embodiments described above are merely exemplary, such as the division of the unit, Ke Yiwei
A kind of logical function partition, there may be another division manner in actual implementation, for example, multiple units or components can combine or
Person is desirably integrated into another system, or some features can be ignored or not executed.Another point, shown or discussed is mutual
Between coupling, direct-coupling or communication connection can be through some interfaces, the INDIRECT COUPLING or communication link of unit or module
It connects, can be electrical or other forms.
The unit as illustrated by the separation member may or may not be physically separated, aobvious as unit
The component shown may or may not be physical unit, it can and it is in one place, or may be distributed over multiple
On unit.It can some or all of the units may be selected to achieve the purpose of the solution of this embodiment according to the actual needs.
It, can also be in addition, the functional units in various embodiments of the present invention may be integrated into one processing unit
It is that each unit physically exists alone, can also be integrated in one unit with two or more units.Above-mentioned integrated list
Member both can take the form of hardware realization, can also realize in the form of software functional units.
If the integrated unit is realized in the form of SFU software functional unit and sells or use as independent product
When, it can store in a computer readable storage medium.Based on this understanding, technical solution of the present invention is substantially
The all or part of the part that contributes to existing technology or the technical solution can be in the form of software products in other words
It embodies, which is stored in a storage medium, including some instructions are used so that a computer
Equipment (can for personal computer, server or network equipment etc.) execute each embodiment the method for the present invention whole or
Part steps.And storage medium above-mentioned includes: that USB flash disk, read-only memory (ROM, Read-Only Memory), arbitrary access are deposited
Reservoir (RAM, Random Access Memory), mobile hard disk, magnetic or disk etc. be various to can store program code
Medium.
The above is only a preferred embodiment of the present invention, it is noted that for the ordinary skill people of the art
For member, various improvements and modifications may be made without departing from the principle of the present invention, these improvements and modifications are also answered
It is considered as protection scope of the present invention.
Claims (13)
1. a kind of Snapshot Method based on object bucket, which is characterized in that the snapshot includes: metadata and object data,
Wherein, the metadata is used to record linking relationship between snapshot, the linking relationship include sub- snapshot to father's snapshot according to
The relationship of relying, the object data is for recording the object for belonging to the snapshot, the Snapshot Method packet based on object bucket
It includes:
After receiving object to be written, target snapshot is determined, wherein the target snapshot is the snapshot ultimately produced；
The version information that the target snapshot is added for the object obtains the object for carrying version information；
Object storage system is written into the object for carrying the version information, and generates the metadata of the object, wherein institute
The metadata for stating object indicates that the object data belongs to the target snapshot.
2. the method according to claim 1, wherein the object for carrying version information write-in object is deposited
Storage system, and generate the metadata of the object, comprising:
If the corresponding object data of the object is not present in the target snapshot, the object of version information will be directly carried
Object storage system is written, and generates the metadata of the object；
If the corresponding object data of the existing object, uses pair for carrying the version information in the target snapshot
As replacing the already present object in the object storage system, and generate the metadata of the object.
3. the method according to claim 1, wherein the method also includes:
It receives first and deletes instruction, and delete instruction according to described first and determine snapshot to be deleted, wherein described first deletes
It include the identification information of snapshot to be deleted in instruction；
Judge whether the snapshot to be deleted is quoted by other snapshots；
It is to delete by the metadata token of the snapshot to be deleted if the snapshot to be deleted is quoted by other snapshots；
If the snapshot to be deleted is not quoted by other snapshots, the metadata and number of objects of the snapshot to be deleted are deleted
According to.
4. according to the method described in claim 3, its feature is being, if the snapshot to be deleted is illuminated the way fastly by other
With, then after being to delete by the metadata token of the snapshot to be deleted, the method also includes:
Father's snapshot of the sub- snapshot of the snapshot to be deleted is changed to father's snapshot of the snapshot to be deleted.
5. the method according to claim 1, wherein the method also includes:
Receive second deleting instruction, wherein the second deleting instruction is for deleting the object to be deleted for belonging to any snapshot；
Judge former snapshot belonging to the object to be deleted whether cited in other snapshots；
If the original snapshot adds institute in the invisible list object of the object to be deleted cited in other snapshots
State former snapshot；
If the original snapshot not cited in other snapshots, deletes the object data of object to be deleted in the former snapshot.
6. the method according to claim 1, wherein the method also includes:
Receive rollback instruction, wherein the rollback instruction includes the mark of the purpose snapshot to rollback；
Creation rollback snapshot is instructed according to the rollback, and determines that the rollback snapshot is the sub- snapshot of the purpose snapshot.
7. according to the method described in claim 6, it is characterized in that, creating new snapshot according to rollback instruction, and really
Surely after the new snapshot created is the sub- snapshot of the purpose snapshot, the method also includes:
The creation for creating snapshot is received to instruct；
Whether detect in the rollback snapshot has object；
If deleting the rollback snapshot without object in the rollback snapshot, and with the non-rollback snapshot that is newly created for father
Snapshot creates sub- snapshot；
It is that father's snapshot creates sub- snapshot with the rollback snapshot if having object in the rollback snapshot.
8. the method according to claim 1, wherein the method also includes:
Detect the creation time with two sub- snapshots of identical father's snapshot；
If the creation time of described two sub- snapshots is less than preset time threshold, described two sub- snapshots are merged,
And by described two sub- snapshots labeled as deleting, wherein disconnect wherein any one sub- snapshot and father's snapshot links pass
System, and will be switched off being connected to another sub- snapshot with the sub- snapshot of the linking relationship of father's snapshot.
9. a kind of fast photographing device based on object bucket, which is characterized in that the snapshot includes: metadata and object data,
Wherein, the metadata is used to record linking relationship between snapshot, the linking relationship include sub- snapshot to father's snapshot according to
The relationship of relying, the object data is for recording the object for belonging to the snapshot, the fast photographing device packet based on object bucket
It includes:
Determining module, for determining target snapshot after receiving object to be written, wherein the target snapshot is last raw
At snapshot；
Adding module obtains pair for carrying version information for adding the version information of the target snapshot for the object
As；
Writing module, object storage system is written in the object for that will carry the version information, and generates the object
Metadata, wherein the metadata of the object indicates that the object data belongs to the target snapshot.
10. a kind of fast photographic system based on object bucket, which is characterized in that the system comprises the objects for storage object
Storage system and at least one snapshot, at least one described snapshot include:
Metadata, for recording the linking relationship between snapshot, the linking relationship includes that sub- snapshot closes the dependence of father's snapshot
System；
Object data, for recording the object for belonging to the snapshot.
11. system according to claim 10, which is characterized in that the metadata includes: father's snapshot identification, the fast sighting target of son
Know the mark with deleted father's snapshot.
12. a kind of storage medium, which is characterized in that the storage medium includes the program of storage, wherein run in described program
When control the storage medium where equipment perform claim require any one of 1 to 8 described in based on the fast of object bucket
According to method.
13. a kind of processor, which is characterized in that the processor is for running program, wherein right of execution when described program is run
Benefit require any one of 1 to 8 described in the Snapshot Method based on object bucket.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910713323.8A CN110515543B (en) | 2019-08-02 | 2019-08-02 | Object bucket-based snapshot method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910713323.8A CN110515543B (en) | 2019-08-02 | 2019-08-02 | Object bucket-based snapshot method, device and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110515543A true CN110515543A (en) | 2019-11-29 |
| CN110515543B CN110515543B (en) | 2021-02-19 |
Family
ID=68624265
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910713323.8A Active CN110515543B (en) | 2019-08-02 | 2019-08-02 | Object bucket-based snapshot method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110515543B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113640321A (en) * | 2020-05-11 | 2021-11-12 | 同方威视技术股份有限公司 | Security check delay optimization method and device |
| CN113821476A (en) * | 2021-11-25 | 2021-12-21 | 云和恩墨(北京)信息技术有限公司 | Data processing method and device |
| CN114116312A (en) * | 2021-11-25 | 2022-03-01 | 北京大道云行科技有限公司 | ROW snapshot design method and system based on distributed block storage |
Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101162469A (en) * | 2007-11-09 | 2008-04-16 | 清华大学 | Fine grit document and catalogs version management method based on snapshot |
| CN101178677A (en) * | 2007-11-09 | 2008-05-14 | 中国科学院计算技术研究所 | Computer system for protecting software and method for protecting software |
| CN101419564A (en) * | 2008-12-11 | 2009-04-29 | 杭州华三通信技术有限公司 | Method and device for recovering data by employing snapshot |
| CN103473277A (en) * | 2013-08-27 | 2013-12-25 | 华为技术有限公司 | Snapshot method and device for file systems |
| CN103544077A (en) * | 2012-07-17 | 2014-01-29 | 华为技术有限公司 | Data processing method and device and shared memory device |
| CN104537023A (en) * | 2014-12-19 | 2015-04-22 | 华为技术有限公司 | Storage method and device for reverse index records |
| CN105095016A (en) * | 2014-05-16 | 2015-11-25 | 北京云巢动脉科技有限公司 | Disk snapshot roll-back method and device |
| CN106569738A (en) * | 2016-09-30 | 2017-04-19 | 华为技术有限公司 | Method and apparatus for deleting cascading snapshot |
| CN107066495A (en) * | 2016-12-29 | 2017-08-18 | 北京瑞卓喜投科技发展有限公司 | The generation method and system for the block chain expanded along longitudinal direction |
| US20180150492A1 (en) * | 2015-08-20 | 2018-05-31 | Vmware, Inc. | Tracking data of virtual disk snapshots using tree data structures |
| CN108604201A (en) * | 2016-12-30 | 2018-09-28 | 华为技术有限公司 | A kind of snapshot rollback method, device, storage control and system |
| CN109063210A (en) * | 2018-09-25 | 2018-12-21 | 郑州云海信息技术有限公司 | Resource object querying method, device, equipment and the storage medium of storage system |
| CN109933564A (en) * | 2019-03-27 | 2019-06-25 | 中国科学院上海微系统与信息技术研究所 | File system management method, device, terminal, the medium of quick rollback are realized based on chained list and N-ary tree construction |
| CN110008175A (en) * | 2019-04-11 | 2019-07-12 | 苏州浪潮智能科技有限公司 | A kind of distributed objects storage Snapshot Method, system, equipment and computer media |
| US20190220205A1 (en) * | 2018-01-12 | 2019-07-18 | Robin Systems, Inc. | Job Manager For Deploying A Bundled Application |
-
2019
- 2019-08-02 CN CN201910713323.8A patent/CN110515543B/en active Active
Patent Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101162469A (en) * | 2007-11-09 | 2008-04-16 | 清华大学 | Fine grit document and catalogs version management method based on snapshot |
| CN101178677A (en) * | 2007-11-09 | 2008-05-14 | 中国科学院计算技术研究所 | Computer system for protecting software and method for protecting software |
| CN101419564A (en) * | 2008-12-11 | 2009-04-29 | 杭州华三通信技术有限公司 | Method and device for recovering data by employing snapshot |
| CN103544077A (en) * | 2012-07-17 | 2014-01-29 | 华为技术有限公司 | Data processing method and device and shared memory device |
| CN103473277A (en) * | 2013-08-27 | 2013-12-25 | 华为技术有限公司 | Snapshot method and device for file systems |
| CN105095016A (en) * | 2014-05-16 | 2015-11-25 | 北京云巢动脉科技有限公司 | Disk snapshot roll-back method and device |
| CN104537023A (en) * | 2014-12-19 | 2015-04-22 | 华为技术有限公司 | Storage method and device for reverse index records |
| US20180150492A1 (en) * | 2015-08-20 | 2018-05-31 | Vmware, Inc. | Tracking data of virtual disk snapshots using tree data structures |
| CN106569738A (en) * | 2016-09-30 | 2017-04-19 | 华为技术有限公司 | Method and apparatus for deleting cascading snapshot |
| CN107066495A (en) * | 2016-12-29 | 2017-08-18 | 北京瑞卓喜投科技发展有限公司 | The generation method and system for the block chain expanded along longitudinal direction |
| CN108604201A (en) * | 2016-12-30 | 2018-09-28 | 华为技术有限公司 | A kind of snapshot rollback method, device, storage control and system |
| US20190220205A1 (en) * | 2018-01-12 | 2019-07-18 | Robin Systems, Inc. | Job Manager For Deploying A Bundled Application |
| CN109063210A (en) * | 2018-09-25 | 2018-12-21 | 郑州云海信息技术有限公司 | Resource object querying method, device, equipment and the storage medium of storage system |
| CN109933564A (en) * | 2019-03-27 | 2019-06-25 | 中国科学院上海微系统与信息技术研究所 | File system management method, device, terminal, the medium of quick rollback are realized based on chained list and N-ary tree construction |
| CN110008175A (en) * | 2019-04-11 | 2019-07-12 | 苏州浪潮智能科技有限公司 | A kind of distributed objects storage Snapshot Method, system, equipment and computer media |
Non-Patent Citations (2)
| Title |
|---|
| LIJUN CHEN等: "A snapshot system based on cloud storage Log-Structured Block System", 《PROCEEDINGS OF THE 11TH IEEE INTERNATIONAL CONFERENCE ON NETWORKING, SENSING AND CONTROL》 * |
| 陈莉君等: "云存储日志文件系统中快照的设计与实现", 《计算机应用与软件》 * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113640321A (en) * | 2020-05-11 | 2021-11-12 | 同方威视技术股份有限公司 | Security check delay optimization method and device |
| CN113640321B (en) * | 2020-05-11 | 2024-04-02 | 同方威视技术股份有限公司 | Security inspection delay optimization method and equipment |
| CN113821476A (en) * | 2021-11-25 | 2021-12-21 | 云和恩墨(北京)信息技术有限公司 | Data processing method and device |
| CN114116312A (en) * | 2021-11-25 | 2022-03-01 | 北京大道云行科技有限公司 | ROW snapshot design method and system based on distributed block storage |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110515543B (en) | 2021-02-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US5276874A (en) | Method for creating a directory tree in main memory using an index file in secondary memory | |
| CN110515543A (en) | Object bucket-based snapshot method, device and system | |
| CN100399327C (en) | Managing file system versions | |
| JP4354233B2 (en) | Backup system and method | |
| US20220222154A1 (en) | Restoration of specified content from an archive | |
| US8271456B2 (en) | Efficient backup data retrieval | |
| CN106874066B (en) | Virtual machine migration method and device and electronic equipment | |
| US8874517B2 (en) | Summarizing file system operations with a file system journal | |
| US8126997B2 (en) | Hot data management method based on hit counter | |
| WO2011108021A1 (en) | File level hierarchical storage management system, method, and apparatus | |
| US20080005145A1 (en) | Data processing | |
| CN100377112C (en) | Disk drive, control method thereof and disk-falsification detection method | |
| US7769719B2 (en) | File system dump/restore by node numbering | |
| EP3042289A1 (en) | Replication of snapshots and clones | |
| US20080281788A1 (en) | Hierarchical structured abstract file system | |
| EP1964004A2 (en) | Multi-segment string search | |
| CN110928498B (en) | Directory traversal method, device, equipment and storage medium | |
| US6192376B1 (en) | Method and apparatus for shadowing a hierarchical file system index structure to enable error recovery | |
| CN114281779A (en) | Data synchronization method and device, computer equipment and storage medium | |
| US20050234951A1 (en) | Method and system for renaming consecutive keys in a B-tree | |
| CN108446308A (en) | The system and method for scalable distributed database | |
| CN110308895A (en) | The project development method that Project Development Platform and application item development platform are carried out | |
| JP3985430B2 (en) | Database management apparatus and method | |
| KR102232003B1 (en) | Method for object management using trace identifier, apparatus for the same, computer program for the same, and recording medium storing computer program thereof | |
| US8886656B2 (en) | Data processing |
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 | ||
| CP03 | Change of name, title or address |
Address after: 100094 101, floors 1-5, building 7, courtyard 3, fengxiu Middle Road, Haidian District, Beijing Patentee after: Beijing Xingchen Tianhe Technology Co.,Ltd. Address before: 100097 room 806-1, block B, zone 2, Jinyuan times shopping center, indigo factory, Haidian District, Beijing Patentee before: XSKY BEIJING DATA TECHNOLOGY Corp.,Ltd. |
|
| CP03 | Change of name, title or address |