Data migration method and device for heterogeneous object storage, equipment, storage medium and program product

Abstract

The invention discloses a data migration method and device for heterogeneous object storage, equipment, a storage medium and a program product, and relates to the technical field of data management, and the method comprises the following steps: migrating stock data before an initial timestamp in source object storage equipment to target object storage equipment; according to the data operation record in the source object log, the incremental data in the source object storage device is migrated to the target object storage device, and the incremental data in the target object storage device is synchronized to the source object storage device; when the incremental data begins to migrate, switching and distributing the current traffic of the incremental data in a source object storage device and a target object storage device; and after the current traffic is switched and distributed, forwarding the subsequent traffic oriented to the source object storage device to the target object for storage. The consistency and integrity of data migration are ensured through a source object log; and uninterrupted migration of data can be realized by migrating and synchronizing stock data, incremental data and traffic.

Description

Technical Field

[0001] The present application relates to the field of data management technology, and in particular to a data migration method, device, equipment, storage medium and program product for heterogeneous object storage. Background Art

[0002] With the development of cloud computing and big data technology, object storage has been widely used in various systems as an efficient and reliable storage method. However, different types of object storage facilities (such as FTP, UDS, ECS, S3, etc.) often have different access interfaces, and they have their own advantages and disadvantages in different scenarios. However, user systems often need to replace different types of storage facilities during development. When user systems need to switch storage facilities, such as switching from UDS to ECS, they often face problems such as complex data migration and high risks.

[0003] The existing technical solutions have the problem of long migration time and impact on business continuity.

[0004] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention

[0005] The main purpose of this application is to provide a data migration method, device, equipment, storage medium and program product for heterogeneous object storage, aiming to solve the technical problems of long migration time and impact on business continuity.

[0006] To achieve the above object, the present application proposes a data migration method for heterogeneous object storage, the method comprising:

[0007] Migrate the existing data before the initial timestamp in the source object storage device to the target object storage device;

[0008] Migrate the incremental data in the source object storage device to the target object storage device according to the data operation record in the source object log, and synchronize the incremental data in the target object storage device to the source object storage device;

[0009] When the incremental data starts to migrate, the current traffic of the incremental data is switched and distributed between the source object storage device and the target object storage device;

[0010] When the current traffic is switched and distributed, the subsequent traffic to the source object storage device is forwarded to the target object storage.

[0011] In one embodiment, before the step of migrating the stock data before the initial timestamp in the source object storage device to the target object storage device, the step further includes:

[0012] A source object log is created based on an operation on a source object storage device, wherein the source object log includes at least one of a source level 1 log, a source level 2 log, a source level 3 log, and a source level 4 log.

[0013] In one embodiment, the step of migrating the stock data before the initial timestamp in the source object storage device to the target object storage device includes:

[0014] determining an initial timestamp in a source object storage device;

[0015] Migrate the existing data before the initial timestamp of the source object storage device to the target object storage device;

[0016] Migrate the logs before the initial timestamp recorded in the source secondary log in the source object log to the source third-level log.

[0017] In one embodiment, the step of migrating incremental data in the source object storage device to the target object storage device according to the data operation record in the source object log includes:

[0018] Read the log records after the initial timestamp in the source secondary log of the source object log;

[0019] Determine the data operation of the incremental data based on the log records after the initial timestamp in the source secondary log;

[0020] According to the data operation of the incremental data, corresponding target operations are performed on the incremental data in the target object storage device.

[0021] In one embodiment, when the incremental data starts to be migrated, before the step of switching and distributing the current traffic of the incremental data in the source object storage device and the target object storage device, the method further includes:

[0022] When the target direction of the current traffic switching distribution is the target object storage device, the current operation state of the current operation object is determined according to the source object log recording the current operation object;

[0023] According to the current operation state of the current operation object, a switching distribution direction of the current operation object flow writing is determined.

[0024] In one embodiment, the step of determining the current operation state of the current operation object according to the source object log recording the current operation object includes:

[0025] When the log recording the current operation object is a source level 1 log, the current operation state of the current operation object is pre-written to the source object storage device;

[0026] When the log recording the current operation object is a source secondary log, the current operation state of the current operation object is pre-synchronized from the source object storage device to the target object storage device;

[0027] When the log recording the current operation object is a source level 4 log, the current operation status of the current operation object is that synchronization from the source object storage device to the target object storage device fails;

[0028] When the source object log does not record the log of the current operation object, the current operation state of the current operation object is a no operation state.

[0029] In one embodiment, the step of determining the switching distribution direction of the current operation object flow writing according to the current operation state of the current operation object includes:

[0030] When the current operation state of the current operation object is pre-writing to the source object storage, the switching distribution direction of the current operation object traffic writing is the source object storage device;

[0031] When the current operation state of the current operation object is pre-synchronization from the source object storage to the target object storage, the switching distribution direction of the current operation object traffic write is the source object storage device;

[0032] When the current operation state of the current operation object is that the synchronization from the source object storage to the target object storage fails, the switching distribution direction of the current operation object traffic write is the source object storage device;

[0033] When the current operation state of the current operation object is the no operation state, the switching distribution direction of the current operation object traffic write is the target object storage device.

[0034] In addition, to achieve the above-mentioned purpose, the present application also proposes a data migration device for heterogeneous object storage, and the data migration device for heterogeneous object storage includes:

[0035] The stock migration module is used to migrate the stock data before the initial timestamp in the source object storage device to the target object storage device;

