CN102495771A - Terminal object classified backup and recovery methods based on cloud architecture - Google Patents
Terminal object classified backup and recovery methods based on cloud architecture Download PDFInfo
- Publication number
- CN102495771A CN102495771A CN2011103048244A CN201110304824A CN102495771A CN 102495771 A CN102495771 A CN 102495771A CN 2011103048244 A CN2011103048244 A CN 2011103048244A CN 201110304824 A CN201110304824 A CN 201110304824A CN 102495771 A CN102495771 A CN 102495771A
- Authority
- CN
- China
- Prior art keywords
- backup
- file
- characteristic information
- end side
- 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
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides terminal object classified backup and recovery methods based on a cloud architecture. During backup, a user interface is arranged at a terminal, and different backup classes are provided according to a preset display policy and can be selected by a user, wherein the different backup classes comprise different backup objects; and according to the backup classes and the backup objects which are selected by the user, terminal files which correspond to the backup objects are backed up on a cloud server at the terminal according to the preset display policy. During recovery, according to recovery classes and recovery objects which are selected by the user, files which are backed up by the terminal or the user and correspond to the backup objects are determined on the cloud server; and according to a preset recovery policy, corresponding recovery is performed at the terminal by using the backup files. By the invention, classified backup and recovery methods are provided, and backup and recovery speeds are improved.
Description
Technical field
The present invention relates to field of computer technology, relate in particular to a kind of terminal object class 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 existing backup tool does not all provide the function of classification backup, and the user can't back up the part of paying close attention to separately; And execution speed 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 based on the terminal object class backup of cloud framework and the method for recovering that technical matters to be solved by this invention is to provide, to overcome that prior art can not provide classification backup and 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, a kind of terminal object class backup method based on the cloud framework of the present invention comprises:
In end side one user interface is provided, to provide different backup classifications to supply the user to select according to the preset strategy of showing, wherein different backup classifications comprise different backup objects;
Backup classification and the object selected according to the user, end side according to preset backup policy with the pairing terminal document of said backup object beyond the clouds server back up.
Wherein, preset a document data bank in the database of said high in the clouds, store different terminals file and uniqueness characteristic information thereof in the said document data bank;
Said end side according to preset backup policy with the uniqueness characteristic information of the pairing terminal document of said backup object beyond the clouds server carry out back-up storage.
Wherein, said backup classification comprises current system, and the backup object that this classification comprises comprises the core document and the mounted application program of operating system; Store core document and uniqueness characteristic information thereof that different operating system comprises in the document data bank that presets in the server of said high in the clouds, and store the uniqueness characteristic information of different application and file is installed;
Said backup-step comprises:
According to the backup request of terminal/subscriber, obtain the core document of end side current operation system and the uniqueness characteristic 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 characteristic information representative of said backup, and and the uniqueness characteristic information representative application program installation file of said backup between corresponding relation.
Wherein, 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.
Wherein, said backup classification comprises application program, and the backup object that this classification comprises comprises the mounted application program in terminal; Store the uniqueness characteristic information of different application in the document data bank that presets in the server of said high in the clouds and file is installed;
Said backup-step comprises:
According to the backup request of terminal/subscriber, obtain the uniqueness characteristic information of the current mounted application program of end side, 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 application program installation file of the uniqueness characteristic information representative of said backup.
Wherein, said backup classification comprises the user data relevant with application program, and the backup object that this classification comprises comprises the subscriber data file of this application program;
Said backup-step comprises:
According to the backup request of terminal/subscriber, obtain the user data of the application program that the user selectes and be sent to high in the clouds server backup storage.
Wherein, said backup-step further comprises:
If said high in the clouds server can't be confirmed the core document of this operating system corresponding with the uniqueness characteristic information of said end side transmission in said document data bank, then the local core document corresponding with this uniqueness characteristic information is sent to high in the clouds server backup storage by said end side.
Wherein, said backup-step further comprises:
If said high in the clouds server can't confirm the uniqueness characteristic information corresponding application program of sending with said end side file is installed in said document data bank, then by said end side will be corresponding with this uniqueness characteristic information the local application file and the modification information of operating system registration table be sent to the high in the clouds server backup store.
Wherein, said backup-step further comprises: the user data of the mounted application program of end side is sent to high in the clouds server backup storage.
Wherein, said end side is obtained the uniqueness characteristic 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.
Wherein, The said end side of obtaining is confirmed the title of terminal local operation system core file according to the core document title of this operating system of storing in the said server side document data bank, and obtains the uniqueness characteristic information of the core document of local operation system in view of the above.
Wherein, the present invention 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.
Wherein, the present invention further comprises:
Obtain the current non-core file and the corresponding uniqueness characteristic information of this operating system by said end side, and be sent to the high in the clouds server stores.
Wherein, the relative position relation information between the core document that further stores different operating system in the said document data bank and comprised.
Wherein, 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.
Wherein, the present invention further comprises: 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.
The present invention and then a kind of terminal object class restoration methods based on the cloud framework is provided comprises:
In end side one user interface is provided, to provide different backup classifications to supply the user to select to recover according to the preset strategy of showing, the wherein different classifications that back up comprise different backup objects;
Recovery classification and the object selected according to the user, beyond the clouds server confirm that this terminal/subscriber backed up with the corresponding file of said backup object, and, utilize said backup file to carry out corresponding recovery in end side according to preset recovery policy.
Wherein, preset a document data bank in the database of said high in the clouds, store different terminals file and uniqueness characteristic information thereof in the said document data bank;
The uniqueness characteristic information that said high in the clouds server has backed up according to terminal/subscriber confirm in document data bank that this terminal/subscriber backed up with the corresponding file of said backup object.
Wherein, the said classification that backed up comprises current system, and the backup object that this classification comprises comprises the core document and the mounted application program of operating system; The corresponding file of said backup object that backed up and said comprises that this operating system kernel file reaches the uniqueness characteristic information of set up applications;
Said recovering step comprises:
The current uniqueness characteristic information of the uniqueness characteristic 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 is mated;
To mate unsuccessful current unique characteristic in end side and know the deletion of information corresponding file, and will mate unsuccessful uniqueness characteristic information corresponding file by the high in the clouds server side and be sent to this end side corresponding stored;
According to the said uniqueness characteristic information that has backed up, use the installation file of the corresponding application program that prestores to carry out installation by the high in the clouds server in end side in the mounted application program of end side,
Wherein, Preset a document data bank in the server of said high in the clouds; Store core document and initial registration list file that different operating system comprises, and the uniqueness characteristic information of said core document, and store the uniqueness characteristic information of different application and file is installed.
Wherein, further store 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.
Wherein, said backup classification comprises application program, and the backup object that this classification comprises comprises the mounted application program in terminal; Said corresponding file of backup object that backed up and said or data comprise the uniqueness characteristic information of set up applications;
Said recovering step comprises:
According to the said uniqueness characteristic information that has backed up, use the installation file of the corresponding application program that prestores to carry out installation by the high in the clouds server in end side in the mounted application program of end side,
Preset a document data bank in the server of said high in the clouds, store the uniqueness characteristic information of different application and file is installed.
Wherein, said backup classification comprises the user data relevant with application program, and the backup object that this classification comprises comprises the subscriber data file of this application program; Said corresponding file of backup object that backed up and said or data comprise the subscriber data file of this application program;
Said recovering step comprises:
Server is sent to the end side corresponding stored from high in the clouds with the user data of this application program that has backed up.
Wherein, said coupling step comprises: the current uniqueness characteristic information of the uniqueness characteristic 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 is mated.
Wherein, said coupling step comprises: the current uniqueness characteristic information of the uniqueness characteristic 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 is mated.
Wherein, said coupling step comprises:
The high in the clouds server is sent to end side with the uniqueness characteristic information of the said operating system kernel file that has backed up;
The current uniqueness characteristic information of the core document that the uniqueness characteristic information of the operating system kernel file that has backed up that end side will receive is corresponding with the local operation system is mated.
Wherein, said coupling step comprises:
By end side the current uniqueness characteristic information of the core document of local operation system is sent to the high in the clouds server;
The uniqueness characteristic information of the core document that had been backed up by this terminal of the said current uniqueness characteristic information that will be received by said high in the clouds server and storage is mated.
Wherein, the present invention 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.
Wherein, said coupling step further comprises: the current uniqueness characteristic information of the uniqueness characteristic 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 is mated.
Wherein, Said high in the clouds server will mate the step that unsuccessful uniqueness characteristic 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.
Wherein, 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.
Wherein, said end side is confirmed the title of the core document of said local operation system according to a presetting rule table.
Wherein, 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.
Wherein, the uniqueness characteristic information of said operating system kernel file comprises the signature of this document.
Wherein, the uniqueness characteristic information of said application program comprises the title and the version number of this program.
Use the present invention, because the option of classification and object is provided, the user can only back up part own interested or that pay close attention to and recover; And the present invention does not need the transfer entity file, only needs the characteristic information of transfer files; 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 object class backup method process flow diagram based on the cloud framework of the embodiment of the invention.
Fig. 2 is according to the described schematic flow sheet that current system is backed up of the embodiment of the invention.
Fig. 3 is according to the described backup synoptic diagram of the embodiment of the invention.
Fig. 4 is the process flow diagram according to the uniqueness characteristic 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. 5 is the schematic flow sheet according to the described backup application of the embodiment of the invention.
Fig. 6 is according to the described a kind of terminal object class restoration methods process flow diagram based on the cloud framework of the embodiment of the invention.
Shown in Figure 7, be schematic flow sheet according to the described current system recovery 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 object class backup method process flow diagram of the embodiment of the invention, comprising based on the cloud framework:
Step 101: in end side one user interface is provided, to provide different backup classifications to supply the user to select according to the preset strategy of showing, wherein different backup classifications comprise different backup objects;
Step 102: backup classification and the object selected according to the user, end side according to preset backup policy with the pairing terminal document of said backup object beyond the clouds server back up.
Wherein, can in the database of said high in the clouds, preset a document data bank, store different terminals file and uniqueness characteristic information thereof in the said document data bank; And said end side can according to preset backup policy with the uniqueness characteristic information of the pairing terminal document of said backup object beyond the clouds server carry out back-up storage.
For example, said backup classification can be current total system, and the backup object that this classification comprises comprises the core document and the mounted application program of operating system; Store core document and initial registration list file that different operating system comprises in the document data bank that presets in the server of said high in the clouds; And the uniqueness characteristic information of said core document, and store the uniqueness characteristic information of different application and file is installed.
As shown in Figure 2, for according to the described schematic flow sheet that current system is backed up of the embodiment of the invention, comprising:
Step 201: according to the backup request of terminal/subscriber, obtain the core document of end side current operation system and the uniqueness characteristic information of current mounted application program, and be sent to high in the clouds server backup storage;
Step 202: 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 characteristic information representative of said backup, and with the application program installation file of the uniqueness characteristic information representative of the mounted application program that backs up between corresponding relation.
The uniqueness characteristic information of said operating system kernel file can be the information that signing messages or MD5 value of this document etc. can unique difference; The uniqueness characteristic information of said application program can be the information that title and the version number or the ID etc. of this program can unique difference.
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 characteristic 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.
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 characteristic 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 characteristic information.
As shown in Figure 3; In terminal 301, 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 302 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 characteristic 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 4, the process flow diagram for according to the uniqueness characteristic 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 401: end side is sent to the high in the clouds server with the uniqueness characteristic information of current operation system;
Step 402: 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 characteristic information of the different operating system of document data bank record, and the title of core document is sent to this end side;
Step 403: said end side is according to the uniqueness characteristic information of the core document of the name acquiring current operation system of said core document.
Title that wherein said uniqueness characteristic 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 characteristic 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 characteristic 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 characteristic 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 characteristic 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 characteristic information of different application and file is installed; Therefore; Through knowing the uniqueness characteristic information of end side backup, can confirm corresponding installation file, so that use when recovering.
And if said high in the clouds server can't confirm that in said document data bank the uniqueness characteristic information corresponding application program of sending with said end side installs file, then by said end side will be corresponding with this uniqueness characteristic information the local application file and the modification information of operating system registration table be sent to the high in the clouds server backup store.
In addition, can also the user data of the mounted application program of end side be sent to the storage of high in the clouds server backup, so that can user data be reduced in the lump when recovering.
According to another embodiment of the present invention, said backup classification can be an application program, and the backup object that this classification comprises comprises the mounted application program in terminal; Store the uniqueness characteristic information of different application in the document data bank that presets in the server of said high in the clouds and file is installed.
As shown in Figure 5, the schematic flow sheet for according to the described backup application of the embodiment of the invention comprises:
Step 501: according to the backup request of terminal/subscriber, obtain the uniqueness characteristic information of the current mounted application program of end side, and be sent to high in the clouds server backup storage;
Step 502: 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 application program installation file of the uniqueness characteristic information representative of said backup.
According to further embodiment of this invention; Said backup classification can be the user data relevant with application program, like the collection setting of browser, or user's Inbox of mailer etc.; The backup object that this classification comprises comprises the subscriber data file of this application program; In when backup, can be according to the backup request of terminal/subscriber, obtain the user data of the application program that the user selectes and be sent to high in the clouds server backup storage.
As shown in Figure 6, for according to the described a kind of terminal object class restoration methods process flow diagram of the embodiment of the invention, comprising based on the cloud framework:
Step 601: in end side one user interface is provided, to provide different backup classifications to supply the user to select to recover according to the preset strategy of showing, the wherein different classifications that back up comprise different backup objects;
Step 602: recovery classification and the object selected according to the user; Beyond the clouds server confirm that this terminal/subscriber backed up with the corresponding file of said backup object; And, utilize said backup file to carry out corresponding recovery in end side according to preset recovery policy.
Wherein, a document data bank be can preset in the database of said high in the clouds, different terminals file and uniqueness characteristic information thereof stored in the said document data bank; The uniqueness characteristic information that said high in the clouds server can back up according to terminal/subscriber confirm in document data bank that this terminal/subscriber backed up with the corresponding file of said backup object.
According to embodiments of the invention, the said classification that backed up comprises current system, and the backup object that this classification comprises comprises the core document and the mounted application program of operating system; The corresponding file of said backup object that backed up and said comprises that this operating system kernel file reaches the uniqueness characteristic information of set up applications.
As shown in Figure 7, the schematic flow sheet for according to the described current system recovery of the embodiment of the invention comprises:
Step 701: the current uniqueness characteristic information of the uniqueness characteristic 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 is mated;
Step 702: will mate unsuccessful current unique characteristic in end side and know the deletion of information corresponding file, and will mate unsuccessful uniqueness characteristic information corresponding file by the high in the clouds server side and be sent to this end side corresponding stored;
Step 703: according to the said uniqueness characteristic information that has backed up, use the installation file of the corresponding application program that prestores to carry out installation by the high in the clouds server in end side in the mounted application program of end side,
Wherein, Preset a document data bank in the server of said high in the clouds; Store core document and initial registration list file that different operating system comprises, and the uniqueness characteristic information of said core document, and store the uniqueness characteristic information of different application and file is installed.
Further can store 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.
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 characteristic information of the uniqueness characteristic 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 characteristic 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 uniqueness characteristic information.
When recovering, the uniqueness characteristic information of the core document of this operating system that can the high in the clouds server side have been backed up is mated with the current uniqueness characteristic 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 characteristic information of the core document of operating system program that the high in the clouds server side has been backed up is mated with the current uniqueness characteristic information of the core document of this corresponding program in end side this locality.
And for the step of the uniqueness characteristic information matches between the core document, can be to carry out by end side, also can be to carry out by server side.
For example, can the uniqueness characteristic 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 characteristic information of the core document that receives with the current uniqueness characteristic information of the core document of local corresponding program.
The current uniqueness characteristic 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 characteristic information of the core document of this operating system program that had been backed up by this terminal of the said current uniqueness characteristic information that will be received by said high in the clouds server then, and storage is mated.
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 characteristic information; The uniqueness characteristic 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 is mated with the current uniqueness characteristic 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 characteristic 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.
According to another embodiment of the present invention, said backup classification can comprise application program, and the backup object that this classification comprises comprises the mounted application program in terminal; Said corresponding file of backup object that backed up and said or data comprise the uniqueness characteristic information of set up applications.
When recovering; By the high in the clouds server according to the said uniqueness characteristic information that has backed up in the mounted application program of end side; The installation file of the corresponding application program that use prestores is carried out in end side and is installed; And in the server of said high in the clouds, preset document data bank, store the uniqueness characteristic information of different application and file is installed.
According to further embodiment of this invention, said backup classification can comprise the user data relevant with application program, and the backup object that this classification comprises comprises the subscriber data file of this application program; Said corresponding file of backup object that backed up and said or data comprise the subscriber data file of this application program;
During recovery, can server be sent to the end side corresponding stored from high in the clouds with the user data of this application program that has backed up.
This shows; The present invention has been owing to the time provide the classification option in backup, wherein different classes ofly also comprises different backup objects, through the selection to classification and object; Realized that the part of only user being paid close attention to backs up and recovers, and has made things convenient for the management of user to the terminal.Simultaneously, the present invention only need back up the characteristic information of current system in when backup, and need not actual backup file content, and therefore, backup rate is very fast, and data quantity transmitted significantly reduces; And be based on diversity ratio recovery when recovering, if promptly the characteristic information of core document does not change, then need not recover this document; That has only that characteristic information changes just need download corresponding document from database; Therefore, the speed of recovery is also very fast, and transmission quantity seldom.In addition, 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 (36)
1. the terminal object class backup method based on the cloud framework is characterized in that, comprising:
In end side one user interface is provided, to provide different backup classifications to supply the user to select according to the preset strategy of showing, wherein different backup classifications comprise different backup objects;
Backup classification and the object selected according to the user, end side according to preset backup policy with the pairing terminal document of said backup object beyond the clouds server back up.
2. the method for claim 1 is characterized in that, presets a document data bank in the database of said high in the clouds, stores different terminals file and uniqueness characteristic information thereof in the said document data bank;
Said end side according to preset backup policy with the uniqueness characteristic information of the pairing terminal document of said backup object beyond the clouds server carry out back-up storage.
3. method as claimed in claim 2 is characterized in that, said backup classification comprises current system, and the backup object that this classification comprises comprises the core document and the mounted application program of operating system; Store core document and uniqueness characteristic information thereof that different operating system comprises in the document data bank that presets in the server of said high in the clouds, and store the uniqueness characteristic information of different application and file is installed;
Said backup-step comprises:
According to the backup request of terminal/subscriber, obtain the core document of end side current operation system and the uniqueness characteristic 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 characteristic information representative of said backup, and and the uniqueness characteristic information representative application program installation file of said backup between corresponding relation.
4. method as claimed in claim 3 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.
5. method as claimed in claim 2 is characterized in that, said backup classification comprises application program, and the backup object that this classification comprises comprises the mounted application program in terminal; Store the uniqueness characteristic information of different application in the document data bank that presets in the server of said high in the clouds and file is installed;
Said backup-step comprises:
According to the backup request of terminal/subscriber, obtain the uniqueness characteristic information of the current mounted application program of end side, 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 application program installation file of the uniqueness characteristic information representative of said backup.
6. method as claimed in claim 2 is characterized in that, said backup classification comprises the user data relevant with application program, and the backup object that this classification comprises comprises the subscriber data file of this application program;
Said backup-step comprises:
According to the backup request of terminal/subscriber, obtain the user data of the application program that the user selectes and be sent to high in the clouds server backup storage.
7. method as claimed in claim 3 is characterized in that, said backup-step further comprises:
If said high in the clouds server can't be confirmed the core document of this operating system corresponding with the uniqueness characteristic information of said end side transmission in said document data bank, then the local core document corresponding with this uniqueness characteristic information is sent to high in the clouds server backup storage by said end side.
8. method as claimed in claim 3 is characterized in that, said backup-step further comprises:
If said high in the clouds server can't confirm the uniqueness characteristic information corresponding application program of sending with said end side file is installed in said document data bank, then by said end side will be corresponding with this uniqueness characteristic information the local application file and the modification information of operating system registration table be sent to the high in the clouds server backup store.
9. like claim 3 or 6 described methods, it is characterized in that said backup-step further comprises: the user data of the mounted application program of end side is sent to high in the clouds server backup storage.
10. method as claimed in claim 3 is characterized in that, said end side is obtained the uniqueness characteristic 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.
11. method as claimed in claim 3; It is characterized in that; The said end side of obtaining is confirmed the title of terminal local operation system core file according to the core document title of this operating system of storing in the said server side document data bank, and obtains the uniqueness characteristic information of the core document of local operation system in view of the above.
12. method as claimed in claim 3 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.
13. method as claimed in claim 3 is characterized in that, further comprises:
Obtain the current non-core file and the corresponding uniqueness characteristic information of this operating system by said end side, and be sent to the high in the clouds server stores.
14. method as claimed in claim 3 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.
15. method as claimed in claim 3 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.
16. like claim 12 or 13 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.
17. method as claimed in claim 3 is characterized in that, the uniqueness characteristic information of said operating system kernel file comprises the signing messages of this document.
18., it is characterized in that the uniqueness characteristic information of said application program comprises the title and the version number of this program like claim 3 or 5 described methods.
19. the terminal object class restoration methods based on the cloud framework is characterized in that, comprising:
In end side one user interface is provided, to provide different backup classifications to supply the user to select to recover according to the preset strategy of showing, the wherein different classifications that back up comprise different backup objects;
Recovery classification and the object selected according to the user, beyond the clouds server confirm that this terminal/subscriber backed up with the corresponding file of said backup object, and, utilize said backup file to carry out corresponding recovery in end side according to preset recovery policy.
20. method as claimed in claim 19 is characterized in that, presets a document data bank in the database of said high in the clouds, stores different terminals file and uniqueness characteristic information thereof in the said document data bank;
The uniqueness characteristic information that said high in the clouds server has backed up according to terminal/subscriber confirm in document data bank that this terminal/subscriber backed up with the corresponding file of said backup object.
21. method as claimed in claim 20 is characterized in that, the said classification that backed up comprises current system, and the backup object that this classification comprises comprises the core document and the mounted application program of operating system; The corresponding file of said backup object that backed up and said comprises that this operating system kernel file reaches the uniqueness characteristic information of set up applications;
Said recovering step comprises:
The current uniqueness characteristic information of the uniqueness characteristic 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 is mated;
To mate unsuccessful current unique characteristic in end side and know the deletion of information corresponding file, and will mate unsuccessful uniqueness characteristic information corresponding file by the high in the clouds server side and be sent to this end side corresponding stored;
According to the said uniqueness characteristic information that has backed up, use the installation file of the corresponding application program that prestores to carry out installation by the high in the clouds server in end side in the mounted application program of end side,
Wherein, Preset a document data bank in the server of said high in the clouds; Store core document and initial registration list file that different operating system comprises, and the uniqueness characteristic information of said core document, and store the uniqueness characteristic information of different application and file is installed.
22. method as claimed in claim 21 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.
23. method as claimed in claim 20 is characterized in that, said backup classification comprises application program, and the backup object that this classification comprises comprises the mounted application program in terminal; Said corresponding file of backup object that backed up and said or data comprise the uniqueness characteristic information of set up applications;
Said recovering step comprises:
According to the said uniqueness characteristic information that has backed up, use the installation file of the corresponding application program that prestores to carry out installation by the high in the clouds server in end side in the mounted application program of end side,
Preset a document data bank in the server of said high in the clouds, store the uniqueness characteristic information of different application and file is installed.
24. method as claimed in claim 20 is characterized in that, said backup classification comprises the user data relevant with application program, and the backup object that this classification comprises comprises the subscriber data file of this application program; Said corresponding file of backup object that backed up and said or data comprise the subscriber data file of this application program;
Said recovering step comprises:
Server is sent to the end side corresponding stored from high in the clouds with the user data of this application program that has backed up.
25. method as claimed in claim 21; It is characterized in that; Said coupling step comprises: the current uniqueness characteristic information of the uniqueness characteristic 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 is mated.
26. method as claimed in claim 21; It is characterized in that; Said coupling step comprises: the current uniqueness characteristic information of the uniqueness characteristic 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 is mated.
27. method as claimed in claim 26 is characterized in that, said coupling step comprises:
The high in the clouds server is sent to end side with the uniqueness characteristic information of the said operating system kernel file that has backed up;
The current uniqueness characteristic information of the core document that the uniqueness characteristic information of the operating system kernel file that has backed up that end side will receive is corresponding with the local operation system is mated.
28. method as claimed in claim 26 is characterized in that, said coupling step comprises:
By end side the current uniqueness characteristic information of the core document of local operation system is sent to the high in the clouds server;
The uniqueness characteristic information of the core document that had been backed up by this terminal of the said current uniqueness characteristic information that will be received by said high in the clouds server and storage is mated.
29. method as claimed in claim 21 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.
30. method as claimed in claim 21; It is characterized in that; Said coupling step further comprises: the current uniqueness characteristic information of the uniqueness characteristic 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 is mated.
31. method as claimed in claim 21; It is characterized in that; Said high in the clouds server will mate the step that unsuccessful uniqueness characteristic 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.
32., 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 29 or 30 described methods.
33. method as claimed in claim 26 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.
34. method as claimed in claim 26 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.
35. method as claimed in claim 21 is characterized in that, the uniqueness characteristic information of said operating system kernel file comprises the signature of this document.
36., it is characterized in that the uniqueness characteristic information of said application program comprises the title and the version number of this program like claim 21 or 23 described methods.
Priority Applications (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2011103048244A CN102495771A (en) | 2011-09-30 | 2011-09-30 | Terminal object classified backup and recovery methods based on cloud architecture |
| PCT/CN2012/081984 WO2013044794A1 (en) | 2011-09-30 | 2012-09-26 | Terminal backup and recovery method |
| US14/347,274 US10108501B2 (en) | 2011-09-30 | 2012-09-26 | Terminal backup and recovery method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2011103048244A CN102495771A (en) | 2011-09-30 | 2011-09-30 | Terminal object classified backup and recovery methods based on cloud architecture |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102495771A true CN102495771A (en) | 2012-06-13 |
Family
ID=46187597
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2011103048244A Pending CN102495771A (en) | 2011-09-30 | 2011-09-30 | Terminal object classified backup and recovery methods based on cloud architecture |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102495771A (en) |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102882923A (en) * | 2012-07-25 | 2013-01-16 | 北京亿赛通科技发展有限责任公司 | Secure storage system and method for mobile terminal |
| WO2013044794A1 (en) * | 2011-09-30 | 2013-04-04 | 北京奇虎科技有限公司 | Terminal backup and recovery method |
| CN103049566A (en) * | 2012-12-31 | 2013-04-17 | 中国电子科技集团公司第十五研究所 | Universal database backup and restoring method |
| CN103619008A (en) * | 2013-12-11 | 2014-03-05 | 北京网秦天下科技有限公司 | System and method for performing backup and restoration on data |
| CN103679029A (en) * | 2013-12-11 | 2014-03-26 | 北京奇虎科技有限公司 | Method and device for repairing cheap-copy application programs |
| CN103778034A (en) * | 2014-02-26 | 2014-05-07 | 广州杰赛科技股份有限公司 | Cloud storage-based data backup disaster recovery method and system |
| CN104301382A (en) * | 2014-09-03 | 2015-01-21 | 惠州Tcl移动通信有限公司 | Cloud data backup and recovery method |
| CN104898918A (en) * | 2014-03-03 | 2015-09-09 | 群晖科技股份有限公司 | Backup device and operation method |
| CN105378677A (en) * | 2013-05-29 | 2016-03-02 | 微软技术许可有限责任公司 | Service-based backup data restoring to devices |
| CN105451223A (en) * | 2014-08-07 | 2016-03-30 | 阿里巴巴集团控股有限公司 | Information monitoring method and device, and mobile terminal |
| CN106027602A (en) * | 2016-04-29 | 2016-10-12 | 乐视控股（北京）有限公司 | Cloud backup and restoration methods and terminal backup and restoration devices for applications |
| CN106294013A (en) * | 2016-08-10 | 2017-01-04 | 广东省科技基础条件平台中心 | A kind of data disaster tolerance method and system between different backup territory |
| CN106790581A (en) * | 2016-12-28 | 2017-05-31 | 深圳天珑无线科技有限公司 | Application data processing method, device and terminal |
| CN108881403A (en) * | 2018-05-29 | 2018-11-23 | 珠海格力电器股份有限公司 | A kind of method and device of backup chat record |
Citations (5)
| 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 |
| CN101038594A (en) * | 2006-03-09 | 2007-09-19 | 国际商业机器公司 | Controlling incremental backups using opaque object attributes |
| US20080126442A1 (en) * | 2006-08-04 | 2008-05-29 | Pavel Cisler | Architecture for back up and/or recovery of electronic data |
| CN101324858A (en) * | 2008-07-10 | 2008-12-17 | 宇龙计算机通信科技(深圳)有限公司 | Method, system and terminal for recovering data |
| CN102063350A (en) * | 2011-02-15 | 2011-05-18 | 宇龙计算机通信科技(深圳)有限公司 | Method, device and terminal for backing up and recovering |
-
2011
- 2011-09-30 CN CN2011103048244A patent/CN102495771A/en active Pending
Patent Citations (5)
| 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 |
| CN101038594A (en) * | 2006-03-09 | 2007-09-19 | 国际商业机器公司 | Controlling incremental backups using opaque object attributes |
| US20080126442A1 (en) * | 2006-08-04 | 2008-05-29 | Pavel Cisler | Architecture for back up and/or recovery of electronic data |
| CN101324858A (en) * | 2008-07-10 | 2008-12-17 | 宇龙计算机通信科技(深圳)有限公司 | Method, system and terminal for recovering data |
| CN102063350A (en) * | 2011-02-15 | 2011-05-18 | 宇龙计算机通信科技(深圳)有限公司 | Method, device and terminal for backing up and recovering |
Cited By (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2013044794A1 (en) * | 2011-09-30 | 2013-04-04 | 北京奇虎科技有限公司 | Terminal backup and recovery method |
| CN102882923A (en) * | 2012-07-25 | 2013-01-16 | 北京亿赛通科技发展有限责任公司 | Secure storage system and method for mobile terminal |
| CN102882923B (en) * | 2012-07-25 | 2015-04-15 | 北京亿赛通科技发展有限责任公司 | Secure storage system and method for mobile terminal |
| CN103049566A (en) * | 2012-12-31 | 2013-04-17 | 中国电子科技集团公司第十五研究所 | Universal database backup and restoring method |
| CN105378677A (en) * | 2013-05-29 | 2016-03-02 | 微软技术许可有限责任公司 | Service-based backup data restoring to devices |
| CN105378677B (en) * | 2013-05-29 | 2018-11-06 | 微软技术许可有限责任公司 | Equipment is restored based on Backup service data |
| CN103619008A (en) * | 2013-12-11 | 2014-03-05 | 北京网秦天下科技有限公司 | System and method for performing backup and restoration on data |
| CN103679029A (en) * | 2013-12-11 | 2014-03-26 | 北京奇虎科技有限公司 | Method and device for repairing cheap-copy application programs |
| CN103778034B (en) * | 2014-02-26 | 2017-12-01 | 广州杰赛科技股份有限公司 | Data backup disaster recovery method and system based on cloud storage |
| CN103778034A (en) * | 2014-02-26 | 2014-05-07 | 广州杰赛科技股份有限公司 | Cloud storage-based data backup disaster recovery method and system |
| CN104898918A (en) * | 2014-03-03 | 2015-09-09 | 群晖科技股份有限公司 | Backup device and operation method |
| CN104898918B (en) * | 2014-03-03 | 2017-11-17 | 群晖科技股份有限公司 | Backup device and operation method |
| CN105451223A (en) * | 2014-08-07 | 2016-03-30 | 阿里巴巴集团控股有限公司 | Information monitoring method and device, and mobile terminal |
| CN105451223B (en) * | 2014-08-07 | 2019-03-15 | 阿里巴巴集团控股有限公司 | Monitoring method, device and the mobile terminal of information |
| CN104301382A (en) * | 2014-09-03 | 2015-01-21 | 惠州Tcl移动通信有限公司 | Cloud data backup and recovery method |
| CN106027602A (en) * | 2016-04-29 | 2016-10-12 | 乐视控股（北京）有限公司 | Cloud backup and restoration methods and terminal backup and restoration devices for applications |
| CN106294013A (en) * | 2016-08-10 | 2017-01-04 | 广东省科技基础条件平台中心 | A kind of data disaster tolerance method and system between different backup territory |
| CN106294013B (en) * | 2016-08-10 | 2019-03-29 | 广东省科技基础条件平台中心 | A kind of different data disaster tolerance method and systems backed up between domain |
| CN106790581A (en) * | 2016-12-28 | 2017-05-31 | 深圳天珑无线科技有限公司 | Application data processing method, device and terminal |
| CN106790581B (en) * | 2016-12-28 | 2020-12-22 | 深圳天珑无线科技有限公司 | Application data processing method and device and terminal |
| CN108881403A (en) * | 2018-05-29 | 2018-11-23 | 珠海格力电器股份有限公司 | A kind of method and device of backup chat record |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| 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 | |
| CN102495772B (en) | Characteristic-based terminal program cloud backup and recovery methods | |
| CN102508735A (en) | Method for backing up and restoring terminal system based on cloud architecture | |
| US20200264775A1 (en) | Serverless solution for continuous data protection | |
| US11409765B2 (en) | Application of information management policies based on operation with a geographic entity | |
| CN102360321A (en) | Terminal program quick backup and recovery method based on cloud architecture | |
| US8090690B2 (en) | Systems and methods for data upload and download | |
| US10108501B2 (en) | Terminal backup and recovery method | |
| US20110196840A1 (en) | System and method for incremental backup storage | |
| US20100312805A1 (en) | System and method for capturing, managing, and distributing computer files | |
| US20120159100A1 (en) | Storage device migration and redirection | |
| JP5868986B2 (en) | Recovery by item | |
| EP3848809A1 (en) | Data disaster recovery method and site | |
| US10747458B2 (en) | Methods and systems for improving efficiency in cloud-as-backup tier | |
| CN103179153A (en) | Mobile terminal and mobile terminal data backup method based on cloud server | |
| CN102331956A (en) | User data backup method and device | |
| CN107506265A (en) | A kind of backup of otherness telefile and recovery system based on internet | |
| US8918427B1 (en) | Virtualization of file input/output operations | |
| US9183208B1 (en) | Fileshot management | |
| CN103530202A (en) | Cloud backing-up and recovering method used for terminal program | |
| CN102682102A (en) | Desktop saving method, client and system | |
| US20150370649A1 (en) | Sending a Request to a Management Service | |
| EP2413233B1 (en) | Android phone with an application for content display | |
| CN103500127A (en) | Terminal program cloud backup and recovery method |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20120613 |