CN105117263A - UNIX environment software system upgrading method - Google Patents
UNIX environment software system upgrading method Download PDFInfo
- Publication number
- CN105117263A CN105117263A CN201510583927.7A CN201510583927A CN105117263A CN 105117263 A CN105117263 A CN 105117263A CN 201510583927 A CN201510583927 A CN 201510583927A CN 105117263 A CN105117263 A CN 105117263A
- Authority
- CN
- China
- Prior art keywords
- aku
- application server
- deployment
- installation
- complete
- 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.)
- Granted
Links
Landscapes
- Stored Programmes (AREA)
Abstract
The invention provides a UNIX environment software system upgrading method. The method comprises the steps that 1, a directory structure is built for upgrade packages in advance; 2, the upgrade packages are installed and deployed; 3, rule mapping tables are built according to the configuration variances between application servers, and the rule mapping tables are stored into all the application servers in advance; 4, the upgrade packages which are installed successfully are applied to other application servers by synthesizing the rule mapping tables; 5, self-adaptive upgrade package installation and deploying are completed for all the application servers. According to the UNIX environment software system upgrading method, formal environment patches are automatically generated, the patch content is not manually changed, and patch accuracy and consistency are ensured.
Description
Technical field
The invention belongs to field of computer technology, particularly relate to a kind of unix environment software system updating method.
Background technology
In enterprise, many important software systems (as large-scale PDM system) are deployed in the class Unix operating system environment such as unix system or Linux of stable performance usually.As shown in Figure 1, system manager individual operating terminal generally and between application system server has fire wall to isolate, keeper is connected to machine (being generally Windows operating system) in the middle of the management of server area at individual operating terminal by corresponding port or software, and then connects with application system server and carry out bookkeeping.
The carrying out of application system upgrade activities is subject to the restriction of upgrade environments, after application system keeper obtains upgrade patch bag, by operating terminal completion system upgrading in accordance with the following steps:
1. by upgrade patch bag import operation terminating machine;
2. pass fire wall through certification, connect with machine in the middle of management;
3. upgrade patch is wrapped and reach machine in the middle of management;
4. use ssh client instrument, the application system server being UNIX (or other class unix system) with host operating system connects, and is uploaded by service packs;
5. the upgrading provided according to exploitation side illustrates, by ssh client input command one by one, comprises and stops application system service, disposes file in service packs one by one, backs up the file that is replaced and restart application system service etc. by hand.
In view of the requirement of general enterprises internal security administrative provisions and the deployment feature of application system itself, current upgrading flow process compares science and relative solidification, but there is following latent defect:
1. the patch that provides of exploitation side is correct, if but patch deployment illustrate in upgrade step have a place wrong, then may cause upgrading unsuccessfully;
2. application system managerial personnel directly sign in application server and operate, and there is possibility of the maloperation carried out beyond normal upgrade command, perhaps can because of the unpredictable problem of introducing of once upgrading;
3. the service packs that different service packs provides personnel to provide there are differences in form, and application management personnel also there are differences the mode that AKU is safeguarded, these all can cause the non-standard phenomena of escalation process;
4., when once upgrading relates to the renewal of hundreds of file needs or adds, process is quite loaded down with trivial details and easily make mistakes;
5. upgrade patch first in test environment deploy, test by rear, may also need manual modification partial file content, again obtain the service packs being applicable to formal production environment, the correctness of change ensures by artificial;
If 6. need rollback after upgrading, if particularly need the state before rolling back to several times upgrading, will be disaster for enforcement personnel.
Huawei Tech Co., Ltd patent CN102193805A discloses a kind of software patch upgrading method, and the method can generate stand-by program automatically, according to service packs auto-update, and can rollback automatically when this is upgraded unsuccessfully.But mainly there is following problem in the method:
For " self-explanatory ": under traditional approach, exploitation side provides AKU and updating operation explanation, file in AKU sane level can place (only otherwise bear the same name), and updating operation can tell in illustrating how operation enforcement personnel dispose the file in AKU one by one.There is following latent defect in this: one is if the AKU that provides of exploitation side is correct, if but patch deployment illustrate in upgrade step have a place wrong, then may cause upgrading unsuccessfully; Two is that enforcement personnel directly log on application server and operate, and there is possibility of the maloperation carried out beyond normal upgrade command, perhaps can because of the unpredictable problem of introducing of once upgrading; Three is that process is quite loaded down with trivial details, consuming time and easily make mistakes if relate to hundreds of file needs when once upgrading when upgrading or add.
Automatically generate for patch: under traditional approach, if an application system deploys many covers on a different server, application system so for different instances will provide different AKU files, in other words a certain station server deploy test the AKU passed through to be deployed on another station server time, need to revise partial file content by hand, such as test macro and formal system, AKU is first in test macro deploy, test is by rear, may also need manual modification partial file content, again the AKU being applicable to formal production environment is obtained, the correctness of change ensures by artificial.
For rollback as required: after upgrading, if need rollback, if particularly need the state before rolling back to several times upgrading, will be disaster for enforcement personnel.Huawei Tech Co., Ltd patent CN102193805A discloses a kind of software patch upgrading method, and the method can generate stand-by program automatically, according to service packs auto-update, and can rollback automatically when this is upgraded unsuccessfully.But the method is only supported when the secondary rollback unsuccessfully of upgrading, do not support when needing to carry out rollback due to other after secondary upgrading successfully, or by the demand of whole for updating operation before several times rollback.
Summary of the invention
For solving the problem, the invention provides a kind of unix environment software system updating method, formal environments patch generates automatically, does not have manual change patch content, and correctness, the consistance of patch are protected.
Unix environment software system updating method of the present invention, it comprises the following steps:
Step 1, the AKU used for this unix environment software system updating sets up bibliographic structure in advance, and this service packs bibliographic structure comprises all upgrade files, the routing information that described upgrade file designs according to target placement location;
Step 2, the installation and deployment of AKU:
AKU is passed on application server by terminal, application server carries out decompress(ion) to this AKU, and the upgrade file traveled through in AKU, according to routing information, corresponding upgrade file is transferred to target placement location, then judge: if target placement location exists the upgrade file of transmission, then first the original on target placement location is transferred to backup library to back up in the mode backing up file, then the original on target placement location is replaced with the upgrade file of transmission; If target placement location does not exist the upgrade file of transmission, be then directly positioned over target location;
Installation and deployment are complete, the backup file folder that in backup library, foundation is once upgraded simultaneously and the timestamp recording once this upgrading in daily record, the original of replacing before comprising this upgrading in this backup file folder, backup file folder is with the name of this update time stamp simultaneously;
Step 3, sets up regular mapping table according to configuration variance between any two in all application servers, then prestores in all application servers by this regular mapping table;
If to be the AKU installation and deployment after step 2 complete and test successful application server through functional performance for application server A, and by complete for installation and deployment on application server A and test successful AKU and directly transfer on the complete application server B of the non-installation and deployment of AKU, this application server B receives described AKU and travels through the rule in its regular mapping table stored, and test successful AKU file content according to the mapping ruler auto modification of wherein application server A and application server B, obtain the self-adaptation AKU being applicable to application server B, application server B completes the installation and deployment of self-adaptation AKU according to the mode of step 2,
Step 4, installation and deployment are complete and to test successful application server through functional performance complete and test the mode of successful application server according to step 3 through functional performance to non-installation and deployment, complete non-installation and deployment complete and test the installation and deployment of successful application server self-adaptation AKU through functional performance, until all application servers complete the installation and deployment of self-adaptation AKU.
Further, after above-mentioned application server installation and deployment, break down in use procedure, then read the daily record in backup library, obtain the timestamp list of all history upgrading, need the update time of rollback to stab according in the list of fault location time stamp, stab AKU all so far according to the reverse rollback of the time sequencing of timestamp from this update time.
Further, the content of rollback comprises:
The backup file folder of this rollback in traversal backup library, transfers to original position by each backup file, and replaces the upgrade file on original position.
Beneficial effect:
The present invention, by reqirement of compilation to patch file hierarchical directory, makes patch file can " self-explanatory " position that should place, saves patch file placement explanation.Formal environments patch of the present invention generates automatically: the patch of formal production environment is tested the patch passed through and obtained through the verify check according to rule list from test environment, do not have manual change patch content, correctness, the consistance of patch are protected.
Patch of the present invention rollback as required in addition.The method devises complete daily record and patch storage structure, and keeper can a key quick rollback several times patch as required, makes System recover to the state needed.
Accompanying drawing explanation
Fig. 1 is the unix environment software system updating method schematic diagram of prior art;
Fig. 2 is unix environment software system updating method process flow diagram of the present invention.
Embodiment
Technical scheme of the present invention is as follows:
A kind of unix environment software system updating method, it comprises the following steps:
Step 1, the AKU used for this unix environment software system updating sets up bibliographic structure in advance, and this service packs bibliographic structure comprises all upgrade files, the routing information that described upgrade file designs according to target placement location.
Step 2, the installation and deployment of AKU:
AKU is passed on application server by terminal, application server carries out decompress(ion) to this AKU, and the upgrade file traveled through in AKU, according to routing information, corresponding upgrade file is transferred to target placement location, then judge: if target placement location exists the upgrade file of transmission, then first the original on target placement location is transferred to backup library to back up in the mode backing up file, then the original on target placement location is replaced with the upgrade file of transmission; If target placement location does not exist the upgrade file of transmission, be then directly positioned over target location.
In service packs installation process, do not need extra patch description document to illustrate and go to replace certain file B with certain file A, but have employed the characteristic based on service packs bibliographic structure " self-explanatory ", complete backup and the Auto-mounting of patch file.
Installation and deployment are complete, the backup file folder that in backup library, foundation is once upgraded simultaneously and the timestamp recording once this upgrading in daily record, the original of replacing before comprising this upgrading in this backup file folder, backup file folder is with the name of this update time stamp simultaneously.
Step 3, sets up regular mapping table according to configuration variance between any two in all application servers, then prestores in all application servers by this regular mapping table;
If to be the AKU installation and deployment after step 2 complete and test successful application server through functional performance for application server A, and by complete for installation and deployment on application server A and test successful AKU and directly transfer on the complete application server B of the non-installation and deployment of AKU, this application server B receives described AKU and travels through the rule in its regular mapping table stored, and test successful AKU file content according to the mapping ruler auto modification of wherein application server A and application server B, obtain the self-adaptation AKU being applicable to application server B, application server B completes the installation and deployment of self-adaptation AKU according to the mode of step 2,
Such as: configuration variance comprises IP address, domain name and system identifier etc., the listed files that may occur these configuration variance items is set up when setting up regular mapping table, as files such as * .property, * .xml, * .conf.If application server A installation and deployment are complete and test successfully through functional performance, successful for test AKU is directly transferred on application server B, this application server B receives the successful AKU of test, decompress(ion) AKU, then the updatingfile list that may need to replace content is filtered out according to file suffixes, then file carries out full text replacement according to personalized difference configuration item one by one, and auto modification obtains the self-adaptation AKU being applicable to application server B.
Step 4, installation and deployment are complete and to test successful application server through functional performance complete and test the mode of successful application server according to step 3 through functional performance to non-installation and deployment, complete non-installation and deployment complete and test the installation and deployment of successful application server self-adaptation AKU through functional performance, until all application servers complete the installation and deployment of self-adaptation AKU.
Because each upgrade activities is wanted first to carry out on application system testing server, pass through after checking until patch, just can apply it on formal server, and in order to ensure the consistance of the patch release be deployed in test macro and formal system, do not wish in real process separately to go out a patch again for formal server.For this reason, this programme is set up and is safeguarded a rule list, it is described that when comprising which file in service packs, needs to make which kind of amendment wherein for different servers.Like this, when service packs test on an application server by after, current server can according to this rule description table, given content in automatic replacement associated documents, can this service packs be directly deployed on other application servers, namely achieving the patch content verify check of rule-based table, avoiding the service packs problem of inconsistency because causing after secondary introducing service packs.
After above-mentioned application server installation and deployment, break down in use procedure, then read the daily record in backup library, obtain the timestamp list of all history upgrading, need the update time of rollback to stab according in the list of fault location time stamp, stab AKU all so far according to the reverse rollback of the time sequencing of timestamp from this update time.In the backup library traveling through this rollback, backup file folder, transfers to original position by each backup file, and replaces the upgrade file on original position.
In real work, may need to carry out rollback to the several times patch disposed before due to a variety of causes, this programme safeguards a daily record storehouse specially, each updating operation all can produce one independently formatted log file stored in daily record storehouse, when need to make application system return to before state sometime time, can according to the daily record storehouse of format by after specifying the moment the whole rollback of service packs of beating; In addition, when system go wrong needs make assessment time, complete log content also can provide objective basis for related personnel.
Said method takes into account the feature of system upgrade, backup and reduction, simplifies conventional updating operation, improves upgrading efficiency, and average update time is than saving more than 80% in the past, and updating operation accuracy can reach 100%; Have cured upgrading flow process, make the convenient management of escalation process; Perfect upgrading log recording, after being easy to make mistakes, system state is recovered.
Software system updating method under unix environment of the present invention can utilize shell script on application system server, realize the Core Feature of escalation process; Intermediate management machine utilizes DOS batch processing script carries out user authentication by SSH agreement, long-range shell script calls and uploaded by SCP protocol realization service packs.The DOS batch processing script that update device is used is deployed on the intermediate management machine that operating system environment is WindowsServer, it is in the application system server of UNIX that shell script then resides in operating system environment, wherein, DOS batch processing script and shell script complete the core business logic of upgrade method jointly.
Certainly; the present invention also can have other various embodiments; when not deviating from the present invention's spirit and essence thereof; those of ordinary skill in the art are when making various corresponding change and distortion according to the present invention, but these change accordingly and are out of shape the protection domain that all should belong to the claim appended by the present invention.
Claims (3)
1. a unix environment software system updating method, is characterized in that, comprises the following steps:
Step 1, the AKU used for this unix environment software system updating sets up bibliographic structure in advance, and this service packs bibliographic structure comprises all upgrade files, the routing information that described upgrade file designs according to target placement location;
Step 2, the installation and deployment of AKU:
AKU is passed on application server by terminal, application server carries out decompress(ion) to this AKU, and the upgrade file traveled through in AKU, according to routing information, corresponding upgrade file is transferred to target placement location, then judge: if target placement location exists the upgrade file of transmission, then first the original on target placement location is transferred to backup library to back up in the mode backing up file, then the original on target placement location is replaced with the upgrade file of transmission; If target placement location does not exist the upgrade file of transmission, be then directly positioned over target location;
Installation and deployment are complete, the backup file folder that in backup library, foundation is once upgraded simultaneously and the timestamp recording once this upgrading in daily record, the original of replacing before comprising this upgrading in this backup file folder, backup file folder is with the name of this update time stamp simultaneously;
Step 3, sets up regular mapping table according to configuration variance between any two in all application servers, then prestores in all application servers by this regular mapping table;
If to be the AKU installation and deployment after step 2 complete and test successful application server through functional performance for application server A, and by complete for installation and deployment on application server A and test successful AKU and directly transfer on the complete application server B of the non-installation and deployment of AKU, this application server B receives described AKU and travels through the rule in its regular mapping table stored, and test successful AKU file content according to the mapping ruler auto modification of wherein application server A and application server B, obtain the self-adaptation AKU being applicable to application server B, application server B completes the installation and deployment of self-adaptation AKU according to the mode of step 2,
Step 4, installation and deployment are complete and to test successful application server through functional performance complete and test the mode of successful application server according to step 3 through functional performance to non-installation and deployment, complete non-installation and deployment complete and test the installation and deployment of successful application server self-adaptation AKU through functional performance, until all application servers complete the installation and deployment of self-adaptation AKU.
2. unix environment software system updating method as claimed in claim 1, it is characterized in that, after above-mentioned application server installation and deployment, break down in use procedure, then read the daily record in backup library, obtain the timestamp list of all history upgrading, need the update time of rollback to stab according in the list of fault location time stamp, stab AKU all so far according to the reverse rollback of the time sequencing of timestamp from this update time.
3. unix environment software system updating method as claimed in claim 2, it is characterized in that, the content of rollback comprises:
The backup file folder of this rollback in traversal backup library, transfers to original position by each backup file, and replaces the upgrade file on original position.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510583927.7A CN105117263B (en) | 2015-09-14 | 2015-09-14 | A kind of unix environment software system updating method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510583927.7A CN105117263B (en) | 2015-09-14 | 2015-09-14 | A kind of unix environment software system updating method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105117263A true CN105117263A (en) | 2015-12-02 |
| CN105117263B CN105117263B (en) | 2018-06-22 |
Family
ID=54665264
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510583927.7A Active CN105117263B (en) | 2015-09-14 | 2015-09-14 | A kind of unix environment software system updating method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105117263B (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106941420A (en) * | 2017-03-16 | 2017-07-11 | 北京深思数盾科技股份有限公司 | A kind of cluster application environment upgrade method and device |
| CN107273139A (en) * | 2017-07-05 | 2017-10-20 | 努比亚技术有限公司 | A kind of method for updating system, equipment and computer-readable recording medium |
| CN107402780A (en) * | 2017-05-15 | 2017-11-28 | 梁亚柳 | Semi-automatic more new version software instrument |
| CN107844314A (en) * | 2017-12-22 | 2018-03-27 | 税友软件集团股份有限公司 | A kind of method and system of upgrading Weblogic application programs |
| CN108664255A (en) * | 2017-03-27 | 2018-10-16 | 中兴通讯股份有限公司 | A kind of method for upgrading software and device |
| CN111190639A (en) * | 2019-12-26 | 2020-05-22 | 中国建设银行股份有限公司 | Automatic upgrading method, system, device and storage medium suitable for WebLogic |
| CN112579358A (en) * | 2020-12-22 | 2021-03-30 | 深圳市科力锐科技有限公司 | Backup point detection method, device, equipment and storage medium |
| CN114895943A (en) * | 2022-05-30 | 2022-08-12 | 山东浪潮科学研究院有限公司 | Method and device for realizing incremental distribution and automatic upgrade of application configuration |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2000194542A (en) * | 1998-12-28 | 2000-07-14 | Hitachi Maxell Ltd | Application distributing method |
| CN1858704A (en) * | 2006-02-07 | 2006-11-08 | 华为技术有限公司 | Method of upgrading sequence |
| CN101030157A (en) * | 2007-04-20 | 2007-09-05 | 北京搜狗科技发展有限公司 | Method and system for updating user vocabulary synchronouslly |
| CN101038549A (en) * | 2007-03-28 | 2007-09-19 | 北京启明星辰信息技术有限公司 | A software updating method capable of crossing system |
| CN101854399A (en) * | 2010-06-09 | 2010-10-06 | 宇龙计算机通信科技(深圳)有限公司 | Method and device for aggregating network data |
| CN101930379A (en) * | 2010-08-20 | 2010-12-29 | 上海普元信息技术股份有限公司 | Structure and method for incremental deploying of server applications in distributed software system |
| CN102025778A (en) * | 2010-11-25 | 2011-04-20 | 成都勤智数码科技有限公司 | Software version upgrading work method based on Shell |
| US8368915B1 (en) * | 2006-06-23 | 2013-02-05 | Open Invention Network, Llc | System and method for printer driver management in an enterprise network |
-
2015
- 2015-09-14 CN CN201510583927.7A patent/CN105117263B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2000194542A (en) * | 1998-12-28 | 2000-07-14 | Hitachi Maxell Ltd | Application distributing method |
| CN1858704A (en) * | 2006-02-07 | 2006-11-08 | 华为技术有限公司 | Method of upgrading sequence |
| US8368915B1 (en) * | 2006-06-23 | 2013-02-05 | Open Invention Network, Llc | System and method for printer driver management in an enterprise network |
| CN101038549A (en) * | 2007-03-28 | 2007-09-19 | 北京启明星辰信息技术有限公司 | A software updating method capable of crossing system |
| CN101030157A (en) * | 2007-04-20 | 2007-09-05 | 北京搜狗科技发展有限公司 | Method and system for updating user vocabulary synchronouslly |
| CN101854399A (en) * | 2010-06-09 | 2010-10-06 | 宇龙计算机通信科技(深圳)有限公司 | Method and device for aggregating network data |
| CN101930379A (en) * | 2010-08-20 | 2010-12-29 | 上海普元信息技术股份有限公司 | Structure and method for incremental deploying of server applications in distributed software system |
| CN102025778A (en) * | 2010-11-25 | 2011-04-20 | 成都勤智数码科技有限公司 | Software version upgrading work method based on Shell |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106941420A (en) * | 2017-03-16 | 2017-07-11 | 北京深思数盾科技股份有限公司 | A kind of cluster application environment upgrade method and device |
| CN106941420B (en) * | 2017-03-16 | 2019-12-13 | 北京深思数盾科技股份有限公司 | cluster application environment upgrading method and device |
| CN108664255A (en) * | 2017-03-27 | 2018-10-16 | 中兴通讯股份有限公司 | A kind of method for upgrading software and device |
| CN108664255B (en) * | 2017-03-27 | 2023-04-11 | 深圳市中兴通讯技术服务有限责任公司 | Software upgrading method and device |
| CN107402780A (en) * | 2017-05-15 | 2017-11-28 | 梁亚柳 | Semi-automatic more new version software instrument |
| CN107273139A (en) * | 2017-07-05 | 2017-10-20 | 努比亚技术有限公司 | A kind of method for updating system, equipment and computer-readable recording medium |
| CN107844314A (en) * | 2017-12-22 | 2018-03-27 | 税友软件集团股份有限公司 | A kind of method and system of upgrading Weblogic application programs |
| CN111190639A (en) * | 2019-12-26 | 2020-05-22 | 中国建设银行股份有限公司 | Automatic upgrading method, system, device and storage medium suitable for WebLogic |
| CN112579358A (en) * | 2020-12-22 | 2021-03-30 | 深圳市科力锐科技有限公司 | Backup point detection method, device, equipment and storage medium |
| CN112579358B (en) * | 2020-12-22 | 2024-03-22 | 深圳市科力锐科技有限公司 | Backup point detection method, device, equipment and storage medium |
| CN114895943A (en) * | 2022-05-30 | 2022-08-12 | 山东浪潮科学研究院有限公司 | Method and device for realizing incremental distribution and automatic upgrade of application configuration |
| CN114895943B (en) * | 2022-05-30 | 2024-05-28 | 山东浪潮科学研究院有限公司 | Method and device for realizing incremental distribution and automatic upgrading of application configuration |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105117263B (en) | 2018-06-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105117263A (en) | UNIX environment software system upgrading method | |
| CN111209346B (en) | Block chain data archiving method and device and computer readable storage medium | |
| US10007499B2 (en) | Decoupled installation of data management systems | |
| US8972963B2 (en) | End-to-end patch automation and integration | |
| CN104487960B (en) | Automated disaster recovery and Data Migration | |
| CN104679534B (en) | System application installation package loading processing method, apparatus and terminal | |
| TWI575362B (en) | Backup method, pre-testing method for enviornment updating and system thereof | |
| CN110784495B (en) | Block chain-based discovery and configuration information management method for big data cluster system | |
| CN104572357A (en) | Backup and recovery method for HDFS (Hadoop distributed filesystem) | |
| US7774771B2 (en) | Method and system for managing and organizing software package installations | |
| CN109981279B (en) | Block chain system, communication method, device, equipment and medium | |
| CN102025778A (en) | Software version upgrading work method based on Shell | |
| CN105959390A (en) | Unified management system and method of micro services | |
| CN107870772B (en) | Cross-environment application deployment method, platform, system and readable storage medium | |
| CN103761329A (en) | Method and device for flashing mobile device | |
| CN112970020A (en) | Monitoring device components using distributed ledger | |
| CN102841824B (en) | Rollback method and rollback device | |
| CN108829433A (en) | A kind of web system version dispositions method, equipment and storage medium | |
| CN102521390B (en) | Database management and monitoring system based on pin function | |
| CN110647425A (en) | Database recovery method and device | |
| JP2014075088A (en) | Image forming apparatus, control method, and program thereof | |
| CN101924794B (en) | Internet based method for monitoring total software operation quantity in real time | |
| CN114024951A (en) | Power edge heterogeneous deployment method based on cloud edge collaboration | |
| CN106161532A (en) | A kind of orientation method for cleaning based on cloud service and system | |
| CN110096226B (en) | Disk array deployment method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |