Data back-to-source method, system and equipment capable of being used for data migration in object storage
By configuring data return rules in the cloud storage system, using S3 protocol to download objects from the source site and store them to a new storage bucket, the problem of slow data migration speed and affecting services in the cloud storage system is solved, and fast and no impact on services is achieved data migration and data security improve the convenience of users using object services.
Patent Information
- Application Number
- CN202411049412.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-01
- Publication Date
- 2024-11-29
AI Technical Summary
In cloud storage systems, data migration is faced with problems such as slow speed, impact on business, and insufficient data security. Especially when the data volume is large and user business needs change, old cloud storage services no longer meet the needs, resulting in increased migration challenges big.
Provide a data return method that can be used for data migration in object storage. By configuring data return rules in the bucket, using S3 protocol to download objects from the source station and store them in a new bucket, supporting user settings, acquisition and deletion Rules, using scope download and shard upload methods to ensure data security.
It realizes rapid and non-affected data migration, improves the convenience of users using object services, meets the data migration needs of cross-cloud storage services, and ensures data security.
Smart Images

Figure CN119045727A_ABST
Abstract
Description
Technical Field
[0001] One or more embodiments of the present invention relate to the field of object storage technology, and in particular, to a data source return method, system, and device that can be used for data migration in object storage. Background Art
[0002] With the development of big data, more and more data is stored in cloud computing storage clusters. The performance of most systems will decline as the business volume expands. In order to deal with the performance degradation problem faced by such storage clusters, it is often necessary to first reconstruct a new system with better performance, and then migrate the data in the old system to the reconstructed new system. In addition, as the user's business develops, the technical solutions provided by the previously selected cloud storage service provider may no longer meet the user's business needs, so that the user needs to transfer his business from one cloud storage service provider to another.
[0003] However, because the amount of data in the cloud storage system may have reached a very large amount after years of accumulation, the migration of old data will face many huge challenges, such as how to migrate data at a faster speed and complete the migration work in the shortest time; how to migrate data without affecting the normal business of users; how to ensure data security during data migration and prevent leakage incidents, etc. Summary of the invention
[0004] One or more embodiments of the present invention describe a data source return method, system, and device that can be used for data migration in object storage, which can effectively improve the convenience of users using object services.
[0005] According to an embodiment of the first aspect of the present invention, a data source return method that can be used for data migration is provided, comprising:
[0006] A. After receiving an object download request from a user, if the object does not exist, check whether a data return-to-source rule is configured for the object in the storage bucket;
[0007] B. If it is detected that a data return-to-source rule is configured for the object in the storage bucket and the object satisfies the data return-to-source rule, a data return-to-source process is executed, wherein a request is made to download the object from the address of the source station configured in the data return-to-source rule according to the S3 protocol, and the object downloaded from the source station is stored in the storage bucket and sent to the user.
[0008] Preferably, in any embodiment, it further comprises:
[0009] A first data return-to-source rule interface for setting a storage bucket and a second data return-to-source rule interface for obtaining a storage bucket are provided to the user, so that the user can call the first data return-to-source rule interface to configure or modify the data return-to-source rule on the storage bucket to be returned to the source.
[0010] Preferably, in any embodiment, it further comprises:
[0011] A third data return-to-source rule interface for deleting a storage bucket is provided for the user, so that the user can call the third data return-to-source rule interface to delete the data return-to-source rule.
[0012] Preferably, in any embodiment,
[0013] The data return-to-source rule includes the object name prefix of the object;
[0014] The data return process is performed only on the object having the object name prefix.
[0015] Preferably, in any embodiment,
[0016] The data return-to-source rule includes a hypertext transfer protocol (http) status code for triggering a data return-to-source process for the object.
[0017] Preferably, in any embodiment,
[0018] The data return-to-source rule is configured with automatic following redirection, and when the object does not exist but redirection is configured, the source station provides a new source station with a redirection address for downloading the object.
[0019] Preferably, in any embodiment,
[0020] The downloading of the object from the source station includes: downloading the object in a range download mode.
[0021] Preferably, in any embodiment,
[0022] The storing the object downloaded from the source station into the storage bucket includes: storing the object into the storage bucket in a piecewise uploading manner.
[0023] According to an embodiment of the second aspect of the present invention, a data retrieval system for data migration in an object storage is provided, which is used to implement the data retrieval method for data migration in an object storage as described above, including:
[0024] A detection module, configured to detect whether a data return-to-source rule is configured for the object in the storage bucket after receiving an object download request from a user and the object does not exist;
[0025] The data retrieval module is used to: if it is detected that a data retrieval rule is configured for the object in the storage bucket and the object satisfies the data retrieval rule, execute a data retrieval process, wherein a request is made to download the object from the address of the source station configured in the data retrieval rule according to the S3 protocol, and the object downloaded from the source station is stored in the storage bucket and sent to the user.
[0026] According to an embodiment of the third aspect of the present invention, there is provided a data retrieval device that can be used for data migration in an object storage, including a memory and a processor, wherein an executable code is stored in the memory, and when the processor executes the executable code, the data retrieval method that can be used for data migration in an object storage as described above is implemented.
[0027] The data source return method, system, and device for data migration in object storage provided according to one or more embodiments of the present invention can effectively improve the convenience of users in using object services. BRIEF DESCRIPTION OF THE DRAWINGS
[0028] In order to more clearly illustrate the embodiments of the present invention 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, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0029] Figure 1 It is a flowchart of a data source return method that can be used for data migration in object storage according to an embodiment of the present invention. DETAILED DESCRIPTION
[0030] The technical solutions of various embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments described in the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0031] One or more embodiments of the present invention describe a data source return method, system, and device that can be used for data migration in object storage, which can effectively improve the convenience of users using object services.
[0032] According to an embodiment of the first aspect of the present invention, a data source return method (such as Figure 1 As shown), comprising the following steps:
[0033] 100. After receiving an object download request from a user, if the object does not exist, detecting whether a data return-to-source rule is configured for the object in the storage bucket;
[0034] 200. If it is detected that a data back-to-source rule is configured for the object in the storage bucket and the object satisfies the data back-to-source rule, a data back-to-source process is executed, wherein a request is made to download the object from the address of the source station configured in the data back-to-source rule according to the S3 protocol, and the object downloaded from the source station is stored in the storage bucket and sent to the user.
[0035] In this way, when a client user needs to download a specific object but the object does not exist, if the object meets the preset data return-to-source rule, the object can be downloaded from the source station where the object exists that is pre-configured in the data return-to-source rule through a pre-configured storage bucket. In this data return-to-source process, on the one hand, the object can be saved in the storage bucket, and on the other hand, the object can be sent to the client user. When the data return-to-source process is completed, the object has been successfully stored in the storage bucket of the current storage system, and the user has also successfully downloaded / received the object on the client without affecting the user's business.
[0036] In this way, a data back-to-source rule can be configured for a specific object in a storage bucket. An available source station is configured for the object in the data back-to-source rule, so as to provide it to users for downloading the object. This is transparent to client users and does not affect user business. It not only provides users with a way to download the required data (such as the object), but also provides the source station data (such as the object) to the storage bucket of the current storage service, thereby achieving smooth and efficient data migration.
[0037] It can be seen that the data source return method that can be used for data migration in object storage provided according to one or more embodiments of the present invention can effectively improve the convenience of users in using object services.
[0038] Preferably, in any embodiment, it further comprises:
[0039] A first data return-to-source rule interface for setting a storage bucket and a second data return-to-source rule interface for obtaining a storage bucket are provided to the user, so that the user can call the first data return-to-source rule interface to configure or modify the data return-to-source rule on the storage bucket to be returned to the source.
[0040] In this way, users can call the corresponding data return source rule interface as needed, and configure the corresponding data return source rule on the storage bucket to be returned to the data source, so that the storage bucket becomes the data return source bucket.
[0041] Optionally, in any embodiment, further comprising:
[0042] Configure multiple optional origins for the object.
[0043] In this way, the source site can be configured as the object storage address of different cloud storage service vendors for hot data migration between different cloud services, which can meet the user's cross-cloud storage service data migration needs and effectively improve the convenience of users using object storage services.
[0044] Optionally, in any embodiment, further comprising:
[0045] A suitable source station is selected from the multiple optional source stations to download the object through polling response or network speed detection.
[0046] In this way, the currently most suitable (for example, the one with the fastest download speed) available source station can be further selected to provide the user with object download, thereby further reducing the impact of the data return process on the user.
[0047] Optionally, in any embodiment, further comprising:
[0048] Different source stations are configured for different objects.
[0049] Optionally, in any embodiment, the different objects include: objects used for different services.
[0050] Preferably, in any embodiment, it further comprises:
[0051] A third data return-to-source rule interface for deleting a storage bucket is provided for the user, so that the user can call the third data return-to-source rule interface to delete the data return-to-source rule.
[0052] In this way, when the user no longer needs to migrate the remote data to the current storage bucket, the third data return-to-source rule interface can be called to delete the corresponding data return-to-source rule.
[0053] Optionally, in any embodiment, the second data return source rule interface includes: an enabled state and a disabled state. In this way, when the user needs to provide remote data from the source station to the current storage bucket (or user), the second data return source rule interface can be enabled, so that the current storage bucket (or user) can obtain remote data from the source station (for example, download the object); when the user no longer needs to provide remote data from the source station to the current storage bucket (or user) (for example, data is migrated to the current storage bucket), the second data return source rule interface can be disabled, so that the current storage bucket (or user) cannot obtain remote data from the source station (for example, download the object). Of course, if needed later, the second data return source rule interface can also be switched to the enabled state at this time.
[0054] It should be understood that the data return to the source rule includes the domain name address of the specified source station, where the object exists in the source station for download or data migration, the source station address is the old address where the data to be migrated exists, the current storage bucket is the destination address of the data to be migrated, and the data needs to be migrated from the source station to the current storage bucket during the data return to the source process. The storage service where the source station is located should support the S3 (Amazon Simple Storage Service, referred to as Amazon S3 or S3) protocol, and the data to be migrated is publicly readable. If the data is private, the data cannot be migrated through data return to the source.
[0055] Preferably, in any embodiment, the data return source rule includes: the object name prefix of the object; the data return source process is only performed on the object with the object name prefix. In this way, the download or data return source of the object will only occur when the object name prefix meets the conditions of the object specified in the data return source rule, and the object that does not meet the data return source rule will not be affected.
[0056] Preferably, in any embodiment, the data return-to-source rule includes a hypertext transfer protocol (http) status code for triggering a data return-to-source process of the object.
[0057] Optionally, in any embodiment, the http status code includes a 404 status code. In this way, the data source return process is triggered only when the object required to be downloaded by the user does not exist.
[0058] Optionally, in any embodiment, the data return-to-source rule includes: when performing data return-to-source, transmitting a request string carried in the user client in the request.
[0059] Optionally, in any embodiment, the data return-to-source rule includes: when performing data return-to-source, carrying a request header in a user client request.
[0060] Optionally, in any embodiment, the data return-to-source rule includes: when the object is unavailable or does not exist in the source station, stopping the data return-to-source process.
[0061] Optionally, in any embodiment, the data return-to-source rule includes: when the object in the source station is unavailable, pausing the data return-to-source process and regularly checking the status of the source station to continue the data return-to-source process.
[0062] Optionally, in any embodiment, the data back-to-source rule includes: when the object in the source station is unavailable, pausing the data back-to-source process and polling or searching the status of other available source stations to continue or restart the data back-to-source process.
[0063] Preferably, in any embodiment, the data return-to-source rule is configured with automatic follow-up redirection, and when the object does not exist but redirection is configured, the source station provides a new source station with a redirection address for downloading the object.
[0064] Optionally, in any embodiment, the automatic follow redirection includes a 301 redirection.
[0065] Optionally, in any embodiment, a maximum number of follow times is configured for the automatic follow redirection, and if the object has not been downloaded when the maximum number of follow times is reached, the data return process is stopped.
[0066] Preferably, in any embodiment, downloading the object from the source station includes: downloading the object in a range download manner.
[0067] Optionally, in any embodiment, during the range download process, the byte step size of each download is configured. In this way, the byte compensation can be adjusted according to the characteristics of the current storage system to select a suitable byte step size with the fastest download speed and download data according to the configured byte step size.
[0068] Optionally, in any embodiment, during the range download process, download requests are sent cyclically, and the specified download byte offset range is updated before each new request is sent. In this way, when the cycle ends, all data are downloaded.
[0069] Preferably, in any embodiment, storing the object to be downloaded from the source station in the storage bucket includes: storing the object in the storage bucket by using a segmented upload method. In this case, the segment size can be fixed or variable (configurable), that is, the appropriate segment size can be selected in combination with the characteristics of the current storage system, so that the object can be uploaded at the fastest speed. The ordinary upload method has restrictions on the size of the object, for example, the default size of an object uploaded at a single time does not exceed 5G; when the size of the data that the user returns to the source is larger than 5G, the ordinary upload method cannot meet the data migration requirements, while the segmented upload method has no such restrictions, and the segmented upload method can use concurrent uploads, which greatly improves the speed of object uploads and improves the overall data migration speed.
[0070] Optionally, in any embodiment, storing the object downloaded from the source station in the storage bucket includes: storing the object in the storage bucket in an encrypted manner, thereby ensuring the security of user data and preventing data leakage.
[0071] Optionally, in any embodiment, storing the object downloaded from the source station in the storage bucket includes: storing the object in the storage bucket in a compressed manner, thereby saving space in the current storage system.
[0072] Optionally, in any embodiment, further comprising:
[0073] The storage quota of the storage bucket is checked, and when the remaining storage quota of the storage bucket is insufficient to store the object, the data retrieval process is stopped.
[0074] In this case, when the current object storage service stores the data returned from the source, it will automatically check the storage quota of the current storage bucket. If the remaining storage quota of the current bucket is insufficient to store the data returned from the source, the data return process will be stopped, and an error indicating that the data return failed will be sent to the user to stop downloading the object.
[0075] Optionally, in any embodiment, the data return rule of the storage bucket includes: the version number or version date of the object. In this way, during the data return process, if the user wants to download different versions of the same object, the multi-version function of the current storage bucket can be turned on, and the version number or version date of the object to be downloaded can be carried in the request parameters. The current object storage system will carry the version number or version date to pull the corresponding version of the object data from the source station. When the pulled back object is uploaded to the current storage bucket, since the multi-version function is provided, the object becomes an object with a version number or version date to support the download of multiple versions of the object.
[0076] In a preferred embodiment of the present application, a data source return method for data migration in an object storage is provided, comprising the following steps:
[0077] 1) Provide users with: the following interfaces: setting data back-to-source rules for a bucket, obtaining data back-to-source rules for a bucket, and deleting data back-to-source rules for a bucket, so that users can call the setting data back-to-source rules interface to configure corresponding data back-to-source rules on the bucket they want to return data to, thus making the bucket a data back-to-source bucket;
[0078] 2) The user transfers the old data business in the old object storage system of the old cloud storage service provider to the new object storage system of the new service provider, and uses the new object storage service address in the new object storage system to conduct their own business;
[0079] 3) When a user uses the new object storage service address to download data stored in the old object storage system, the data retrieval process can be triggered, and the required data (i.e., the data of the object) is downloaded to the storage bucket of the new object storage system and sent to the user;
[0080] 4) The user migrates all data in the old object storage system to the new object storage system (any available tools, such as other cold data migration tools, may be used) to complete the entire data migration.
[0081] In a preferred embodiment of the present application, the data return process described in step 3) above may include:
[0082] When a user needs to download an object from a new object storage service, if the object does not exist, the object storage service will automatically check whether a data back-to-source rule has been configured on the current bucket.
[0083] If the current bucket does not have a data return rule configured, a 404 error may be directly returned to the client user, indicating that the object does not exist. Therefore, data return is not performed and the current download request ends.
[0084] If the current bucket has been configured with data back-to-source rules, check whether the configured data back-to-source rules meet the data back-to-source rules of the object, for example, check whether the object prefix name meets the requirements;
[0085] If it is checked that the conditions for triggering the data return-to-source rule of the object are met, the data return-to-source process begins;
[0086] During the data retrieval process, the current object storage service can send a request to download the object to an available source station (the address of the source station has been specified or set in the data retrieval rule) according to the S3 protocol. If the object is available in the source station, the data migration work (i.e., the data retrieval) starts.
[0087] The current object storage service stores the downloaded data (e.g., the object) in the current storage bucket, and can stream (e.g., send in real time) the received data (e.g., the object) to the client user. During this process, the client user is almost unaware of the data return process, so this data migration method will not interrupt the user's normal business.
[0088] The data is returned to the source, the object has been stored in the current new object storage system (eg, the storage bucket), and the client user has successfully received the object.
[0089] In a preferred embodiment of the present application, a data source return method for data migration in an object storage is provided, comprising the following steps:
[0090] Receive an object download request;
[0091] If the object exists, the object is directly provided for download; otherwise, whether a data return-to-source rule is configured for the object in the storage bucket of the current storage system is detected;
[0092] If it is detected that a data return-to-source rule is configured for the object in the storage bucket, the data return-to-source rule is parsed, and if the object meets the data return-to-source rule conditions, the data return-to-source process is executed, wherein a request is made to download the object from the address of the source station configured in the data return-to-source rule according to the S3 protocol, and the object downloaded from the source station is stored in the storage bucket and sent to the user.
[0093] In a preferred embodiment of the present application, a data source return method for data migration in an object storage is provided, comprising the following steps:
[0094] After receiving the object download request, determine whether the object exists: if the object exists, provide the object download to the user; otherwise, check whether a data return-to-source rule is configured for the object in the storage bucket of the current storage system;
[0095] If it is detected that a data return-to-source rule is configured for the object in the storage bucket, the data return-to-source rule is parsed, and the data return-to-source process is executed if the object meets the data return-to-source rule condition;
[0096] Requesting the source site address configured in the data back-to-source rule to download the object according to the S3 protocol, storing the object downloaded from the source site in the storage bucket and sending it to the user;
[0097] The data return process is completed.
[0098] It can be seen that, through the data back-to-source method that can be used for data migration in the object storage provided by the present invention, the data back-to-source rules of the bucket are configured on the bucket of the current object storage system (wherein the data back-to-source rules may include the address of the available source station, the data back-to-source conditions, etc.), when the client user needs to download an object from the object storage bucket but the object does not exist, the object storage service can automatically download the object from the available source station configured on the bucket, not only save the object in the bucket, but also return the object to the client user.
[0099] The implementation of the data back-to-source method that can be used for data migration in the object storage provided in the present invention is transparent to the client user, and can achieve the migration of object data from the source station to the storage bucket of the current object storage service without the client user being aware of it and without affecting the user's business. The source station can be configured as the object storage address of different cloud storage service vendors, which is used for hot data migration between different cloud services, and can meet the user's cross-cloud storage service data migration needs, effectively improving the convenience of users using the object storage service.
[0100] According to an embodiment of the second aspect of the present invention, a data retrieval system for data migration in an object storage is provided, which is used to implement the data retrieval method for data migration in an object storage as described above, including:
[0101] A detection module, configured to detect whether a data return-to-source rule is configured for the object in the storage bucket after receiving an object download request from a user and the object does not exist;
[0102] The data retrieval module is used to: if it is detected that a data retrieval rule is configured for the object in the storage bucket and the object satisfies the data retrieval rule, execute a data retrieval process, wherein a request is made to download the object from the address of the source station configured in the data retrieval rule according to the S3 protocol, and the object downloaded from the source station is stored in the storage bucket and sent to the user.
[0103] According to an embodiment of the third aspect of the present invention, there is provided a data retrieval device that can be used for data migration in an object storage, including a memory and a processor, wherein an executable code is stored in the memory, and when the processor executes the executable code, the data retrieval method that can be used for data migration in an object storage as described above is implemented.
[0104] The data source return method, system, and device for data migration in object storage provided according to one or more embodiments of the present invention can effectively improve the convenience of users in using object services.
[0105] It should be noted that the terms used in the embodiments of the present invention are only for the purpose of describing specific embodiments, and are not intended to limit the present invention. The singular forms of "a", "said" and "the" used in the embodiments of the present invention and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings.
[0106] It should be understood that the term "and / or" used in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.
[0107] It is to be understood that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the device of the embodiment of the present invention. In other embodiments of the specification, the above-mentioned device may include more or fewer components than those shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.
[0108] The various embodiments of the present invention are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.
[0109] Those skilled in the art should be aware that in one or more of the above examples, the functions described in the present invention can be implemented by hardware, software, widgets, or any combination thereof. When implemented by software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium.
[0110] The specific implementation methods described above further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above description is only a specific implementation method of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made on the basis of the technical solution of the present invention should be included in the scope of protection of the present invention.
Claims
1. A data source return method for data migration in object storage, characterized in that: include: A. After receiving an object download request from a user, if the object does not exist, check whether a data return-to-source rule is configured for the object in the storage bucket; B. If it is detected that a data return-to-source rule is configured for the object in the storage bucket and the object satisfies the data return-to-source rule, a data return-to-source process is executed, wherein a request is made to download the object from the address of the source station configured in the data return-to-source rule according to the S3 protocol, and the object downloaded from the source station is stored in the storage bucket and sent to the user.
2. The data source return method for data migration in object storage according to claim 1, characterized in that: Further including: A first data return-to-source rule interface for setting a storage bucket and a second data return-to-source rule interface for obtaining a storage bucket are provided to the user, so that the user can call the first data return-to-source rule interface to configure or modify the data return-to-source rule on the storage bucket to be returned to the source.
3. The data source return method for data migration in object storage according to claim 2, characterized in that: Further including: A third data return-to-source rule interface for deleting a storage bucket is provided for the user, so that the user can call the third data return-to-source rule interface to delete the data return-to-source rule.
4. The data source return method for data migration in object storage according to claim 1, characterized in that: The data return-to-source rule includes the object name prefix of the object; The data return process is performed only on the object having the object name prefix.
5. The data source return method for data migration in object storage according to claim 1, characterized in that: The data return-to-source rule includes a hypertext transfer protocol (http) status code for triggering a data return-to-source process for the object.
6. The data source return method for data migration in object storage according to claim 1, characterized in that: The data return-to-source rule is configured with automatic following redirection, and when the object does not exist but redirection is configured, the source station provides a new source station with a redirection address for downloading the object.
7. The data source return method for data migration in object storage according to claim 1, characterized in that: The downloading of the object from the source station includes: downloading the object in a range download mode.
8. The data source return method for data migration in object storage according to claim 1, characterized in that: The storing the object downloaded from the source station into the storage bucket includes: storing the object into the storage bucket in a piecewise uploading manner.
9. A data source return system that can be used for data migration in object storage, characterized in that: The method is used to implement a data source return method that can be used for data migration in an object storage according to any one of claims 1 to 8, comprising: A detection module, configured to detect whether a data return-to-source rule is configured for the object in the storage bucket after receiving an object download request from a user and the object does not exist; The data retrieval module is used to: if it is detected that a data retrieval rule is configured for the object in the storage bucket and the object satisfies the data retrieval rule, execute a data retrieval process, wherein a request is made to download the object from the address of the source station configured in the data retrieval rule according to the S3 protocol, and the object downloaded from the source station is stored in the storage bucket and sent to the user.
10. A data source return device that can be used for data migration in object storage, characterized in that: It comprises a memory and a processor, wherein the memory stores executable code, and when the processor executes the executable code, the data source return method that can be used for data migration in the object storage according to any one of claims 1 to 8 is implemented.