[0036] An incremental migration module, used to migrate incremental data in a source object storage device to a target object storage device and synchronize incremental data in a target object storage device to a source object storage device according to data operation records in a source object log;

[0037] A traffic switching module, used for switching and distributing the current traffic of the incremental data between the source object storage device and the target object storage device when the incremental data starts to migrate;

[0038] The traffic synchronization module is used to forward the subsequent traffic facing the source object storage device to the target object storage after the current traffic switching and distribution is completed.

[0039] In addition, to achieve the above-mentioned purpose, the present application also proposes a data migration device for heterogeneous object storage, the device comprising: a memory, a processor, and a computer program stored on the memory and executable on the processor, the computer program being configured to implement the steps of the data migration method for heterogeneous object storage as described above.

[0040] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the data migration method of heterogeneous object storage as described above are implemented.

[0041] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the data migration method for heterogeneous object storage as described above are implemented.

[0042] One or more technical solutions proposed in this application have at least the following technical effects:

[0043] The embodiment of the present application proposes a data migration method, device, equipment, storage medium and program product for heterogeneous object storage, which migrates the stock data before the initial timestamp in the source object storage device to the target object storage device; according to the data operation record in the source object log, migrates the incremental data in the source object storage device to the target object storage device, and synchronizes the incremental data in the target object storage device to the source object storage device; when the incremental data begins to migrate, the current traffic where the incremental data is located is switched and distributed in the source object storage device and the target object storage device; when the current traffic is switched and distributed, the subsequent traffic facing the source object storage device is forwarded to the target object storage. The consistency and integrity of data migration is ensured by the source object log; uninterrupted data migration can be achieved by migrating and synchronizing the stock data, incremental data and traffic. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0045] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0046] Figure 1 A flowchart of a first embodiment of a method for data migration of heterogeneous object storage provided in the present application;

[0047] Figure 2 A schematic diagram of the process of incremental data migration in the data migration method for heterogeneous object storage of this application;

[0048] Figure 3 A flow chart of traffic migration provided for an embodiment of a method for data migration of heterogeneous object storage of the present application;

[0049] Figure 4 A schematic diagram of the module structure of a data migration device for heterogeneous object storage according to an embodiment of the present application;

[0050] Figure 5 A schematic diagram of the device structure of the hardware operating environment involved in the data migration method for heterogeneous object storage in an embodiment of the present application.

[0051] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0052] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0053] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0054] The main solution of the embodiment of the present application is: migrate the existing data before the initial timestamp in the source object storage device to the target object storage device; migrate the incremental data in the source object storage device to the target object storage device according to the data operation record in the source object log, and synchronize the incremental data in the target object storage device to the source object storage device; when the incremental data starts to migrate, switch and distribute the current traffic containing the incremental data in the source object storage device and the target object storage device; when the current traffic is switched and distributed, forward the subsequent traffic to the source object storage device to the target object storage.

[0055] In this embodiment, for ease of description, the following description is made by taking the identification of heterogeneous object storage devices as the execution subject.

[0056] With the development of cloud computing and big data technology, object storage has been widely used in various systems as an efficient and reliable storage method. However, different types of object storage facilities (such as FTP, UDS, ECS, S3, etc.) often have different access interfaces, and they have their own advantages and disadvantages in different scenarios. However, user systems often need to replace different types of storage facilities during development. When user systems need to switch storage facilities, such as switching from UDS to ECS, they often face problems such as complex data migration and high risks. Existing technical solutions have problems such as long migration time and impact on business continuity.

[0057] This application ensures the consistency and integrity of data migration through source object logs; by migrating and synchronizing existing data, incremental data, and flow data, uninterrupted data migration can be achieved.

[0058] It should be noted that the execution subject of this embodiment may be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device capable of realizing the above functions, a heterogeneous object storage device, etc. The following takes a heterogeneous object storage device as an example to illustrate this embodiment and the following embodiments.

[0059] Based on this, the present application embodiment provides a data migration method for heterogeneous object storage, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the data migration method for heterogeneous object storage of the present application.

[0060] In this embodiment, the data migration method of the heterogeneous object storage includes steps S10 to S30:

[0061] Step S10: Migrate the stock data before the initial timestamp in the source object storage device to the target object storage device.

[0062] It should be noted that the source object storage device refers to the data storage device from which the data is migrated. The source object storage device can be a local database or a cloud storage service, or other storage system that supports the object storage mode. Object is a general term for various files. A file, an audio, a video, or a photo can all be called an object.

[0063] In addition, it should be noted that the target object storage device refers to a data storage device to which data is migrated. The target object storage device may be a local database or a cloud storage service, or other storage system that supports the object storage mode.

[0064] In addition, it should be noted that the stock data refers to the data written and stored in the source object storage device before the initial timestamp.

[0065] In addition, it should be noted that the initial timestamp is a timestamp of a specific time point determined before the start of the stock data migration, which is used to define the stock data and incremental data, that is, the data written and stored in the source object storage device before the initial timestamp is the stock data, and the data written and stored in the source object storage device after the initial timestamp is the incremental data. In one embodiment of the present application, the initial timestamp is the timestamp corresponding to the time point when the data migration starts, the data stored in the source object storage device before the time point when the data migration starts is the stock data, and the data generated by the data source and transmitted to the source object storage device after the time point when the data migration starts is the incremental data.

[0066] Specifically, the time point when the stock data migration starts is recorded as the initial timestamp, and the stock data in the source object storage device is migrated to the target object storage device. After the data migration is completed, all log files corresponding to the stock data in the source secondary log, that is, the logs before the initial timestamp in the source secondary log, are migrated to the source third-level log.

[0067] Step S20: Migrate the incremental data in the source object storage device to the target object storage device according to the data operation record in the source object log, and synchronize the incremental data in the target object storage device to the source object storage device.

[0068] It should be noted that the source object log refers to a log recording operations on the source object storage device, including but not limited to read operations, write operations, write requests, read requests, etc. The source object log includes at least one of the source level 1 log, source level 2 log, source level 3 log, and source level 4 log.

[0069] In addition, it should be noted that the incremental data refers to the write operation data distributed by the data source to the source object storage device or the target object storage device after the initial timestamp, and generally refers to the write operation data that is distributed by the data source to the source object storage device or the target object storage device after the stock data starts to migrate. After the initial timestamp, the source object storage device or the target object storage device may still have data written, modified, or deleted. Incremental data migration refers to the migration of these newly generated or changed data after the stock data starts to migrate, so as to ensure data consistency between the source object storage device or the target object storage device.

[0070] Specifically, when the incremental data is distributed to the source object storage device, the log record corresponding to the timestamp after the initial timestamp in the source secondary log of the source object log is read; the target operation of the incremental data is determined according to the log record corresponding to the next timestamp of the initial timestamp in the source secondary log; and the corresponding target operation is performed on the incremental data in the target object storage device according to the target operation. When the incremental data is distributed to the target object storage device, the log record corresponding to the timestamp after the initial timestamp in the target secondary log of the target object log is read; the target operation of the incremental data is determined according to the log record corresponding to the next timestamp of the initial timestamp in the target secondary log; and the corresponding target operation is performed on the incremental data in the source object storage device according to the target operation.

[0071] Furthermore, after completing the migration of existing data and incremental data, a trial read of the target object storage device data is performed. The trial read is performed without affecting the business application. When the business application has a read request to the source object storage device, the read request is copied, and another thread is opened to simulate the application reading the target object storage device. The source object log will record the status and duration of the request for both the source object storage and the target object storage, and analyze and check whether the read performance of the target object storage device matches the read performance of the source object storage device, so as to expose problems early.

[0072] Step S30: When the incremental data starts to migrate, the current traffic of the incremental data is switched and distributed between the source object storage device and the target object storage device.

[0073] It should be noted that the data source refers to the data source that generates data before data migration and writes the data into the source object storage device.

[0074] In addition, it should be noted that the traffic refers to requests, and one request is one traffic. For example, uploading, modifying, deleting, and querying a file are all counted as one traffic. The current traffic of incremental data refers to the data requests throughout the migration process of stock data and incremental data.

[0075] Specifically, after the stock data migration synchronization is completed, when the incremental data starts to migrate, and after the trial reading of the target object storage device data, the current traffic where the incremental data is located is switched and distributed between the source object storage device and the target object storage device. The data source that generates the traffic gradually forwards the traffic write request instruction of the data source to the source object storage device to the target object storage device, and writes the traffic written to the source object storage device to the target object storage device.

[0076] More specifically, in the process of switching and distributing the current traffic containing the incremental data between the source object storage device and the target object storage device, it is necessary to control the switching direction and traffic distribution ratio of the traffic.

[0077] In one embodiment of the present application, a polling strategy is adopted to control the proportion of traffic distribution. For example, a variable a is used to mark the traffic of the source object storage device, and a variable b is used to mark the traffic of the target object storage device. The initial values ​​of both variables are 0. Assuming that the step length of traffic switching is 10%, that is, according to 0%, 10%, 20% to 100%, if 80% of the traffic is to be stored in the source object and the remaining 20% ​​of the traffic is to be stored in the target object, the process is as follows:

[0078] When the first request comes in, the mark a=a+1=0+1=1, and the traffic is distributed to the source object storage device;

[0079] When the second request comes, it is marked as a=a+1=1+1=2, and the traffic is distributed to the source object storage device;

[0080] When the third request comes, it is marked as a=a+1=2+1=3, and the traffic is distributed to the source object storage device;

[0081] When the fourth request comes, the mark a=a+1=3+1=4, and the traffic is distributed to the source object storage device;

[0082] When the fifth request comes in, it is marked as a=a+1=4+1=5, and the traffic is distributed to the source object storage device;

[0083] When the sixth request comes in, it is marked as a=a+1=5+1=6, and the traffic is distributed to the source object storage device;

[0084] When the seventh request comes, the mark a=a+1=6+1=7, and the traffic is distributed to the source object storage device;

[0085] When the eighth request comes in, it is marked as a=a+1=7+1=8, and the traffic is distributed to the source object storage device;

[0086] When the 9th request comes, it is found that a is equal to 8, which means that 8 flows have been distributed to the source object storage device. At this time, the flow should be distributed to the target object storage device, so b=b+1=0+1=1 is marked. In order to continue, a must be reset to 0 at this time;

[0087] When the 10th request comes in, it is marked as b=b+1=1+1=2, and the traffic is distributed to the target object storage device;

[0088] When the 11th request comes, it is found that b is already equal to 2, which means that 2 flows have been distributed to the target object storage device before. At this time, the flow should be distributed to the source object storage device, so a=a+1=0+1=1. In order to continue, b must be reset to 0 at this time.

[0089] Step S40: After the current traffic is switched and distributed, the subsequent traffic directed to the source object storage device is forwarded to the target object storage.

[0090] It should be noted that the subsequent traffic directed to the source object storage device refers to the traffic that is subsequently transmitted after the current traffic containing the incremental data is transmitted.

[0091] Specifically, after the current traffic switching is completed and the traffic of the data source can be stably 100% transmitted to the target object storage device, the traffic forwarding direction of the data source is stably set to the target object storage device.

[0092] This embodiment uses the above solution to ensure the consistency and integrity of data migration through source object logs; and can achieve uninterrupted data migration by migrating and synchronizing existing data, incremental data, and flow data.

[0093] Based on the above implementation scheme, in a feasible implementation manner, before migrating the stock data before the initial timestamp in the source object storage device to the target object storage device, the step S70 is further included:

[0094] Step S70: creating a source object log based on the operation on the source object storage device, wherein the source object log includes at least one of a source level 1 log, a source level 2 log, a source level 3 log, and a source level 4 log.

[0095] It should be noted that the source object log refers to a log recording operations on the source object storage device, including but not limited to read operations, write operations, write requests, read requests and other operations. The source object log includes at least one of the source level 1 log, source level 2 log, source level 3 log, and source level 4 log. Furthermore, the source object log also includes a source abnormal write log and a source abnormal read log. The source abnormal write log is used to record the log when the data source makes an abnormal write request to the source object storage device; the source abnormal read log is used to record the log when the data source makes an abnormal read request to the source object storage device.

[0096] In addition, it should be noted that the source level log is used to record data written to the source object storage device (addition, deletion, modification), but the log of the uncompleted write request contains information such as the object data ID, the metadata of the object data, and the start time of the write data request.

[0097] In addition, it should be noted that the source secondary log is used to record the request information of successfully writing data to the source object storage device, but the object data write operation has not yet been synchronized to the target object. When the write operation is synchronized to the target object storage device, the corresponding log will be transferred to the source third-level log.

[0098] In addition, it should be noted that the source level 3 log is used to record all write operations on the source object storage device. If the object data is inconsistent with the target object storage device, the log can be used to backtrack and then find the cause of the inconsistency and repair the inconsistency.

[0099] In addition, it should be noted that the source level 4 log is used to record the abnormal log when the data in the source object storage device fails to be synchronized to the target object storage device.

[0100] Specifically, a source object log is created based on the operation on the source object storage device, and the source object log includes at least one of the source level 1 log, the source level 2 log, the source level 3 log, and the source level 4 log. Furthermore, the source object log also includes a source abnormal write log and a source abnormal read log. The source abnormal write log is used to record the log when the data source makes an abnormal write request to the source object storage device; the source abnormal read log is used to record the log when the application makes an abnormal read request to the source object storage device.

[0101] More preferably, relative to the source object log, a target object log is created based on the operation on the target object storage device, and the target object log includes at least one of a target level 1 log, a target level 2 log, a target level 3 log, and a target level 4 log. More preferably, the target object log also includes a target abnormal write log and a target abnormal read log.

[0102] More specifically, the record content of the log contained in the target object log corresponds to the source object log. The target object log refers to a log that records operations on the target object storage device, including but not limited to read operations, write operations, write requests, read requests, and other operations. The target level 1 log is used to record the log of writing data (addition, deletion, modification) to the target object storage device, but not completing the write request, including information such as the object data ID, the metadata of the object data, and the start time of the write data request. The target level 2 log is used to record the request information that the data is successfully written to the target object storage device, but the object data write operation has not yet been synchronized to the source object. When the write operation is synchronized to the source object storage device, the corresponding log will be transferred to the target level 3 log. The target level 3 log is used to record all write operations to the target object storage device. If the object data is inconsistent with the source object storage device, it can be traced back through this log. The target level 4 log is used to record the abnormal log of the failure of data synchronization from the target object storage device to the source object storage device. The target exception write log is used to record the log when the write request to the target object storage device is abnormal; the target exception read log is used to record the log when the application makes an abnormal read request to the target object storage device.

[0103] This embodiment uses the above scheme to create a source object log, which includes at least one of a source level 1 log, a source level 2 log, a source level 3 log, and a source level 4 log. By creating multiple levels of source object logs, different logs can ensure the consistency and integrity of the migrated data by recording corresponding log records.

[0104] Based on the above implementation scheme, in a feasible implementation manner, the migration of the stock data before the initial timestamp in the source object storage device to the target object storage device includes steps S11 to S13:

[0105] Step S11, determining an initial timestamp in a source object storage device.

[0106] Specifically, the timestamp of the start time of the stock data migration is recorded as the initial timestamp, and the data stored in the source object storage device before the initial timestamp is the stock data.

[0107] Step S12: Migrate the stock data before the initial timestamp of the source object storage device to the target object storage device.

[0108] Specifically, after determining the initial timestamp, determine the size of the existing data and the resources required for data migration (such as network bandwidth, storage space, computing resources, etc.); determine the tool for data migration, which can perform data reading, data transmission, data writing, and data verification; use the data migration tool to migrate the existing data from the source object storage device to the target object storage device. During the transmission process, compression, encryption and other measures can be taken to improve the efficiency and security of the transmission. During the transmission process, monitor the progress and status of the transmission to ensure that there are no interruptions or errors during the data transmission process.

[0109] The transferred data is written on the target object storage device. During the writing process, operations such as data format conversion and index update may be required. After writing is completed, the data in the target object storage device is verified to ensure the integrity, consistency and accuracy of the data. This can be achieved by comparing the source data and the target data, checking the checksum of the data file, etc. After the data migration is completed, the metadata and index information are updated on the target object storage device to ensure that the migrated data can be correctly retrieved and accessed. If an exception occurs during the migration synchronization process, the migration process is stopped and the specific cause of the exception is analyzed.

[0110] Step S13: Migrate the logs before the initial timestamp recorded in the source second-level log in the source object log to the source third-level log.

[0111] Specifically, after the stock data is completely and synchronously migrated to the target object storage device, all logs before the initial timestamp in the source secondary log in the source object log, that is, logs corresponding to the stock data, are migrated to the source third-level log.

[0112] Based on the above implementation scheme, in a feasible implementation manner, migrating the incremental data in the source object storage device to the target object storage device according to the data operation record in the source object log includes steps S21 to S23:

[0113] Step S21, reading log records after the initial timestamp in the source secondary log of the source object log.

[0114] Specifically, the stock data before the initial timestamp has been migrated from the source object storage device to the target object storage device. After the stock data starts to migrate, new data is written or modified. The source secondary log is used to record the request information that the data is successfully written to the source object storage device, but the object data write operation has not yet been synchronized to the target object. The log records after the initial timestamp in the source secondary log of the source object log are read, that is, the log records of incremental data. The log records include but are not limited to the timestamp (sent time), operation type (indicates the type of operation, such as add, modify, delete), operation object (identification ID of the data object being operated), and other contents.

[0115] Step S22, determining the data operation of the incremental data according to the log records after the initial timestamp in the source secondary log.

[0116] It should be noted that data operations on incremental data include but are not limited to data operations such as modification, addition, and deletion.

[0117] Specifically, according to the operation type in the log record, the data operation of the incremental data in the source object storage device is determined, and the data operation may be an operation such as modification, addition, and deletion.

[0118] Step S23: performing corresponding target operations on the incremental data in the target object storage device according to the data operation of the incremental data.

[0119] Specifically, when the data operation of the incremental data is a deletion operation, the incremental data and the corresponding data operation are determined according to the data identification ID of the incremental data, and the incremental data in the target object storage device is deleted; when the data operation of the incremental data is a modification / addition operation, the incremental data in the target object storage device is stored. When the target operation is successfully completed, the log record corresponding to the incremental data in the source secondary log is transferred to the source third-level log; when the target operation fails to synchronize, the target operation is repeated several times. If it still fails after several times, the log is transferred from the source secondary log to the source fourth-level log. The number of attempts can be one, two, three, etc., which can be set by yourself.

[0120] For easier understanding, please refer to Figure 2 , Figure 2 This is a flowchart for incremental data migration. First, the log records after the initial timestamp in the source secondary log are read to determine the data operation type of the incremental data. When the data operation is deletion, the incremental data is deleted from the target object storage device. If the data operation type is addition or modification, the incremental data after the operation is synchronously stored in the target object storage device. After the operation is successful, the records in the source secondary log are transferred to the source third-level log. If it fails, the records in the source secondary log are transferred to the source fourth-level log.

[0121] According to the data operation records in the source object log, the step of migrating the incremental data in the source object storage device to the target object storage device can synchronize the write operations in the source object storage device to the target object storage device. Furthermore, it is necessary to synchronize the write operations of the incremental data in the target object storage device to the source object storage device. The specific steps are: reading the log records after the initial timestamp in the target secondary log of the target object log; determining the data operation of the incremental data according to the log records after the initial timestamp in the target secondary log; performing corresponding target operations on the incremental data in the source object storage device according to the data operation of the incremental data. By synchronizing the write operations of the incremental data in the source object storage device and the target object storage device, it can be ensured that the data in the source object storage device and the target object storage device are complete, and the traffic can be switched back at any time when an abnormality occurs.

[0122] Through the above scheme, this embodiment determines the data operation of incremental data according to log records, and then performs corresponding target operations on the incremental data synchronized to the target object storage device according to the data operation. The incremental data can be updated accordingly to ensure the integrity and consistency of the data, which is the key content to achieve uninterrupted migration.

[0123] Based on the above implementation scheme, in a feasible implementation manner, the forwarding of the data source's traffic write request instruction to the source object storage device to the target object storage device and the writing of the traffic written to the source object storage device to the target object storage device also include steps S50 to S60:

[0124] Step S50: When the target direction of the current traffic switching distribution is the target object storage device, the current operation state of the current operation object is determined according to the source object log recording the current operation object.

[0125] It should be noted that the current operation object refers to the object to be operated by the current request instruction. In the data migration process of heterogeneous object storage, after the synchronization migration of existing data is completed, there is a situation in which the source object storage device and the target storage device perform read and write operations on an object at the same time during the traffic switching process. If it is not controlled, the problem of dirty read or dirty write of data is likely to occur. The current operation object is the object on which the source object storage device and the target storage device perform read and write operations at the same time. Therefore, in order to solve the problem of dirty read or dirty write, if the traffic read / write request instruction is forwarded to the target object storage device at the beginning of the traffic switching, before the target object storage executes the instruction, it is also necessary to check whether there is an instruction in the source object storage that operates on the object and has not yet been synchronized to the target object storage. If so, the current read / write instruction is forwarded to the source object storage for execution.

[0126] Data dirty write is a problem that easily occurs during data transmission and causes data inconsistency. For example, there is a current operation object Q, and its storage data in the source object storage device and the target object storage are consistent. At this time, if a write request A has arrived at the source object storage device to modify the current operation object Q, the object type of the metadata of the current operation object Q is changed to pdf, and then another write request B arrives at the target object storage device to change the object type of the metadata of the current operation object Q to word. If there is no control, after the two-way data synchronization, the final type of the current operation object Q may be pdf, but in fact, the write request B is later than the write request A, and the final type of the current operation object Q should eventually be word.

