CN104182294A

CN104182294A - Method and device for backing up and recovering file

Info

Publication number: CN104182294A
Application number: CN201310195321.7A
Authority: CN
Inventors: 杜仲明; 张东旭
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2013-05-23
Filing date: 2013-05-23
Publication date: 2014-12-03

Abstract

The embodiment of the invention discloses a method and a device for backing up and recovering a file, relates to the field of data processing, solves the problem of conflict in the file back-up process and solves the problem that in the case of conflict in the file back-up process, the file which needs to be recovered is lost or a file name is modified. The invention adopts the specific scheme that the method comprises the following steps: acquiring a configuration file; according to attribute information of the configuration file and at least one file to be backed up, generating a configuration information set of the files to be backed up; adding configuration information of at least one file to be backed up in the configuration information set of the files to be backed up into the configuration file; according to the configuration information set of the files to be backed up, backing up the file to be backed up, which corresponds to the configuration information of at least one file to be backed up in the configuration information set of the files to be backed up to a server, and when a client needs to recover the file from the server, downloading the file which needs to be recovered from the server according to the configuration file. The method and the device for backing up and recovering the file are used in the file back-up and recovering process.

Description

A kind of file backup, file restoration methods and device

Technical field

The present invention relates to data processing field, relate in particular to a kind of file backup, file restoration methods and device.

Background technology

Along with the development of mobile Internet, the demand of storage, migration and the management of user to personal data is more and more stronger, mobile phone cloud backup software is exactly a kind of data backup software very popular on current mobile phone, data on mobile phone can be backuped in the server in high in the clouds, and can be from the server in high in the clouds real-time carry out data recovery.

Current mobile phone generally all can have two Security Digital (SD)s (Secure Digital Memory Card, SD card), and on these two SD cards, probably can there is the identical but file that content is different of name, if desired by the file backup on SD card to the lower time of same catalogue in the server in high in the clouds, just can cause file backup to clash.

And, while clashing in the time of file backup, just the file of uploading after in two files identical title but that content is different is carried out to rename, or the file of uploading after the file of before uploading quilt covers, like this in the time that file recovers, just can cause the filename of the file that returns to client and the filename of original inconsistent, or cause the File lose of uploading above, user be experienced bad.

Summary of the invention

Embodiments of the invention provide a kind of file backup method and device, have solved the collision problem in file backup process.

For achieving the above object, embodiments of the invention adopt following technical scheme:

A first aspect of the present invention, provides a kind of file backup method, comprising:

Obtain configuration file; Wherein, the configuration information that comprises at least one historical backup file in described configuration file;

According to the attribute information of described configuration file and at least one file to be backed up, generate file configuration information aggregate to be backed up; Wherein, the configuration information that described file configuration information aggregate to be backed up comprises file to be backed up described at least one;

By described in described file configuration information aggregate to be backed up described at least one the configuration information of file to be backed up add in described configuration file;

According to described file configuration information aggregate to be backed up, back up the described file to be backed up that the configuration information of file to be backed up is corresponding described at least one in described file configuration information aggregate to be backed up to server.

In conjunction with first aspect, in a kind of possible implementation, also comprise:

Show the configuration information of the file that has backed up to described server in client according to described configuration file.

In conjunction with first aspect and above-mentioned possible implementation, in the possible implementation of another kind, described in obtain configuration file, comprising:

Send the first request to described server; Wherein, described the first request is used for asking described server to issue described configuration file;

Receive the described configuration file that described server sends;

Described by described in described file configuration information aggregate to be backed up described at least one the configuration information of file to be backed up add described configuration file in after, also comprise:

Described configuration file is backed up to described server, so that the original configuration file of described server update.

In conjunction with first aspect and above-mentioned possible implementation, in the possible implementation of another kind, describedly generate file configuration information aggregate to be backed up according to the attribute information of described configuration file and at least one file to be backed up, comprising:

According to the configuration information of described at least one the historical backup file in described configuration file, from the attribute information of described at least one file to be backed up, determine fileinfo set to be backed up; In described fileinfo set to be backed up, comprise at least one and need to back up to the attribute information of the described file to be backed up of described server;

In the time comprising the attribute information of a described file to be backed up that need to back up to described server in described fileinfo set to be backed up, judge that the filename of the described described file to be backed up that need to back up to described server is identical with the filename of described historical backup file, revise the filename of the described described file to be backed up that need to back up to described server;

In the time comprising the attribute information of at least two described files to be backed up that need to back up to described server in described fileinfo set to be backed up, the filename that judges described the first file to be backed up is identical with the filename of the second file to be backed up, and/or, the filename of described the first file to be backed up is identical with the filename of described history file to be backed up, revises the filename of described the first file to be backed up; Wherein, the attribute information of the attribute information of described the first file to be backed up and described the second file to be backed up is contained in described fileinfo set to be backed up;

Generate described file configuration information aggregate to be backed up; Wherein, described file configuration information aggregate to be backed up comprise described at least one need to back up to the configuration information of the described file to be backed up of described server.

In conjunction with first aspect and above-mentioned possible implementation, in the possible implementation of another kind, described according to described file configuration information aggregate to be backed up, back up the described file to be backed up that the configuration information of file to be backed up is corresponding described at least one in described file configuration information aggregate to be backed up to server, also comprise:

Receive the backup failure response that described server sends; Wherein, the response of described backup failure is used for notifying described client backup the 3rd file failure to be backed up, and described the 3rd file to be backed up is any one file to be backed up that need to back up at least one file to be backed up of described server;

According to described backup failure response, the configuration information of described the 3rd file to be backed up is deleted from described configuration file;

Described configuration file is backed up to described server again, so that the existing configuration file of described server update.

In conjunction with first aspect and above-mentioned possible implementation, in the possible implementation of another kind,

Described configuration information comprise following at least one: backup file name, file size, file type, file layout, Message Digest Algorithm 5 MD5, client stores path, server end store path, rename instruction, old file name;

Described attribute information comprise following at least one: the server end store path of the filename of described file to be backed up, the file size of described file to be backed up, the file type of described file to be backed up, the file layout of described file to be backed up, the MD5 of described file to be backed up, the client stores path of described file to be backed up, described file to be backed up.

A second aspect of the present invention, provides a kind of file backup device, comprising:

Acquiring unit, for obtaining configuration file; Wherein, the configuration information that comprises at least one historical backup file in described configuration file;

Generation unit, for the attribute information of the described configuration file that obtains according to described acquiring unit and at least one file to be backed up, generates file configuration information aggregate to be backed up; Wherein, the configuration information that described file configuration information aggregate to be backed up comprises file to be backed up described at least one;

Adding device, for file configuration information aggregate described to be backed up that described generation unit is obtained described described at least one the configuration information of file to be backed up add in described configuration file;

The first backup units, for the file configuration information aggregate described to be backed up that obtains according to described generation unit, back up the described file to be backed up that the configuration information of file to be backed up is corresponding described at least one in described file configuration information aggregate to be backed up to server.

In conjunction with second aspect, in a kind of possible implementation, also comprise:

Display unit, for showing the configuration information of the file that has backed up to described server in client according to described configuration file.

In conjunction with second aspect and above-mentioned possible implementation, in the possible implementation of another kind, described acquiring unit, comprising:

Sending module, for sending the first request to described server; Wherein, described the first request is used for asking described server to issue described configuration file;

Receiver module, the described configuration file sending for receiving described server;

Described file backup device, also comprises:

The second backup units, for described adding device by described file configuration information aggregate to be backed up described described at least one the configuration information of file to be backed up add described configuration file in after, described configuration file is backed up to described server, so that the original configuration file of described server update.

In conjunction with second aspect and above-mentioned possible implementation, in the possible implementation of another kind, described generation unit, comprising:

Determination module, for according to the configuration information of described configuration file described historical backup file described at least one, determines to be backed up fileinfo set the attribute information of file to be backed up from described described at least one; In described fileinfo set to be backed up, comprise at least one and need to back up to the attribute information of the described file to be backed up of described server;

Judge modified module, for comprise a described file to be backed up that need to back up to described server when described fileinfo set to be backed up attribute information time, judge that the filename of the described described file to be backed up that need to back up to described server is identical with the filename of described historical backup file, revise the filename of the described described file to be backed up that need to back up to described server; In the time comprising the attribute information of at least two described files to be backed up that need to back up to described server in described fileinfo set to be backed up, the filename that judges described the first file to be backed up is identical with the filename of the second file to be backed up, and/or, the filename of described the first file to be backed up is identical with the filename of described history file to be backed up, revises the filename of described the first file to be backed up; Wherein, the attribute information of the attribute information of described the first file to be backed up and described the second file to be backed up is contained in described fileinfo set to be backed up;

Generation module, for generating described file configuration information aggregate to be backed up; Wherein, described file configuration information aggregate to be backed up comprise described at least one need to back up to the configuration information of the described file to be backed up of described server.

In conjunction with second aspect and above-mentioned possible implementation, in the possible implementation of another kind, also comprise:

Receiving element, be used in described the first backup units according to described file configuration information aggregate to be backed up, back up the described file to be backed up that the configuration information of file to be backed up is corresponding described at least one in described file configuration information aggregate to be backed up to after described server, receive the backup failure response that described server sends; Wherein, the response of described backup failure is used for notifying described client backup the 3rd file failure to be backed up, and described the 3rd file to be backed up is any one file to be backed up that need to back up at least one file to be backed up of described server;

Delete cells, also the described backup failure response for obtaining according to described receiving element is deleted the configuration information of described the 3rd file to be backed up from described configuration file;

Described the second backup units, also for described configuration file is backed up to described server again, so that the existing configuration file of described server update.

In conjunction with second aspect and above-mentioned possible implementation, in the possible implementation of another kind,

The file backup method that the embodiment of the present invention provides and device, by the configuration information of at least one historical backup file and the attribute information of at least one file to be backed up that comprise in the configuration file getting, obtain file configuration information aggregate to be backed up, the configuration information that comprises at least one file to be backed up in this file configuration information aggregate to be backed up, then the configuration information of at least one file to be backed up in file configuration information aggregate to be backed up is added in configuration file, and back up file to be backed up that the configuration information of at least one file to be backed up in file configuration information aggregate to be backed up is corresponding to server according to file configuration information aggregate to be backed up, solve the collision problem in file backup process.

The embodiment of the present invention also provides a kind of file restoration methods and device, has solved in the time that file backup clashes the problem that the File lose that the needs of appearance recover or filename are modified.

A third aspect of the present invention, provides a kind of file restoration methods, comprising:

In the time that client need to be from server recovery file, obtain and treat the set of recovery file configuration information according to configuration file; Wherein, described in, treat to comprise at least one in the set of recovery file configuration information and treat the configuration information of recovery file;

According to the first configuration information for the treatment of recovery file, judge that described first revises in the time backing up to described server until the filename of recovery file, revise the described first backup file name for the treatment of recovery file according to the described first old file name for the treatment of recovery file; Wherein, described first treat recovery file treat described in being described in the set of recovery file configuration information at least one configuration information for the treatment of recovery file corresponding treat any one in recovery file;

Described in download, treat in the set of recovery file configuration information described at least one treat the configuration information of recovery file corresponding treat recovery file.

In conjunction with the third aspect, in a kind of possible implementation,, in the time that client need to be from server recovery file, before obtaining and treat the set of recovery file configuration information according to configuration file, also comprise described:

Receive the described configuration file that described server sends.

In conjunction with the third aspect and above-mentioned possible implementation, in the possible implementation of another kind, described in described download, treat in the set of recovery file information configuration described at least one treat the configuration information of recovery file corresponding treat recovery file before, also comprise:

According to the described first configuration information for the treatment of recovery file, judge that described first treats that the old file name of recovery file is identical with the filename of the first file, revise the filename of described the first file; Wherein, described the first file is the file for the treatment of under the client stores path of recovery file described first.

In conjunction with the third aspect and above-mentioned possible implementation, in the possible implementation of another kind,

Described configuration information comprise following at least one: backup file name, file size, file type, file layout, Message Digest Algorithm 5 MD5, client stores path, server end store path, rename instruction, old file name.

A fourth aspect of the present invention, provides a kind of file recovery device, comprising:

Acquiring unit, in the time that client need to be from server recovery file, obtains and treats the set of recovery file configuration information according to configuration file; Wherein, described in, treat to comprise at least one in the set of recovery file configuration information and treat the configuration information of recovery file;

Judgement amendment unit, for according to the first configuration information for the treatment of recovery file, judge that described first revises in the time backing up to described server until the filename of recovery file, revise the described first backup file name for the treatment of recovery file according to the described first old file name for the treatment of recovery file; Wherein, described first treat recovery file treat described in being described in the set of recovery file configuration information at least one configuration information for the treatment of recovery file corresponding treat any one in recovery file;

Download unit, for treat described in downloading the set of recovery file configuration information described at least one treat the configuration information of recovery file corresponding treat recovery file.

In conjunction with fourth aspect, in a kind of possible implementation, also comprise:

Transmitting element, for described in the time that client need to be from server recovery file, described acquiring unit sends the first request to described server before obtaining and treat the set of recovery file configuration information according to configuration file; Wherein, described the first request is used for asking described server to issue described configuration file;

Receiving element, the described configuration file sending for receiving described server.

In conjunction with fourth aspect and above-mentioned possible implementation, in the possible implementation of another kind,

Described judgement amendment unit, also for treat described in downloading at described download unit the set of recovery file information configuration described at least one treat the configuration information of recovery file corresponding treat recovery file before, according to the described first configuration information for the treatment of recovery file, judge that described first treats that the old file name of recovery file is identical with the filename of the first file, revise the filename of described the first file; Wherein, described the first file is the file for the treatment of under the client stores path of recovery file described first.

File restoration methods and device that the embodiment of the present invention provides, in the time that client need to be from server recovery file, obtain and treat the set of recovery file configuration information according to configuration file, this treats to comprise at least one in the set of recovery file configuration information and treats the configuration information of recovery file, according to the first configuration information for the treatment of recovery file, judge that first revises in the time backing up to server until the filename of recovery file, treat that according to first the old file name amendment first of recovery file treats the backup file name of recovery file, then download treat at least one in the set of recovery file configuration information treat the configuration information of recovery file corresponding treat recovery file, in the time of needs recovery file, can download and treat recovery file according to configuration file, solve in the time that file backup clashes, the problem that the File lose that the needs that occur recover or filename are modified.

Brief description of the drawings

In order to be illustrated more clearly in the embodiment of the present invention or technical scheme of the prior art, to the accompanying drawing of required use in embodiment or description of the Prior Art be briefly described below, apparently, accompanying drawing in the following describes is only some embodiments of the present invention, for those of ordinary skill in the art, do not paying under the prerequisite of creative work, can also obtain according to these accompanying drawings other accompanying drawing.

A kind of file backup method process flow diagram that Fig. 1 provides for one embodiment of the invention;

A kind of file restoration methods process flow diagram that Fig. 2 provides for another embodiment of the present invention;

A kind of file backup method process flow diagram that Fig. 3 provides for another embodiment of the present invention;

The another kind of file restoration methods process flow diagram that Fig. 4 provides for another embodiment of the present invention;

A kind of file backup installation composition schematic diagram that Fig. 5 provides for another embodiment of the present invention;

The another kind of file backup installation composition schematic diagram that Fig. 6 provides for another embodiment of the present invention;

The another kind of file recovery device composition schematic diagram that Fig. 7 provides for another embodiment of the present invention;

The another kind of file recovery device composition schematic diagram that Fig. 8 provides for another embodiment of the present invention;

The another kind of file backup installation composition schematic diagram that Fig. 9 provides for another embodiment of the present invention;

The another kind of file recovery device composition schematic diagram that Figure 10 provides for another embodiment of the present invention;

A kind of file backup and recovery system composition schematic diagram that Figure 11 provides for another embodiment of the present invention.

Embodiment

Below in conjunction with the accompanying drawing in the embodiment of the present invention, the technical scheme in the embodiment of the present invention is clearly and completely described, obviously, described embodiment is only the present invention's part embodiment, instead of whole embodiment.Based on the embodiment in the present invention, those of ordinary skill in the art, not making the every other embodiment obtaining under creative work prerequisite, belong to the scope of protection of the invention.

At least there are the following problems in the time analyzing prior art, to find prior art: if clash when file is carried out to cloud backup, if cloud server by after the file uploaded carry out rename, like this when user need to from cloud server download before upload file time, occur download the title of file and the title of original inconsistent; Or time clash file being carried out to cloud backup, if after the file uploaded the file of uploading is above override, just can cause like this File lose of uploading above, user is experienced bad.In order to address this problem, the embodiment of the present invention provides a kind of file backup, file restoration methods and device, and file backup and recovery system.

One embodiment of the invention provides a kind of file backup method, and as shown in Figure 1, the method can comprise:

101a, client are obtained configuration file.

Wherein, in configuration file, comprise the configuration information of at least one historical backup file.The form of configuration file can be extensible markup language (Extensive Makeup Language, XML) form, can be also database format, and configuration file can be stored in client, also can back up to server.The configuration information of historical backup file comprises but is not limited to: the backup file name of historical backup file, the file size of historical backup file, the file type of historical backup file, the file layout of historical backup file, Message Digest Algorithm 5 (the Message-Digest Algorithm5 of historical backup file, MD5), the client stores path of historical backup file, the server end store path of historical backup file, the rename instruction of historical backup file, the old file name of historical backup file, wherein rename instruction is used to indicate historical backup file and in backup procedure, whether has carried out rename, MD5 is that current computer field completes one of hashing algorithm of consistent use for guaranteeing communication, also can be called hash algorithm, digest algorithm etc.

It should be noted that, the position of the form to configuration file and configuration file stores does not limit in embodiments of the present invention.

102a, client, according to the attribute information of configuration file and at least one file to be backed up, generate file configuration information aggregate to be backed up.

Wherein, the configuration information that file configuration information aggregate to be backed up comprises at least one file to be backed up.After getting configuration file, just can, first according to the attribute information of the configuration information of the historical backup file comprising in configuration file and at least one file to be backed up, determine file configuration information aggregate to be backed up.Concrete, can obtain which file according to the configuration information of all historical backup files in the attribute information of file to be backed up and configuration file is to have backed up to server, which file does not also back up to server, so just, can finally obtain really need to backing up to the file all to be backed up of server, then can also judge in the final file to be backed up that need to back up to server of determining and whether have conflict, only has one when backing up to the file to be backed up of server, need judgement need to back up to the filename of this file to be backed up under server catalogue whether identical with the backup file name of the history file to be backed up under this catalogue, if have identical, the filename that need to back up to this file to be backed up of server is modified, in the time need to backing up to the file to be backed up of server and have at least two, if desired back up to and in the file of server, occur that filename is identical but two or more files that content is different, and these files will back up under the same catalogue of server, or, need to back up in the file to be backed up under server catalogue documentary filename identical with the backup file name of the history file to be backed up under this catalogue, now client can be modified the filename of wherein one or more files to be backed up, final also need will be revised the old file name of file to be backed up of filename, whether rename, the information such as backup file name are as the configuration information of this file to be backed up, and by file configuration information aggregate to be backed up the configuration information combination producing of all files to be backed up.So just, can ensure that file clashes in backup procedure time, can not lose the identical but file that file content is different of filename.Wherein, the attribute information of file to be backed up includes but not limited at least following a kind of: the server end store path of the filename of file to be backed up, the file size of file to be backed up, the file type of file to be backed up, the file layout of file to be backed up, the MD5 of file to be backed up, the client stores path of file to be backed up, file to be backed up.

103a, client are added the configuration information of at least one file to be backed up in file configuration information aggregate to be backed up in configuration file to.

Wherein, after getting file configuration information aggregate to be backed up, just can be according to fileinfo set Reconfigurations file to be backed up, concrete, the configuration information of all files to be backed up in the configuration information of at least one file to be backed up in file configuration information aggregate to be backed up is added in configuration file.

104a, client be according to file configuration information aggregate to be backed up, backs up file to be backed up that the configuration information of at least one file to be backed up in file configuration information aggregate to be backed up is corresponding to server.

Wherein, after getting file configuration information aggregate to be backed up, just can be according to file configuration information aggregate to be backed up, by the file backup to be backed up corresponding configuration information of all files to be backed up in the configuration information of at least one file to be backed up in file configuration information aggregate to be backed up to server.

The file backup method that the embodiment of the present invention provides, by the configuration information of at least one historical backup file and the attribute information of at least one file to be backed up that comprise in the configuration file getting, obtain file configuration information aggregate to be backed up, the configuration information that comprises at least one file to be backed up in this file configuration information aggregate to be backed up, then the configuration information of at least one file to be backed up in file configuration information aggregate to be backed up is added in configuration file, and back up file to be backed up that the configuration information of at least one file to be backed up in file configuration information aggregate to be backed up is corresponding to server according to file configuration information aggregate to be backed up, solve the collision problem in file backup process.

Another embodiment of the present invention provides a kind of file restoration methods, and as shown in Figure 2, the method can comprise:

101b, in the time that client need to be from server recovery file, obtain and treat the set of recovery file configuration information according to configuration file.

Wherein, treat to comprise at least one in the set of recovery file configuration information and treat the configuration information of recovery file.

102b, client, according to the first configuration information for the treatment of recovery file, judge that first revises in the time backing up to server until the filename of recovery file, treat that according to first the old file name amendment first of recovery file treats the backup file name of recovery file.

Wherein, first treat recovery file be treat in the set of recovery file configuration information at least one configuration information for the treatment of recovery file corresponding treat any one in recovery file.

103b, download treat at least one in the set of recovery file configuration information treat the configuration information of recovery file corresponding treat recovery file.

Wherein, in the time of needs recovery file, download and treat recovery file according to configuration file, concrete, the configuration information of storing in configuration file comprises until recovery file in the whether rename instruction of rename of when backup, and comprise this and treat the old file name of recovery file, carry out rename during at file backup until recovery file if obtain this according to rename instruction, so just, can the backup file name of this file be revised as to old file name during until recovery file in download, the filename while having ensured to download the file obtaining with this file backup is consistent.

The file restoration methods that the embodiment of the present invention provides, in the time that client need to be from server recovery file, obtain and treat the set of recovery file configuration information according to configuration file, this treats to comprise at least one in the set of recovery file configuration information and treats the configuration information of recovery file, according to the first configuration information for the treatment of recovery file, judge that first revises in the time backing up to server until the filename of recovery file, treat that according to first the old file name amendment first of recovery file treats the backup file name of recovery file, then download treat at least one in the set of recovery file configuration information treat the configuration information of recovery file corresponding treat recovery file, in the time of needs recovery file, can download and treat recovery file according to configuration file, solve in the time that file backup clashes, the problem that the File lose that the needs that occur recover or filename are modified.

Another embodiment of the present invention provides a kind of file backup method, file restoration methods, in a kind of application scenarios that file is backed up, when file need to back up to server from client, and configuration file is while also backing up to server, as shown in Figure 3, the method can comprise:

201, user end to server sends the first request.

Wherein, the first request issues configuration file for request server, in the time that client need to arrive server by file backup, can send the first request to server end, to obtain configuration file from server end.

202, the configuration file that client server sends.

Wherein, after server is received the first request of client transmission, just configuration file can be sent to client, now client just can receive the configuration file that server sends, and comprises the configuration information of at least one historical backup file in this configuration file.Wherein, configuration information comprises but is not limited to backup file name, file size, file type, file layout, MD5, client stores path, server end store path, rename instruction, old file name.Certainly,, in the time backing up for the first time, in configuration file, do not comprise any content.The form of the configuration information comprising in configuration file can be database format, can be also XML form.Taking XML form as example, the configuration information comprising in configuration file can be as follows:

Wherein, <name>xx.jpg</na me> represents the backup file of file xx.jpg by name, <size>1123</size > represents that the file size of file is 1123, <type>photo</typ e> represents that the file type of file is picture, <format>jpg</for mat> represents that the file layout of file is jpg form, <md5>0ca175b9c0f726a831d895e2 69332461</md5> represents that the MD5 value of file is 0ca175b9c0f726a831d895e269332461, this field of <localpath>/mnt/sdcard/DCIM/C amera/</localpath> is used to indicate the store path of file in client, this field of <serverpath>/Server/media/pho to/</serverpath> is used to indicate the store path of file at server end, this field of <ischangename>0</ischangename> is used to indicate file in the whether rename of when backup, if rename is not carried out in 0 expression, if 1 shows to have carried out rename, this field of <oldname>xx.jpg</oldname> is used to indicate the old file name of file.

It should be noted that, the form of the embodiment of the present invention to configuration file, and the form of each field of the configuration information that comprises of configuration file does not limit.

203, client, according to the configuration information of at least one the historical backup file in configuration file, is determined fileinfo set to be backed up from the attribute information of at least one file to be backed up.

Wherein, after the configuration file that client sends to server, just can obtain at least one file to be backed up with the attribute information of backup file according to the configuration information of at least one the historical backup file comprising in this configuration file and at least one, which file has backuped to server, which file does not also backup to server, so just can will finally will back up to the attribute information combination producing fileinfo set to be backed up of file to be backed up of server.Wherein, in this fileinfo set to be backed up, comprising at least one needs backup but does not also back up to the attribute information of the file to be backed up of server.

Optionally, after client gets fileinfo set to be backed up, in the time comprising the attribute information of at least two files to be backed up that need to back up to server in fileinfo set to be backed up, client can judge that whether the filename of the first file to be backed up is identical with the filename of the second file to be backed up, and/or, judge that whether the filename of the first file to be backed up and the filename of historical file to be backed up be identical, concrete judge in the file all to be backed up in fileinfo set to be backed up, whether there is the identical but file content of filename, and need to back up to the different files under the same catalogue of server, whether and it is identical with the backup file name of the backup file under this catalogue to judge that any one in the file all to be backed up in fileinfo set to be backed up need to back up to the filename of the file to be backed up under certain catalogue in server.Certainly, in the time only comprising the attribute information of a file to be backed up that need to back up to server in fileinfo set to be backed up, whether the backup file name that the filename that only needs to judge this file to be backed up that need to back up to server and this file need to backup to the historical backup file under the catalogue of server is identical, when judging the filename that needs to revise this when identical and need to back up to the file to be backed up of server.For example, when in fileinfo set to be backed up, comprise two files to be backed up attribute information time, the result that obtains of judgement shows that the filename of the first file to be backed up is identical with the filename of the second file to be backed up but content is different and the first file to be backed up and the second file to be backed up need to back up under the same catalogue of server, or the filename of the first file to be backed up and this first file to be backed up need to back up to certain under the catalogue of server, and the backup name of backup file is identical but content is different, illustrate that so these files just can clash in the time backing up, can carry out following steps 204.

204, client is revised the filename of the first file to be backed up in fileinfo set to be backed up.

Wherein, when client obtains fileinfo set to be backed up, and when the attribute information that comprises at least two files to be backed up in this fileinfo set to be backed up, obtain the filename of the first file to be backed up identical with the filename of the second file to be backed up and need to back up under the same catalogue of server, or the filename that obtains the first file to be backed up is identical with the backup file name that it will back up to the historical backup file under the same catalogue of server, and now client just can be revised the filename of the first file to be backed up; In the time only comprising the attribute information of first file to be backed up in this fileinfo set to be backed up, the filename that obtains the first file to be backed up is identical with the backup file name that it will back up to the historical backup file under the same catalogue of server, and now client can be revised the filename of the first file to be backed up.Wherein, the first file to be backed up is any one in the file to be backed up that the attribute information of at least one file to be backed up of comprising in fileinfo set to be backed up is corresponding, the second file to be backed up is also any one in the file to be backed up that the attribute information of at least one file to be backed up of comprising in fileinfo set to be backed up is corresponding, and the first file to be backed up is different from the second file to be backed up.

It should be noted that, client need to all be carried out collision detection by the filename of all files to be backed up in fileinfo set to be backed up.Collision detection described in the embodiment of the present invention refers to that the filename that detects other files to be backed up in the file to be backed up whether filename of file to be backed up is corresponding with the attribute information that need to back up at least one file to be backed up in the fileinfo set to be backed up under same catalogue in server clashes, and whether the filename that detects file to be backed up clashes with the filename that it need to back up to the historical backup file under the catalogue of server.

For example, the first file to be backed up and the second file to be backed up are the final file that need to back up to server of determining, and the first file to be backed up and the second file to be backed up will back up under the same catalogue of server, the concrete grammar detecting so can be whether first detect the filename of the first file to be backed up and the second file to be backed up identical, if testing result shows that the first file to be backed up is identical with the filename of the second file to be backed up, whether identically next can detect the content of the first file to be backed up and the second file to be backed up according to other information that comprise in the attribute information of the first file to be backed up and the second file to be backed up, as whether identical with the file size of the second file to be backed up in being the detection file size of the first file to be backed up, also can be whether detect the MD5 of the first file to be backed up identical with the MD5 of the second file to be backed up etc., be understandable that, if can obtain fast testing result by judging that whether the file size of the first file to be backed up is identical with the file size of the second file to be backed up, but the accuracy of this detection method is not high, if whether identical with the MD5 of the second file to be backed up by detecting the MD5 of the first file to be backed up, whether the content that the first file to be backed up and the second file to be backed up just can be detected comparatively is accurately identical, but the efficiency of this detection method is not high.Wherein, the method of the MD5 value of employing comparison document detects the high reason of testing result accuracy obtaining and is: each file can adopt MD5 algorithm to produce a MD5 value, MD5 value can be with a string representation, and the MD5 value that different files obtains is different, the MD5 value of file and people's fingerprint are similar, be " digital finger-print " for identifying different files, and if file is changed, the MD5 value of this file also can correspondence change.

It should be noted that, between file to be backed up, between file to be backed up and historical backup file, whether exist the detection method embodiment of the present invention of conflicting just simply to illustrate, the method of concrete collision detection can decide according to practical application scene, and the embodiment of the present invention is not done detailed restriction at this to the method for collision detection.

205, client generates file configuration information aggregate to be backed up.

Wherein, after inspection that all files to be backed up in the file to be backed up corresponding attribute information of at least one file to be backed up in fileinfo set to be backed up are all conflicted, and after the filename that has the file conflicting is modified, just can generate file configuration information aggregate to be backed up.Wherein, file configuration information aggregate to be backed up comprises the configuration information of all files to be backed up in fileinfo set to be backed up, concrete, the configuration information of file to be backed up comprises but is not limited to the backup file name of file to be backed up, the file size of file to be backed up, the file type of file to be backed up, the file layout of file to be backed up, the MD5 of file to be backed up, the client stores path of file to be backed up, the server end store path of file to be backed up, the rename instruction of file to be backed up, the old file name of file to be backed up, wherein rename instruction is used to indicate file to be backed up and whether has carried out rename.

It should be noted that, client can be to treat backup file to carry out collision detection, if conflict detected, after the filename of file to be backed up is modified, directly generate the configuration information of this file to be backed up, then other files to be backed up for the treatment of in backup file information aggregate carry out identical operation, obtain the configuration information of other files to be backed up, finally by file configuration information aggregate to be backed up the configuration information combination producing of all files to be backed up, also can be first all files to be backed up to be carried out to collision detection, and after the filename of amendment conflict file, the configuration information of all files to be backed up of regeneration, finally by file configuration information aggregate to be backed up the configuration information combination producing of all files to be backed up, the concrete generative process that the embodiment of the present invention is treated the set of backup file configuration information at this is not restricted.

206, client is added the configuration information of at least one file to be backed up in file configuration information aggregate to be backed up in configuration file to.

Wherein, after client generates file configuration information aggregate to be backed up, just can be according to file configuration information aggregate Reconfigurations file to be backed up, concrete, the configuration information of all files to be backed up in the configuration information of at least one file to be backed up comprising in file configuration information aggregate to be backed up is added in configuration file.

It should be noted that, it can be the configuration information of a file to be backed up of every generation, in the configuration file that the configuration information of this file to be backed up is added, also can be after the configuration information for the treatment of all files to be backed up all generates, the configuration information of all files to be backed up is together added in configuration file, the embodiment of the present invention does not limit at this.

207, configuration file is backed up to server by client, so that the original configuration file of server update.

Wherein, after the configuration information of the file to be backed up corresponding attribute information of all files to be backed up in fileinfo set to be backed up is added in configuration file, just the configuration file after upgrading can be backed up to server, after server receives the configuration file of client backup, just can the configuration file of storage in the past be replaced with the configuration file that receives newly, to ensure the configuration information of the All Files that comprises client backup in the configuration file of server end.

Optionally, after server successfully receives the configuration file of client transmission, send backup success response to client, backed up successfully so that client is learnt configuration file.

208, client is according to file configuration information aggregate to be backed up, backs up file to be backed up that the configuration information of at least one file to be backed up in file configuration information aggregate to be backed up is corresponding to server.

Wherein, after configuration file is backed up to server by client, just can be according to file configuration information aggregate to be backed up, by the file backup to be backed up corresponding configuration information of all files to be backed up in the configuration information of at least one file to be backed up comprising in file configuration information aggregate to be backed up to server.Concrete, can be according to the server end store path comprising in the configuration information in file configuration information aggregate to be backed up by file backup to be backed up to the destination path of server.

209, the backup failure response that client server sends.

Wherein, if in backup procedure, the 3rd file backup failure to be backed up, for file corresponding to configuration information that ensures to comprise in configuration file all successfully backs up to server, server can send backup failure response to client, this backup failure response is used for notifying client backup the 3rd file failure to be backed up, and the 3rd file to be backed up is any one file to be backed up in the file to be backed up that the attribute information of at least one file to be backed up in fileinfo set to be backed up is corresponding.

210, client responds according to backup failure, and the configuration information of the 3rd file to be backed up is deleted from configuration file.

Wherein, after the backup failure response that client sends to server, just can respond Reconfigurations file according to backup failure, concrete, can be that the configuration information of the 3rd file to be backed up is deleted from configuration file, if the configuration information of the file of backup failure is not deleted from configuration file, while backup so afterwards, client can think that this file successfully backs up to server, cause the file of this backup failure forever cannot back up successfully, in a word, ensure that the configuration information in configuration file is consistent with the file of server end backup.

211, configuration file is again backed up to server by client, so that the existing configuration file of server update.

Wherein, after the file of backup failure is deleted from configuration file, the configuration file after upgrading can be backed up to server again, so that server is preserved up-to-date configuration file.

Optionally, the 3rd file to be backed up can be put into while backup next time, then back up.

212, client shows the configuration information of the file that has backed up to server in client according to configuration file.

Wherein, in the time that client need to be checked the information of the All Files that has backed up to server, can be real-time according to configuration file, fast the information of the All Files of backup server is shown.

And, in the time that client need to be checked the information of the All Files that has backed up to server, can be directly real-time according to configuration file, fast the information of the All Files of backup server is shown.

In a kind of application scenarios that file is recovered, when downloading and back up to the file of server from server, and configuration file be also need to download from server time, and as shown in Figure 4, the method can comprise:

301,, in the time that client need to be from server recovery file, user end to server sends the first request.

Wherein, the first request issues configuration file for request server.In the time that client need to be recovered to back up to the file of server from server, can send the first request to server.For example, in the time having File lose to download the file of losing from server end under certain catalogue of client, client just can send the first request to server.

302, the configuration file that client server sends.

Wherein, after user end to server sends the first request, server can be sent to client by up-to-date configuration file, the configuration file that now client just can reception server sends.

303, client is obtained and is treated the set of recovery file configuration information according to configuration file.

Wherein, after the configuration file that client sends to server, just can obtain and treat the set of recovery file configuration information according to configuration file, concrete, client can search under this path, whether there is file identical with the old file name for the treatment of recovery file and that content is identical according to the client stores path of configuration information in configuration file, illustrate that if identical this file does not need to recover, if different, illustrate that this file need to return to client, so just, can obtain treating the set of recovery file configuration information, wherein treat to comprise at least one in the set of recovery file configuration information and treat the configuration information of recovery file, the configuration information for the treatment of recovery file comprise following at least one: the backup file name for the treatment of recovery file, treat the file size of recovery file, treat the file type of recovery file, treat the file layout of recovery file, treat the MD5 of recovery file, treat the client stores path of recovery file, treat the server end store path of recovery file, treat the rename instruction of recovery file, treat the old file name of recovery file etc.

It should be noted that, in the embodiment of the present invention, search the method for the collision detection in determination methods and the embodiment of the present invention step 204 that whether has and the file that content is identical identical with the old file name for the treatment of recovery file under this path according to the client stores path of configuration information in configuration file similar, can be with reference to the specific descriptions for collision detection method in the embodiment of the present invention for the specific descriptions of searching the determination methods that whether has and file that content identical identical with the old file name for the treatment of recovery file under certain path in the embodiment of the present invention, this is no longer going to repeat them for the embodiment of the present invention.

304, client, according to the first configuration information for the treatment of recovery file, judges that first revises in the time backing up to server until the filename of recovery file, treats that according to first the old file name amendment first of recovery file treats the backup file name of recovery file.

Wherein, after client obtains treating the set of recovery file configuration information, just can the rename in the configuration information of recovery file indicate to judge whether first carried out rename in the time backing up until recovery file according to comprise first in recovery file information aggregate, in the time backing up, carry out rename until recovery file when judgement obtains first, needed to treat that by first the backup file name of recovery file is revised as old file name.First treat recovery file be treat in the set of recovery file configuration information at least one configuration information for the treatment of recovery file corresponding treat any one in recovery file.

305, client, according to the first configuration information for the treatment of recovery file, judges that first treats that the old file name of recovery file is identical with the filename of the first file.

Wherein, after getting and treating the set of recovery file configuration information, also need to judge under this path, whether there be filename but file that content different identical from the old file name for the treatment of recovery file according to the old file name for the treatment of recovery file and the client stores path for the treatment of recovery file.Concrete can be, judgement obtains the identical of the first old file name for the treatment of recovery file and the first file, still first treats that the content of recovery file is different from the first file, and the first file is the file for the treatment of under the client stores path of recovery file first.

306, client is revised the filename of the first file.

Wherein, when obtaining second, judgement treats that the old file name of recovery file is identical with the filename of the first file, but after both content differences, in order to ensure to treat that by second recovery file downloads to client accurately, the filename of the first file can be modified.

When by corresponding the configuration information for the treatment of the recovery file that needs in the set of recovery file configuration information treat that recovery file carries out the judgement of step 305-step 306 and does corresponding processing after, just can carry out following steps 307.

It should be noted that, step 305 does not have sequencing with the execution of step 306, and the embodiment of the present invention does not limit step 305 and the execution sequence of step 306.

307, client is according to treating the set of recovery file configuration information, download treat the configuration information of the recovery file that needs in recovery file information aggregate corresponding treat recovery file.

Wherein, client can, according to the client stores path for the treatment of in the set of recovery file configuration information, download to client by the recovery file for the treatment of corresponding to configuration information for the treatment of the recovery file that needs in the set of recovery file configuration information.

In order to facilitate those skilled in the art's understanding, the embodiment of the present invention further illustrates file backup and file restoration methods, for example, client is mobile phone terminal, and this mobile phone terminal comprises two SD cards, and there are two pictures that filename is identical in these two SD cards, and the content difference of this two pictures, this two pictures need to be backuped under the same catalogue of cloud server now, the old file name of this two pictures is A.jpg, wherein a pictures at the store path of mobile phone terminal is :/sdcard0/DCIM/Camera/, another pictures at the store path of mobile phone terminal is /sdcard1/DCIM/Camera/.

Concrete process can be: first, mobile phone terminal can be determined the file that this two pictures does not also back up in server according to the information of configuration file and this two pictures, and this two pictures is finally definite need to back up to server file; Secondly, mobile phone terminal carries out collision detection, discovery need to back up to that the filename of two pictures of server is identical and content is different, and will back up under the same catalogue of server, now mobile phone terminal can carry out rename by a pictures wherein, for example, client changes the filename of the picture under be stored in/sdcard1/DCIM/Camera/ path into COPYA.jpg; Again, mobile phone terminal can generate the configuration information of two pictures, and the configuration information of this two pictures is added in configuration file, and for example, configuration file can be as follows:

Then, in the time that mobile phone terminal need to recover this two pictures, just can directly know that according to configuration file wherein a pictures has carried out rename in the time backing up, and can learn that according to the old file name field of configuration information in configuration file this picture carries out rename filename before, like this in the time carrying out file recovery, just can the filename of this picture be revised as to backup filename before according to old file name field, and according to client stores path field, can accurately this two pictures be returned to mobile phone terminal.

And the configuration information in configuration file also comprises the store path of backup file in client, in the time that needs carry out file recovery, just can file be recovered accurately according to client stores path.

Another embodiment of the present invention provides a kind of file backup device, as shown in Figure 5, comprising: acquiring unit 41, generation unit 42, adding device 43, the first backup units 44.

Acquiring unit 41, for obtaining configuration file; Wherein, the configuration information that comprises at least one historical backup file in described configuration file.

Generation unit 42, for the attribute information of the described configuration file that obtains according to described acquiring unit 41 and at least one file to be backed up, generates file configuration information aggregate to be backed up; Wherein, the configuration information that described file configuration information aggregate to be backed up comprises file to be backed up described at least one.

Adding device 43, for file configuration information aggregate described to be backed up that described generation unit 42 is obtained described described at least one the configuration information of file to be backed up add in described configuration file.

The first backup units 44, for the file configuration information aggregate described to be backed up that obtains according to described generation unit 42, back up the described file to be backed up that the configuration information of file to be backed up is corresponding described at least one in described file configuration information aggregate to be backed up to server.

Further, as shown in Figure 6, described file backup device, can also comprise: display unit 45.

Display unit 45, for showing the configuration information of the file that has backed up to described server in client according to described configuration file.

Further, described acquiring unit 41 can comprise: sending module 411, receiver module 412.

Sending module 411, for sending the first request to described server; Wherein, described the first request is used for asking described server to issue described configuration file.

Receiver module 412, the described configuration file sending for receiving described server.

Described file backup device, can also comprise: the second backup units 46.

The second backup units 46, for described adding device 43 by described file configuration information aggregate to be backed up described described at least one the configuration information of file to be backed up add described configuration file in after, described configuration file is backed up to described server, so that the original configuration file of described server update.

Further, described generation unit 42 can comprise: determination module 421, judge modified module 422, generation module 423.

Determination module 421, for according to the configuration information of described configuration file described historical backup file described at least one, determines to be backed up fileinfo set the attribute information of file to be backed up from described described at least one; In described fileinfo set to be backed up, comprise at least one and need to back up to the attribute information of the described file to be backed up of described server.

Judge modified module 422, for comprise a described file to be backed up that need to back up to described server when described fileinfo set to be backed up attribute information time, judge that the filename of the described described file to be backed up that need to back up to described server is identical with the filename of described historical backup file, revise the filename of the described described file to be backed up that need to back up to described server; In the time comprising the attribute information of at least two described files to be backed up that need to back up to described server in described fileinfo set to be backed up, the filename that judges described the first file to be backed up is identical with the filename of the second file to be backed up, and/or, the filename of described the first file to be backed up is identical with the filename of described history file to be backed up, revises the filename of described the first file to be backed up; Wherein, the attribute information of the attribute information of described the first file to be backed up and described the second file to be backed up is contained in described fileinfo set to be backed up.

Generation module 423, for generating described file configuration information aggregate to be backed up; Wherein, described file configuration information aggregate to be backed up comprise described at least one need to back up to the configuration information of the described file to be backed up of described server.

Further, described file backup device can also comprise: receiving element 47, delete cells 48.

Receiving element 47, be used in described the first backup units 44 according to described file configuration information aggregate to be backed up, back up the described file to be backed up that the configuration information of file to be backed up is corresponding described at least one in described file configuration information aggregate to be backed up to after described server, receive the backup failure response that described server sends; Wherein, the response of described backup failure is used for notifying described client backup the 3rd file failure to be backed up, and described the 3rd file to be backed up is any one file to be backed up that need to back up at least one file to be backed up of described server.

Delete cells 48 for the described backup failure response obtaining according to described receiving element 47, is deleted the configuration information of described the 3rd file to be backed up from described configuration file.

Described the second backup units 46, also for described configuration file is backed up to described server again, so that the existing configuration file of described server update.

Further, described configuration information comprise following at least one: backup file name, file size, file type, file layout, Message Digest Algorithm 5 MD5, client stores path, server end store path, rename instruction, old file name.

The file backup device that the embodiment of the present invention provides, by the configuration information of at least one historical backup file and the attribute information of at least one file to be backed up that comprise in the configuration file getting, obtain file configuration information aggregate to be backed up, the configuration information that comprises at least one file to be backed up in this file configuration information aggregate to be backed up, then the configuration information of at least one file to be backed up in file configuration information aggregate to be backed up is added in configuration file, and back up file to be backed up that the configuration information of at least one file to be backed up in file configuration information aggregate to be backed up is corresponding to server according to file configuration information aggregate to be backed up, solve the collision problem in file backup process.

Another embodiment of the present invention provides a kind of file recovery device, as shown in Figure 7, comprising: acquiring unit 51, judgement amendment unit 52, download unit 53.

Acquiring unit 51, in the time that client need to be from server recovery file, obtains and treats the set of recovery file configuration information according to configuration file; Wherein, described in, treat to comprise at least one in the set of recovery file configuration information and treat the configuration information of recovery file.

Judgement amendment unit 52, for according to the first configuration information for the treatment of recovery file, judge that described first revises in the time backing up to described server until the filename of recovery file, revise the described first backup file name for the treatment of recovery file according to the described first old file name for the treatment of recovery file; Wherein, described first treat recovery file treat described in being described in the set of recovery file configuration information at least one configuration information for the treatment of recovery file corresponding treat any one in recovery file.

Download unit 53, for treat described in downloading the set of recovery file configuration information described at least one treat the configuration information of recovery file corresponding treat recovery file.

Further, as shown in Figure 8, described file recovery device can also comprise: transmitting element 54, receiving element 55.

Transmitting element 54, for described in the time that client need to be from server recovery file, described acquiring unit 51 sends the first request to described server before obtaining and treat the set of recovery file configuration information according to configuration file; Wherein, described the first request is used for asking described server to issue described configuration file;

Receiving element 55, the described configuration file sending for receiving described server.

Further, described judgement amendment unit 52, also for treat described in downloading at described download unit the set of recovery file information configuration described at least one treat the configuration information of recovery file corresponding treat recovery file before, according to the described first configuration information for the treatment of recovery file, judge that described first treats that the old file name of recovery file is identical with the filename of the first file, revise the filename of described the first file; Wherein, described the first file is the file for the treatment of under the client stores path of recovery file described first.

The file recovery device that the embodiment of the present invention provides, in the time that client need to be from server recovery file, obtain and treat the set of recovery file configuration information according to configuration file, this treats to comprise at least one in the set of recovery file configuration information and treats the configuration information of recovery file, according to the first configuration information for the treatment of recovery file, judge that first revises in the time backing up to server until the filename of recovery file, treat that according to first the old file name amendment first of recovery file treats the backup file name of recovery file, then download treat at least one in the set of recovery file configuration information treat the configuration information of recovery file corresponding treat recovery file, in the time of needs recovery file, can download and treat recovery file according to configuration file, solve in the time that file backup clashes, the problem that the File lose that the needs that occur recover or filename are modified.

Another embodiment of the present invention provides a kind of file backup device, as shown in Figure 9, comprising:

At least one processor 61, storer 62, communication interface 63 and bus 64, this at least one processor 61, storer 62 and communication interface 63 are connected by bus 64 and complete mutual communication, wherein:

Described bus 64 can be industry standard architecture (Industry Standard Architecture, ISA) bus, peripheral component interconnect (Peripheral Component Interconnect, PCI) bus or extended industry-standard architecture (Extended Industry Standard Architecture, EISA) bus etc.This bus 64 can be divided into address bus, data bus, control bus etc.For ease of representing, in Fig. 9, only represent with a thick line, but do not represent only to have the bus of a bus or a type.

Described storer 62 is for stores executable programs code, and this program code comprises computer-managed instruction.Storer 62 may comprise high-speed RAM storer, also may also comprise nonvolatile memory (non-volatile memory), for example at least one magnetic disk memory.

Described processor 61 may be a central processing unit (Central Processing Unit, CPU), or specific integrated circuit (Application Specific Integrated Circuit,, or be configured to implement one or more integrated circuit of the embodiment of the present invention ASIC).

Described communication interface 63, is mainly used in realizing the communication between the equipment of the present embodiment.

Described processor 61, for carrying out the executable program code of described storer 62 storages, concrete for carrying out following operation:

Described processor 61, for obtaining configuration file; Wherein, the configuration information that comprises at least one historical backup file in described configuration file; According to the attribute information of described configuration file and at least one file to be backed up, generate file configuration information aggregate to be backed up; Wherein, the configuration information that described file configuration information aggregate to be backed up comprises file to be backed up described at least one; By described in described file configuration information aggregate to be backed up described at least one the configuration information of file to be backed up add in described configuration file; According to described file configuration information aggregate to be backed up, back up the described file to be backed up that the configuration information of file to be backed up is corresponding described at least one in described file configuration information aggregate to be backed up to server.

Further, described storer 62, also for storing described configuration file.

Further, described processor 61, also for showing the configuration information of the file that has backed up to described server in client according to described configuration file.

Further, described processor 61, also for sending the first request to described server; Wherein, described the first request is used for asking described server to issue described configuration file; Receive the described configuration file that described server sends.

Described processor 61, also for described by described file configuration information aggregate to be backed up described described at least one the configuration information of file to be backed up add described configuration file in after, described configuration file is backed up to described server, so that the original configuration file of described server update.

Further, described processor 61 also, for according to the configuration information of described at least one historical backup file of described configuration file, is determined fileinfo set to be backed up from the attribute information of described at least one file to be backed up; In described fileinfo set to be backed up, comprise at least one and need to back up to the attribute information of the described file to be backed up of described server; In the time comprising the attribute information of a described file to be backed up that need to back up to described server in described fileinfo set to be backed up, judge that the filename of the described described file to be backed up that need to back up to described server is identical with the filename of described historical backup file, revise the filename of the described described file to be backed up that need to back up to described server; In the time comprising the attribute information of at least two described files to be backed up that need to back up to described server in described fileinfo set to be backed up, the filename that judges described the first file to be backed up is identical with the filename of the second file to be backed up, and/or, the filename of described the first file to be backed up is identical with the filename of described history file to be backed up, revises the filename of described the first file to be backed up; Wherein, the attribute information of the attribute information of described the first file to be backed up and described the second file to be backed up is contained in described fileinfo set to be backed up; Generate described file configuration information aggregate to be backed up; Wherein, described file configuration information aggregate to be backed up comprise described at least one need to back up to the configuration information of the described file to be backed up of described server.

Further, described processor 61, also for described according to described file configuration information aggregate to be backed up, back up the described file to be backed up that the configuration information of file to be backed up is corresponding described at least one in described file configuration information aggregate to be backed up to server, receive the backup failure response that described server sends; Wherein, the response of described backup failure is used for notifying described client backup the 3rd file failure to be backed up, and described the 3rd file to be backed up is any one file to be backed up that need to back up at least one file to be backed up of described server; According to described backup failure response, the configuration information of described the 3rd file to be backed up is deleted from described configuration file; Described configuration file is backed up to described server again, so that the existing configuration file of described server update.

Another embodiment of the present invention provides a kind of file recovery device, as shown in figure 10, comprise: at least one processor 71, storer 72, communication interface 73 and bus 74, this at least one processor 71, storer 72 and communication interface 73 are connected by bus 74 and complete mutual communication, wherein:

Described bus 74 can be industry standard architecture (Industry Standard Architecture, ISA) bus, peripheral component interconnect (Peripheral Component Interconnect, PCI) bus or extended industry-standard architecture (Extended Industry Standard Architecture, EISA) bus etc.This bus 74 can be divided into address bus, data bus, control bus etc.For ease of representing, in Figure 10, only represent with a thick line, but do not represent only to have the bus of a bus or a type.

Described storer 72 is for stores executable programs code, and this program code comprises computer-managed instruction.Storer 72 may comprise high-speed RAM storer, also may also comprise nonvolatile memory (non-volatile memory), for example at least one magnetic disk memory.

Described processor 71 may be a central processing unit (Central Processing Unit, CPU), or specific integrated circuit (Application Specific Integrated Circuit,, or be configured to implement one or more integrated circuit of the embodiment of the present invention ASIC).

Described communication interface 73, is mainly used in realizing the communication between the equipment of the present embodiment.

Described processor 71, for carrying out the executable program code of described storer 72 storages, concrete for carrying out following operation:

Described processor 71, in the time that client need to be from server recovery file, obtains and treats the set of recovery file configuration information according to configuration file; Wherein, described in, treat to comprise at least one in the set of recovery file configuration information and treat the configuration information of recovery file; According to the first configuration information for the treatment of recovery file, judge that described first revises in the time backing up to described server until the filename of recovery file, revise the described first backup file name for the treatment of recovery file according to the described first old file name for the treatment of recovery file; Wherein, described first treat recovery file treat described in being described in the set of recovery file configuration information at least one configuration information for the treatment of recovery file corresponding treat any one in recovery file; Described in download, treat in the set of recovery file configuration information described at least one treat the configuration information of recovery file corresponding treat recovery file.

Further, described storer 72, also for storing described configuration file.

Further, described processor 71, also for described in the time that client need to be from server recovery file, before obtaining and treat the set of recovery file configuration information according to configuration file, send the first request to described server; Wherein, described the first request is used for asking described server to issue described configuration file; Receive the described configuration file that described server sends.

Further, described processor 71, also for described in described download, treat the set of recovery file information configuration described at least one treat the configuration information of recovery file corresponding treat recovery file before, according to the described first configuration information for the treatment of recovery file, judge that described first treats that the old file name of recovery file is identical with the filename of the first file, revise the filename of described the first file; Wherein, described the first file is the file for the treatment of under the client stores path of recovery file described first.

Another embodiment of the present invention provides a kind of file backup and recovery system, as shown in figure 11, comprising: file backup device 81, file recovery device 82 and server 83.

Described file backup device 81, for obtaining configuration file; Wherein, the configuration information that comprises at least one historical backup file in described configuration file; According to the attribute information of described configuration file and at least one file to be backed up, generate file configuration information aggregate to be backed up; Wherein, the configuration information that described file configuration information aggregate to be backed up comprises file to be backed up described at least one; By described in described file configuration information aggregate to be backed up described at least one the configuration information of file to be backed up add in described configuration file; According to described file configuration information aggregate to be backed up, back up the described file to be backed up that the configuration information of file to be backed up is corresponding described at least one in described file configuration information aggregate to be backed up to described server 83.

Described file recovery device 82, for when needs are during from server 83 recovery file, obtains and treats the set of recovery file configuration information according to configuration file; Wherein, described in, treat to comprise at least one in the set of recovery file configuration information and treat the configuration information of recovery file; According to the first configuration information for the treatment of recovery file, judge that described first revises in the time backing up to described server 83 until the filename of recovery file, revise the described first backup file name for the treatment of recovery file according to the described first old file name for the treatment of recovery file; Wherein, described first treat recovery file treat described in being described in the set of recovery file configuration information at least one configuration information for the treatment of recovery file corresponding treat any one in recovery file; Described in download, treat in the set of recovery file configuration information described at least one treat the configuration information of recovery file corresponding treat recovery file.

Described server 83, for the described file to be backed up corresponding to configuration information of file to be backed up described at least one of storing file configuration information aggregate to be backed up that described file backup device 81 backs up.

In the time of the 3rd backup file backup failure, send backup failure response to described file backup device 81.

Further, described server 83, the configuration file also backing up for storing described file backup device 81, receive the first request that described file backup device 81 and described file recovery device 82 send, and send described configuration file to described file backup device and described file recovery device 82, in the time of the 3rd backup file backup failure, send backup failure response to described file backup device 81, receive the described configuration file that described file backup device 81 backs up again, and upgrade existing configuration file.

The file backup that the embodiment of the present invention provides and recovery system, by the configuration information of at least one historical backup file and the attribute information of at least one file to be backed up that comprise in the configuration file getting, obtain file configuration information aggregate to be backed up, the configuration information that comprises at least one file to be backed up in this file configuration information aggregate to be backed up, then the configuration information of at least one file to be backed up in file configuration information aggregate to be backed up is added in configuration file, and back up file to be backed up that the configuration information of at least one file to be backed up in file configuration information aggregate to be backed up is corresponding to server according to file configuration information aggregate to be backed up, in the time that client need to be from server recovery file, download the file that needs recovery from server according to configuration file, both solved the collision problem in file backup process.Also solve in the time that file backup clashes the problem that the File lose that the needs of appearance recover or filename are modified.

And, in the time that client need to be checked the information of the All Files that has backed up to server, can be directly real-time according to configuration file, fast the information of the All Files of backup server is shown, and the configuration information in configuration file also comprises the store path of backup file in client, in the time that needs carry out file recovery, just can file be recovered accurately according to client stores path.

Through the above description of the embodiments, those skilled in the art can be well understood to the mode that the present invention can add essential common hardware by software and realize, and can certainly pass through hardware, but in a lot of situation, the former is better embodiment.Based on such understanding, the part that technical scheme of the present invention contributes to prior art in essence in other words can embody with the form of software product, this computer software product is stored in the storage medium can read, as the floppy disk of computing machine, hard disk or CD etc., comprise that some instructions are in order to make a computer equipment (can be personal computer, server, or the network equipment etc.) carry out the method described in each embodiment of the present invention.

The above; be only the specific embodiment of the present invention, but protection scope of the present invention is not limited to this, any be familiar with those skilled in the art the present invention disclose technical scope in; the variation that can expect easily or replacement, within all should being encompassed in protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion with the protection domain of described claim.

Claims

1. a file backup method, is characterized in that, comprising:

2. file backup method according to claim 1, is characterized in that, also comprises:

3. file backup method according to claim 1 and 2, is characterized in that, described in obtain configuration file, comprising:

Receive the described configuration file that described server sends;

4. file backup method according to claim 1 and 2, is characterized in that, describedly generates file configuration information aggregate to be backed up according to the attribute information of described configuration file and at least one file to be backed up, comprising:

5. file backup method according to claim 1, it is characterized in that, described according to described file configuration information aggregate to be backed up, back up the described file to be backed up that the configuration information of file to be backed up is corresponding described at least one in described file configuration information aggregate to be backed up to server, also comprise:

6. according to the file backup method described in any one in claim 1-5, it is characterized in that,

7. a file restoration methods, is characterized in that, comprising:

8. file restoration methods according to claim 7, is characterized in that,, in the time that client need to be from server recovery file, before obtaining and treat the set of recovery file configuration information, also comprises according to configuration file described:

Receive the described configuration file that described server sends.

9. file restoration methods according to claim 7, is characterized in that, described in described download, treat in the set of recovery file information configuration described at least one treat the configuration information of recovery file corresponding treat recovery file before, also comprise:

10. according to the file restoration methods described in any one in claim 7-9, it is characterized in that,

11. 1 kinds of file backup devices, is characterized in that, comprising:

12. file backup devices according to claim 11, is characterized in that, also comprise:

13. according to the file backup device described in claim 11 or 12, it is characterized in that, described acquiring unit, comprising:

Described file backup device, also comprises:

14. according to the file backup device described in claim 11 or 12, it is characterized in that, described generation unit, comprising:

15. file backup devices according to claim 11, is characterized in that, also comprise:

16. 1 kinds of file recovery devices, is characterized in that, comprising:

17. file recovery devices according to claim 16, is characterized in that, also comprise:

18. file recovery devices according to claim 16, is characterized in that,