CN117609148A - Data migration method, device, equipment and storage medium - Google Patents

Abstract

This application relates to a data migration method, device, equipment and storage medium, which relates to the field of communication technology and is applied to the destination. The destination belongs to a distributed file system. The distributed file system also includes: a source and a server; distributed files The system is an open source system. The method includes: responding to a mounting instruction, mounting a target storage block in the server; wherein the target storage block stores target data of the source end; and then, responding to the migration instruction, migrating the data in the target storage block to the destination end. This application is used for secure data migration.

Description

Data migration methods, devices, equipment and storage media

Technical field

The present application relates to the field of communication technology, and in particular, to a data migration method, device, equipment and storage medium.

Background technique

The cloud computing technology provided by the cloud platform allows enterprises to adjust computing power, storage resources and network resources according to actual needs, and flexibly respond to changes in business needs without worrying about insufficient or wasted hardware resources. Therefore, enterprises need to migrate business systems to cloud platforms.

The existing technology usually installs migration software on the local side of the enterprise and the cloud platform, and builds a transmission tunnel between the two migration software, thereby completing the migration of the business system from the local side to the cloud platform.

However, due to the insecurity of the migration software, the security of business system migration cannot be guaranteed.

Contents of the invention

This application provides a data migration method, device, equipment and storage medium to at least solve the problem in the existing technology that the security of business system migration cannot be guaranteed due to the insecurity of migration software. The technical solution of this application is as follows:

The first aspect is to provide a data migration method, which is applied to the destination. The destination belongs to the distributed file system. The distributed file system also includes: the source and the server; the distributed file system is an open source system; the method includes: response In response to the mount instruction, the target storage block in the server is mounted; the target storage block stores the target data of the source end; in response to the migration instruction, the data in the target storage block is migrated to the destination end.

In a possible implementation, the target storage block includes: a first storage block, or a second storage block; the first storage block is obtained by copying the target data; the second storage block is obtained by copying the first storage block. Snapshot obtained.

In a possible implementation, the above method further includes: receiving user information and permission information sent by the server; and establishing a connection relationship between the destination and the server based on the user information and permission information.

In the second aspect, a data migration method is provided, which is applied to the source end. The source end belongs to the distributed file system. The distributed file system also includes: the destination end and the server; the distributed file system is an open source system; the method includes: response In response to the mount instruction, the first storage block in the server is mounted; in response to the copy instruction, the target data of the source end is copied to the first storage block, so that the destination end migrates the target data to the destination end according to the first storage block.

In a possible implementation, the above method further includes: receiving user information and permission information sent by the server; and establishing a connection relationship between the source end and the server based on the user information and permission information.

In the third aspect, a data migration device is provided, which is applied to the destination. The destination belongs to the distributed file system. The distributed file system also includes: the source and the server; the distributed file system is an open source system; the data migration device It includes: a mounting unit and a migration unit; the mounting unit is used to mount the target storage block in the server in response to the mounting instruction; the target storage block stores the target data of the source end; the migration unit is used to respond to the migration instruction, Migrate the data in the target storage block to the destination.

In a possible implementation, the target storage block includes: a first storage block, or a second storage block; the first storage block is obtained by copying the target data; the second storage block is obtained by copying the first storage block. Snapshot obtained.

In a possible implementation, the above-mentioned data migration device further includes a receiving unit and an establishing unit; the receiving unit is used to receive user information and authority information sent by the server; and the establishing unit is used to establish the purpose based on the user information and authority information. The connection relationship between the client and the server.

In the fourth aspect, a data migration device is provided, which is applied to the source end. The source end belongs to the distributed file system. The distributed file system also includes: the destination end and the server; the distributed file system is an open source system; the data migration device It includes a mounting unit and a copying unit; the mounting unit is used to mount the first storage block in the server in response to the mounting instruction; the copying unit is used to copy the target data from the source to the first storage in response to the copying instruction. block, so that the destination end migrates the target data to the destination end based on the first storage block.

In a possible implementation, the above-mentioned data migration device further includes a receiving unit and a establishing unit; the receiving unit is used to receive user information and authority information sent by the server; and the establishing unit is used to establish the source based on the user information and authority information. The connection relationship between the client and the server.

A fifth aspect provides an electronic device, including: a processor. Memory used to store instructions executable by the processor. Wherein, the processor is configured to execute instructions to implement the method of the above-mentioned first aspect and any possible implementation thereof, or to implement the method of the above-mentioned second aspect and any possible implementation thereof.

A sixth aspect provides a computer-readable storage medium that, when instructions in the computer-readable storage medium are executed by a processor of an electronic device, enables the electronic device to execute the above-mentioned first aspect and any of its possible implementations. method, or a method for performing the above second aspect and any possible implementation thereof.

A seventh aspect provides a computer program product. The computer program product includes computer instructions. When the computer instructions are run on an electronic device, the electronic device causes the electronic device to execute the method of the first aspect and any of its possible implementations, or, The method of performing the above second aspect and any possible implementation manner thereof.

The first aspect of the technical solution provided by this application at least brings the following beneficial effects: the existing technology uses migration software for data migration. Due to the insecurity of the migration software, the security of business system migration cannot be guaranteed. This application provides a data migration method, which is applied to the destination end. The destination end belongs to the distributed file system. The distributed file system also includes: the source end and the server; the distributed file system is an open source system; the method includes: responding to the hanging The load instruction is used to mount the target storage block in the server; the target storage block stores the target data of the source end; and then, in response to the migration instruction, the data in the target storage block is migrated to the destination end. Since the distributed file system is an open source system, it can ensure the security of data migration and improve the security of data migration.

It should be noted that the technical effects brought by any implementation method in the second to seventh aspects can be referred to the technical effects brought by the corresponding implementation method in the first aspect, and will not be described again here.

It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and do not limit the present application.

Description of drawings

The drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present application, and are used together with the description to explain the principles of the present application, and do not constitute undue limitations on the present application.

Figure 1 is a schematic structural diagram of a distributed file system according to an exemplary embodiment;

Figure 2 is a flow chart of a data migration method according to an exemplary embodiment;

Figure 3 is a flow chart of yet another data migration method according to an exemplary embodiment;

Figure 4 is a schematic diagram of a data migration method according to an exemplary embodiment;

Figure 5 is a block diagram of a data migration device according to an exemplary embodiment;

Figure 6 is a block diagram of yet another data migration device according to an exemplary embodiment;

FIG. 7 is a block diagram of an electronic device according to an exemplary embodiment.

Detailed ways

In order to enable ordinary people in the art to better understand the technical solutions of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings.

It should be noted that the terms "first", "second", etc. in the description and claims of this application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances so that the embodiments of the application described herein can be practiced in sequences other than those illustrated or described herein. The implementations described in the following exemplary embodiments do not represent all implementations consistent with this application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the appended claims.

Before introducing the data migration method provided in this application in detail, the background technology involved in this application will be briefly introduced.

With the development of cloud computing technology, more and more enterprises will use cloud computing technology to carry their own business. Different cloud operators continue to launch various products based on the development of cloud computing. Enterprises can choose a cloud platform that suits them based on the characteristics of the product. However, if it is the first time for an enterprise to use a cloud platform, it needs to migrate its local business systems to the cloud platform. If an enterprise changes cloud operators, it needs to migrate the source business system to the destination.

Existing technologies usually migrate business systems through the following two methods: 1. Deploy a new business system. However, deploying new business systems requires a lot of time for debugging, data recovery, and business testing, which will have a great impact on existing businesses. 2. Migrate existing applications, data and business processes from the local side (such as private data centers) to the cloud platform. Cloud migration involves moving applications and data from physical servers, virtual machines, or other cloud environments to a cloud service provider's cloud platform. This approach can reduce the cost of redeploying business systems in the cloud. At the same time, there is no need to make changes to the existing business, and the business system can be switched to the cloud within the allowed time.

