CN114442941B - Data migration method, system, storage medium and equipment - Google Patents
Data migration method, system, storage medium and equipment Download PDFInfo
- Publication number
- CN114442941B CN114442941B CN202210006146.1A CN202210006146A CN114442941B CN 114442941 B CN114442941 B CN 114442941B CN 202210006146 A CN202210006146 A CN 202210006146A CN 114442941 B CN114442941 B CN 114442941B
- Authority
- CN
- China
- Prior art keywords
- lun
- data
- storage device
- synchronization service
- data synchronization
- 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/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/0647—Migration mechanisms
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- 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/061—Improving I/O performance
- G06F3/0611—Improving I/O performance in relation to response time
-
- 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/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/0671—In-line storage system
- G06F3/0683—Plurality of storage devices
- G06F3/0689—Disk arrays, e.g. RAID, JBOD
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Quality & Reliability (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Signal Processing For Digital Recording And Reproducing (AREA)
Abstract
The application provides a data migration method, a system, a storage medium and a device, wherein after a first storage device determines that data of a third LUN changes on other storage devices, a data change bitmap of the first storage device is synchronized to data synchronization services of the first LUN to the third LUN, and data increment of the first LUN is synchronized to the third LUN, so that a data change identifier and the data change bitmap are updated; the second storage device senses the data change of the third LUN through the data change identification and the data change bitmap of the third LUN, synchronizes the data change bitmap of the third LUN to the data synchronization service from the third LUN to the second LUN, synchronizes the data increment of the third LUN to the second LUN, and updates the data change identification and the data change bitmap of the third LUN when the third LUN processes the write command, so that the data change of the third LUN is sensed when the third LUN is imported into other storage devices, the operation complexity in the migration process is reduced, the migration time is shortened, and the migration efficiency is improved.
Description
Technical Field
The present disclosure relates to the field of data storage technologies, and in particular, to a data migration method, system, storage medium, and device.
Background
With the advent of the big data age, the data volume is becoming larger and more important, and data migration and backup across devices are becoming a common requirement. In a typical implementation, data is frequently migrated between the data center S1 and the data center S2 through a network, but if the network between the data center S1 and the data center S2 is not enabled due to security factors, the data cannot be migrated by using the existing data synchronization service (such as replication, mirroring, copying, etc.), and based on this, how to frequently migrate data across devices is regarded as an important research content under the condition that network communication is not available.
At present, an alternative solution is proposed to use the disk as a usb disk, and it is assumed that data needs to be migrated from LUN1 (Logical Unit Number ) of data center S1 to LUN2 of data center S2, which is specifically implemented as follows: LUN3 is created in the data center S1, data synchronization service is configured, the total data in the LUN1 is synchronized into the LUN3, and related service is forbidden after data synchronization is completed, so that the LUN3 is exported. When LUN3 is imported into the data center S2, a data synchronization service needs to be configured, and after the data in LUN3 is completely synchronized to LUN2, related services need to be disabled, and LUN3 needs to be exported. After LUN3 is imported to data center S1, the above-described step of configuring data synchronization service is performed again at the next data migration, and full-scale synchronization is performed. It can be seen that, whether the data of LUN1 is synchronized into LUN3 in data center S1 or the data of LUN3 is synchronized into LUN2 in data center S2, the repeated configuration and disabling of the data synchronization service are required to be configured in data center S1 and data center S2, and the full synchronization is performed in both data center S1 and data center S2 to synchronize all the data, which makes the migration process complicated in operation, long in migration time, and low in migration efficiency.
Disclosure of Invention
The application provides a data migration method, a data migration system, a storage medium and a storage device, so as to improve data migration efficiency.
The technical scheme that this application provided includes:
in a first aspect, an embodiment of the present application provides a data migration method, where the method includes:
when a first storage device imports a third LUN belonging to other storage devices to the first storage device, after determining that the third LUN has data synchronization service belonging to the first storage device and data synchronization service belonging to other storage devices, if the data change identifier of the third LUN is detected to be a second identifier value, synchronizing a data change bitmap of the third LUN to the data synchronization service from the first LUN to the third LUN, initializing the data change bitmap of the third LUN, and changing the changed data identifier of the third LUN to the first identifier value; synchronizing the data increment of the first LUN into the third LUN according to the configured data synchronization business from the first LUN to the third LUN, changing the data change mark of the third LUN into a second mark value, and updating the data change bitmap of the third LUN; the first LUN is designated for producing the data volume, the third LUN is designated for moving the data volume, the first identification value is used for indicating that the data is unchanged, the second identification value is used for indicating that the data is changed, and the data change bitmap is used for recording the data change condition;
When the second storage device imports the third LUN belonging to the other storage devices to the second storage device, after determining that the third LUN has the data synchronization service belonging to the second storage device and the data synchronization service belonging to the other storage devices, if the data change identifier of the third LUN is detected to be the second identifier value, synchronizing the data change bitmap of the third LUN to the data synchronization service from the third LUN to the second LUN, changing the data change identifier of the third LUN to be the first identifier value according to the configured data synchronization service from the third LUN to the second LUN, and initializing the data change bitmap of the third LUN; when a write command is processed by a third LUN, changing a data change mark of the third LUN into a second mark value, and updating a data change bitmap; the data increment of the third LUN is synchronized into the second LUN; the second LUN is designated for storing a data copy of the production data volume.
In a second aspect, embodiments of the present application provide a data migration system, where the system includes at least a first storage device and a second storage device;
the first storage device is configured to, when a third LUN belonging to another storage device is imported to the first storage device, determine that the third LUN has a data synchronization service belonging to the first storage device and a data synchronization service belonging to another storage device, if it is detected that a data change identifier of the third LUN is a second identifier value, synchronize a data change bitmap of the third LUN to a data synchronization service from the first LUN to the third LUN, initialize the data change bitmap of the third LUN, and change the change data identifier of the third LUN to a first identifier value; synchronizing the data increment of the first LUN into the third LUN according to the configured data synchronization business from the first LUN to the third LUN, changing the data change mark of the third LUN into a second mark value, and updating the data change bitmap of the third LUN; the first LUN is designated for producing the data volume, the third LUN is designated for moving the data volume, the first identification value is used for indicating that the data is unchanged, the second identification value is used for indicating that the data is changed, and the data change bitmap is used for recording the data change condition;
The second storage device is configured to, when the third LUN belonging to the other storage device is imported to the second storage device, determine that the third LUN has a data synchronization service belonging to the second storage device and a data synchronization service belonging to the other storage device, and if it is detected that the data change identifier of the third LUN is a second identifier value, synchronize the data change bitmap of the third LUN to the data synchronization service from the third LUN to the second LUN, change the data change identifier of the third LUN to the first identifier value, and initialize the data change bitmap of the third LUN; when a write command is processed by a third LUN, changing a data change mark of the third LUN into a second mark value, and updating a data change bitmap; synchronizing the data increment of the third LUN into the second LUN according to the configured data synchronization business from the third LUN to the second LUN; the second LUN is designated for storing a data copy of the production data volume.
According to the technical scheme, in the application, the first storage device determines whether the data of the third LUN changes or not through the data change identification of the third LUN, namely, whether the data of the third LUN is written into other storage devices or not, and synchronizes the data change bitmap of the third LUN to the data synchronization service of the first LUN to the third LUN according to the data change identification representing the data changes, so that the first storage device can sense the data changes of the third LUN on other storage devices, and change the data change identification of the third LUN to be a first identification value, initialize the data change bitmap of the third LUN, and synchronize the data increment of the first LUN into the third LUN according to the configured data synchronization service, and update the data change identification and the data change bitmap of the third LUN; the second storage device perceives the data change of the third LUN on other storage devices through the data change identification and the data change bitmap of the third LUN, synchronizes the data change bitmap of the third LUN to the data synchronization service from the third LUN to the second LUN, changes the data change identification of the third LUN to be a first identification value, initializes the data change bitmap of the third LUN, changes the data change identification of the third LUN to be a second identification value when the third LUN processes a write command, updates the data change bitmap so as to be perceived as to change the data when the third LUN is imported into other storage devices, and synchronizes the data increment of the third LUN to the second LUN according to the configured data synchronization service. In this way, in the process of migrating data, the data synchronization service is not required to be repeatedly configured and disabled on the first storage device and the second storage device, and the data increment synchronization can be performed according to the data change bitmap and the data change identifier. By applying the migration method provided by the embodiment of the application, the operation complexity in the migration process can be reduced, the migration time is shortened, and the migration efficiency is improved.
Drawings
FIG. 1 is a flow chart of a data migration method provided in the present application;
FIG. 2 is a flow chart of implementing step 101 provided herein;
FIG. 3 is a flow chart of an implementation step 102 provided herein;
FIG. 4 is a schematic diagram of a data migration system according to the present disclosure;
fig. 5 is a schematic structural diagram of an electronic device provided in the present application.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the accompanying claims.
The terminology used in the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the present 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 or all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, a first message may also be referred to as a second message, and similarly, a second message may also be referred to as a first message, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.
Referring to fig. 1, fig. 1 is a flowchart of a data migration method provided in the present application, where the method includes:
The first LUN and the third LUN are located on different disks of the first storage device, that is, the disk storing the first LUN does not store the third LUN, and the disk storing the third LUN does not store the first LUN.
The first storage device is named for convenience of distinction from the following devices and is not intended to limit a certain storage device.
The first storage device is used to configure data synchronization traffic for the LUN, which may include copy traffic, mirror traffic, copy traffic, or the like.
The LUN refers to an independent available storage space created based on RAID (Redundant Arrays of Independent Disks, disk array) and is generally used for writing data of a front-end application server, in the embodiment of the present invention, the first LUN and the third LUN do not refer to any two fixed LUNs, but may refer to any two LUNs for storing data, which will not be described later in the embodiment of the present invention.
In this embodiment, a first LUN is created in the first storage device, designated for producing the data volume, and a third LUN may be created in the first storage device, designated for moving the data volume when initially used for moving the data volume.
In this embodiment, the first identification value and the second identification value do not refer to any two fixed identification values, but may refer to any two identification values on the LUN, which will not be described later.
The first identification value is merely named for convenience of distinction from the following identification values and is not intended to limit a certain device.
In this embodiment, a data change identifier may be set on each LUN, where the data change identifier may include an initial identifier value, a first identifier value and a second identifier value, where the initial identifier value indicates that the identifier is invalid, and no attention is paid to the condition of the identifier and the data change, and a "0" identifier may be used, and the first identifier value is used to indicate that the data is not changed, a "1" identifier may be used, and the second identifier value is used to indicate that the data is changed, and a "2" identifier may be used.
The data change bitmap is used to record the data change condition of the LUN. The storage space of the LUN is divided into a plurality of storage blocks according to a preset size, each storage block corresponds to 1 bit in the data change bitmap, if a certain bit value is 0, the data of the storage block corresponding to the bit value is unchanged, and if the bit value is 1, the data of the storage block corresponding to the bit value is changed.
Exemplary:
when the first LUN and the third LUN are created on the first storage device, the data change marks of the first LUN and the third LUN are set to an initial mark value, if the initial mark value is 0, a data change bitmap is not created.
When the second LUN is created on the second storage device, the data change identifier of the second LUN is set to an initial identifier value, such as an initial identifier value 0, and no data change bitmap is created.
In this embodiment, when processing a write command for each LUN, if the data change identifier of the LUN is the initial identifier value, no special processing is performed, otherwise, if the data change identifier of the LUN is the first identifier value, the data change identifier is modified to be the second identifier value, and the bit value corresponding to the storage block corresponding to the write command in the data change bitmap is modified to be 1; if the data change identifier of the LUN is the second identifier value, the bit value corresponding to the storage block corresponding to the write command in the change data change bitmap is 1.
In this embodiment, the data synchronization traffic of the first LUN to the third LUN has been configured in the first storage device, and the initial data synchronization has been completed. In the initial synchronization process, the data change identifier of the third LUN is the initial identifier value, so that the data change identifier and the data change bitmap of the third LUN do not need to be updated.
When the first storage device imports the third LUN, that is, after the third LUN has been imported into other storage devices, the first storage device returns to the first storage device, the data change condition can be perceived according to the data change identifier and the data change bitmap of the third LUN, and if the data change identifier is the second identifier value, the data change condition of the third LUN can be obtained through the data change bitmap. In this step, the data change bitmap of the third LUN is synchronized to the data synchronization traffic of the first LUN to the third LUN, so that the first LUN can perceive the difference, taking the copy traffic as an example, the first LUN is used as a source LUN of the copy traffic, the data change condition on the first LUN is recorded through the difference bitmap, and when the data change bitmap of the third LUN is synchronized to the copy traffic of the first LUN to the third LUN, the data change bitmap of the third LUN is merged to the difference bitmap of the first LUN, so that the merged difference bitmap of the first LUN contains the data change bitmap of the third LUN.
Because the third LUN also has a data synchronization service belonging to other storage devices, that is, the other storage devices care about the data change condition of the third LUN on the first storage device, after synchronizing the data change bitmap of the third LUN to the data synchronization services of the first LUN to the third LUN, the data change bitmap of the third LUN needs to be initialized, and the data change identifier of the third LUN is changed to the first identifier value, so that the data change condition of the third LUN on the first storage device can be marked by the data change identifier of the third LUN and the data change bitmap.
When the first storage device synchronizes the data increment of the first LUN to the third LUN according to the configured data synchronization service from the first LUN to the third LUN, on one hand, taking the replication service as an example, when the replication task from the first LUN to the third LUN is started for the first time, the difference data can be synchronized from the first LUN to the third LUN according to the difference bitmap of the first LUN after being combined, so that the increment synchronization is realized; on the other hand, when the third LUN processes the write command, the data change identifier of the third LUN is modified to the second identifier value, and the data change bitmap is updated according to the write command until the third LUN is exported. The third LUN records the data change condition of the third LUN on the first storage device through the data change identification and the data change bitmap, so that when the third LUN is imported into other storage devices again, the service on the other storage devices can sense the data change condition of the third LUN on the first storage device.
As an embodiment, after determining that the third LUN has the data synchronization service belonging to the first storage device and the data synchronization service belonging to the other storage devices, if it is detected that the data change identifier of the third LUN is the first identifier value, the first storage device synchronizes the data increment of the first LUN to the third LUN according to the configured data synchronization service from the first LUN to the third LUN and the difference condition of the data synchronization service recorded by the first LUN, and changes the data change identifier of the third LUN to the second identifier value, and updates the data change bitmap of the third LUN.
As another embodiment, after determining that the third LUN has the data synchronization service belonging to the first storage device and the data synchronization service belonging to the other storage devices, if it is detected that the data change identifier of the third LUN is the initial identifier value, the first storage device creates a data change bitmap for the third LUN, changes the data change identifier of the third LUN to be the first identifier value, synchronizes the data increment of the first LUN to the third LUN according to the configured data synchronization service from the first LUN to the third LUN and the difference condition of the data synchronization service recorded by the first LUN, changes the data change identifier of the third LUN to be the second identifier value, and updates the data change bitmap of the third LUN.
As an embodiment, the above-mentioned copy service may also be replaced by other data synchronization services, such as mirror service, copy service, etc.
In this embodiment, the second LUN is designated to hold a copy of the data of the production data volume, and the second LUN is created in the second storage device.
The second storage device is named for convenience of description only and is not intended to limit a device.
The second LUN is also named for ease of description only and is not intended to limit a certain LUN.
In this embodiment, the data synchronization service of the third LUN to the second LUN has been configured in the second storage device, and the initial data synchronization of the third LUN to the second LUN has been completed.
In this embodiment, after the first storage device completes the incremental synchronization from the first LUN to the third LUN, the third LUN is pulled out and inserted into the second storage device. When the second storage device imports the third LUN, after determining that the data synchronization service of the second storage device exists on the third LUN and the data synchronization service belonging to other storage devices exists, checking the data change identifier of the third LUN, if the data change identifier is the second identifier value, indicating that the third LUN writes data on other storage devices, recording the data change condition through the data change bitmap, and based on the data change identifier, synchronizing the data change bitmap to the data synchronization service of the third LUN on the second storage device, so that the second storage device perceives the data change condition of the third LUN on other storage devices. Taking the copy service as an example, the third LUN is used as a source LUN of the copy service, the data change condition on the third LUN is recorded through the difference bitmap, the second LUN is used as a target LUN of the copy service, the data change condition on the second LUN is recorded through the difference bitmap, and when the data change bitmap of the third LUN is synchronized to the copy service from the third LUN to the second LUN, the data change bitmap of the third LUN is used as the difference bitmap of the first LUN, so that the difference bitmap of the first LUN comprises the data change bitmap of the third LUN.
Because the third LUN also has data synchronization service belonging to other storage devices, that is, the other storage devices care about the data change condition of the third LUN in the second storage device, after synchronizing the data change bitmap of the third LUN to the data synchronization service from the third LUN to the second LUN, the data change bitmap of the third LUN needs to be initialized, and the data change identifier of the third LUN is changed to the first identifier value; when the third LUN processes the write command, the modified data change mark is a second mark value, and the bit value corresponding to the storage block corresponding to the write command in the data change bitmap is changed to be 1, namely, the data change condition of the third LUN on the second storage device is recorded through the data change bitmap, so that other storage devices can mark the data change condition of the third LUN on the second storage device through the data change mark of the third LUN and the data change bitmap.
When the second storage device synchronizes the data increment of the first LUN to the third LUN according to the configured data synchronization service from the third LUN to the second LUN, taking the copying service as an example, merging the difference bitmap recorded on the second LUN to the difference bitmap of the third LUN when the copying task from the third LUN to the first LUN is started for the first time, and synchronizing the difference data from the third LUN to the second LUN according to the merged difference bitmap of the third LUN, thereby realizing increment synchronization.
As an embodiment, after determining that the third LUN has the data synchronization service belonging to the second storage device and the data synchronization service belonging to the other storage devices, if it is checked that the data change identifier of the third LUN is the first identifier value, the second storage device indicates that the third LUN has not written data in the other storage devices; when a write command is processed by a third LUN, changing a data change mark of the third LUN into a second mark value, and updating a data change bitmap; and synchronizing the increment data of the third LUN into the second LUN according to the configured data synchronization service from the third LUN to the second LUN and the difference condition of the data synchronization service recorded by the second LUN.
As another embodiment, after determining that the third LUN has the data synchronization service belonging to the second storage device and the data synchronization service belonging to the other storage devices, if it is checked that the data change identifier of the third LUN is the initial identifier value, the second storage device creates a data change bitmap for the third LUN, and changes the data change identifier of the third LUN to the first identifier value; when a write command is processed by a third LUN, changing a data change mark of the third LUN into a second mark value, and updating a data change bitmap; and synchronizing the increment data of the third LUN into the second LUN according to the configured data synchronization service from the third LUN to the second LUN and the difference condition of the data synchronization service recorded by the second LUN.
As an embodiment, the above-mentioned copy service may also be replaced by other data synchronization services, such as mirror service, copy service, etc.
The description shown in fig. 1 is thus completed. As can be seen from the flowchart shown in fig. 1, in the present application, the first storage device determines whether the data of the third LUN on other storage devices changes through the data change identifier of the third LUN, that is, whether the data of the third LUN is written into the other storage devices, and synchronizes the data change bitmap of the third LUN to the data synchronization service, such as the copy service, from the first LUN to the third LUN for the data change identifier indicating the data change, so that the first storage device can sense the data change of the third LUN on the other storage devices, change the data change identifier of the third LUN to the first identifier value, initialize the data change bitmap of the third LUN, synchronize the data of the first LUN to the third LUN according to the configured data synchronization service, such as the copy service, and update the data change identifier and the data change bitmap of the third LUN. The second storage device perceives the data change of the third LUN on other storage devices through the data change identification and the data change bitmap of the third LUN, synchronizes the data change bitmap of the third LUN to the data synchronization service, such as the copy service, of the third LUN to the second LUN, changes the data change identification of the third LUN to be a first identification value, initializes the data change bitmap of the third LUN, changes the data change identification of the third LUN to be a second identification value when the third LUN processes a write command, updates the data change bitmap, perceives the data change of the third LUN when the third LUN is imported into other storage devices, and synchronizes the data increment of the third LUN to the second LUN according to the configured data synchronization service. In this way, in the process of migrating data, the data synchronization service is not required to be repeatedly configured and disabled on the first storage device and the second storage device, and the data increment synchronization can be performed according to the data change bitmap and the data change identifier. By applying the migration method provided by the embodiment of the application, the operation complexity in the migration process can be reduced, the migration time is shortened, and the migration efficiency is improved.
After completing the flow shown in fig. 1, as an embodiment, the method further comprises: after the first storage device determines that the third LUN has the data synchronization service belonging to the first storage device and does not have the data synchronization service belonging to other storage devices, if the data change identifier of the third LUN is detected to be the second identifier value, synchronizing the data change bitmap of the third LUN to the data synchronization service from the first LUN to the third LUN, changing the data change identifier of the third LUN to the initial identifier value, deleting the data change bitmap of the third LUN, and synchronizing the data increment of the first LUN to the third LUN according to the configured data synchronization service from the first LUN to the third LUN.
The data synchronization service belonging to the first storage device exists in the third LUN, the first storage device is concerned about the data change condition of the third LUN on other storage devices, and if the data change identifier of the third LUN is the second identifier value, the data change bitmap of the third LUN needs to be synchronized to the data synchronization service of the first LUN to the data synchronization service of the third LUN, so that the data synchronization service of the first LUN to the third LUN can sense the data change condition of the third LUN on other storage devices; in addition, the third LUN does not have data synchronization service belonging to other storage devices, that is, there is no concern about the data change condition of the third LUN on the first storage device, so after synchronizing the data change bitmap of the third LUN to the data synchronization service of the first LUN to the third LUN, the data change identifier of the third LUN may be changed to the initial identifier value, and the data change bitmap of the third LUN is deleted. In some embodiments, when the data of the first LUN is delta-synchronized to the third LUN according to the configured data synchronization service from the first LUN to the third LUN, delta-synchronization can be implemented according to the difference bitmap after merging on the first LUN, and in the delta-synchronization process, because the data change identifier of the third LUN is the initial identifier value, the data change identifier and the data change bitmap are not updated when the third LUN processes the write command, thereby improving the processing efficiency of the write command.
In other embodiments, after determining that the third LUN has the data synchronization service belonging to the second storage device and does not have the data synchronization service belonging to other storage devices, if it is detected that the data change identifier of the third LUN is a second identifier value, the second storage device synchronizes the data change bitmap of the third LUN to the data synchronization service from the third LUN to the second LUN, changes the data change identifier of the third LUN to an initial identifier value, deletes the data change bitmap of the third LUN, and synchronizes the data increment of the third LUN to the first LUN according to the configured data synchronization service from the third LUN to the second LUN.
The data synchronization service belonging to the second storage device exists in the third LUN, the second storage device is concerned about the data change condition of the third LUN on other storage devices, and if the data change identifier of the third LUN is the second identifier value, the data change bitmap of the third LUN needs to be synchronized to the data synchronization service from the third LUN to the second LUN, so that the data synchronization service from the third LUN to the second LUN can sense the data change condition of the third LUN on other storage devices; in addition, the third LUN does not have data synchronization service belonging to other storage devices, that is, the storage device does not care about the data change condition of the third LUN on the second storage device, so after the data change bitmap of the third LUN is synchronized to the data synchronization service from the third LUN to the second LUN, the data change identifier of the third LUN can be changed to be the initial identifier value, and the data change bitmap of the third LUN is deleted, so that the data change identifier and the data change bitmap are not updated when the third LUN processes the write command, and the processing efficiency of the write command is improved. In some embodiments, when the data of the third LUN is delta-synchronized to the second LUN according to the configured data synchronization traffic of the third LUN to the second LUN, delta-synchronization may be implemented according to the difference bitmap after merging on the third LUN.
As another embodiment, the method further comprises: and after the first storage device determines that the third LUN does not have the data synchronization service belonging to the first storage device and has the data synchronization service belonging to other storage devices, changing the data change identifier of the third LUN into a first identification value, and initializing the data change bitmap of the third LUN. This means that the third LUN does not have data synchronization service belonging to the first storage device, and the first storage device does not care about the data change condition of the third LUN on other storage devices, so that it is not necessary to check the data change identifier and the data change bitmap of the third LUN; in addition, the third LUN has data synchronization service belonging to other storage devices, and the other storage devices concern about the data change condition of the third LUN on the first storage device, so that the data change identifier of the third LUN is changed to a first identifier value, and the data change bitmap of the third LUN is initialized, so that the data change identifier of the third LUN is changed to a second identifier value when the third LUN processes a write command, and the data change bitmap is updated, so that the data change of the third LUN is perceived when the third LUN is imported into other storage devices.
As further embodiments, the method further comprises: and after the second storage device determines that the third LUN does not have the data synchronization service belonging to the second storage device and has the data synchronization service belonging to other storage devices, changing the data change identifier of the third LUN into a first identification value, and initializing the data change bitmap of the third LUN. This means that the third LUN does not have data synchronization service belonging to the second storage device, and the second storage device does not care about the data change condition of the third LUN on other storage devices, so that it is not necessary to check the data change identifier and the data change bitmap of the third LUN; in addition, the third LUN has data synchronization service belonging to other storage devices, and the other storage devices concern about the data change condition of the third LUN on the second storage device, so that the data change identifier of the third LUN is changed to a first identifier value, and the data change bitmap of the third LUN is initialized, so that the data change identifier of the third LUN is changed to a second identifier value when the third LUN processes a write command, and the data change bitmap is updated, so that the data change of the third LUN is perceived when the third LUN is imported into other storage devices.
As another embodiment, the method further comprises: and after the first storage device determines that the data synchronization service belonging to the first storage device does not exist in the third LUN and the data synchronization service belonging to other storage devices does not exist in the third LUN, changing the data change identifier of the third LUN to be an initial identifier value, and deleting the data change bitmap of the third LUN. This means that the third LUN does not have data synchronization service belonging to the first storage device, and the first storage device does not care about the data change condition of the third LUN on other storage devices, so that it is not necessary to check the data change identifier and the data change bitmap of the third LUN; in addition, the third LUN does not have data synchronization service belonging to other storage devices, and the other storage devices do not care about the data change condition of the third LUN on the first storage device, so that the data change mark of the third LUN is changed to be an initial mark value, and the data change bitmap of the third LUN is deleted, and therefore, the data change mark and the data change bitmap are not updated when the third LUN processes a write command, and the write command processing efficiency is improved.
As further embodiments, the method further comprises: and after the second storage device determines that the data synchronization service belonging to the second storage device does not exist in the third LUN and the data synchronization service belonging to other storage devices does not exist in the third LUN, changing the data change identifier of the third LUN to be an initial identifier value, and deleting the data change bitmap of the third LUN. This means that the third LUN does not have data synchronization service belonging to the second storage device, and the second storage device does not care about the data change condition of the third LUN on other storage devices, so that it is not necessary to check the data change identifier and the data change bitmap of the third LUN; in addition, the third LUN does not have data synchronization service belonging to other storage devices, and the other storage devices do not care about the data change condition of the third LUN on the second storage device, so that the data change mark of the third LUN is changed to be an initial mark value, and the data change bitmap of the third LUN is deleted, and therefore, the data change mark and the data change bitmap are not updated when the third LUN processes a write command, and the write command processing efficiency is improved.
In some embodiments, as shown in fig. 2, the determining in the step 101 that the third LUN has the data synchronization service belonging to the first storage device and the data synchronization service belonging to the other storage devices includes the following steps 201 to 206:
In this embodiment, the third LUN carries a device identification that is used to represent the unique identity of the first storage device.
Step 203 determines that the third LUN does not have a data synchronization service belonging to the first storage device.
In this step, as long as it is determined that the third LUN carries the device identifier of the first storage device, it indicates that the third LUN has the data synchronization service belonging to the first storage device, and if it is found that the third LUN also carries the device identifier of the non-first storage device, it indicates that the third LUN also has the data synchronization service belonging to other storage devices.
It should be noted that, step 201 and step 204 are not sequentially executed, and step 201 may be executed first, or step 204 may be executed first, which is not limited in this embodiment.
In step 205, it is determined that the third LUN has data synchronization services belonging to other storage devices.
In step 206, it is determined that the third LUN does not have data synchronization services belonging to other storage devices.
Based on the above embodiment, as shown in fig. 3, the determining, by the second storage device in the above step 102, that the third LUN has the data synchronization service belonging to the second storage device and does not have the data synchronization service belonging to the other storage device includes steps 301 to 306:
In this embodiment, the third LUN carries a device identification for representing the unique identity of the second storage device.
In this step, as long as it is determined that the third LUN carries the device identifier of the second storage device, it indicates that the third LUN has the data synchronization service belonging to the second storage device, and if it is found that the third LUN also carries the device identifier of the second storage device, it indicates that the third LUN also has the data synchronization service belonging to other storage devices.
It should be noted that, step 301 and step 304 are not sequentially executed, and step 301 may be executed first, or step 304 may be executed first, which is not limited in this embodiment.
In step 305, it is determined that the third LUN has data synchronization services belonging to other storage devices.
Therefore, by applying the method provided by the embodiment of the application, whether the data synchronization service belonging to the storage device corresponding to the device identifier exists or not and whether the data synchronization service belonging to other storage devices not corresponding to the device identifier exists or not can be rapidly and accurately determined through the device identifier.
As an example, the device identifier is a UUID (Universally Unique Identifier, universal unique identifier) or a device serial number.
If the actual service usage requirement of the service changes, for example, the third LUN is used on the first storage device or the second storage device for a long time, and when the third LUN is no longer used for moving the data volume, the data synchronization service belonging to other storage devices on the third LUN is no longer required to be reserved, and based on the data synchronization service, the data synchronization service belonging to other storage devices can be manually deleted. As an embodiment, the method further comprises: and after deleting the data synchronization service belonging to other storage devices on the third LUN, the first storage device changes the data change identifier of the third LUN into an initial identifier value, and simultaneously deletes the data change bitmap of the third LUN. Thus, when the third LUN on the first storage device does not have the data synchronization service belonging to other storage devices, the other storage devices do not care about the data change condition of the third LUN on the first storage device, so that the data change identifier of the third LUN is changed to be the initial identifier value, and the data change bitmap of the third LUN is deleted, and therefore, the data change identifier and the data change bitmap are not updated when the third LUN processes the write command, and the write command processing efficiency is improved. As another embodiment, the second storage device changes the data change identifier of the third LUN to the initial identifier value after deleting the data synchronization service belonging to the other storage device on the third LUN, and deletes the data change bitmap of the third LUN. Thus, when the third LUN on the second storage device does not have the service belonging to other storage devices, the other storage devices do not care about the data change condition of the third LUN on the second storage device, so that the data change identifier of the third LUN is changed to the initial identifier value, and the data change bitmap of the third LUN is deleted, and therefore, the data change identifier and the data change bitmap are not updated when the third LUN processes the write command, and the write command processing efficiency is improved.
Thus, the description of the above embodiments is completed.
Referring to fig. 4, fig. 4 is a system configuration diagram of a data migration 400 provided in this embodiment. The system comprises at least a first storage device 401 and a second storage device 402;
a first storage device 401, configured to, when importing a third LUN belonging to another storage device into the first storage device, determine that the third LUN has a data synchronization service belonging to the first storage device and a data synchronization service belonging to another storage device, if it is detected that a data change identifier of the third LUN is a second identifier value, synchronize a data change bitmap of the third LUN to a data synchronization service from the first LUN to the third LUN, initialize the data change bitmap of the third LUN, and change the changed data identifier of the third LUN to a first identifier value; synchronizing the data increment of the first LUN into the third LUN according to the configured data synchronization business from the first LUN to the third LUN, changing the data change mark of the third LUN into a second mark value, and updating the data change bitmap of the third LUN; the first LUN is designated for producing the data volume, the third LUN is designated for moving the data volume, the first identification value is used for indicating that the data is unchanged, the second identification value is used for indicating that the data is changed, and the data change bitmap is used for recording the data change condition;
A second storage device 402, configured to, when importing the third LUN belonging to the other storage device to the second storage device, determine that the third LUN has a data synchronization service belonging to the second storage device and a data synchronization service belonging to the other storage device, if it is detected that the data change identifier of the third LUN is a second identifier value, synchronize the data change bitmap of the third LUN to the data synchronization service from the third LUN to the second LUN, change the data change identifier of the third LUN to the first identifier value, and initialize the data change bitmap of the third LUN; when a write command is processed by a third LUN, changing a data change mark of the third LUN into a second mark value, and updating a data change bitmap; synchronizing the data increment of the third LUN into the second LUN according to the configured data synchronization business from the third LUN to the second LUN; the second LUN is designated for storing a data copy of the production data volume.
As an embodiment, the first storage device 401 is further configured to determine that, after the third LUN has the data synchronization service belonging to the first storage device and no data synchronization service belonging to other storage devices, if it is detected that the data change identifier of the third LUN is the second identifier value, synchronize the data change bitmap of the third LUN to the data synchronization service from the first LUN to the third LUN, change the data change identifier of the third LUN to the initial identifier value, delete the data change bitmap of the third LUN, and synchronize the data increment of the first LUN to the third LUN according to the configured data synchronization service from the first LUN to the third LUN; or/and (or)
The second storage device 402 is further configured to determine that, after the third LUN has the data synchronization service belonging to the second storage device and no data synchronization service belonging to other storage devices, if it is detected that the data change identifier of the third LUN is a second identifier value, synchronize the data change bitmap of the third LUN to the data synchronization service from the third LUN to the second LUN, change the data change identifier of the third LUN to an initial identifier value, delete the data change bitmap of the third LUN, and synchronize the data increment of the third LUN to the first LUN according to the configured data synchronization service from the third LUN to the second LUN.
As an embodiment, the first storage device 401 is further configured to change the data change identifier of the third LUN to the first identifier value and initialize the data change bitmap of the third LUN after determining that the third LUN does not have the data synchronization service belonging to the first storage device and has the data synchronization service belonging to the other storage device; or/and (or)
The second storage device is further configured to change a data change identifier of the third LUN to a first identifier value after determining that the third LUN does not have a data synchronization service belonging to the second storage device and has a data synchronization service belonging to another storage device, and initialize a data change bitmap of the third LUN.
As an embodiment, the first storage device 401 is further configured to change the data change identifier of the third LUN to an initial identifier value after determining that the third LUN does not have the data synchronization service belonging to the first storage device and does not have the data synchronization service belonging to other storage devices, and delete the data change bitmap of the third LUN; or/and (or)
The second storage device 402 is further configured to change a data change identifier of the third LUN to an initial identifier value after determining that the third LUN does not have a data synchronization service belonging to the second storage device and does not have a data synchronization service belonging to another storage device, and delete a data change bitmap of the third LUN.
As an embodiment, the determining, in the first storage device 401, that the third LUN exists in the data synchronization service belonging to the first storage device and the data synchronization service belonging to the other storage devices is specifically used:
searching whether the equipment identifier belonging to the first storage equipment exists in the data synchronization service configuration recorded by the third LUN, if so, determining that the data synchronization service belonging to the first storage equipment exists in the third LUN, and if not, determining that the data synchronization service belonging to the first storage equipment does not exist in the third LUN; searching whether the equipment identifier which does not belong to the first storage equipment exists in the data synchronization service configuration recorded by the third LUN, if so, determining that the data synchronization service which belongs to other storage equipment exists in the third LUN, and if not, determining that the data synchronization service which belongs to the other storage equipment does not exist in the third LUN;
The determining, in the second storage device 402, that the third LUN has a data synchronization service belonging to the second storage device and a data synchronization service belonging to another storage device is specifically configured to:
searching whether the equipment identifier of the second storage equipment exists in the data synchronization service configuration recorded by the third LUN, if so, determining that the data synchronization service belonging to the second storage equipment exists in the third LUN, and if not, determining that the data synchronization service belonging to the second storage equipment does not exist in the third LUN; and searching whether the equipment identifier which does not belong to the second storage equipment exists in the data synchronization service configuration recorded by the third LUN, if so, determining that the data synchronization service which belongs to other storage equipment exists in the third LUN, and if not, determining that the data synchronization service which belongs to the other storage equipment does not exist in the third LUN.
As an embodiment, the first storage device 401 is further configured to change the data change identifier of the third LUN to an initial identifier value after deleting the data synchronization service belonging to the other storage device on the third LUN, and delete the data change bitmap of the third LUN at the same time; or/and (or)
The second storage device 402 is further configured to change the data change identifier of the third LUN to an initial identifier value after deleting the data synchronization service belonging to other storage devices on the third LUN, and delete the data change bitmap of the third LUN.
Thus, the description shown in fig. 4 is completed.
As can be seen from the flowchart shown in fig. 4, in the present application, the first storage device determines whether the data of the third LUN changes through the data change identifier of the third LUN, that is, whether the data of the third LUN is written into other storage devices, and synchronizes the data change bitmap of the third LUN to the data synchronization service from the first LUN to the third LUN for the data change identifier indicating the data change, so that the first storage device can sense the data change of the third LUN on other storage devices, change the data change identifier of the third LUN to be the first identifier value, initialize the data change bitmap of the third LUN, synchronize the data increment of the first LUN to the third LUN according to the configured data synchronization service, and update the data change identifier and the data change bitmap of the third LUN; the second storage device perceives the data change of the third LUN on other storage devices through the data change identification and the data change bitmap of the third LUN, synchronizes the data change bitmap of the third LUN to the data synchronization service from the third LUN to the second LUN, changes the data change identification of the third LUN to be a first identification value, initializes the data change bitmap of the third LUN, changes the data change identification of the third LUN to be a second identification value when the third LUN processes a write command, updates the data change bitmap so as to be perceived as to change the data when the third LUN is imported into other storage devices, and synchronizes the data increment of the third LUN to the second LUN according to the configured data synchronization service. In this way, in the process of migrating data, the data synchronization service is not required to be repeatedly configured and disabled on the first storage device and the second storage device, and the data increment synchronization can be performed according to the data change bitmap and the data change identifier. By applying the migration method provided by the embodiment of the application, the operation complexity in the migration process can be reduced, the migration time is shortened, and the migration efficiency is improved.
The implementation process of the functions and roles of each unit in the above system is specifically shown in the implementation process of the corresponding steps in the above method, and will not be described herein again.
For system embodiments, reference is made to the description of method embodiments for the relevant points, since they essentially correspond to the method embodiments. The system embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purposes of the present application. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
The description of the apparatus shown in fig. 4 is thus completed.
In the electronic device provided in the embodiment of the present application, from a hardware level, a schematic diagram of a hardware architecture may be shown in fig. 5. Comprising the following steps: a machine-readable storage medium and a processor, wherein: the machine-readable storage medium stores machine-executable instructions executable by the processor; the processor is configured to execute machine-executable instructions to implement the application of the example disclosure to data migration operations.
The machine-readable storage medium provided by the embodiments of the present application stores machine-executable instructions that, when invoked and executed by a processor, cause the processor to implement the application of the above example disclosure to data migration operations.
Here, a machine-readable storage medium may be any electronic, magnetic, optical, or other physical storage device that may contain or store information, such as executable instructions, data, or the like. For example, a machine-readable storage medium may be: RAM (Radom Access Memory, random access memory), volatile memory, non-volatile memory, flash memory, a storage drive (e.g., hard drive), a solid state drive, any type of storage disk (e.g., optical disk, dvd, etc.), or a similar storage medium, or a combination thereof.
The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer, which may be in the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being functionally divided into various units, respectively. Of course, the functions of each element may be implemented in one or more software and/or hardware elements when implemented in the present application.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Moreover, these computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
For the device embodiments, reference is made to the description of the method embodiments for the relevant points, since they essentially correspond to the method embodiments. The apparatus embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the units may be selected according to actual needs to achieve the purposes of the present application. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
The foregoing description of the preferred embodiments of the present invention is not intended to limit the invention to the precise form disclosed, and any modifications, equivalents, improvements and alternatives falling within the spirit and principles of the present invention are intended to be included within the scope of the present invention.
Claims (14)
1. A method of data migration, the method comprising:
when a first storage device imports a third LUN belonging to other storage devices to the first storage device, after determining that the third LUN has data synchronization service belonging to the first storage device and data synchronization service belonging to other storage devices, if the data change identifier of the third LUN is detected to be a second identifier value, synchronizing a data change bitmap of the third LUN to the data synchronization service from the first LUN to the third LUN, initializing the data change bitmap of the third LUN, and changing the changed data identifier of the third LUN to the first identifier value; synchronizing the data increment of the first LUN into the third LUN according to the configured data synchronization business from the first LUN to the third LUN, changing the data change mark of the third LUN into a second mark value, and updating the data change bitmap of the third LUN; the first LUN is designated for producing the data volume, the third LUN is designated for moving the data volume, the first identification value is used for indicating that the data is unchanged, the second identification value is used for indicating that the data is changed, and the data change bitmap is used for recording the data change condition;
When the second storage device imports the third LUN belonging to the other storage devices to the second storage device, after determining that the third LUN has the data synchronization service belonging to the second storage device and the data synchronization service belonging to the other storage devices, if the data change identification of the third LUN is detected to be the second identification value, synchronizing the data change bitmap of the third LUN to the data synchronization service from the third LUN to the second LUN, changing the data change identification of the third LUN to be the first identification value, and initializing the data change bitmap of the third LUN; when a write command is processed by a third LUN, changing a data change mark of the third LUN into a second mark value, and updating a data change bitmap; synchronizing the data increment of the third LUN into the second LUN according to the configured data synchronization business from the third LUN to the second LUN; the second LUN is designated for storing a data copy of the production data volume.
2. The method according to claim 1, characterized in that the method further comprises:
after the first storage device determines that the third LUN has the data synchronization service belonging to the first storage device and does not have the data synchronization service belonging to other storage devices, if the data change identifier of the third LUN is detected to be the second identifier value, synchronizing the data change bitmap of the third LUN to the data synchronization service from the first LUN to the third LUN, changing the data change identifier of the third LUN to the initial identifier value, deleting the data change bitmap of the third LUN, and synchronizing the data increment of the first LUN to the third LUN according to the configured data synchronization service from the first LUN to the third LUN; or/and (or)
After the second storage device determines that the third LUN has the data synchronization service belonging to the second storage device and does not have the data synchronization service belonging to other storage devices, if the data change identifier of the third LUN is detected to be the second identifier value, synchronizing the data change bitmap of the third LUN to the data synchronization service from the third LUN to the second LUN, changing the data change identifier of the third LUN to the initial identifier value, deleting the data change bitmap of the third LUN, and synchronizing the data increment of the third LUN to the first LUN according to the configured data synchronization service from the third LUN to the second LUN.
3. The method according to claim 1, characterized in that the method further comprises:
after the first storage device determines that the third LUN does not have the data synchronization service belonging to the first storage device and has the data synchronization service belonging to other storage devices, changing the data change identifier of the third LUN to a first identifier value, and initializing a data change bitmap of the third LUN; or/and (or)
And after the second storage device determines that the third LUN does not have the data synchronization service belonging to the second storage device and has the data synchronization service belonging to other storage devices, changing the data change identifier of the third LUN into a first identification value, and initializing the data change bitmap of the third LUN.
4. The method according to claim 1, characterized in that the method further comprises:
after the first storage device determines that the third LUN does not have the data synchronization service belonging to the first storage device and does not have the data synchronization service belonging to other storage devices, changing the data change identifier of the third LUN to an initial identifier value, and deleting the data change bitmap of the third LUN; or/and (or)
And after the second storage device determines that the data synchronization service belonging to the second storage device does not exist in the third LUN and the data synchronization service belonging to other storage devices does not exist in the third LUN, changing the data change identifier of the third LUN to be an initial identifier value, and deleting the data change bitmap of the third LUN.
5. The method of any of claims 1-4, wherein the first storage device determining that the third LUN exists for data synchronization traffic belonging to the first storage device and data synchronization traffic belonging to other storage devices comprises:
the first storage device searches whether the device identifier belonging to the first storage device exists in the data synchronization service configuration recorded by the third LUN, if yes, it is determined that the data synchronization service belonging to the first storage device exists in the third LUN, and if not, it is determined that the data synchronization service belonging to the first storage device does not exist in the third LUN; searching whether the equipment identifier which does not belong to the first storage equipment exists in the data synchronization service configuration recorded by the third LUN, if so, determining that the data synchronization service which belongs to other storage equipment exists in the third LUN, and if not, determining that the data synchronization service which belongs to the other storage equipment does not exist in the third LUN;
The second storage device determining that the third LUN has a data synchronization service belonging to the second storage device and a data synchronization service belonging to other storage devices, including:
the second storage device searches whether the device identifier of the second storage device exists in the data synchronization service configuration recorded by the third LUN, if yes, it is determined that the data synchronization service belonging to the second storage device exists in the third LUN, and if not, it is determined that the data synchronization service belonging to the second storage device does not exist in the third LUN; and searching whether the equipment identifier which does not belong to the second storage equipment exists in the data synchronization service configuration recorded by the third LUN, if so, determining that the data synchronization service which belongs to other storage equipment exists in the third LUN, and if not, determining that the data synchronization service which belongs to other storage equipment does not exist in the third LUN.
6. The method according to any one of claims 1 to 4, further comprising:
after deleting the data synchronization service belonging to other storage devices on the third LUN, the first storage device changes the data change identifier of the third LUN into an initial identifier value, and deletes the data change bitmap of the third LUN; or/and (or)
And after deleting the data synchronization service belonging to other storage devices on the third LUN, the second storage device changes the data change identifier of the third LUN into an initial identifier value, and simultaneously deletes the data change bitmap of the third LUN.
7. A data migration system, the system comprising at least a first storage device and a second storage device;
the first storage device is configured to, when a third LUN belonging to another storage device is imported to the first storage device, determine that the third LUN has a data synchronization service belonging to the first storage device and a data synchronization service belonging to another storage device, if it is detected that a data change identifier of the third LUN is a second identifier value, synchronize a data change bitmap of the third LUN to a data synchronization service from the first LUN to the third LUN, initialize the data change bitmap of the third LUN, and change the change data identifier of the third LUN to a first identifier value; synchronizing the data increment of the first LUN into the third LUN according to the configured data synchronization business from the first LUN to the third LUN, changing the data change mark of the third LUN into a second mark value, and updating the data change bitmap of the third LUN; the first LUN is designated for producing the data volume, the third LUN is designated for moving the data volume, the first identification value is used for indicating that the data is unchanged, the second identification value is used for indicating that the data is changed, and the data change bitmap is used for recording the data change condition;
The second storage device is configured to, when the third LUN belonging to the other storage device is imported to the second storage device, determine that the third LUN has a data synchronization service belonging to the second storage device and a data synchronization service belonging to the other storage device, and if it is detected that the data change identifier of the third LUN is a second identifier value, synchronize the data change bitmap of the third LUN to the data synchronization service from the third LUN to the second LUN, change the data change identifier of the third LUN to the first identifier value, and initialize the data change bitmap of the third LUN; when a write command is processed by a third LUN, changing a data change mark of the third LUN into a second mark value, and updating a data change bitmap; synchronizing the data increment of the third LUN into the second LUN according to the configured data synchronization business from the third LUN to the second LUN; the second LUN is designated for storing a data copy of the production data volume.
8. The system of claim 7, wherein the first storage device is further configured to, after determining that the third LUN has the data synchronization service belonging to the first storage device and no data synchronization service belonging to another storage device, synchronize the data change bitmap of the third LUN to the data synchronization service from the first LUN to the third LUN if the data change bitmap of the third LUN is checked to be the second identification value, change the data change identifier of the third LUN to the initial identification value, delete the data change bitmap of the third LUN, and synchronize the data increment of the first LUN to the third LUN according to the configured data synchronization service from the first LUN to the third LUN; or/and the second storage device is further configured to determine that after the third LUN has the data synchronization service belonging to the second storage device and no data synchronization service belonging to other storage devices, if it is detected that the data change identifier of the third LUN is a second identifier value, synchronize the data change bitmap of the third LUN to the data synchronization service from the third LUN to the second LUN, change the data change identifier of the third LUN to an initial identifier value, delete the data change bitmap of the third LUN, and synchronize the data increment of the third LUN to the first LUN according to the configured data synchronization service from the third LUN to the second LUN.
9. The system of claim 7, wherein the first storage device is further configured to change a data change identifier of the third LUN to a first identifier value after determining that the third LUN does not have data synchronization traffic pertaining to the first storage device and that data synchronization traffic pertaining to other storage devices exists, and initialize a data change bitmap of the third LUN; or/and (or)
The second storage device is further configured to change a data change identifier of the third LUN to a first identifier value after determining that the third LUN does not have a data synchronization service belonging to the second storage device and has a data synchronization service belonging to another storage device, and initialize a data change bitmap of the third LUN.
10. The system of claim 7, wherein the first storage device is further configured to change the data change identifier of the third LUN to an initial identifier value after determining that the third LUN does not have data synchronization traffic pertaining to the first storage device and does not have data synchronization traffic pertaining to other storage devices, and delete the data change bitmap of the third LUN; or/and (or)
And the second storage device is further configured to change the data change identifier of the third LUN to an initial identifier value after determining that the third LUN does not have the data synchronization service belonging to the second storage device and does not have the data synchronization service belonging to other storage devices, and delete the data change bitmap of the third LUN.
11. The system according to any of claims 7-10, wherein the determining in the first storage device that the third LUN exists for data synchronization traffic belonging to the first storage device and data synchronization traffic belonging to other storage devices is specifically configured to:
searching whether the equipment identifier belonging to the first storage equipment exists in the data synchronization service configuration recorded by the third LUN, if so, determining that the data synchronization service belonging to the first storage equipment exists in the third LUN, and if not, determining that the data synchronization service belonging to the first storage equipment does not exist in the third LUN; searching whether the equipment identifier which does not belong to the first storage equipment exists in the data synchronization service configuration recorded by the third LUN, if so, determining that the data synchronization service which belongs to other storage equipment exists in the third LUN, and if not, determining that the data synchronization service which belongs to the other storage equipment does not exist in the third LUN;
the second storage device determines that the third LUN has a data synchronization service belonging to the second storage device and a data synchronization service belonging to other storage devices, and is specifically configured to:
Searching whether the equipment identifier of the second storage equipment exists in the data synchronization service configuration recorded by the third LUN, if so, determining that the data synchronization service belonging to the second storage equipment exists in the third LUN, and if not, determining that the data synchronization service belonging to the second storage equipment does not exist in the third LUN; and searching whether the equipment identifier which does not belong to the second storage equipment exists in the data synchronization service configuration recorded by the third LUN, if so, determining that the data synchronization service which belongs to other storage equipment exists in the third LUN, and if not, determining that the data synchronization service which belongs to the other storage equipment does not exist in the third LUN.
12. The system according to any one of claims 7 to 10, wherein the first storage device is further configured to change the data change identifier of the third LUN to an initial identifier value after deleting the data synchronization service belonging to the other storage device on the third LUN, and simultaneously delete the data change bitmap of the third LUN; or/and (or)
The second storage device is further configured to change the data change identifier of the third LUN to an initial identifier value after deleting the data synchronization service belonging to the other storage devices on the third LUN, and delete the data change bitmap of the third LUN.
13. An electronic device comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor; the processor is configured to execute machine executable instructions to implement the method steps of any of claims 1-6.
14. A computer readable storage medium, characterized in that the computer readable storage medium has stored therein a computer program which, when executed by a processor, implements any of the steps of the method of claims 1-6.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202210006146.1A CN114442941B (en) | 2022-01-05 | 2022-01-05 | Data migration method, system, storage medium and equipment |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202210006146.1A CN114442941B (en) | 2022-01-05 | 2022-01-05 | Data migration method, system, storage medium and equipment |
Publications (2)
Publication Number | Publication Date |
---|---|
CN114442941A CN114442941A (en) | 2022-05-06 |
CN114442941B true CN114442941B (en) | 2023-05-12 |
Family
ID=81366201
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202210006146.1A Active CN114442941B (en) | 2022-01-05 | 2022-01-05 | Data migration method, system, storage medium and equipment |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN114442941B (en) |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6732231B1 (en) * | 2001-02-28 | 2004-05-04 | Emc Corporation | System and method for management of mirrored storage devices storing device serial numbers |
US9400611B1 (en) * | 2013-03-13 | 2016-07-26 | Emc Corporation | Data migration in cluster environment using host copy and changed block tracking |
CN106383667A (en) * | 2016-09-18 | 2017-02-08 | 华为数字技术(成都)有限公司 | Method and apparatus for LUN migration in business operation |
WO2019076236A1 (en) * | 2017-10-17 | 2019-04-25 | 中兴通讯股份有限公司 | Data synchronization method and device, super controller, domain controller, and storage medium |
CN111367892A (en) * | 2020-03-31 | 2020-07-03 | 中国建设银行股份有限公司 | Data migration method and device |
CN112783449A (en) * | 2021-01-25 | 2021-05-11 | 中国工商银行股份有限公司 | Data migration method and device |
-
2022
- 2022-01-05 CN CN202210006146.1A patent/CN114442941B/en active Active
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6732231B1 (en) * | 2001-02-28 | 2004-05-04 | Emc Corporation | System and method for management of mirrored storage devices storing device serial numbers |
US9400611B1 (en) * | 2013-03-13 | 2016-07-26 | Emc Corporation | Data migration in cluster environment using host copy and changed block tracking |
CN106383667A (en) * | 2016-09-18 | 2017-02-08 | 华为数字技术(成都)有限公司 | Method and apparatus for LUN migration in business operation |
WO2019076236A1 (en) * | 2017-10-17 | 2019-04-25 | 中兴通讯股份有限公司 | Data synchronization method and device, super controller, domain controller, and storage medium |
CN111367892A (en) * | 2020-03-31 | 2020-07-03 | 中国建设银行股份有限公司 | Data migration method and device |
CN112783449A (en) * | 2021-01-25 | 2021-05-11 | 中国工商银行股份有限公司 | Data migration method and device |
Also Published As
Publication number | Publication date |
---|---|
CN114442941A (en) | 2022-05-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP4900811B2 (en) | Storage system and storage control method | |
US7865473B2 (en) | Generating and indicating incremental backup copies from virtual copies of a data set | |
US7383465B1 (en) | Undoable volume using write logging | |
JP4845724B2 (en) | Storage system with backup function | |
CN109144416B (en) | Method and device for querying data | |
CN109902034B (en) | Snapshot creating method and device, electronic equipment and machine-readable storage medium | |
JP2005332067A (en) | Backup acquisition method and disk array device | |
US10977143B2 (en) | Mirrored write ahead logs for data storage system | |
CN105302665B (en) | A kind of improved Copy on write Snapshot Method and system | |
CN110147296B (en) | Data processing method, device, equipment and readable storage medium | |
CN112000426B (en) | Data processing method and device | |
CN109165120B (en) | Method and product for generating management snapshot and difference bitmap in distributed storage system | |
CN104750755A (en) | Method and system for recovering data after switching between main database and standby database | |
CN112783449A (en) | Data migration method and device | |
US10452496B2 (en) | System and method for managing storage transaction requests | |
CN115454723A (en) | Data backup and recovery method and system based on storage snapshot | |
JP2017531892A (en) | Improved apparatus and method for performing a snapshot of a block level storage device | |
CN109753381B (en) | Continuous data protection method based on object storage | |
CN114442944B (en) | Data replication method, system and equipment | |
CN114442941B (en) | Data migration method, system, storage medium and equipment | |
CN109582235B (en) | Management metadata storage method and device | |
CN105573862B (en) | Method and equipment for recovering file system | |
CN111399774B (en) | Data processing method and device based on snapshot under distributed storage system | |
CN114442943B (en) | Data migration method, system and equipment | |
CN114442942B (en) | Data migration method, system, equipment and storage medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |