CN107577433B - Storage medium and file data migration method, device and equipment - Google Patents
Storage medium and file data migration method, device and equipment Download PDFInfo
- Publication number
- CN107577433B CN107577433B CN201710823164.8A CN201710823164A CN107577433B CN 107577433 B CN107577433 B CN 107577433B CN 201710823164 A CN201710823164 A CN 201710823164A CN 107577433 B CN107577433 B CN 107577433B
- Authority
- CN
- China
- Prior art keywords
- migration
- file
- data
- junk
- current
- 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
- 230000005012 migration Effects 0.000 title claims abstract description 290
- 238000013508 migration Methods 0.000 title claims abstract description 275
- 238000000034 method Methods 0.000 title claims abstract description 57
- 230000001960 triggered effect Effects 0.000 claims abstract description 14
- 238000001514 detection method Methods 0.000 claims description 3
- 230000000694 effects Effects 0.000 abstract description 4
- 230000008569 process Effects 0.000 description 13
- 238000010586 diagram Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 125000004122 cyclic group Chemical group 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000000717 retained effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Images
Abstract
The invention discloses a file data migration method, which is applied to a distributed file system and comprises the following steps: determining whether a junk object exists according to historical migration information recorded in the log file, and if so, clearing the junk object; after file migration is triggered, recording migration information of current migration data in a file in a log file mode; and writing the current migration data into the target storage pool, and updating the migration information. Therefore, by the migration method, when the migration system of the migration file is started, the migration condition of the last migration data can be known according to the historical migration information contained in the log file generated when the system operates last time, so that whether the garbage objects exist or not is judged, all the garbage objects are removed in time, the storage space of the system is saved, and the utilization rate of the storage space of the system is improved. In addition, the invention also discloses a file data migration device, equipment and a computer readable storage medium, and the effects are as above.
Description
Technical Field
The present invention relates to the field of data storage, and in particular, to a method, an apparatus, and a device for migrating storage media and file data.
Background
With the rapid development of information technology, data that people can obtain increases exponentially, so that a distributed file system capable of effectively solving the problems of data storage and management arises. The distributed file system extends a certain file system fixed at a certain place to any multiple places/multiple file systems, and a plurality of nodes form a file system network. Each node may be distributed at different locations, with communication and data transfer between nodes over the network. When using a distributed file system, one does not need to care about which node the data is stored on or retrieved from, but only needs to manage and store the data in the file system as if using a local file system.
However, in the normal use process of the distributed file system, some file data in the distributed file system often need to be migrated, the normal file data migration is performed in a cycle by taking data of a certain data amount as a unit, and no garbage object is generated in the file data migration process, but once an exception occurs in the data migration process, which causes system exit or system crash, a garbage object which cannot be cleared is generated, and the storage space of the system is occupied, thereby causing waste of the storage space of the system.
Therefore, how to ensure that the garbage objects generated in the file data migration process can be removed in time, thereby saving the storage space of the system and further improving the utilization rate of the storage space of the system is a technical problem that needs to be solved by technical personnel in the field.
Disclosure of Invention
The invention aims to provide a method, a device and equipment for migrating storage media and file data, which can ensure that garbage objects generated in the file data migration process are removed in time, thereby saving the storage space of a system and improving the utilization rate of the storage space of the system.
In order to solve the above technical problem, the present invention provides a file data migration method, applied to a distributed file system, including:
determining whether a junk object exists according to historical migration information recorded in a log file, and if so, clearing the junk object;
after file migration is triggered, recording migration information of current migration data in a file in a log file mode;
and writing the current migration data into a target storage pool, and updating the migration information.
Preferably, the determining whether a garbage object exists according to historical migration information recorded in a log file specifically includes:
reading the last recorded last history migration information with a writing success mark in the log file;
and judging whether the identification of the storage pool in which the file is positioned only contains the identification of the target storage pool in the last migration information.
Preferably, the recording migration information of the current migration data in the file in a log file manner specifically includes:
and recording the migration information to a current log file in an additional mode before writing the current migration data into a target storage pool.
Preferably, the migration method further comprises:
after all migration data in the file are written into the target storage pool, judging whether a junk file object is generated, and if not, deleting the current log file;
correspondingly, the determining whether the garbage object exists according to the historical migration information recorded in the log file specifically includes:
detecting whether the log file exists;
if yes, the step of determining whether a junk object exists according to historical migration information recorded in the log file is carried out, and if not, the step of recording migration information of current migration data in the file in a log file mode after file migration is triggered is carried out.
Preferably, the determining whether to generate the junk file object specifically includes:
judging whether the migration data in the source storage pool is successfully deleted;
if so, judging that the junk file object is not generated;
if not, judging whether the migration data in the target storage pool is successfully deleted; if yes, the junk file object is judged not to be generated, and if not, the junk file object is judged to be generated.
Preferably, after the determining is to generate the junk file object, the migration method further includes:
and clearing the junk file object and deleting the current log file.
In order to solve the above technical problem, the present invention further provides a file data migration apparatus, applied to a distributed file system, including:
the determining module is used for determining whether a garbage object exists according to historical migration information recorded in the log file, and if so, clearing the garbage object;
the recording module is used for recording migration information of current migration data in a file in a log file mode after file migration is triggered;
and the updating module is used for writing the current migration data into a target storage pool and updating the current migration data to the migration information.
Preferably, the migration apparatus further comprises:
a judging module, configured to judge whether the garbage object is generated after all migration data in the file is written in the target storage pool, and if not, delete the current log file;
and the detection module is used for detecting whether the log file exists or not.
In order to solve the above technical problem, the present invention further provides a file data migration device, which is applied to a distributed storage system, and includes:
a memory for storing a file migration program;
and the processor is used for realizing the steps of any one of the migration methods when the file migration program is executed.
In order to solve the above technical problem, the present invention further provides a computer-readable storage medium, on which a file migration program is stored, and the file migration program, when executed by a processor, implements the steps of any of the migration methods described above.
Compared with the prior art, the file data migration method provided by the invention is applied to a distributed file system, and comprises the following steps: determining whether a junk object exists according to historical migration information recorded in the log file, and if so, clearing the junk object; after file migration is triggered, recording migration information of current migration data in a file in a log file mode; and writing the current migration data into the target storage pool, and updating the migration information. Therefore, according to the file data migration method provided by the invention, because the migration information of the current migration data is recorded in a log file manner, and the migration information is updated to the migration information of the current migration data which is successfully migrated after the current migration data is written into the target storage pool, when the migration system of the migration file is restarted, the migration condition of the previous migration data can be known according to the historical migration information contained in the log file generated in the last operation of the system, so that whether the garbage object exists or not is judged, and all the garbage objects can be immediately removed as long as the garbage object is judged to exist, so that the garbage object generated in the file data migration process can be timely removed, the storage space of the system is further saved, and the utilization rate of the storage space of the system is improved. In addition, the invention also provides a file data migration device, equipment and a computer readable storage medium, and the effects are as above.
Drawings
In order to illustrate the embodiments of the present invention more clearly, the drawings that are needed in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings can be obtained by those skilled in the art without inventive effort.
Fig. 1 is a flowchart of a file data migration method according to an embodiment of the present invention;
fig. 2 is a flowchart of another file data migration method according to an embodiment of the present invention;
fig. 3 is a structural diagram of a file data migration apparatus according to an embodiment of the present invention;
fig. 4 is a structural diagram of a file data migration apparatus according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without any inventive step, are within the scope of the present invention.
The invention aims to provide a method, a device and equipment for migrating storage media and file data, which can ensure that garbage objects generated in the file data migration process are removed in time, thereby saving the storage space of a system and improving the utilization rate of the storage space of the system.
In order to make the technical solutions of the present invention better understood, the present invention will be further described in detail with reference to the accompanying drawings and specific embodiments.
Fig. 1 is a flowchart of a file data migration method according to an embodiment of the present invention. The file data migration method provided by the embodiment of the invention is applied to a distributed file system, and as shown in fig. 1, the migration method comprises the following steps:
s10: and determining whether a garbage object exists according to the history migration information recorded in the log file, if so, proceeding to step S11, and if not, skipping step S11.
S11: and clearing the garbage object.
S12: after file migration is triggered, migration information of current migration data in the files is recorded in a log file mode.
S13: and writing the current migration data into the target storage pool, and updating the migration information.
When file data is migrated, cyclic migration is performed by taking data with a certain data volume as a unit, the migrated file data is hereinafter collectively referred to as a file, data in the file is collectively referred to as migration data, and currently migrated data is collectively referred to as current migration data; the storage pools in which the files are not migrated are collectively referred to as source storage pools, and the new storage pools to which the files are to be migrated are collectively referred to as target storage pools. The history migration information at least comprises an inode number of the file, an identifier of the source storage pool (such as an ID of the source storage pool), an identifier of the target storage pool (such as an ID of the target storage pool), a data volume of the migration data and a flag indicating whether the writing is successful; after file migration is triggered, migration information recorded in a log file mode at least comprises an inode number of a file, an identifier of a source storage pool, an identifier of a target storage pool and data volume of migration data; updating the migration information is to add the flag indicating successful writing to the migration information corresponding to the current migration data. The garbage object comprises a garbage file object and a garbage data object, wherein the garbage data object is migration data stored in the target storage pool when only partial migration data in the file is stored in the target storage pool, and the garbage file object is migration data stored in the source storage pool when all the migration data in the file is stored in the target storage pool.
In a specific implementation, step S10 needs to be executed first each time the system for file migration is started. Moreover, for step S10, since the file is only stored in the target storage pool corresponding to the last target storage identifier if no garbage object is generated after the file migration is successful, it can be determined whether there is a garbage object by determining whether the identifier of the storage pool in which the file is currently located only includes the last target storage pool identifier, where the last target storage pool identifier is the target storage pool identifier in the last history migration information with a write success flag in the log file. Specifically, if the number of the storage pools in which the file is currently located is two, the file is indicated to exist in the two storage pools at the same time, a garbage object exists, and migration data stored in the source storage pool is the garbage object; if the number of the storage pools in which the files are currently located is one, and the identification of the last target storage pool is the same as the identification of the storage pool in which the files are currently located, all migration data in the files are successfully migrated into the target storage pool, and no junk object exists; if the last target storage pool identifier is different from the identifier of the storage pool in which the file is currently located, it is indicated that only a part of migration data is successfully migrated into the target storage pool, that is, the part of migration data that is successfully migrated is stored in both the target storage pool and the source storage pool, a garbage object exists, and the part of migration data stored in the target storage pool is the garbage object.
As a preferred embodiment, determining whether there is a garbage object according to the historical migration information recorded in the log file specifically includes: reading the last recorded last history migration information with a writing success mark in the log file; and judging whether the identification of the storage pool in which the file is positioned only contains the identification of the target storage pool in the last migration information.
For step S11, if the number of storage pools in which the file currently exists is two, deleting the migration data stored in the source storage pool; and if the number of the storage pools in which the files are currently located is one, and the identification of the target storage pool is different from the identification of the storage pool in which the files are currently located, deleting the migration data in the target storage pool.
With respect to step S12, since the system needs to determine whether there is a garbage object from the history migration information, when performing file migration, migration information of the file migration needs to be recorded. Moreover, since the file migration is performed in a cyclic manner by taking migration data of a certain data amount as a unit, when the file migration is triggered, migration information may be recorded along with the migration of the current migration data, that is, each time migration of the migration data is performed, migration information corresponding to the current migration data may be recorded in a current log file, where the current log file may be a log file in which history migration information is recorded in step S10, or a log file newly created by the system.
As a preferred embodiment, recording migration information of current migration data in a file in a log file specifically includes: before writing the current migration data into the target storage pool, the migration information is recorded to the current log file in an additional mode. Furthermore, it is preferable that the log file recording the history migration information is directly deleted after the step S10 is executed to save the storage space, and the migration information of the current migration data is additionally recorded into the newly created log file when the step S11 is executed.
Therefore, according to the file data migration method provided by this embodiment, because the migration information of the current migration data is recorded in the form of a log file, and the migration information is updated to the migration information that the migration is successful after the current migration data is written in the target storage pool, when the migration system of the migration file is restarted, the migration condition of the last migration data can be known according to the historical migration information contained in the log file generated when the system last operates, so as to determine whether a garbage object exists, and all the garbage objects can be immediately removed as long as it is determined that the garbage object exists, so that the garbage object generated in the file data migration process can be timely removed, thereby saving the storage space of the system and improving the utilization rate of the storage space of the system.
Fig. 2 is a flowchart of another file data migration method according to an embodiment of the present invention. In a specific implementation, in order to respond to a file migration request more quickly when a migration system for migrating files is started, this embodiment is further improved on the basis of the above embodiment, after file data is all migrated and written into a target storage pool, if no garbage object is generated, a current log file is directly deleted, when the migration system for migrating files is started again, it is only necessary to directly detect whether there is a log file, if no log file is generated, it is proved that no garbage object exists, and the step of recording migration information of the current migration data in the file in a log file manner after file migration is triggered is directly performed.
As shown in fig. 2, as a preferred embodiment, on the basis of fig. 1, the method further includes:
s20: it is detected whether or not there is a log file, and if yes, it proceeds to step S10, and if no, it proceeds to step S12.
S21: after all migration data in a file is written to the target storage pool, it is determined whether a garbage file object is generated, and if not, step S23 is executed, and if so, step S21 is executed.
S22: the current log file is retained and step S23 is not performed.
S23: and deleting the current log file.
It should be noted that step S20 is executed before step S10 is executed, and step S21 is executed after step S13 is executed. In the normal migration process of the file data, after all migration data in the file are successfully written into the target storage pool, all the migration data in the source storage pool are deleted, and if the migration data in the source storage pool are deleted unsuccessfully, all the migration data in the target storage pool are deleted. However, if all migration data in the file are successfully written into the target storage pool due to a system exception, and all migration data in the source storage pool are not deleted or are not deleted successfully in the source storage pool, and then all migration data in the target storage pool are continuously deleted, a garbage file object may be generated, where the garbage file object is file data (all migration data in the file) stored in the source storage pool.
For step S20, if there is no log file, it indicates that no garbage object was generated during the last file migration, i.e. there is no garbage object in the distributed storage system, and step S12 is executed directly without executing step S10.
For step S21, after all the migration data in the file is written into the target storage pool, first, a preliminary judgment is made by judging whether the migration data in the source storage is successfully deleted, and if the migration data in the source storage is successfully deleted, it can be concluded that no junk file object is generated; if the migration data in the source storage is not successfully deleted, it is further required to determine whether the migration data in the target storage is successfully deleted, and if the migration data in the target storage is successfully deleted, it may also be concluded that a junk file object is not generated, whereas if the migration data in the target storage is not successfully deleted, it may be concluded that a junk file object is generated.
As a preferred embodiment, the determining whether to generate the junk file object specifically includes:
and judging whether the migration data in the source storage pool is successfully deleted.
If so, it is determined that no junk file object is generated.
If not, judging whether the migration data in the target storage pool is successfully deleted; if yes, the junk file object is judged not to be generated, and if not, the junk file object is judged to be generated.
For step S21, if no garbage file object is generated, it is proved that no exception occurs during the migration of the whole file, and no other garbage data object is generated, so that it is not necessary to analyze the historical migration information in the log file to determine and delete the garbage object when the migration system for migrating the file is started next time. Therefore, in the specific implementation, the current log file can be directly deleted after the previous file is successfully migrated, so that when the migration system for migrating the file is started next time, the file migration request can be directly responded instead of analyzing the historical migration information in the log file because the log file does not exist, and the speed of responding to the file migration request is improved.
In addition, if the migration system for migrating the file does not cause the migration system for migrating the file to exit or crash although the junk file object is generated due to the system exception when the update source data request is sent to the source data server, in order to increase the speed of responding to the file migration request, as a preferred embodiment, after determining that the junk file object is generated, the method further includes: and clearing the junk file object and deleting the current log file. Of course, it can be understood that, in order to prevent the system from falling into the dead loop to cause the system crash, the maximum number of times of clearing the same garbage file object may be set, and if the number of times of clearing the same garbage file object is greater than the maximum number of times, the clearing operation is abandoned and continued, and a corresponding prompt is performed.
The foregoing describes in detail an embodiment of a file data migration method provided by the present invention, and the present invention further provides a file data migration apparatus corresponding to the migration method.
Fig. 3 is a structural diagram of a file data migration apparatus according to an embodiment of the present invention. As shown in fig. 3, the migration apparatus for file data is applied to a distributed file system, and includes:
and the determining module 30 is configured to determine whether a garbage object exists according to the historical migration information recorded in the log file, and if so, clear the garbage object.
The recording module 31 is configured to record migration information of current migration data in a file in a log file manner after file migration is triggered.
And the updating module 32 is configured to write the current migration data into the target storage pool and update the current migration data to the migration information.
As a preferred implementation manner, the migration apparatus provided in the embodiment of the present invention further includes:
and the judging module is used for judging whether a garbage object is generated or not after all the migration data in the file is written into the target storage pool, and if not, deleting the current log file.
And the detection module is used for detecting whether the log file exists or not.
Therefore, the file data migration apparatus provided in this embodiment records the migration information of the currently migrated data in the form of a log file by the recording module, and the updating module updates the migration information into migration information of successful migration after the current migration data is written into the target storage pool, therefore, when the migration system for migrating files is started again, the determining module can know the migration condition of the last migration data according to the historical migration information contained in the log file generated when the system was last operated, thereby judging whether the garbage objects exist or not, and as long as the garbage objects are judged to exist, the determining module can immediately clear all the garbage objects, therefore, the junk objects generated in the file data migration process can be cleared in time, the storage space of the system is saved, and the utilization rate of the storage space of the system is improved.
The present invention further provides a device for migrating file data corresponding to the migration method, where, since the embodiment of the device part corresponds to the embodiment of the method part, for the embodiment of the device part, reference is made to the description of the embodiment of the method part, and details are not repeated here.
Fig. 4 is a structural diagram of a file data migration apparatus according to an embodiment of the present invention. As shown in fig. 4, the migration apparatus includes:
and the memory 40 is used for storing a file migration program.
The processor 41 is configured to implement the steps of the migration method provided in any of the above embodiments when executing the file migration program.
Therefore, the file data migration device provided in this embodiment may call the file migration program stored in the memory through the processor to implement the steps of the migration method provided in any of the above embodiments, so that the migration device has the same practical effects as the migration method.
The present invention further provides a computer-readable storage medium, and a file migration program is stored on the computer-readable storage medium, and when the file migration program stored on the computer-readable storage medium is executed by a processor, the steps of the migration method provided in any of the above embodiments can be implemented.
As can be seen from this, the computer-readable storage medium provided in this embodiment stores a file migration program executable by a processor, and when the file migration program is executed by the processor, the file migration program may be a step of implementing the migration method provided in any of the above embodiments, so that the computer-readable storage medium has the same practical effects as the migration method described above.
The storage medium and the file data migration method, device and equipment provided by the invention are described in detail above. The embodiments are described in a progressive mode in the specification, the emphasis of each embodiment is different from that of other embodiments, and the same and similar parts among the embodiments are referred to each other.
It should be noted that, for those skilled in the art, it is possible to make various improvements and modifications to the present invention without departing from the principle of the present invention, and those improvements and modifications also fall within the scope of the claims of the present invention.
It is further noted that, in the present specification, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Claims (8)
1. A file data migration method is applied to a distributed file system and is characterized by comprising the following steps:
determining whether a junk object exists according to historical migration information recorded in a log file, and if so, clearing the junk object;
after file migration is triggered, recording migration information of current migration data in a file in a log file mode;
writing the current migration data into a target storage pool, and updating the migration information;
further comprising:
after all migration data in the file are written into the target storage pool, judging whether a junk file object is generated, and if not, deleting the current log file;
correspondingly, the determining whether the garbage object exists according to the historical migration information recorded in the log file specifically includes:
detecting whether the log file exists;
if yes, entering the step of determining whether a junk object exists according to historical migration information recorded in a log file, and if not, entering the step of recording migration information of current migration data in the file in a log file mode after file migration is triggered;
the judging whether to generate the junk file object specifically includes:
judging whether the migration data in the source storage pool is successfully deleted;
if so, judging that the junk file object is not generated;
if not, judging whether the migration data in the target storage pool is successfully deleted; if yes, the junk file object is judged not to be generated, and if not, the junk file object is judged to be generated.
2. The migration method according to claim 1, wherein the determining whether the garbage object exists according to the historical migration information recorded in the log file specifically comprises:
reading the last recorded last history migration information with a writing success mark in the log file;
and judging whether the identification of the storage pool in which the file is positioned only contains the identification of the target storage pool in the last historical migration information.
3. The migration method according to claim 2, wherein the recording migration information of the current migration data in the file in a log file manner specifically includes:
and recording the migration information to a current log file in an additional mode before writing the current migration data into a target storage pool.
4. The migration method according to claim 1, further comprising, after said determining that said garbage file object is generated:
and clearing the junk file object and deleting the current log file.
5. A migration apparatus of file data, applied to a distributed file system, is characterized by comprising:
the determining module is used for determining whether a garbage object exists according to historical migration information recorded in the log file, and if so, clearing the garbage object;
the recording module is used for recording migration information of current migration data in a file in a log file mode after file migration is triggered;
the updating module is used for writing the current migration data into a target storage pool and updating the current migration data to the migration information; after all migration data in the file are written into the target storage pool, judging whether a junk file object is generated, and if not, deleting the current log file;
correspondingly, the determining module specifically includes:
detecting whether the log file exists;
if yes, entering the step of determining whether a junk object exists according to historical migration information recorded in a log file, and if not, entering the step of recording migration information of current migration data in the file in a log file mode after file migration is triggered;
wherein the determining whether to generate the junk file object specifically includes:
judging whether the migration data in the source storage pool is successfully deleted;
if so, judging that the junk file object is not generated;
if not, judging whether the migration data in the target storage pool is successfully deleted; if yes, the junk file object is judged not to be generated, and if not, the junk file object is judged to be generated.
6. The migration device according to claim 5, further comprising:
a judging module, configured to judge whether the garbage object is generated after all migration data in the file is written in the target storage pool, and if not, delete the current log file;
and the detection module is used for detecting whether the log file exists or not.
7. A migration apparatus of file data, characterized by comprising:
a memory for storing a file migration program;
a processor for implementing the steps of the migration method according to any one of claims 1 to 4 when executing the file migration program.
8. A computer-readable storage medium, having stored thereon a file migration program which, when executed by a processor, implements the steps of the migration method according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710823164.8A CN107577433B (en) | 2017-09-13 | 2017-09-13 | Storage medium and file data migration method, device and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710823164.8A CN107577433B (en) | 2017-09-13 | 2017-09-13 | Storage medium and file data migration method, device and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107577433A CN107577433A (en) | 2018-01-12 |
| CN107577433B true CN107577433B (en) | 2020-09-22 |
Family
ID=61032947
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710823164.8A Active CN107577433B (en) | 2017-09-13 | 2017-09-13 | Storage medium and file data migration method, device and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107577433B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115145497B (en) * | 2022-09-06 | 2022-11-29 | 深圳市杉岩数据技术有限公司 | Volume data online migration method based on distributed storage |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103514274A (en) * | 2013-09-17 | 2014-01-15 | 宁波东冠科技有限公司 | Method for data migration of non-relational database HBase |
| CN105868343A (en) * | 2016-03-28 | 2016-08-17 | 上海携程商务有限公司 | Database migration method and system |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105468473B (en) * | 2014-07-16 | 2019-03-01 | 北京奇虎科技有限公司 | Data migration method and data migration device |
| WO2016051512A1 (en) * | 2014-09-30 | 2016-04-07 | 株式会社日立製作所 | Distributed storage system |
| CN106570093B (en) * | 2016-10-24 | 2020-03-27 | 南京中新赛克科技有限责任公司 | Mass data migration method and device based on independent metadata organization structure |
-
2017
- 2017-09-13 CN CN201710823164.8A patent/CN107577433B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103514274A (en) * | 2013-09-17 | 2014-01-15 | 宁波东冠科技有限公司 | Method for data migration of non-relational database HBase |
| CN105868343A (en) * | 2016-03-28 | 2016-08-17 | 上海携程商务有限公司 | Database migration method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107577433A (en) | 2018-01-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107729558B (en) | Method, system and device for defragmenting file system and computer storage medium | |
| KR101496179B1 (en) | System and method for searching information based on data absence tagging | |
| CN110018989B (en) | Snapshot comparison method and device | |
| CN107040576B (en) | Information pushing method and device and communication system | |
| CN108153594B (en) | Resource fragment sorting method of artificial intelligence cloud platform and electronic equipment | |
| CN112712702B (en) | Illegal event duplicate removal method and device, electronic equipment and machine-readable storage medium | |
| CN111198856A (en) | File management method and device, computer equipment and storage medium | |
| CN105867962A (en) | System upgrading method and device | |
| KR100899147B1 (en) | Method of storing meta-data and system for storing meta-data | |
| CN109165175A (en) | Device identification generation method and device | |
| CN107577433B (en) | Storage medium and file data migration method, device and equipment | |
| CN112328602B (en) | Method, device and equipment for writing data into Kafka | |
| JP5956064B2 (en) | Computer system, data management method, and computer | |
| CN111488117B (en) | Method, electronic device, and computer-readable medium for managing metadata | |
| CN113687783B (en) | Object aggregation method, system, device and computer storage medium | |
| CN110908610A (en) | Volume recovery station cleaning method, device, equipment and readable storage medium | |
| CN116126859A (en) | Data management method and device, electronic equipment and storage medium | |
| CN113886352B (en) | Metadata recovery method, device, equipment and medium of distributed file system | |
| CN111221468A (en) | Storage block data deleting method and device, electronic equipment and cloud storage system | |
| CN114518848A (en) | Hierarchical storage system, and method, apparatus, device, and medium for processing storage data | |
| CN109241011B (en) | Virtual machine file processing method and device | |
| CN110874182B (en) | Processing method, device and equipment for strip index | |
| CN107766216A (en) | It is a kind of to be used to obtain the method and apparatus using execution information | |
| CN106959888B (en) | Task processing method and device in cloud storage system | |
| CN115658626B (en) | Distributed network small file storage management method |
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 | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200826 Address after: 215100 No. 1 Guanpu Road, Guoxiang Street, Wuzhong Economic Development Zone, Suzhou City, Jiangsu Province Applicant after: SUZHOU LANGCHAO INTELLIGENT TECHNOLOGY Co.,Ltd. Address before: 450018 Henan province Zheng Dong New District of Zhengzhou City Xinyi Road No. 278 16 floor room 1601 Applicant before: ZHENGZHOU YUNHAI INFORMATION TECHNOLOGY Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |