CN117131014A - Database migration method, device, equipment and storage medium - Google Patents
Database migration method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN117131014A CN117131014A CN202311099145.7A CN202311099145A CN117131014A CN 117131014 A CN117131014 A CN 117131014A CN 202311099145 A CN202311099145 A CN 202311099145A CN 117131014 A CN117131014 A CN 117131014A
- Authority
- CN
- China
- Prior art keywords
- storage
- target data
- database
- migrated
- data
- 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.)
- Pending
Links
- 238000013508 migration Methods 0.000 title claims abstract description 104
- 230000005012 migration Effects 0.000 title claims abstract description 104
- 238000000034 method Methods 0.000 title claims abstract description 64
- 238000013500 data storage Methods 0.000 claims abstract description 102
- 230000015654 memory Effects 0.000 claims abstract description 92
- 238000012360 testing method Methods 0.000 claims description 22
- 238000004891 communication Methods 0.000 claims description 5
- 238000011084 recovery Methods 0.000 abstract description 12
- 238000005192 partition Methods 0.000 abstract description 9
- 238000007726 management method Methods 0.000 description 12
- 230000008569 process Effects 0.000 description 11
- 238000012545 processing Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 238000004364 calculation method Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000012790 confirmation Methods 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 239000007787 solid Substances 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/214—Database migration support
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2228—Indexing structures
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Software Systems (AREA)
- Human Computer Interaction (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to the technical field of computers, and discloses a database migration method, a device, equipment and a storage medium, wherein the method comprises the following steps: acquiring an original storage catalog of target data; identifying a storage position of target data under an original storage directory; updating a data storage catalog of the database to be migrated based on the original storage catalog when the storage position represents that the target data is stored in the database to be migrated; when the storage position represents that the target data is not stored in the database to be migrated, migrating the target data to the database to be migrated, and updating a data storage catalog of the database to be migrated based on the original storage catalog; the invention can transfer the data of the database partition on the standard hard disk of the nonvolatile memory back to the mechanical hard disk, and reduce the data volume on the standard hard disk of the nonvolatile memory, thereby reducing the data recovery time consumption when the standard hard disk of the nonvolatile memory is replaced and increasing the reliability of the storage system.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a database migration method, apparatus, device, and storage medium.
Background
The distributed storage system stores data by taking the object storage service as a unit, the bottom layer of the object storage service manages the data through the storage system so as to directly write the data into the mechanical hard disk, the database can be placed on the mechanical hard disk as well as the data, or the high-speed storage space can be placed on the non-volatile memory standard hard disk based on the consideration of improving the performance, and then part of the high-speed storage space is reserved on the mechanical hard disk. Meanwhile, in order to fully play the performance of the standard hard disk with non-volatile memory and achieve the aim of saving cost, the database partitions of a plurality of data disks are generally put on the same standard hard disk with non-volatile memory.
However, since the standard hard disk of the nonvolatile memory has a service life, when the service life of the standard hard disk of the nonvolatile memory is reached, a large amount of metadata information is stored in the database, and at this time, when the standard hard disk of the nonvolatile memory is replaced by the distributed data storage system, data recovery is required, and the more metadata, the more time is required for recovery.
Disclosure of Invention
In view of this, the present invention provides a database migration method, apparatus, device and storage medium, so as to solve the problem that when the existing distributed data storage system replaces the standard hard disk of the nonvolatile memory, it takes a long time to restore metadata, and once the restoration is interrupted, the metadata is easy to cause the situation of restoring errors, thereby increasing the risk of replacing the standard hard disk of the nonvolatile memory.
In a first aspect, the present invention provides a database migration method, the method comprising: acquiring an original storage catalog of target data; identifying a storage position of target data under an original storage directory; updating a data storage catalog of the database to be migrated based on the original storage catalog when the storage position represents that the target data is stored in the database to be migrated; and when the storage position characterizes that the target data is not stored in the database to be migrated, migrating the target data to the database to be migrated, and updating the data storage catalog of the database to be migrated based on the original storage catalog. Through the process, the data of the database partition on the standard hard disk of the nonvolatile memory can be migrated back to the mechanical hard disk, so that the data volume on the standard hard disk of the nonvolatile memory is reduced, the data recovery time consumption during the replacement of the standard hard disk of the nonvolatile memory is reduced, and the reliability of a storage system is improved.
In an alternative embodiment, updating the data store directory of the database to be migrated based on the original store directory includes:
acquiring a directory index of target data and an original storage directory;
and updating the directory index into the index of the target data and the data storage directory.
In an alternative embodiment, before migrating the target data to the database to be migrated, the method further includes:
determining the validity of the original storage catalogue and the data storage catalogue to obtain a validity determination result;
when the validity determination result indicates that the original storage catalogue and the data storage catalogue exist and are not invalid, executing the step of migrating target data to a database to be migrated;
and outputting migration error information and stopping migration of the target data when the validity determination result indicates that the original storage directory and the data storage directory do not exist or fail.
In an alternative embodiment, migrating the target data to the database to be migrated includes:
acquiring the space capacity of a first storage space occupied before migration of target data and the space capacity of a second storage space allocated by a database to be migrated;
and comparing the space capacity of the first storage space with the space capacity of the second storage space, and migrating the target data to the database to be migrated based on the capacity comparison result.
In an alternative embodiment, migrating the target data to the database to be migrated based on the capacity comparison result includes:
when the capacity comparison result represents that the space capacity of the first storage space is larger than or equal to the space capacity of the second storage space, migrating the target data to a database to be migrated;
When the capacity comparison result indicates that the space capacity of the first storage space is smaller than the space capacity of the second storage space, the application of the storage space to the database to be migrated is performed based on the space capacity of the first storage space.
In an alternative embodiment, after migrating the target data to the database to be migrated and updating the data storage directory of the database to be migrated based on the original storage directory, the method further includes:
acquiring a first content value corresponding to target data in an original storage catalog;
calculating a second content value of the content limited by the target data under the data storage catalog, and comparing the second content value with the first content value;
if the second content value is different from the first content value, determining that the target data in the original storage catalog is different from the target data in the data storage catalog;
and if the second content value is the same as the first content value, determining that the target data under the original storage catalog is the same as the target data under the data storage catalog.
In an alternative embodiment, after determining that the target data under the original storage directory is the same as the target data under the data storage directory, the method further comprises:
performing read-write test on the target data to obtain a test result;
When the test result represents that the target data is successfully read and written, performing failure marking on the database to be migrated;
and when the test result represents that the reading and writing of the target data fail, the target data is migrated again.
In a second aspect, the present invention provides a database migration apparatus, the apparatus mainly comprising: the system comprises a catalog acquisition module, a position identification module, a catalog updating module and a data migration module; the directory acquisition module is used for acquiring an original storage directory of the target data; the position identification module is used for identifying the storage position of the target data under the original storage catalog; the catalog updating module is used for updating the data storage catalog of the database to be migrated based on the original storage catalog when the storage position represents that the target data is stored in the database to be migrated; and the data migration module is used for migrating the target data to the database to be migrated when the storage position represents that the target data is not stored in the database to be migrated, and updating the data storage catalog of the database to be migrated based on the original storage catalog. Through the process, the data of the database partition on the standard hard disk of the nonvolatile memory can be migrated back to the mechanical hard disk, so that the data volume on the standard hard disk of the nonvolatile memory is reduced, the data recovery time consumption during the replacement of the standard hard disk of the nonvolatile memory is reduced, and the reliability of a storage system is improved.
In a third aspect, the present invention provides a computer device comprising: the database migration method comprises the steps of storing computer instructions in a memory and a processor, wherein the memory and the processor are in communication connection, the memory stores the computer instructions, and the processor executes the computer instructions, so that the database migration method of the first aspect or any implementation mode corresponding to the first aspect is executed.
In a fourth aspect, the present invention provides a computer readable storage medium having stored thereon computer instructions for causing a computer to perform the database migration method of the first aspect or any one of its corresponding embodiments.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are needed in the description of the embodiments or the prior art will be briefly described, and it is obvious that the drawings in the description below are some embodiments of the present invention, and other drawings can be obtained according to the drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic illustration of an application environment of an embodiment of the present invention;
FIG. 2 is a flow chart of a database migration method according to an embodiment of the present invention;
FIG. 3 is a flow chart of another database migration method according to an embodiment of the present invention;
FIG. 4 is a flow chart of yet another database migration method according to an embodiment of the present invention;
FIG. 5 is a flowchart of a database migration method according to an embodiment of the present invention;
FIG. 6 is a block diagram of a database migration apparatus according to an embodiment of the present invention;
fig. 7 is a schematic diagram of a hardware structure of a computer device according to an embodiment of the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments of the present invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The terms first and second in the description and claims of the invention and in the above-mentioned figures are used for distinguishing between different objects and not for describing a particular sequential order. Furthermore, the term "include" and any variations thereof is intended to cover non-exclusive protection. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed steps or elements but may include other steps or elements not listed or inherent to such process, method, article, or apparatus. The term "plurality" in the present invention may mean at least two, for example, two, three or more, and embodiments of the present invention are not limited.
Referring to fig. 1, fig. 1 is a schematic diagram of an application environment according to an embodiment of the present invention, where the schematic diagram includes a storage server 100 that may include a display 101, a processor 102, and a memory 103. The storage server 100 may be communicatively coupled to a storage management server 200 via a network 300, the storage management server 200 may be configured to provide services (e.g., management services, etc.) for computing programs installed on clients, and a database 201 may be provided on the storage management server 200 or independent of the storage management server 200 for providing data storage services for the storage management server 200. In addition, the storage management server 200 may have a processing engine 202 running therein, the processing engine 202 being operable to perform the steps performed by the storage management server 200.
Alternatively, the storage server 100 may be, but is not limited to, a terminal capable of calculating data, such as a mobile terminal (e.g., tablet computer), a notebook computer, a PC (Personal Computer ) or the like, and the network may include, but is not limited to, a wireless network or a wired network. Wherein the wireless network comprises: bluetooth, WIFI (Wireless Fidelity ) and other networks that enable wireless communications. The wired network may include, but is not limited to: wide area network, metropolitan area network, storage management server cluster. The storage management server 200 may include, but is not limited to, any hardware device capable of performing calculations.
In addition, in this embodiment, the database migration method may be applied, but not limited to, to an independent processing device with a relatively high processing capability, without data interaction. For example, the processing device may be, but is not limited to, a more processing-capable terminal device, i.e., the various operations of the database migration method described above may be integrated into a single processing device. The above is merely an example, and is not limited in any way in the present embodiment.
Alternatively, in this embodiment, the above database migration method may be performed by the storage management server 200, may be performed by the storage server 100, or may be performed by both the storage management server 200 and the storage server 100. The database migration method performed by the storage server 100 according to the embodiment of the present invention may be performed by a client installed thereon.
In accordance with an embodiment of the present invention, a database migration method embodiment is provided, it being noted that the steps shown in the flowchart of the figures may be performed in a computer system, such as a set of computer executable instructions, and, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in an order other than that shown or described herein.
In this embodiment, a database migration method is provided, which may be used in the foregoing storage server, where the storage server includes a target hard disk and a non-volatile memory standard hard disk, at least one database partition is provided in the non-volatile memory standard hard disk, for example, a database to be migrated is also provided in the target hard disk (for example, a mechanical hard disk), and a part of a database storage space is also provided in the target hard disk (for example, a database to be migrated is also provided in the target hard disk), and fig. 2 is a flowchart of a database migration method according to an embodiment of the present invention, as shown in fig. 2, where the flowchart includes the following steps:
step S201, an original storage directory of the target data is acquired.
In this embodiment, the original storage directory of the target data is obtained, so that the target data stored in the original storage directory is migrated to the target hard disk.
In an alternative implementation manner, first, monitoring hard disk information of a standard hard disk of a nonvolatile memory, and generating a database migration instruction when the data volume of data (such as target data) stored in the standard hard disk of the nonvolatile memory is greater than a threshold value before the service cycle of the standard hard disk of the nonvolatile memory reaches a life cycle; stopping the storage service based on the non-volatile memory standard hard disk and the target hard disk based on the database migration instruction) and confirming that the storage service has stopped. And then, confirming that the state of the target hard disk is normal, confirming that the standard hard disk of the nonvolatile memory is accessible and confirming that the storage server is in a fault domain through the hard disk detection command. Then, the original storage catalog for storing the target data stored in the database to be migrated is obtained through the catalog obtaining instruction.
Taking target data as a file as an example, firstly, stopping the storage service by an object storage service through a stop instruction, and after confirming that the service is stopped, carrying out environment confirmation, including confirming that the state of a target hard disk is normal through a hard disk detection command, confirming that a non-volatile memory standard hard disk is accessible, and confirming that a storage server does not exceed a fault domain. And after the environment confirmation is completed, adding a catalog acquisition instruction for acquiring catalog information of files recorded by the migration access database, wherein the instruction execution flow is that a file system of a storage server is opened, the file information under the super-high-speed space storage catalog, the high-speed space storage catalog and the slow-speed space storage catalog recorded by the file system is acquired, the file name and the number of the files under each catalog are output at a migration interface, and if the reading fails, the corresponding error information is output. It is understood that the original storage directory may be a collection of multiple spatial storage directories.
Step S202, the storage position of the target data under the original storage directory is identified.
In this embodiment, by identifying the storage location of the target data under the original storage directory, whether to migrate the target data or update the index directory of the target data is determined based on the storage location of the target data, so as to avoid the situation that the target data is repeatedly migrated or is incompletely migrated.
In step S203, when the storage location representation target data is stored in the database to be migrated, the data storage directory of the database to be migrated is updated based on the original storage directory.
In this embodiment, when the storage location of the target data is to be migrated into the database under the original storage directory, the data storage directory to be migrated into the database is updated based on the original storage directory, so that the update of the target data storage directory is realized, and the situation that the data read-write error occurs due to no migration of the target data directory after the subsequent migration of the database of the standard hard disk with nonvolatile memory is completed is avoided.
In an alternative implementation manner, an original storage directory of the target data storage is checked first, if the target data is stored under the original storage directory, but the target data is actually stored in the database to be migrated, the data storage directory of the database to be migrated is updated based on the original storage directory, so that the directory indexes of the target data and the original storage directory are updated into the indexes of the target data and the data storage directory, and the content of the original storage directory corresponding to the database to be migrated is deleted.
In the implementation, based on step S201, if a file is stored under the slow space storage directory and the file is in the database to be migrated, the compression instruction is increased or decreased to compress the file stored under the slow space storage directory into the database to be migrated, and update the index of the file and the slow space storage directory to be the data storage directory of the database to be migrated, where the data storage directory may be the high-speed space storage directory of the high-speed storage space in the database to be migrated. If the file is stored in the slow space storage catalog, and the file is in the database to be migrated, opening a file system of a storage server in the distributed storage system and the database to be migrated, calling a connection interface between the database to be migrated and the file system, updating catalog index information of the file in the slow space storage catalog, updating the catalog index of the file in the slow space storage catalog into a high-speed space storage catalog of a high-speed storage space in the database to be migrated, executing a failure stopping flow, and outputting error information at a migration interface.
Further, it can also check if the index of the file under the slow-speed space storage directory has been updated to the high-speed space storage directory of the high-speed storage space in the database to be migrated, the target data not stored in the database to be migrated can be migrated to the database to be migrated until the migration of the database to be migrated is completed, if the index of the file under the slow-speed space storage directory has failed to be updated, the migration process of migrating the target data not stored in the database to be migrated to the database to be migrated is stopped, and error information is output at the migration interface.
In step S204, when the storage location indicates that the target data is not stored in the database to be migrated, the target data is migrated to the database to be migrated, and the data storage directory of the database to be migrated is updated based on the original storage directory.
In this embodiment, when the target data is not stored in the database to be migrated under the original storage directory, the target data is migrated to the database to be migrated, and the data storage directory of the database to be migrated is updated based on the original storage directory, so as to migrate the target data, further migrate the data of the database to be migrated on the standard hard disk of the nonvolatile memory back to the target hard disk, reduce the data amount on the standard hard disk of the nonvolatile memory, thereby reducing the data recovery time consumption when the standard hard disk of the nonvolatile memory is replaced, and increasing the reliability of the storage system.
In an alternative implementation manner, an original storage directory of the target data storage is checked first, if target data is stored under the original storage directory and the target data is stored in the database to be migrated, the target data is migrated to the database to be migrated, the data storage directory of the database to be migrated is updated based on the original storage directory, so that an index of the target data is updated to the data storage directory, and the content of the original storage directory corresponding to the database to be migrated is deleted.
In the implementation, based on step S201, a data migration instruction is added first, so as to migrate all files stored on the non-volatile memory standard hard disk under the high-speed space storage directory and the slow-speed space storage directory to the target hard disk and update the directory index of the files.
Further, checking the original storage catalogue and the data storage catalogue, if the catalogue does not exist or is inaccessible due to catalog failure, outputting error information at a migration interface, and stopping migration service; wherein the absence of the directory includes being deleted or corrupted. And then acquiring the capacity used by the files stored on the non-volatile memory standard hard disk under the current high-speed space storage catalog and the low-speed space storage catalog and the capacity allocated by the data storage catalog on the target hard disk, judging whether the capacity of the allocated space of the data storage catalog can meet the requirement, if the capacity of the allocated space of the data storage catalog does not meet the requirement, the data storage catalog applies for the space again, and stopping the database migration flow and outputting error information at the migration interface if the capacity of the allocated space of the data storage catalog cannot be applied for enough space. And finally, the file system service acquires all files in the database to be migrated, namely, reads the files stored on the standard hard disk of the nonvolatile memory under the conditions of the ultra-high speed space storage catalogue and the high-speed space storage, writes the read files on the target hard disk, updates the catalogue index information of the files in the database to be migrated after the files are written, updates the log files of the database to be migrated after the migration of all the files is completed, and marks the partition failure of the database to be migrated on the standard hard disk of the nonvolatile memory. And when the file is read from the standard hard disk of the nonvolatile memory or written to the target hard disk, an error occurs, the migration action is stopped, and error information is output.
According to the database migration method provided by the embodiment, firstly, the original storage catalog of the target data is obtained so as to facilitate migration of the target data stored in the original storage catalog to the target hard disk; the storage position of the target data under the original storage directory is identified, so that whether the target data is migrated or the index directory of the target data is updated is determined based on the storage position of the target data, and the situation that the target data is repeatedly migrated or is not completely migrated is avoided; updating the data storage catalogue of the target data to be migrated into the database based on the original storage catalogue when the storage position of the target data is to be migrated into the database under the original storage catalogue, so that the updating of the target data storage catalogue is realized, and the situation that data read-write errors occur due to the fact that the catalogue of the target data is not migrated after the database of the non-volatile memory standard hard disk is migrated in the follow-up process is avoided; and migrating the target data to the database to be migrated when the target data is not stored in the database to be migrated under the original storage catalog, and updating the data storage catalog of the database to be migrated based on the original storage catalog so as to realize the migration of the target data. Therefore, the invention can realize that the data to be migrated into the database on the standard hard disk of the nonvolatile memory is migrated back to the target hard disk (such as a mechanical hard disk), and reduce the data quantity on the standard hard disk of the nonvolatile memory, thereby reducing the data recovery time consumption when the standard hard disk of the nonvolatile memory is replaced and increasing the reliability of a storage system.
In this embodiment, a database migration method is provided, which may be used in the foregoing storage server, where the storage server includes a target hard disk and a non-volatile memory standard hard disk, at least one database partition, such as a database to be migrated, is disposed in the non-volatile memory standard hard disk, and a portion of a database storage space is also disposed in the target hard disk, such as a database to be migrated, and fig. 3 is a flowchart of a database migration method according to an embodiment of the present invention, as shown in fig. 3, where the flowchart includes the following steps:
step S301, an original storage directory of the target data is acquired.
In this embodiment, the original storage directory of the target data is obtained, so that the target data stored in the original storage directory is migrated to the target hard disk.
Please refer to step S201 in the embodiment shown in fig. 2 in detail, which is not described herein.
Step S302, the storage position of the target data under the original storage directory is identified.
In this embodiment, by identifying the storage location of the target data under the original storage directory, whether to migrate the target data or update the index directory of the target data is determined based on the storage location of the target data, so as to avoid the situation that the target data is repeatedly migrated or is incompletely migrated.
In step S303, when the storage location characterizing target data is stored in the database to be migrated, the data storage directory of the database to be migrated is updated based on the original storage directory.
Specifically, the step S303 includes:
in step S3031, the directory index of the target data and the original storage directory is obtained.
In this embodiment, when the storage location of the target data in the original storage directory is to be migrated into the database, the directory indexes of the target data and the original storage directory are obtained, so as to obtain the original directory index information of the target data.
In step S3032, the directory index is updated to the index of the target data and data storage directory.
In this embodiment, when the storage location of the target data in the original storage directory is to be migrated into the database, the directory indexes of the target data and the original storage directory are updated to be the indexes of the target data and the data storage directory, so that the update of the target data storage directory is realized, and the situation that the data read-write error occurs because the directory of the target data is not migrated after the subsequent migration of the database of the standard hard disk with nonvolatile memory is completed is avoided.
In step S304, when the storage location indicates that the target data is not stored in the database to be migrated, the target data is migrated to the database to be migrated, and the data storage directory of the database to be migrated is updated based on the original storage directory.
In this embodiment, when the target data is not stored in the database to be migrated under the original storage directory, the target data is migrated to the database to be migrated, and the data storage directory of the database to be migrated is updated based on the original storage directory, so as to migrate the target data, further migrate the data of the database to be migrated on the standard hard disk of the nonvolatile memory back to the target hard disk, reduce the data amount on the standard hard disk of the nonvolatile memory, thereby reducing the data recovery time consumption when the standard hard disk of the nonvolatile memory is replaced, and increasing the reliability of the storage system.
According to the database migration method provided by the embodiment, firstly, the original storage catalog of the target data is obtained so as to facilitate migration of the target data stored in the original storage catalog to the target hard disk; the storage position of the target data under the original storage directory is identified, so that whether the target data is migrated or the index directory of the target data is updated is determined based on the storage position of the target data, and the situation that the target data is repeatedly migrated or is not completely migrated is avoided; updating the data storage catalogue of the target data to be migrated into the database based on the original storage catalogue when the storage position of the target data is to be migrated into the database under the original storage catalogue, so that the updating of the target data storage catalogue is realized, and the situation that data read-write errors occur due to the fact that the catalogue of the target data is not migrated after the database of the non-volatile memory standard hard disk is migrated in the follow-up process is avoided; and migrating the target data to the database to be migrated when the target data is not stored in the database to be migrated under the original storage catalog, and updating the data storage catalog of the database to be migrated based on the original storage catalog so as to realize the migration of the target data. Therefore, the invention can realize that the data to be migrated into the database on the standard hard disk of the nonvolatile memory is migrated back to the target hard disk (such as a mechanical hard disk), and reduce the data quantity on the standard hard disk of the nonvolatile memory, thereby reducing the data recovery time consumption when the standard hard disk of the nonvolatile memory is replaced and increasing the reliability of a storage system.
In this embodiment, a database migration method is provided, which may be used in the foregoing storage server, where the storage server includes a target hard disk and a non-volatile memory standard hard disk, at least one database partition, such as a database to be migrated, is disposed in the non-volatile memory standard hard disk, and a portion of a database storage space, such as a database to be migrated, is also disposed in the target hard disk, and fig. 4 is a flowchart of a database migration method according to an embodiment of the present invention, as shown in fig. 4, where the flowchart includes the following steps:
step S401, an original storage directory of the target data is acquired.
In this embodiment, the original storage directory of the target data is obtained, so that the target data stored in the original storage directory is migrated to the target hard disk.
Please refer to step S201 in the embodiment shown in fig. 2 in detail, which is not described herein.
Step S402, identify the storage location of the target data under the original storage directory.
In this embodiment, by identifying the storage location of the target data under the original storage directory, whether to migrate the target data or update the index directory of the target data is determined based on the storage location of the target data, so as to avoid the situation that the target data is repeatedly migrated or is incompletely migrated.
In step S403, when the storage location characterizing target data is stored in the database to be migrated, the data storage directory of the database to be migrated is updated based on the original storage directory.
In this embodiment, when the storage location of the target data is to be migrated into the database under the original storage directory, the data storage directory to be migrated into the database is updated based on the original storage directory, so that the update of the target data storage directory is realized, and the situation that the data read-write error occurs due to no migration of the target data directory after the subsequent migration of the database of the standard hard disk with nonvolatile memory is completed is avoided.
Please refer to step S303 in the embodiment shown in fig. 3 in detail, which is not described herein.
In step S404, when the storage location representation target data is not stored in the database to be migrated, validity of the original storage directory and the data storage directory is determined to obtain a validity determination result.
In this embodiment, when the target data in the original storage directory is not stored in the database to be migrated, validity of the original storage directory and the data storage directory is determined, so as to provide a judgment standard for whether the target data is migrated subsequently.
In step S405, when the validity determination result indicates that the original storage directory and the data storage directory exist and are not invalid, the target data is migrated to the database to be migrated.
In this embodiment, when the original storage directory and the data storage directory exist and do not fail, the target data is migrated to the database to be migrated, so as to avoid the situation that the migration of the target data fails due to the loss or failure of the original storage directory and the data storage directory.
Step S406, when the validity determination result indicates that the original storage directory and the data storage directory do not exist or fail, migration error information is output, and migration of the target data is stopped.
In this embodiment, when the original storage directory and the data storage directory do not exist or fail, migration error information is output, and migration of target data is stopped, so that the problem of server crash caused by forced data migration is avoided.
It can be understood that when the target data is not stored in the database to be migrated under the original storage catalog, the target data is migrated to the database to be migrated, and the data storage catalog of the database to be migrated is updated based on the original storage catalog, so that the target data is migrated, the data to be migrated in the database on the standard hard disk of the nonvolatile memory is migrated back to the target hard disk, the data volume on the standard hard disk of the nonvolatile memory is reduced, the data recovery time consumption during the standard hard disk replacement of the nonvolatile memory is reduced, and the reliability of the storage system is increased.
Please refer to step S204 in the embodiment shown in fig. 2 in detail, which is not described herein.
According to the database migration method provided by the embodiment, firstly, the original storage catalog of the target data is obtained so as to facilitate migration of the target data stored in the original storage catalog to the target hard disk; the storage position of the target data under the original storage directory is identified, so that whether the target data is migrated or the index directory of the target data is updated is determined based on the storage position of the target data, and the situation that the target data is repeatedly migrated or is not completely migrated is avoided; updating the data storage catalogue of the target data to be migrated into the database based on the original storage catalogue when the storage position of the target data is to be migrated into the database under the original storage catalogue, so that the updating of the target data storage catalogue is realized, and the situation that data read-write errors occur due to the fact that the catalogue of the target data is not migrated after the database of the non-volatile memory standard hard disk is migrated in the follow-up process is avoided; determining the validity of the original storage catalogue and the data storage catalogue when target data is not stored in the database to be migrated under the original storage catalogue, and providing a judgment standard for whether the target data is migrated subsequently; when the original storage catalogue and the data storage catalogue exist and are not invalid, migrating target data to a database to be migrated, so that the situation that the migration of the target data fails due to the loss or invalidation of the original storage catalogue and the data storage catalogue is avoided; when the original storage catalogue and the data storage catalogue do not exist or fail, migration error information is output, and migration of target data is stopped, so that the problem that a server is crashed due to forced data migration is avoided. Therefore, the invention can realize that the data to be migrated into the database on the standard hard disk of the nonvolatile memory is migrated back to the target hard disk (such as a mechanical hard disk), and reduce the data quantity on the standard hard disk of the nonvolatile memory, thereby reducing the data recovery time consumption when the standard hard disk of the nonvolatile memory is replaced and increasing the reliability of a storage system.
In this embodiment, a database migration method is provided, which may be used in the foregoing storage server, where the storage server includes a target hard disk and a non-volatile memory standard hard disk, at least one database partition, such as a database to be migrated, is disposed in the non-volatile memory standard hard disk, and a portion of a database storage space is also disposed in the target hard disk, such as a database to be migrated, and fig. 5 is a flowchart of a database migration method according to an embodiment of the present invention, as shown in fig. 5, where the flowchart includes the following steps:
in step S501, an original storage directory of target data is acquired.
In this embodiment, the original storage directory of the target data is obtained, so that the target data stored in the original storage directory is migrated to the target hard disk.
Please refer to step S201 in the embodiment shown in fig. 2 in detail, which is not described herein.
Step S502, identify the storage location of the target data under the original storage directory.
In this embodiment, by identifying the storage location of the target data under the original storage directory, whether to migrate the target data or update the index directory of the target data is determined based on the storage location of the target data, so as to avoid the situation that the target data is repeatedly migrated or is incompletely migrated.
In step S503, when the storage location representation target data is not stored in the database to be migrated, validity of the original storage directory and the data storage directory is determined, so as to obtain a validity determination result.
In this embodiment, when the target data in the original storage directory is not stored in the database to be migrated, validity of the original storage directory and the data storage directory is determined, so as to provide a judgment standard for whether the target data is migrated subsequently.
In step S504, when the validity determination result indicates that the original storage directory and the data storage directory exist and are not invalid, the target data is migrated to the database to be migrated.
In this embodiment, when the original storage directory and the data storage directory exist and do not fail, the target data is migrated to the database to be migrated, so as to avoid the situation that the migration of the target data fails due to the loss or failure of the original storage directory and the data storage directory.
Specifically, the step S504 includes:
in step S5041, the space capacity of the first storage space occupied before the migration of the target data and the space capacity of the second storage space allocated by the database to be migrated are obtained.
In this embodiment, the target data is migrated to the database to be migrated by acquiring the space capacity of the first storage space occupied before the migration of the target data and the space capacity of the second storage space allocated to the database to be migrated, so that the result of comparing the space capacity of the first storage space with the space capacity of the second storage space is convenient.
In step S5042, the space capacity of the first storage space is compared with the space capacity of the second storage space, and the target data is migrated to the database to be migrated based on the result of the capacity comparison.
In this embodiment, the space capacity of the first storage space is compared with the space capacity of the second storage space, and the target data is migrated to the database to be migrated based on the capacity comparison result, so as to realize migration of the target data.
In an alternative embodiment, when the capacity comparison result indicates that the space capacity of the first storage space is greater than or equal to the space capacity of the second storage space, migrating the target data to the database to be migrated; when the capacity comparison result indicates that the space capacity of the first storage space is smaller than the space capacity of the second storage space, the application of the storage space to the database to be migrated is performed based on the space capacity of the first storage space.
In an optional implementation manner, after migrating the target data to the database to be migrated and updating the data storage directory of the database to be migrated based on the original storage directory, a first content value corresponding to the target data in the original storage directory may also be obtained; calculating a second content value of the content limited by the target data under the data storage catalog, and comparing the second content value with the first content value; if the second content value is different from the first content value, determining that the target data in the original storage catalog is different from the target data in the data storage catalog; and if the second content value is the same as the first content value, determining that the target data under the original storage catalog is the same as the target data under the data storage catalog. The calculation of the first content value and the second content value may be obtained by a hash calculation method, or may be obtained by a comparison algorithm of data similarity. It can be understood that the consistency of the target data before and after the migration is judged by comparing the first content value with the second content value, so that the situation that the later data read-write errors or inconsistencies are caused by data loss or messy codes in the data migration process is avoided.
In an optional implementation manner, after determining that the target data in the original storage directory is the same as the target data in the data storage directory, a read-write test can be performed on the target data to obtain a test result; when the test result represents that the target data is successfully read and written, performing failure marking on the database to be migrated; and when the test result represents that the reading and writing of the target data fail, the target data is migrated again. The read-write test of the target data can be a read-write test of continuous data or a read-write test of random data. It can be understood that when the test result represents that the target data is successfully read and written, the database to be migrated is marked with failure, so that the condition that the database to be migrated in the standard hard disk of the nonvolatile memory is reused can be avoided, and a necessary condition is provided for the replacement of the standard hard disk of the subsequent nonvolatile memory. And when the test result represents that the read-write of the target data fails, the target data is migrated again, so that the migration of the database to be migrated is finally realized.
Step S505, when the validity determination result indicates that the original storage directory and the data storage directory do not exist or fail, migration error information is output, and migration of target data is stopped.
In this embodiment, when the original storage directory and the data storage directory do not exist or fail, migration error information is output, and migration of target data is stopped, so that the problem of server crash caused by forced data migration is avoided.
According to the database migration method provided by the embodiment, firstly, the original storage catalog of the target data is obtained so as to facilitate migration of the target data stored in the original storage catalog to the target hard disk; the storage position of the target data under the original storage directory is identified, so that whether the target data is migrated or the index directory of the target data is updated is determined based on the storage position of the target data, and the situation that the target data is repeatedly migrated or is not completely migrated is avoided; determining the validity of the original storage catalogue and the data storage catalogue when target data is not stored in the database to be migrated under the original storage catalogue, and providing a judgment standard for whether the target data is migrated subsequently; when the original storage catalogue and the data storage catalogue do not exist or fail, migration error information is output, and migration of target data is stopped, so that the problem that a server is crashed due to forced data migration is avoided. Therefore, the invention can realize that the data to be migrated into the database on the standard hard disk of the nonvolatile memory is migrated back to the target hard disk (such as a mechanical hard disk), and reduce the data quantity on the standard hard disk of the nonvolatile memory, thereby reducing the data recovery time consumption when the standard hard disk of the nonvolatile memory is replaced and increasing the reliability of a storage system.
In this embodiment, a database migration device is further provided, and the device is used to implement the foregoing embodiments and preferred embodiments, and will not be described in detail. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. While the means described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.
The present embodiment provides a database migration apparatus, as shown in fig. 6, including:
the catalog acquisition module 601 is configured to acquire an original storage catalog of target data.
The location identification module 602 is configured to identify a storage location of the target data under the original storage directory.
The catalog updating module 603 is configured to update the data storage catalog of the database to be migrated based on the original storage catalog when the storage location representation target data is stored in the database to be migrated.
In some alternative embodiments, the catalog update module 603 includes:
and the index acquisition unit is used for acquiring the target data and the directory index of the original storage directory.
And the index updating unit is used for updating the index of the catalog into the index of the target data and the data storage catalog.
The data migration module 604 is configured to migrate the target data to the database to be migrated when the storage location indicates that the target data is not stored in the database to be migrated, and update the data storage directory of the database to be migrated based on the original storage directory.
In some alternative embodiments, the data migration module 604 includes:
and the validity determining unit is used for determining the validity of the original storage catalogue and the data storage catalogue so as to obtain a validity determining result.
And the data migration unit is used for migrating the target data to the database to be migrated when the validity determination result indicates that the original storage directory and the data storage directory exist and are not invalid.
Optionally, when migrating the target data to the database to be migrated, firstly acquiring the space capacity of the first storage space occupied by the target data before migration and the space capacity of the second storage space allocated by the database to be migrated; and comparing the space capacity of the first storage space with the space capacity of the second storage space, and migrating the target data to the database to be migrated based on the capacity comparison result.
Specifically, when the capacity comparison result indicates that the space capacity of the first storage space is larger than or equal to the space capacity of the second storage space, migrating the target data to a database to be migrated; when the capacity comparison result indicates that the space capacity of the first storage space is smaller than the space capacity of the second storage space, the application of the storage space to the database to be migrated is performed based on the space capacity of the first storage space.
And the stopping unit is used for outputting migration error information and stopping migration of target data when the validity determining result indicates that the original storage directory and the data storage directory do not exist or fail.
In some alternative embodiments, the apparatus further comprises:
the consistency determining module is used for acquiring a first content value corresponding to target data in the original storage catalog; calculating a second content value of the content limited by the target data under the data storage catalog, and comparing the second content value with the first content value; if the second content value is different from the first content value, determining that the target data in the original storage catalog is different from the target data in the data storage catalog; and if the second content value is the same as the first content value, determining that the target data under the original storage catalog is the same as the target data under the data storage catalog.
The read-write test module is used for performing read-write test on the target data to obtain a test result; when the test result represents that the target data is successfully read and written, performing failure marking on the database to be migrated; and when the test result represents that the reading and writing of the target data fail, the target data is migrated again.
Further functional descriptions of the above respective modules and units are the same as those of the above corresponding embodiments, and are not repeated here.
The database migration apparatus in this embodiment is presented in the form of a functional unit, where a unit refers to an ASIC (application specific integrated circuit) circuit, a processor and a memory that execute one or more software or firmware programs, and/or other devices that can provide the above functions.
The embodiment of the invention also provides computer equipment, which is provided with the database migration device shown in the figure 6.
Referring to fig. 7, fig. 7 is a schematic structural diagram of a computer device according to an alternative embodiment of the present invention, as shown in fig. 7, the computer device includes: one or more processors 10, memory 20, and interfaces for connecting the various components, including high-speed interfaces and low-speed interfaces. The various components are communicatively coupled to each other using different buses and may be mounted on a common motherboard or in other manners as desired. The processor may process instructions executing within the computer device, including instructions stored in or on memory to display graphical information of the GUI on an external input/output device, such as a display device coupled to the interface. In some alternative embodiments, multiple processors and/or multiple buses may be used, if desired, along with multiple memories and multiple memories. Also, multiple computer devices may be connected, each providing a portion of the necessary operations (e.g., as a storage server array, a set of blade storage servers, or a multiprocessor system). One processor 10 is illustrated in fig. 7.
The processor 10 may be a central processor, a network processor, or a combination thereof. The processor 10 may further include a hardware chip, among others. The hardware chip may be an application specific integrated circuit, a programmable logic device, or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general-purpose array logic, or any combination thereof.
Wherein the memory 20 stores instructions executable by the at least one processor 10 to cause the at least one processor 10 to perform a method for implementing the embodiments described above.
The memory 20 may include a storage program area that may store an operating system, at least one application program required for functions, and a storage data area; the storage data area may store data created from the use of the computer device of the presentation of a sort of applet landing page, and the like. In addition, the memory 20 may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid-state storage device. In some alternative embodiments, memory 20 may optionally include memory located remotely from processor 10, which may be connected to the computer device via a network. Examples of such networks include, but are not limited to, the internet, intranets, server clusters, mobile communication networks, and combinations thereof.
Memory 20 may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as flash memory, hard disk, or solid state disk; the memory 20 may also comprise a combination of the above types of memories.
The computer device also includes a communication interface 30 for the computer device to communicate with other devices or communication networks.
The embodiments of the present invention also provide a computer readable storage medium, and the method according to the embodiments of the present invention described above may be implemented in hardware, firmware, or as a computer code which may be recorded on a storage medium, or as original stored in a remote storage medium or a non-transitory machine readable storage medium downloaded through a network and to be stored in a local storage medium, so that the method described herein may be stored on such software process on a storage medium using a general purpose computer, a special purpose processor, or programmable or special purpose hardware. The storage medium can be a magnetic disk, an optical disk, a read-only memory, a random access memory, a flash memory, a hard disk, a solid state disk or the like; further, the storage medium may also comprise a combination of memories of the kind described above. It will be appreciated that a computer, processor, microprocessor controller or programmable hardware includes a storage element that can store or receive software or computer code that, when accessed and executed by the computer, processor or hardware, implements the methods illustrated by the above embodiments.
Although embodiments of the present invention have been described in connection with the accompanying drawings, various modifications and variations may be made by those skilled in the art without departing from the spirit and scope of the invention, and such modifications and variations fall within the scope of the invention as defined by the appended claims.
Claims (10)
1. A method of database migration, the method comprising:
acquiring an original storage catalog of target data;
identifying the storage position of the target data under the original storage directory;
updating a data storage catalog of the database to be migrated based on the original storage catalog when the storage position characterizes the target data to be stored in the database to be migrated;
and when the storage position characterizes that the target data is not stored in the database to be migrated, migrating the target data to the database to be migrated, and updating a data storage catalog of the database to be migrated based on the original storage catalog.
2. The method of claim 1, wherein updating the data store directory of the database to be migrated based on the original store directory comprises:
acquiring a catalog index of the target data and the original storage catalog;
Updating the directory index to the index of the target data and the data storage directory.
3. The method of claim 1, wherein prior to migrating the target data to the database to be migrated, the method further comprises:
determining the validity of the original storage catalogue and the data storage catalogue to obtain a validity determination result;
when the validity determination result represents that the original storage catalogue and the data storage catalogue exist and are not invalid, executing the step of migrating the target data to the database to be migrated;
and outputting migration error information and stopping migration of the target data when the validity determination result represents that the original storage directory and the data storage directory do not exist or fail.
4. The method of claim 3, wherein the migrating the target data to the database to be migrated comprises:
acquiring the space capacity of a first storage space occupied by the target data before migration and the space capacity of a second storage space allocated by the database to be migrated;
and comparing the space capacity of the first storage space with the space capacity of the second storage space, and migrating the target data to the database to be migrated based on a capacity comparison result.
5. The method of claim 4, wherein the migrating the target data to the database to migrate based on the capacity comparison result comprises:
when the capacity comparison result represents that the space capacity of the first storage space is larger than or equal to the space capacity of the second storage space, migrating the target data to the database to be migrated;
and when the capacity comparison result represents that the space capacity of the first storage space is smaller than the space capacity of the second storage space, applying for the storage space to the database to be migrated based on the space capacity of the first storage space.
6. The method of any one of claims 1 to 5, wherein after the migrating the target data to the database to be migrated and updating the data storage directory of the database to be migrated based on the original storage directory, the method further comprises:
acquiring a first content value corresponding to the target data under an original storage directory;
calculating a second content value of the content limited by the target data under the data storage directory, and comparing the second content value with the first content value;
If the second content value is different from the first content value, determining that the target data in the original storage directory is different from the target data in the data storage directory;
and if the second content value is the same as the first content value, determining that the target data under the original storage directory is the same as the target data under the data storage directory.
7. The method of claim 6, wherein after the determining that the target data under the original storage directory is the same as the target data under the data storage directory, the method further comprises:
performing read-write test on the target data to obtain a test result;
when the test result represents that the target data is successfully read and written, performing failure marking on the database to be migrated;
and when the test result represents that the reading and writing of the target data fail, the target data is migrated again.
8. A database migration apparatus for use in a database, the apparatus comprising:
the catalog acquisition module is used for acquiring an original storage catalog of the target data;
the position identification module is used for identifying the storage position of the target data under the original storage directory;
The catalog updating module is used for updating the data storage catalog of the database to be migrated based on the original storage catalog when the storage position characterizes the target data to be stored in the database to be migrated;
and the data migration module is used for migrating the target data to the database to be migrated when the storage position characterizes that the target data is not stored in the database to be migrated, and updating the data storage catalog of the database to be migrated based on the original storage catalog.
9. A computer device, comprising:
a memory and a processor in communication with each other, the memory having stored therein computer instructions which, upon execution, cause the processor to perform the method of any of claims 1 to 7.
10. A computer readable storage medium having stored thereon computer instructions for causing a computer to perform the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311099145.7A CN117131014A (en) | 2023-08-29 | 2023-08-29 | Database migration method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311099145.7A CN117131014A (en) | 2023-08-29 | 2023-08-29 | Database migration method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117131014A true CN117131014A (en) | 2023-11-28 |
Family
ID=88860931
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311099145.7A Pending CN117131014A (en) | 2023-08-29 | 2023-08-29 | Database migration method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117131014A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117591495A (en) * | 2024-01-18 | 2024-02-23 | 中核武汉核电运行技术股份有限公司 | Data storage method and system for nuclear power historical data migration |
-
2023
- 2023-08-29 CN CN202311099145.7A patent/CN117131014A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117591495A (en) * | 2024-01-18 | 2024-02-23 | 中核武汉核电运行技术股份有限公司 | Data storage method and system for nuclear power historical data migration |
| CN117591495B (en) * | 2024-01-18 | 2024-05-03 | 中核武汉核电运行技术股份有限公司 | Data storage method and system for nuclear power historical data migration |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11481121B2 (en) | Physical media aware spacially coupled journaling and replay | |
| JP6854885B2 (en) | Systems and methods for repairing images in deduplication storage | |
| US9223788B2 (en) | File system consistency check on part of a file system | |
| US8924664B2 (en) | Logical object deletion | |
| CN108701048B (en) | Data loading method and device | |
| US20110072224A1 (en) | Snapshot metadata management in a storage system | |
| US10489289B1 (en) | Physical media aware spacially coupled journaling and trim | |
| CN107870802B (en) | Virtual machine migration method and device | |
| US9519545B2 (en) | Storage drive remediation in a raid system | |
| US9436554B2 (en) | Information processing apparatus and data repairing method | |
| CN117131014A (en) | Database migration method, device, equipment and storage medium | |
| JP2007133544A (en) | Failure information analysis method and its implementation device | |
| CN110019063B (en) | Method for computing node data disaster recovery playback, terminal device and storage medium | |
| US9588884B2 (en) | Systems and methods for in-place reorganization of device storage | |
| CN111966531B (en) | Data snapshot method and device, computer equipment and storage medium | |
| US8595271B1 (en) | Systems and methods for performing file system checks | |
| EP3264254A1 (en) | System and method for a simulation of a block storage system on an object storage system | |
| CN113312205A (en) | Data verification method and device, storage medium and computer equipment | |
| CN111930707B (en) | Method and system for correcting drive letter of windows cloud migration | |
| CN114328373A (en) | Method, electronic device and computer program product for managing a file system | |
| CN113590309B (en) | Data processing method, device, equipment and storage medium | |
| CN115617580B (en) | Incremental backup and recovery method and system based on Shared SST (SST) file | |
| CN109542359B (en) | Data reconstruction method, device, equipment and computer readable storage medium | |
| KR20190003091A (en) | Device and method on file system journaling using atomic operation | |
| CN117539386A (en) | Disk array data processing method, device, 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 |