A hierarchical system data migration method, device, equipment and storage medium

Abstract

The application discloses a kind of hierarchical system data migration method, device, equipment and storage medium, it is applied to hierarchical system total center in the field of data migration, comprising: obtaining the cascade registration request sent by target subcenter is cascaded, and according to the data migration task of surrogate migration data is generated;Get migration task execution instruction, and the corresponding surrogate migration data and the agent information of several to-be-migrated collection agents are issued to target subcenter;Data receiving information returned by target subcenter is acquired, cascade instruction is issued to to-be-migrated collection agent to realize the cascade of to-be-migrated collection agent and target subcenter, and target information that data migration succeeds is generated, and the end of surrogate data migration task is marked according to target information.Through the data migration between nodes and node cascade, the information and the right of original node are effectively and safely migrated to new node, while the function of original node is not interrupted, new node can obtain the management right of the data and assets of original node.

Description

Technical Field

[0001] This invention relates to the field of data migration, and in particular to a method, apparatus, device and storage medium for data migration in a cascaded system. Background Technology

[0002] In actual cascading deployments, the standard deployment process of "Headquarters > Branch Centers > Data Acquisition Agents" cannot be followed entirely. Sometimes, previously deployed nodes may need to be attached to newly added nodes, or the original organizational structure may need to be altered to attach them to other nodes. In such cases, the underlying node information, asset management permissions, and security personnel data are still normally connected and communicating with the original superior node. Therefore, while maintaining normal operation, it is necessary to change the superior node being connected to, synchronize the data to the new superior node, and transfer approval and management permissions to the new superior node.

[0003] Therefore, after the lower-level system and the upper-level system complete the initial cascading, the upper-level system contains management data on assets, personnel, and other information of the units involved in the lower-level system. This data needs to be migrated to the lower-level system. Specifically, basic data is synchronized to the lower-level system, asset management permissions are transferred to the lower-level system, and the data collection capabilities of the data collection agent are migrated to the lower-level system. For example, if a new branch center node is added, the data collection agent node originally registered in the central center needs to be migrated to the new branch center node. Furthermore, related basic data, asset management permissions, and security personnel information are all handed over to the new branch center node.

[0004] Therefore, how to perform managed data migration to support unconventional cascaded deployments in actual deployments is a problem that needs to be solved in this field. Summary of the Invention

[0005] In view of this, the purpose of this invention is to provide a data migration method, apparatus, device, and storage medium for a cascaded system. Through data migration between nodes and node cascading, the information and permissions of the original node are effectively and securely migrated to a new node. While the original node's functionality remains uninterrupted, the new node can acquire management permissions for the original node's data and assets. The specific solution is as follows:

[0006] Firstly, this application provides a data migration method for a cascaded system, applied to the central hub of a cascaded system, comprising:

[0007] Obtain the cascading registration request sent by the target sub-center, cascade with the target sub-center based on the cascading registration request, and generate the managed data migration task corresponding to the target sub-center based on the managed migration data;

[0008] Obtain the migration task execution instruction sent by the root administrator based on the managed data migration task, and issue the corresponding managed migration data and the agent information of several collection agents to be migrated to the target sub-center according to the migration task execution instruction;

[0009] Obtain first data reception information returned by the target sub-center, indicating that the managed migration data and the agent information have been successfully received, and issue a corresponding cascading instruction to the acquisition agent to be migrated according to the first data reception information, so that the acquisition agent to be migrated can send a cascading request to the target sub-center according to the cascading instruction, thereby realizing the cascading of the acquisition agent to be migrated and the target sub-center, and generating corresponding target information indicating that the managed migration data has been successfully migrated.

[0010] Obtain the target information and mark the end of the managed data migration task corresponding to the target sub-center.

[0011] Optionally, obtaining the cascading registration request sent by the target sub-center, and cascading with the target sub-center based on the cascading registration request, includes:

[0012] Obtain the cascading registration request sent by the target sub-center, and approve the cascading registration request;

[0013] If the approval is granted, the cascading registration request will be cascaded with the target sub-center.

