CN116910034A - Data migration method, device, equipment and readable storage medium - Google Patents
Data migration method, device, equipment and readable storage medium Download PDFInfo
- Publication number
- CN116910034A CN116910034A CN202310928091.4A CN202310928091A CN116910034A CN 116910034 A CN116910034 A CN 116910034A CN 202310928091 A CN202310928091 A CN 202310928091A CN 116910034 A CN116910034 A CN 116910034A
- Authority
- CN
- China
- Prior art keywords
- data
- migration
- module
- modules
- merchant
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000013508 migration Methods 0.000 title claims abstract description 235
- 230000005012 migration Effects 0.000 title claims abstract description 235
- 238000000034 method Methods 0.000 title claims abstract description 68
- 230000008569 process Effects 0.000 claims abstract description 19
- 230000004927 fusion Effects 0.000 claims description 22
- 238000013524 data verification Methods 0.000 claims description 15
- 238000012163 sequencing technique Methods 0.000 claims description 11
- 238000004590 computer program Methods 0.000 claims description 9
- 238000010586 diagram Methods 0.000 description 8
- 101001072091 Homo sapiens ProSAAS Proteins 0.000 description 6
- 102100036366 ProSAAS Human genes 0.000 description 6
- 238000004891 communication Methods 0.000 description 4
- 230000001419 dependent effect Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000013500 data storage Methods 0.000 description 3
- 238000011022 operating instruction Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000005096 rolling process Methods 0.000 description 2
- 238000013519 translation Methods 0.000 description 2
- 238000007792 addition Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses a data migration method, a device, equipment and a readable storage medium, which are applied to the field of data migration, wherein the method comprises the following steps: acquiring and obtaining the migration sequence of each merchant in the old system according to the business volume of each merchant in the old system; migrating each merchant data in the old system to the new system according to the migration sequence; when a plurality of solutions are fused in the process that each merchant migrates from an old system to a new system, the data in the solutions are split into modules; taking the same modules in different solutions after splitting as a common module and different modules as separate modules; combining the data meeting the combining conditions in the public module to obtain combined data; the data of the individual modules, the merged data and the non-merged data in the common module are migrated from the old system to the new system. The application can reduce the data migration risk; and may also be accomplished when the data migration involves multiple solutions.
Description
Technical Field
The present application relates to the field of data migration, and in particular, to a data migration method, apparatus, device, and readable storage medium.
Background
When the system is overturned and upgraded, the old system is completely abandoned and the new system is used, at the moment, the data of the old system is required to be migrated to the new system, and the traditional data migration method is to directly migrate all the data in the old system to the new system, so that when the new system is not stable enough or the new system is in a problem, the data is disordered or even lost, and therefore, the traditional data migration method has high risk.
And, at system upgrades, cross-solution merging may also be involved, e.g., the same merchant uses both retail and mall systems before, then the new system can contain retail and mall functionality after the system upgrade is performed. At this time, the data of two systems, such as package data and user data, should be fused, and the same customer (mobile phone number is the same) should have two pieces of user data in the previous two systems, so that the migration to the new system will be fused into one piece of user data.
Thus, traditional data migration methods are at high risk and do not support cross-solution data fusion.
Disclosure of Invention
In view of the above, the present application aims to provide a data migration method, apparatus, device and readable storage medium, which solve the problems of high risk of data migration and no support of data fusion across solutions in the prior art.
In order to solve the technical problems, the present application provides a data migration method, including:
acquiring the business volume of each merchant in an old system, and sequencing each merchant from small to large according to the business volume to obtain the migration sequence of each merchant in the old system;
migrating the data of each merchant in the old system to a new system according to the migration sequence;
when fusion of a plurality of solutions exists in the process of migrating each merchant from an old system to the new system, all data in the plurality of solutions are split into modules;
taking the same modules in different solutions after splitting as a common module;
combining the data meeting the combining conditions in the public module to obtain combined data;
taking different modules in different solutions after splitting as independent modules;
and migrating the data of the individual modules, the merged data and the non-merged data in the common module from the old system to the new system.
Optionally, after the different modules in the different solutions after splitting are taken as separate modules, the method further includes:
taking the modules with mutual dependency as a module group;
accordingly, the migration of the data of the individual modules, the merged data and the non-merged data in the common module from the old system to the new system includes:
and migrating the data of the individual modules, the merged data and the non-merged data in the common module from the old system to the new system according to the dependency relationship existing in the module group.
Optionally, the migrating the data of the separate module, the merged data and the non-merged data in the common module from the old system to the new system includes:
performing full migration on the data of the independent module in the old system, the merged data and the non-merged data in the common module, and migrating to the new system; when the full migration is performed, the old system is in a normal use state;
after the full migration is completed, performing incremental migration on the data of the independent module in the old system, the merged data and the non-merged data in the public module, and migrating to the new system; when the incremental migration is performed, the new system and the old system are in a down state.
Optionally, after the migrating the data of the separate module, the merged data and the non-merged data in the common module from the old system to the new system, the method further includes:
acquiring data in the old system before migration and the new system after migration, and performing data verification;
and when the data verification fails, sending failure information to the terminal.
Optionally, after the step of sending the failure information to the terminal when the data verification fails, the method further includes:
and migrating the data which fails to migrate again.
Optionally, the migrating the data of each merchant in the old system to the new system according to the migration sequence includes:
acquiring merchant IDs of all merchants;
reading data of all merchants in the old system according to the migration sequence and the merchant ID;
and writing the data into corresponding positions in a new system sharing table according to the migration sequence and the merchant ID.
Optionally, before the acquiring the traffic of each merchant in the old system, the method further includes:
setting a login interface; the login interface is used for managing user rights;
acquiring the authority of a current login user through the login interface;
when the login user has the right of data migration, acquiring a migration task set by the login user so as to execute data migration according to the migration task; the migration tasks include migration merchants, migration solutions and migration times.
The application also provides a data migration device, which comprises:
the business volume acquisition and sequencing module is used for acquiring business volumes of all merchants in the old system, sequencing all the merchants from small to large according to the business volumes, and obtaining migration sequences of all the merchants in the old system;
the first migration module is used for migrating the data of all merchants in the old system to a new system according to the migration sequence;
the splitting module is used for splitting all data in the solutions when fusion of the solutions exists in the process that all merchants migrate from the old system to the new system;
the public module determining module is used for taking the same module in different solutions after splitting as a public module;
the data fusion module is used for merging the data meeting the merging conditions in the public module to obtain merged data;
the independent module determining module is used for taking different modules in different solutions after splitting as independent modules;
and the second migration module is used for migrating the data of the independent module, the merged data and the non-merged data in the common module from the old system to the new system.
The application also provides a data migration device, comprising:
a memory for storing a computer program;
and the processor is used for realizing the steps of the data migration method when executing the computer program.
The present application also provides a readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the data migration method described above.
Therefore, the migration sequence is ordered according to the business volume of each merchant on the system, and the merchants with small business volume are migrated, so that the risk is reduced; if the cross-solution fusion exists in the migration process of the merchant, the data of each solution is split into modules, and the data which can be combined exists in the public module are combined and then migrated, so that the system upgrade can be completed when the system upgrade involves a plurality of solutions.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present application, and that other drawings can be obtained according to the provided drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a data migration method according to an embodiment of the present application;
fig. 2 is a diagram illustrating an example of a data merging flow in a cross-solution common module according to an embodiment of the present application;
FIG. 3 is a diagram of a module dependent loop-free directed example provided by an embodiment of the present application;
FIG. 4 is a flowchart illustrating data migration according to an embodiment of the present application;
FIG. 5 is a flowchart illustrating a solution fusion according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a data migration apparatus according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of a data migration device according to an embodiment of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
Referring to fig. 1, fig. 1 is a flowchart of a data migration method according to an embodiment of the present application. The method may include:
s101: and acquiring the business volume of each merchant in the old system, and sequencing each merchant from small to large according to the business volume to obtain the migration sequence of each merchant in the old system.
The execution body of the embodiment is a terminal. The present embodiment is not limited to the type of terminal, as long as the data migration operation can be completed. For example, a general-purpose terminal; or may also be a dedicated terminal. The old system and the new system in this embodiment aim at system upgrade, that is, upgrade the old system to obtain the new system. The system in this embodiment may be based on the use of each merchant. For example, the system may be a Software-as-a-Service (SAAS system), the SAAS platform provider uniformly deploys the application Software on its own server, the customer may order the required application Software Service to the manufacturer through the internet according to the actual working requirement, pay the manufacturer for the amount and time of the ordered Service, and obtain the Service provided by the SAAS platform provider through the internet.
Further, in order to better obtain a safer upgrade experience for merchants using the system, before the service volume of each merchant in the old system is obtained, the method may further include the following steps:
step 61: setting a login interface; the login interface is used for managing user rights;
step 62: acquiring the authority of a current login user through a login interface;
step 63: when the login user has the right of data migration, acquiring a migration task set by the login user so as to execute data migration according to the migration task; the migration tasks include migration merchants, migration solutions, and migration times.
The terminal is provided with a login interface for managing the authority of a login user, the login user has the authority of data migration setting to set a migration task, and the migration task can specifically comprise a migration merchant, a migration solution and migration time. And acquiring the traffic volume of the migration merchant in the migration task, determining the migration sequence of the migration merchant according to the traffic volume, and performing data migration according to the migration sequence to complete the system upgrade of the merchant.
S102: and migrating the data of all merchants in the old system to the new system according to the migration sequence.
Sorting merchants, upgrading the merchants with small traffic on the system, upgrading the merchants with large traffic on the system, and upgrading the merchants sequentially, wherein the aim of upgrading the merchants is to reduce the upgrading risk.
S103: when fusion of multiple solutions exists in the process of migrating each merchant from an old system to a new system, all data in the multiple solutions are split into modules.
If the SAAS system is upgraded, a set of SAAS services will usually provide multiple solutions, if the SAAS system is upgraded, two solutions in the old system are fused into one solution of the new system. For example: the same merchant uses both retail and mall solutions, and then one solution for the new system after a system upgrade may be able to include both retail and mall functionality. At this time, data fusion, such as package data, user data, and two pieces of user data should be included in the previous two solutions by the same customer (mobile phone number), and then migration to a new system would fuse into one piece of user data.
One solution is made up of multiple independent modules, some of which are basic, common modules that are used by multiple solutions, and modules that are unique to some solutions. A reasonable module split may be performed prior to migration.
S104: taking the same modules in different solutions after splitting as a common module;
s105: combining the data meeting the combining conditions in the public module to obtain combined data;
s106: taking different modules in different solutions after splitting as independent modules;
steps S104 to S106 are module splitting for different solutions, and the same module in the different solutions is used as a common module, for example: the two solutions are split to form a heavy module, such as a user module and a package module, of the independent modules, and the overlapping modules are public modules. If the data meeting the data merging condition in the public module, the data can be merged; the different modules in the different solutions are taken as separate modules, i.e. modules unique to each solution. The present embodiment is not limited to the combination condition. For example: the combination of the users can use the mobile phone number or the identification card number as the combination condition. An understanding of merging data may be made with reference to fig. 2, and fig. 2 is an exemplary diagram of a data merging flow in a common module of a cross-solution according to an embodiment of the present application.
S107: the data of the individual modules, the merged data and the non-merged data in the common module are migrated from the old system to the new system.
And migrating the data in each module. Further, in view of the relevance between modules, after the above-mentioned different modules in the different solutions after splitting are used as separate modules, the method may further include the following steps, which may specifically include:
taking the modules with mutual dependency as a module group;
accordingly, step S107 may specifically include:
and migrating the data of the individual modules, the merged data and the non-merged data in the common module from the old system to the new system according to the dependency relationship existing in the module group.
Each solution is composed of a plurality of modules, the modules are mutually dependent, and the migration of the following modules can be operated only when the migration of the dependent modules is completed. The principle of dependency is data or service dependency, such as: the shopping cart module must rely on the commodity module, and the point module must rely on the membership module, i.e. the commodity module is required to migrate first and then the shopping cart module migrates; the membership module is migrated first, and the integration module is migrated again.
For example, as shown in fig. 3, fig. 3 is a diagram of a module dependent loop-free directed example provided in an embodiment of the present application.
Further, in order to reduce the influence of system upgrade on the merchant, the migration of the data of the individual modules, the merged data and the non-merged data in the common module from the old system to the new system may include the following steps:
step 31: the data of the independent modules in the old system, the combined data and the uncombined data in the public module are subjected to full migration, and the data are migrated to the new system; when the full migration is carried out, the old system is in a normal use state;
step 32: after the full migration is completed, performing incremental migration on the data of the independent modules in the old system, the merged data and the non-merged data in the common module, and migrating to the new system; when incremental migration is performed, the new system and the old system are in a down state.
Firstly, carrying out full-quantity migration on data, wherein old system merchants can normally use the full-quantity migration, after the full-quantity migration is completed, carrying out incremental migration on the data, and carrying out the migration on the incremental data generated in the full-quantity migration process, wherein when the incremental migration is carried out, the new system and the old system are in a stop state, namely cannot be used. Thus, the influence time of the merchant is only the time occupied by the migration of a small amount of incremental data.
Further, in order to ensure accuracy of data migration, after the data of the separate module, the merged data and the non-merged data in the common module are migrated from the old system to the new system, the method may further include the following steps:
acquiring data in an old system before migration and a new system after migration, and performing data verification;
and when the data verification fails, sending failure information to the terminal.
And acquiring old data before the data is migrated to the old system, acquiring new data after the data is migrated to the new system, performing data verification on the old data and the new data, and checking whether the data is migrated in a missing, lost or error mode.
Further, in order to ensure that the data migration is not missed or lost, after the failure information is sent to the terminal when the data verification fails, the method may further include the following steps:
and migrating the data which fails to migrate again.
Further, in order to ensure the regularity of data migration and save the cost of data storage, the foregoing migration of the data of each merchant in the old system to the new system according to the migration sequence may include the following steps:
acquiring merchant IDs of all merchants;
reading data of all merchants in the old system according to the migration sequence and the merchant IDs;
and writing the data into corresponding positions in the new system sharing table according to the migration sequence and the merchant ID.
In the process of data migration, data needs to be isolated, and various data isolation modes of multiple merchants exist, such as a independent database mode, b, a shared database mode, an independent table mode and c, a shared table mode. The larger the individual granularity, the higher the cost, but the higher the security, and the smaller the direct interaction of merchants. Wherein the list schema is shared, each merchant has a unique ID (identification number) by which the data is isolated.
By applying the data migration method provided by the embodiment of the application, the migration sequence of each merchant in the old system is obtained by acquiring the business volume of each merchant in the old system and sequencing each merchant from small to large according to the business volume; migrating the data of each merchant in the old system to a new system according to the migration sequence; when fusion of a plurality of solutions exists in the process of migrating each merchant from an old system to the new system, all data in the plurality of solutions are split into modules; taking the same modules in different solutions after splitting as a common module; combining the data meeting the combining conditions in the public module to obtain combined data; taking different modules in different solutions after splitting as independent modules; and migrating the data of the individual modules, the merged data and the non-merged data in the common module from the old system to the new system. According to the method, the migration sequence is ordered according to the business volume of each merchant on the system, and the merchants with small business volume are migrated, so that the risk is reduced; if the cross-solution fusion exists in the migration process of the merchant, the data of each solution is split into modules, and the data which can be combined exists in the public module are combined and then migrated, so that the system upgrade can be completed when the system upgrade involves a plurality of solutions. Moreover, the login permission of the user is obtained, and the security of data migration is ensured; in order to ensure the logic property of the modules with the dependency relationship in the migration process, a module group is set, and the modules are sequenced and migrated; moreover, the data migration is carried out in an incremental migration and full migration mode, so that the influence on merchants is reduced; and moreover, the data storage cost is saved, the data migration is avoided from being disordered, and the data is migrated to the sharing table according to the ID of the merchant.
For better understanding of the present application, please refer to fig. 4, fig. 4 is a flowchart illustrating a data migration method according to an embodiment of the present application, which may include: when a user clicks on a login interface to perform configured migration plan triggering, scheduling a first stage to start full-quantity migration, performing full-quantity rolling to pull data of an old system to perform data translation, calling a new interface or a direct connection DB to perform data migration (newly added data), and performing migration records or exception logs; when the user stops working at the second stage of the login interface motor configuration, the second stage is scheduled to start incremental migration, the incremental rolling pull is performed on the data in the old system from the end moment of the first stage to the current moment, data translation is performed, a new interface or a direct connection DB is called to perform data migration (both addition, deletion and modification can be performed), a migration record or a daily log is recorded, data verification is performed after the two stages are completed, and whether the data in the old system is consistent with the data in the new system is checked. Fig. 5 is a flowchart illustrating a solution fusion according to an embodiment of the present application. The method specifically comprises the following steps: creating migration tasks for the solution 1 and the solution 2 respectively, performing full migration on the public module and the unique module in the solution 1, judging whether the modules have data meeting the merging condition when the public module in the solution 2 performs full migration, and merging if the modules meet the merging condition, and performing full migration on the unique module in the solution 2; when the public module and the unique module in the solution 1 perform the disservice migration (incremental migration), judging whether the data meeting the merging condition exists in the modules or not when the public module in the solution 2 performs the disservice migration, merging if the data meeting the merging condition exists in the modules, and performing the disservice migration on the unique module in the solution 2; and after the migration is completed, performing migration verification.
For a better understanding, reference may be made in particular to the following examples:
the solution 1 is a enterprise micro assistant; solution 2 is a mall;
1. splitting the mall solution module: frame, promotion, merchant, coupon code, material, search platform, point balance, shopping cart, member marketing, payment finance, UC, etc.
2. Splitting enterprise micro-assistant solution modules: frame, material, weChat customer service, UC, payment finance, CDP, enterprise micro and other modules.
3. The configuration modules depend on that the first level module is a framework, the second level is UC and material, the third level is other modules, and the last level is payment finance.
4. And respectively creating migration tasks of the mall and the enterprise micro assistant solutions according to the merchant ID.
5. According to the execution sequence, the method comprises the following steps: the method comprises the steps of full-scale migration of a click mall task, full-scale migration of a click enterprise micro-assistant task, stop service migration of the click enterprise micro-assistant task, successful migration of the click mall task and data verification, successful migration of the click enterprise micro-assistant task and data verification.
6. The whole data fusion is completed.
The following describes a data migration apparatus provided in an embodiment of the present application, and the data migration apparatus described below and the data migration method described above may be referred to correspondingly.
Referring to fig. 6 specifically, fig. 6 is a schematic structural diagram of a data migration apparatus according to an embodiment of the present application, which may include:
the business volume obtaining and ordering module 100 is used for obtaining business volumes of all merchants in an old system, ordering all the merchants from small to large according to the business volumes, and obtaining migration sequences of all the merchants in the old system;
a first migration module 200, configured to migrate data of each merchant in the old system to a new system according to the migration order;
a splitting module 300, configured to split all data in a plurality of solutions when there is fusion of the solutions in the process that each merchant migrates from an old system to the new system;
a common module determining module 400, configured to take the same module in different solutions after splitting as a common module;
the data fusion module 500 is configured to combine the data meeting the combination condition in the common module to obtain combined data;
an individual module determining module 600, configured to take different modules in different solutions after splitting as individual modules;
and a second migration module 700, configured to migrate the data of the separate module, the merged data and the non-merged data in the common module from the old system to the new system.
Based on the above embodiment, the data migration apparatus may further include:
the module group module is used for taking the modules with mutual dependency relations as a module group after taking different modules in different solutions after splitting as independent modules;
the second migration module 700 is specifically configured to: and migrating the data of the individual modules, the merged data and the non-merged data in the common module from the old system to the new system according to the dependency relationship existing in the module group.
Based on the above embodiment, the second migration module 700 may include:
the full migration unit is used for performing full migration on the data of the single module in the old system, the merged data and the uncombined data in the public module, and migrating the data to the new system; when the full migration is performed, the old system is in a normal use state;
the incremental migration unit is used for performing incremental migration on the data of the independent module, the merged data and the non-merged data in the public module in the old system and migrating the data to the new system after the full migration is completed; when the incremental migration is performed, the new system and the old system are in a down state.
Based on the above embodiment, the data migration apparatus may further include:
the data checking module is used for acquiring the data in the old system before migration and the new system after migration after the data of the independent module, the merged data and the non-merged data in the public module are migrated from the old system to the new system, and performing data checking;
and the failure information sending module is used for sending the failure information to the terminal when the data verification fails.
Based on the above embodiment, the data migration apparatus may further include:
and the migration module is used for migrating the data which are failed to migrate again after the failure information is sent to the terminal when the data verification fails.
Based on the above embodiment, the first migration module 200 may include:
a merchant ID obtaining unit, configured to obtain a merchant ID of each merchant;
the data reading unit is used for reading the data of all merchants in the old system according to the migration sequence and the merchant IDs;
and the data writing unit is used for writing the data into the corresponding position in the new system sharing table according to the migration sequence and the merchant ID.
Based on the above embodiment, the data migration apparatus may further include:
the login interface setting module is used for setting a login interface before the business volume of each merchant in the old system is acquired; the login interface is used for managing user rights;
the permission acquisition module is used for acquiring the permission of the current login user through the login interface;
the execution module is used for acquiring a migration task set by the login user when the login user has the right of data migration so as to execute data migration according to the migration task; the migration tasks include migration merchants, migration solutions and migration times.
The data migration device provided by the embodiment of the application is used for acquiring the business volume of each merchant in an old system through the business volume acquisition and sequencing module 100, and sequencing each merchant from small to large according to the business volume to obtain the migration sequence of each merchant in the old system; a first migration module 200, configured to migrate data of each merchant in the old system to a new system according to the migration order; a splitting module 300, configured to split all data in a plurality of solutions when there is fusion of the solutions in the process that each merchant migrates from an old system to the new system; a common module determining module 400, configured to take the same module in different solutions after splitting as a common module; the data fusion module 500 is configured to combine the data meeting the combination condition in the common module to obtain combined data; an individual module determining module 600, configured to take different modules in different solutions after splitting as individual modules; and a second migration module 700, configured to migrate the data of the separate module, the merged data and the non-merged data in the common module from the old system to the new system. The migration sequence is ordered according to the business volume of each merchant on the system, and the merchants with small business volume are migrated, so that the risk is reduced; if the cross-solution fusion exists in the migration process of the merchant, the data of each solution is split into modules, and the data which can be combined exists in the public module are combined and then migrated, so that the system upgrade can be completed when the system upgrade involves a plurality of solutions. Moreover, the login permission of the user is obtained, and the security of data migration is ensured; in order to ensure the logic property of the modules with the dependency relationship in the migration process, a module group is set, and the modules are sequenced and migrated; moreover, the data migration is carried out in an incremental migration and full migration mode, so that the influence on merchants is reduced; and moreover, the data storage cost is saved, the data migration is avoided from being disordered, and the data is migrated to the sharing table according to the ID of the merchant.
The following describes a data migration device provided by an embodiment of the present application, where the data migration device described below and the data migration method described above may be referred to correspondingly.
Referring to fig. 7, fig. 7 is a schematic structural diagram of a data migration apparatus according to an embodiment of the present application, which may include:
a memory 10 for storing a computer program;
a processor 20 for executing a computer program to implement the data migration method described above.
The memory 10, the processor 20, and the communication interface 31 all communicate with each other via a communication bus 32.
In the embodiment of the present application, the memory 10 is used for storing one or more programs, the programs may include program codes, the program codes include computer operation instructions, and in the embodiment of the present application, the memory 10 may store programs for implementing the following functions:
acquiring the business volume of each merchant in the old system, and sequencing each merchant from small to large according to the business volume to obtain the migration sequence of each merchant in the old system;
migrating the data of all merchants in the old system to the new system according to the migration sequence;
when fusion of a plurality of solutions exists in the process that each merchant migrates from an old system to a new system, all data in the solutions are split into modules;
taking the same modules in different solutions after splitting as a common module;
combining the data meeting the combining conditions in the public module to obtain combined data;
taking different modules in different solutions after splitting as independent modules;
the data of the individual modules, the merged data and the non-merged data in the common module are migrated from the old system to the new system.
In one possible implementation, the memory 10 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, and at least one application program required for functions, etc.; the storage data area may store data created during use.
In addition, memory 10 may include read only memory and random access memory and provide instructions and data to the processor. A portion of the memory may also include NVRAM. The memory stores an operating system and operating instructions, executable modules or data structures, or a subset thereof, or an extended set thereof, where the operating instructions may include various operating instructions for performing various operations. The operating system may include various system programs for implementing various basic tasks as well as handling hardware-based tasks.
The processor 20 may be a central processing unit (Central Processing Unit, CPU), an asic, a dsp, a fpga or other programmable logic device, and the processor 20 may be a microprocessor or any conventional processor. The processor 20 may call a program stored in the memory 10.
The communication interface 31 may be an interface of a communication module for connecting with other devices or systems.
Of course, it should be noted that the structure shown in fig. 7 does not limit the data migration apparatus in the embodiment of the present application, and the data migration apparatus may include more or fewer components than those shown in fig. 7 or may combine some of the components in practical applications.
The following describes a readable storage medium provided in an embodiment of the present application, where the readable storage medium described below and the data migration method described above may be referred to correspondingly.
The present application also provides a readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the data migration method described above.
The computer readable storage medium may include: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described in a different point from other embodiments, so that the same or similar parts between the embodiments are referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant points refer to the description of the method section.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative elements and steps are described above generally in terms of functionality in order to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
Finally, it is further noted that, in this document, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
The foregoing has described in detail a data migration method, apparatus, device and readable storage medium provided by the present application, and specific examples have been applied herein to illustrate the principles and embodiments of the present application, and the above examples are only used to help understand the method and core idea of the present application; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope in accordance with the ideas of the present application, the present description should not be construed as limiting the present application in view of the above.
Claims (10)
1. A method of data migration, comprising:
acquiring the business volume of each merchant in an old system, and sequencing each merchant from small to large according to the business volume to obtain the migration sequence of each merchant in the old system;
migrating the data of each merchant in the old system to a new system according to the migration sequence;
when fusion of a plurality of solutions exists in the process of migrating each merchant from the old system to the new system, all data in the plurality of solutions are split into modules;
taking the same modules in different solutions after splitting as a common module;
combining the data meeting the combining conditions in the public module to obtain combined data;
taking different modules in different solutions after splitting as independent modules;
and migrating the data of the individual modules, the merged data and the non-merged data in the common module from the old system to the new system.
2. The data migration method of claim 1, further comprising, after said taking different modules of different solutions after splitting as separate modules:
taking the modules with mutual dependency as a module group;
accordingly, the migration of the data of the individual modules, the merged data and the non-merged data in the common module from the old system to the new system includes:
and migrating the data of the individual modules, the merged data and the non-merged data in the common module from the old system to the new system according to the dependency relationship existing in the module group.
3. The data migration method of claim 1, wherein said migrating the data of the individual modules, the merged data and the non-merged data in the common module from the old system to the new system comprises:
performing full migration on the data of the independent module in the old system, the merged data and the non-merged data in the common module, and migrating to the new system; when the full migration is performed, the old system is in a normal use state;
after the full migration is completed, performing incremental migration on the data of the independent module in the old system, the merged data and the non-merged data in the public module, and migrating to the new system; when the incremental migration is performed, the new system and the old system are in a down state.
4. The data migration method according to claim 1, further comprising, after said migrating the data of the individual module, the merged data and the non-merged data in the common module from the old system to the new system:
acquiring data in the old system before migration and the new system after migration, and performing data verification;
and when the data verification fails, sending failure information to the terminal.
5. The data migration method of claim 4, further comprising, after said sending failure information to the terminal when said data verification fails:
and migrating the data which fails to migrate again.
6. The data migration method of claim 1, wherein the migrating data of each merchant in the old system to a new system according to the migration order comprises:
acquiring merchant IDs of all merchants;
reading data of all merchants in the old system according to the migration sequence and the merchant ID;
and writing data into corresponding positions in a new system sharing table according to the migration sequence and the merchant ID.
7. The data migration method of claim 1, further comprising, prior to said acquiring traffic for each merchant in the old system:
setting a login interface; the login interface is used for managing user rights;
acquiring the authority of a current login user through the login interface;
when the login user has the right of data migration, acquiring a migration task set by the login user so as to execute data migration according to the migration task; the migration tasks include migration merchants, migration solutions and migration times.
8. A data migration apparatus, comprising:
the business volume acquisition and sequencing module is used for acquiring business volumes of all merchants in the old system, sequencing all the merchants from small to large according to the business volumes, and obtaining migration sequences of all the merchants in the old system;
the first migration module is used for migrating the data of all merchants in the old system to a new system according to the migration sequence;
the splitting module is used for splitting all data in the solutions when fusion of the solutions exists in the process that all merchants migrate from the old system to the new system;
the public module determining module is used for taking the same module in different solutions after splitting as a public module;
the data fusion module is used for merging the data meeting the merging conditions in the public module to obtain merged data;
the independent module determining module is used for taking different modules in different solutions after splitting as independent modules;
and the second migration module is used for migrating the data of the independent module, the merged data and the non-merged data in the common module from the old system to the new system.
9. A data migration apparatus, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the data migration method according to any one of claims 1 to 7 when executing the computer program.
10. A readable storage medium, characterized in that the readable storage medium has stored thereon a computer program which, when executed by a processor, implements the steps of the data migration method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310928091.4A CN116910034A (en) | 2023-07-26 | 2023-07-26 | Data migration method, device, equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310928091.4A CN116910034A (en) | 2023-07-26 | 2023-07-26 | Data migration method, device, equipment and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116910034A true CN116910034A (en) | 2023-10-20 |
Family
ID=88366567
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310928091.4A Pending CN116910034A (en) | 2023-07-26 | 2023-07-26 | Data migration method, device, equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116910034A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117494045A (en) * | 2023-11-06 | 2024-02-02 | 南京海汇装备科技有限公司 | Data integration intelligent management and control system and method based on data fusion |
-
2023
- 2023-07-26 CN CN202310928091.4A patent/CN116910034A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117494045A (en) * | 2023-11-06 | 2024-02-02 | 南京海汇装备科技有限公司 | Data integration intelligent management and control system and method based on data fusion |
| CN117494045B (en) * | 2023-11-06 | 2024-04-26 | 南京海汇装备科技有限公司 | Data integration intelligent management and control system and method based on data fusion |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| RU2488166C2 (en) | Service-oriented conveyor-based architecture | |
| JP6463393B2 (en) | Tenant data recovery across tenant migration | |
| US9904796B2 (en) | Leading system determination | |
| CA3131079A1 (en) | Test case generation method and device, computer equipment and storage medium | |
| US7895332B2 (en) | Identity migration system apparatus and method | |
| CN102135895B (en) | System upgrading method and system | |
| CN116910034A (en) | Data migration method, device, equipment and readable storage medium | |
| CN109933486B (en) | Logistics data monitoring processing method, device and system | |
| US20150012921A1 (en) | Systems, methods, and computer program products for processing sets of instructions for mobile devices | |
| CN108121774A (en) | A kind of tables of data backup method and terminal device | |
| CN106384255A (en) | Method and device for creating information code promotion information | |
| US20140244484A1 (en) | Network computing environment collection and notification of point of sale information | |
| CN111324373B (en) | Method and device for sub-coding warehouse on multiple engineering files and computing equipment | |
| CN116662351A (en) | Bank data acquisition method and system | |
| CN109246077B (en) | Distributed concurrent transaction verification method, device and computer storage medium | |
| CN110955547B (en) | Management method, system, equipment and readable storage medium for interface abnormal information | |
| CN110765144B (en) | Distributed heterogeneous database data processing method and device | |
| CN111652580B (en) | Method and device for processing data of nodes | |
| CN114281798A (en) | Data migration method and device for heterogeneous database and computer readable medium | |
| CN114328560A (en) | Lean logistics execution method, device, system and computer readable storage medium | |
| CN114063982A (en) | Method for automatically constructing functional components based on multi-scenario application | |
| CN110221952B (en) | Service data processing method and device and service data processing system | |
| CN108363614B (en) | Application service module management method and device and server | |
| CN111930363A (en) | Block interface code generation method and device | |
| CN111563183A (en) | Automatic generation method and device of visit record, computing equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |