Method and device for data backup

• US 7,822,725 B2
• Filed: 02/05/2007
• Issued: 10/26/2010
• Est. Priority Date: 11/24/2006
• Status: Expired due to Fees

• Current Assignee: Officeplus GmbH
• Original Assignee: BDT-Solutions GmbH (BDT AG)
• Inventors: Jiao, Yu, Lautar, Igor, Volk, Dejan, Beltram, Tomaz, Rejc, Dario, Walliser, Stefan, Haug, Oliver
• Primary Examiner(s): Mofiz; Apu M
• Assistant Examiner(s): Bibbee; Jared M
• Application Number:
  US11/671,001
• Publication Number:
  US 20080126431A1
• Time in Patent Office: 1,359 Days
• Field of Search: 707/200, 707/203, 707/204, 707/651, 707/698
• US Class Current: 707/698
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/1456 Hardware arrangements for backup
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 11/1469 Backup restoration techniques
• CPC Class Codes: G06F 2201/83 the solution involving signatures

Abstract

A method for storing data with a first storage system and a second storage system, wherein the second storage system is used for backing up the data from the first storage system, wherein the first storage system comprises a file system on which the data that is to be backed up is stored, with a client that monitors the first storage system, and a server that administers the second storage system, with the method comprising the following steps:

• • checking the files on the first storage system for any changes by the client, depending on one or several events;
  • if changes have been detected, determining a hash value in relation to the file, which hash value is structured such that the identity of the file can be determined,
  • transmitting the hash value to the server,
  • checking, by means of the hash value, by the server as to whether the identical file is stored on the second storage system, and
    if the file already exists, the file is not requested, but an annotation is made to the effect that the file is stored on the first storage system, and if the file does not exist, requesting the entire file, or parts of the file that have changed, from the first storage system, and storing the file on the second storage system, with an annotation relating to the first storage system.

Claims

1. A method for the safe transfer of data in a hierarchical storage system having a plurality of volumes, with the storage system comprising storage devices of different speeds, wherein the data automatically migrates from one hierarchy to another according to predeterminable criteria, comprising the following steps:

generating a first hash value for the data, from which hash value the identity of the data can be established prior to migration, wherein a ABSHASH is used, to avoid frequent copying operations the ABSHASH value has been adapted with additional bytes accordingly so that it shows the volume in which the objects or files are to be filed,

checking the integrity of the data after migration by reading the data and generating a second hash value so that it can be compared with the first hash value; and

if the hash values do not agree, renewed copying of the data.

2. The method according to the claim 1, wherein the hash value is stored in a database so that fast access is made possible, wherein the database is preferably stored so as to be redundant.

3. The method according to the claim 1, wherein the data relates to files or e-mails.

4. The method according to the claim 1, wherein during storing and loading, checks are made, by means of the hash value, as to whether the data is correct.

5. The method according to the claim 1, wherein the hash is an SHA1 hash.

6. A hierarchical storage system comprising storage devices of different speeds having a plurality of volumes, which storage devices are arranged in a hierarchy, wherein data automatically migrates between the hierarchies according to predeterminable criteria, comprising the following components:

means for generating a first hash value for data, from which hash value the identity of the data is determinable prior to migration, wherein a ABSHASH is used, to avoid frequent copying operations the ABSHASH value has been adapted with additional bytes accordingly so that it shows the volume in which the objects or files are to be filed;

means for checking the integrity of the data after migration by reading the data and generating a second hash value so that it can be compared with the first hash value; and

if the hash values do not agree, the means undertake renewed copying of the data.

7. The device according to the preceding claim 6, wherein the hash value is stored in a database so that fast access is made possible, wherein the database is preferably stored so as to be redundant.

8. The device according to claim 6, wherein the data relates to files or e-mails.

9. The device according to claim 6, wherein means are provided which during storing and loading, check the hash value, as to whether the data is correct.

10. The device according to claim 6, wherein the hash is an SHA1 hash.