CN109614055B - Snapshot creating method and device, electronic equipment and machine-readable storage medium - Google Patents
Snapshot creating method and device, electronic equipment and machine-readable storage medium Download PDFInfo
- Publication number
- CN109614055B CN109614055B CN201811574817.4A CN201811574817A CN109614055B CN 109614055 B CN109614055 B CN 109614055B CN 201811574817 A CN201811574817 A CN 201811574817A CN 109614055 B CN109614055 B CN 109614055B
- Authority
- CN
- China
- Prior art keywords
- snapshot
- full
- state
- data
- production volume
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
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/0614—Improving the reliability of storage systems
Abstract
The application provides a snapshot creating method and device, electronic equipment and a machine-readable storage medium. In the present application, a write redirection snapshot mode is enabled for a production volume and a snapshot policy is preset, and a series of snapshots are created for the production volume according to the snapshot policy, where the types of the snapshots include: incremental snapshot, full snapshot; acquiring a space mapping table of the production volume, wherein the space mapping table is used for recording storage mapping information of data in the production volume; and creating a full snapshot corresponding to the production volume based on the space mapping table, and reducing the dependence among a plurality of incremental snapshots by matching the full snapshot or the full snapshot with the incremental snapshots, thereby improving the data security of the snapshots, reducing the time required by the snapshot rollback and improving the snapshot rollback efficiency.
Description
Technical Field
The present application relates to the field of storage technologies, and in particular, to a snapshot creation method and apparatus, an electronic device, and a machine-readable storage medium.
Background
In the big data era, the data volume is getting bigger and bigger, and the data is also getting more and more important, so that it has become a mainstream way to store the data in a special storage device and improve the data reliability by the data protection characteristic of the storage device.
Snapshots are one of the data protection features of storage devices and are a common solution to deal with "soft disasters". Soft disasters, so called "soft" disasters, generally refer to production data that is logically corrupted or unreadable due to misoperations, software bugs, viruses, and the like. By means of snapshot technology, old data can be stored before new data is written, so that when a soft disaster occurs to the data, the old data stored before can be used for recovery, and the data can be rolled back to an available time plane.
Disclosure of Invention
The application provides a snapshot creating method, a production volume starts a write redirection snapshot mode and presets a snapshot strategy, and a series of snapshots are created for the production volume according to the snapshot strategy, wherein the types of the snapshots comprise: incremental snapshot, full snapshot, the method comprising:
acquiring a space mapping table of the production volume, wherein the space mapping table is used for recording storage mapping information of data in the production volume;
and creating a full snapshot corresponding to the production volume based on the space mapping table.
Optionally, before the obtaining the space mapping table of the production volume, the method further includes:
acquiring a full identifier of the production volume, wherein the full identifier is used for marking whether the production volume is in a state of creating a full snapshot, and possible values of the state of the full identifier include: a first state or a second state, the state default value of the full identity being the second state;
and if the state of the full identity is the first state, forbidding the creation operation of a new full snapshot.
Optionally, before creating the full-volume snapshot corresponding to the production volume based on the space mapping table, the method further includes:
if the state of the full identifier is the second state, updating the state of the full identifier to be the first state;
and creating a copy state record table corresponding to the space mapping table of the production volume, wherein the copy state record table is used for recording the copy state of copying the space mapping table to the full snapshot.
Optionally, after creating the full-volume snapshot corresponding to the production volume based on the space mapping table, the method further includes:
and updating the state of the full identifier from a first state to a second state, and deleting the copy state record table.
Optionally, the copy status record table is based on a bitmap, where each bit in the bitmap is used to mark whether a storage block with a preset length in the space mapping table has been copied, and possible values of each bit are: the default value of each bit is the first type; the creating a full snapshot corresponding to the production volume based on the space mapping table includes:
based on each bit of the bitmap, copying data in a storage block with a preset length corresponding to the bit in the space mapping table TB1 into a space mapping table TB2 correspondingly stored in the full snapshot, and updating the value of the bit from a first type to a second type.
Optionally, the method further includes:
and if the data D1 in the storage block with the preset length corresponding to one or more bits of the copy state recording table in the space mapping table TB1 is to be updated to be the data D2 and the state of the one or more bits is of a second type, updating the corresponding data D1 in the space mapping table TB1 to be the data D2.
Optionally, the method further includes:
if data D1 in a storage block with a preset length corresponding to one or more bits of the copy state record table in the space mapping table TB1 is to be updated to be data D2, and the state of the one or more bits is of a first type, creating a mutual exclusion lock, wherein the mutual exclusion lock is used for forbidding updating of the data D1 to be the data D2;
copying data in a storage block with a preset length corresponding to one or more bits where the data D1 is located from the space mapping table to a space mapping table TB2 correspondingly stored in the full snapshot, and updating the state of the bits of the storage block with the preset length corresponding to the one or more bits where the data D1 is located in the copy state recording table to be of a second type;
deleting the mutual exclusion lock, wherein the mutual exclusion lock is used for allowing the data D1 to be updated into the data D2; and updates the data D1 to the data D2.
Optionally, when triggering the production volume snapshot to roll back to the target snapshot, the method further includes:
if the target snapshot is a full snapshot, acquiring a space mapping table TB2 of the full snapshot;
and covering the space mapping table TB1 of the production volume with TB2, and rolling back the production volume to the historical data at the corresponding moment of the target snapshot.
Optionally, when triggering the production volume snapshot to roll back to the target snapshot, the method further includes:
if the target snapshot is an incremental snapshot, acquiring a most recent full snapshot after the creation time of the target snapshot and other incremental snapshots between the target snapshot and the full snapshot creation time;
rolling back the production volume to historical data at a corresponding moment of the full snapshot;
and rolling back the production volume to historical data of the target snapshot at the corresponding moment according to the creation time of the other incremental snapshots from new to old.
The application also provides a snapshot creating device, where a production volume has enabled a write redirection snapshot mode and is preset with a snapshot policy, and a series of snapshots are created for the production volume according to the snapshot policy, where the types of the snapshots include: incremental snapshot, full snapshot, the apparatus comprising:
the acquisition module is used for acquiring a space mapping table of the production volume, wherein the space mapping table is used for recording storage mapping information of data in the production volume;
and the creating module is used for creating the full snapshot corresponding to the production volume based on the space mapping table.
Optionally, before the obtaining the space mapping table of the production volume, the creating module further includes:
acquiring a full identifier of the production volume, wherein the full identifier is used for marking whether the production volume is in a state of creating a full snapshot, and possible values of the state of the full identifier include: a first state or a second state, the state default value of the full identity being the second state;
and if the state of the full identity is the first state, forbidding the creation operation of a new full snapshot.
Optionally, before creating the full-volume snapshot corresponding to the production volume based on the space mapping table, the creating module further includes:
if the state of the full identifier is the second state, updating the state of the full identifier to be the first state;
and creating a copy state record table corresponding to the space mapping table of the production volume, wherein the copy state record table is used for recording the copy state of copying the space mapping table to the full snapshot.
Optionally, after the creating a full snapshot corresponding to the production volume based on the space mapping table, the creating module further includes:
and updating the state of the full identifier from a first state to a second state, and deleting the copy state record table.
Optionally, the copy status record table is based on a bitmap, where each bit in the bitmap is used to mark whether a storage block with a preset length in the space mapping table has been copied, and possible values of each bit are: the default value of each bit is a first type or a second type; the creating a full snapshot corresponding to the production volume based on the space mapping table includes:
the creation module copies data in a storage block with a preset length corresponding to the bit in the space mapping table TB1 to a space mapping table TB2 correspondingly stored in the full snapshot based on each bit of the bitmap, and updates the value of the bit from a first type to a second type.
Optionally, the creating module further includes:
and if the data D1 in the storage block with the preset length corresponding to one or more bits of the copy state recording table in the space mapping table TB1 is to be updated into the data D2 and the state of the one or more bits is of a second type, updating the corresponding data D1 in the space mapping table TB1 into the data D2.
Optionally, the creating module further includes:
if data D1 in a storage block with a preset length corresponding to one or more bits of the copy state record table in the space mapping table TB1 is to be updated to be data D2, and the state of the one or more bits is of a first type, creating a mutual exclusion lock, wherein the mutual exclusion lock is used for forbidding updating of the data D1 to be the data D2;
copying data in a storage block with a preset length corresponding to one or more bits where the data D1 is located from the space mapping table to a space mapping table TB2 correspondingly stored in the full snapshot, and updating the state of the bits of the storage block with the preset length corresponding to the one or more bits where the data D1 is located in the copy state recording table to be of a second type;
deleting the mutual exclusion lock, wherein the mutual exclusion lock is used for allowing the data D1 to be updated into the data D2; and updates the data D1 to the data D2.
Optionally, when triggering the production volume snapshot to roll back to the target snapshot, the method further includes:
the rollback module is used for acquiring a space mapping table TB2 of the full snapshot if the target snapshot is the full snapshot;
and the rollback module is used for covering the space mapping table TB1 of the production volume with TB2 and rolling back the production volume to the historical data of the target snapshot at the corresponding moment.
Optionally, when triggering the production volume snapshot to rollback to the target snapshot, the rollback module further includes:
if the target snapshot is an incremental snapshot, acquiring a most recent full snapshot after the creation time of the target snapshot and other incremental snapshots between the target snapshot and the full snapshot within the creation time;
rolling back the production volume to historical data at a moment corresponding to the full snapshot;
and rolling back the production volume to historical data of the target snapshot at the corresponding moment according to the creation time of the other incremental snapshots from new to old.
The application also provides an electronic device, which comprises a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are mutually connected through the bus; the memory stores machine-readable instructions, and the processor executes the method by calling the machine-readable instructions.
The present application also provides a machine-readable storage medium having stored thereon machine-readable instructions which, when invoked and executed by a processor, implement the above-described method.
Through the above embodiment, the storage device enables a write redirection snapshot mode for a production volume and presets a snapshot policy, and creates a series of snapshots for the production volume according to the snapshot policy, where the types of the snapshots include: incremental snapshot, full snapshot; acquiring a space mapping table of the production volume, wherein the space mapping table is used for recording storage mapping information of data in the production volume; and creating a full snapshot corresponding to the production volume based on the space mapping table, and reducing the dependence among a plurality of incremental snapshots by matching the full snapshot or the full snapshot with the incremental snapshots, thereby improving the data security of the snapshots, reducing the time required by the snapshot rollback and improving the snapshot rollback efficiency.
Drawings
FIG. 1 is a flow chart of a snapshot creation method provided by an exemplary embodiment.
FIG. 2 is a flow diagram of a full volume snapshot creation provided by an exemplary embodiment.
Fig. 3 is a block diagram of a management apparatus for snapshot creation according to an exemplary embodiment.
Fig. 4 is a hardware block diagram of an electronic device according to an exemplary embodiment.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at" \8230; \8230when "or" when 8230; \823030, when "or" in response to a determination ", depending on the context.
In order to make those skilled in the art better understand the technical solution in the embodiment of the present application, the snapshot related technology related to the embodiment of the present application is briefly described below.
Write redirection, or ROW (Redirect On Write), is a commonly used snapshot technology at present, and the method is to, after creating a new snapshot, allocate an additional area for new data to be written instead of covering the original area corresponding to the production volume data when the data of the production volume is changed for the first time, and at the same time, change the old data in the original area corresponding to the production volume data into snapshot data to be provided for the latest snapshot to use. The ROW mode snapshot is an incremental snapshot, and each new snapshot records only data which is changed for the first time on a production volume after the creation time of the new snapshot, and the data which is changed for the first time does not need to be recorded to an old snapshot. For the snapshot in the ROW mode, after a snapshot a is created, when new data ND is written into a production volume for the first time to a certain storage location, the new data ND is redirected to a new storage location, that is, old data OD stored corresponding to the storage address is converted into snapshot data of the snapshot a, a physical space corresponding to the storage location does not change, and the new data ND is still in the original location, that is, the new data ND does not affect the storage location of the snapshot data (i.e., the old data OD) of the snapshot a.
Based on the above analysis, the present application introduces several newly defined concepts: full snapshot, incremental snapshot. The full snapshot refers to that at the creation time T1 of a certain snapshot B, a copy of the space mapping table of the production volume corresponding to the creation time T1 is made as the management data of the snapshot B, based on the above description, the data of the production volume corresponding to the creation time T1 of the snapshot B can be quickly accessed through the management data of the snapshot B, that is, the management information of the snapshot B includes the complete space mapping table of the production volume, and the snapshot B is called a full snapshot. Accordingly, some snapshot C in the existing implementation is referred to as an incremental snapshot.
In some scenarios, the advantage of the ROW incremental snapshot in the existing implementation is: the generation speed is high; the disadvantages are that: data rollback is complex, and if production volume data is rolled back to the creation time corresponding to the designated snapshot, all snapshots before the current time and after the creation time corresponding to the designated snapshot need to be rolled back. Such as: assuming that one snapshot is created every 1 hour on a production volume and 72 snapshots have been created, the current time is 10 am and a half today, if a soft disaster is found on the production volume, the data in the production volume needs to be rolled back to an available time plane; if the available time plane corresponds to 8 points in the previous day, namely, the production volume needs to be rolled back to the snapshot corresponding to 8 points in yesterday, the snapshot corresponding to 8 points in yesterday needs to be rolled back to the snapshot corresponding to 10 points in today, 27 snapshots are needed in total, and the snapshots from 10 points in today are rolled back one by one according to the snapshot creation time from the newest to the oldest; if the available time plane corresponds to an earlier snapshot 8 o' clock before yesterday, the rollback involves a greater number of snapshots and the rollback time is longer. It can be seen from the above description that the existing incremental snapshot is fast in generation speed, but the old incremental snapshot depends on the new incremental snapshot, if the new incremental snapshot is lost, the production volume cannot be rolled back to the time corresponding to the old incremental snapshot, that is, there is a strict dependency relationship among the plurality of incremental snapshots, the snapshot data security has a certain risk, in addition, the snapshot rolling back process involves all the incremental snapshots between the rolled back target snapshot and the current time, the rolling back time is long, and the rolling back efficiency is low.
Based on this, the present application provides a snapshot creation technical solution, where a storage device enables a write redirection snapshot mode for a production volume and presets a snapshot policy, and creates a series of snapshots for the production volume according to the snapshot policy, where the types of the snapshots include: incremental snapshot, full snapshot; the scheme comprises the following steps:
acquiring a space mapping table of the production volume, wherein the space mapping table is used for recording storage mapping information of data in the production volume; and creating a full snapshot corresponding to the production volume based on the space mapping table, and reducing the dependence among a plurality of incremental snapshots through the cooperation of the full snapshot or the full snapshot and the incremental snapshots, thereby improving the data security of the snapshots, reducing the time required by the rollback of the snapshots, and improving the efficiency of the rollback of the snapshots.
The present application is described below by using specific embodiments and in conjunction with specific application scenarios.
Referring to fig. 1, fig. 1 is a block diagram illustrating a snapshot creating method according to an embodiment of the present application, applied to a storage device; the method comprises the following steps that a write redirection snapshot mode is started for a production volume, a snapshot strategy is preset, and a series of snapshots are created for the production volume according to the snapshot strategy, wherein the types of the snapshots comprise: incremental snapshot, full snapshot, the above method executes the following steps:
102, obtaining a space mapping table of the production volume, wherein the space mapping table is used for recording storage mapping information of data in the production volume.
The production volume actually corresponds to a storage volume, the volume type of the storage volume may be a common volume or a thin provisioning volume, and is not specifically limited in this application, the production volume already enables a write-redirect snapshot mode and is preset with a snapshot policy, and the storage device may create a series of snapshots for the production volume according to the snapshot policy. The space mapping table here refers to a space mapping table TB1 that the storage device simultaneously obtains the corresponding time of the production volume at time T1 when the storage device creates a full snapshot FS1 for the production volume at time T1, where the space mapping table is used to record storage mapping information of data in the production volume, that is, record an actual storage location of the data in the production volume.
Optionally, in an illustrated embodiment, before the storage device obtains the space mapping table TB1 of the production volume, the storage device obtains a full identifier of the production volume, where the full identifier is used to mark whether the production volume is in a state of creating a full snapshot, and a possible value of the state of the full identifier includes: the snapshot creating method comprises a first state or a second state, wherein the first state is used for identifying that the production volume is in the process of creating a full snapshot, namely a full snapshot creating state, the second state is used for identifying that the production volume is not in the process of creating the full snapshot, namely the full snapshot creating idle state, and the default value of the state of the full identification is the second state, namely the idle state. Specifically, if the state of the full identifier is the first state, that is, the state of the full identifier is the state during creation of the full snapshot, the storage device prohibits the creation operation of a new full snapshot on the production volume, that is, the storage device ensures that two or more full snapshots cannot be created together at the same time.
Optionally, in another shown embodiment, before the storage device creates the full snapshot corresponding to the production volume based on the space mapping table TB1, the storage device needs to obtain the full identifier of the production volume first. Specifically, if the state of the full identifier is the second state, that is, the state of the full identifier is the idle state created by the full snapshot, the state of the full identifier is updated from the second state to the first state, that is, the state of the full identifier is updated from the idle state created by the full snapshot to the state in the creation of the full snapshot; and meanwhile, the storage device creates a copy state record table corresponding to the space mapping table TB1 of the production volume, wherein the copy state record table is used for recording the copy state of copying the space mapping table to the full snapshot.
And 104, creating a full snapshot corresponding to the production volume based on the space mapping table.
In this application, as described in step 102 above, after the storage device obtains the space mapping table TB1 of the production volume, the storage device performs a process of creating a full snapshot corresponding to the production volume based on the space mapping table TB1, and as illustrated in fig. 2, the following steps are performed:
step 202, according to the copy state record table, gradually copying the TB1 to the full snapshot and storing the TB1 as TB2 according to the storage block unit of the space mapping table TB1 of the production volume.
Here, the copy status record table is created by the storage device as described in step 102, and the copy status record table may be created in various ways, such as: in a preferred mode, the copy status record table is implemented based on a bitmap file, wherein each bit in the bitmap file is used to mark whether a storage block with a preset length in the space mapping table has been copied, and possible values of each bit are as follows: the first type is used for marking that the storage blocks with preset length in the space mapping table corresponding to the bit are not copied, namely, are not copied for short, the second type is used for marking that the storage blocks with preset length in the space mapping table corresponding to the bit are copied, namely, are copied for short, and the default value of each bit is the first type, namely, the default value of each bit is not copied. And the storage equipment copies data in a storage block with a preset length corresponding to the bit in the space mapping table TB1 to a space mapping table TB2 correspondingly stored in the full snapshot based on each bit of the bitmap file corresponding to the copy state recording table, and updates the value of the bit from the first type to the second type, namely updates the type of the bit from the uncopyed state to the copied state.
Specifically, for example: the space mapping table TB1 of the production volume correspondingly occupies 1GB (Gigabyte) storage space, and the copy state recording table correspondingly marks based on a bitmap file, where each bit in the bitmap file is used to mark whether a storage block with a preset length of 256KB (Kilobyte) in the space mapping table is copied, so that the bitmap file requires 1 × 1024/256=4096 bits altogether, and the default value of each bit is not copied. The storage device traverses each bit in 4096 bits of the bitmap file corresponding to the copy state record table, copies data in a storage block with a preset length of 256KB corresponding to the bit in the space mapping table TB1 into the full snapshot, and updates the type of the bit from un-copied to copied until 1GB of storage data corresponding to the 4096 bits of the bitmap file are stored in the full snapshot, namely a space mapping table TB2 in the full snapshot is a complete copy of the space mapping table TB1 of the production volume at the corresponding creation time of the full snapshot.
And step 204, gradually updating the data correspondingly stored in the storage block corresponding to the TB1 according to the copy state record table and the storage block state corresponding to the space mapping table TB1 of the production volume.
When the storage device creates the full snapshot as described in step 202 above according to the copy status record table, the storage device may support updating the data in the space mapping table TB1 of the production volume.
Optionally, in an embodiment shown, if data D1 in a storage block of a preset length corresponding to one or more bits of the copy state record table in the space mapping table TB1 is to be updated to data D2, and the state of the one or more bits is of the second type, the storage device updates the corresponding data D1 in the space mapping table TB1 to data D2.
Specifically, the copy status record table is implemented based on a bitmap file, and if data D1 in a memory block with a preset length of 256KB corresponding to one or more bits of the bitmap file in the space mapping table TB1 is to be updated to data D2, the data D1 is expected to change to D2, for example: 3 bits in a bitmap file respectively correspond to 3 storage blocks with the size of 256KB, stored data in the 3 storage blocks are respectively A1, B1 and C1, when the stored data in the 3 storage blocks are respectively required to be updated to be A2, B2 and C2, a storage device respectively acquires the states of the 3 bits, if the states of the 3 bits are respectively copied, the storage device identifies that the storage block corresponding to the space mapping table TB1 corresponding to the 3 bits has been copied from the production volume to the full snapshot, and the storage device respectively updates the stored data A1, B1 and C1 in the space mapping table TB1 corresponding to the 3 bits to be A2, B2 and C2. The above procedure is only one possibility of example, and in fact there are many possibilities, such as: the states of the 3 bits may be partly copied and partly not copied, and the specific possible combination is not limited in the application, and the similar process is not described again.
Optionally, in another shown embodiment, if data D1 in a storage block of a preset length corresponding to one or more bits of the bitmap file in the space mapping table TB1 is to be updated to data D2, and the state of the one or more bits is of a first type, the storage device creates a mutual exclusion lock, where the mutual exclusion lock is used to prohibit updating of the data D1 to the data D2; the storage device copies data in a storage block with a preset length corresponding to one or more bits where the data D1 is located from the space mapping table to a space mapping table TB2 correspondingly stored in the full snapshot, and updates the state of the bits of the storage block with the preset length corresponding to the one or more bits where the data D1 is located in the copy state recording table to a second type; the storage device deletes the mutual exclusion lock, and is used for allowing the data D1 to be updated into the data D2; and updates the data D1 to the data D2.
Specifically, the copy status record table is implemented based on a bitmap file, and if data D1 in a memory block with a preset length of 256KB corresponding to one or more bits of the bitmap file in the space mapping table TB1 is to be updated to data D2, the data D1 is expected to change to D2, for example: 3 bits in a bitmap file correspond to 3 storage blocks with the size of 256KB respectively, the data stored in the 3 storage blocks are a11, B11 and C11 respectively, when the data stored in the 3 storage blocks need to be updated to a22, B22 and C22 respectively, the storage device obtains the states of the 3 bits respectively, if the states of the 3 bits are not copied, the storage device identifies that the storage blocks corresponding to the space mapping table TB1 corresponding to the 3 bits have not been copied from the production volume to the full snapshot, and the storage device creates 3 mutexes L1, L2 and L3 corresponding to the 3 storage blocks corresponding to the space mapping table TB1 corresponding to the 3 bits respectively, wherein the mutexes L1, L2 and L3 are used for prohibiting the storage data a11, B11 and C11 in the 3 storage blocks from being updated to a22, B22 and C22 respectively. After the storage device executes the process shown in step 202, copying the storage block corresponding to the space mapping table TB1 corresponding to the 3 bits from the production volume to the full snapshot; the storage device deletes the three mutexes L1, L2, and L3, that is, allows data to be updated, and updates the storage data a11, B11, and C11 corresponding to the 3 storage blocks in the space mapping table TB1 corresponding to the 3 bits to a22, B22, and C22, respectively. The above is only one possibility of example, and in fact there are many possibilities, such as: data in one or more 256KB sized memory blocks are updated, such as: the states of the 3 bits may be partly copied and partly not copied, and the specific possible combination is not limited in the application, and similar processes are not described in detail.
And step 206, updating the state of the full identifier corresponding to the production volume, and deleting the copy state record table.
Optionally, in an illustrated embodiment, after the storage device creates a full snapshot corresponding to the production volume based on the space mapping table, the storage device updates the state of the full identifier from a first state to a second state, and deletes the copy state record table.
Specifically, after the storage device creates the full snapshot corresponding to the production volume based on the space mapping table, the storage device updates the state of the full identifier from the state in the creation of the full snapshot to the state in the creation of the full snapshot, and deletes the copy state record table.
In the process of creating the full snapshot as described in steps 102 to 104, the storage device may generate a series of full snapshots at a certain period based on a preset snapshot policy; the storage equipment can also generate a series of incremental snapshots according to a certain period based on a preset snapshot strategy; the corresponding creation time of the full snapshot and the incremental snapshot has a certain time interval. Such as: the preset snapshot policy specifically includes: starting from 2018-09-01 00; snapshots are automatically created every 1 hour, with one full snapshot created every 12 hours and all other snapshots created at other times being incremental snapshots. According to the preset snapshot policy, it can be seen that the storage device creates at most 14 full snapshots and 154 incremental snapshots, and please refer to the following steps in the specific creation process of a series of snapshots:
a) At 2018-09-01 00.
b) At 2018-09-01 00, namely according to a preset snapshot strategy, from the start of creating the snapshot to the 1 st time when the interval 12 hours is reached, the storage device creates a1 st full snapshot, and then continues to create new incremental snapshots at the whole point of each hour.
c) Until 2018-09-0200, namely according to a preset snapshot strategy, when the interval of creating the full snapshot from the 1 st time reaches 12 hours, the storage device creates the 2 nd full snapshot.
d) The process similar to the above steps a to c is repeatedly executed until 168 snapshots have been created, that is, the number of snapshots created by the storage device reaches the maximum number of saved snapshots 168, and the storage device has created 14 full snapshots and 154 incremental snapshots. When a new snapshot is created subsequently, the method is implemented in the same manner as the prior art, that is, when the number of snapshots reaches the maximum number of snapshots, the oldest snapshot corresponding to the creation time is automatically deleted before the new snapshot is created, and then the new snapshot is created, which is not described in detail herein.
Based on the creation of the full snapshot, optionally, in an illustrated embodiment, when a user needs to rollback a snapshot, that is, when the production volume snapshot is triggered to rollback to a target snapshot, if the target snapshot is the full snapshot, the storage device obtains a space mapping table TB2 of the full snapshot; and covering the space mapping table TB1 of the production volume with TB2, and rolling back the production volume to the historical data at the corresponding moment of the target snapshot.
Specifically, for example: according to a preset snapshot strategy, when the production volume snapshot is rolled back to a target snapshot at the time 2018-09-02 00; and covering the space mapping table TB1 of the production volume with TB2, and rolling back the production volume to the corresponding history data at the 2018-09-0200. The target snapshot described above is only one possibility of example, and there are actually many possibilities, such as: the target snapshot is F1, and for another example: the target snapshot is F3, which may not be limited in this application, and similar processes are not described again.
Based on the creation of the full snapshot, optionally, in another embodiment shown, when a user needs to rollback the snapshot, that is, when the production volume snapshot is triggered to rollback to the target snapshot, if the target snapshot is an incremental snapshot, the storage device obtains the full snapshot closest to the creation time after the creation time of the target snapshot and other incremental snapshots between the target snapshot and the full snapshot within the creation time; rolling back the production volume to historical data at a corresponding moment of the full snapshot; and rolling back the production volume to historical data of the target snapshot at the corresponding moment according to the creation time of the other incremental snapshots from new to old.
Specifically, for example: according to a preset snapshot strategy, when a plurality of times 2018-09-0112 exist in a production volume, the following total snapshots of; snapshots existing every hour between every two full snapshots are incremental snapshots; when the production volume snapshot is triggered to roll back to the target snapshot at time 2018-09-02 08, the storage device checks that the target snapshot A8 at time 2018-09-02 08 is an incremental snapshot, then the storage device acquires the most recent full snapshot after the target snapshot A8 creation time 2018-09-0200 is F33 and other incremental snapshots within 2018-09-02 00; the storage device firstly obtains a space mapping table TB33 in the full snapshot F33; covering a space mapping table TB1 of the production volume with TB33, and rolling back the production volume to corresponding historical data at the 2018-09-02 time of the 2018; then, the storage device rolls back the incremental snapshot corresponding to the time 2018-09-0211 from new to old according to the creation time of the plurality of incremental snapshots, namely rolls back the incremental snapshot corresponding to the time 2018-09-0211, then rolls back the incremental snapshot corresponding to the time 2018-09-02 10.
To this end, the process shown in fig. 1 is completed, and as can be seen from the process shown in fig. 1, a storage device enables a write redirection snapshot mode for a production volume and has a snapshot policy in advance, and creates a series of snapshots for the production volume according to the snapshot policy, where the types of the snapshots include: incremental snapshot, full snapshot; acquiring a space mapping table of the production volume, wherein the space mapping table is used for recording storage mapping information of data in the production volume; and creating a full snapshot corresponding to the production volume based on the space mapping table.
By applying the embodiment of the application, the full snapshot or the full snapshot is matched with the incremental snapshot, so that the incremental snapshot only depends on the closest full snapshot in the creation time after the creation time of the incremental snapshot and other incremental snapshots in the creation time of the incremental snapshot and the full snapshot, and does not have a dependency relationship with other incremental snapshots or full snapshots after the full snapshot, on one hand, the dependency among a plurality of incremental snapshots is reduced, and the data security of the snapshot is improved; on the other hand, the snapshot rollback does not relate to all snapshots after the full snapshot, so that the time required by the snapshot rollback is reduced, and the efficiency of the snapshot rollback is improved.
Fig. 3 is a block diagram of a snapshot creation apparatus according to an exemplary embodiment of the present application. Corresponding to the above method embodiment, the present application further provides an embodiment of a snapshot creating apparatus, where a snapshot mode of write redirection is enabled for a production volume and a snapshot policy is preset, and a series of snapshots are created for the production volume according to the snapshot policy, where the types of the snapshots include: incremental snapshot, full snapshot, please refer to a snapshot creation apparatus 30 illustrated in fig. 3, which includes:
an obtaining module 301, configured to obtain a space mapping table of the production volume, where the space mapping table is used to record storage mapping information of data in the production volume;
a creating module 302, configured to create a full snapshot corresponding to the production volume based on the space mapping table.
In this embodiment, before the obtaining the space mapping table of the production volume, the creating module 302 further includes:
acquiring a full identifier of the production volume, wherein the full identifier is used for marking whether the production volume is in a state of creating a full snapshot, and the possible values of the state of the full identifier include: a first state or a second state, the state default value of the full identity being the second state;
and if the state of the full identity is the first state, forbidding the creation operation of the new full snapshot.
In this embodiment, before creating the full-volume snapshot corresponding to the production volume based on the space mapping table, the creating module 302 further includes:
if the state of the full identifier is the second state, updating the state of the full identifier to be the first state;
and creating a copy state record table corresponding to the space mapping table of the production volume, wherein the copy state record table is used for recording the copy state of copying the space mapping table to the full snapshot.
In this embodiment, after the creating a full snapshot corresponding to the production volume based on the space mapping table, the creating module 302 further includes:
and updating the state of the full identifier from a first state to a second state, and deleting the copy state record table.
In this embodiment, the copy status record table is based on a bitmap, where each bit in the bitmap is used to mark whether a storage block with a preset length in the space mapping table has been copied, and possible values of each bit are: the default value of each bit is the first type; the creating of the full snapshot corresponding to the production volume based on the space mapping table includes:
the creating module 302 copies data in a storage block with a preset length corresponding to the bit in the space mapping table TB1 to a space mapping table TB2 correspondingly stored in the full snapshot based on each bit of the bitmap, and updates the value of the bit from a first type to a second type.
In this embodiment, the creating module 302 further includes:
and if the data D1 in the storage block with the preset length corresponding to one or more bits of the copy state recording table in the space mapping table TB1 is to be updated to be the data D2 and the state of the one or more bits is of a second type, updating the corresponding data D1 in the space mapping table TB1 to be the data D2.
In this embodiment, the creating module 302 further includes:
if data D1 in a storage block with a preset length corresponding to one or more bits of the copy state record table in the space mapping table TB1 is to be updated to be data D2, and the state of the one or more bits is of a first type, creating a mutual exclusion lock, wherein the mutual exclusion lock is used for forbidding updating of the data D1 to be the data D2;
copying data in a storage block with preset length corresponding to one or more bits where the data D1 is located from the space mapping table to a space mapping table TB2 correspondingly stored in the full snapshot, and updating the state of the bits of the storage block with the preset length corresponding to the one or more bits where the data D1 is located in the copy state recording table to be a second type;
deleting the mutual exclusion lock, wherein the mutual exclusion lock is used for allowing the data D1 to be updated into the data D2; and updates the data D1 to the data D2.
In this embodiment, when triggering the production volume snapshot to roll back to the target snapshot, the method further includes:
a rollback module 303, configured to obtain a space mapping table TB2 of the full snapshot if the target snapshot is the full snapshot;
the rollback module 303 covers the space mapping table TB1 of the production volume with TB2, and rolls back the production volume to the historical data at the time corresponding to the target snapshot.
In this embodiment, when triggering the production volume snapshot to roll back to the target snapshot, the roll-back module 303 further includes:
if the target snapshot is an incremental snapshot, acquiring a most recent full snapshot after the creation time of the target snapshot and other incremental snapshots between the target snapshot and the full snapshot creation time;
rolling back the production volume to historical data at a moment corresponding to the full snapshot;
and rolling back the production volume to historical data of the target snapshot at the corresponding moment according to the creation time of the other incremental snapshots from new to old.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the modules described as separate components may or may not be physically separate, and the components displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
The systems, devices, modules or modules illustrated in the above embodiments may be implemented by a computer chip or an entity, or by an article of manufacture with certain functionality. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
The embodiment of the snapshot creation apparatus of the present application may be applied to the electronic device shown in fig. 4. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. Taking a software implementation as an example, as a logical device, the device is a machine executable instruction formed by reading a corresponding computer program instruction in a machine readable storage medium through a processor of the electronic device where the device is located and then running the computer program instruction. From a hardware aspect, as shown in fig. 4, a hardware structure diagram of an electronic device in which a snapshot creating apparatus of the present application is located is shown, except for the processor, the communication interface, the bus, and the machine-readable storage medium shown in fig. 4, the electronic device in which the apparatus is located in the embodiment may also include other hardware according to an actual function of the electronic device, which is not described again.
Correspondingly, an embodiment of the present application further provides a hardware structure of an electronic device of the apparatus shown in fig. 3, please refer to fig. 4, and fig. 4 is a schematic diagram of the hardware structure of the electronic device provided in the embodiment of the present application. The apparatus comprises: a communication interface 401, a processor 402, a machine-readable storage medium 403, and a bus 404; the communication interface 401, the processor 402, and the machine-readable storage medium 403 are all configured to communicate with each other via a bus 404. The communication interface 401 is used for performing network communication. The processor 402 may be a Central Processing Unit (CPU), and the processor 402 may execute machine-readable instructions stored in a machine-readable storage medium 403 to implement the methods described above.
The machine-readable storage medium 403 referred to herein may be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and the like. For example, the machine-readable storage medium may be: volatile memory, non-volatile memory, or similar storage media. In particular, the machine-readable storage medium 403 may be a RAM (random Access Memory), a flash Memory, a storage drive (e.g., a hard disk drive), a solid state disk, any type of storage disk (e.g., a compact disk, a DVD, etc.), or similar storage medium, or a combination thereof.
Up to this point, the description of the hardware configuration shown in fig. 4 is completed.
Further, embodiments of the present application also provide a machine-readable storage medium, such as machine-readable storage medium 403 in fig. 4, comprising machine-executable instructions, which are executable by processor 402 in a data processing apparatus to implement the above-described method.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.
The above description is only a preferred embodiment of the present application and should not be taken as limiting the present application, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present application should be included in the protection scope of the present application.
Claims (20)
1. A method for creating a snapshot is characterized in that a write redirection snapshot mode is enabled for a production volume, a snapshot strategy is preset, a series of snapshots with snapshot types of full volume snapshots and a plurality of incremental snapshots arranged at intervals are created for the production volume according to the snapshot strategy, the full volume snapshot refers to copying a space mapping table of the production volume which produces the snapshot and corresponds to the creation time as management data of the snapshot at the creation time of any snapshot, and the method comprises the following steps:
acquiring a space mapping table of the production volume; wherein the space mapping table is used for recording the storage mapping information of the data in the production volume,
and creating a full snapshot corresponding to the production volume based on the space mapping table.
2. The method according to claim 1, further comprising, before said obtaining the space map table of the production volume:
acquiring a full identifier of the production volume, wherein the full identifier is used for marking whether the production volume is in a state of creating a full snapshot, and the possible values of the state of the full identifier include: a first state or a second state, the state default value of the full identity being the second state;
and if the state of the full identity is the first state, forbidding the creation operation of a new full snapshot.
3. The method of claim 2, further comprising, prior to said creating a full snapshot corresponding to said production volume based on said space map table:
if the state of the full identifier is the second state, updating the state of the full identifier to be the first state;
and creating a copy state record table corresponding to the space mapping table of the production volume, wherein the copy state record table is used for recording the copy state of copying the space mapping table to the full snapshot.
4. The method according to claim 3, further comprising, after said creating a full volume snapshot corresponding to said production volume based on said space mapping table:
and updating the state of the full identifier from a first state to a second state, and deleting the copy state record table.
5. The method according to claim 4, wherein the copy status record table is based on a bitmap, wherein each bit in the bitmap is used to mark whether a storage block with a preset length in the space mapping table has been copied, and possible values of each bit are: the default value of each bit is the first type; the creating of the full snapshot corresponding to the production volume based on the space mapping table includes:
based on each bit of the bitmap, copying data in a storage block with a preset length corresponding to the bit in the space mapping table TB1 into a space mapping table TB2 correspondingly stored in the full snapshot, and updating the value of the bit from a first type to a second type.
6. The method of claim 5, further comprising:
and if the data D1 in the storage block with the preset length corresponding to one or more bits of the copy state recording table in the space mapping table TB1 is to be updated to be the data D2 and the state of the one or more bits is of a second type, updating the corresponding data D1 in the space mapping table TB1 to be the data D2.
7. The method of claim 6, further comprising:
if data D1 in a storage block with a preset length corresponding to one or more bits of the copy state record table in the space mapping table TB1 is to be updated to be data D2, and the state of the one or more bits is of a first type, creating a mutual exclusion lock, wherein the mutual exclusion lock is used for forbidding updating of the data D1 to be the data D2;
copying data in a storage block with a preset length corresponding to one or more bits where the data D1 is located from the space mapping table to a space mapping table TB2 correspondingly stored in the full snapshot, and updating the state of the bits of the storage block with the preset length corresponding to the one or more bits where the data D1 is located in the copy state recording table to be of a second type;
deleting the mutual exclusion lock, wherein the mutual exclusion lock is used for allowing the data D1 to be updated into the data D2; and updates the data D1 to the data D2.
8. The method of claim 7, wherein when triggering the production volume snapshot to roll back to a target snapshot, further comprising:
if the target snapshot is a full snapshot, acquiring a space mapping table TB2 of the full snapshot;
and covering the space mapping table TB1 of the production volume with TB2, and rolling back the production volume to the historical data at the corresponding moment of the target snapshot.
9. The method of claim 7, when triggering the roll-back of the production volume snapshot to a target snapshot, further comprising:
if the target snapshot is an incremental snapshot, acquiring a most recent full snapshot after the creation time of the target snapshot and other incremental snapshots between the target snapshot and the full snapshot creation time;
rolling back the production volume to historical data at a moment corresponding to the full snapshot;
and rolling back the production volume to historical data of the target snapshot at the corresponding moment according to the creation time of the other incremental snapshots from new to old.
10. A snapshot creating device is characterized in that a write redirection snapshot mode is enabled for a production volume, a snapshot strategy is preset, a series of snapshots with snapshot types of full snapshots and a plurality of incremental snapshots arranged at intervals are created for the production volume according to the snapshot strategy, the full snapshots refer to the fact that at the time of creating any snapshot, a space mapping table of the production volume producing the snapshot corresponding to the time of creating the snapshot is copied to serve as management data of the snapshot, and the device comprises:
the acquisition module is used for acquiring a space mapping table of the production volume, wherein the space mapping table is used for recording storage mapping information of data in the production volume;
and the creating module is used for creating the full snapshot corresponding to the production volume based on the space mapping table.
11. The apparatus of claim 10, wherein before the obtaining the space map table for the production volume, the creating module further comprises:
acquiring a full identifier of the production volume, wherein the full identifier is used for marking whether the production volume is in a state of creating a full snapshot, and the possible values of the state of the full identifier include: a first state or a second state, the state default value of the full identity being the second state;
and if the state of the full identity is the first state, forbidding the creation operation of a new full snapshot.
12. The apparatus according to claim 11, wherein before the creating a full snapshot corresponding to the production volume based on the space map, the creating module further comprises:
if the state of the full identifier is the second state, updating the state of the full identifier to be the first state;
and creating a copy state record table corresponding to the space mapping table of the production volume, wherein the copy state record table is used for recording the copy state of copying the space mapping table to the full snapshot.
13. The apparatus according to claim 12, wherein after the creating a full snapshot corresponding to the production volume based on the space mapping table, the creating module further comprises:
and updating the state of the full identifier from a first state to a second state, and deleting the copy state record table.
14. The apparatus according to claim 13, wherein the copy status record table is based on a bitmap, wherein each bit in the bitmap is used to mark whether a storage block with a preset length in the space mapping table has been copied, and possible values of each bit are: the default value of each bit is the first type; the creating a full snapshot corresponding to the production volume based on the space mapping table includes:
and the creating module copies data in a storage block with a preset length corresponding to the bit in the space mapping table TB1 to a space mapping table TB2 correspondingly stored in the full snapshot based on each bit of the bitmap, and updates the value of the bit from the first type to the second type.
15. The apparatus of claim 14, wherein the creation module further comprises:
and if the data D1 in the storage block with the preset length corresponding to one or more bits of the copy state recording table in the space mapping table TB1 is to be updated to be the data D2 and the state of the one or more bits is of a second type, updating the corresponding data D1 in the space mapping table TB1 to be the data D2.
16. The apparatus of claim 15, wherein the creation module further comprises:
if data D1 in a storage block with a preset length corresponding to one or more bits of the copy state record table in the space mapping table TB1 is to be updated to be data D2, and the state of the one or more bits is of a first type, creating a mutual exclusion lock, wherein the mutual exclusion lock is used for forbidding updating of the data D1 to be the data D2;
copying data in a storage block with preset length corresponding to one or more bits where the data D1 is located from the space mapping table to a space mapping table TB2 correspondingly stored in the full snapshot, and updating the state of the bits of the storage block with the preset length corresponding to the one or more bits where the data D1 is located in the copy state recording table to be a second type;
deleting the mutual exclusion lock, wherein the mutual exclusion lock is used for allowing the data D1 to be updated into the data D2; and updates the data D1 to the data D2.
17. The apparatus of claim 16, when triggering the roll-back of the production volume snapshot to a target snapshot, further comprising:
the rollback module is used for acquiring a space mapping table TB2 of the full snapshot if the target snapshot is the full snapshot;
and the rollback module is used for covering the space mapping table TB1 of the production volume with TB2 and rolling back the production volume to the historical data of the target snapshot at the corresponding moment.
18. The apparatus of claim 17, wherein when triggering the production volume snapshot to roll back to a target snapshot, the roll-back module further comprises:
if the target snapshot is an incremental snapshot, acquiring a most recent full snapshot after the creation time of the target snapshot and other incremental snapshots between the target snapshot and the full snapshot creation time;
rolling back the production volume to historical data at a moment corresponding to the full snapshot;
and rolling back the production volume to historical data of the target snapshot at the corresponding moment according to the creation time of the other incremental snapshots from new to old.
19. An electronic device is characterized by comprising a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are connected with each other through the bus;
the memory has stored therein machine-readable instructions, which the processor executes by calling the processor to perform the method of any one of claims 1 to 9.
20. A machine-readable storage medium having stored thereon machine-readable instructions which, when invoked and executed by a processor, carry out the method of any of claims 1 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811574817.4A CN109614055B (en) | 2018-12-21 | 2018-12-21 | Snapshot creating method and device, electronic equipment and machine-readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811574817.4A CN109614055B (en) | 2018-12-21 | 2018-12-21 | Snapshot creating method and device, electronic equipment and machine-readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109614055A CN109614055A (en) | 2019-04-12 |
| CN109614055B true CN109614055B (en) | 2022-11-04 |
Family
ID=66010450
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811574817.4A Active CN109614055B (en) | 2018-12-21 | 2018-12-21 | Snapshot creating method and device, electronic equipment and machine-readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109614055B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110658993A (en) * | 2019-08-29 | 2020-01-07 | 北京浪潮数据技术有限公司 | Snapshot rollback method, device, equipment and storage medium |
| CN110704239B (en) * | 2019-09-03 | 2022-05-27 | 杭州宏杉科技股份有限公司 | Data copying method and device and electronic equipment |
| CN111090400B (en) * | 2019-12-29 | 2022-03-22 | 浪潮(北京)电子信息产业有限公司 | Method, device and equipment for automatically rolling back snapshot |
| CN113238857B (en) * | 2021-04-21 | 2022-10-14 | 宜通世纪物联网研究院(广州)有限公司 | Map mapping table multithreading traversal method and device based on memory pool |
| CN113448774B (en) * | 2021-06-04 | 2023-01-24 | 山东英信计算机技术有限公司 | Method, system, device and medium for optimizing copy-on-write storage snapshot management |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009009979A1 (en) * | 2007-07-18 | 2009-01-22 | Huawei Technologies Co., Ltd. | Snapshot protecting method and apparatus |
| WO2017113059A1 (en) * | 2015-12-28 | 2017-07-06 | 华为技术有限公司 | Discrepant data backup method, storage system and discrepant data backup device |
Family Cites Families (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101256528B (en) * | 2008-03-20 | 2010-07-28 | 中国科学院计算技术研究所 | Magnetic disk data backup system and method supporting nought backup window |
| CN101295276B (en) * | 2008-06-20 | 2010-06-09 | 中国科学院计算技术研究所 | Magnetic disk data backup system and method |
| CN101419564B (en) * | 2008-12-11 | 2010-08-25 | 杭州华三通信技术有限公司 | Method and device for recovering data by employing snapshot |
| US9565002B2 (en) * | 2012-10-06 | 2017-02-07 | Telefonaktiebolaget L M Ericsson | CRS interference mitigation for EPDCCH/PDSCH demodulation under CoMP |
| CN103019888B (en) * | 2012-12-21 | 2016-03-30 | 华为技术有限公司 | Backup method and device |
| CN105242987B (en) * | 2015-09-22 | 2018-09-07 | 浪潮(北京)电子信息产业有限公司 | A kind of disaster recovery method of snapshot extending, apparatus and system |
| CN105224422B (en) * | 2015-10-20 | 2019-02-12 | 浙江大华技术股份有限公司 | A kind of data back up method and equipment |
| CN107179964A (en) * | 2016-03-11 | 2017-09-19 | 中兴通讯股份有限公司 | The reading/writing method and device of snapshot |
| CN106126371A (en) * | 2016-06-15 | 2016-11-16 | 腾讯科技（深圳）有限公司 | Data return a grade method, Apparatus and system |
| CN106777219B (en) * | 2016-12-23 | 2020-03-03 | 北京亚细亚智业科技有限公司 | Data processing method and device for virtualized data center |
| CN106776147B (en) * | 2016-12-29 | 2020-10-09 | 华为技术有限公司 | Differential data backup method and differential data backup device |
| CN107943557B (en) * | 2017-11-18 | 2020-07-17 | 浙江网新恒天软件有限公司 | Virtual machine disk incremental snapshot method based on cloud platform |
| CN109032507B (en) * | 2018-06-28 | 2021-11-19 | 郑州云海信息技术有限公司 | Method, system and related assembly for generating source volume storage snapshot |
-
2018
- 2018-12-21 CN CN201811574817.4A patent/CN109614055B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009009979A1 (en) * | 2007-07-18 | 2009-01-22 | Huawei Technologies Co., Ltd. | Snapshot protecting method and apparatus |
| WO2017113059A1 (en) * | 2015-12-28 | 2017-07-06 | 华为技术有限公司 | Discrepant data backup method, storage system and discrepant data backup device |
Non-Patent Citations (2)
| Title |
|---|
| 一种远程备份数据虚拟重构方法;张也等;《四川大学学报(自然科学版)》;20150928(第05期);第1014-1020页 * |
| 一种迭代式快照系统的设计与实现;刘振军等;《计算机工程与应用》;20060511(第14期);第11-15页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109614055A (en) | 2019-04-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109614055B (en) | Snapshot creating method and device, electronic equipment and machine-readable storage medium | |
| CN109902034B (en) | Snapshot creating method and device, electronic equipment and machine-readable storage medium | |
| CN109684271B (en) | Snapshot data management method and device, electronic equipment and machine-readable storage medium | |
| CN106357703B (en) | Cluster switching method and device | |
| US11640244B2 (en) | Intelligent block deallocation verification | |
| CN109496292A (en) | A kind of disk management method, disk management device and electronic equipment | |
| CN111666046B (en) | Data storage method, device and equipment | |
| KR101738965B1 (en) | Apparatus and method for journaling based on garbage collection | |
| CN106709014B (en) | File system conversion method and device | |
| CN109753381B (en) | Continuous data protection method based on object storage | |
| CN111427514B (en) | View migration method and device | |
| CN110531925B (en) | Data reading method and device, electronic equipment and machine-readable storage medium | |
| US11726668B2 (en) | Device with flash memory and method for writing/erasing/updating data in flash memory thereof | |
| CN109960611B (en) | Data recovery method and device, electronic equipment and machine-readable storage medium | |
| WO2005041050A1 (en) | Recording medium, data processing apparatus, and data processing method | |
| CN110795031A (en) | Data deduplication method, device and system based on full flash storage | |
| CN115328851A (en) | Data protection method, device, equipment and medium | |
| CN115421856A (en) | Data recovery method and device | |
| CN114792016A (en) | Processing method and electronic equipment | |
| CN113626089A (en) | Data operation method, system, medium and equipment based on BIOS system | |
| CN113467698A (en) | Writing method and device based on file system, computer equipment and storage medium | |
| CN111625500A (en) | File snapshot method and device, electronic equipment and storage medium | |
| JP2003150321A (en) | Device, method and program for managing virtual storage device, and computer readable recording medium recorded with virtual storage device | |
| CN114880277B (en) | Block device snapshot method, system and storage medium | |
| CN111435331A (en) | Data writing method and device for storage volume, electronic equipment and machine-readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |