CN104714864A - Intelligent computer data backup method - Google Patents
Intelligent computer data backup method Download PDFInfo
- Publication number
- CN104714864A CN104714864A CN201510123310.7A CN201510123310A CN104714864A CN 104714864 A CN104714864 A CN 104714864A CN 201510123310 A CN201510123310 A CN 201510123310A CN 104714864 A CN104714864 A CN 104714864A
- Authority
- CN
- China
- Prior art keywords
- file
- backup
- list
- rule
- delta
- 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
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides an intelligent computer data backup method. By means of the method, data belonging to user data are determined, and backup is conducted on the user data. In the full backup process, a user operating system is scanned, and the name, version, installation path, application program name, application program version, application program installation path and other features are obtained; after the features are compared with cloud backup files, backup does not need to be conducted on the common files in the backup process; the full path names of the user backup files are compared with the abstract value, if matching is successful, backup does not need to be conducted on this type of user target files as well, and thus the backup speed is increased; after one-time full backup is finished, target files which change are determined when a user uses a computer, when a backup command is received, backup is directly conducted on the changed target files, the changed files do not need to be determined through scanning, and backup software performance can be improved greatly; meanwhile, the user does not need to set the backup path again, and the defects of missing of files and loss of data are overcome.
Description
Technical field
The present invention relates to information security field, particularly relate to a kind of computer data intelligent backup method.
Background technology
Along with the generally use of computer technology, create a large amount of data, these data are mainly kept on various storage medium with the form of volume, file, database, and these data store in a large number with document form, use and transmit.Due to computing machine self fragility feature, data are often subject to full spectrum of threats, as virus, maloperation, stolen, mechanical disorder, disaster etc., make data be very easy to deleted, damage and lose.Tackling these threatens best bet to be carry out data backup.
For file backup, common way is: install a backup agent program on the user computer, adopt timed backup or strategy of backing up in realtime, regularly or in real time user file data (hereinafter referred to as file destination) are backuped to local storage medium or high in the clouds.In backup procedure, backup agent requires that user provides configuration information, as file path, file type, creation-time, modification time etc.But a lot of naive user does not also know file destination path, does not understand file type yet, say nothing of creation-time, modification time.Therefore, important file destination is often caused not back up.
Common backup policy can be divided into backup, incremental backup and differential backup completely.Backup is that all backup objects are all copied one time completely.Incremental backup copies the data changed between twice backup.Differential backup is the data copying this backup and change between backup completely.For incremental backup and differential backup, when adopting timed backup strategy, all need the change between contrast twice backup, determine that the general way of data variation is that scanning needs file destination and determines which file there occurs change at present.
In scanning process, first step is the metadata obtaining file destination, as complete trails filename, file size, modification time, last access time etc., judges whether file destination there occurs change with this; If first step can confirm that file destination there occurs change, then back up this file destination, if can not confirm, the digest value usually calculating file destination confirms whether file destination changes, if there occurs change, then backs up this file destination.Take up room in larger situation, as reached TB level, or in the more situation of file destination number for file destination, as reached 1,000,000 grades, then backup agent is by file destinations all for scanning, scans consuming time longer, cause subscriber computer performance degradation, even can not normally use.And in fact, in a backup cycle, within the time, the file destination that user just really uses, the file destination of actual generation data variation is fewer, needs to scan and determines whether that the file destination that data variation occurs is in the great majority.Backup agent takes a large amount of read-write resources and the time judges whether a file destination there occurs change, causes a large amount of waste, seriously drags slow computing power.
Summary of the invention
In order to solve the problem, the present invention proposes a kind of computer data intelligent backup method, helps user to determine which data belongs to user data, and backs up user data.In complete backup procedure, scanning operating system of user, obtain OS name, version, installation path, the features such as application name, version, installation path, and high in the clouds backup file contrast after, this type of known file can not be backed up during backup, on the other hand, the user's comspec of backup file and digest value is compared, after coupling, also need not back up this type of ownership goal file, thus improve backup rate.After completing once backup completely, use in computer procedures user and determine which file destination there occurs change, after receiving backup instruction, directly back up the file destination changed, and obstructed overscanning is determined to change to can greatly improve backup software performance by file.Meanwhile, user does not need to need Offered target file path more yet, overcomes the defect of file destination omission, loss of data risk.
The present invention relates to a kind of computer data intelligent backup method, comprising:
Step 1, complete backup module suspense file change detects, scanning custom system, obtain custom system feature and be sent to high in the clouds, generate non-backup file list and back up completely to high in the clouds, custom system feature at least comprises title, version, the installation path of application program of OS name, version, installation path and all installations;
Step 2, activates file change and detects, and complete backup module sends to file change detection module and activates message, and file change module changes running status into from halted state;
Step 3, file change detects and sends, file change detection module obtains system file change events, and obtains the file full path name relevant with this file change events, time, process name and type and form a file change events message, and sends to increment determination module;
Step 4, rule is loaded into step, and increment determination module is loaded into rule from rule base, at least comprises user class rule and system class rule;
Step 5, delta file determination step, increment determination module wait-receiving mode file change event, judge whether file change event is repeated events, rule in matching rule base, if do not mate all user class rule or mate any system class rule, then the file full path name of file change event is written to delta file list, otherwise abandons this file change events message;
Step 6, reads in delta file listings step, and incremental backup module reads in the comspec of all delta files;
Step 7, incremental backup finds out the standby volume of increasing at delta file place, travels through the standby volume of each increasing, to each increasing standby volume generating snapshot, carry snapshot, and delta file, delta file comspec, delta file digest value are sent to high in the clouds, delete snapshot, finally empty delta file list;
Step 8, rule base step of updating, rule base update module sends host characteristics to high in the clouds, and high in the clouds, according to host characteristics, returns rule base;
Step 9, rule base write step, the rule after renewal is written in rule base by Policy Updates module.
Generate non-backup file list in described step 1 and back up completely to high in the clouds and be further:
Step 21, high in the clouds is according to custom system feature, compare with the operating system file backed up in advance, application file, when after coupling, in conjunction with local system installation path, the comspec generating matching files is written in backup file list (but not needing file digest values), the subscriber data file list backed up in the past and digest value is write in backup file list simultaneously, backup file list is sent to complete backup module;
Step 22, all volumes of system of enumerating, generate the list of complete standby volume;
Step 23, judges whether the list of complete standby volume is empty, if be empty, goes to step 28, if be not empty, goes to step 24;
Step 24, selects one in the list of complete standby volume complete standby volume, to this complete standby volume generating snapshot;
Step 25, generate non-backup file listings step, the snapshot that carry step 24 generates, each file in traversal snapshot, file, generate comspec, by comspec and backup file list contrast, for the comspec matched in backup file list, if this comspec does not contain digest value, then think that the match is successful, this file backs up, otherwise, if containing digest value, then calculate the digest value of this file in local system, and it is more equal with the digest value of corresponding record in backup file list, if equal, then think that this file backs up, otherwise add this file complete trails to non-backup file list, for the comspec do not mated in backup file list, add this file complete trails to non-backup file list,
Step 26, sends non-backup file list, non-backup file, digest value to high in the clouds, empty non-backup file list;
Step 27, the snapshot that delete step 24 generates, removes this complete standby volume, goes to step 23 from the list of complete standby volume;
Step 28, sends full backup end to high in the clouds;
Step 29, sends to file change detection module and activates message, and file change detects and becomes running status from halted state.
User class rule and system class rule in described step 4, is characterized in that:
User class rule at least comprises: consumer process exclusionary rules, consumer process directory name exclusionary rules, file name exclusionary rules; System class rule at least comprises: system process comprises rule;
Consumer process exclusionary rules matching condition: process title;
Consumer process directory name exclusionary rules matching condition: consumer process name and the comspec of catalogue;
File name exclusionary rules matching condition: the comspec of file;
System process comprises rule match conditions: process title.
Described step 5 is further:
Step 41, wait-receiving mode file change event message, comprises document creation, file is write, file moves, go to step 42 after receiving file change event message;
Step 42, searches in delta file list, if certain file full path name is identical with the file full path name of current file change events message, then thinks that this file change events is repeated events, goes to step 41, otherwise go to step 43;
Step 43, compares process title and whether belongs to system user, if so, is then system process, goes to step 44, if not, go to step 45;
Step 44, compares process title and whether mates certain system process and comprise rule, if coupling, then thinks that this file change events belongs to backup scope, goes to step 46, otherwise go to step 41;
Step 45, is written to delta file list, goes to step 41 by file full path name;
Whether step 46, compare process title and mate with certain consumer process exclusionary rules, if coupling, then think that this file change is not within the scope of backup, goes to step 41, otherwise goes to step 47;
Step 47, compares change file directory name and whether process title mates certain consumer process directory name exclusionary rules, if coupling, then thinks that this file change is not within the scope of backup, goes to step 41, otherwise goes to step 48;
Step 48, compares change file full path name and whether mates certain user file name exclusionary rules, if coupling, then think that this file change is not within the scope of backup, goes to step 41, otherwise goes to step 45.
Described step 7 is further:
Step 51, travels through each delta file comspec, obtains the file label of delta file place volume, if not this file label in the list of increment volume, then write increases the list of standby volume, otherwise does not write;
Step 52, judges that whether increase the list of standby volume is empty, as empty, then go to step 56, otherwise goes to step 53;
Step 53, selects one to increase standby volume, generates the snapshot of the standby volume of this increasing in the list of increasing standby volume;
Step 54, the list of traversal delta file, finds the delta file comspec belonging to this increment volume, and the snapshot of the standby volume of this increasing reads this delta file, sends delta file, delta file comspec, delta file digest value to high in the clouds;
Step D55, deletes this increasing for volume shadow copy, removes file label, go to step 53 from the list of increasing standby volume;
Step 56, empties delta file list.
Described step 8 is further:
Step 61, rule base update module scanning operating system of user, obtains custom system feature, obtains present system time;
Step 62, sends custom system characteristic sum present system time to high in the clouds;
Step 63, responds if do not receive high in the clouds, then goes to step 67, otherwise go to step 64;
Step 64, the rule base version returned in high in the clouds and current version compare, and as changed, go to step 65, otherwise go to step 66;
Step 65, downloads new rule base from high in the clouds;
Step 66, latency period P step, goes to step 61;
Step 67, latency period Q step, goes to step 61.
Beneficial effect of the present invention is that user does not need configuration target file path, and ownership goal file is not omitted, and reduces the burden that user uses standby system; Without the need to backing up operating system file, the application file in preset high in the clouds, without the need to backing up the data backed up, improve complete backup rate; Obtaining file change without the need to scanning file destination during incremental backup, using process classification Sum fanction to filter, obtaining the user's delta file that there is backup and be worth, directly back up delta file, saved system I/O, greatly accelerated backup rate.
Accompanying drawing explanation
Fig. 1 is each module rack composition.
Fig. 2 is data intelligence backup process flow diagram.
Fig. 3 is for back up process flow diagram completely.
Fig. 4 is file increment change decision flowchart.
Fig. 5 is that incremental backup flow process is as figure.
Fig. 6 is that rule base upgrades process flow diagram.
Embodiment
Below in conjunction with accompanying drawing, the present invention is described in further detail.
The each module rack composition of the present invention as shown in Figure 1.
File change detection module A, for detecting file change event, file change detection module is the filtration drive or the microfiltration driving that are arranged on operating system file system drive layer, be usually located in operating system nucleus, after file change event being detected, as document creation, file write, file moves, file change event is packaged as file change event message and sends to increment determination module.Each file change event forms a file change events message, and file change event message is by comprising following field:
File full path name: file store path and filename that file change event occurs, such as: C: testA testB.txt;
Time: the system time that file change occurs, be accurate to millisecond;
Type: for document creation, file write, file movement wherein a kind of;
Process name: the process name causing file change.
Complete backup module B, for executing full backup, detecting the All Files be present in operating system, obtaining local system feature, compare with the existing operating system file in high in the clouds, application file and user backup file, non-backup file is backuped to high in the clouds.
Delta file list C, for storing the record being defined as delta file through increment determination module, each delta file record, each record comprises following field:
File full path name: the file store path of file destination and filename, such as: C: testA testB.txt.
Incremental backup module D, for backing up delta file.When performing incremental backup, from delta file list C, reading delta file information, delta file is transferred to high in the clouds and completes backup.
Increment determination module E, for judging the data variation whether the file change event of sending from file change detection module occurs as user file, if so, write delta file list C, if not, then abandons.
Rule base F, for the decision rule needed for storage file change determination module E.Rule at least comprises two large classes, first kind rule is user class rule, Equations of The Second Kind rule is system class rule, three little rule-likes are at least comprised again in first kind rule, be respectively consumer process exclusionary rules FR101, consumer process directory name exclusionary rules FR102, file name exclusionary rules FR103, each little rule-like can comprise one or more; In Equations of The Second Kind rule, at least comprise a little rule-like, for system process comprises regular FR201, each little rule-like can comprise one or more.
Consumer process exclusionary rules FR101 can be described as:
Process title: such as: video player.
Consumer process exclusionary rules FR101 effect: get rid of the consumer process that can not produce user data, as video player, audio player, this type of consumer process may from network download data and file system buffer memory, but this type of video, voice data are not the data that user produces, not there is backup be worth, got rid of.
Consumer process directory name exclusionary rules FR102 can be described as:
Consumer process name: process software of such as handling official business;
The comspec of catalogue: such as: C: testA.
Consumer process directory name exclusionary rules FR102 effect: get rid of the temporary file that some software produces, this type of software can produce temporary file in formulation catalogue, but this class file produces in user's use procedure, it not the file of the actual editor of user, not there is backup be worth, as the cache file of browser in upper network process.
File name exclusionary rules FR103 can be described as:
The comspec of file: such as: C: pagefile.sys.
The effect of file name exclusionary rules FR103: removal system or application cache or swap file.
System process comprises regular FR201 and can be described as:
Process title: such as: mysqld-nt.exe, it is the system service process of MySql database.
System process comprises the effect of regular FR201: the file change that the system process comprising the change of generation user data causes.
Rule base update module G, for reading rule from high in the clouds, and update rule storehouse.
High in the clouds H, for storing user ID file, backup file list, digest value, rule base etc., high in the clouds is one or one group of server composition, is positioned over Local or Remote and provides backup services.
Data intelligence backup process flow diagram of the present invention as shown in Figure 2.
Step T201, complete backup-step, complete backup module suspense file change detects, scanning custom system, obtain custom system feature, upload user system features is to high in the clouds, high in the clouds returns backup file list, complete backup module enumerates all volumes, generate the list of complete standby volume, to each volume generating snapshot in the list of complete standby volume, carry snapshot, All Files folder in traversal snapshot, file, and contrast with backup file list, generate non-backup file list, complete backup module is according to non-backup file list, non-backup file list is sent to high in the clouds, non-backup file, digest value, non-backup file list is emptied after being transmitted, delete snapshot, full backup end is sent to high in the clouds.
Step T202, activates file change detecting step, and complete backup module sends to file change detection module and activates message, and file change module changes running status into from halted state.
Step T203, file change detects and forwarding step, file change detection module obtains system file change events, and obtains the file full path name relevant with this file change events, time, process name and type and form a file change events message, and sends to increment determination module.
Step T204, rule is loaded into step, and increment determination module is loaded into rule from rule base, at least comprises user class rule and system class rule.
Step T205, delta file determination step, first increment determination module judges whether file change event is repeated events, then the rule in matching rule base, if coupling, be then written to delta file list by delta file comspec, otherwise abandon this file change events message.
Step T206, reads in delta file listings step, and incremental backup module reads in all delta file comspecs from delta file list.
Step T207, incremental backup step, incremental backup module reads All Files comspec from delta file list, find out the standby volume of increasing at delta file place, travel through the standby volume of each increasing, to each increasing standby volume generating snapshot, carry snapshot, and delta file, delta file comspec, delta file digest value are sent to high in the clouds, delete snapshot, finally empty delta file list.
Step T208, rule base step of updating, rule base update module sends host characteristics to high in the clouds, as OS name, version, installation path, and application name, version, installation path and present system time, if high in the clouds does not respond, then latency period Q sends again, and high in the clouds, according to host characteristics, returns rule base, rule base update module downloads latency period P behind new regulation storehouse, then executing rule storehouse step of updating.
Step T209, rule base write step, the rule after renewal is written in rule base by Policy Updates module.
The flow process of backup completely of the present invention as shown in Figure 3.
Step B301, suspense file change detects, obtain custom system feature and be sent to high in the clouds step, complete backup module sends the message suspended and detect to file change detection module, scanning custom system, obtain title, version, the installation path of application program of OS name, version, installation path and all installations, and above-mentioned information is dealt into high in the clouds.
Step B302, obtain user's backup file listings step, high in the clouds is according to custom system feature, comprise OS name, version, application name, version, compare with the operating system file backed up in advance, application file, when after coupling, in conjunction with local system installation path, the comspec generating matching files is written to (but not needing file digest values) in backup file list, the subscriber data file list backed up in the past and digest value are write in backup file list simultaneously, backup file list is sent to complete backup module.Backup file list is made up of backup file record, and each backup file record comprises two parts, and a part is comspec, and another part is digest value.
Step B303, generate complete standby volume listings step, all volumes of system of enumerating, generate the list of complete standby volume.
Step B304, judges whether in the list of complete standby volume be sky step, if be empty, goes to step B309, if be not empty, go to step B305.
Step B305, selects complete standby volume and generating snapshot step, selects one in the list of complete standby volume complete standby volume, to this complete standby volume generating snapshot.
Step B306, generate non-backup file listings step, the snapshot that carry step B305 generates, each file in traversal snapshot, file, generate comspec, by comspec and backup file list contrast, for the comspec matched in backup file list, if this comspec does not contain digest value, then think that the match is successful, this file backs up, otherwise, if containing digest value, then calculate the digest value of this file in local system, and it is more equal with the digest value of corresponding record in backup file list, if equal, then think that this file backs up, otherwise add this file complete trails to non-backup file list, for the comspec do not mated in backup file list, this file complete trails is added the backup file list that puts in place.
Step B307, send non-backup file list, non-backup file, digest value step to high in the clouds, first send non-backup file list to high in the clouds, complete backup module is again according to non-backup file list, send non-backup file and digest value to high in the clouds item by item, finally empty non-backup file list.
Step B308, deletes snapshot, removes this complete standby volume step from the list of complete standby volume, and after these complete standby volume associated documents have backed up, the snapshot that complete backup module delete step B305 generates, then removes this volume, go to step B304 from the list of complete standby volume.
Step B309, sends full backup end to high in the clouds, once after complete Backup end, complete backup module sends full backup end to high in the clouds.
Step B310, sends to file change detection module and activates message, and complete backup module sends to file change detection module and activates message, and file change detects and becomes running status from halted state.
File increment change determination flow of the present invention as shown in Figure 3.
Step e 401, wait-receiving mode file change event message step, increment determination module waits for the file change event message sent from file change detection module, when receiving file change event message, comprise document creation, file is write, file moves, and goes to step E402.
Step e 402, whether comparison document change events is repetition eventing step, increment determination module parses file full path name from current file change events message, the list of traversal delta file, when the file full path name of certain record is equal with the file full path name of current file change events message, then think that this file change events is repeated events, go to step E401, otherwise go to step E403.
Step e 403, compares the step whether process belongs to system process, increment determination module according to process name, calling system interface, whether the determinating processes owner belongs to system user, and if so, then this process is system process, go to step E404, if not, go to step E405.
Step e 404, compare process name whether mate certain system process comprise rule step, if coupling, then think that this file change events belongs to backup scope, go to step E406, otherwise go to step E401.
Step e 405, is written to the step of delta file list, change file full path name is written to delta file list, goes to step E401 by change file full path name.
Step e 406, compare process name whether with the step of certain consumer process exclusionary rules coupling, if coupling, then think that this file change is not within the scope of backup, goes to step E401, otherwise goes to step E407.
Step e 407, compares change file directory name and whether process name mates the step of certain consumer process directory name exclusionary rules simultaneously, if coupling, then thinks that this file change is not within the scope of backup, goes to step E401, otherwise goes to step E408.
Step e 408, compares the step whether change file full path name mates certain user file name exclusionary rules, if coupling, then thinks that this file change is not within the scope of backup, goes to step E401, otherwise goes to step E405.
Incremental backup flow process of the present invention as shown in Figure 5.
Step D501, obtains increasing the step of standby volume list, travels through every bar delta file record, obtains the file label storing delta file, if not this file label in the list of increment volume, then write increases the list of standby volume, otherwise does not write.
Step D502, whether be sky step, judge that whether increase the list of standby volume is empty, as empty, then turn D506, otherwise turns D503 if increasing in the list of standby volume.
Step D503, selects one to increase standby volume and generating snapshot step, selects one to increase standby volume, generate the snapshot of the standby volume of this increasing in the list of increasing standby volume.
Step D504, send delta file, delta file comspec, delta file digest value to high in the clouds step, the list of incremental backup module walks delta file, find the delta file comspec belonging to this increment volume, the snapshot of the standby volume of this increasing reads this delta file, sends delta file, delta file comspec, delta file digest value to high in the clouds.
Step D505, deletes this increasing for volume shadow copy, removes file label step, go to step D503 from the list of increasing standby volume.
Step D506, empties delta file listings step.
More new technological process is as shown in Figure 6 for rule base of the present invention.
Step G601, obtains custom system characteristic sum present system time step, and rule base update module scanning operating system of user, obtain OS name, version, installation path, application name, version, installation path are as custom system feature.
Step G602, sends custom system characteristic sum present system time step to high in the clouds.
Whether step G603, receive high in the clouds and respond step, responds, then go to step G607, otherwise go to step G604 if do not receive high in the clouds.
Step G604, judgment rule storehouse changes step, and the rule base version returned in high in the clouds and current version compare, and as changed, go to step G605, otherwise go to step G606.
Step G605, download rule base, update rule storehouse step, Policy Updates library module downloads new rule base from high in the clouds, update rule storehouse.
Step G606, latency period P step, goes to step G601.
Step G607, latency period Q step, goes to step G601.
Those skilled in the art, under the condition not departing from the spirit and scope of the present invention that claims is determined, can also carry out various amendment to above content.Therefore scope of the present invention is not limited in above explanation, but determined by the scope of claims.
Claims (6)
1. a computer data intelligent backup method, is characterized in that, comprising:
Step 1, complete backup module suspense file change detects, scanning custom system, obtain custom system feature and be sent to high in the clouds, generate non-backup file list and back up completely to high in the clouds, custom system feature at least comprises title, version, the installation path of application program of OS name, version, installation path and all installations;
Step 2, activates file change and detects, and complete backup module sends to file change detection module and activates message, and file change module changes running status into from halted state;
Step 3, file change detects and sends, file change detection module obtains system file change events, and obtains the file full path name relevant with this file change events, time, process name and type and form a file change events message, and sends to increment determination module;
Step 4, rule is loaded into step, and increment determination module is loaded into rule from rule base, at least comprises user class rule and system class rule;
Step 5, delta file determination step, increment determination module wait-receiving mode file change event, judge whether file change event is repeated events, rule in matching rule base, if do not mate all user class rule or mate any system class rule, then the file full path name of file change event is written to delta file list, otherwise abandons this file change events message;
Step 6, reads in delta file listings step, and incremental backup module reads in the comspec of all delta files;
Step 7, incremental backup finds out the standby volume of increasing at delta file place, travels through the standby volume of each increasing, to each increasing standby volume generating snapshot, carry snapshot, and delta file, delta file comspec, delta file digest value are sent to high in the clouds, delete snapshot, finally empty delta file list;
Step 8, rule base step of updating, rule base update module sends host characteristics to high in the clouds, and high in the clouds, according to host characteristics, returns rule base;
Step 9, rule base write step, the rule after renewal is written in rule base by Policy Updates module.
2. the computer data intelligent backup method as described in claim 1, is characterized in that, generates non-backup file list and back up completely to high in the clouds to be further in described step 1:
Step 21, high in the clouds is according to custom system feature, compare with the operating system file backed up in advance, application file, when after coupling, in conjunction with local system installation path, the comspec generating matching files is written in backup file list (but not needing file digest values), the subscriber data file list backed up in the past and digest value is write in backup file list simultaneously, backup file list is sent to complete backup module;
Step 22, all volumes of system of enumerating, generate the list of complete standby volume;
Step 23, judges whether the list of complete standby volume is empty, if be empty, goes to step 28, if be not empty, goes to step 24;
Step 24, selects one in the list of complete standby volume complete standby volume, to this complete standby volume generating snapshot;
Step 25, generate non-backup file listings step, the snapshot that carry step 24 generates, each file in traversal snapshot, file, generate comspec, by comspec and backup file list contrast, for the comspec matched in backup file list, if this comspec does not contain digest value, then think that the match is successful, this file backs up, otherwise, if containing digest value, then calculate the digest value of this file in local system, and it is more equal with the digest value of corresponding record in backup file list, if equal, then think that this file backs up, otherwise add this file complete trails to non-backup file list, for the comspec do not mated in backup file list, add this file complete trails to non-backup file list,
Step 26, sends non-backup file list, non-backup file, digest value to high in the clouds, empty non-backup file list;
Step 27, the snapshot that delete step 24 generates, removes this complete standby volume, goes to step 23 from the list of complete standby volume;
Step 28, sends full backup end to high in the clouds;
Step 29, sends to file change detection module and activates message, and file change detects and becomes running status from halted state.
3. the computer data intelligent backup method as described in claim 1, is characterized in that, user class rule and system class rule in described step 4, is characterized in that:
User class rule at least comprises: consumer process exclusionary rules, consumer process directory name exclusionary rules, file name exclusionary rules; System class rule at least comprises: system process comprises rule;
Consumer process exclusionary rules matching condition: process title;
Consumer process directory name exclusionary rules matching condition: consumer process name and the comspec of catalogue;
File name exclusionary rules matching condition: the comspec of file;
System process comprises rule match conditions: process title.
4. the computer data intelligent backup method as described in claim 1, is characterized in that, described step 5 is further:
Step 41, wait-receiving mode file change event message, comprises document creation, file is write, file moves, go to step 42 after receiving file change event message;
Step 42, searches in delta file list, if certain file full path name is identical with the file full path name of current file change events message, then thinks that this file change events is repeated events, goes to step 41, otherwise go to step 43;
Step 43, compares process title and whether belongs to system user, if so, is then system process, goes to step 44, if not, go to step 45;
Step 44, compares process title and whether mates certain system process and comprise rule, if coupling, then thinks that this file change events belongs to backup scope, goes to step 46, otherwise go to step 41;
Step 45, is written to delta file list, goes to step 41 by file full path name;
Whether step 46, compare process title and mate with certain consumer process exclusionary rules, if coupling, then think that this file change is not within the scope of backup, goes to step 41, otherwise goes to step 47;
Step 47, compares change file directory name and whether process title mates certain consumer process directory name exclusionary rules, if coupling, then thinks that this file change is not within the scope of backup, goes to step 41, otherwise goes to step 48;
Step 48, compares change file full path name and whether mates certain user file name exclusionary rules, if coupling, then think that this file change is not within the scope of backup, goes to step 41, otherwise goes to step 45.
5. the computer data intelligent backup method as described in claim 1, is characterized in that, described step 7 is further:
Step 51, travels through each delta file comspec, obtains the file label of delta file place volume, if not this file label in the list of increment volume, then write increases the list of standby volume, otherwise does not write;
Step 52, judges that whether increase the list of standby volume is empty, as empty, then go to step 56, otherwise goes to step 53;
Step 53, selects one to increase standby volume, generates the snapshot of the standby volume of this increasing in the list of increasing standby volume;
Step 54, the list of traversal delta file, finds the delta file comspec belonging to this increment volume, and the snapshot of the standby volume of this increasing reads this delta file, sends delta file, delta file comspec, delta file digest value to high in the clouds;
Step D55, deletes this increasing for volume shadow copy, removes file label, go to step 53 from the list of increasing standby volume;
Step 56, empties delta file list.
6. the computer data intelligent backup method as described in claim 1, is characterized in that, described step 8 is further:
Step 61, rule base update module scanning operating system of user, obtains custom system feature, obtains present system time;
Step 62, sends custom system characteristic sum present system time to high in the clouds;
Step 63, responds if do not receive high in the clouds, then goes to step 67, otherwise go to step 64;
Step 64, the rule base version returned in high in the clouds and current version compare, and as changed, go to step 65, otherwise go to step 66;
Step 65, downloads new rule base from high in the clouds;
Step 66, latency period P step, goes to step 61;
Step 67, latency period Q step, goes to step 61.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510123310.7A CN104714864A (en) | 2015-03-20 | 2015-03-20 | Intelligent computer data backup method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510123310.7A CN104714864A (en) | 2015-03-20 | 2015-03-20 | Intelligent computer data backup method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN104714864A true CN104714864A (en) | 2015-06-17 |
Family
ID=53414226
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510123310.7A Pending CN104714864A (en) | 2015-03-20 | 2015-03-20 | Intelligent computer data backup method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104714864A (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105373452A (en) * | 2015-12-11 | 2016-03-02 | 上海爱数信息技术股份有限公司 | Data backup method |
| CN106598785A (en) * | 2016-12-16 | 2017-04-26 | 广东美晨通讯有限公司 | File system backup and restoration method and device |
| CN109522160A (en) * | 2018-11-29 | 2019-03-26 | 上海英方软件股份有限公司 | Compare backup method and system by saving the file information abstract progress file directory |
| WO2020037985A1 (en) * | 2018-08-23 | 2020-02-27 | 华为技术有限公司 | Method and apparatus for calculating backup file size |
| CN111159109A (en) * | 2019-11-26 | 2020-05-15 | 陶壮壮 | Method and system for detecting file occupied by disk space |
| CN112181756A (en) * | 2019-07-04 | 2021-01-05 | 上海泰宇信息技术股份有限公司 | Data monitoring and security method |
| CN115061856A (en) * | 2022-08-16 | 2022-09-16 | 四川大学 | Block-based persistent volume backup method, system, storage medium and recovery method thereof |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101403988A (en) * | 2008-11-05 | 2009-04-08 | 中国科学院计算技术研究所 | File back-up system and method of computer system |
| US20100058010A1 (en) * | 2008-09-04 | 2010-03-04 | Oliver Augenstein | Incremental backup using snapshot delta views |
| CN102521075A (en) * | 2011-12-01 | 2012-06-27 | 浪潮电子信息产业股份有限公司 | Fast and reliable file incremental backup method |
| CN103389925A (en) * | 2012-05-09 | 2013-11-13 | 南京壹进制信息技术有限公司 | Real-time backup method based on process name identification |
| CN103412801A (en) * | 2013-08-09 | 2013-11-27 | 厦门天锐科技有限公司 | Method for file backup based on process identification file |
| CN103995757A (en) * | 2014-05-12 | 2014-08-20 | 浪潮电子信息产业股份有限公司 | Rapid file backup method based on changed file monitoring |
-
2015
- 2015-03-20 CN CN201510123310.7A patent/CN104714864A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100058010A1 (en) * | 2008-09-04 | 2010-03-04 | Oliver Augenstein | Incremental backup using snapshot delta views |
| CN101403988A (en) * | 2008-11-05 | 2009-04-08 | 中国科学院计算技术研究所 | File back-up system and method of computer system |
| CN102521075A (en) * | 2011-12-01 | 2012-06-27 | 浪潮电子信息产业股份有限公司 | Fast and reliable file incremental backup method |
| CN103389925A (en) * | 2012-05-09 | 2013-11-13 | 南京壹进制信息技术有限公司 | Real-time backup method based on process name identification |
| CN103412801A (en) * | 2013-08-09 | 2013-11-27 | 厦门天锐科技有限公司 | Method for file backup based on process identification file |
| CN103995757A (en) * | 2014-05-12 | 2014-08-20 | 浪潮电子信息产业股份有限公司 | Rapid file backup method based on changed file monitoring |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105373452A (en) * | 2015-12-11 | 2016-03-02 | 上海爱数信息技术股份有限公司 | Data backup method |
| CN105373452B (en) * | 2015-12-11 | 2019-02-01 | 上海爱数信息技术股份有限公司 | A kind of data back up method |
| CN106598785A (en) * | 2016-12-16 | 2017-04-26 | 广东美晨通讯有限公司 | File system backup and restoration method and device |
| WO2020037985A1 (en) * | 2018-08-23 | 2020-02-27 | 华为技术有限公司 | Method and apparatus for calculating backup file size |
| CN109522160A (en) * | 2018-11-29 | 2019-03-26 | 上海英方软件股份有限公司 | Compare backup method and system by saving the file information abstract progress file directory |
| CN109522160B (en) * | 2018-11-29 | 2020-05-05 | 上海英方软件股份有限公司 | Method and system for comparing and backing up file directory by saving file information abstract |
| CN112181756A (en) * | 2019-07-04 | 2021-01-05 | 上海泰宇信息技术股份有限公司 | Data monitoring and security method |
| CN111159109A (en) * | 2019-11-26 | 2020-05-15 | 陶壮壮 | Method and system for detecting file occupied by disk space |
| CN115061856A (en) * | 2022-08-16 | 2022-09-16 | 四川大学 | Block-based persistent volume backup method, system, storage medium and recovery method thereof |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104714864A (en) | Intelligent computer data backup method | |
| US10198451B2 (en) | Systems and methods for using metadata to enhance data identification operations | |
| CN102880663B (en) | The optimization of the file of part deduplication | |
| CN101809566B (en) | Efficient file hash identifier computation | |
| US8112464B2 (en) | On-demand access to container file directories | |
| US8478729B2 (en) | System and method for controlling the storage of redundant electronic files to increase storage reliability and space efficiency | |
| KR101626186B1 (en) | Differential file and system restores from peers and the cloud | |
| US9141289B2 (en) | Intelligent data storage utilizing one or more records | |
| US8321482B2 (en) | Selectively modifying files of a container file | |
| US20090228669A1 (en) | Storage Device Optimization Using File Characteristics | |
| CN103460197A (en) | Computer system, file management method and metadata server | |
| CN104462389B (en) | Distributed file system implementation method based on classification storage | |
| CN104408111A (en) | Method and device for deleting duplicate data | |
| CN103037004A (en) | Implement method and device of cloud storage system operation | |
| US7640588B2 (en) | Data processing system and method | |
| EP2291748A2 (en) | Maintenance of exo-file system metadata on removable storage device | |
| US11550913B2 (en) | System and method for performing an antivirus scan using file level deduplication | |
| CN113448946B (en) | Data migration method and device and electronic equipment | |
| CN102142010A (en) | Method and equipment for inputting data to multimedia service database on embedded equipment | |
| US10228961B2 (en) | Live storage domain decommissioning in a virtual environment | |
| EP2973008A1 (en) | Grouping files for optimized file operations | |
| CN109325005A (en) | A kind of data processing method and electronic equipment | |
| CN101872406A (en) | Computer file tracking method | |
| US8370589B1 (en) | System and method for re-use of writeable PPIs | |
| US7974953B1 (en) | System and method for deletion of writeable PPIS |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20150617 |
|
| WD01 | Invention patent application deemed withdrawn after publication |