KR20190030406A - System for controlling file backup - Google Patents

Abstract

The present invention provides a system for controlling files stored in a backup storage not to be infected by a malicious code such as Ransomware when backing up the files to the backup storage. The system includes: a management apparatus generating a signature of each of the files to be backed up whenever a new file to be backed up is generated or edited, and transmitting a signature generation module which adds the signature to the file to a device which generates or edits the file to be backed up; and a signature verification and backup apparatus receiving the file to be backed up from the device which generates and edits the file, verifying the validity of the signature by generating a signature from the received file to be backed up and comparing a signature recently added to the received file to be backed up, and storing the received file to be backed up in the backup storage if the verification is successful.

Description

System for controlling file backup {SYSTEM FOR CONTROLLING FILE BACKUP}

The present invention relates to backup techniques, and more particularly, to a system for controlling file backup in backing up files to backup storage.

Recently, malicious code called Ransomware has been spreading and causing damage. Ransomware is a malicious program that infringes Internet users' computers and prevents them from encrypting internal documents, spreadsheets, picture files, etc., and then sends money to send a decryption key program. It is a compound word of ransom (ransom) and ware (product). It is a name attached to computer users' documents as' hostage 'and demand money.

When infected with Ransomware, the file is encrypted with a complicated algorithm and the contents can not be read even if the file is opened. It is often infected by running attachments sent via e-mail, social network services (SNS), instant messaging, etc., and can also be infected through website visits. Even if you remove the malicious code with the vaccine program, the encrypted file is not recovered and is called the worst malicious code ever. Hackers ask for money on the condition that they allow the file to be opened, which threatens to increase the amount of money and make it impossible to recover the file.

Until now, Ransomware support is blocking the execution of unknown processes like all other malicious codes. This method is meaningless when a new pattern of malicious code appears. Backing up all files on an hourly basis is known as the only way to prevent Ransomware. If you back up all your files over time, the files will continue to accumulate indiscriminately, so massive storage is essential. As a result, the same files are updated with overwrites to improve storage space efficiency. However, this method is also contaminated with storage by Ransomware. That is, after backing up a file to storage, if the same file locally is infected by Ransomware, the infected file is overwritten by the same file in the storage, and the file stored in the storage is also infected. For example, if a.dat file is already backed up to storage and the a.dat file stored on the local computer is infected by Ransomware, the a.dat file that is already backed up to storage The infected .dat file will be overwritten and eventually infected.

The present invention aims at providing a system for controlling a file stored in a backup storage to be infected by a malicious code such as a random software in backing up a file to backup storage.

A system for controlling file backup to backup storage according to one aspect includes a signature generation module for generating a signature of each file to be backed up and adding the signature to the backup file each time a new file is created or edited, To a device for creating or editing a file; And generating a signature on the received file to be backed up and verifying the validity of the signature by comparing the received signature with a recent signature added to the file to be backed up, And a signature verification and backup device for storing the received file to be backed up in the backup storage upon successful verification.

The signature verification and backup apparatus can directly store the file to be backed up in the backup storage if a file having the same file name as the file to be backed up does not exist in the backup storage.

Wherein the signature verification and backup apparatus further comprises a signature verification unit for verifying whether or not a signature of a file having the same file name as the file to be backed up exists in the backup storage, The file name of the file to be backed up may be changed and stored in the backup storage.

Wherein the signature verification and backup apparatus further comprises a signature verification unit for verifying whether or not a signature of a file having the same file name as the file to be backed up exists in the backup storage, The file having the same file name existing in the backup storage can be overwritten with the file to be backed up.

A system for controlling file backup to backup storage according to another aspect includes a signature generation module for generating a signature of each file to be backed up and adding the signature to the file to be backed up each time a new file is created or edited, A signature verification module for generating a signature from the file to be backed up and comparing the latest signature added to the file to be backed up to a device for creating or editing the file to be backed up; Device; And a backup device for receiving the file to be backed up, which has successfully verified the signature from the signature verification module, and storing the received file in the backup storage.

The backup device may store the file to be backed up in the backup storage as is, if the backup storage does not have a file with the same file name as the file to be backed up.

Wherein the backup device is configured to delete a file having the same file name as a file to be backed up from a previous signature among a plurality of signatures added to the file to be backed up, And the file name of the file to be backed up may be changed and stored in the backup storage in other cases.

Wherein the backup device is configured to delete a file having the same file name as a file to be backed up from a previous signature among a plurality of signatures added to the file to be backed up, The latest signature added is compared, and if it is the same, the file having the same file name existing in the backup storage can be overwritten with the file to be backed up.

A system for controlling file backup to backup storage according to another aspect includes a signature generation module that generates a signature of each file to be backed up and adds the signature to the backup file each time a new file is created or edited, A backup module for storing the file to be backed up in the backup storage upon successful validation of the signature added to the file, to a device for creating or editing the file to be backed up; And a signature validation module configured to receive the file to be backed up from which the signature is added from the signature generation module, generate a signature from the received file to be backed up, and compare the signature with the latest signature added to the file to be backed up And a signature verification device for transmitting the verification result to the backup module.

The backup module can directly store the file to be backed up in the backup storage if a file having the same file name as the file to be backed up does not exist in the backup storage.

Wherein the backup module is configured to, when a file having the same file name as the file to be backed up exists in the backup storage, to delete the old signature from the plurality of signatures added to the backup file, And the file name of the file to be backed up may be changed and stored in the backup storage in other cases.

Wherein the backup module is configured to, when a file having the same file name as the file to be backed up exists in the backup storage, to delete the old signature from the plurality of signatures added to the backup file, The latest signature added is compared, and if it is the same, the file having the same file name existing in the backup storage can be overwritten with the file to be backed up.

Unlike existing vaccine programs, the present invention does not require updating of new malicious codes.

In addition, the present invention utilizes a signature of a cryptographic technique to increase the security strength of a file that fails to validate the signature because the backup is blocked from the source.

In addition, when the file is backed up to the backup storage, the present invention can update the same file to overwrite the same file, thereby enhancing the space efficiency of the backup storage and preventing infection by the malicious code of the backup storage.

1 is a block diagram illustrating a file backup control system according to an embodiment of the present invention.
2 is a diagram illustrating a process of adding a signature to a file according to an embodiment of the present invention.
3 is a flow diagram of one embodiment illustrating a method for controlling file backup in the system of FIG.
4 is a flow diagram of another embodiment illustrating a method for controlling file backup in the system of FIG.
5 is a diagram illustrating a file backup control system according to another embodiment of the present invention.
6 is a diagram illustrating a file backup control system according to another embodiment of the present invention.

The foregoing and other objects, features and advantages of the present invention will become more apparent from the following detailed description of the present invention when taken in conjunction with the accompanying drawings, in which: There will be. In the following description, well-known functions or constructions are not described in detail since they would obscure the invention in unnecessary detail. Hereinafter, a preferred embodiment of the present invention will be described in detail with reference to the accompanying drawings.

1, a file backup control system according to an embodiment of the present invention includes a management server 120, a signature verification and backup server 130, And a backup storage 140, wherein the client device 110 communicates with a file backup control system to back up locally stored files to the backup storage 140.

The backup storage 140 is a storage device connected to the client device 110 and the communication network 150 and connected to the client device 110 in a wired manner or connected to a network such as a local area network (LAN), a peer-to- (WAN), or a network that may be implemented as a global network, commonly known as the Internet. The backup storage 140 may be any of a variety of devices, including, but not limited to, cloud storage, network attached storage, or other computing devices, server-based computing devices, PDAs, Or the like. Preferably, the backup storage 140 may be a cloud storage such as a drop box or a Google Drive that provides API (Application Programming Interface) for reading, writing, and storing files.

The communication network 150 is a medium used for providing communication links between various devices and systems connected to each other. Communication network 150 may include connections such as wires, wireless communication links, or fiber optic cables. The communication network 150 may be any of a wide area network (WAN), a local area network (LAN), a WAN or LAN wireless network, a mobile network, a virtual private network (VPN) Or a variety of different communication technologies, such as a Public Switched Telephone Network (PSTN) or the like.

The management server 120 downloads the signature generation module 121 to the client device 110 that intends to use the file backup service. The client device 110 is a device having a communication function such as a notebook computer, a desktop computer, a tablet PC, or a smart phone. However, the present invention is not limited thereto, and the client device 110 is not limited as long as it is capable of generating a file and capable of communication. The management server 120 may be a dedicated server of a provider providing a file backup service, or may be an application store such as Google Play.

The signature generation module 121 may be an application program installed in the client device 110. The signature generation module 121 identifies a file to be backed up. For example, if a user stores a file in a specific folder, the file is identified as a file to be backed up. Alternatively, if the user selects a file stored in an arbitrary folder and selects the backup menu by pressing the right button of the mouse, the selected file is identified as a file to be backed up. Or the file stored in the backup storage 120 is opened by the user and is opened and edited and stored, the edited file is identified as a file to be backed up. The specific folder may be designated by the user.

The signature generation module 121 generates a signature from the identified file if there is no signature in the identified file, and adds the signature to the identified file. For example, when a user stores a file in a specific folder, the signature generation module 121 generates a signature of the file stored in the specific folder and adds the signature to the file. Alternatively, when a user selects a file stored in an arbitrary folder and selects a backup menu by pressing the right button of the mouse, the signature generation module 121 checks whether the file has a signature and generates a signature of the file if there is no signature And add it to the file. Since the signature is generated from the file, each file is unique to each file. The signature generation module 121 can change the extension of the file after adding a signature to the file. Signatures are generated from the files to be backed up and are publicly available such as RSA (Rivest Shamir Adleman), DSA (Digital Signature Algorithm), KCDSA (Korean Certificate-based Digital Signature Algorithm), ECDSA (Elliptic Curve Digital Signature Algorithm) (MAC) such as a hash-based message authentication code (HMAC), a cipher block chaining message authentication code (CBC-MAC), or a Galois message authentication code (GMAC) , SHA2, SHA3, MD5, etc., or a chuck-sum.

The signature generation module 121 adds at least two signatures to the file to be backed up. In the case of a newly generated file, a signature generated from the file and a signature (or a null value) predetermined in advance are added. Accordingly, it can be seen that the file is a newly generated file through the signature promised in advance. If a file that already has a signature added is edited, a signature is generated from the edited file each time the file is edited and added to the file. Therefore, all edited files can be added from the signature created when the file was first created to the signature created after the last edit. When a new signature is created for each new file and each file is edited, the size of the file can be increased. Therefore, only the latest signature and the signature immediately before can be stored.

2 is a diagram illustrating a process of adding a signature to a file according to an embodiment of the present invention. 2 (a) shows an example in which a signature is first added to a file to be backed up in the client device 110, in which a previously promised value is inserted or left blank in a signature field 1, a signature generated in the file, Enter '121Ndq45'. Here, the signature field may be a specific area of the header of the file. 2 (a) is modified by the user. In the signature field 2, a signature generated from the modified file, for example, 'a92hp765' is added. In the signature field 1, That is, the signature created in (a) of FIG. 2, for example, '121Ndq45' is added. FIG. 3C shows a case where the user has modified the file shown in FIG. 2B. In the signature field 2, a signature generated from the modified file, for example, '47a3Rq65' That is, the signature generated in (b) of FIG. 2 and stored in the signature field 2, for example, 'a92hp765' is added.

The signature generation module 121 generates a new signature of the edited file when the user opens a file having the signature added thereto stored in the backup storage 140, Add both the previous signature and the new signature after the edit to the file. In the embodiment of the present invention, the file stored in the backup storage 140 has already been added with a signature that has already been successfully validated.

The signature generation module 121 adds a signature to a file to be backed up and sends the file to the signature verification and backup server 130 to request a backup.

The signature verification and backup server 130 verifies the validity of the most recent signature added to the file received from the signature generation module 121. The signature verification and backup server 130 validates the signature by generating a signature from the file requested to be backed up and comparing it with the most recent signature added to the file. If the signatures match, it is determined that the validation is successful, and if the signatures do not match, it is determined that the validation fails.

The validation fails if: When a malicious code, such as Rangumware, modifies an unsigned file stored in the client device 110 and adds an arbitrary signature to the modulated file, the arbitrary signature is not generated from the modulated file , The signature validation of the modulated file fails. Or, if malicious code, such as Ransomware, modifies a file to which a signature has been added, and then adds the existing signature to the tampered file, the signature generated from the tampered file will be different from the existing signature because the file has been tampered with, Validation fails.

The signature verification and backup server 130 stores the file that has successfully verified the signature in the backup storage 140 and blocks storing the file that failed to validate the signature in the backup storage 140. [ Therefore, a file modulated by a malicious code such as a random software is not stored in the backup storage 140, and therefore, a file safely stored in the backup storage 140 is not overwritten with a file modulated by malicious code, Can be maintained.

The signature verification and backup server 130 stores the file in the backup storage 140. If the file with the same file name does not exist in the backup storage 140, ).

The signature verification and backup server 130 checks the signature of the file to be backed up and the signature of the file having the same file name stored in the backup storage 140 if the file having the same file name as the file whose validity has been verified is present in the backup storage 140 After the signatures are compared, the backup of the file is blocked according to the result of the comparison, the file name of the file to be backed up is changed and stored, or the file stored in the backup storage 140 is overwritten.

Specifically, the signature verification and backup server 130 blocks the backup of the file to be backed up when a file having the same file name as that of the file whose validity has been successfully verified exists in the backup storage 140 and the two files have the latest signatures do. For example, if the A.datv file is already stored in the backup storage 140 and the recent signature of the A.datv file is' 47a3Rp65 ', the file name of the file to be backed up is A.datv and the recent signature is' 47a3Rp65 ', the backup of the file to be backed up is blocked because the file name and the latest signature are the same. This is because the same file is already stored in the backup storage 140. The signature verification and backup server 130 determines whether the file having the same file name as that of the file whose validity has been successfully verified is present in the backup storage 140 and that the two files have different recent signatures, If the latest signature of the file stored in the storage 140 is also different, the file name of the file to be backed up is changed and stored in the backup storage 140. For example, if the A.datv file is already stored in the backup storage 140 and the recent signature of the A.datv file is' 47a3Rp65 ', the file name of the file to be backed up is A.datv and the recent signature is' 68b4Qp75 'and the old signature of the file to be backed up (' 75c6Up55 ') and the backup signature of the backup storage (' The file name of the file to be backed up is changed to, for example, A (1) .datv, and the backup signature is stored in the backup storage 140 because the latest signature ('47a3Rp65') of the file stored in the backup file 140 is also different . This is because the file names are different from each other and only the file names are in the same state. Alternatively, the signature verification and backup server 130 may be configured such that a file having the same file name as that of the file whose validity has been successfully verified exists in the backup storage 140 and the two files have different recent signatures. However, If the latest signature of the file stored in the backup storage 140 is the same, the file to be backed up is overwritten to the file having the same file name stored in the backup storage 140. [ For example, if the A.datv file is already stored in the backup storage 140 and the recent signature of the A.datv file is' 47a3Rp65 ', the file name of the file to be backed up is A.datv and the recent signature is' ('47a3Rp65' vs '68b4Qp75'), the recent signatures of the files stored in the backup storage 140 ('47a3Rp65', '68b4Qp75' ) And the previous signature ('47a3Rp65') of the file to be backed up are the same, the file to be backed up is overwritten to the file having the same file name stored in the backup storage 140. In this case, a file stored in the backup storage 140 in the client device 110 is loaded and edited, and the file is stored again.

The signature verification and backup server 130 may include a memory, one or more processors, communication circuitry, and the functions and operations described above may be implemented as a program and installed in memory and then executed by the one or more processors. The memory may include high speed random access memory and may also include one or more magnetic disk storage devices, non-volatile memory such as flash memory devices, or other non-volatile semiconductor memory devices. An operating system may be installed as a software component in the memory. The operating system may be an embedded operating system such as, for example, Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS or VxWorks, Android, etc. and may include general system tasks Device control, power management, etc.), and facilitates communication between the various hardware and software components. The communication circuitry may be implemented by means of the Internet, called the World Wide Web (WWW), the intranet and the network and / or a wireless network such as a cellular telephone network, a wireless LAN and / or a metropolitan area network (MAN) And can communicate with other devices.

3 is a flow diagram of one embodiment illustrating a method for controlling file backup in the system of FIG.

Referring to FIG. 3, the client device 110 downloads and installs the signature generation module 121 from the management server 120 (S301). The user creates a file to be backed up on the client device 110 (S302). The file to be backed up includes, for example, a document file, a music file, or a video file, but does not have any special limitation. The signature generation module 121 installed in the client device 110 generates a signature of the file to be backed up (S303). When the user stores the file in a specific folder or the user selects the file stored in an arbitrary folder and selects the backup menu by pressing the right button of the mouse, the signature generation module 121 generates a signature from the file .

After generating the signature, the signature generation module 121 adds the signature to the file (S304). Since the first signature has been created, the signature generation module 121 adds the generated signature to the recent signature field, and inserts a predetermined value or a random value into the previous signature field. The signature generation module 121 transmits the signature-added file to the signature verification and backup server 130 and requests a backup (S305).

The signature verification and backup server 130 verifies the validity of the most recent signature added to the backup requested file (S306). That is, the signature verification and backup server 130 verifies the validity of the signature by generating a signature from the file requested to be backed up and comparing it with the most recent signature added to the file. If the signatures match, it is determined that the validity verification succeeds. If the signatures do not match, it is determined that the validity verification fails (S307).

If the signature validation fails, the signature verification and backup server 130 blocks the backup of the file requested to be backed up (S308). The signature verification and backup server 130 may notify the client device 110 of the blocking of the backup.

If the signature validation is successful, the signature verification and backup server 130 checks whether a file with the same file name as the file name of the file to be backed up exists in the backup storage 140 (S309). If the file name of the same file does not exist, the file name is directly stored in the backup storage 140 without changing the file name (S310).

If a file with the same file name as the file name of the file to be backed up exists in the backup storage 140, the signature verification and backup server 130 checks whether the recent signatures of the two files are identical to each other (S311). If the two files have the same recent signature, the signature verification and backup server 130 blocks backup of the requested file (S308). On the other hand, if the recent signatures of the two files are different from each other, the signature verification and backup server 130 modifies the file name of the file requested to be backed up (S312) and then starts again from step S309.

4 is a flow diagram of another embodiment illustrating a method for controlling file backup in the system of FIG. 4, the signature generation module 121 is installed in the client device 110. The client device 110 loads and edits a file stored in the backup storage 140, (140).

Referring to FIG. 4, in response to a user's input, the client device 110 loads and opens a file stored in the backup storage 140 (S401). After editing the opened file (S402), the signature generation module 121 of the client device 110 newly creates a signature of the edited file (S403), and then edits the newly created signature (S404). Thus, the edited file has both the newly created signature and the old signature added together. The signature generation module 121 transmits the signature added file to the signature verification and backup server 130 and requests a backup (405).

The signature verification and backup server 130 verifies the validity of the most recent signature added to the backup requested file (S406). That is, the signature verification and backup server 130 verifies the validity of the signature by generating a signature from the file requested to be backed up and comparing it with the most recent signature added to the file. When the signatures match, it is determined that the validity verification succeeds. If the signatures do not match, it is determined that the validity verification fails (S407).

If the signature validation fails, the signature verification and backup server 130 blocks the backup of the file requested to be backed up (S408). The signature verification and backup server 130 may notify the client device 110 of the blocking of the backup.

If the signature validation is successful, the signature verification and backup server 130 checks whether a file having the same file name as the file name of the file to be backed up exists in the backup storage 140 (S409). In this embodiment, since the file requested to be backed up is loaded and edited in the backup storage 140, a file having the same file name exists in the backup storage 140. If a file with the same file name does not exist in the backup storage 140, the signature verification and backup server 130 stores the backup requested file in the backup storage 140 as it is. In this case, the user loads and edits a file in the backup storage 140, and then changes and saves the file name.

As a result of checking in step S409, if a file with the same file name exists, the signature verification and backup server 130 determines whether the signature of the file having the same file name stored in the backup storage 140 (S411). If they are the same, the signature verification and backup server 130 overwrites the file to be backed up with a file having the same file name stored in the backup storage 140 (S413). On the other hand, if the signatures of the two files are not identical, the signature verification and backup server 130 modifies the file name of the file requested to be backed up (S414) and then starts again from step S409.

5 is a diagram illustrating a file backup control system according to another embodiment of the present invention. 1, the management server 120 downloads only the signature generation module 121 to the client device 110. In the embodiment of FIG. 5, the management server 120 downloads not only the signature generation module 121 but also the signature verification module 501 to the client device 110. [ The signature verification module 501 performs an operation to verify the validity of the signature performed by the signature verification and backup server 130 in the embodiment of FIG. The signature verification module 501 may be implemented as an application together with the signature generation module 121. [ That is, the signature verification function of FIG. 1 and the signature verification function of the backup server 130 are implemented in the signature verification module 501 and downloaded to the client device 110, and only the backup processing function remains in the backup server 520 .

The signature verification module 501 verifies the validity of the most recent signature added to the file to be backed up. The signature verification module 501 verifies the validity of the signature by generating a signature from the file to be backed up and comparing it with the most recent signature added to the file. If the signatures match, it is determined that the validation is successful, and if the signatures do not match, it is determined that the validation fails. The signature verification module 501 transmits the file to be backed up, which has been successfully verified with the signature, to the backup server 520 to request a backup.

The backup server 520 stores the file that has successfully verified the signature in the backup storage 140 and blocks the storage of the file that failed the validity verification of the signature in the backup storage 140. [ Therefore, a file modulated by a malicious code such as a random software is not stored in the backup storage 140, and therefore, a file safely stored in the backup storage 140 is not overwritten with a file modulated by malicious code, Can be maintained.

The backup server 520 stores the file in the backup storage 140 without storing the file name of the file in the backup storage 140 if the file with the same file name does not exist in the backup storage 140 do.

The backup server 520 compares the signature of the file to be backed up with the signature of the file having the same file name stored in the backup storage 140 if a file having the same file name as the file whose validity is verified is present in the backup storage 140 After that, the backup of the file is blocked according to the comparison result, the file name of the file to be backed up is changed and stored, or the file stored in the backup storage 140 is overwritten.

Specifically, the backup server 520 blocks the backup of the file to be backed up when a file having the same file name as the file to be backed up exists in the backup storage 140 and the two files have the same recent signature. The backup server 520 determines that the files having the same file names as the files to be backed up are present in the backup storage 140 and that the two files have different recent signatures and that the old signature and the backup storage 140 If the latest signature of the stored file is also different, the file name of the file to be backed up is changed and stored in the backup storage 140. The backup server 520 is configured such that a file having the same file name as the file to be backed up exists in the backup storage 140 and the two files have different recent signatures, If the latest signature of the file is the same, the file to be backed up is overwritten to the file having the same file name stored in the backup storage 140. In this case, a file stored in the backup storage 140 in the client device 110 is loaded and edited, and the file is stored again.

6 is a diagram illustrating a file backup control system according to another embodiment of the present invention. 1, the management server 120 downloads only the signature generation module 121 to the client device 110. In the embodiment of FIG. 6, the management server 120 downloads not only the signature generation module 121 but also the backup module 601 to the client device 110. [ Thus, the signature verification and backup server 130 of FIG. 1 only retains the signature verification function.

The signature generation module 121 of the client device 110 adds a signature to a file to be backed up and then sends a signature added file to the signature verification server 620 before performing backup to request verification.

The signature verification server 620 verifies the validity of the most recent signature added to the file. The signature verification server 620 verifies the validity of the signature by generating a signature from the file and comparing it with the latest signature added to the file. If the signatures match, it is determined that the validation is successful, and if the signatures do not match, it is determined that the validation fails. The signature verification server 620 returns the result of the signature verification to the backup module 601. [

The backup module 601 of the client device 110 stores the file in which the validity of the signature has been successfully verified in the backup storage 140 and blocks the storage of the file in the backup storage 140 that fails to validate the signature . Therefore, a file modulated by a malicious code such as a random software is not stored in the backup storage 140, and therefore, a file safely stored in the backup storage 140 is not overwritten with a file modulated by malicious code, Can be maintained.

The backup module 601 stores the file in the backup storage 140 without storing the file name of the file in the backup storage 140 if the file with the same file name does not exist in the backup storage 140 do.

The backup module 601 compares the signature of the file to be backed up with the signature of the file having the same file name stored in the backup storage 140 when a file having the same file name as the file whose validity is verified is present in the backup storage 140 After that, the backup of the file is blocked according to the comparison result, the file name of the file to be backed up is changed and stored, or the file stored in the backup storage 140 is overwritten.

Specifically, the backup module 601 blocks the backup of the file to be backed up when a file having the same file name as the file to be backed up exists in the backup storage 140 and the two files have the same recent signature. The backup module 601 determines whether the file having the same file name as the file to be backed up exists in the backup storage 140 and the latest signature of the two files is different from each other and the old signature and the backup storage 140 If the latest signature of the stored file is also different, the file name of the file to be backed up is changed and stored in the backup storage 140. The backup module 601 is configured such that a file having the same file name as the file to be backed up exists in the backup storage 140 and the latest signature of the two files is different, If the latest signature of the file is the same, the file to be backed up is overwritten to the file having the same file name stored in the backup storage 140. In this case, a file stored in the backup storage 140 in the client device 110 is loaded and edited, and the file is stored again.

While the specification contains many features, such features should not be construed as limiting the scope of the invention or the scope of the claims. In addition, the features described in the individual embodiments herein may be combined and implemented in a single embodiment. Conversely, various features described in the singular < Desc / Clms Page number 5 > embodiments herein may be implemented in various embodiments individually or in combination as appropriate.

Although the operations have been described in a particular order in the figures, it should be understood that such operations are performed in a particular order as shown, or that all described operations are performed to obtain a sequence of sequential orders, or a desired result . In certain circumstances, multitasking and parallel processing may be advantageous. It should also be understood that the division of various system components in the above embodiments does not require such distinction in all embodiments. The above-described program components and systems can generally be implemented as a single software product or as a package in multiple software products.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit or scope of the invention. The present invention is not limited to the drawings.

110: Client device
120: management server
121: signature generation module
130: Signature verification and backup server
140: Backup storage
150: Network
501: Signature verification module
520: backup server
601: Backup module
620: Signature verification server

Claims (12)

A system for controlling file backup to backup storage,
A management device that generates a signature for each file to be backed up and adds the signature to the file to be backed up each time a new file is created or edited, to a device for creating or editing the file to be backed up; And
Receiving a file to be backed up from the device for generating or editing, generating a signature from the received file to be backed up, verifying the validity of the signature by comparing the received file with the latest signature added to the file to be backed up, And a signature verification and backup device for storing the received file to be backed up in the backup storage upon success. The method according to claim 1,
Said signature verification and backup device comprising:
If the backup storage does not have a file with the same file name as the file to be backed up, stores the file to be backed up in the backup storage as it is. The method according to claim 1,
Said signature verification and backup device comprising:
Wherein if a file having the same file name as the file to be backed up exists in the backup storage, a latest signature added to a file of the same file name existing in the backup storage among a plurality of signatures added to the backup file And changes the file name of the file to be backed up in other cases and stores the changed file name in the backup storage. The method according to claim 1,
Said signature verification and backup device comprising:
Wherein if a file having the same file name as the file to be backed up exists in the backup storage, a latest signature added to a file of the same file name existing in the backup storage among a plurality of signatures added to the backup file And overwrites the file with the same file name existing in the backup storage with the file to be backed up if they are the same. A system for controlling file backup to backup storage,
A signature generation module for generating a signature of the file to be backed up each time a new file is created or edited, and adding the signature to the file to be backed up; and a signature generation module for generating a signature from the file to be backed up, A signature verification module for performing signature validation for comparison with a recent signature added to the file to be created, or to a device for creating or editing the file to be backed up; And
And a backup device for receiving the file to be backed up that has successfully verified the signature from the signature verification module and storing the received file in the backup storage. 6. The method of claim 5,
The backup device comprising:
If the backup storage does not have a file with the same file name as the file to be backed up, stores the file to be backed up in the backup storage as it is. 6. The method of claim 5,
The backup device comprising:
Wherein if a file having the same file name as the file to be backed up exists in the backup storage, a latest signature added to a file of the same file name existing in the backup storage among a plurality of signatures added to the backup file And changes the file name of the file to be backed up in other cases and stores the changed file name in the backup storage. 6. The method of claim 5,
The backup device comprising:
Wherein if a file having the same file name as the file to be backed up exists in the backup storage, a latest signature added to a file of the same file name existing in the backup storage among a plurality of signatures added to the backup file And overwrites the file with the same file name existing in the backup storage with the file to be backed up if they are the same. A system for controlling file backup to backup storage,
A signature generation module for generating a signature of the file to be backed up each time a new file is created or edited and adding the signature to the file to be backed up when the file to be backed up is created or edited; A management device for transmitting the backup module stored in the backup storage to a device for creating or editing the file to be backed up; And
A signature verification module for receiving the file to be backed up with the signature added from the signature generation module, generating a signature from the received file to be backed up and comparing it with a recent signature added to the file to be backed up, And send a result to the backup module. 10. The method of claim 9,
Wherein the backup module comprises:
If the backup storage does not have a file with the same file name as the file to be backed up, stores the file to be backed up in the backup storage as it is. 10. The method of claim 9,
Wherein the backup module comprises:
Wherein if a file having the same file name as the file to be backed up exists in the backup storage, a latest signature added to a file of the same file name existing in the backup storage among a plurality of signatures added to the backup file And changes the file name of the file to be backed up in other cases and stores the changed file name in the backup storage. 10. The method of claim 9,
Wherein the backup module comprises:
Wherein if a file having the same file name as the file to be backed up exists in the backup storage, a latest signature added to a file of the same file name existing in the backup storage among a plurality of signatures added to the backup file And overwrites the file with the same file name existing in the backup storage with the file to be backed up if they are the same.

Images