Systems and methods for data backup over a network

• US 20030056139A1
• Filed: 09/20/2002
• Published: 03/20/2003
• Est. Priority Date: 09/20/2001
• Status: Active Grant

• Current Assignee: Carbonite LLC (Open Text Corporation)
• Original Assignee: Evault Incorporated (Seagate Technology Holdings Plc)
• Inventors: Murray, Bill, Lewitzky, Andre, Boldt, Tim
• Granted Patent: US 7,134,041 B2
• Time in Patent Office: Days
• US Class Current: 714/4
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99955 Archiving or backup

Abstract

A system and method for data backup over a network has been developed. The method includes creating a baseline copy of the data files that are to be archived. When the data is subsequently being backed up, the system checks for the presence of newly added files by comparing the sort order of the present data files with the sort order of the baseline copy. Any newly added files are then saved to the baseline copy. The system checks for any changes in existing files by comparing the hash numbers of the present data files with the hash numbers of the data files in the baseline copy. Any changed files are then merged into their corresponding data files in the baseline copy.

Claims

1. A method for storage of data files, comprising:

creating a baseline copy of the data files, where each baseline data file has a sort order position and a hash number;

performing a backup session with at least one updated data file, where each updated data file has a sort order position and a hash number;

determining if the updated data file does not exist as any baseline data file by comparing the sort order positions of the baseline data files with the sort order positions of the updated data files;

wherein if the updated data file does not exist as any baseline data file, the updated data file is added to the baseline copy of data files;

determining if the updated file is an new version of any baseline data file by comparing the hash numbers of the baseline data files with the hash numbers of the updated data files; and

wherein if the updated file is a new version of any baseline data file, the updated data file is merged with the baseline data file in the baseline copy of data files.

2. The method of claim 1, where the hash number of each baseline data file is kept in a hash line index.

3. The method of claim 1, where the baseline copy of the data files comprises multiple storage groups containing the baseline data files.

4. The method a claim 3, where the baseline copy of data files further comprises:

a location file, where the location file contains the name and location of each baseline data file; and

an index file, where the index file contains any updated data files and any new data files for the baseline copy of data files.

5. The method of claim 3, where the baseline data files are divided into the storage groups based on access frequency of the baseline data files.

6. The method of claim 1, where an updated data file is added to the baseline copy of data files during the backup session.

7. The method of claim 1, where an updated data file is added to the baseline copy of data files upon receiving a retrieval request.

8. The method of claim 1, where an updated data file is merged with any baseline data file during the backup session.

9. The method of claim 1, where an updated data file is merged with any baseline data file upon receiving a retrieval request.

10. A method for storing data files, comprising:

step of creating a baseline copy of the data files;

step of running a backup session with updated data files;

step of identifying and adding new backup data files to the baseline copy of data files by comparison of sort order positions; and

step of identifying and merging a pre-existing backup data file into a corresponding baseline data file by comparison of hash numbers.