CN104063294A - Linux system backup and restoring method - Google Patents
Linux system backup and restoring method Download PDFInfo
- Publication number
- CN104063294A CN104063294A CN201410319101.5A CN201410319101A CN104063294A CN 104063294 A CN104063294 A CN 104063294A CN 201410319101 A CN201410319101 A CN 201410319101A CN 104063294 A CN104063294 A CN 104063294A
- Authority
- CN
- China
- Prior art keywords
- backup
- scheme
- incremental
- linux system
- host
- 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
Abstract
The invention provides a Linux system backup and restoring method. The method includes the following steps that (1) a full backup scheme, an incremental backup scheme, a raw device restoring scheme and an increment restoring scheme are defined in advance; (2) real-time plan commands are received; (3) legality of a plan is detected; (4) the state of target nodes is determined; (5) the scheme according with the plan is executed. According to the Linux system backup and restoring method, a set of complete backup and restoring schemes are designed, servers are recognized through IP addresses, the backup and restoring plan commands are received, backup time is reasonably distributed, intelligentized centralized management of backups and restoration of the Linux servers in large batches is achieved, manpower and material resource consumption is reduced, and responding and processing efficiency is greatly improved.
Description
Technical field
The present invention relates to a kind of backup and restoration methods, specifically a kind of linux system backup and restoration methods.
Background technology
Install under the server of (SuSE) Linux OS; still mainly by system manager, be responsible for backup and the recovery of operating system; data base administrator is responsible for backup and the recovery of database; application system keeper is responsible for backup and the recovery of application system; there is no that a kind of instrument or system are operating system under whole server, database data, application system data, other data backups and recover, more not having the Linux server under completely online (the not shutting down) state of system or instrument support to back up completely.Rely on keepers' the script instrument mutually incompatible with each backup tool manufacturer, back-up job complexity and easily makeing mistakes.
Particularly, in the Linux server backup in the face of One's name is legion in machine room and the problem of management of recovery, the unified platform of neither one is as support, by keeper one by one and in a large number not the Shell scripts of easy care be difficult to deal with.The title of the backup information of each keeper definition, to preserve position, validity, use-pattern not identical, or even the corresponding relation of backup information and server, recover the information such as applicable elements and all there is no record, be all that recovery and the use of these Backup Datas brings difficulty.Say nothing of when keeper changes, back up and resume work handing-over, just extremely difficult especially.
Summary of the invention
In order to address the above problem, the invention provides a kind of linux system backup and restoration methods, by the processing scheme of default Four types, realize the intelligent backup of Linux server in enormous quantities and recovery operation.
The present invention is by the following technical solutions: a kind of linux system backup and restoration methods, it is characterized in that, and described method comprises the following steps:
Predefine full backup scheme, incremental backup scheme, raw device recovery scheme, increment recovery scheme;
Receive real-time Planning Directive;
Detect the legitimacy of plan;
Confirm the state of destination node;
Execution meets the scheme of plan.
Further, the process of predefine full backup scheme is:
Defining named standard;
Select the catalogue under operating system, set backup scope;
Set NFS agreement and two kinds of host-host protocols of SSH agreement;
Definition backup library node structure;
Setting command mode, two kinds of backup modes of snapshot mode;
Full backup scheme after audit is saved in database.
Further, the process of predefine incremental backup scheme is:
Defining named standard;
Set cumulative increment backup and two kinds of incremental backup types of difference incremental backup;
Select the catalogue under operating system, set backup scope;
Set NFS agreement and two kinds of host-host protocols of SSH agreement;
Definition auto-increment BACKUP TIME;
Defined node backup library structure;
Incremental backup scheme after audit is saved in database.
Further, resident client RCT can upload to database by the load state of destination node, according to numerous destination node load distribution situations, arranges each node incremental backup initial time.
Further, in incremental backup scheme implementation, whether resident client utility RCT former the component list of automatic comparison object node and current up-to-date the component list be variant, if variant, safeguard the component list change inventory that comprises component Name, affiliated bag, newly-increased/deletion content, and after the execution of incremental backup scheme finishes, pass back in backup set storehouse and merge and preserve with former the component list.
Further, when resident client utility RCT carries out the selected command mode of incremental backup scheme, whether RCT, according to the file attribute in backup scope, has relatively had alter operation since Last Backup, has and backs up packing as new incremental backup object.
Further, the process of predefine raw device recovery scheme is:
Setting recovery action required system, full backup collection, path, storehouse, incremental backup collection place;
Set NFS agreement and two kinds of host-host protocols of SSH agreement;
Definition recovers library structure;
Select LiveISO;
Select the resident instrument of RCT client;
Raw device recovery scheme after audit is saved in database.
Further, the process of predefine increment recovery scheme is:
Path, storehouse, the required incremental backup collection place of setting recovery;
Set NFS agreement and two kinds of host-host protocols of SSH agreement;
Definition recovers library structure;
Set backup detection module;
Increment recovery scheme after audit is saved in database.
The invention has the beneficial effects as follows: the present invention has designed a set of complete backup and recovery scheme, by IP Address Recognition server, receive backup and recover Planning Directive, reasonable distribution BACKUP TIME, realized the intelligent management to Linux server backup in enormous quantities and recovery, manpower and materials have been reduced, the efficiency that has greatly improved reaction and processed.
Accompanying drawing explanation
Fig. 1 is schematic flow sheet of the present invention;
Fig. 2 is the schematic flow sheet that the present invention carries out full backup scheme;
Fig. 3 is the schematic flow sheet that the present invention carries out incremental backup scheme;
Fig. 4 is the schematic flow sheet that the present invention carries out raw device recovery scheme;
Fig. 5 is the schematic flow sheet that the present invention carries out increment recovery scheme.
Embodiment
A kind of linux system backup and restoration methods as shown in Figure 1, described method comprises the following steps:
S101: predefine full backup scheme, its process is: the Naming conventions that definition needs; Select the catalogue under operating system, set backup scope, wherein, for system component, equipment, config directory etc., do not need selection to be automatically included in scope; Set NFS and SSH backup host-host protocol, wherein, NFS agreement needs the open backup set of backup center storehouse authority, and SSH agreement needs user in advance the user cipher of backup target server to be kept in database, if change of secret code meeting causes backup failure; Definition backup library node structure; Setting command mode, two kinds of backup modes of snapshot mode, wherein, command mode is applicable to all kinds of Linux backup target servers, and snapshot mode requires destination server disk slack space for using the more than 1.5 times of space, and free space allows subregion again; After finally this plan being examined, full backup scheme is saved in database.
S102: predefine incremental backup scheme, its process is: the Naming conventions that definition needs; Set cumulative increment backup and two kinds of incremental backup types of difference incremental backup, wherein, the increment of cumulative increment backup backup since last time full backup or accumulative total incremental backup, difference incremental backup has backed up the increment since Last Backup; Select the catalogue under operating system, set backup scope; Set NFS and SSH backup host-host protocol, wherein, NFS agreement needs the open backup set of backup center storehouse authority, and SSH agreement needs user in advance the user cipher of backup target server to be kept in database, if change of secret code meeting causes backup failure; The time of definition incremental backup, can be every day some, weekly just/end, the beginning of each month/end, beginning of each quarter/end, the per beginning of the year/last equal time; Defined node backup library structure; Setting command mode, two kinds of backup modes of snapshot mode, wherein, command mode is applicable to all kinds of Linux backup target servers, and snapshot mode requires destination server disk slack space for using the more than 1.5 times of space, and free space allows subregion again; After finally this plan being examined, incremental backup scheme is saved in database.
S103: predefine raw device recovery scheme, its process is: setting recovery action required system, full backup collection, path, storehouse, incremental backup collection place, select host-host protocol, definition recovers library structure, select LiveISO, select the resident instrument of RCT client, and this scheme is examined, information is kept in database.
S104: predefine increment recovery scheme, its process is: path, storehouse, the required incremental backup collection place of setting recovery, select host-host protocol, definition recovers library structure, and this scheme is examined, and information is kept in database.
S105: receive real-time Planning Directive, this Planning Directive can be artificial input, can be also the feedback of destination node.
S106: whether legally detect plan, if legal, enter next step, if illegal, return to previous step.
S107: confirm that destination node is in connection status, and the communications protocol of select target node employing;
S108: carry out the scheme that meets plan.
For the difference of four kinds of schemes in clear and definite this invention, below, by reference to the accompanying drawings the implementation of four kinds of schemes is described.
As shown in Figure 2, the process of execution full backup scheme is:
S201: select a kind of backup mode;
S202: transfer the file within the scope of backup;
S203: according to Naming conventions to the file compression of packing;
S204: carry out communication according to host-host protocol, backup set is filed in backup set storehouse corresponding to full backup scheme, the Data Source that the file directory in this backup set storehouse can be recovered as raw device.
As shown in Figure 3, the process of execution incremental backup scheme is:
S301: check each server state, set each server delta backup initial time;
S302: select a kind of backup mode;
S303: transfer the file within the scope of backup;
S304: whether resident client utility RCT former the component list of automatic comparison object node and current up-to-date the component list be variant, if variant, after safeguarding the component list change inventory that comprises component Name, affiliated bag, newly-increased/deletion content, enter step S305, if fruit does not have, directly enter next step;
S305: according to Naming conventions to the file compression of packing;
S306: carry out communication according to host-host protocol, backup set is filed in backup set storehouse corresponding to full backup scheme, the Data Source that the file directory in this backup set storehouse can be recovered as raw device.
Further, when resident client utility RCT carries out the selected command mode of incremental backup scheme, whether RCT, according to the file attribute in backup scope, has relatively had alter operation since Last Backup, has and backs up packing as new incremental backup object.
As shown in Figure 4, the process of execution increment recovery scheme is:
S401: carry out communication, receive the backup set that recovers requirements of plan;
S402: whether check needs to recover front backup, enters next step after if so, carrying out backup operation, if not, directly enters next step;
S403: transfer recovery data, carry out recovery operation;
S404: check whether restoration result meets the requirements, and if so, enters next step, if not, returns to previous step;
S405: rejuvenation records and upload to database.
As shown in Figure 5, the process of execution raw device recovery scheme is:
S501: make LiveISO mirror optical disk, CD-ROM drive is written into this CD on destination server, the automatic Boot Server of guiding tool on this CD starts and enters raw device recovery routine;
S502: with backup library communication, receive and recover needed backup medium and backup set;
S503: recovery operation system;
S504: RCT instrument is installed;
S505: recover full backup data;
S506: recover incremental backup data;
S507: check whether restoration result meets the requirements, and if so, enters next step, if not, returns to S502;
S508: rejuvenation records and upload to database.
In the implementation of four kinds of schemes, the information that destination node or server comprise comprises the IP address of server, server name, the host-host protocol of supporting, OS Type and version, file system type, hard disk configuration, memory configurations, network card configuration, directory information, module information etc., wherein, IP address is the foundation that backup and rehabilitation center identify numerous backup target servers or recovery destination server, OS Type and version, file system type, hard disk configuration, memory configurations, network card configuration, directory information, module information etc., user name at input destination server, after password, can be connected to destination server by the automatic acquisition instrument of this platform, carry out corresponding system order automatic acquisition.
Except structure of the present invention, all the other are prior art.
The above is the preferred embodiment of the present invention, for those skilled in the art, under the premise without departing from the principles of the invention, can also make some improvements and modifications, and these improvements and modifications are also regarded as protection scope of the present invention.
Claims (8)
1. linux system backup and a restoration methods, is characterized in that, described method comprises the following steps:
Predefine full backup scheme, incremental backup scheme, raw device recovery scheme, increment recovery scheme;
Receive real-time Planning Directive;
Detect the legitimacy of plan;
Confirm the state of destination node;
Execution meets the scheme of plan.
2. a kind of linux system backup according to claim 1 and restoration methods, is characterized in that, the process of predefine full backup scheme is:
Defining named standard;
Select the catalogue under operating system, set backup scope;
Set NFS agreement and two kinds of host-host protocols of SSH agreement;
Defined node backup library structure;
Setting command mode, two kinds of backup modes of snapshot mode;
Full backup scheme after audit is saved in database.
3. a kind of linux system backup according to claim 1 and restoration methods, is characterized in that, the process of predefine incremental backup scheme is:
Defining named standard;
Set cumulative increment backup and two kinds of incremental backup types of difference incremental backup;
Select the catalogue under operating system, set backup scope;
Set NFS agreement and two kinds of host-host protocols of SSH agreement;
Definition auto-increment BACKUP TIME;
Definition backup library node structure;
Incremental backup scheme after audit is saved in database.
4. a kind of linux system according to claim 3 backs up and restoration methods, it is characterized in that, resident client RCT can upload to database by the load state of destination node, according to numerous destination node load distribution situations, arranges each node incremental backup initial time.
5. a kind of linux system according to claim 3 backs up and restoration methods, it is characterized in that, in incremental backup scheme implementation, whether resident client utility RCT former the component list of automatic comparison object node and current up-to-date the component list be variant, if variant, safeguard that one comprises component Name, affiliated bag, newly-increased/to delete the component list change inventory of content, and after the execution of incremental backup scheme finishes, pass back in backup set storehouse and merge and preserve with former the component list.
6. a kind of linux system according to claim 3 backs up and restoration methods, it is characterized in that, when resident client utility RCT carries out the selected command mode of incremental backup scheme, RCT is according to the file attribute in backup scope, relatively since Last Backup, whether there is alter operation, have and back up packing as new incremental backup object.
7. a kind of linux system backup according to claim 1 and restoration methods, is characterized in that, the process of predefine raw device recovery scheme is:
Setting recovery action required system, full backup collection, path, storehouse, incremental backup collection place;
Set NFS agreement and two kinds of host-host protocols of SSH agreement;
Definition recovers library structure;
Select LiveISO;
Select the resident instrument of RCT client;
Raw device recovery scheme after audit is saved in database.
8. a kind of linux system backup according to claim 1 and restoration methods, is characterized in that, the process of predefine increment recovery scheme is:
Path, storehouse, the required incremental backup collection place of setting recovery;
Set NFS agreement and two kinds of host-host protocols of SSH agreement;
Definition recovers library structure;
Increment recovery scheme after audit is saved in database.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410319101.5A CN104063294B (en) | 2014-07-07 | 2014-07-07 | A kind of linux system backup and restoration methods |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410319101.5A CN104063294B (en) | 2014-07-07 | 2014-07-07 | A kind of linux system backup and restoration methods |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104063294A true CN104063294A (en) | 2014-09-24 |
| CN104063294B CN104063294B (en) | 2016-03-16 |
Family
ID=51551016
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410319101.5A Active CN104063294B (en) | 2014-07-07 | 2014-07-07 | A kind of linux system backup and restoration methods |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104063294B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105302671A (en) * | 2015-11-11 | 2016-02-03 | 中国建设银行股份有限公司 | Automatic backup and rollback method and device |
| CN106339278A (en) * | 2016-08-24 | 2017-01-18 | 浪潮电子信息产业股份有限公司 | Data backup and recovery method for network file system |
| CN106919477A (en) * | 2017-03-03 | 2017-07-04 | 上海爱数信息技术股份有限公司 | The analytic method and system of a kind of virtual disk |
| CN114610535A (en) * | 2022-02-21 | 2022-06-10 | 广州鼎甲计算机科技有限公司 | Linux operating system bare computer recovery method, system, device and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100505614C (en) * | 2006-08-15 | 2009-06-24 | 华为技术有限公司 | System backup and recovery method, and backup and recovery server |
| CN102693168A (en) * | 2011-03-22 | 2012-09-26 | 中兴通讯股份有限公司 | A method, a system and a service node for data backup recovery |
| US20120324280A1 (en) * | 2011-06-14 | 2012-12-20 | Computer Associates Think, Inc. | System and method for data disaster recovery |
| CN103885855A (en) * | 2012-12-20 | 2014-06-25 | 航天信息股份有限公司 | Data backup and recovery method and data backup and recovery device |
-
2014
- 2014-07-07 CN CN201410319101.5A patent/CN104063294B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100505614C (en) * | 2006-08-15 | 2009-06-24 | 华为技术有限公司 | System backup and recovery method, and backup and recovery server |
| CN102693168A (en) * | 2011-03-22 | 2012-09-26 | 中兴通讯股份有限公司 | A method, a system and a service node for data backup recovery |
| US20120324280A1 (en) * | 2011-06-14 | 2012-12-20 | Computer Associates Think, Inc. | System and method for data disaster recovery |
| CN103885855A (en) * | 2012-12-20 | 2014-06-25 | 航天信息股份有限公司 | Data backup and recovery method and data backup and recovery device |
Non-Patent Citations (1)
| Title |
|---|
| 张兴发等: "分布式Linux下数据库文件自动备份和恢复", 《计算机时代》, no. 1, 31 January 2006 (2006-01-31), pages 16 - 17 * |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105302671A (en) * | 2015-11-11 | 2016-02-03 | 中国建设银行股份有限公司 | Automatic backup and rollback method and device |
| CN106339278A (en) * | 2016-08-24 | 2017-01-18 | 浪潮电子信息产业股份有限公司 | Data backup and recovery method for network file system |
| CN106919477A (en) * | 2017-03-03 | 2017-07-04 | 上海爱数信息技术股份有限公司 | The analytic method and system of a kind of virtual disk |
| CN106919477B (en) * | 2017-03-03 | 2020-05-22 | 上海爱数信息技术股份有限公司 | Virtual disk analysis method and system |
| CN114610535A (en) * | 2022-02-21 | 2022-06-10 | 广州鼎甲计算机科技有限公司 | Linux operating system bare computer recovery method, system, device and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104063294B (en) | 2016-03-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11907254B2 (en) | Provisioning and managing replicated data instances | |
| US10218587B2 (en) | Transparently tracking provenance information in distributed data systems | |
| CN109582443A (en) | Virtual machine standby system based on distributed storage technology | |
| CN104239166A (en) | Method for realizing file backup for running virtual machine | |
| CN104781791A (en) | Universal pluggable cloud disaster recovery system | |
| JP5868986B2 (en) | Recovery by item | |
| CN105446831A (en) | Server-Free backup method in conjunction with SAN | |
| CN104063294B (en) | A kind of linux system backup and restoration methods | |
| CN112800019A (en) | Data backup method and system based on Hadoop distributed file system | |
| US11748495B2 (en) | Systems and methods for data usage monitoring in multi-tenancy enabled HADOOP clusters | |
| US11902452B2 (en) | Techniques for data retrieval using cryptographic signatures | |
| US8700750B2 (en) | Web deployment functions and interfaces | |
| KR100935831B1 (en) | A method for a data synchronizing based on a data structure which has multiple event identifier and the Data back up solution uses the method | |
| US11079960B2 (en) | Object storage system with priority meta object replication | |
| US20220075769A1 (en) | Logfile collection and consolidation | |
| US11074002B2 (en) | Object storage system with meta object replication | |
| US11093465B2 (en) | Object storage system with versioned meta objects | |
| US20240045770A1 (en) | Techniques for using data backup and disaster recovery configurations for application management | |
| US20240031353A1 (en) | Techniques for secure host connectivity in disaster recovery scenarios | |
| US20240086285A1 (en) | Configuration recovery for a data management system | |
| US20240160534A1 (en) | Snappable recovery chain over generic managed volume | |
| US20230376386A1 (en) | Backup management for synchronized databases | |
| JP3215125U (en) | Backup system | |
| CN104035841A (en) | Virtual desktop data backup and recovery method and virtual desktop data backup and recovery device | |
| Bach et al. | Implementing Data Guard |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |