CN112114839A - Method and system for rapid upgrade of standby environment - Google Patents

Abstract

The invention discloses a method and system for rapid upgrade of the standby environment, which can complete the upgrade of the standby system in a short time, and greatly reduces the unavailability risk of the standby system. The technical scheme is as follows: the subsystems in the main system are marked with a version label when the data upgrade is completed and the verification test can go online; the main system starts to upgrade after the reliability verification passes the backup system, and the backup system automatically judges in the process of receiving the data replication of the main system. Whether the version label is received, if the version label is received, the data replication process of the standby system receiving the master system ends. The version label is used to ensure the consistency of the active and standby environments through version information control; the standby system performs subsystem application deployment and online verification testing , reliability verification and completed through backup system upgrade.

Description

A method and system for rapid upgrade of standby environment

technical field

The present invention relates to a technology for upgrading a standby system, in particular to a method and system for rapidly upgrading a standby environment.

Background technique

Usually, a complex core business system has a large number of subsystems, and the system is upgraded frequently. Each upgrade involves the sequential upgrade of the active and standby environments. After upgrading the main system and switching back to business services, it takes a lot of time to verify the reliability and stability of the main system, and then start upgrading the standby environment after the main system is stable.

In the prior art, a database replication tool is generally used to synchronize the upgrade data of the primary system and the switchback service data within the time period used to verify the reliability of the primary system to the standby system. However, due to the huge amount of data, it takes a long time for data replication to be fully synchronized to the standby system. During this period, the standby system is in an unverified and unavailable state. During this period, if the main system encounters any serious problems and needs to switch to other environments, there will be no environment available, and the risk is extremely high. Therefore, there is currently a need in the industry for a technology that minimizes the unavailable time of the backup system.

SUMMARY OF THE INVENTION

A brief summary of one or more aspects is presented below to provide a basic understanding of the aspects. This summary is not an exhaustive overview of all contemplated aspects and is neither intended to identify key or critical elements of all aspects nor attempt to delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

The purpose of the present invention is to solve the above problems, and to provide a method and system for rapid upgrade of the standby environment, which can complete the upgrade of the standby system in a short time, and greatly reduces the unavailability risk of the standby system.

The technical scheme of the present invention is as follows: the present invention discloses a method for rapid upgrade of the standby environment, including:

The subsystems in the main system are marked with version tags when the data upgrade is completed and the verification test can be launched;

The primary system starts the upgrade after the backup system passes the reliability verification. The backup system automatically determines whether it has received the version label during the process of receiving the data copy of the primary system. If the version label is received, the backup system receives the data copy process of the primary system. It is used to ensure the consistency of the active and standby environments through version information control;

The backup system performs subsystem application deployment, online verification test, reliability verification, and is completed through the backup system upgrade.

According to an embodiment of the method for rapid upgrade of the standby environment of the present invention, during the data upgrade process of the main system, if the online verification test fails or the reliability verification test fails, the main system is rolled back and then the main system upgrade is restarted.

According to an embodiment of the method for rapid upgrade of the standby environment of the present invention, during the data upgrade process of the standby system, if the online verification test fails or the reliability verification test fails, the standby system is rolled back and the standby system upgrade is restarted.

According to an embodiment of the method for rapid upgrade of the standby environment of the present invention, each subsystem in the standby system performs parallel data replication to improve efficiency.

The invention also discloses a system for rapid upgrade of the standby environment, comprising:

The main system upgrade module, the subsystems in the main system are marked with version labels when the data upgrade is completed and the verification test can be launched;

The data replication module of the active and standby systems. The standby system starts to upgrade after the main system passes the reliability verification. The standby system automatically determines whether it has received the version label during the process of receiving the data copy of the main system. If the version label is received, the standby system receives the main system. The data replication process is completed, and the version label is used to ensure the consistency of the active and standby environments through version information control;

The backup system upgrade module, the backup system is completed after the subsystem application deployment, online verification test, reliability verification and the backup system upgrade.

According to an embodiment of the system for rapid upgrade of the standby environment of the present invention, the main system upgrade module is configured to perform a rollback of the main system if the online verification test fails or the reliability verification test fails during the data upgrade process of the main system. Restart the main system upgrade.

According to an embodiment of the system for rapid upgrade of the standby environment of the present invention, the standby system upgrade module is configured so that during the data upgrade process of the standby system, if the online verification test fails or the reliability verification test fails, the standby system is rolled back. Restart the standby system upgrade.

According to an embodiment of the system for rapid upgrade of the standby environment of the present invention, each subsystem in the standby system performs parallel data replication to improve efficiency.

The invention also discloses a system for rapid upgrade of the standby environment, the system includes:

processor; and

a memory configured to store a series of computer-executable instructions and computer-accessible data associated with the series of computer-executable instructions,

Wherein, the series of computer-executable instructions, when executed by the processor, cause the processor to perform the aforementioned method.

The present invention also discloses a non-transitory computer-readable storage medium, where a series of computer-executable instructions are stored on the non-transitory computer-readable storage medium, when the series of executable instructions are executed by a computing device , causing the computing device to perform the aforementioned method.

Compared with the prior art, the present invention has the following beneficial effects: the present invention adds a version label after the main system data upgrade is completed, and the version label is used for the subsequent judgment as to whether the process of receiving the main system data replication by the standby system is over. Through this process, the present invention can realize:

1. The present invention can quickly upgrade the backup system, greatly shorten the unavailable time of the backup system in the version process, and reduce the risk of no system being available.

2. The present invention can clearly understand the completion time of version upgrade configuration data and business operation data, so that the system upgrade process becomes controllable.

3. The present invention enables each subsystem in the entire complex system to have a definite version label, which can also be based on evidence in the future system operation, maintenance and upgrade process.

Description of drawings

The above-described features and advantages of the present invention can be better understood after reading the detailed description of the embodiments of the present disclosure in conjunction with the following drawings. In the drawings, components are not necessarily drawn to scale and components with similar related characteristics or features may have the same or similar reference numerals.

FIG. 1 shows a flow chart of an embodiment of a method for rapid upgrade of a standby environment of the present invention.

FIG. 2 shows a sequence diagram of an example of the method for rapidly upgrading the standby environment using the present invention.

FIG. 3 shows a schematic diagram of data transmission between the primary system and the backup system.

FIG. 4 shows a schematic diagram of an embodiment of the system for rapid upgrade of the standby environment of the present invention.

Detailed ways

The present invention will be described in detail below with reference to the accompanying drawings and specific embodiments. Note that the aspects described below in conjunction with the accompanying drawings and specific embodiments are only exemplary, and should not be construed as any limitation to the protection scope of the present invention.

FIG. 1 shows the flow of an embodiment of the method for rapid upgrade of the standby environment of the present invention. Referring to FIG. 1 , the following is a detailed description of each implementation step of the method of this embodiment.

Step S101: The main system starts to upgrade.

Step S102: each subsystem in the main system performs data upgrade.

Step S103: Application deployment of each subsystem in the main system.

Step S104: the main system performs an online verification test.

Step S105: Determine whether the main system can go online. If yes, go to step S106, if not, go to step S118.

Step S106: the main system is marked with a version label.

The version label is used as a condition for subsequently judging whether the process of receiving the data replication of the primary system by the standby system ends.

Step S107: Perform reliability verification on the main system.

Step S108: Determine whether it is stable. If it is stable, go to step S109, and if it is not stable, go to step S118.

Step S109: the standby system starts to upgrade.

Step S110: The backup system receives the data copy of the master system.

FIG. 3 shows an example of data replicated from the primary system to the standby system, such as data replication of the CRM/BRM/WEB/HR subsystem (including configuration data, version tags and business data).

Step S111: Determine whether a version label is received, if the version label is received, go to step S112, and if not, go to step S110.

Step S112: Application deployment of each subsystem of the standby system.

Step S113: The standby system performs an online verification test.

Step S114: Determine whether the system of the standby system can go online, if it can go online, go to step S115, and if it cannot go online, go to step S117.

Step S115: The standby system performs reliability verification.

Step S116 : Determine whether the standby system is stable, if it is stable, it means that the upgrade is completed, and the process ends, and if it is unstable, go to Step S117 .

Step S117 : the standby system is rolled back. Then step S109 is executed.

Step S118: the primary system is rolled back. Then step S101 is executed.

The active/standby system includes multiple subsystems, and the upgrade of the standby system is mainly completed by data replication generated during the upgrade process of the main system. During the data replication process of the standby system, it is difficult to clearly know the exact time when the version upgrade of each subsystem is completed. Therefore, the existing practice is to wait for the version upgrade data of all subsystems and the business data during environmental verification to be copied to the The standby environment considers that the version upgrade of all services is completed, and then the standby environment is verified. It can be seen that it is particularly critical to determine the exact upgrade completion time of each business subsystem.

The present invention takes into account that the main system will have a node after the upgrade test is completed: Go Live. As shown in Figure 2, the main system Go Live will be announced at 6:00 in the morning on November 2. Each sub-application system is marked with a label, for example, a version identification table is created in the customer relationship management system (CRM): T_CRM_VERSION, and the label data is marked in this table: 6.8, plus the timestamp of the Go Live moment. In this way, the data from 16:00 on 11/1 to 6:00 on 11/2 is the configuration data of the version upgrade.

Set a trigger on the version identification table of the standby system: T_CRM_VERSION, when the standby system receives the flag bit written by the main system (for example, the standby system starts to replicate from 22:00 on 11/4, and finds the T_CRM_VERSION table at 23:00). The tag data of 6.8 and the time stamp of the main system online have been copied over), the trigger will call the utl_file component of the database to write to an operating system local file.

The operating system will have a code that scans every 5 seconds to detect whether the file has been written. Once it is found to be written, it will send an email or short message to notify the staff that the backup system is ready for verification. During this period, no manual intervention is required, and automatic processing is realized.

As shown in Figure 2, it can be seen that the original backup system takes 29 hours from 11/4 22:00 to the completion of data replication and test verification. If the new technical solution is adopted, it only takes 1 hour to configure data replication, plus the later period It can be announced that the upgrade of the standby system is completed at 11:00 on 11/5, that is to say, the unavailability time of the upgrade stage of the standby system of the example of the present invention is only 13 hours, which saves 16 hours of unavailability compared to the original solution. use time.

FIG. 4 shows the principle of an embodiment of the system for rapid upgrade of the standby environment according to the present invention. Referring to FIG. 4 , the system of this embodiment includes: a main system upgrade module, an active and standby system data replication module, and a standby system upgrade module.

The main system upgrade module is used to label the subsystems in the main system with version labels when the data upgrade is completed and the verification test can be launched. The main system upgrade module is configured as the main system. During the data upgrade process, if the online verification test fails or the reliability verification test fails, the main system is rolled back and the main system upgrade is restarted.

The data replication module of the active and standby systems is used for the standby system to start the upgrade after the main system passes the reliability verification. The standby system determines whether it has received the version label during the process of receiving the data copy of the main system. If the version label is received, the standby system receives the main system. The data copy process ends.

The backup system upgrade module is used for the backup system to be upgraded after the subsystem application deployment, online verification test, reliability verification and backup system upgrade. The backup system upgrade module is configured as the backup system. During the data upgrade process, if the online verification test fails or the reliability verification test fails, the backup system is rolled back and the backup system upgrade is restarted.

In addition, the present invention also discloses a system for rapid upgrade of the standby environment, the system includes a processor and a memory, the memory is configured to store a series of computer-executable instructions and the computer-executable instructions associated with the series of computer-executable instructions. access data. The series of computer-executable instructions, when executed by the processor, cause the processor to perform the method performed by the embodiment shown in FIG. 1 . The specific steps of the method have been described in detail in the foregoing content, and are not repeated here.

In addition, the present invention also discloses a non-transitory computer-readable storage medium. The non-transitory computer-readable storage medium stores a series of computer-executable instructions. When the series of executable instructions is executed by a computing device, The computing device is caused to perform the method of the embodiment shown in FIG. 1 . The specific steps of the method have been described in detail in the foregoing content, and are not repeated here.

As seen from the above-described embodiments, the technical effects of the present invention include the following aspects:

1. The backup environment upgrade time is greatly shortened, reducing the risk of no environment availability after the main environment fails;

2. The backup environment is automatically upgraded by the data replication software, which reduces manpower investment and reduces the risk of upgrade failure;

3. The backup environment database automatically finds the version upgrade success sign, and promptly informs the application department to upgrade the application;

4. There is version information control to ensure that the active and standby environments are strictly consistent and will not cause business confusion in the active and standby environments;

5. Each subsystem of the backup environment can replicate data in parallel, and the upgrade efficiency is higher.

Although the above-described methods are illustrated and described as a series of acts for simplicity of explanation, it should be understood and appreciated that these methods are not limited by the order of the acts, as some acts may occur in a different order in accordance with one or more embodiments and/or occur concurrently with other actions from or not shown and described herein but understood by those skilled in the art.

Those skilled in the art will further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and design constraints imposed on the overall system. 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 invention.

The various illustrative logic blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented using general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other Programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein are implemented or performed. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration.

The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integrated into the processor. The processor and storage medium may reside in the ASIC. The ASIC may reside in the user terminal. In the alternative, the processor and storage medium may reside in the user terminal as discrete components.

In one or more exemplary embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software as a computer program product, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage medium can be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage, or other magnetic storage devices, or can be used to carry or store instructions or data structures in the form of Any other medium that conforms to program code and that can be accessed by a computer. Any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a web site, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave , then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc as used herein includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and blu-ray disc, where disks are often reproduced magnetically data, and discs reproduce the data optically with a laser. Combinations of the above should also be included within the scope of computer-readable media.

The previous description of the present disclosure is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to the present disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of the present disclosure. Thus, the present disclosure is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (10)

1. a method for rapid upgrade of a standby environment, characterized in that, comprising: The subsystems in the main system are marked with version tags when the data upgrade is completed and the verification test can be launched; The primary system starts the upgrade after the backup system passes the reliability verification. The backup system automatically determines whether it has received the version label during the process of receiving the data copy of the primary system. If the version label is received, the backup system receives the data copy process of the primary system. It is used to ensure the consistency of the active and standby environments through version information control; The backup system performs subsystem application deployment, online verification test, reliability verification, and is completed through the backup system upgrade. 2. The method for rapid upgrade of a standby environment according to claim 1, wherein in the data upgrade process of the main system, if the online verification test fails or the reliability verification test fails, the main system is rolled back and restarted Main system upgrade. 3. The method for rapid upgrade of the standby environment according to claim 1, wherein, in the data upgrade process of the standby system, if the online verification test fails or the reliability verification test fails, the standby system is rolled back and restarted Backup system upgrade. 4 . The method for rapid upgrade of a standby environment according to claim 1 , wherein each subsystem in the standby system performs parallel data replication to improve efficiency. 5 . 5. A system for rapid upgrade of standby environment, characterized in that, comprising: The main system upgrade module, the subsystems in the main system are marked with version labels when the data upgrade is completed and the verification test can be launched; The data replication module of the active and standby systems. The standby system starts to upgrade after the main system passes the reliability verification. The standby system automatically determines whether it has received the version label during the process of receiving the data copy of the main system. If the version label is received, the standby system receives the main system. The data replication process is completed, and the version label is used to ensure the consistency of the active and standby environments through version information control; The backup system upgrade module, the backup system is completed after the subsystem application deployment, online verification test, reliability verification and the backup system upgrade. 6. The system for rapid upgrade of the standby environment according to claim 5, wherein the main system upgrade module is configured to be the main system in the data upgrade process, if the online verification test fails or the reliability verification test fails, then carry out Restart the primary system upgrade after the primary system is rolled back. 7. The system for rapid upgrade of standby environment according to claim 5, it is characterized in that, standby system upgrade module is configured to standby system in data upgrade process, if on-line verification test fails or reliability verification test fails, then carry out After the backup system is rolled back, restart the backup system upgrade. 8 . The system for rapid upgrade of the standby environment according to claim 5 , wherein each subsystem in the standby system performs parallel data replication to improve efficiency. 9 . 9. A system for rapid upgrade of a standby environment, characterized in that the system comprises: processor; and a memory configured to store a series of computer-executable instructions and computer-accessible data associated with the series of computer-executable instructions, wherein the series of computer-executable instructions, when executed by the processor, cause the processor to perform the method of any one of claims 1-4. 10. A non-transitory computer-readable storage medium, wherein a series of computer-executable instructions are stored on the non-transitory computer-readable storage medium, and when the series of executable instructions are executed by a computing device , causing the computing device to perform the method of any one of claims 1-4.

Images