[0014] Optionally, generating the managed data migration task corresponding to the target sub-center based on the managed migration data includes:

[0015] Based on the organizational structure after the cascading of itself and the target sub-center is completed, determine whether there is any entrusted migration data that needs to be migrated to the target sub-center;

[0016] If it exists, then generate the managed data migration task corresponding to the target sub-center based on the managed migration data.

[0017] Optionally, after generating the managed data migration task corresponding to the target sub-center based on the managed migration data, the method further includes:

[0018] If a migration task termination instruction is received from the root administrator based on the managed data migration task, then the managed data migration task is terminated according to the migration task termination instruction.

[0019] Optionally, after issuing the corresponding managed migration data and the agent information of several acquisition agents to be migrated to the target sub-center according to the migration task execution instruction, the method further includes:

[0020] If the target sub-center returns second data reception information indicating that the managed migration data and the agent information failed to be received, then the step of sending the corresponding managed migration data and the agent information of several agents to be migrated to the target sub-center according to the migration task execution instruction is re-executed.

[0021] Optionally, the step of sending the corresponding cascading instruction to the acquisition agent to be migrated based on the first data reception information includes:

[0022] Based on the first data reception information, the cascading instruction corresponding to each of the several acquisition agents to be migrated is sequentially issued to the several acquisition agents to be migrated, so that the several acquisition agents to be migrated can sequentially send the cascading request to the target sub-center according to the corresponding cascading instruction.

[0023] Optionally, the step of sending the corresponding cascading instruction to the acquisition agent to be migrated based on the first data reception information includes:

[0024] The cascading instruction is generated based on the signature of the central control center, the branch center information of the target branch center, the collection agent certificate information and the gateway configuration information of the collection agent to be migrated;

[0025] According to the first data reception information, the cascading instruction is sent to the acquisition agent to be migrated, so that the acquisition agent to be migrated sends the cascading request to the target sub-center according to the cascading instruction. The target sub-center verifies whether the signature of the central center is passed according to the cascading request. After the signature of the central center is passed, the target sub-center modifies its own configuration according to the acquisition agent certificate information and the network gateway configuration information to realize the cascading of the acquisition agent to be migrated and the target sub-center.

[0026] Secondly, this application provides a cascade system data migration device, applied to the central hub of a cascade system, comprising:

[0027] The task generation module is used to obtain the cascading registration request sent by the target sub-center, cascade the cascading registration request with the target sub-center, and generate the managed data migration task corresponding to the target sub-center according to the managed migration data.

[0028] The data distribution module is used to obtain the migration task execution instruction sent by the root administrator based on the managed data migration task, and distribute the corresponding managed migration data and the agent information of several collection agents to be migrated to the target sub-center according to the migration task execution instruction.

[0029] The instruction issuing module is used to obtain the first data reception information returned by the target sub-center, which indicates that the managed migration data and the agent information have been successfully received, and to issue a corresponding cascading instruction to the acquisition agent to be migrated according to the first data reception information, so that the acquisition agent to be migrated can send a cascading request to the target sub-center according to the cascading instruction, thereby realizing the cascading of the acquisition agent to be migrated and the target sub-center, and generating corresponding target information indicating that the managed migration data has been successfully migrated;

[0030] The task marking module is used to obtain the target information and mark the end of the managed data migration task corresponding to the target sub-center.

[0031] Thirdly, this application provides an electronic device, which includes a processor and a memory; wherein the memory is used to store a computer program, which is loaded and executed by the processor to implement the aforementioned cascaded system data migration method.

[0032] Fourthly, this application provides a computer-readable storage medium for storing a computer program, which, when executed by a processor, implements the aforementioned cascaded system data migration method.

[0033] This application first obtains the cascading registration request sent by the target sub-center, cascades with the target sub-center based on the cascading registration request, and generates a managed data migration task corresponding to the target sub-center based on the managed migration data; then, it obtains the migration task execution instruction sent by the root administrator based on the managed data migration task, and sends the corresponding managed migration data and agent information of several acquisition agents to be migrated to the target sub-center according to the migration task execution instruction; after obtaining the first data reception information returned by the target sub-center indicating that the managed migration data and agent information have been successfully received, it sends the corresponding cascading instruction to the acquisition agents to be migrated according to the first data reception information, so that the acquisition agents to be migrated can send a cascading request to the target sub-center according to the cascading instruction to realize the cascading of the acquisition agents to be migrated and the target sub-center, and generate the corresponding target information indicating that the managed migration data has been successfully migrated; the managed data migration task corresponding to the target sub-center is marked as ended by obtaining the target information. This application can effectively and securely migrate the information and permissions of the original node to the new node through data migration and node cascading. While maintaining the uninterrupted function of the original node, the new node can obtain management permissions for the data and assets of the original node, providing effective support for unconventional cascading deployments in actual deployments. Attached Figure Description

[0034] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0035] Figure 1 A flowchart of a data migration method for a cascaded system is provided in this application;

[0036] Figure 2 This application provides a specific schematic diagram of the data migration logic of a cascading system.

[0037] Figure 3 A flowchart of a specific system cascading method provided in this application;

[0038] Figure 4 A schematic diagram of a data migration device for a cascaded system is provided in this application;

[0039] Figure 5 This application provides a structural diagram of an electronic device. Detailed Implementation

[0040] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0041] In actual cascading deployments, there are situations where previously deployed nodes need to be attached to newly added nodes, or where the original organizational structure needs to be changed to attach to other nodes. In these cases, the information of subordinate basic nodes, asset management permissions, and security personnel data are still normally connected and communicating with the original superior node. This necessitates changing the connected superior node while maintaining normal operation, synchronizing data to the new superior node, and transferring approval and management permissions to the new superior node. This application can effectively and securely migrate the information and permissions of the original node to the new node through data migration and node cascading, maintaining uninterrupted functionality of the original node while allowing the new node to access the original node's data and asset management permissions. This provides effective support for unconventional cascading deployments in actual deployments.

[0042] See Figure 1 As shown, this embodiment of the invention discloses a data migration method for a cascaded system, applied to the central hub of a cascaded system, comprising:

[0043] Step S11: Obtain the cascading registration request sent by the target sub-center, cascade the cascading registration request with the target sub-center, and generate the managed data migration task corresponding to the target sub-center based on the managed migration data.

[0044] In this embodiment, the cascading registration request sent by the target sub-center is first obtained. Based on the cascading registration request, a cascading connection is established with the target sub-center, and a managed data migration task corresponding to the target sub-center is generated according to the managed migration data. For example... Figure 2 As shown, after receiving the cascading registration request from the target branch center, the request needs to be approved. If the cascading system's central authority approves it, the system cascades with the target branch center based on the cascading registration request. Furthermore, before generating the managed data migration task corresponding to the target branch center based on the managed migration data, it needs to determine whether there is managed migration data to be migrated to the target branch center based on the organizational structure after the cascading with the target branch center. If so, a managed data migration task corresponding to the target branch center is generated based on the managed migration data, and the central authority's root administrator can determine whether to execute the task. If a migration task termination instruction is received from the root administrator based on the managed data migration task, the managed data migration task is terminated according to the migration task termination instruction. In this way, by checking the organizational structure tree when adding a node, generating managed data migration tasks based on whether there are any anomalies in the asset ownership logic, and having the central authority's root administrator manually review whether to execute, the system ensures task accuracy while giving users time to consider the appropriate timing for execution.

[0045] Step S12: Obtain the migration task execution instruction sent by the root administrator based on the managed data migration task, and issue the corresponding managed migration data and the agent information of several collection agents to be migrated to the target sub-center according to the migration task execution instruction.

[0046] In this embodiment, the root administrator can obtain the migration task execution instruction sent based on the managed data migration task, and issue the corresponding managed migration data and the agent information of several collection agents to be migrated to the target sub-center according to the migration task execution instruction, so as to complete the migration of cascaded system data.

[0047] Furthermore, after sending the corresponding managed migration data and the proxy information of several collection agents to be migrated to the target sub-center according to the migration task execution instruction, if the target sub-center returns second data reception information indicating that the managed migration data and proxy information failed to be received, then the above steps of sending the corresponding managed migration data and the proxy information of several collection agents to be migrated to the target sub-center according to the migration task execution instruction are re-executed.

[0048] Step S13: Obtain the first data reception information returned by the target sub-center, which indicates that the managed migration data and the agent information have been successfully received. Based on the first data reception information, issue a corresponding cascading instruction to the acquisition agent to be migrated, so that the acquisition agent to be migrated can send a cascading request to the target sub-center according to the cascading instruction, thereby realizing the cascading of the acquisition agent to be migrated and the target sub-center, and generating corresponding target information indicating that the managed migration data has been successfully migrated.

[0049] In this embodiment, as Figure 2 As shown, the system obtains first data reception information from the target branch center, indicating successful reception of the managed migration data and agent information. Based on this information, it issues a corresponding cascading instruction to the acquisition agent to be migrated. This allows the acquisition agent to send a cascading request to the target branch center, achieving cascading between the acquisition agent and the target branch center, and generating corresponding target information indicating successful migration of the managed migration data. Essentially, the node at the target branch center receives the data and reports whether reception was successful. If unsuccessful, the central center re-executes the distribution operation; if successful, the central center issues a migration instruction to the acquisition agent node to be migrated. By having the central center execute the migration task, the reliability of the certificate signed by the central center is ensured, since both the branch center and the acquisition agent are directly connected to the central center.

[0050] Step S14: Obtain the target information and mark the end of the managed data migration task corresponding to the target sub-center.

[0051] In this embodiment, the central hub of the cascaded system obtains the target information indicating the successful migration of managed data, and then marks the end of the managed data migration task corresponding to the target sub-center.

[0052] It is understood that in this embodiment, the cascading relationship is: Headquarters > Branch Centers > Collection Agents, where the Headquarters is unique, and the number of Branch Centers and Collection Agents is unlimited. Through the above technical solution, firstly, the cascading registration request sent by the target Branch Center is obtained; based on the cascading registration request, a cascading connection is established with the target Branch Center, and a managed data migration task corresponding to the target Branch Center is generated based on the managed migration data; then, the migration task execution instruction sent by the root administrator based on the managed data migration task is obtained, and the corresponding managed migration data and agent information of several collection agents to be migrated are sent to the target Branch Center according to the migration task execution instruction; after obtaining the first data reception information returned by the target Branch Center indicating successful reception of the managed migration data and agent information, the corresponding cascading instruction is sent to the collection agents to be migrated based on the first data reception information, so that the collection agents to be migrated can send a cascading request to the target Branch Center according to the cascading instruction to achieve the cascading of the collection agents to be migrated and the target Branch Center, and generate corresponding target information indicating successful migration of the managed migration data; the managed data migration task corresponding to the target Branch Center is marked as complete by obtaining the target information. This embodiment effectively and securely migrates the information and permissions of the original node to the new node through data migration and node cascading. While maintaining the uninterrupted functionality of the original node, the new node can obtain management permissions for the data and assets of the original node. This provides effective support for unconventional cascading deployments in actual deployments. Furthermore, by checking the organizational structure tree when adding a new node and generating a managed data migration task based on whether there are any anomalies in the asset ownership logic, the root administrator in the central office manually reviews whether to execute the task. This ensures the accuracy of the task while giving users time to consider the execution and ensures that the execution is carried out at the appropriate time.

[0053] As can be seen from the previous embodiment, this application can effectively and securely migrate the information and permissions of the original node to the new node through data migration between nodes and node cascading. Next, this embodiment will describe in detail the cascading process of the data acquisition agent and the sub-center after data migration. See [link to documentation]. Figure 3 As shown, this embodiment of the invention discloses a specific system cascading method, applied to the central hub of a cascading system, including:

[0054] Step S21: Obtain the first data reception information returned by the target sub-center indicating successful reception of managed migration data and proxy information.

[0055] Step S22: Generate a cascading instruction based on the central signature, the sub-center information of the target sub-center, the acquisition agent certificate information and gateway configuration information of the acquisition agent to be migrated, and issue the cascading instruction to the acquisition agent to be migrated based on the first data receiving information. After the acquisition agent to be migrated sends a cascading request to the target sub-center according to the cascading instruction, the target sub-center verifies whether the central signature is valid based on the cascading request. After the central signature verification is successful, the target sub-center modifies its own configuration based on the acquisition agent certificate information and gateway configuration information to realize the cascading of the acquisition agent to be migrated and the target sub-center, and generates corresponding target information indicating that the managed migration data has been successfully migrated.

[0056] In this embodiment, as Figure 2 As shown, the central control center can generate cascading instructions based on its signature, the target branch center's information, and the acquisition agent certificate and gateway configuration information of the acquisition agent to be migrated. It then issues these cascading instructions to the acquisition agent to be migrated based on the first data reception information. In this way, the acquisition agent to be migrated can send a cascading request to the target branch center based on the cascading instructions. The target branch center verifies the central control center's signature based on the cascading request. After successful verification, the target branch center modifies its own configuration based on the acquisition agent certificate and gateway configuration information to ensure normal communication with the acquisition agent node. This achieves the cascading of the acquisition agent to be migrated and the target branch center, and generates corresponding target information indicating successful migration of the managed data. It is understandable that if multiple acquisition agents exist, the central control center can issue cascading instructions for each acquisition agent to be migrated sequentially based on the first data reception information, allowing each acquisition agent to send a cascading request to the target branch center sequentially based on its corresponding cascading instructions.

[0057] Step S23: Obtain the target information and mark the end of the managed data migration task corresponding to the target sub-center.

[0058] Based on the above embodiments, this embodiment first initiates an initialization cascading application from a newly created branch center node, which is then reviewed and approved by the central center node. The central center then checks if any managed data needs to be migrated. If so, the central center generates a node managed data migration task. After the root administrator determines whether to execute the task, the central center sends the managed data migration information and the information of the data acquisition agent nodes to be migrated to the branch center. The branch center then reports back to the central center whether the managed data has been successfully received. Upon successful reception, the central center sends a migration instruction to the relevant data acquisition agent nodes, including the central center's signature, the data acquisition agent certificate information, and the data acquisition agent's own network gateway configuration information. The data acquisition agent node then initiates a migration cascading application to the branch center. The branch center receives the application, verifies the signature, saves the data acquisition agent certificate information, and adds network gateway configuration for this data acquisition agent. After processing, the branch center reports the migration completion to the central center. Upon confirmation by the central center, the entire process is complete.

[0059] For more detailed processing procedures regarding steps S21 and S23, please refer to the corresponding content disclosed in the foregoing embodiments, which will not be repeated here.

[0060] In this embodiment, firstly, the first data reception information returned by the target sub-center, indicating successful reception of managed migration data and agent information, is obtained. Then, a cascading instruction is generated based on the central center's signature, the target sub-center's sub-center information, and the acquisition agent certificate information and network gateway configuration information of the acquisition agent to be migrated. This cascading instruction is then sent to the acquisition agent to be migrated based on the first data reception information. After the acquisition agent to be migrated sends a cascading request to the target sub-center according to the cascading instruction, the target sub-center verifies the central center's signature based on the cascading request. If the central center's signature verification is successful, the target sub-center modifies its own configuration based on the acquisition agent certificate information and network gateway configuration information to achieve cascading between the acquisition agent to be migrated and the target sub-center, and generates corresponding target information indicating successful migration of managed migration data. The target information is then obtained, and the managed data migration task corresponding to the target sub-center is marked as complete. In this way, the migration task is performed by the central hub. Since both the branch centers and the data acquisition agents are directly connected to the central hub, the reliability of the certificates signed by the central hub is ensured. Furthermore, because the data acquisition agents are connected to the central hub normally, the network gateway configuration information issued by the central hub can be directly configured and used by the branch centers, saving the time spent on communication and debugging with the data acquisition agents. There is no need to worry about communication anomalies, and the information and permissions of the original nodes can be safely migrated to the new nodes.

[0061] See Figure 4 As shown in the illustration, this application also discloses a cascaded system data migration device, applied to the central hub of a cascaded system, comprising:

[0062] The task generation module 11 is used to obtain the cascading registration request sent by the target sub-center, cascade the cascading registration request with the target sub-center, and generate the managed data migration task corresponding to the target sub-center according to the managed migration data.

[0063] The data distribution module 12 is used to obtain the migration task execution instruction sent by the root administrator based on the managed data migration task, and distribute the corresponding managed migration data and the agent information of several collection agents to be migrated to the target sub-center according to the migration task execution instruction.

[0064] The instruction issuing module 13 is used to obtain the first data receiving information returned by the target sub-center, which indicates that the managed migration data and the agent information have been successfully received, and to issue a corresponding cascading instruction to the acquisition agent to be migrated according to the first data receiving information, so that the acquisition agent to be migrated can send a cascading request to the target sub-center according to the cascading instruction, thereby realizing the cascading of the acquisition agent to be migrated and the target sub-center, and generating corresponding target information indicating that the managed migration data has been successfully migrated;

[0065] The task marking module 14 is used to obtain the target information and mark the end of the managed data migration task corresponding to the target sub-center.

[0066] This embodiment first obtains the cascading registration request sent by the target sub-center, cascades with the target sub-center based on the cascading registration request, and generates a managed data migration task corresponding to the target sub-center according to the managed migration data; then, it obtains the migration task execution instruction sent by the root administrator based on the managed data migration task, and sends the corresponding managed migration data and agent information of several acquisition agents to be migrated to the target sub-center according to the migration task execution instruction; after obtaining the first data reception information returned by the target sub-center indicating that the managed migration data and agent information have been successfully received, it sends the corresponding cascading instruction to the acquisition agents to be migrated according to the first data reception information, so that the acquisition agents to be migrated can send a cascading request to the target sub-center according to the cascading instruction to realize the cascading of the acquisition agents to be migrated and the target sub-center, and generate the corresponding target information indicating that the managed migration data has been successfully migrated; the managed data migration task corresponding to the target sub-center is marked as ended by obtaining the target information. This application can effectively and securely migrate the information and permissions of the original node to the new node through data migration and node cascading. While maintaining the uninterrupted function of the original node, the new node can obtain management permissions for the data and assets of the original node, providing effective support for unconventional cascading deployments in actual deployments.

[0067] In some specific embodiments, the task generation module 11 specifically includes:

[0068] The request approval unit is used to obtain the cascading registration request sent by the target sub-center and to approve the cascading registration request.

[0069] The first system cascading unit is used to cascade with the target sub-center based on the cascading registration request if the approval is passed.

[0070] In some specific embodiments, the task generation module 11 specifically includes:

[0071] The data judgment unit is used to determine, based on the organizational structure after the cascading of itself and the target sub-center, whether there is any entrusted migration data that needs to be migrated to the target sub-center.

[0072] The task generation unit is used to generate a managed data migration task corresponding to the target sub-center based on the managed migration data, if such a task exists.

[0073] In some specific embodiments, the task generation module 11 further includes:

[0074] The task termination unit is used to terminate the managed data migration task based on the migration task sent by the root administrator based on the managed data migration task if it receives a migration task termination instruction from the root administrator.

[0075] In some specific embodiments, the data delivery module 12 further includes:

[0076] The data distribution unit is used to re-execute the step of distributing the corresponding managed migration data and the agent information of several collection agents to the target sub-center according to the migration task execution instruction if it receives second data reception information indicating that the managed migration data and the agent information have failed to be received.

[0077] In some specific embodiments, the instruction issuing module 13 specifically includes:

[0078] The instruction issuing unit is used to sequentially issue the cascading instruction corresponding to each of the several acquisition agents to be migrated to the several acquisition agents to be migrated according to the first data receiving information, so that the several acquisition agents to be migrated can sequentially send the cascading request to the target sub-center according to the corresponding cascading instruction.

[0079] In some specific embodiments, the instruction issuing module 13 specifically includes:

[0080] The instruction generation unit is used to generate the cascading instruction based on the signature of the central center, the branch center information of the target branch center, the collection agent certificate information and the gateway configuration information of the collection agent to be migrated;

[0081] The second system cascading unit is used to issue the cascading instruction to the acquisition agent to be migrated according to the first data receiving information, so that after the acquisition agent to be migrated sends the cascading request to the target sub-center according to the cascading instruction, the target sub-center verifies whether the signature of the central center is passed according to the cascading request, and after the signature verification of the central center is passed, it modifies its own configuration according to the acquisition agent certificate information and the network gateway configuration information to realize the cascading of the acquisition agent to be migrated and the target sub-center.

[0082] Furthermore, embodiments of this application also disclose an electronic device, Figure 5 This is a structural diagram of an electronic device 20 according to an exemplary embodiment. The content of the diagram should not be construed as limiting the scope of this application.

[0083] Figure 5 This is a schematic diagram of the structure of an electronic device 20 provided in an embodiment of this application. Specifically, the electronic device 20 may include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. The memory 22 stores a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the cascaded system data migration method disclosed in any of the foregoing embodiments. Alternatively, the electronic device 20 in this embodiment may specifically be an electronic computer.

[0084] In this embodiment, the power supply 23 is used to provide operating voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows can be any communication protocol applicable to the technical solution of this application, and is not specifically limited here; the input / output interface 25 is used to acquire external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.

[0085] In addition, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk or optical disk, etc. The resources stored thereon can include operating system 221, computer program 222, etc., and the storage method can be temporary storage or permanent storage.

[0086] The operating system 221 is used to manage and control the various hardware devices on the electronic device 20 and the computer program 222, which may be Windows Server, Netware, Unix, Linux, etc. In addition to including a computer program capable of performing the cascaded system data migration method executed by the electronic device 20 as disclosed in any of the foregoing embodiments, the computer program 222 may further include a computer program capable of performing other specific tasks.

[0087] Furthermore, this application also discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, it implements the aforementioned cascaded system data migration method. Specific steps of this method can be found in the corresponding content disclosed in the foregoing embodiments, and will not be repeated here.

[0088] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section.

[0089] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0090] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0091] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0092] The technical solutions provided in this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the methods and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A data migration method for a cascaded system, characterized in that, Applied to the central hub of cascaded systems, including: Obtain the cascading registration request sent by the target sub-center, cascade with the target sub-center based on the cascading registration request, and generate the managed data migration task corresponding to the target sub-center based on the managed migration data; Obtain the migration task execution instruction sent by the root administrator based on the managed data migration task, and issue the corresponding managed migration data and the agent information of several collection agents to be migrated to the target sub-center according to the migration task execution instruction; Obtain first data reception information returned by the target sub-center, indicating that the managed migration data and the agent information have been successfully received, and issue a corresponding cascading instruction to the acquisition agent to be migrated according to the first data reception information, so that the acquisition agent to be migrated can send a cascading request to the target sub-center according to the cascading instruction, thereby realizing the cascading of the acquisition agent to be migrated and the target sub-center, and generating corresponding target information indicating that the managed migration data has been successfully migrated. Obtain the target information and mark the end of the managed data migration task corresponding to the target sub-center; The step of generating the managed data migration task corresponding to the target sub-center based on the managed migration data includes: Based on the organizational structure after the cascading of itself and the target sub-center is completed, determine whether there is any entrusted migration data that needs to be migrated to the target sub-center; If it exists, then generate the managed data migration task corresponding to the target sub-center based on the managed migration data; Furthermore, the step of issuing corresponding cascading instructions to the acquisition agent to be migrated based on the first data reception information includes: The cascading instruction is generated based on the signature of the central control center, the branch center information of the target branch center, the collection agent certificate information and the gateway configuration information of the collection agent to be migrated; According to the first data reception information, the cascading instruction is sent to the acquisition agent to be migrated, so that the acquisition agent to be migrated sends the cascading request to the target sub-center according to the cascading instruction. The target sub-center verifies whether the signature of the central center is passed according to the cascading request. After the signature of the central center is passed, the target sub-center modifies its own configuration according to the acquisition agent certificate information and the network gateway configuration information to realize the cascading of the acquisition agent to be migrated and the target sub-center.

2. The cascading system data migration method according to claim 1, characterized in that, The step of obtaining the cascading registration request sent by the target sub-center and cascading it with the target sub-center based on the cascading registration request includes: Obtain the cascading registration request sent by the target sub-center, and approve the cascading registration request; If the approval is granted, the cascading registration request will be cascaded with the target sub-center.

3. The cascading system data migration method according to claim 1, characterized in that, After generating the managed data migration task corresponding to the target sub-center based on the managed migration data, the process further includes: If a migration task termination instruction is received from the root administrator based on the managed data migration task, then the managed data migration task is terminated according to the migration task termination instruction.

4. The cascading system data migration method according to claim 1, characterized in that, After issuing the corresponding managed migration data and agent information of several acquisition agents to be migrated to the target sub-center according to the migration task execution instruction, the process further includes: If the target sub-center returns second data reception information indicating that the managed migration data and the agent information failed to be received, then the step of sending the corresponding managed migration data and the agent information of several agents to be migrated to the target sub-center according to the migration task execution instruction is re-executed.

5. The cascading system data migration method according to claim 1, characterized in that, The step of sending the corresponding cascading instruction to the acquisition agent to be migrated based on the first data received information includes: Based on the first data reception information, the cascading instruction corresponding to each of the several acquisition agents to be migrated is sequentially issued to the several acquisition agents to be migrated, so that the several acquisition agents to be migrated can sequentially send the cascading request to the target sub-center according to the corresponding cascading instruction.

6. A data migration device for a cascaded system, characterized in that, Applied to the central hub of cascaded systems, including: The task generation module is used to obtain the cascading registration request sent by the target sub-center, cascade the cascading registration request with the target sub-center, and generate the managed data migration task corresponding to the target sub-center according to the managed migration data. The data distribution module is used to obtain the migration task execution instruction sent by the root administrator based on the managed data migration task, and distribute the corresponding managed migration data and the agent information of several collection agents to be migrated to the target sub-center according to the migration task execution instruction. The instruction issuing module is used to obtain the first data reception information returned by the target sub-center, which indicates that the managed migration data and the agent information have been successfully received, and to issue a corresponding cascading instruction to the acquisition agent to be migrated according to the first data reception information, so that the acquisition agent to be migrated can send a cascading request to the target sub-center according to the cascading instruction, thereby realizing the cascading of the acquisition agent to be migrated and the target sub-center, and generating corresponding target information indicating that the managed migration data has been successfully migrated; The task marking module is used to obtain the target information and mark the end of the managed data migration task corresponding to the target sub-center. The task generation module includes: The data judgment unit is used to determine, based on the organizational structure after the cascading of itself and the target sub-center, whether there is any entrusted migration data that needs to be migrated to the target sub-center. The task generation unit is used to generate a managed data migration task corresponding to the target sub-center based on the managed migration data, if such a task exists. Furthermore, the instruction issuing module includes: The instruction generation unit is used to generate the cascading instruction based on the signature of the central center, the branch center information of the target branch center, the collection agent certificate information and the gateway configuration information of the collection agent to be migrated; The second system cascading unit is used to issue the cascading instruction to the acquisition agent to be migrated according to the first data receiving information, so that after the acquisition agent to be migrated sends the cascading request to the target sub-center according to the cascading instruction, the target sub-center verifies whether the signature of the central center is passed according to the cascading request, and after the signature verification of the central center is passed, it modifies its own configuration according to the acquisition agent certificate information and the network gateway configuration information to realize the cascading of the acquisition agent to be migrated and the target sub-center.

7. An electronic device, characterized in that, The electronic device includes a processor and a memory; wherein the memory is used to store a computer program, which is loaded and executed by the processor to implement the cascaded system data migration method as described in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, Used to store a computer program, which, when executed by a processor, implements the cascaded system data migration method as described in any one of claims 1 to 5.

Images