Data sharing method and device, electronic equipment and storage medium

Abstract

The invention relates to a data sharing method and device, electronic equipment and a storage medium, and the method comprises the steps: obtaining a mirror image member from a source end data center based on a request of a mirror image replication parameter; wherein the mirror image replication parameters are used for representing mirror image data of mirror image members; acquiring mirror image data of the mirror image member from a target storage platform, and filling the mirror image copy parameter with the mirror image data; and sending the mirror image replication parameter filled with the mirror image data to a target end data center, and obtaining the mirror image data of the mirror image member from the target storage platform based on the mirror image replication parameter. According to the method and the device, the problem that the complete machine mirror image in one data center cannot be used by another data center in the prior art is solved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a data sharing method and device, an electronic device and a storage medium. Background Art

[0002] The existing method of image data sharing is to create the same virtual machine in two data centers, perform the same operation and create a whole machine image for use. It can be seen that in the prior art, the whole machine image in one data center cannot be used by another data center, resulting in low efficiency of image data sharing. Summary of the invention

[0003] The present application provides a data sharing method and device, an electronic device and a storage medium to solve the problem in the prior art that a whole machine image in one data center cannot be used by another data center.

[0004] In a first aspect, the present application provides a data sharing method, comprising: obtaining a mirror member from a source data center based on a request for a mirror replication parameter; wherein the mirror replication parameter is used to characterize the mirror data of the mirror member; obtaining the mirror data of the mirror member from a target storage platform, and filling the mirror data into the mirror replication parameter; sending the mirror replication parameter filled with the mirror data to the target data center, and obtaining the mirror data of the mirror member from the target storage platform based on the mirror replication parameter.

[0005] In a second aspect, the present application provides a data sharing device, comprising: an acquisition module, used to acquire mirror members from a source data center based on a request for mirror replication parameters; wherein the mirror replication parameters are used to characterize the mirror data of the mirror members; a first processing module, used to acquire the mirror data of the mirror members from a target storage platform, and fill the mirror data into the mirror replication parameters; a second processing module, used to send the mirror replication parameters filled with mirror data to the target data center, and acquire the mirror data of the mirror members from the target storage platform based on the mirror replication parameters.

[0006] In a third aspect, the present application provides an electronic device comprising: at least one communication interface; at least one bus connected to the at least one communication interface; at least one processor connected to the at least one bus; and at least one memory connected to the at least one bus, wherein the processor is configured to execute the data sharing method described in the first aspect of the present application.

[0007] In a fourth aspect, the present application further provides a computer storage medium storing computer executable instructions, wherein the computer executable instructions are used to execute the data sharing method described in the first aspect of the present application.

[0008] The above technical solution provided by the embodiment of the present application has the following advantages over the prior art: the method provided by the embodiment of the present application uses the target storage platform as a data transfer. In the process of copying the mirror data of the source data center to the target data center, the corresponding mirror data can be first obtained from the target storage platform, and the obtained mirror data can be filled into the mirror copy parameters, and then the copy parameters can be sent to the target data center to obtain the mirror data of the source data center, thereby realizing the sharing of mirror data between the source data center and the target data center, and solving the problem in the prior art that the whole machine mirror in one data center cannot be used by another data center. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0010] 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, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0011] One or more embodiments are exemplarily described by pictures in the corresponding drawings, and these exemplified descriptions do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings represent similar elements, and unless otherwise stated, the figures in the drawings do not constitute proportional limitations.

[0012] Figure 1 A flow chart of a data sharing method provided in an embodiment of the present application;

[0013] Figure 2 An optional flow chart of a data sharing method provided in an embodiment of the present application;

[0014] Figure 3 A flow chart of processing source data provided in an embodiment of the present application;

[0015] Figure 4 A flowchart of processing target end data provided by an embodiment of the present application;

[0016] Figure 5 A schematic diagram of the structure of a data sharing device provided in an embodiment of the present application;

[0017] Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0018] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0019] The disclosure below provides many different embodiments or examples to implement different structures of the present invention. In order to simplify the disclosure of the present invention, the parts and settings of specific examples are described below. Of course, they are only examples, and the purpose is not to limit the present invention. In addition, the present invention can repeat reference numbers and / or letters in different examples. This repetition is for the purpose of simplification and clarity, and does not itself indicate the relationship between the various embodiments and / or settings discussed.

[0020] First, the relevant terms in the embodiments of the present application are explained;

[0021] Openstack: open source cloud operating system;

[0022] Nova: The component responsible for the computing part of openstack;

[0023] Cinder: The component responsible for the storage part of OpenStack;

[0024] Glance: The component responsible for image management in OpenStack;

[0025] Snapshot: A copy of data at a certain point in time;

[0026] Nova-api / nova-scheduler / nova-compute: the core components of the nova service.

[0027] Figure 1 A flow chart of a data sharing method provided in an embodiment of the present application, such as Figure 1 As shown, the steps of the method include:

[0028] Step 101, based on a request for a mirror replication parameter, obtaining a mirror member from a source data center; wherein the mirror replication parameter is used to characterize the mirror data of the mirror member;

[0029] In a specific example, the data center involved in this application is a data center based on Openstack (open source cloud operating system), which includes multiple components, such as Nova, which is responsible for the computing part; Cinder, which is responsible for the storage part; Glance, which is responsible for the image management component. In addition, the image members in the embodiment of this application may include local system disks, data disks, cloud disks, etc.

[0030] Step 102, obtaining the mirror data of the mirror member from the target storage platform, and filling the mirror data into the mirror replication parameter;

[0031] In a specific example, the target storage platform is a platform for storing data of an object, for example, the storage object is a local system, or the storage object is a data disk, a cloud disk, etc. Based on this, in the embodiment of the present application, the image data of the local system disk can be stored in the glance-related bucket of the target storage platform; the image data of the local data disk can be stored in the kvm backup-related bucket of the target storage platform; the image data of the cloud disk can be stored in the EBS (block storage)-related bucket of the target storage platform.

[0032] Step 103: Send the mirror replication parameters filled with mirror data to the target data center, and obtain the mirror data of the mirror member from the target storage platform based on the mirror replication parameters.

[0033] Through the above steps 101 to 103, with the target storage platform as the data transfer, in the process of copying the mirror data of the source data center to the target data center, the corresponding mirror data can be first obtained from the target storage platform, and the obtained mirror data is filled into the mirror copy parameters, and then the copy parameters are sent to the target data center to obtain the mirror data of the source data center, thereby realizing the sharing of mirror data between the source data center and the target data center, and solving the problem in the prior art that the whole machine mirror in one data center cannot be used by another data center.

[0034] In an optional implementation manner of the embodiment of the present application, when the mirror member in the embodiment of the present application is a local system disk, the method of obtaining the mirror data of the mirror member from the target storage platform and filling the mirror data into the mirror replication parameter involved in the above step 102 may further include:

[0035] Step 11, obtaining the image data of the local system disk from the target storage platform;

[0036] Step 12: Fill the direct connection uniform resource locator URL corresponding to the image data of the local system disk into the image copy parameter.

[0037] In this regard, in a specific example, after the source glance-api in the source data obtains the image data, it can fill the direct_url (direct connection uniform resource locator) of the system disk image into the image copy parameter.

[0038] Based on this, the method of obtaining the mirror data of the mirror member based on the mirror replication parameter involved in the above step 103 may further include:

[0039] Step 21, obtaining the corresponding storage object from the target storage platform based on the direct connection URL;

[0040] Step 22: write the storage object into the storage object corresponding to the target data center in the target storage platform, and generate snapshot information of the storage object.

[0041] In this regard, in a specific example, the target glance_api of the target data center can generate an object readable by the source glance_store target storage platform based on the direct_url in the image replication parameter, and then write the object readable by the source glance_store target storage platform into the target storage platform of the target glance_store. Through the above steps 11 to 12, and steps 21 to 22, the purpose of sharing the image data of the system disk from the source data center to the target data center is achieved.

[0042] In an optional implementation manner of the embodiment of the present application, when the mirror member is a data disk, the method involved in the above step 102 of obtaining the mirror data of the mirror member from the target storage platform and filling the mirror data into the mirror replication parameter may further include:

[0043] Step 31, obtaining replication parameters of the data disk snapshot from the target storage platform;

[0044] Step 32, write the replication parameters of the data disk snapshot into the image replication parameters.

[0045] For the above steps 31 and 32, in a specific example, the source glance_api in the source data requests the source nova_api for the replication parameters of the data disk snapshot. After nova_api feeds back the assignment parameters of the data disk snapshot, glance_api fills the replication parameters of the data disk snapshot into the image replication parameters.

[0046] The method of obtaining the mirror data of the mirror member based on the mirror replication parameter involved in the above step 102 may further include:

[0047] Step 41 : based on the replication parameters of the data disk snapshot in the mirror replication parameters, cache the data disk snapshot to obtain the mirror data of the data disk.

[0048] In this regard, in a specific example, a data disk snapshot is obtained through the mirror replication parameters sent by the source data center, and the mirror data of the corresponding data disk is started. It can be seen that through the above steps 31 to 22, and step 41, the purpose of sharing the mirror data of the data disk from the source data center to the target data center is achieved.

[0049] In an optional implementation of the embodiment of the present application, when the mirror member is a cloud disk, the method involved in the above step 102 of obtaining the mirror data of the mirror member from the target storage platform and filling the mirror data into the mirror replication parameter may further include:

[0050] Step 51, obtaining link information of the cloud disk snapshot from the target storage platform;

[0051] Step 52: Generate replication parameters of the cloud disk snapshot based on the link information, and fill the replication parameters of the cloud disk snapshot into the image replication parameters.

[0052] In this regard, in a specific example, the source glance_api of the source data center requests the link information of the snapshot from the source cinder-api, the source cinder-api requests the link information of the snapshot from the source cinder_volume, the source cinder_volume feeds back the link information of the snapshot to the source cinder-api, and the source cinder-api feeds back the link information of the snapshot to the source glance_api. The source glance_api generates the replication parameters of the cloud disk snapshot based on the link information and fills it into the image replication parameters.

[0053] The method of obtaining the mirror data of the mirror member based on the mirror replication parameter involved in the above step 102 may further include:

[0054] Step 61 : acquiring the replication parameters of the corresponding cloud disk snapshot based on the image replication parameters, and replicating the image data of the cloud disk based on the replication parameters of the cloud disk snapshot.

[0055] In this regard, in a specific example, after the target glance_api of the target data center obtains the snapshot information of the cloud disk based on the image replication parameters, the snapshot information is written into the target glance_store cinder, the glance_storecinder creates a virtual volume and a virtual snapshot to the target cinder_api, and uploads the snapshot information to the virtual snapshot, and the snapshot information of the cloud disk data is cached by the target glance_api. It can be seen that through the above steps 51 to 52, and step 61, the purpose of sharing the image data of the cloud disk from the source data center to the target data center is achieved.

[0056] like Figure 2 As shown, in an optional implementation manner of the embodiment of the present application, the method of the embodiment of the present application may also include:

[0057] Step 104 , globally lock the mirror data replication process, wherein the global lock indicates that only one replication task is executed at the same time, and one replication task includes replication of mirror data of one or more different mirror members.

[0058] Step 105: Set an upper limit on the number of data copies executed by a copy task.

