CN116339815A - Upgrade plan management method, system, electronic equipment and storage medium - Google Patents
Upgrade plan management method, system, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN116339815A CN116339815A CN202310416501.7A CN202310416501A CN116339815A CN 116339815 A CN116339815 A CN 116339815A CN 202310416501 A CN202310416501 A CN 202310416501A CN 116339815 A CN116339815 A CN 116339815A
- Authority
- CN
- China
- Prior art keywords
- data
- snapshot
- upgrade
- plan management
- upgrade plan
- 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
- 238000007726 management method Methods 0.000 title claims abstract description 177
- 238000000034 method Methods 0.000 claims abstract description 52
- 238000004590 computer program Methods 0.000 claims description 16
- 238000004458 analytical method Methods 0.000 claims description 8
- 239000004973 liquid crystal related substance Substances 0.000 claims description 5
- 238000005096 rolling process Methods 0.000 claims 3
- 230000008569 process Effects 0.000 abstract description 13
- 238000010586 diagram Methods 0.000 description 13
- 238000004891 communication Methods 0.000 description 8
- 238000000605 extraction Methods 0.000 description 8
- 238000012545 processing Methods 0.000 description 7
- 238000013499 data model Methods 0.000 description 6
- 230000008859 change Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 230000004048 modification Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000001960 triggered effect Effects 0.000 description 4
- 230000005856 abnormality Effects 0.000 description 3
- 238000012217 deletion Methods 0.000 description 3
- 230000037430 deletion Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000007792 addition Methods 0.000 description 2
- 239000003086 colorant Substances 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000012216 screening Methods 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000010367 cloning Methods 0.000 description 1
- 230000000052 comparative effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 239000011521 glass Substances 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 230000014759 maintenance of location Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Quality & Reliability (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses an upgrade plan management method, an upgrade plan management system, electronic equipment and a storage medium. Wherein the method comprises the following steps: and acquiring upgrade plan management data, and backing up the upgrade plan management data to an upgrade plan database according to a preset trigger condition. According to the embodiment of the invention, the upgrade plan management data is backed up to the upgrade plan database when the trigger condition is preset, so that more upgrade plan management data can be reserved, the management problem of the upgrade plan management data in the upgrade process is solved, the management efficiency of the upgrade plan is improved, and the workload and energy of management staff are reduced.
Description
Technical Field
The present invention relates to the field of data processing technologies, and in particular, to an upgrade plan management method, an upgrade plan management system, an electronic device, and a storage medium.
Background
The operation of the information system needs to rely on the infrastructure software such as an operating system, a database, middleware and the like, and the infrastructure software needs to be correspondingly upgraded along with the updating iteration of the information system. For upgrading of the infrastructure software, the software is often limited by many factors such as software version conflict, information system operation compatibility and the like, so that the software upgrading operation needs to be carried out in batches, time periods and categories according to the actual operation condition of the information system.
In the process of managing the upgrade plans of the infrastructure software, a manager is usually required to manually record plan management data such as which plans are being implemented, which plans are about to be implemented, which plans need to be adjusted due to the influence of a front link, which plans are delayed, and the like, so that the whole process of managing the upgrade plans is very complicated, large workload and energy of the manager are required to be spent, and the efficiency of managing the upgrade plans is low.
Disclosure of Invention
The invention provides an upgrade plan management method, an upgrade plan management system, electronic equipment and a storage medium, which are used for realizing the management of upgrade plan management data in the upgrade process, improving the management efficiency of an upgrade plan and reducing the workload and energy of management staff.
According to an aspect of the present invention, there is provided an upgrade plan management method applied to an upgrade plan management system, the method including:
acquiring upgrade plan management data;
and backing up the upgrade plan management data to an upgrade plan database according to a preset trigger condition.
According to another aspect of the present invention, there is provided an upgrade plan management system, comprising:
the data acquisition module is used for acquiring upgrade plan management data;
And the data backup module is used for backing up the upgrade plan management data to the upgrade plan database according to a preset trigger condition.
According to another aspect of the present invention, there is provided an electronic apparatus including:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein, the liquid crystal display device comprises a liquid crystal display device,
the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the upgrade plan management method according to any one of the embodiments of the present invention.
According to another aspect of the present invention, there is provided a computer readable storage medium storing computer instructions for causing a processor to implement the upgrade plan management method according to any one of the embodiments of the present invention when executed.
According to the technical scheme, the upgrade plan management data are backed up to the upgrade plan database according to the preset trigger conditions by acquiring the upgrade plan management data. According to the embodiment of the invention, the upgrade plan management data is backed up to the upgrade plan database when the trigger condition is preset, so that more upgrade plan management data can be reserved, the management problem of the upgrade plan management data in the upgrade process is solved, the management efficiency of the upgrade plan is improved, and the workload and energy of management staff are reduced.
It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the invention or to delineate the scope of the invention. Other features of the present invention will become apparent from the description that follows.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of an upgrade plan management method provided according to a first embodiment of the present invention;
FIG. 2 is a flow chart of an upgrade plan management method according to a second embodiment of the present invention;
FIG. 3 is a flowchart of a method for extracting and displaying attributes based on data snapshot according to a second embodiment of the present invention;
FIG. 4 is a flowchart of a data comparison method based on data snapshot according to a second embodiment of the present invention;
fig. 5 is a flowchart of a data rollback method according to a second embodiment of the present invention;
FIG. 6 is a flowchart of another data rollback method according to a second embodiment of the present invention;
FIG. 7 is a flow chart of an upgrade plan management method provided in accordance with a third embodiment of the present invention;
FIG. 8 is an exemplary diagram of creating a snapshot of data according to a third embodiment of the present invention;
FIG. 9 is an exemplary diagram of a data snapshot attribute extraction and comparison display provided in accordance with a third embodiment of the present invention;
FIG. 10 is an exemplary diagram of a data snapshot contrast presentation provided in accordance with a third embodiment of the present invention;
fig. 11 is an exemplary diagram of a data rollback method based on a time point according to a third embodiment of the present invention;
FIG. 12 is a schematic diagram of an upgrade plan management system according to a fourth embodiment of the present invention;
fig. 13 is a schematic structural diagram of an electronic device implementing an upgrade plan management method according to an embodiment of the present invention.
Detailed Description
In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.
It should be noted that the terms "first," "second," and the like in the description and the claims of the present invention and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the invention described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Example 1
Fig. 1 is a flowchart of an upgrade plan management method according to an embodiment of the present invention, where the method may be performed by an upgrade plan management system, which may be implemented in hardware and/or software, and may be configured in an electronic device. As shown in fig. 1, the upgrade plan management method provided in the first embodiment is applied to an upgrade plan management system, and specifically includes the following steps:
S110, acquiring upgrade plan management data.
In the implementation of the present invention, the upgrade plan management data may be understood as upgrade tracking data of the infrastructure software of the target information system in the upgrade process, and the upgrade plan management data may include identification data, upgrade time data, upgrade target data, upgrade progress data, upgrade description data, and the like
Specifically, before performing an upgrade operation on the infrastructure software of the target information system, upgrade plan management data related to the infrastructure software may be obtained from a preset upgrade plan management database or an upgrade plan management file uploaded by a manager, where the upgrade plan management data may include, but is not limited to: identification data, upgrade time data, upgrade target data, upgrade progress data, upgrade specification data, and the like. The manner of acquiring upgrade plan management data may be: in the upgrade plan management database stored in the local or remote server, the upgrade plan management data related to the infrastructure software is searched from the database by using a data matching mode, wherein the data matching mode is not limited to fuzzy matching, character string matching and the like. The manner of acquiring the upgrade plan management data may also be: and extracting upgrade plan management data related to the infrastructure software according to the label or the number of the infrastructure software in the upgrade plan management file of the target information system uploaded by the manager.
And S120, backing up the upgrade plan management data to an upgrade plan database according to a preset trigger condition.
In the implementation of the present invention, the preset triggering condition may be understood as a pre-configured condition for triggering the upgrade plan management data to perform the backup operation, where the preset triggering condition may include: the method comprises the steps of reaching preset backup time, reaching upgrading progress set by a manager in a self-defining way, manually triggering by the manager and the like. An upgrade plan database may be understood as a database for storing backup data corresponding to upgrade plan management data, and may include: mySQL database, oracle database, mongoDb database, etc
Specifically, one or more preset trigger conditions may be preconfigured on the electronic device, where the preset trigger conditions may include, but are not limited to: and when the preset triggering condition triggers, the upgrade plan management data is backed up to a preset upgrade plan database. The mode of backing up the upgrade plan management data to the upgrade plan database according to the preset trigger condition may be: and when the timing trigger condition is triggered, backup is carried out on the upgrade plan management data by using a mode of creating a data snapshot, and the backup data is stored in a MySQL database. The mode of backing up the upgrade plan management data to the upgrade plan database according to the preset trigger condition may also be: when the upgrade progress set by the manager in a user-defined manner is reached, the remote mirror technology is utilized to backup upgrade plan management data, and the backup data are stored in the MongoDb database.
According to the technical scheme, the upgrade plan management data are backed up to the upgrade plan database according to the preset trigger conditions by acquiring the upgrade plan management data. According to the embodiment of the invention, the upgrade plan management data is backed up to the upgrade plan database when the trigger condition is preset, so that more upgrade plan management data can be reserved, the management problem of the upgrade plan management data in the upgrade process is solved, the management efficiency of the upgrade plan is improved, and the workload and energy of management staff are reduced.
Example two
Fig. 2 is a flowchart of an upgrade plan management method according to a second embodiment of the present invention, which is further optimized and expanded based on the foregoing embodiments, and may be combined with each of the optional technical solutions in the foregoing embodiments. As shown in fig. 2, the upgrade plan management method provided in the second embodiment specifically includes the following steps:
s210, acquiring upgrade plan management data.
S220, creating a data snapshot for the upgrade plan management data according to the designated data attribute in a preset triggering mode, wherein the preset triggering mode comprises at least one of the following steps: timing trigger, custom condition trigger, manual trigger.
In the implementation of the present invention, the preset triggering manner may be understood as a preconfigured manner for triggering the preset triggering condition, where the preset triggering manner may include at least one of the following: timing trigger, custom condition trigger, manual trigger, wherein the timing trigger can comprise 12-point trigger per day or 24-point trigger per day, etc.; the custom condition trigger can comprise time condition trigger, data update degree condition trigger and the like; the manual triggering may include: and the manager manually triggers according to the running condition of the target information system in the upgrading process, and manually triggers when the manager needs to compare the difference between the upgrading plan management data at the current moment and the historical upgrading plan management data. The data attributes may be understood as attributes contained in the upgrade plan management data, and may include at least one of the following: the system comprises a data identifier, a software identifier, a system identifier, a plan classification, an upgrade time, an upgrade target, an upgrade progress and an upgrade description, wherein the data identifier can be a unique identifier of upgrade plan management data and can be used for judging whether the upgrade plan management data in different data snapshots are the same data or not; the software identification, the system identification, may be the basic information of the upgrade plan management data, the system identification generally does not change, and the software identification may change upon completion of the upgrade plan. A data snapshot is understood as a technology of retaining a data image at a certain moment or under a certain specific condition, and the created data snapshot may be a copy of upgrade plan management data or a copy of upgrade plan management data, and the manner of the data snapshot may include cloning the snapshot, mirroring the separated snapshot, copying the snapshot when writing, redirecting the snapshot when writing, and the like.
Specifically, at least one preset trigger condition may be preconfigured on the electronic device according to a preset trigger manner, where the preset trigger manner may include at least one of the following: the method comprises the steps of timing triggering, custom condition triggering and manual triggering, and when the preset triggering condition triggering is performed, creating a corresponding data snapshot for upgrade plan management data according to specified data attributes, wherein the data attributes can comprise at least one of the following: data identification, software identification, system identification, plan classification, upgrade time, upgrade objective, upgrade progress, upgrade description, and the manner of data snapshot may include, but is not limited to, the following: clone snapshot, mirror split snapshot, copy-on-write snapshot, redirect-on-write snapshot, etc. The method for creating the data snapshot for the upgrade plan management data according to the specified data attribute in the preset triggering mode can be as follows: when the timing trigger condition is triggered, creating a corresponding data snapshot of the upgrade plan management data according to the designated data attribute by utilizing a clone snapshot mode; it may also be: when the custom trigger condition is triggered, the corresponding data snapshot is created by the upgrade plan management data according to the appointed data attribute in a mirror image snapshot separation mode.
S230, storing the data snapshot into a snapshot version library according to a snapshot version identifier, wherein the snapshot version identifier comprises at least one of the following: timestamp of data snapshot, condition information.
In the implementation of the present invention, the snapshot version library may be understood as a database for storing data snapshots corresponding to upgrade plan management data, where the snapshot version library may include: mySQL database, oracle database, mongoDb database, etc. The snapshot version identification may be understood as a unique identification corresponding to each data snapshot, and may include at least one of the following: timestamp of data snapshot, condition information.
Specifically, the corresponding data snapshot may be stored in a pre-configured snapshot version library according to a snapshot version identifier of each data snapshot, for example, a timestamp, condition information, etc. of the data snapshot, where the timestamp and condition information corresponding to each data snapshot may be used as a unique identifier of the data snapshot, so as to ensure that data of different data snapshots are not mixed and not polluted.
The manner of storing the data snapshot in the snapshot version library according to the snapshot version identifier may be: storing the corresponding data snapshot into a pre-configured snapshot version library according to the time stamp of each data snapshot. The data snapshot is stored in the snapshot version library according to the snapshot version identifier, which may also be: and storing the corresponding data snapshot into a pre-configured snapshot version library according to the time stamp and the condition information of each data snapshot.
Fig. 3 is a flowchart of a data snapshot-based attribute extraction and display method according to a second embodiment of the present invention. As shown in fig. 3, the attribute extraction and display method based on the data snapshot provided in the second embodiment specifically includes the following steps:
s310, extracting a first data snapshot and a second data snapshot from a snapshot version library according to the designated snapshot version identification.
In the implementation of the present invention, the first data snapshot and the second data snapshot may be understood as two data snapshots having different snapshot version identifications.
Specifically, the corresponding first data snapshot and second data snapshot can be extracted from the snapshot version library according to the snapshot version identifier specified by the manager. For example, if the snapshot version identifier specified by the administrator is T1 and T2, the corresponding first data snapshot K1 and the second data snapshot K2 may be found from the snapshot version library according to the snapshot version identifier.
S320, extracting and comparing the data attributes appointed in the first data snapshot and the second data snapshot, and further generating and displaying snapshot comparison data.
In the embodiment of the present invention, snapshot comparison data may be understood as data obtained by comparing data attributes specified in the first data snapshot and the second data snapshot.
Specifically, corresponding snapshot data can be extracted and compared in the first data snapshot and the second data snapshot according to one or more specified data attributes to generate corresponding snapshot comparison data, and then the snapshot comparison data is displayed. If the specified data attribute is the upgrade progress, the data about the upgrade progress in the first data snapshot and the second data snapshot are extracted and compared, so that corresponding snapshot comparison data are generated, and the snapshot comparison data are displayed in a data table form, so that management staff can know the upgrade progress of the infrastructure software in different upgrade plans in real time.
Fig. 4 is a flowchart of a data comparison method based on a data snapshot according to a second embodiment of the present invention. As shown in fig. 4, the data comparison method based on the data snapshot provided in the second embodiment specifically includes the following steps:
s410, extracting a first data snapshot and a second data snapshot from a snapshot version library according to the designated snapshot version identification.
S420, marking data of the first data snapshot and the second data snapshot according to the content difference and the total data volume difference.
In the implementation of the present invention, the content difference may be understood as a difference between the first data snapshot and the second data snapshot on the data content, and the content difference may include: the data identification of the first data snapshot and the second data snapshot, whether the data of the other data attributes are identical, and the like. The total data volume difference may be understood as a difference in total data volume between the first data snapshot and the second data snapshot, and may include newly added data, deleted data, and the like.
Specifically, it may be first determined whether the data identifiers corresponding to the first data snapshot and the second data snapshot are the same, if yes, then further determine differences between the data content and the total data size of the first data snapshot and the second data snapshot, and mark the corresponding difference data, where the marking of the difference data may include, but is not limited to: content difference data, newly added data, deleted data, and the like. In some embodiments, the data identifier may first determine whether the first data snapshot and the second data snapshot are upgrade plan management data of the same infrastructure software, if so, then compare whether the first data snapshot and the second data snapshot have differences in data attributes, and if so, mark the data as content difference data; and comparing whether the first data snapshot and the second data snapshot have differences in the total data quantity, and marking the corresponding data as newly added data or deleted data according to the newly added or deleted data quantity.
S430, generating and displaying an analysis report according to the first data snapshot and the second data snapshot after the data marking.
In the practice of the present invention, an analytical report may be understood as a report generated from difference data after marking of a first data snapshot and a second data snapshot.
Specifically, difference data on the content difference and the total data volume difference in the first data snapshot and the second data snapshot can be respectively identified in different modes, such as different colors, different textures and the like, and the identified difference data is led out to be a corresponding analysis report, so that a manager can quickly and clearly know differences among different versions of data snapshots according to the analysis report.
Fig. 5 is a flowchart of a data rollback method according to a second embodiment of the present invention. As shown in fig. 5, the data rollback method provided in the second embodiment specifically includes the following steps:
s510, when the upgrade plan management data is required to be rolled back, a corresponding first target data snapshot is extracted from a snapshot version library according to the designated snapshot version identifier.
In the implementation of the present invention, data rollback may be understood as an operation of restoring a target information system to a previous normal state when an abnormality occurs in the system. The first target data snapshot may be understood as a data snapshot corresponding to the specified snapshot version identification and used for data rollback.
Specifically, when an exception occurs in the target information system and the rollback of upgrade plan management data is required, a corresponding first target data snapshot may be extracted from the snapshot version library according to a specified snapshot version identifier, where the specified snapshot version identifier may include, but is not limited to: the snapshot version identification customized by the manager, the snapshot version identification corresponding to the latest version of the data snapshot of the target information system before the abnormality occurs, and the like.
S520, the first target data snapshot is directly covered with the upgrade plan management data at the current moment, so that the upgrade plan management data is rolled back to the first target data snapshot.
Specifically, the first target data snapshot can be directly covered on the data attribute corresponding to the upgrade plan management data at the current moment according to the data attribute, so that the upgrade plan management data is returned to the first target data snapshot, and the target information system is enabled to be in a normal state.
Fig. 6 is a flowchart of another data rollback method according to the second embodiment of the present invention. As shown in fig. 6, another data rollback method provided in the second embodiment specifically includes the following steps:
and S610, when the upgrade plan management data is required to be backed up, a second target data snapshot is extracted from the snapshot version library according to the target back-off time point, wherein the time stamp of the second target data snapshot is earlier than the target back-off time point, and the time stamp is closest to the target back-off time point compared with other data snapshots.
In the implementation of the present invention, the target backoff time point may be understood as a time point when the upgrade plan management data needs to be backoff, that is, the upgrade plan management data is backoff to the target backoff time point, so that the target information system is restored to a normal state. The second target data snapshot may be understood as a data snapshot determined according to the target backoff time point and used for data backoff.
Specifically, when an abnormality occurs in the target information system and the upgrade plan management data rollback is required, a second target data snapshot with a timestamp located before and closest to the target rollback time point may be extracted from the snapshot version library according to the target rollback time point.
S620, all user operation records between the time stamp of the second target data snapshot and the target rollback time point are acquired.
In the implementation of the present invention, the user operation record may be understood as an operation record made by an administrator for the infrastructure software, and the user operation record may include, for example, an operation record made for data addition, deletion, modification, and the like made for the infrastructure software.
Specifically, according to the timestamp of the second target data snapshot and the target rollback time point, searching all user operation records located in the snapshot version library or the preconfigured user operation record database, wherein the user operation records can include, but are not limited to, operation records such as data addition, deletion, modification and the like made for the infrastructure software.
S630, performing forward operation on the second target data snapshot by utilizing all user operation records so as to roll back the upgrade plan management data to a target roll-back time point.
In the implementation of the present invention, the forward operation may be understood as the same operation corresponding to the user operation record, and for example, if the operation in the user operation record is to modify a certain data, the forward operation corresponds to modifying the data; if the operation in the user operation record is to delete a certain data, the data is deleted corresponding to the forward operation.
Specifically, according to all user operation records between the obtained time stamp of the second target data snapshot and the target rollback time point, corresponding forward operations are sequentially executed on the second target data snapshot, and after all user operations are executed, the upgrade plan management data can be rolled back to the target rollback time point.
According to the technical scheme, the upgrade plan management data are obtained, and the data snapshot is created according to the appointed data attribute in the preset triggering mode, wherein the preset triggering mode comprises at least one of the following steps: the method comprises the steps of timing triggering, custom condition triggering and manual triggering, and storing a data snapshot into a snapshot version library according to a snapshot version identifier, wherein the snapshot version identifier comprises at least one of the following: timestamp of data snapshot, condition information. According to the embodiment of the invention, the frequency of data snapshot management can be improved by designing the preset triggering modes of various data snapshots such as timing triggering, custom condition triggering, manual triggering and the like, so that more upgrade plan management data can be reserved, the management problem of the upgrade plan management data in the upgrade process is solved, the management efficiency of an upgrade plan is improved, and the workload and energy of management staff are reduced.
Example III
Fig. 7 is a method for managing an upgrade plan according to a third embodiment of the present invention. The embodiment provides an implementation manner of an upgrade plan management method based on the embodiment, which can realize data snapshot triggering, rapid screening and comparison of data snapshots, generation of data snapshot comparison analysis reports, data rollback and other upgrade plan management works on upgrade plan management data. As shown in fig. 7, the upgrade plan management method provided in the third embodiment of the present invention specifically includes the following steps:
s710, establishing an upgrade plan management data model.
The embodiment of the invention establishes a data model applicable to all upgrade plan management data, namely, designs a set of standardized plan attributes, and the plan management data model comprises the following data attributes: the system comprises a data identifier, a software identifier, a system identifier, a plan classification, an upgrade time, an upgrade target, an upgrade progress and an upgrade description, wherein the data identifier can be a unique identifier of upgrade plan management data and can be used for judging whether the upgrade plan management data in different data snapshots are the same data or not; the software identification, the system identification, may be the basic information of the upgrade plan management data, the system identification generally does not change, and the software identification may change upon completion of the upgrade plan.
Furthermore, upgrade plan management data corresponding to the infrastructure software of the target information system can be stored in a preset database to form standardized and reusable data information.
S720, creating a data snapshot for the upgrade plan management data when a preset trigger condition is triggered.
In the embodiment of the present invention, the preset triggering modes may include the following three modes: timing trigger, custom condition trigger, manual trigger. The timing trigger is used as the most basic trigger mode of the embodiment of the invention, so that the backup data of a certain level in a certain period of the target information system can be ensured; custom conditional triggers may also include time conditional triggers, data update degree conditional triggers, and the like. Through the three preset triggering modes, the frequency of data snapshot management can be improved, so that more upgrade plan management data can be reserved. Fig. 8 is an exemplary diagram for creating a data snapshot according to a third embodiment of the present invention.
And S730, extracting and comparing the data attributes appointed in the first data snapshot and the second data snapshot, and further generating and displaying snapshot comparison data.
Fig. 9 is an exemplary diagram of data snapshot attribute extraction and comparative display according to a third embodiment of the present invention.
And S740, marking data of the first data snapshot and the second data snapshot according to the content difference and the total data volume difference, and further generating and displaying an analysis report.
In the embodiment of the invention, the data snapshot comparison can find the difference in a large amount of snapshot data of two snapshot versions, and the difference is divided into two dimensions: content variance and overall data volume variance. For content difference, firstly judging whether two data in different snapshot data are the same data according to the data identification, then comparing whether data attributes such as software identification, system identification, plan classification, upgrading time, upgrading target, upgrading progress and the like are different for the same data, and if so, marking the data as content difference data. For the overall data volume difference, the identification of the difference data is performed through the addition and deletion information of the data identification in the statistical data attribute. Finally, the identified difference data are exported to form an analysis report, and the comparison results of different dimensions can be marked and distinguished by adopting different colors. Fig. 10 is an exemplary diagram of a comparison display of a data snapshot according to a third embodiment of the present invention.
And S750, when the upgrade plan management data rollback is required, executing the data rollback operation according to a preset data rollback mode so as to restore the target information system to a normal state.
In the embodiment of the invention, the preset data rollback mode has two modes, namely rollback based on data snapshot and rollback based on time point. Wherein the rollback based on the data snapshot is achieved by directly overwriting the current data with the stored data snapshot; based on the rollback of the time point, the latest version data snapshot stored before the target rollback time point is selected to cover the current data, and then forward operation is carried out on the data through the operation record of the user between the time stamp of the data snapshot and the target rollback time point, so that the data is restored to the target rollback time point. Fig. 11 is an exemplary diagram of a data rollback method based on a time point according to a third embodiment of the present invention.
According to the technical scheme, the upgrade plan management data model is established, when the preset trigger condition triggers, the data snapshot is created for the upgrade plan management data, the data attributes appointed in the first data snapshot and the second data snapshot are extracted and compared, snapshot comparison data are further generated and displayed, and when the upgrade plan management data is required to be backed, the data backing operation is executed according to the preset data backing mode so that the target information system is restored to the normal state. According to the embodiment of the invention, the upgrade plan management data model is established, so that the data model is ensured to be applicable to all upgrade plan management data; by designing a data snapshot mechanism, a snapshot version library is established, and more upgrade plan management data can be saved; multiple data snapshot triggering and storing modes such as timing triggering, custom condition triggering and manual triggering are designed, and an automatic management function of the data snapshots is realized; the rapid screening function of the upgrade plan management data of different snapshot versions is supported, the target snapshot version can be rapidly positioned, and the appointed target attribute information is extracted; the automatic difference comparison method of different snapshot versions is designed, so that a difference comparison report of data attributes of different data snapshots can be generated, and the change condition of an upgrade plan can be rapidly mastered; the method can support the rapid recovery function of the data snapshot and realize the effective data retention and multiplexing of the upgrade plan.
Example IV
Fig. 12 is a schematic structural diagram of an upgrade plan management system according to a fourth embodiment of the present invention. As shown in fig. 12, the system includes:
the data acquisition module 41 is configured to acquire upgrade plan management data.
The data backup module 42 is configured to backup the upgrade plan management data to the upgrade plan database according to a preset trigger condition.
According to the technical scheme, the data acquisition module acquires the upgrade plan management data, and the data backup module backs up the upgrade plan management data to the upgrade plan database according to the preset trigger condition. According to the embodiment of the invention, the upgrade plan management data is backed up to the upgrade plan database when the trigger condition is preset, so that more upgrade plan management data can be reserved, the management problem of the upgrade plan management data in the upgrade process is solved, the management efficiency of the upgrade plan is improved, and the workload and energy of management staff are reduced.
Further, on the basis of the above embodiment of the present invention, the data backup module 32 includes:
the data snapshot creation unit is used for creating a data snapshot for the upgrade plan management data according to the designated data attribute in a preset triggering mode, wherein the preset triggering mode comprises at least one of the following steps: timing trigger, custom condition trigger, manual trigger.
The data snapshot storage unit is used for storing the data snapshot to the snapshot version library according to the snapshot version identification, wherein the snapshot version identification comprises at least one of the following: timestamp of data snapshot, condition information.
Further, on the basis of the above embodiment of the invention, the data attribute includes at least one of: data identification, software identification, system identification, plan classification, upgrade time, upgrade objective, upgrade progress, and upgrade description.
Further, on the basis of the above embodiment of the present invention, the data backup module 32 further includes:
and the first data snapshot extraction unit is used for extracting the first data snapshot and the second data snapshot from the snapshot version library according to the designated snapshot version identification.
And the comparison data display unit is used for extracting the data attribute appointed in the first data snapshot and the second data snapshot and comparing the data attribute, so as to generate and display snapshot comparison data.
Further, on the basis of the above embodiment of the present invention, the data backup module 32 further includes:
and the second data snapshot extraction unit is used for extracting the first data snapshot and the second data snapshot from the snapshot version library according to the designated snapshot version identification.
And the data marking unit is used for marking the data of the first data snapshot and the second data snapshot according to the content difference and the total data volume difference.
And the report display unit is used for generating and displaying an analysis report according to the first data snapshot and the second data snapshot which are marked by the data.
Further, on the basis of the above embodiment of the present invention, the data backup module 32 further includes:
and the first target data snapshot extraction unit is used for extracting the corresponding first target data snapshot from the snapshot version library according to the designated snapshot version identifier when the upgrade plan management data rollback is required.
And the first data rollback unit is used for directly covering the upgrade plan management data at the current moment by the first target data snapshot so as to rollback the upgrade plan management data to the first target data snapshot.
Further, on the basis of the above embodiment of the present invention, the data backup module 32 further includes:
and the second target data snapshot extraction unit is used for extracting a second target data snapshot from the snapshot version library according to a target rollback time point when the upgrade plan management data rollback is required, wherein the timestamp of the second target data snapshot is earlier than the target rollback time point, and the timestamp is closest to the target rollback time point compared with other data snapshots.
And the user operation record acquisition unit is used for acquiring all user operation records between the time stamp of the second target data snapshot and the target rollback time point.
And the second data rollback unit is used for executing forward operation on the second target data snapshot by utilizing all user operation records so as to rollback the upgrade plan management data to a target rollback time point.
The upgrade plan management system provided by the embodiment of the invention can execute the upgrade plan management method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.
Example five
Fig. 13 shows a schematic diagram of an electronic device 50 that may be used to implement an embodiment of the invention. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. Electronic equipment may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.
As shown in fig. 13, the electronic device 50 includes at least one processor 51, and a memory, such as a Read Only Memory (ROM) 52, a Random Access Memory (RAM) 53, etc., communicatively connected to the at least one processor 51, in which the memory stores a computer program executable by the at least one processor, and the processor 51 may perform various appropriate actions and processes according to the computer program stored in the Read Only Memory (ROM) 52 or the computer program loaded from the storage unit 58 into the Random Access Memory (RAM) 53. In the RAM 53, various programs and data required for the operation of the electronic device 50 can also be stored. The processor 51, the ROM 52 and the RAM 53 are connected to each other via a bus 54. An input/output (I/O) interface 55 is also connected to bus 54.
Various components in the electronic device 50 are connected to the I/O interface 55, including: an input unit 56 such as a keyboard, a mouse, etc.; an output unit 57 such as various types of displays, speakers, and the like; a storage unit 58 such as a magnetic disk, an optical disk, or the like; and a communication unit 59 such as a network card, modem, wireless communication transceiver, etc. The communication unit 59 allows the electronic device 50 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunications networks.
The processor 51 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 51 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, digital Signal Processors (DSPs), and any suitable processor, controller, microcontroller, etc. The processor 51 performs the various methods and processes described above, such as the upgrade plan management method.
In some embodiments, the upgrade plan management method may be implemented as a computer program tangibly embodied on a computer-readable storage medium, such as storage unit 58. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 50 via the ROM 52 and/or the communication unit 59. When the computer program is loaded into the RAM 53 and executed by the processor 51, one or more steps of the upgrade plan management method described above may be performed. Alternatively, in other embodiments, the processor 51 may be configured to perform the upgrade plan management method in any other suitable manner (e.g., by means of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.
A computer program for carrying out methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be implemented. The computer program may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) through which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.
The computing system may include clients and servers. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical hosts and VPS service are overcome.
It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps described in the present invention may be performed in parallel, sequentially, or in a different order, so long as the desired results of the technical solution of the present invention are achieved, and the present invention is not limited herein.
The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.
Claims (10)
1. An upgrade plan management method, applied to an upgrade plan management system, comprising:
acquiring upgrade plan management data;
and backing up the upgrade plan management data to an upgrade plan database according to a preset trigger condition.
2. The method of claim 1, wherein backing up the upgrade plan management data to an upgrade plan database according to a preset trigger condition comprises:
Creating a data snapshot for the upgrade plan management data according to the specified data attribute in the preset triggering mode, wherein the preset triggering mode comprises at least one of the following steps: timing trigger, custom condition trigger, manual trigger.
Storing the data snapshot to a snapshot version library according to a snapshot version identifier, wherein the snapshot version identifier comprises at least one of the following: and the time stamp of the data snapshot and the condition information.
3. The method of claim 2, wherein the data attributes comprise at least one of: data identification, software identification, system identification, plan classification, upgrade time, upgrade objective, upgrade progress, and upgrade description.
4. The method as recited in claim 2, further comprising:
extracting a first data snapshot and a second data snapshot from the snapshot version library according to the specified snapshot version identifier;
and extracting the data attributes specified by the first data snapshot and the second data snapshot, and comparing the data attributes, so as to generate and display snapshot comparison data.
5. The method as recited in claim 2, further comprising:
extracting a first data snapshot and a second data snapshot from the snapshot version library according to the specified snapshot version identifier;
Marking data of the first data snapshot and the second data snapshot according to the content difference and the total data volume difference;
and generating and displaying an analysis report according to the first data snapshot and the second data snapshot after the data marking.
6. The method as recited in claim 2, further comprising:
when the upgrade plan management data rollback is required to be carried out, extracting a corresponding first target data snapshot from the snapshot version library according to the designated snapshot version identifier;
and directly covering the upgrade plan management data at the current moment by the first target data snapshot so as to roll back the upgrade plan management data to the first target data snapshot.
7. The method as recited in claim 2, further comprising:
when the upgrade plan management data is required to be rolled back, a second target data snapshot is extracted from the snapshot version library according to a target rolling back time point, wherein the timestamp of the second target data snapshot is earlier than the target rolling back time point, and is closest to the target rolling back time point compared with other data snapshots;
acquiring all user operation records between the time stamp of the second target data snapshot and the target rollback time point;
And executing forward operation on the second target data snapshot by using the user operation records so as to roll back the upgrade plan management data to the target roll-back time point.
8. An upgrade plan management system, the system comprising:
the data acquisition module is used for acquiring upgrade plan management data;
and the data backup module is used for backing up the upgrade plan management data to an upgrade plan database according to a preset trigger condition.
9. An electronic device, the electronic device comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein, the liquid crystal display device comprises a liquid crystal display device,
the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the upgrade plan management method of any one of claims 1-7.
10. A computer readable storage medium storing computer instructions for causing a processor to implement the upgrade plan management method of any one of claims 1-7 when executed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310416501.7A CN116339815A (en) | 2023-04-18 | 2023-04-18 | Upgrade plan management method, system, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310416501.7A CN116339815A (en) | 2023-04-18 | 2023-04-18 | Upgrade plan management method, system, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116339815A true CN116339815A (en) | 2023-06-27 |
Family
ID=86889463
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310416501.7A Pending CN116339815A (en) | 2023-04-18 | 2023-04-18 | Upgrade plan management method, system, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116339815A (en) |
-
2023
- 2023-04-18 CN CN202310416501.7A patent/CN116339815A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20230012642A1 (en) | Method and device for snapshotting metadata, and storage medium | |
| CN113254267B (en) | Data backup method and device for distributed database | |
| CN113434585B (en) | Resource preservation method and equipment | |
| CN116339815A (en) | Upgrade plan management method, system, electronic equipment and storage medium | |
| CN115328736A (en) | Probe deployment method, device, equipment and storage medium | |
| US11416801B2 (en) | Analyzing value-related data to identify an error in the value-related data and/or a source of the error | |
| CN116089739A (en) | Message pushing method, device, electronic equipment and storage medium | |
| CN115640280A (en) | Data migration method and device | |
| CN115618234A (en) | Model training method, device, equipment and storage medium | |
| CN114564149A (en) | Data storage method, device, equipment and storage medium | |
| CN112860376A (en) | Snapshot chain making method and device, electronic equipment and storage medium | |
| CN113220573A (en) | Test method and device for micro-service architecture and electronic equipment | |
| CN110597669A (en) | Bank historical data parameterized backup recovery method and device | |
| CN111159237A (en) | System data distribution method and device, storage medium and electronic equipment | |
| CN113360689B (en) | Image retrieval system, method, related device and computer program product | |
| CN115794459A (en) | Flash-back processing method, device, equipment and storage medium of native application program | |
| US20240095869A1 (en) | Information acquisition method and apparatus, electronic device, and storage medium | |
| CN117251196A (en) | Data maintenance method, device, equipment and storage medium | |
| CN115421979A (en) | Log file breakpoint determination method, device, equipment and storage medium | |
| CN116644137A (en) | Database data synchronization method, device, equipment and storage medium | |
| CN117609055A (en) | Data management method, device, electronic equipment and storage medium | |
| CN117331550A (en) | Page multiplexing method and device based on form system | |
| CN118069025A (en) | Snapshot processing method, device and equipment based on storage system and storage medium | |
| CN117609209A (en) | Data recovery method, data recovery device, data recovery equipment, and storage medium | |
| CN117215838A (en) | Data processing method, device, equipment and medium of database |
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 |