However, the above-mentioned second method has the following shortcomings: 1. A network tunnel needs to be established between the local end and the cloud platform. When the network quality of the network tunnel is poor, it will cause errors in the migration data, causing the migration to fail. 2. When data is migrated through a network tunnel, data cannot be backed up during the migration process, resulting in the inability to restore the migrated data in the event of data loss. 3. The network tunnel is provided by the server and consumes additional resources. 4. Migration software needs to be installed on the local side and the cloud platform to establish a network tunnel, and the migration software may affect the stability and security of the local side. 5. Cross-system migration requires that the storage capacity, central processing unit (CPU) number, and memory of the local end and the destination end are consistent. It also relies on the software and hardware performance of the intermediate server, which increases the difficulty of migration.

Before introducing the data migration method provided in this application in detail, the implementation environment (implementation architecture) involved in this application will be briefly introduced.

The data migration method provided by the embodiments of this application can be applied to distributed file systems. Figure 1 shows a schematic structural diagram of the distributed file system. As shown in FIG. 1 , the distributed file system 10 includes a server 11 , a source end 12 , and a destination end 13 .

The server 11 is used to configure user information and permission information, and send the user information and permission information to the source end 12 . The server 11 is also used to send user information and authority information to the destination 13 .

The source end 12 is used to receive user information and permission information sent by the server. According to the user information and authority information, the connection relationship between the source end 12 and the server 11 is established.

The destination 13 is used to receive user information and permission information sent by the server. According to the user information and authority information, a connection relationship between the destination terminal 13 and the server 11 is established.

The source end 12 is also configured to mount the first storage block in the server 11 in response to the mount instruction. In response to the copy instruction, the target data of the source end is copied to the first storage block, so that the destination end migrates the target data to the destination end according to the first storage block.

The server 11 is used to take a snapshot of the first storage block to obtain the second storage block.

The destination end 13 is used to mount the target storage block in the server in response to the mount instruction. The target storage block includes: a first storage block, or a second storage block. The first storage block is obtained by copying the target data. The second storage block is obtained by taking a snapshot of the first storage block.

The destination 13 is also used to migrate the data in the target storage block to the destination in response to the migration instruction.

For ease of understanding, the data migration method provided by this application is introduced in detail below with reference to the accompanying drawings.

FIG. 2 is a flow chart of a data migration method according to an exemplary embodiment, which is applied to the destination end in the distributed file system. As shown in Figure 2, this data migration method includes the following steps:

S201. The destination responds to the mounting instruction and mounts the target storage block in the server.

Among them, the target storage block stores the target data of the source end.

As a possible implementation manner, when the target storage block is the first storage block, the source end copies the target data to the first storage block. Afterwards, the destination responds to the mount instruction and mounts the first storage block in the server.

As another possible implementation manner, when the target storage block is the second storage block, the source end copies the target data to the first storage block. Afterwards, the server takes a snapshot of the first storage block and obtains the second storage block. Further, the destination responds to the mount instruction and mounts the second storage block in the server.

For example, the source end is the host that needs to be migrated, and the destination end is the host to which the source end is migrated.

S202. The destination responds to the migration instruction and migrates the data in the target storage block to the destination.

As a possible implementation manner, the destination responds to the migration instruction and migrates the data in the first storage block to the destination.

As another possible implementation manner, the destination responds to the migration instruction and migrates the data in the second storage block to the destination.

It is understandable that the existing technology uses migration software for data migration. Due to the insecurity of the migration software, the security of business system migration cannot be guaranteed. This application provides a data migration method, which is applied to the destination end. The destination end belongs to the distributed file system. The distributed file system also includes: the source end and the server. The distributed file system is an open source system. The method includes: in response to a mount instruction, mounting a target storage block in the server. Among them, the target storage block stores the target data of the source end. Afterwards, in response to the migration instruction, the data in the target storage block is migrated to the destination. Since the distributed file system is an open source system, it can ensure the security of data migration and improve the security of data migration.

In a possible implementation, the target storage block includes: a first storage block, or a second storage block. The first storage block is obtained by copying the target data. The second storage block is obtained by taking a snapshot of the first storage block.

It can be understood that by taking a snapshot of the first storage block, the second storage block can be obtained, and the target data can be backed up, so that in the process of migrating the target data from the target storage block to the destination, the target data is modified. In this case, data restoration is achieved through the first storage block or the second storage block.

The embodiment of the present application provides another data migration method, which is applied to the distributed file system. As shown in Figure 3, the method includes the following steps:

S301. The server responds to the configuration instruction and configures user information and permission information.

As a possible implementation manner, the server creates the first storage block in the storage pool in response to the creation instruction. Afterwards, the server responds to the configuration instructions and configures user information and permission information.

As another possible implementation, manually prepare servers and network equipment. After that, Internet protocol (IP) addresses, storage channels, and management channels are manually planned to adjust the network between various network devices. Next, the operating system, monitor (monitor), storage library (librados), and storage block device (rados block device, RBD) services are manually installed on the server. Then, manually perform the basic configuration of endpoint, authentication, and storage pool. Next, a creation instruction is manually input, and the server creates the first storage block in the storage pool in response to the creation instruction. Further, the configuration instructions are manually input, and the server responds to the configuration instructions and configures user information and permission information. Afterwards, the server enters the user information and permission information into the keyring file.

As an example, the distributed file system can be a ceph system.

S302. In response to the sending instruction, the server sends user information and permission information to the source end.

S303. The source receives the user information and permission information sent by the server.

As a possible implementation method, manually download the distributed file system client corresponding to the operating system based on the source operating system. After that, manually set the parameters of the distributed file system client based on the key ring file. Further, the source receives the user information and permission information sent by the server.

As an example, the distributed file system client can be a ceph client.

S304. The source end establishes a connection relationship between the source end and the server based on the user information and permission information.

As a possible implementation method, manually enter user information and permission information into the distributed file system client corresponding to the source end, and log in to the distributed file system client corresponding to the source end. Afterwards, the source end responds to the login instruction and establishes a connection relationship between the source end and the server based on the user information and permission information.

S305. The source end responds to the mounting instruction and mounts the first storage block in the server.

As a possible implementation method, manually enter the mount instructions in the distributed file system client corresponding to the source end. Afterwards, the source responds to the mount instruction and mounts the first storage block in the server.

S306. In response to the copy instruction, the source end copies the target data of the source end to the first storage block, so that the destination end migrates the target data to the destination end according to the first storage block.

As a possible implementation manner, the source end copies the target data of the source end to the first storage block in response to the copy instruction.

For example, when the source operating system is Windows, the copy command can be the "backup current file" command that comes with Windows. The copy command can also be a system migration command of a third-party software. When the source operating system is Linux, the copy instructions can be dd, cp and other instructions.

S307. In response to the snapshot instruction, the server takes a snapshot of the first storage block to obtain the second storage block.

S308. In response to the sending instruction, the server sends user information and permission information to the destination.

S309. The destination receives the user information and permission information sent by the server.

As a possible implementation method, manually download the distributed file system client corresponding to the operating system based on the operating system of the destination. After that, manually set the parameters of the distributed file system client based on the key ring file. Further, the destination receives the user information and permission information sent by the server.

S310. The destination establishes a connection relationship between the destination and the server based on the user information and permission information.

As a possible implementation method, manually enter user information and permission information into the distributed file system client corresponding to the destination, and log in to the distributed file system client corresponding to the destination. Afterwards, the source end responds to the login instruction and establishes a connection relationship between the destination end and the server based on the user information and permission information.

S311. The destination responds to the mounting instruction and mounts the second storage block in the server.

S312. The destination responds to the migration instruction and migrates the data in the second storage block to the destination.

As a possible implementation manner, the destination responds to the migration instruction and migrates the data in the second storage block to the destination.

For example, when the operating system of the destination is Windows, the migration instruction can be the "restore" instruction provided by Windows. The restore instruction can also be the system migration instruction of a third-party software. When the operating system of the destination is Linux, the migration instructions can be dd, cp and other instructions.

For example, after migrating the data of the second storage block to the destination, the boot disk needs to be adjusted according to the virtualization software so that the migrated system disk can be used as the system disk.

For example, after migrating the data of the second storage block to the destination, the performance and data of data restoration need to be verified. For example, when the operating system is Windows, the drive letter of the data disk needs to be adjusted to ensure the validity of the link. After the verification is completed, the storage blocks provided by the distributed file system can be unmounted. For example, detach the first storage block mounted on the source end and the second storage block mounted on the destination end. At the same time, if data migration needs to be performed again, just mount the first storage block or the second storage block directly. When the migration of target data involves hardware replacement, the corresponding driver needs to be installed on the destination.

For example, after migrating the data of the second storage block to the destination, the target data of the source can be deleted to save storage resources.

It is understandable that since the distributed file system is an open source system, by building a distributed file system, data migration can be carried out while ensuring data security. At the same time, since the second storage block is obtained by taking a snapshot of the first storage block, if a problem occurs during data migration between the second storage block and the destination, the first storage block can be mounted or the first storage block can be mounted again. Block snapshots are taken to ensure that the data migrated to the destination is the target data of the source, further ensuring the effectiveness of data migration.

Figure 4 is a schematic diagram of a data migration method provided by an embodiment of the present application. As shown in Figure 4, after the source end mounts the first storage block, the target data in the source end is copied to the first storage block. Afterwards, the server takes a snapshot of the first storage block and obtains the second storage block. Then, the destination mounts the second storage block and copies the target data in the second storage block to the destination, thereby completing the data migration.

The above mainly introduces the solutions provided by the embodiments of the present application from the perspective of methods. In order to realize the above functions, the data migration device or electronic device includes hardware structures and/or software modules corresponding to each function. Persons skilled in the art should easily realize that, with the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed by hardware or computer software driving the hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered beyond the scope of this application.

Embodiments of the present application can exemplarily divide the data migration apparatus or electronic equipment into functional modules according to the above method. For example, the data migration apparatus or electronic equipment may include functional modules corresponding to each functional division, or two or Two or more functions are integrated into one processing module. The above integrated modules can be implemented in the form of hardware or software function modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. In actual implementation, there may be other division methods.

Figure 5 shows a data migration device 400 according to an exemplary embodiment. It is applied to the destination end. The destination end belongs to the distributed file system. The distributed file system also includes: a source end and a server. The distributed file system is an open source system. As shown in FIG. 5 , the data migration device 400 includes: a mounting unit 401 , a migration unit 402 , a receiving unit 403 and an establishing unit 404 .

The mounting unit 401 is used to mount the target storage block in the server in response to the mounting instruction. The target storage block stores the target data of the source side.

The migration unit 402 is used to migrate the data in the target storage block to the destination in response to the migration instruction.

Optionally, the target storage block includes: a first storage block, or a second storage block. The first storage block is obtained by copying the target data. The second storage block is obtained by taking a snapshot of the first storage block.

Optionally, in order to establish a connection relationship between the destination end and the server, as shown in Figure 5, the receiving unit 403 is used to receive user information and permission information sent by the server.

The establishment unit 404 is used to establish a connection relationship between the destination and the server based on the user information and authority information.

Figure 6 shows a data migration device 500 according to an exemplary embodiment. It is applied to the source end. The source end belongs to the distributed file system. The distributed file system also includes: a destination end and a server. The distributed file system is an open source system. As shown in FIG. 6 , the data migration device 500 includes a mounting unit 501 , a copying unit 502 , a receiving unit 503 and an establishing unit 504 .

The mounting unit 501 is configured to mount the first storage block in the server in response to the mounting instruction.

The copy unit 502 is configured to copy the target data of the source end to the first storage block in response to the copy instruction, so that the destination end migrates the target data to the destination end according to the first storage block.

Optionally, in order to establish a connection relationship between the source end and the server, as shown in Figure 6, the receiving unit 503 is used to receive user information and permission information sent by the server.

The establishment unit 504 is used to establish a connection relationship between the source end and the server based on the user information and permission information.

FIG. 7 is a block diagram of an electronic device according to an exemplary embodiment. As shown in FIG. 7 , the electronic device 600 includes but is not limited to: a processor 601 and a memory 602 .

The above-mentioned memory 602 is used to store executable instructions of the above-mentioned processor 601. It can be understood that the above-mentioned processor 601 is configured to execute instructions to implement the data migration method in the above embodiment.

It should be noted that those skilled in the art can understand that the structure of the electronic device shown in Figure 7 does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than those shown in Figure 7, or a combination of certain components. components, or different component arrangements.

The processor 601 is the control center of the electronic device, using various interfaces and lines to connect various parts of the entire electronic device, by running or executing software programs and/or modules stored in the memory 602, and calling data stored in the memory 602 , perform various functions of the electronic device and process data, thereby overall monitoring the electronic device. Processor 601 may include one or more processing units. Optionally, the processor 601 can integrate an application processor and a modem processor, where the application processor mainly processes the operating system, user interface, application programs, etc., and the modem processor mainly processes wireless communications. It can be understood that the above modem processor may not be integrated into the processor 601.

Memory 602 may be used to store software programs as well as various data. The memory 602 may mainly include a program storage area and a data storage area, where the program storage area may store an operating system, an application program required by at least one functional module, etc. (such as a mounting unit, a copy unit, a receiving unit, and a creation unit). In addition, memory 602 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.

In an exemplary embodiment, a computer-readable storage medium including instructions, such as a memory including instructions, is also provided, and the instructions can be executed by a processor of an electronic device to implement the data migration method in the above embodiment.

In actual implementation, the functions of the mounting unit 401, the migration unit 402, the receiving unit 403 and the establishing unit 404, or the functions of the mounting unit 501, the copying unit 502, the receiving unit 503 and the establishing unit 504 can all be processed by the process in Figure 7 The processor 601 calls the computer program stored in the memory 602 for implementation. For its specific execution process, please refer to the description of the data migration method in the above embodiment, and will not be described again here.

Optionally, the computer-readable storage medium may be a non-transitory computer-readable storage medium. For example, the non-transitory computer-readable storage medium may be a read-only memory (read-only memory, ROM) or a random access memory (random memory). access memory (RAM), CD-ROM, tapes, floppy disks and optical data storage devices, etc.

In an exemplary embodiment, the embodiment of the present application also provides a computer program product including one or more instructions, which can be executed by a processor of an electronic device to complete the method in the above embodiment.

It should be noted that when the instructions in the computer-readable storage medium or one or more instructions in the computer program product are executed by the processor of the electronic device, each process of the above method embodiment is implemented, and the same results as the above method can be achieved. To avoid repetition, the technical effects will not be repeated here.

Through the above description of the embodiments, those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above functional modules is used as an example. In actual applications, the above functions can be allocated as needed. It is completed by different functional modules, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of modules or units is only a logical function division. In actual implementation, there may be other division methods, for example, multiple units or components may be combined or can be integrated into another device, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.

A unit described as a separate component may or may not be physically separate. A component shown as a unit may be one physical unit or multiple physical units, that is, it may be located in one place, or it may be distributed to multiple different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated units can be implemented in the form of hardware or software functional units.