[0059] In the embodiment of the present application, since resources such as disk and storage platform upload and download will be consumed during the data replication process, it is necessary to control the concurrency of the replication process. First, in the embodiment of the present application, only one replication task can be executed at the same time, and the replication task can only be for one or more mirror members. For example, the current replication task is for the replication of the mirror data in the local system disk and the data disk, and for the replication of part of the data in the local system disk and the data disk, if it is necessary to copy the remaining data in the local system disk and the data disk, it is necessary to wait until the current replication task is completed before the next replication task can be created. In this way, it is possible to avoid excessive resource occupation by the replication task, and it is also possible to ensure the stable execution and completion of the replication task. In addition, in the embodiment of the present application, the number of a replication task is also set with an upper limit, and it is implemented by means of a token bucket. For example, the number of tokens in the token bucket corresponding to the current replication task is set to 500, and the current replication task can have a maximum of 500 data.

[0060] The present application is explained below in conjunction with a specific implementation of an embodiment of the present application. The specific implementation provides a method for supporting cross-machine room sharing of whole machine images, such as Figure 3 The following is the execution process of the source data center, and the process includes:

[0061] Step 301, dashboard (control panel) requests copy parameters from source glance_api;

[0062] Step 302, source glance_api obtains image member information;

[0063] Step 303, the source glance_api fills the direct_url of the system disk image into the image copy parameter;

[0064] Step 304: The source glance_api requests the source nova_api for replication parameters of the local data disk snapshot;

[0065] Step 305, the source nova_api feeds back the replication parameters of the local data disk snapshot to the source glance_api;

[0066] Step 306, the source glance_api fills the replication parameters of the local data disk snapshot into the image replication parameters;

[0067] Step 307, the source glance_api requests the source cinder_api for snapshot link information;

[0068] Step 308, the source cinder_api requests the link information of the snapshot from the source cinder_volume;

[0069] Step 309, the source cinder_volume feeds back the snapshot link information to the source cinder_api;

[0070] Step 310, the source cinder_api feeds back the link information of the snapshot to the source glance_api;

[0071] Step 311, the source glance_api generates cloud disk snapshot replication parameters and fills them into the image replication parameters;

[0072] Step 312: The source glance_api returns the image replication parameters to the dashboard.

[0073] like Figure 4 The figure shows the processing flow of the target data center, and the process includes:

[0074] Step 401, dashboard sends image replication parameters to the target glance_api and requests to start replication;

[0075] Step 402, the target glance_api creates a new image;

[0076] Step 403, the destination glance_api generates a source glance_store target storage platform readable object;

[0077] Step 404, the destination glance_api writes the source glance_store target storage platform into the destination glance_store target storage platform according to the objects that can be read by the source glance_store target storage platform;

[0078] Step 405: The target glance_api generates a source glance_store cinder readable object

[0079] Step 406, the destination glance_api writes the object readable by the source glance_store cinder into the destination glance_store target storage platform;

[0080] Step 407, caching system disk snapshot information;

[0081] Step 408, the destination glance_api sends the assignment parameters of the source local data snapshot to the destination nova_api, and starts copying;

[0082] Step 409, the target glance_api obtains the snapshot status;

[0083] Step 410, target glance_api cache data snapshot information;

[0084] Step 411, the target glance_api writes the snapshot information to the target glance_store cinder;

[0085] Step 412, the target glance_store cinder creates a virtual volume and a virtual snapshot to the target cinder_api

[0086] Step 413, the target glance_store cinder uploads the snapshot to the virtual snapshot;

[0087] Step 414, target glance_api cache data snapshot information;

[0088] Step 415, the target glance_api saves the snapshot information into the mirror data.

[0089] Through the above Figure 3 and Figure 4 , taking the target storage platform as the data transfer station, the whole machine image member data of the source end is downloaded through the mirror node and uploaded to the destination end, realizing the sharing of the whole machine image across computer rooms.

[0090] Corresponding to the above Figure 1 , the embodiment of the present application also provides a data sharing device, such as Figure 5 As shown, the device comprises:

[0091] The acquisition module 502 is used to acquire the mirror member from the source data center based on the request of the mirror replication parameter; wherein the mirror replication parameter is used to characterize the mirror data of the mirror member;

[0092] The first processing module 504 is used to obtain the mirror data of the mirror member from the target storage platform and fill the mirror data into the mirror replication parameter;

[0093] The second processing module 506 is used to send the mirror replication parameters filled with mirror data to the target data center, and obtain the mirror data of the mirror member from the target storage platform based on the mirror replication parameters.

[0094] Through the device of the embodiment of the present application, the target storage platform is used as a data transfer. In the process of copying the mirror data of the source data center to the target data center, the corresponding mirror data can be first obtained from the target storage platform, and the obtained mirror data is filled into the mirror copy parameters, and then the copy parameters are sent to the target data center to obtain the mirror data of the source data center, thereby realizing the sharing of mirror data between the source data center and the target data center, and solving the problem in the prior art that the whole machine mirror in one data center cannot be used by another data center.

[0095] In an optional implementation of an embodiment of the present application, the mirror member is a local system disk, and the first processing module includes: a first processing unit, which is used to obtain the mirror data of the local system disk from the target storage platform, and fill the direct connection uniform resource locator URL corresponding to the mirror data of the local system disk into the mirror copy parameter; the second processing module includes: a second processing unit, which is used to obtain the corresponding storage object from the target storage platform based on the direct connection URL, write the storage object into the storage object corresponding to the target data center in the target storage platform, and generate snapshot information of the storage object.

[0096] In an optional implementation of an embodiment of the present application, the mirror member is a data disk, and the first processing module includes: a third processing unit, used to obtain the replication parameters of the data disk snapshot from the target storage platform, and write the replication parameters of the data disk snapshot into the mirror replication parameters; the second processing module includes: a fourth processing unit, used to cache the data disk snapshot based on the replication parameters of the data disk snapshot in the mirror replication parameters to obtain the mirror data of the data disk.

[0097] In an optional implementation of an embodiment of the present application, the mirror member is a cloud disk, and the first processing module includes: a fifth processing unit, which is used to obtain the link information of the cloud disk snapshot from the target storage platform, and generate the replication parameters of the cloud disk snapshot based on the link information, and fill the replication parameters of the cloud disk snapshot into the mirror replication parameters; the second processing module includes: a sixth processing unit, which is used to obtain the replication parameters of the corresponding cloud disk snapshot based on the mirror replication parameters, and replicate the mirror data of the cloud disk based on the replication parameters of the cloud disk snapshot.

[0098] In an optional implementation of the embodiment of the present application, the device of the embodiment of the present application may also include: a third processing module, which is used to globally lock the copying process of the mirror data, wherein the global lock indicates that only one copy task is executed at the same time, and one copy task includes the copying of the mirror data of one or more different mirror members.

[0099] In an optional implementation manner of the embodiment of the present application, the device of the embodiment of the present application may further include: a setting module, used to set an upper limit on the number of data copies performed by a copy task.

[0100] like Figure 6 As shown, the embodiment of the present application provides an air conditioner control device, including a processor 611, a communication interface 612, a memory 613 and a communication bus 614, wherein the processor 611, the communication interface 612, and the memory 613 communicate with each other through the communication bus 614.

[0101] Memory 613, used for storing computer programs;

[0102] In one embodiment of the present application, the processor 611 is used to implement the data sharing method provided by any of the aforementioned method embodiments when executing the program stored in the memory 613. The role it plays is similar and will not be repeated here.

[0103] An embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of the data sharing method provided in any one of the aforementioned method embodiments are implemented.

[0104] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0105] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a general hardware platform, and of course, by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the relevant technology can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0106] It should be understood that the terms used herein are only for the purpose of describing specific example embodiments and are not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms "one", "an" and "said" as used herein may also be meant to include plural forms. The terms "include", "comprise", "contain", and "have" are inclusive, and therefore specify the existence of stated features, steps, operations, elements and / or parts, but do not exclude the existence or addition of one or more other features, steps, operations, elements, parts, and / or combinations thereof. The method steps, processes, and operations described herein are not interpreted as necessarily requiring them to be performed in the specific order described or illustrated, unless the execution order is clearly indicated. It should also be understood that additional or alternative steps may be used.

[0107] The foregoing is merely a specific embodiment of the present invention, which enables those skilled in the art to understand or implement the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A data sharing method, characterized in that: include: Based on the request of the mirror replication parameter, the mirror member is obtained from the source data center; wherein the mirror replication parameter is used to characterize the mirror data of the mirror member; Acquire the mirror data of the mirror member from the target storage platform, and fill the mirror data into the mirror replication parameter; The mirror replication parameters filled with mirror data are sent to the target data center, and the mirror data of the mirror member is acquired from the target storage platform based on the mirror replication parameters.

2. The method according to claim 1, characterized in that The mirror member is a local system disk; Acquiring the image data of the image member from the target storage platform, and filling the image data into the image replication parameter, including: acquiring the image data of the local system disk from the target storage platform, and filling the direct connection uniform resource locator URL corresponding to the image data of the local system disk into the image replication parameter; The mirror data of the mirror member is obtained based on the mirror replication parameters, including: obtaining the corresponding storage object from the target storage platform based on the direct connection URL, writing the storage object into the storage object corresponding to the target data center in the target storage platform, and generating snapshot information of the storage object.

3. The method according to claim 1, characterized in that The mirror member is a data disk; Acquiring the mirror data of the mirror member from the target storage platform and filling the mirror data into the mirror replication parameter, including: acquiring the replication parameter of the data disk snapshot from the target storage platform, and writing the replication parameter of the data disk snapshot into the mirror replication parameter; Acquiring the mirror data of the mirror member based on the mirror replication parameters includes: based on the replication parameters of the data disk snapshot in the mirror replication parameters, caching the data disk snapshot to obtain the mirror data of the data disk.

4. The method according to claim 1, characterized in that: The mirror member is a cloud disk; Acquiring the image data of the image member from the target storage platform and filling the image data into the image replication parameter, including: acquiring the link information of the cloud disk snapshot from the target storage platform, generating the replication parameter of the cloud disk snapshot based on the link information, and filling the replication parameter of the cloud disk snapshot into the image replication parameter; Acquiring the mirror data of the mirror member based on the mirror replication parameter includes: acquiring the replication parameters of the corresponding cloud disk snapshot based on the mirror replication parameter, and replicating the mirror data of the cloud disk based on the replication parameters of the cloud disk snapshot.

5. The method according to claim 1, characterized in that The method further comprises: A global lock is performed on the mirror data replication process, wherein the global lock indicates that only one replication task is executed at the same time, and the one replication task includes replication of mirror data of one or more different mirror members.

6. The method according to claim 5, characterized in that The method further comprises: Set an upper limit on the number of data copies executed by the copy task.

7. A data sharing device, characterized in that: include: An acquisition module, used to acquire a mirror member from a source data center based on a request for a mirror replication parameter; wherein the mirror replication parameter is used to characterize the mirror data of the mirror member; A first processing module, configured to obtain the image data of the image member from the target storage platform, and fill the image data into the image replication parameter; The second processing module is used to send the mirror replication parameters filled with mirror data to the target data center, and obtain the mirror data of the mirror member from the target storage platform based on the mirror replication parameters.

8. The device according to claim 7, characterized in that The mirror member is a local system disk; The first processing module includes: a first processing unit, configured to obtain the image data of the local system disk from the target storage platform, and fill the direct connection uniform resource locator URL corresponding to the image data of the local system disk into the image copy parameter; The second processing module includes: a second processing unit, which is used to obtain the corresponding storage object from the target storage platform based on the direct connection URL, write the storage object into the storage object corresponding to the target data center in the target storage platform, and generate snapshot information of the storage object.

9. An electronic device, comprising: at least one communication interface; at least one bus connected to the at least one communication interface; at least one processor coupled to the at least one bus; At least one memory connected to the at least one bus, wherein the processor is configured to execute the data sharing method according to any one of claims 1 to 6 of the present application.

10. A computer storage medium storing computer executable instructions, wherein the computer executable instructions are used to execute the data sharing method according to any one of claims 1 to 6 of the present application.

Images