CN102508735A - Method for backing up and restoring terminal system based on cloud architecture - Google Patents
Method for backing up and restoring terminal system based on cloud architecture Download PDFInfo
- Publication number
- CN102508735A CN102508735A CN2011103048386A CN201110304838A CN102508735A CN 102508735 A CN102508735 A CN 102508735A CN 2011103048386 A CN2011103048386 A CN 2011103048386A CN 201110304838 A CN201110304838 A CN 201110304838A CN 102508735 A CN102508735 A CN 102508735A
- Authority
- CN
- China
- Prior art keywords
- end side
- file
- identification information
- core
- document
- 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
Images
Abstract
The invention provides a method for backing up and restoring a terminal system based on a cloud architecture. The method comprises the following steps of: in the process of backing up, pre-setting a file database on a cloud server, wherein core files included in different operation systems and unique identifier information of the core files, and unique attribute information of different application programs and installation files of the unique attribute information are stored in the file database; then, according to a system backup request of a terminal/ user, obtaining the unique identifier information of the core file of the current operation system of a terminal side and the unique attribute information of the currently installed application program, and sending the unique identifier information and the unique attribute information to the cloud server to be backed up and stored; and determining a corresponding relation between the terminal/user for executing a backup and the core file of the operation system represented by the unique identifier information of the backup and a corresponding relation between the terminal/user for executing the backup and the installation file of the application program represented by the unique attribute information of the installed application program of the backup by the cloud server according to the file database. The method disclosed by the invention is capable of increasing speed for backing up and restoring and reducing transmission quantity.
Description
Technical field
The present invention relates to field of computer technology, relate in particular to a kind of terminal system backup and restoration methods based on the cloud framework.
Background technology
The development of Along with computer technology, the program of in various terminals, installing are also more and more.With regard to personal computer terminal, in general, operating system program and some application programs are installed wherein, the various operational requirements of user are satisfied in the work that cooperatively interacts of these programs.
But after a period of time, because the destruction of virus or the generation of self garbage files, it is more and more slower that a lot of programs can be moved at terminal operating, even owing to file corruption causes and can't normally open or use.To this situation, restoring system backup instruments such as Ghost have appearred, the data full backup of whole subregion come out, in needs, again Backup Data is reverted to former subregion.
But the execution speed of this type of backup and reduction instrument is quite slow; Since its backup principle is by the sector with the backup of former data clone, write back whole Backup Data is intact again when recovering reduction, therefore; Not only require bigger storage space; And very consuming time, if apply to based on network storage backup, then the data volume of its transmission is quite big.
On the other hand; The performed backup-and-restore operation of present backup and reduction instrument all is that comparison machinery is mechanical, just as taking a picture, duplicates out with what former data file was kept intact fully; And reduction is gone back; Do not consider the compositing characteristic and the operation characteristic of program self, even if before the backup because long-time running causes the garbage files or the harmful file that exist, still can be loyal with its backup preservation; And after these cause garbage files or harmful file of program run obstacle to restore go back to the terminal, still can cause program run not smooth.
Summary of the invention
It is a kind of that technical matters to be solved by this invention is to provide, and overcome under the prior art backup and the speed recovered is slow and can not improve the problem of program feature.
For solving the problems of the technologies described above, the present invention provides a kind of terminal system backup method based on the cloud framework, comprising:
Server presets a document data bank beyond the clouds, stores core document and uniqueness identification information thereof that different operating system comprises, and stores the uniqueness attribute information of different application and file is installed;
According to the system backup request of terminal/subscriber, obtain the uniqueness identification information of the core document of end side current operation system, and the uniqueness attribute information of current mounted application program, and be sent to high in the clouds server backup storage;
Corresponding relation between said high in the clouds server is confirmed this execution backup according to said document data bank terminal/subscriber and the operating system kernel file of the uniqueness identification information representative of said backup, and and the application program installation file of the uniqueness attribute information representative of the mounted application program of backup between corresponding relation.
The present invention and then a kind of terminal system restoration methods based on the cloud framework also is provided comprises:
According to the recovery request of terminal/subscriber, said high in the clouds server is confirmed the uniqueness identification information of the core document of the operating system that this terminal/subscriber has backed up, and the uniqueness attribute information of mounted application program;
The current uniqueness identification information of the uniqueness identification information of the core document of the operating system at this terminal that the high in the clouds server side has been backed up and the file of end side local operation system matees;
To mate unsuccessful current uniqueness identification information corresponding file deletion in end side, and will mate unsuccessful uniqueness identification information corresponding file by the high in the clouds server side and be sent to this end side corresponding stored;
, use corresponding installation file to carry out and install according to the said uniqueness attribute information that has backed up by the high in the clouds server in end side in the mounted application program of end side,
Wherein, said high in the clouds server presets a document data bank, stores core document and uniqueness identification information thereof that different operating system comprises, and stores the uniqueness attribute information of different application and file is installed.
Use the present invention,, only need the characteristic information of transfer files owing to do not need the transfer entity file; Therefore, the speed that can greatly improve backup and recover reduces volume of transmitted data; And when recovering owing to be based on diversity ratio recovery, characteristic information does not have the file of difference then not need to recover before and after backup, discrepant just the needs recovers; Therefore not only resume speed is fast, and the deletion of garbage files that can end side is harmful, promotes program feature.
Description of drawings
Fig. 1 is according to the described a kind of terminal system backup method process flow diagram based on the cloud framework of the embodiment of the invention.
Fig. 2 is that described backup concerns synoptic diagram according to the embodiment of the invention.
Fig. 3 is the process flow diagram according to the uniqueness identification information of the core document of the described operating system program that obtains desire backup in end side of the embodiment of the invention.
Fig. 4 is according to the described a kind of terminal system restoration methods process flow diagram based on the cloud framework of the embodiment of the invention.
Embodiment
Below in conjunction with accompanying drawing, embodiments of the invention are elaborated.
As shown in Figure 1, for according to the described a kind of terminal system backup method process flow diagram of the embodiment of the invention, comprise the steps: based on the cloud framework
Step 101: server presets a document data bank beyond the clouds, stores core document and uniqueness identification information thereof that different operating system comprises, and stores the uniqueness attribute information of different application and file is installed;
Step 102: according to the system backup request of terminal/subscriber, obtain the uniqueness identification information of the core document of end side current operation system, and the uniqueness attribute information of current mounted application program, and be sent to high in the clouds server backup storage;
Step 103: the corresponding relation between said high in the clouds server is confirmed this execution backup according to said document data bank terminal/subscriber and the operating system kernel file of the uniqueness identification information representative of said backup, and and the application program installation file of the uniqueness attribute information representative of the mounted application program of backup between corresponding relation.
In addition, further store the initial registration list file of different operating system in the said document data bank; Said high in the clouds server is confirmed the terminal/subscriber of this execution backup and the corresponding relation between the initial registration list file according to said document data bank.
The notion of high in the clouds server; Sizable development and utilization have been obtained at present; For example, for the foundation in virus characteristic storehouse, can be arranged at the high in the clouds server; Client only need be uploaded the local file characteristic and can compare with the virus characteristic in the server of high in the clouds, thus utilization blacklist killing virus.
In like manner, embodiments of the invention preset a document data bank in the server beyond the clouds, store the core document of the running program of different classes of different editions, and the uniqueness identification information of core document, and the installation file of different application.
Through long-term accumulation, server can be set up a huge document data bank that comprises numerous common programs files beyond the clouds, and operating system more commonly used and the application program that some are commonly used can be included in wherein.
And through actual analysis, be the scope that can know its original core document of various running programs.Said core document can be the original document that this running program is discharging in the terminal after the installation; Or those keep the requisite master file of operating system; Perhaps also can be meant the general character file that still keeps same content after those same operating system programs are installed in different terminals and move a period of time.
The scope of core document is selected, and can confirm according to different operating system program and different backup requests.Obviously, the scope of the core document of backup is big more, the appearance attitude when then back up at the also faithful to more terminal of the program after the reduction; And the scope of the core document of backup is more little, and then the backed up data amount is more little, and the program after the reduction is more near the initial appearance attitude of this operating system program after installation.But clearly, those some garbage files that possibly after program run a period of time, produced or can be comprised in the core document by some harmful files that rogue program injected such as viruses.
The same operation system program in running on different terminals, the content major part of its core document is identical, and the file that is damaged is minority after all, and therefore, this just provides the foundation for multiplexing high in the clouds file data library file.
Store the core document that various operating system program comprises in the document data bank in the server of high in the clouds, and the uniqueness identification information of said core document.The MD5 value that signing messages that said uniqueness identification information can be this document or calculating obtain etc.
Owing to run on the core document that same operating system program comprised in the terminal, if be not destroyed, then its signing messages be with the high in the clouds database in the signing messages of this core document be consistent.Therefore; The signing messages of this core document of this operating system program in the terminal is stored in server side; Just can play this core document is backed up in the identical purpose of server side, be pre-stored in database and suffered because have the identical core document of same signature information.Only for the inconsistent core document of those signing messages, just need be by the actual middle storage that uploads onto the server of this end side.
So; The uniqueness identification information of core document that the operating system program of backup only need be uploaded in this terminal has just been accomplished the work of backup operation system, and the high in the clouds server promptly can confirm which the operating system kernel file of this terminal backup is according to this uniqueness identification information.
As shown in Figure 2; In terminal 201, moving the operating system program 1 of desire backup, it includes core document 1, core document 2, core document 3, and garbage files 4; Corresponding uniqueness signing messages is file signature 1, file signature 2 and file signature 3, and file signature 4.In server 202 data-base recording the core document 1 of operating system program 1, core document 2 and core document 3, corresponding uniqueness signing messages is file signature 1, file signature 2 and file signature 3.And only need write down file signature 1, file signature 2 and the file signature 3 of the operating system program 1 of this terminal or ID 201 and backup in the content of server side backup.Clearly, terminal backed up data content seldom but is enough to confirm the routine data that this terminal need be backed up at server side.And because backup all is the core document of program, the garbage files that some are possible forecloses, and this has not only reduced backup data quantity, and after recovery, can reduce a clean program.
Said end side can be according to the core document title of the operating system program of this desire backup of writing down in the rule list that presets, and obtains the uniqueness identification information of core document of the operating system program of desire backup.This rule list can be that end side carries, the original document that this program discharged that for example when this operating system program is carried out installation, writes down in end side; Or through the tabulation of end of scan local file, ask for to server end according to program name and version, server end then stores the core document rule list of numerous common programs.Can control the range size of core document through this rule list flexibly.
In addition; Can also directly utilize the described document data bank of the embodiment of the invention to confirm core document; As shown in Figure 3, the process flow diagram for according to the uniqueness identification information of the core document of the described operating system program that obtains desire backup in end side of the embodiment of the invention comprises:
Step 301: end side is sent to the high in the clouds server with the uniqueness attribute information of current operation system;
Step 302: said high in the clouds server is confirmed the core document that this operating system and institute's correspondence thereof comprise according to the uniqueness attribute information of the different operating system of document data bank record, and the title of core document is sent to this end side;
Step 303: said end side is according to the uniqueness identification information of the core document of the name acquiring current operation system of said core document.
Title that wherein said uniqueness attribute information can be this operating system program and version number or program ID etc. can be unique the information of confirming this program object.
According to embodiments of the invention; If said high in the clouds server can't be confirmed the corresponding core document of uniqueness identification information with said end side transmission in said document data bank; The signing messages of signing messages and this core document in the server side database that this core document of end side then is described is inconsistent; It might be the personality file of being crossed by user's modification, at this moment can the local core document corresponding with this uniqueness identification information be sent to high in the clouds server backup storage by said end side.
In addition, can also define the non-core file of some these operating system programs, for example the file of some static configuration; Or the file of user data, although, possibly write down user's use habit because these files do not influence the operation of program; Therefore, also can when backup, extract.Like this, can obtain the current non-core file of the program of said desire backup, and be sent to high in the clouds server backup storage by said end side.The uniqueness identification information of the non-core file of perhaps further acquisition is back-up storage in the lump.The form of confirming to take equally rule list of non-core file.
For most program; Its file that back release is installed all can be under same directory path; That is to say that its relative position relation is unimportant, but for some comparatively complicated program, for example operating system program; Possibly be nested with the situation of multilayer catalogue, at this moment can the relative position relation information between the core document be stored in the document data bank; Also can be the relative position relation information between the core document of said desire stand-by program to be sent to the high in the clouds server stores by said end side.
Equally, concerning non-core file, end side also can be sent to the high in the clouds server stores with the relative position relation between current core document and the non-core file.
And for the set up applications of end side; Only need the uniqueness attribute information of this application program of backup, for example get final product for the title of this application program and version number or ID number, owing in the server side document data bank, store the uniqueness attribute information of different application and file is installed; Therefore; Through knowing the uniqueness attribute information of end side backup, can confirm corresponding installation file, so that use when recovering.
As shown in Figure 4, for according to the described a kind of terminal system restoration methods process flow diagram of the embodiment of the invention, comprising based on the cloud framework:
Step 401: according to the recovery request of terminal/subscriber, said high in the clouds server is confirmed the uniqueness identification information of the core document of the operating system that this terminal/subscriber has backed up, and the uniqueness attribute information of mounted application program;
Step 402: the current uniqueness identification information of the uniqueness identification information of the core document of the operating system at this terminal that the high in the clouds server side has been backed up and the file of end side local operation system matees;
Step 403: will mate unsuccessful current uniqueness identification information corresponding file deletion in end side, and will mate unsuccessful uniqueness identification information corresponding file by the high in the clouds server side and be sent to this end side corresponding stored;
Step 404:, use corresponding installation file to carry out and install according to the said uniqueness attribute information that has backed up by the high in the clouds server in end side in the mounted application program of end side,
Wherein, said high in the clouds server presets a document data bank, stores core document and uniqueness identification information thereof that different operating system comprises, and stores the uniqueness attribute information of different application and file is installed.
Can also further store the initial registration list file of different operating system in the said document data bank; Use corresponding installation file before the installation of end side executive utility in step 404, then may further include: the initial registration list file of storing in the document data bank corresponding with end side operating system is sent to the end side corresponding stored by the high in the clouds server.
If comprise registry file in the core document of when backup, selecting; So; Because the personalization of registry file is quite strong, often after operation a period of time, will produce difference, like this with initial registry file; In when backup because the uniqueness identification information of the uniqueness identification information of end side registry file and the core document in the document data bank is different; Can't confirm in the document data bank corresponding core document in view of the above, therefore will require the end side registry file back-up storage that uploads onto the server, and when recovering with its end side of redispatching back.
But because the registration table of this end side possibly include junk data when backup, if again its former state is recovered the improvement that can not bring performance; Therefore; Can in document data bank, further store the initial clean registry data of this operating system, when recovering, again these initial registration table data are sent to end side after can the file of operating system being recovered; Replace its current registry data; Like this, just can bring a clean registry file for end side, and set up applications on this basis.
Further, just do not comprise registry file in the core document that can when backup, select, but the initial registration table is used in unification when recovering, and then can back up faster and recover, and brings the performance recovery of operating system simultaneously.
The high in the clouds server just can be known the active user according to the user login information of end side, also just can know the data that this user once backed up.For most of terminal/subscriber, after receiving its recovery request, server just can be confirmed the uniqueness identification information that this user ID is crossed.As shown in Figure 2; Core document in the signing messages-database that writes down in the core document signing messages-high in the clouds document data bank of the operating system program-end side core document of user terminal-end side backup and signing messages thereof-backed up, these corresponding relations all are linked to each other through the uniqueness identification information.
When recovering, the uniqueness identification information of the core document of this operating system that can the high in the clouds server side have been backed up matees with the current uniqueness identification information of all files of this corresponding program in end side this locality.So; End side need not confirmed the scope of operating system kernel file; Every and the inconsistent local program file of signing messages that backed up all can be deleted, comprise more local garbage files relevant with this program and because file is impaired or revise after cause the file of signing messages variation; And at server side; The signing messages that has backed up representative that can successful match is excellent in the end side respective file; And the signing messages of backup that can't successful match representes that the end side original has changed, and this just need utilize the respective file in the document data bank to be sent to the end side storage.Because because can't successful match and deleted, therefore, the respective file in the database just be sent to end side and have replaced original this original that has changed.Because it is visible; It is right that the reset mode of the embodiment of the invention is based on aspect ratio; The file that has only signing messages to change just needs reality to be sent to the terminal from server; This with regard to very big reduction volume of transmitted data, and deleted the garbage files that end side produces in program operation process, improved the terminal system performance.
When recovering, can also be that the uniqueness identification information of the core document of operating system program that the high in the clouds server side has been backed up matees with the current uniqueness identification information of the core document of this corresponding program in end side this locality.
And for the step that the uniqueness identification information between the core document matees, can be to carry out by end side, also can be to carry out by server side.
For example, can the uniqueness identification information of the core document of the said system program of backup operation be sent to end side by the high in the clouds server; Then, end side is mated the uniqueness identification information of the core document that receives with the current uniqueness identification information of the core document of local corresponding program.
The current uniqueness identification information of the core document of the operating system program that perhaps, desire is recovered by end side is sent to the high in the clouds server; The uniqueness identification information of the core document of this operating system program that had been backed up by this terminal of the said current uniqueness identification information that will be received by said high in the clouds server then, and storage matees.
The coupling of only carrying out between the core document can reduce the scope of end side deleted file, thereby can keep the end side personality file more accurately, and the reduction of inclusive NAND core document complements one another.
If also back up the non-core file of operating system at server side, the non-core file of this operating system program that then can be further end side have been backed up by the high in the clouds server is sent to the end side corresponding stored.
If the high in the clouds server backup non-core file with and corresponding uniqueness identification information; The uniqueness identification information of the non-core file of this operating system program that then can the high in the clouds server side have been backed up matees with the current uniqueness identification information of the file of the local corresponding program of this end side; If coupling is consistent; Then supporting paper is intact, does not need replacement, if mate inconsistent; Then can end side be mated unsuccessful non-core file delete, and the unsuccessful non-core file of coupling that again server side is backed up is sent to the end side corresponding stored.
And for the store path of program file in end side; Can store according to the default installation path; Also can know the installation path of this program through the News Search technology in end side, in fact, generally as long as end side has a core document just can know the installation path of this program.
In addition, said end side can also be stored core document according to the relative position relation between the said core document of server record beyond the clouds; Or according to the said non-core file of server record and the relative position relation between the core document are stored non-core file beyond the clouds.
At some in particular cases; If do not find said corresponding program at said terminal; Then the description operation system possibly be replaced, at this moment can be with in the server of said high in the clouds, being sent to this end side corresponding stored with the corresponding core document of uniqueness identification information that has backed up.
In addition, when recovering,, be the title that to confirm the core document of the corresponding program in said this locality according to a presetting rule table equally if end side need be known the core document scope of this program; Or confirm said local corresponding core document title according to the core document title of the said program that writes down in the document data bank in the server of said high in the clouds.
And for the recovery of application program; Utilize the installation file in the server side document data bank to cover installation exactly local execution of end side; Perhaps earlier the configuration file and the user data of this application program are preserved in this locality; And then carry out and install, again configuration file and user data correspondence are reduced after the installation.
This shows that the present invention be owing to the time only need back up the characteristic information of current system in backup, and need not actual backup file content, therefore, backup rate is very fast, and data quantity transmitted significantly reduces; Simultaneously, be based on diversity ratio recovery during recovery, if promptly the signature identification of core document does not change; Then need not recover this document, that has only that signature identification changes just need download corresponding document from database, therefore; The speed of recovering is also very fast, and transmission quantity seldom.Simultaneously, owing to be based on diversity ratio recovery, therefore, harmful files such as garbage files that file extent during with backup or content there are differences can be eliminated, and after recovery, have promoted program feature.
Claims (27)
1. the terminal system backup method based on the cloud framework is characterized in that, comprising:
Server presets a document data bank beyond the clouds, stores core document and uniqueness identification information thereof that different operating system comprises, and stores the uniqueness attribute information of different application and file is installed;
According to the system backup request of terminal/subscriber, obtain the uniqueness identification information of the core document of end side current operation system, and the uniqueness attribute information of current mounted application program, and be sent to high in the clouds server backup storage;
Corresponding relation between said high in the clouds server is confirmed this execution backup according to said document data bank terminal/subscriber and the operating system kernel file of the uniqueness identification information representative of said backup, and and the application program installation file of the uniqueness attribute information representative of the mounted application program of backup between corresponding relation.
2. the method for claim 1 is characterized in that, further stores the initial registration list file of different operating system in the said document data bank; Said high in the clouds server is confirmed the terminal/subscriber of this execution backup and the corresponding relation between the initial registration list file according to said document data bank.
3. the method for claim 1 is characterized in that, said end side is obtained the uniqueness identification information of the core document of current operation system according to the core document title of the current operation system that writes down in the rule list that presets.
4. the method for claim 1 is characterized in that, the step of the uniqueness identification information of the said core document that obtains the end side current operation system comprises:
End side is sent to the high in the clouds server with the uniqueness attribute information of current operation system;
Said high in the clouds server is confirmed the core document that this operating system and institute's correspondence thereof comprise according to the uniqueness attribute information of the different operating system of document data bank record, and the title of core document is sent to this end side;
Said end side is according to the uniqueness identification information of the core document of the name acquiring current operation system of said core document.
5. the method for claim 1 is characterized in that, further comprises:
If said high in the clouds server can't be confirmed the core document of this operating system corresponding with the uniqueness identification information of said end side transmission in said document data bank, then the local core document corresponding with this uniqueness identification information is sent to high in the clouds server backup storage by said end side.
6. the method for claim 1 is characterized in that, further comprises:
Obtain the current non-core file of this operating system by said end side, and be sent to high in the clouds server backup storage.
7. the method for claim 1 is characterized in that, further comprises:
Obtain the current non-core file and the corresponding uniqueness identification information of this operating system by said end side, and be sent to the high in the clouds server stores.
8. the method for claim 1 is characterized in that, the relative position relation information between the core document that further stores different operating system in the said document data bank and comprised.
9. the method for claim 1 is characterized in that, said end side is sent to the high in the clouds server stores with the relative position relation information between the core document of this operating system.
10. like claim 6 or 7 described methods, it is characterized in that, further comprise: said end side is sent to the high in the clouds server stores with the current core document of this operating system and the relative position relation between the non-core file.
11. method as claimed in claim 4 is characterized in that, the uniqueness attribute information of said operating system comprises the title and the version number of this operating system.
12. the method for claim 1 is characterized in that, the uniqueness attribute information of said application program comprises the title and the version number of this application program
13., it is characterized in that the uniqueness identification information of said file comprises the signing messages of this document like claim 1 or 7 described methods.
14. the terminal system restoration methods based on the cloud framework is characterized in that, comprising:
According to the recovery request of terminal/subscriber, said high in the clouds server is confirmed the uniqueness identification information of the core document of the operating system that this terminal/subscriber has backed up, and the uniqueness attribute information of mounted application program;
The current uniqueness identification information of the uniqueness identification information of the core document of the operating system at this terminal that the high in the clouds server side has been backed up and the file of end side local operation system matees;
To mate unsuccessful current uniqueness identification information corresponding file deletion in end side, and will mate unsuccessful uniqueness identification information corresponding file by the high in the clouds server side and be sent to this end side corresponding stored;
, use corresponding installation file to carry out and install according to the said uniqueness attribute information that has backed up by the high in the clouds server in end side in the mounted application program of end side,
Wherein, said high in the clouds server presets a document data bank, stores core document and uniqueness identification information thereof that different operating system comprises, and stores the uniqueness attribute information of different application and file is installed.
15. method as claimed in claim 14 further stores the initial registration list file of different operating system in the said document data bank; Use corresponding installation file before the installation steps of end side executive utility said, further comprise: the initial registration list file of storing in the document data bank corresponding with end side operating system is sent to the end side corresponding stored by the high in the clouds server.
16. method as claimed in claim 14; It is characterized in that; Said coupling step comprises: the current uniqueness identification information of the uniqueness identification information of the core document of the said operating system that the high in the clouds server side has been backed up and all files of this end side local operation system matees.
17. method as claimed in claim 14; It is characterized in that; Said coupling step comprises: the current uniqueness identification information of the uniqueness identification information of the core document of the said operating system that the high in the clouds server side has been backed up and the core document of this end side local operation system matees.
18. method as claimed in claim 17 is characterized in that, said coupling step comprises:
The high in the clouds server is sent to end side with the uniqueness identification information of the said operating system kernel file that has backed up;
The current uniqueness identification information of the core document that the uniqueness identification information of the operating system kernel file that has backed up that end side will receive is corresponding with the local operation system matees.
19. method as claimed in claim 17 is characterized in that, said coupling step comprises:
By end side the current uniqueness identification information of the core document of local operation system is sent to the high in the clouds server;
The uniqueness identification information of the core document that had been backed up by this terminal of the said current uniqueness identification information that will be received by said high in the clouds server and storage matees.
20. method as claimed in claim 14 is characterized in that, further comprises:
By the high in the clouds server the non-core file of operating system that end side has backed up is sent to the end side corresponding stored.
21. method as claimed in claim 14; It is characterized in that; Said coupling step further comprises: the current uniqueness identification information of the uniqueness identification information of the non-core file of operating system that the high in the clouds server side has been backed up and the file of this end side local operation system matees.
22. method as claimed in claim 14; It is characterized in that; Said high in the clouds server will mate the step that unsuccessful uniqueness identification information corresponding file is sent to the end side corresponding stored, comprise: said end side is stored core document according to the relative position relation between the said core document of server record beyond the clouds.
23., it is characterized in that said end side is according to the said non-core file of server record and the relative position relation between the core document are stored non-core file beyond the clouds like claim 20 or 21 described methods.
24. method as claimed in claim 17 is characterized in that, said end side is confirmed the title of the core document of said local operation system according to a presetting rule table.
25. method as claimed in claim 17 is characterized in that, said end side is confirmed said local respective operations system core file name according to the core document title of the said operating system that writes down in the document data bank in the server of said high in the clouds.
26., it is characterized in that the uniqueness identification information of said file comprises the signing messages of this document like claim 14 or 20 described methods.
27. method as claimed in claim 14 is characterized in that, the uniqueness attribute information of said application program comprises the title and the version number of application program.
Priority Applications (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2011103048386A CN102508735A (en) | 2011-09-30 | 2011-09-30 | Method for backing up and restoring terminal system based on cloud architecture |
| US14/347,274 US10108501B2 (en) | 2011-09-30 | 2012-09-26 | Terminal backup and recovery method |
| PCT/CN2012/081984 WO2013044794A1 (en) | 2011-09-30 | 2012-09-26 | Terminal backup and recovery method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2011103048386A CN102508735A (en) | 2011-09-30 | 2011-09-30 | Method for backing up and restoring terminal system based on cloud architecture |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102508735A true CN102508735A (en) | 2012-06-20 |
Family
ID=46220827
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2011103048386A Pending CN102508735A (en) | 2011-09-30 | 2011-09-30 | Method for backing up and restoring terminal system based on cloud architecture |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102508735A (en) |
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2013044794A1 (en) * | 2011-09-30 | 2013-04-04 | 北京奇虎科技有限公司 | Terminal backup and recovery method |
| CN103246510A (en) * | 2013-04-23 | 2013-08-14 | 北京小米科技有限责任公司 | Method and device for system replication and restoration |
| CN103544409A (en) * | 2012-07-11 | 2014-01-29 | 腾讯科技（深圳）有限公司 | Method for controlling application program, use equipment and server |
| CN103679029A (en) * | 2013-12-11 | 2014-03-26 | 北京奇虎科技有限公司 | Method and device for repairing cheap-copy application programs |
| CN103685342A (en) * | 2012-08-31 | 2014-03-26 | 百度在线网络技术（北京）有限公司 | Personal cloud data storage center and cloud data storage method |
| CN104168309A (en) * | 2014-07-24 | 2014-11-26 | 深圳天珑无线科技有限公司 | Data backup and operation method based on cloud service |
| CN104881335A (en) * | 2015-03-16 | 2015-09-02 | 广东欧珀移动通信有限公司 | Backup application restoration method and terminal |
| WO2016033929A1 (en) * | 2014-09-03 | 2016-03-10 | 惠州Tcl移动通信有限公司 | Cloud data backup and recovery method |
| CN105635201A (en) * | 2014-10-29 | 2016-06-01 | Tcl集团股份有限公司 | Application starting method and application starting system based on pushed information |
| CN105630637A (en) * | 2016-02-14 | 2016-06-01 | 北京艾森思科技有限公司 | Software backup method, software backup terminal, software recovery method and software recovery terminal |
| CN106027602A (en) * | 2016-04-29 | 2016-10-12 | 乐视控股（北京）有限公司 | Cloud backup and restoration methods and terminal backup and restoration devices for applications |
| CN106528337A (en) * | 2016-10-25 | 2017-03-22 | 广东欧珀移动通信有限公司 | Backup method, device and system of data |
| CN106713507A (en) * | 2017-02-22 | 2017-05-24 | 上海斐讯数据通信技术有限公司 | Management method and management system for batches of cloud terminal devices |
| CN106790581A (en) * | 2016-12-28 | 2017-05-31 | 深圳天珑无线科技有限公司 | Application data processing method, device and terminal |
| CN109298973A (en) * | 2018-09-28 | 2019-02-01 | 联想(北京)有限公司 | A kind of information recovering method and electronic equipment |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1838083A (en) * | 2005-03-21 | 2006-09-27 | 微软公司 | System and method of efficient data backup in a networking environment |
| CN101324858A (en) * | 2008-07-10 | 2008-12-17 | 宇龙计算机通信科技(深圳)有限公司 | Method, system and terminal for recovering data |
| CN102141953A (en) * | 2011-04-01 | 2011-08-03 | 奇智软件（北京）有限公司 | Method and device for showing progress bar |
-
2011
- 2011-09-30 CN CN2011103048386A patent/CN102508735A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1838083A (en) * | 2005-03-21 | 2006-09-27 | 微软公司 | System and method of efficient data backup in a networking environment |
| CN101324858A (en) * | 2008-07-10 | 2008-12-17 | 宇龙计算机通信科技(深圳)有限公司 | Method, system and terminal for recovering data |
| CN102141953A (en) * | 2011-04-01 | 2011-08-03 | 奇智软件（北京）有限公司 | Method and device for showing progress bar |
Cited By (22)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2013044794A1 (en) * | 2011-09-30 | 2013-04-04 | 北京奇虎科技有限公司 | Terminal backup and recovery method |
| CN103544409A (en) * | 2012-07-11 | 2014-01-29 | 腾讯科技（深圳）有限公司 | Method for controlling application program, use equipment and server |
| CN103685342A (en) * | 2012-08-31 | 2014-03-26 | 百度在线网络技术（北京）有限公司 | Personal cloud data storage center and cloud data storage method |
| CN103685342B (en) * | 2012-08-31 | 2018-01-09 | 百度在线网络技术（北京）有限公司 | The method of personal cloud storage data center and cloud data storage |
| CN103246510B (en) * | 2013-04-23 | 2016-12-28 | 小米科技有限责任公司 | A kind of method and apparatus carrying out system copies and reduction |
| CN103246510A (en) * | 2013-04-23 | 2013-08-14 | 北京小米科技有限责任公司 | Method and device for system replication and restoration |
| CN103679029A (en) * | 2013-12-11 | 2014-03-26 | 北京奇虎科技有限公司 | Method and device for repairing cheap-copy application programs |
| CN104168309A (en) * | 2014-07-24 | 2014-11-26 | 深圳天珑无线科技有限公司 | Data backup and operation method based on cloud service |
| WO2016011825A1 (en) * | 2014-07-24 | 2016-01-28 | 深圳天珑无线科技有限公司 | Cloud-service-based data backup and operation method |
| US9979784B2 (en) | 2014-09-03 | 2018-05-22 | Huizhou Tcl Mobile Communication Co., Ltd. | Method for cloud data backup and recovery |
| WO2016033929A1 (en) * | 2014-09-03 | 2016-03-10 | 惠州Tcl移动通信有限公司 | Cloud data backup and recovery method |
| CN105635201A (en) * | 2014-10-29 | 2016-06-01 | Tcl集团股份有限公司 | Application starting method and application starting system based on pushed information |
| CN104881335B (en) * | 2015-03-16 | 2019-06-18 | Oppo广东移动通信有限公司 | A kind of back-up application restoring method and terminal |
| CN104881335A (en) * | 2015-03-16 | 2015-09-02 | 广东欧珀移动通信有限公司 | Backup application restoration method and terminal |
| CN105630637A (en) * | 2016-02-14 | 2016-06-01 | 北京艾森思科技有限公司 | Software backup method, software backup terminal, software recovery method and software recovery terminal |
| CN106027602A (en) * | 2016-04-29 | 2016-10-12 | 乐视控股（北京）有限公司 | Cloud backup and restoration methods and terminal backup and restoration devices for applications |
| CN106528337A (en) * | 2016-10-25 | 2017-03-22 | 广东欧珀移动通信有限公司 | Backup method, device and system of data |
| CN106528337B (en) * | 2016-10-25 | 2020-04-10 | Oppo广东移动通信有限公司 | Data backup method, device and system |
| CN106790581A (en) * | 2016-12-28 | 2017-05-31 | 深圳天珑无线科技有限公司 | Application data processing method, device and terminal |
| CN106713507A (en) * | 2017-02-22 | 2017-05-24 | 上海斐讯数据通信技术有限公司 | Management method and management system for batches of cloud terminal devices |
| CN106713507B (en) * | 2017-02-22 | 2020-01-14 | 上海斐讯数据通信技术有限公司 | Management method and management system for batch cloud terminal equipment |
| CN109298973A (en) * | 2018-09-28 | 2019-02-01 | 联想(北京)有限公司 | A kind of information recovering method and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102508735A (en) | Method for backing up and restoring terminal system based on cloud architecture | |
| CN102495772B (en) | Characteristic-based terminal program cloud backup and recovery methods | |
| CN102495771A (en) | Terminal object classified backup and recovery methods based on cloud architecture | |
| CN102360320A (en) | Terminal backup object sharing and recovery method based on cloud architecture | |
| CN102360321A (en) | Terminal program quick backup and recovery method based on cloud architecture | |
| US20200264775A1 (en) | Serverless solution for continuous data protection | |
| CN102594849B (en) | Data backup and recovery method and device, virtual machine snapshot deleting and rollback method and device | |
| US10146630B1 (en) | Block changes framework for delta file incremental backup | |
| US11907078B2 (en) | Data backup method, apparatus, and system | |
| JP2017084332A (en) | Method and apparatus for creating system disk snapshot of virtual machine | |
| US8738870B1 (en) | Block based backup | |
| US20210208982A1 (en) | Data disaster recovery method and site | |
| US10108501B2 (en) | Terminal backup and recovery method | |
| CN103034566A (en) | Method and device for restoring virtual machine | |
| CN103473277A (en) | Snapshot method and device for file systems | |
| EP2628085B1 (en) | Item level recovery | |
| CN104461773A (en) | Backup deduplication method of virtual machine | |
| CN103179153A (en) | Mobile terminal and mobile terminal data backup method based on cloud server | |
| US11669404B2 (en) | Efficient access-based reallocation of backup data within an object storage | |
| US8898407B1 (en) | Incremental block based backup | |
| CN103530202A (en) | Cloud backing-up and recovering method used for terminal program | |
| US9483358B1 (en) | Synthetic block based backup | |
| US10620883B1 (en) | Multi-format migration for network attached storage devices and virtual machines | |
| CN103500127A (en) | Terminal program cloud backup and recovery method | |
| US20230401176A1 (en) | Storage tiering for computing system snapshots |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20120620 |
|
| RJ01 | Rejection of invention patent application after publication |