Integrated units may be stored in a readable storage medium if they are implemented in the form of software functional units and sold or used as independent products. Based on this understanding, the technical solutions of the embodiments of the present application are essentially or contribute to the existing technology, or all or part of the technical solution can be embodied in the form of a software product, and the software product is stored in a storage medium , including several instructions to cause a device (which can be a microcontroller, a chip, etc.) or a processor to execute all or part of the steps of the methods of various embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, ROM, RAM, magnetic disk or optical disk and other media that can store program codes.

The above are only specific implementations of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application shall be covered by the protection scope of the present application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims (12)

1. A data migration method, applied to a destination, the destination belonging to a distributed file system, the distributed file system further comprising: the system comprises a source end and a server; the distributed file system is an open source system;

the method comprises the following steps:

mounting a target storage block in the server in response to a mounting instruction; the target storage block stores target data of the source end;

and responding to a migration instruction, and migrating the data in the target storage block to the destination end.

2. The method of claim 1, wherein the target memory block comprises: a first memory block or a second memory block; the first storage block is obtained by copying the target data; the second storage block is obtained by snapshot of the first storage block.

3. The method according to claim 1 or 2, characterized in that the method further comprises:

receiving user information and authority information sent by the server;

and establishing a connection relation between the destination end and the server according to the user information and the authority information.

4. A data migration method, applied to a source, where the source belongs to a distributed file system, and the distributed file system further includes: the destination end and the server; the distributed file system is an open source system;

the method comprises the following steps:

mounting a first storage block in the server in response to a mounting instruction;

and in response to a copying instruction, copying the target data of the source end to the first storage block so that the destination end can migrate the target data to the destination end according to the first storage block.

5. The method according to claim 4, wherein the method further comprises:

receiving user information and authority information sent by the server;

and establishing a connection relation between the source end and the server according to the user information and the authority information.

6. A data migration apparatus, applied to a destination, the destination being assigned to a distributed file system, the distributed file system further comprising: the system comprises a source end and a server; the distributed file system is an open source system;

the device comprises: a mounting unit and a migration unit;

the mounting unit is used for responding to the mounting instruction and mounting the target storage block in the server; the target storage block stores target data of the source end;

and the migration unit is used for responding to a migration instruction and migrating the data in the target storage block to the destination end.

7. The apparatus of claim 6, wherein the target memory block comprises: a first memory block or a second memory block; the first storage block is obtained by copying the target data; the second storage block is obtained by snapshot of the first storage block.

8. The apparatus according to claim 6 or 7, further comprising a receiving unit and an establishing unit;

the receiving unit is used for receiving the user information and the authority information sent by the server;

the establishing unit is used for establishing the connection relation between the destination end and the server according to the user information and the authority information.

9. A data migration apparatus, applied to a source, the source being assigned to a distributed file system, the distributed file system further comprising: the destination end and the server; the distributed file system is an open source system;

the device comprises a mounting unit and a copying unit;

the mounting unit is used for responding to the mounting instruction and mounting the first storage block in the server;

the copying unit is used for responding to a copying instruction and copying the target data of the source end to the first storage block so that the destination end can migrate the target data to the destination end according to the first storage block.

10. The apparatus according to claim 9, further comprising a receiving unit and an establishing unit;

the receiving unit is used for receiving the user information and the authority information sent by the server;

the establishing unit is used for establishing the connection relation between the source end and the server according to the user information and the authority information.

11. An electronic device, comprising: a processor;

a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the method of any one of claims 1-3 or to implement the method of claim 4 or 5.

12. A computer readable storage medium, characterized in that, when computer-executable instructions stored in the computer readable storage medium are executed by a processor of an electronic device, the electronic device is capable of performing the method of any one of claims 1-3 or of performing the method of claim 4 or 5.