[0127] It should be noted that when the target direction of the current traffic switching distribution is the target object storage device, the current operation status refers to the current state of the current operation object. The current operation status of the current operation object recorded in the source object log includes pre-write to the source object storage device, pre-synchronization from the source object storage device to the target object storage device, failure to synchronize from the source object storage device to the target object storage device, and newly generated pre-write.

[0128] Specifically, when the target direction of the switching distribution of the current traffic is the target object storage device, when the log recording the current operation object is the source level 1 log, the current operation state of the current operation object is pre-written to the source object storage device; when the log recording the current operation object is the source level 2 log, the current operation state of the current operation object is pre-synchronized from the source object storage device to the target object storage device; when the log recording the current operation object is the source level 4 log, the current operation state of the current operation object is a failure to synchronize from the source object storage device to the target object storage device; when the source log module does not record the log of the current operation object, the current operation state of the current operation object is a newly generated pre-write.

[0129] Step S60: Determine the switching distribution direction of the flow writing of the current operation object according to the current operation state of the current operation object.

[0130] Specifically, for a better understanding, please refer to Figure 3 , Figure 3 The flowchart of traffic migration is shown. When the target direction of the current traffic switching distribution is the target object storage device, when the current operation state of the current operation object is pre-written to the source object storage, the forwarding direction of the data write request instruction of the current operation object is the source object storage device; when the current operation state of the current operation object is pre-synchronized from the source object storage to the target object storage, the forwarding direction of the data write request instruction of the current operation object is the source object storage device; when the current operation state of the current operation object is the failure of synchronization from the source object storage to the target object storage, the forwarding direction of the data write request instruction of the current operation object is the source object storage device; when the current operation state of the current operation object is newly generated pre-written, the forwarding direction of the data write request instruction of the current operation object is the target object storage device.

[0131] Furthermore, when the target direction of the switching distribution of the current traffic is the source object storage device, when the log recording the current operation object is the target first-level log, the current operation state of the current operation object is pre-written to the target object storage device, and the switching distribution direction of the current operation object traffic writing is the target object storage device; when the log recording the current operation object is the target second-level log, the current operation state of the current operation object is pre-synchronized from the target object storage device to the source object storage device, and the switching distribution direction of the current operation object traffic writing is the target object storage device; when the log recording the current operation object is the target fourth-level log, the current operation state of the current operation object is the failure to synchronize from the target object storage device to the source object storage device, and the switching distribution direction of the current operation object traffic writing is the target object storage device; when the target object log does not record the log of the current operation object, the current operation state of the current operation object is the no operation state, and the switching distribution direction of the current operation object traffic writing is the source object storage device.

[0132] Through the above scheme, this embodiment determines the current operation state of the current operation object according to the log recording the current operation object; and determines the forwarding direction of the data write request instruction of the current operation object according to the current operation state of the current operation object, thereby avoiding data dirty writing and ensuring the consistency and integrity of the migrated data.

[0133] Based on the above implementation scheme, in a feasible implementation manner, the step of determining the current operation state of the current operation object according to the source object log recording the current operation object includes S51 to S54:

[0134] Step S51, when the log recording the current operation object is a source level one log, the current operation state of the current operation object is pre-written into the source object storage device.

[0135] Specifically, when the log recording the current operation object is a source level log, the source level log is used to record requests to write data to the source object storage device, indicating that the data of the current operation object may not have been actually written to the source object storage device. Therefore, the current operation status of the current operation object is pre-written to the source object storage device.

[0136] Step S52: When the log recording the current operation object is a source secondary log, the current operation state of the current operation object is pre-synchronized from the source object storage device to the target object storage device.

[0137] Specifically, when the log recording the current operation object is a source secondary log, the source secondary log is used to record the request information that data is successfully written to the source object storage device, but the object data write operation has not yet been synchronized to the target object, indicating that the data of the current operation object has been actually written to the source object storage device, but has not yet been migrated to the target object storage device. Therefore, the current operation status of the current operation object is pre-synchronized from the source object storage device to the target object storage device.

[0138] Step S53: when the log recording the current operation object is a source level 4 log, the current operation state of the current operation object is failure to synchronize from the source object storage device to the target object storage device.

[0139] Specifically, when the log recording the current operation object is a source level 4 log, the source level 4 log is used to record an abnormal log of failure in synchronization of incremental data in the source object storage device to the target object storage, indicating that data in the source object storage device failed to be synchronized to the target object storage device.

[0140] Step S54: when the source object log does not record the log of the current operation object, the current operation state of the current operation object is a no operation state.

[0141] Specifically, when the source object log does not record the log of the current operation object, it can be considered that the state of the current operation object is consistent between the source object storage device and the target object storage device, and there is no known conflict or synchronization problem.

[0142] Based on the above implementation scheme, in a feasible implementation manner, determining the switching distribution direction of the current operation object flow writing according to the current operation state of the current operation object includes steps S61 to S64:

[0143] Step S61, when the current operation state of the current operation object is pre-writing to the source object storage, the switching distribution direction of the current operation object flow writing is the source object storage device.

[0144] Specifically, the log recording the current operation object is the source level log, which is used to record the request to write data to the source object storage device, indicating that the data of the current operation object may not have been actually written yet, so the current operation state of the current operation object is pre-written to the source object storage device. If the write request is allowed to directly reach the target object storage device at this time, and this write request conflicts with the request being processed by the source object storage device for the current operation object (recorded in the source level log), it may cause data inconsistency. Therefore, the data write request is forwarded to the source object storage device to ensure that all write operations are executed in the source object storage device in the order in which they are received. Doing so can maintain the consistency of the data in the source object storage device, and when the data is synchronized to the target object storage device, it can ensure that the data in the target object storage device is consistent with the data in the source object storage device.

[0145] Step S62: When the current operation state of the current operation object is pre-synchronization from the source object storage to the target object storage, the switching distribution direction of the current operation object traffic write is the source object storage device.

[0146] Specifically, when the log recording the current operation object is a source secondary log, the source secondary log is used to record the request information that the data is successfully written to the source object storage device, but the object data write operation has not yet been synchronized to the target object, indicating that the current operation state of the current operation object is pre-synchronized from the source object storage to the target object storage. If a new data write request instruction is allowed to directly reach the target object storage device at this time, and this new data write request instruction conflicts with the most recently completed write operation in the source object storage (recorded in the source secondary log), it may cause data inconsistency. Therefore, the new data write request instruction is forwarded to the source object storage device to ensure that all write operations are executed in the order in which they are processed in the source object storage device. This can maintain the consistency of the data in the source object storage device, and when the data is synchronized to the target object storage device, it can ensure that the data in the target object storage device is consistent with the data in the source object storage.

[0147] Step S63: When the current operation state of the current operation object is that synchronization from the source object storage to the target object storage fails, the switching distribution direction of the current operation object traffic write is the source object storage device.

[0148] Specifically, when the log recording the current operation object is a source level 4 log, the source level 4 log is used to record the abnormal log of the failure of the incremental synchronization of data in the source object storage device to the target object storage, indicating that the data in the source object storage device failed to be synchronized to the target object storage device. If a new data write request instruction is allowed to directly reach the target object storage device at this time, and the failure record in the source level 4 log is not considered, it may cause inconsistency of data between the source object storage device and the target object storage device. Therefore, the data write request instruction is forwarded to the source object storage device to ensure that all write operations are first executed in the source object storage device, and only after the synchronization is successful, these changes will be copied to the target object storage device. Doing so can ensure that the consistency and integrity of the data in the source object storage device and the target object storage can be maintained even in the event of a synchronization failure.

[0149] Step S64, when the current operation state of the current operation object is a no-operation state, the switching distribution direction of the current operation object flow writing is the target object storage device.

[0150] Specifically, when the source object log does not record the log of the current operation object, it can be considered that the state of the current operation object is consistent between the source object storage device and the target object storage device, and there is no known conflict or synchronization problem. The data write request instruction is forwarded to the target object storage device, and the request is recorded in the target primary log. After the write operation is successful, the log of the write operation is transferred to the target secondary log. If the write fails, the log of the write operation is transferred to the target abnormal write log.

[0151] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the data migration method for heterogeneous object storage of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0152] This application also provides a data migration device for heterogeneous object storage, please refer to Figure 3 , the data migration device for heterogeneous object storage includes:

[0153] The stock migration module 401 is used to migrate the stock data before the initial timestamp in the source object storage device to the target object storage device;

[0154] The incremental migration module 402 is used to migrate the incremental data in the source object storage device to the target object storage device according to the data operation record in the source object log, and synchronize the incremental data in the target object storage device to the source object storage device;

[0155] The traffic switching module 403 is used to switch and distribute the current traffic of the incremental data between the source object storage device and the target object storage device when the incremental data starts to be migrated;

[0156] The traffic synchronization module 404 is used to forward the subsequent traffic oriented to the source object storage device to the target object storage after the current traffic switching and distribution is completed.

[0157] The data migration device for heterogeneous object storage provided by the present application adopts the data migration method for heterogeneous object storage in the above embodiment, which can solve the technical problem of long migration time and affecting business continuity. Compared with the prior art, the beneficial effects of the data migration device for heterogeneous object storage provided by the present application are the same as the beneficial effects of the data migration method for heterogeneous object storage provided by the above embodiment, and other technical features in the data migration device for heterogeneous object storage are the same as the features disclosed in the above embodiment method, which will not be repeated here.

[0158] The present application provides a data migration device for heterogeneous object storage, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the data migration method for heterogeneous object storage in the above-mentioned embodiment 1.

[0159] Reference below Figure 5 , which shows a schematic diagram of the structure of a data migration device for heterogeneous object storage suitable for implementing the embodiment of the present application. The data migration device for heterogeneous object storage in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 5 The data migration device for heterogeneous object storage shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0160] like Figure 5As shown, the data migration device for heterogeneous object storage may include a processing device 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. Various programs and data required for the operation of the data migration device for heterogeneous object storage are also stored in the RAM 1004. The processing device 1001, the ROM 1002, and the RAM 1004 are connected to each other via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems may be connected to the I / O interface 1006: input devices 1007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 1003 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 1009. The communication device 1009 may allow the data migration device for heterogeneous object storage to communicate wirelessly or wired with other devices to exchange data. Although the figure shows a data migration device for heterogeneous object storage with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems may be implemented or have instead.

[0161] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0162] The data migration device for heterogeneous object storage provided by the present application adopts the data migration method for heterogeneous object storage in the above embodiment, which can solve the technical problem of long migration time and impact on business continuity. Compared with the prior art, the beneficial effects of the data migration device for heterogeneous object storage provided by the present application are the same as the beneficial effects of the data migration method for heterogeneous object storage provided by the above embodiment, and other technical features in the data migration device for heterogeneous object storage are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0163] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0164] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0165] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the data migration method for heterogeneous object storage in the above-mentioned embodiment.

[0166] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0167] The computer-readable storage medium may be included in the data migration device for heterogeneous object storage; or may exist independently without being assembled into the data migration device for heterogeneous object storage.

[0168] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the data migration device of heterogeneous object storage, the data migration device of heterogeneous object storage: migrates the existing data before the initial timestamp in the source object storage device to the target object storage device; migrates the incremental data in the source object storage device to the target object storage device according to the data operation record in the source object log, and synchronizes the incremental data in the target object storage device to the source object storage device; when the incremental data starts to migrate, switches and distributes the current traffic containing the incremental data in the source object storage device and the target object storage device; when the current traffic is switched and distributed, forwards the subsequent traffic facing the source object storage device to the target object storage.

[0169] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0170] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0171] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0172] The readable storage medium provided in this application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned data migration method for heterogeneous object storage, and can solve the technical problems of long migration time and impact on business continuity. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as the beneficial effects of the data migration method for heterogeneous object storage provided in the above-mentioned embodiment, and will not be repeated here.

[0173] The present application also provides a computer program product, including a computer program, which implements the steps of the above-mentioned heterogeneous object storage data migration method when executed by a processor.

[0174] The computer program product provided by this application can solve the technical problem of long migration time and impact on business continuity. Compared with the prior art, the beneficial effects of the computer program product provided by this application are the same as the beneficial effects of the data migration method for heterogeneous object storage provided by the above embodiment, which will not be repeated here.

[0175] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A data migration method for heterogeneous object storage, characterized in that: The method comprises: Migrate the existing data before the initial timestamp in the source object storage device to the target object storage device; Migrate the incremental data in the source object storage device to the target object storage device according to the data operation record in the source object log, and synchronize the incremental data in the target object storage device to the source object storage device; When the incremental data starts to migrate, the current traffic of the incremental data is switched and distributed between the source object storage device and the target object storage device; When the current traffic is switched and distributed, the subsequent traffic to the source object storage device is forwarded to the target object storage.

2. The method according to claim 1, characterized in that Before the step of migrating the stock data before the initial timestamp in the source object storage device to the target object storage device, the step further includes: A source object log is created based on an operation on a source object storage device, wherein the source object log includes at least one of a source level 1 log, a source level 2 log, a source level 3 log, and a source level 4 log.

3. The method according to claim 1, characterized in that The step of migrating the stock data before the initial timestamp in the source object storage device to the target object storage device includes: determining an initial timestamp in a source object storage device; Migrate the existing data before the initial timestamp of the source object storage device to the target object storage device; Migrate the logs before the initial timestamp recorded in the source secondary log in the source object log to the source third-level log.

4. The method according to claim 1, characterized in that The step of migrating the incremental data in the source object storage device to the target object storage device according to the data operation record in the source object log includes: Read the log records after the initial timestamp in the source secondary log of the source object log; Determine the data operation of the incremental data based on the log records after the initial timestamp in the source secondary log; According to the data operation of the incremental data, corresponding target operations are performed on the incremental data in the target object storage device.

5. The method according to claim 1, characterized in that When the incremental data starts to be migrated, before the step of switching and distributing the current traffic of the incremental data in the source object storage device and the target object storage device, the step further includes: When the target direction of the current traffic switching distribution is the target object storage device, the current operation state of the current operation object is determined according to the source object log recording the current operation object; According to the current operation state of the current operation object, a switching distribution direction of the current operation object flow writing is determined.

6. The method according to claim 5, characterized in that The step of determining the current operation state of the current operation object according to the source object log recording the current operation object comprises: When the log recording the current operation object is a source level 1 log, the current operation state of the current operation object is pre-written to the source object storage device; When the log recording the current operation object is a source secondary log, the current operation state of the current operation object is pre-synchronized from the source object storage device to the target object storage device; When the log recording the current operation object is a source level 4 log, the current operation status of the current operation object is that synchronization from the source object storage device to the target object storage device fails; When the source object log does not record the log of the current operation object, the current operation state of the current operation object is a no operation state.

7. The method according to claim 5, characterized in that The step of determining the switching distribution direction of the current operation object flow writing according to the current operation state of the current operation object comprises: When the current operation state of the current operation object is pre-writing to the source object storage, the switching distribution direction of the current operation object traffic writing is the source object storage device; When the current operation state of the current operation object is pre-synchronization from the source object storage to the target object storage, the switching distribution direction of the current operation object traffic write is the source object storage device; When the current operation state of the current operation object is that the synchronization from the source object storage to the target object storage fails, the switching distribution direction of the current operation object traffic write is the source object storage device; When the current operation state of the current operation object is the no operation state, the switching distribution direction of the current operation object traffic write is the target object storage device.

8. A data migration device for heterogeneous object storage, characterized in that: The device comprises: The stock migration module is used to migrate the stock data before the initial timestamp in the source object storage device to the target object storage device; An incremental migration module, used to migrate incremental data in a source object storage device to a target object storage device and synchronize incremental data in a target object storage device to a source object storage device according to data operation records in a source object log; A traffic switching module, used for switching and distributing the current traffic of the incremental data between the source object storage device and the target object storage device when the incremental data starts to migrate; The traffic synchronization module is used to forward the subsequent traffic facing the source object storage device to the target object storage after the current traffic switching and distribution is completed.

9. A data migration device for heterogeneous object storage, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the data migration method for heterogeneous object storage according to any one of claims 1 to 7.

10. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the data migration method for heterogeneous object storage according to any one of claims 1 to 7 are implemented.

11. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the data migration method for heterogeneous object storage according to any one of claims 1 to 7 are implemented.

Images