CN115145497A - Volume data online migration method based on distributed storage - Google Patents

Volume data online migration method based on distributed storage Download PDF

Info

Publication number
CN115145497A
CN115145497A CN202211081206.2A CN202211081206A CN115145497A CN 115145497 A CN115145497 A CN 115145497A CN 202211081206 A CN202211081206 A CN 202211081206A CN 115145497 A CN115145497 A CN 115145497A
Authority
CN
China
Prior art keywords
migration
volume
data
target volume
data object
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202211081206.2A
Other languages
Chinese (zh)
Other versions
CN115145497B (en
Inventor
王家传
文刘飞
陈坚
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Sandstone Data Technology Co ltd
Original Assignee
Shenzhen Sandstone Data Technology Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Shenzhen Sandstone Data Technology Co ltd filed Critical Shenzhen Sandstone Data Technology Co ltd
Priority to CN202211081206.2A priority Critical patent/CN115145497B/en
Publication of CN115145497A publication Critical patent/CN115145497A/en
Application granted granted Critical
Publication of CN115145497B publication Critical patent/CN115145497B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input 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/06Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601Interfaces specially adapted for storage systems
    • G06F3/0628Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0646Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
    • G06F3/0647Migration mechanisms
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input 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/06Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601Interfaces specially adapted for storage systems
    • G06F3/0602Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/0604Improving or facilitating administration, e.g. storage management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input 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/06Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601Interfaces specially adapted for storage systems
    • G06F3/0602Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/061Improving I/O performance
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input 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/06Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601Interfaces specially adapted for storage systems
    • G06F3/0668Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/067Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The invention provides a volume data online migration method based on distributed storage, which comprises the following steps: a migration preparation stage: receiving a migration instruction, acquiring and creating a migration task and a target volume according to the migration instruction, establishing an online migration relationship between a source volume and the target volume on line, suspending IO, modifying an IO scheduling strategy on line after all received service requests are scheduled and executed, and then removing the suspended IO, so that the service can be correctly routed to the source volume or the target volume for execution, and the service is ensured to be continuously online; and a data migration stage: migrating all data objects of the source volume to the target volume in sequence, and updating the migration progress in sequence to support breakpoint continuous transmission; a migration completion stage: deleting the source volume and the migration task; the method and the system route the service write request to the target volume only for writing during the data migration, thereby effectively avoiding the write amplification and the waste of storage system resources caused by the synchronous writing of the service data to the source volume and the target volume.

Description

Volume data online migration method based on distributed storage
Technical Field
The invention relates to the field of online migration of data, in particular to an online migration method of volume data based on distributed storage.
Background
Business data of an enterprise do not all have the same use value. Part of business data of an enterprise can be accessed by frequent hot spots, part of other business data is rarely accessed, and even some business data is not accessed in time span of annual level. From the perspective of an enterprise, the occupation of high-performance precious storage system resources by the large amount of low-use business data invisibly increases the enterprise cost burden.
In addition, considering cost factors, enterprises typically employ non-high performance storage system resources to store data of the businesses at a previous date. However, as the enterprise continues to develop deeply, the business of the young people may also develop and grow into a popular business in the market, and then the access frequency of the related business data becomes very frequent, so that the enterprise faces the problem that the non-high performance storage system resource may not be able to bear the current high frequency business access pressure at this time.
One of the solutions to these business pain problems for enterprises is online migration of data. The online migration of data can realize the data migration between storage devices with different performance levels under the condition of ensuring that the service at the host end is not interrupted.
Although the Ceph community also supports volume migration, before data migration, user traffic on the source volume must be disconnected. After the volume migration preparation operation is completed, the user service can be restored only by docking the user service to the target volume again. Then, the continuity of the user service in the data migration process can be ensured. Thus, volume migration of the Ceph community is not truly online live migration.
Copy-Up technique: as shown in FIG. 1, i.e., the IO flow for the first read and write of a data object of Ceph clone volume, it is referred to as Copy-Up technique herein. Because the clone volume shares data with its parent volume, it is itself free of any data objects. Therefore, when a data object of the clone volume is written for the first time, the shared data must be read from the data object corresponding to the parent volume, and then the shared data and the business data are written into the data object of the clone volume as a transaction, and the data are atomically written into the data object of the clone volume in sequence.
In the existing volume online migration scheme, although it can be guaranteed that data migration between storage devices with different performance levels is achieved under the condition that host-side services are not interrupted, during the period of migrating source volume data to a target volume, foreground write services must write data into the source volume and the target volume synchronously, and the defect of obvious write amplification exists. And the service data of the user is synchronously written into the source volume and the target volume, so that the service data of the user is excessively redundant in the storage system to cause the waste of precious storage system resources, and the production cost of the user is invisibly increased. Meanwhile, in the whole life cycle of the IO process in which user service data is synchronously written into the source volume and the target volume, resources such as partial network bandwidth, memory bandwidth, CPU (central processing unit) resource, disk bandwidth and the like may be additionally occupied, and resources required by the user foreground service may be occupied to a certain extent, causing jitter in performance of the user foreground service.
Disclosure of Invention
The invention aims to solve the problems of storage system resource waste and resource occupation in volume data online migration, and provides a volume data online migration method based on distributed storage.
In order to achieve the purpose, the invention adopts the following technical scheme:
a volume data online migration method based on distributed storage comprises the following steps:
s1, a migration preparation stage: receiving a migration instruction, acquiring and creating a migration task and a target volume according to the migration instruction, establishing an online migration relationship between a source volume and the target volume on line, suspending IO, modifying an IO scheduling strategy on line after all received service requests are scheduled and executed, and then removing the suspended IO, so that the service can be routed to the source volume or the target volume for execution, and the service is ensured to be continuously online;
s2, data migration stage: migrating all data objects of the source volume to the target volume in sequence, and updating the migration progress in sequence so as to support breakpoint continuous transmission;
s3, a migration completion stage: deleting the source volume and the migration task;
wherein during migration the traffic data is written to only one volume, i.e. the source volume or the target volume.
In some embodiments, in step S1, the received service is routed to the source volume for execution before the IO is suspended, and the received service is routed to the target volume for execution after the IO is suspended.
In some embodiments, in step S1, after the migration task and the target volume are created, the metadata of the copy source volume is also copied.
In some embodiments, in step S1, the migration relationship is established by notifying the source volume client of online using a subscription and publication mechanism.
In some embodiments, step S1 further comprises: and suspending subsequent incoming service requests, and modifying the IO scheduling strategy after all the requests received in the queue waiting for IO, namely the requests received before suspending IO are scheduled and executed.
In some embodiments, when the background migration source volume data object is written into the target volume, the check that the target volume data object does not exist and the data of the source volume data object are written into the target volume data object are used as a transaction to perform atomic operation, and if the execution result of the transaction is successful or the target volume data object already exists, the current migration of the source volume data object to the target volume is considered successful.
In some embodiments, during migrating data, foreground service writing is routed to a target volume for execution, when writing the target volume, checking that a target volume data object exists and the foreground service writing the target volume data object are packaged into a transaction for atomic operation, and if the transaction execution result is that the target volume data object does not exist, copy-on-write processing is performed by using a Copy-Up-like method.
In some embodiments, the Copy-Up-like method comprises the steps of:
a. reading all data of the source volume data object;
b. the write requests and new write requests received during the period of reading all data of the source volume data object are sequentially pressed into a waiting queue;
c. checking the nonexistence of the target volume data object and writing the data of the source volume data object into the target volume data object as a transaction for carrying out atomic processing;
d. and if the transaction execution result is successful or the target volume data object exists, assembling all the data to be written of the write requests in the waiting queue into a complete data buff in sequence, and writing the data to be written into the target volume data object.
In some embodiments, in step S2, data of the source volume data objects are read in sequence, written into the target volume in sequence, and the migration progress is updated in sequence, that is, the migration of the nth data object of the source volume is recorded in sequence, so as to resume at the breakpoint.
The present invention also provides a computer-readable storage medium, on which a computer program is stored, which, when executed by a processor, is capable of implementing the above-mentioned volume data online migration method based on distributed storage.
The invention has the following beneficial effects:
the invention establishes the migration relationship and IO scheduling strategy between the source volume and the target volume on line and intelligently routes the foreground write service to the source volume or the target volume on line for execution, and the invention only routes the service write request to the target volume for writing during data migration, thereby effectively avoiding the write amplification of the synchronous writing of the service data to the source volume and the target volume and the waste of storage system resources, simultaneously reducing the pressure of the background task on the storage cluster, better providing high-efficiency service for the foreground service of a user and saving the storage and production cost for the user.
Drawings
FIG. 1 is a flow diagram of a prior art read-write IO of a Ceph clone volume data object in the background art;
FIG. 2 is a flow chart of a method for online migration of volume data based on distributed storage according to an embodiment of the present invention;
FIG. 3 is a flow chart of a migration preparation phase in an embodiment of the present invention;
FIG. 4 is a flow chart of foreground service write in an embodiment of the present invention;
fig. 5 is a flow sequence diagram of foreground service reading in the embodiment of the present invention.
Detailed Description
The embodiments of the present invention will be described in detail below. It should be emphasized that the following description is merely exemplary in nature and is not intended to limit the scope of the invention or its application.
Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of the embodiments of the present invention, "a plurality" means two or more unless specifically limited otherwise.
Referring to fig. 2, the online migration of volume data according to the embodiment of the present invention mainly includes the following three stages:
firstly, receiving a migration instruction, and a migration preparation stage: acquiring and creating a migration task according to the migration instruction, establishing an online migration relationship between the source volume and the target volume on line, and modifying an IO scheduling strategy, so that user foreground service IO can be intelligently and correctly routed to the source volume or the target volume for execution, and the continuous online of user services is always ensured;
then, the data migration phase: and migrating all data objects of the source volume to the target volume in sequence, and updating the migration progress in sequence so as to support breakpoint continuous transmission.
Finally, a migration completion phase: the source volume and migration task are deleted.
In this embodiment, an online migration relationship between a source volume and a target volume is established online, and an IO is suspended, after all received service requests are scheduled and executed, an IO scheduling policy is modified online, and then the suspended IO is released, so that a user service can be ensured to be continuously online without interruption; when data is migrated, the service request is intelligently routed to the target volume for processing according to the latest IO scheduling strategy, so that the service data is ensured to be only written into the target volume, and the defects of synchronous writing of the data into the source volume and the target volume, write amplification, storage system resource waste and the like can be effectively avoided; during data migration, when a foreground service writes and a background migration writes a target volume, the checking of the existence of the target volume data object and the writing of the target volume data object are taken as a transaction to carry out atomic operation, and Copy-on-write processing is carried out on the foreground service writing target volume by combining a Copy-Up method, so that the mutual exclusion of foreground service writing and background data migration writing is ensured, and the correctness of user service data is ensured.
1. Preparation for migration
Referring to fig. 3, a migration task and a target volume are created according to task information acquired from a migration instruction, and metadata of a copy source volume is copied. Then, a subscription and release mechanism is utilized to inform a source volume client side to establish an online migration relationship with a target volume, then a subsequent service IO request is suspended, an IO scheduling strategy is modified after all the received requests (the requests received before the IO is suspended) in an IO waiting queue are scheduled and executed, and finally the suspension of the service IO is released, so that the preparation work of a migration task is completed under the condition that the user service is ensured to be uninterrupted; and routing the received service to a source volume for execution before suspending the IO, and routing the received service to a target volume for execution after releasing the suspended IO.
During the migration preparation period, before and after suspending the service IO, the user service IO may be correctly routed to the source volume or the target volume for execution according to the IO scheduling policy (i.e. before the IO scheduling policy is modified, the service IO is routed to the source volume for execution, otherwise, the service IO is routed to the target volume for execution). During the period of suspending the business IO, the user is almost insensitive due to the extremely short suspension time. Thus, the user traffic is continuously online and maintains good continuity.
The processing logic for migration preparation is as follows:
(1) Acquiring migration task metadata according to the migration instruction, creating a migration task and a target volume according to the migration task metadata, and copying metadata of the source volume to the target volume;
(2) Informing a source volume client to establish an online migration relationship with a target volume online, suspending IO and modifying an IO scheduling strategy after all received service requests are scheduled and executed, and finally releasing IO suspension;
2. migrating data
And reading the data of the data objects of the source volume in sequence, writing the data into the target volume in sequence, and updating the migration progress in sequence, namely recording the migration of the Nth data object of the source volume which is completed in sequence so as to be convenient for breakpoint continuous transmission.
When the background migration source volume data object is written into the target volume, the check that the target volume data object does not exist and the writing of the source volume data object data into the target volume data object are taken as a transaction to carry out atomic operation (one or a series of operations which cannot be interrupted). If the transaction execution result is successful or the target volume data object already exists, the migration of the source volume data object to the target volume is considered to be successful.
During data migration, foreground service writing is routed to a target volume for execution, and when the target volume is written, the existence of the data object of the target volume is checked and the data object of the target volume is packaged into a transaction for atomic operation by the foreground service. If the transaction execution result is that the target volume data object does not exist, copy-on-write processing is carried out by adopting a Copy-Up method:
a. reading all data of the source volume data object;
b. the write requests and new write requests received during the period of reading all data of the source volume data object are sequentially pressed into a waiting queue;
c. checking the nonexistence of the target volume data object and writing the data of the source volume data object into the target volume data object as a transaction for carrying out atomic processing;
d. if the transaction execution result is successful or the target volume data object exists, assembling all the data to be written in the write requests in the waiting queue into a complete data buf in sequence, and writing the data into the target volume data object;
therefore, by checking whether the target volume data object exists or not and writing data into the target volume data object as a transaction to perform atomic operation and combining Copy-on-write processing of the Copy-Up-like method, mutual exclusion of background migration write and foreground service write of the target volume is ensured, and correctness of service data is guaranteed.
In addition, during data migration, if foreground business reading IO comes, the data object corresponding to the target volume is directly read; and if the target volume data object does not exist, the target volume data object is routed to the source volume to read the data object corresponding to the source volume.
3. Migration completion
After all data objects of the source volume are successfully migrated and written into the target volume in sequence, the source volume and the migration task can be deleted. And the migration task is completed.
In the above, under the condition that foreground service writing and background data migration writing are concurrent, the processing method of foreground service writing and foreground service reading is as follows:
referring to fig. 4, in the case that foreground service write and background data migration write are concurrent, the foreground service write processing logic is as follows:
(1) If the received foreground service write request is routed to the source volume for execution before the migration preparation hangs IO, the data is directly written into the source volume;
(2) If the received foreground service write request is routed to the target volume for execution after the migration prepares to suspend IO, and when data is written to the target volume, the checking of the existence of the target volume data object and the writing of the target volume data object are taken as one transaction for atomic operation:
if the transaction execution result is that the target volume data object does not exist, adopting a Copy-Up method to perform Copy-on-write processing:
a. reading all data of the source volume data object;
b. the write requests and new write requests received during the period of reading all data of the source volume data object are sequentially pressed into a waiting queue;
c. checking the nonexistence of the target volume data object and writing the data of the source volume data object into the target volume data object as a transaction to carry out atomic operation;
d. and if the transaction execution result is successful or the target volume data object exists, assembling all the data to be written of the write requests in the waiting queue into a data buf in sequence, and writing the data to be written into the target volume data object.
Referring to fig. 5, in the case that foreground service reading and background data migration are concurrent, the processing logic of foreground service reading is as follows:
(1) If the received service reading request is routed to the source volume for execution before the migration preparation hangs IO, the data is directly read from the source volume;
(2) If the received service reading request is processed after the migration preparation suspension IO, the service reading request is routed to the target volume to execute:
if the target volume data object to be read does not exist, reading the data of the corresponding data object from the source volume;
and if the target volume data object to be read already exists, directly reading the data of the data object corresponding to the target volume.
The service, foreground service, user service and user foreground service all express the meaning of the user service.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams 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.
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.
The foregoing is a further detailed description of the invention in connection with specific/preferred embodiments and it is not intended to limit the invention to the specific embodiments described. It will be apparent to those skilled in the art that various substitutions and modifications can be made to the described embodiments without departing from the spirit of the invention, and these substitutions and modifications should be considered to fall within the scope of the invention. In the description herein, references to the description of the term "one embodiment," "some embodiments," "preferred embodiments," "an example," "a specific example," or "some examples" or the like are intended to mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Various embodiments or examples and features of various embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction. Although embodiments of the present invention and their advantages have been described in detail, it should be understood that various changes, substitutions and alterations can be made herein without departing from the scope of the claims.

Claims (10)

1. A volume data online migration method based on distributed storage is characterized by comprising the following steps:
s1, a migration preparation stage: receiving a migration instruction, acquiring and creating a migration task and a target volume according to the migration instruction, establishing an online migration relationship between a source volume and the target volume on line, suspending IO, modifying an IO scheduling strategy on line after all received service requests are scheduled and executed, and then removing the suspended IO, so that the service can be routed to the source volume or the target volume for execution, and the service is ensured to be continuously online;
s2, data migration: migrating all data objects of the source volume to the target volume in sequence, and updating the migration progress in sequence so as to support breakpoint continuous transmission;
s3, a migration completion stage: deleting the source volume and the migration task;
wherein during migration the traffic data is written to only one volume, i.e. the source volume or the target volume.
2. The online migration method of volume data based on distributed storage according to claim 1, wherein in step S1, the received service is routed to the source volume for execution before suspending the IO, and the received service is routed to the target volume for execution after releasing the suspended IO.
3. The online migration method based on volume data in distributed storage according to claim 1, wherein in step S1, after the migration task and the target volume are created, the metadata of the copy source volume is also copied.
4. The distributed storage based volume data online migration method according to claim 1, wherein in step S1, the migration relationship is established by notifying the source volume client online using a subscription and publication mechanism.
5. The online migration method of volume data based on distributed storage according to claim 1, wherein step S1 further comprises: and hanging subsequent incoming service requests, and modifying the IO scheduling strategy after all the requests received in the queue waiting for IO, namely the requests received before the IO is hung are scheduled and executed.
6. The online migration method of volume data based on distributed storage according to claim 5, wherein when the background migration source volume data object is written into the target volume, the check that the target volume data object does not exist and the data of the source volume data object is written into the target volume data object are used as a transaction to perform an atomic operation, and if the execution result of the transaction is successful or the target volume data object already exists, the current migration of the source volume data object to the target volume is considered to be successful.
7. The method for online migrating volume data based on distributed storage according to claim 5, wherein during migrating data, foreground service write is routed to the target volume for execution, when writing the target volume, the check that the target volume data object exists and the foreground service write the target volume data object are encapsulated into a transaction for atomic operation, if the transaction execution result is that the target volume data object does not exist, copy-on-write processing is performed by using a Copy-Up-like method.
8. The method for online migration of volume data based on distributed storage according to claim 7, wherein the Copy-Up-like method comprises the steps of:
a. reading all data of the source volume data object;
b. the writing request and new writing requests received during the period of reading all data of the source volume data object are sequentially pressed into a waiting queue;
c. checking the nonexistence of the target volume data object and writing the data of the source volume data object into the target volume data object as a transaction for carrying out atomic processing;
d. and if the transaction execution result is successful or the target volume data object exists, assembling all the data to be written of the write requests in the waiting queue into a complete data buff in sequence, and writing the data into the target volume data object.
9. The online migration method for volume data based on distributed storage according to claim 1, wherein in step S2, data of the source volume data objects are read in sequence, written into the target volume in sequence, and the migration progress is updated in sequence, that is, the migration of the nth data object of the source volume is completed in sequence is recorded, so as to continue to be transferred at a breakpoint.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, is capable of implementing the method for online migration of volume data based on distributed storage according to any one of claims 1 to 9.
CN202211081206.2A 2022-09-06 2022-09-06 Volume data online migration method based on distributed storage Active CN115145497B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211081206.2A CN115145497B (en) 2022-09-06 2022-09-06 Volume data online migration method based on distributed storage

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211081206.2A CN115145497B (en) 2022-09-06 2022-09-06 Volume data online migration method based on distributed storage

Publications (2)

Publication Number Publication Date
CN115145497A true CN115145497A (en) 2022-10-04
CN115145497B CN115145497B (en) 2022-11-29

Family

ID=83416649

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211081206.2A Active CN115145497B (en) 2022-09-06 2022-09-06 Volume data online migration method based on distributed storage

Country Status (1)

Country Link
CN (1) CN115145497B (en)

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107577433A (en) * 2017-09-13 2018-01-12 郑州云海信息技术有限公司 The moving method of a kind of storage medium and file data, device and equipment
CN110169040A (en) * 2018-07-10 2019-08-23 深圳花儿数据技术有限公司 Distributed data storage method and system based on multilayer consistency Hash
CN110413213A (en) * 2018-04-28 2019-11-05 伊姆西Ip控股有限责任公司 Seamless migration of the storage volume between storage array
CN111367470A (en) * 2020-02-21 2020-07-03 苏州浪潮智能科技有限公司 Online migration method, system and device for distributed storage volume and readable storage medium
CN111427514A (en) * 2020-03-27 2020-07-17 杭州宏杉科技股份有限公司 View migration method and device
CN112433669A (en) * 2020-10-23 2021-03-02 苏州浪潮智能科技有限公司 Method, system, equipment and medium for online migration of distributed storage volume
CN113268449A (en) * 2021-03-03 2021-08-17 浪潮云信息技术股份公司 Distributed file migration method and system based on object storage
US20210344752A1 (en) * 2020-04-29 2021-11-04 Silicon Motion Technology (Hong Kong) Limited Method and apparatus for performing simple storage service seamless migration using index objects
CN114860154A (en) * 2021-02-03 2022-08-05 慧与发展有限责任合伙企业 Data migration using cache state changes
CN114936198A (en) * 2022-06-07 2022-08-23 中国银行股份有限公司 Data migration method and device

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107577433A (en) * 2017-09-13 2018-01-12 郑州云海信息技术有限公司 The moving method of a kind of storage medium and file data, device and equipment
CN110413213A (en) * 2018-04-28 2019-11-05 伊姆西Ip控股有限责任公司 Seamless migration of the storage volume between storage array
CN110169040A (en) * 2018-07-10 2019-08-23 深圳花儿数据技术有限公司 Distributed data storage method and system based on multilayer consistency Hash
CN111367470A (en) * 2020-02-21 2020-07-03 苏州浪潮智能科技有限公司 Online migration method, system and device for distributed storage volume and readable storage medium
CN111427514A (en) * 2020-03-27 2020-07-17 杭州宏杉科技股份有限公司 View migration method and device
US20210344752A1 (en) * 2020-04-29 2021-11-04 Silicon Motion Technology (Hong Kong) Limited Method and apparatus for performing simple storage service seamless migration using index objects
CN112433669A (en) * 2020-10-23 2021-03-02 苏州浪潮智能科技有限公司 Method, system, equipment and medium for online migration of distributed storage volume
CN114860154A (en) * 2021-02-03 2022-08-05 慧与发展有限责任合伙企业 Data migration using cache state changes
CN113268449A (en) * 2021-03-03 2021-08-17 浪潮云信息技术股份公司 Distributed file migration method and system based on object storage
CN114936198A (en) * 2022-06-07 2022-08-23 中国银行股份有限公司 Data migration method and device

Also Published As

Publication number Publication date
CN115145497B (en) 2022-11-29

Similar Documents

Publication Publication Date Title
US11816063B2 (en) Automatic archiving of data store log data
CN108664496B (en) Data migration method and device
US10289684B2 (en) Live migration of virtual machine persistent data using mirrored input-output operations
EP2288975B1 (en) Method for optimizing cleaning of maps in flashcopy cascades containing incremental maps
US6848021B2 (en) Efficient data backup using a single side file
JPH0683687A (en) Data processing system and method thereof
CN108228102B (en) Method and device for data migration between nodes, computing equipment and computer storage medium
US8412674B2 (en) Replication resynchronization
US9984139B1 (en) Publish session framework for datastore operation records
US8775753B2 (en) Synchronization of logical copy relationships
US6636951B1 (en) Data storage system, data relocation method and recording medium
US10929359B2 (en) Dynamically reorganizing a dataset using online migration while allowing concurrent user access to data in the dataset
JP4693540B2 (en) Database reconfiguration device and database reconfiguration program
US11816000B2 (en) Virtual recovery of unstructured data
CN112800026A (en) Data transfer node, method, system and computer readable storage medium
US11977453B2 (en) Virtual replication of unstructured data
CN115145497B (en) Volume data online migration method based on distributed storage
US20160139842A1 (en) Storage control apparatus and storage system
JP2020177274A (en) Storage device, storage system, and program
CN114201109A (en) Tracking changes to a storage volume during data transfers
CN114442942B (en) Data migration method, system, equipment and storage medium
CN110673985A (en) Method for automatically backing up version library, storage medium and server
TWI693550B (en) Backup method for supporting multi-dsik architecture of virtual machine
CN111666338B (en) Data replication method, control node and electronic equipment
CA3151014A1 (en) Virtual recovery and replication of unstructured data

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