IP Library Granted Patent US 7,752,171
Granted Patent B2
US 7,752,171 · App. 11/834,344 · Granted Jul 6, 2010

Efficient computer file backup system and method

Assignee: DataCenterTechnologies N.V
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,752,171
App. No.
11/834,344
Filed
Aug 6, 2007
Granted
Jul 6, 2010
Kind
B2
Art Unit
2161
USPC
707/204
Abstract

A system and method for efficiently backing up and restoring computer files to a central storage system. A hashing key is computed for each file to be backed up on a target computer. The hashing key is compared to a list of hashing keys stored locally to see if the local file has been previously backed up. If the hashing key is not listed locally, then the hashing key is compared to a list of hashing keys of centrally backed up files. Only if the hashing key is not present in both the local and the central list is the file backed up. Backed up files may be renamed to their hashing key for further efficiencies.

Claims (62)

1. A method for deciding whether a specific file on a target computer should be backed up to a central storage system, said method comprising:

computing a specific hashing key from the content of said specific file;

verifying if said specific hashing key is already present in a local database, wherein, for each computer file on said target computer which has been previously backed up, said local database comprises a record including a local file path in said target computer where said computer file should be restored, said file path being associated with said file hashing key;

if a file whose name comprises the specific hashing key has not already been backed up to the central storage system, backing up said specific file by performing the steps of:

creating a backup file which is a duplicate of said specific file;

renaming said backup file to said specific hashing key;

storing said renamed backup file in said central storage system; and

storing an indication that a file whose name comprises the specific hashing key has been backed up to the central storage system; and

if a file whose name comprises the specific hashing key has already been backed up to the central storage system, not backing up said specific file in said central storage system.

2. The method according to claim 1 , further comprising the steps of:

verifying if a file whose name comprises said specific hashing key has already been backed up to said central storage system; and

backing up said specific file if and only if said specific hashing key has not already been backed up to said central storage system.

3. The method according to claim 2 , wherein said target computer is connected to a LAN and further wherein said central storage system is connected to said LAN by a WAN.

4. The method according to claim 1 , wherein a plurality of target computers are connected with said central storage system, and further wherein said specific file is not backed up if it is already present in said central storage system as the result of a backup from any target computer.

5. The method according to claim 4 , wherein the location of said renamed backup file in said central storage system depends on said specific hashing key.

6. The method according to claim 5 , wherein said central storage system comprises a plurality of storage devices.

7. A method for restoring a specific file to a target computer, said method comprising:

requesting a specific hashing key corresponding to said specific file from a local database storing a previously computed hashing key for each backed up computer file;

using said specific hashing key to retrieve a backup file from a central storage server, said backup file being a duplicate of said specific file; and

accessing a local database that comprises a record including a local file path in said target computer where said specific file should be restored, said file path being associated with said file hashing key;

saving said specific file on said target computer.

8. The method according to claim 7 , wherein the location at which said backup file has been stored in said central storage server depends on said hashing key.

9. The method according to claim 8 , wherein the name under which said backup file has been stored in said central storage server depends on said hashing key.

10. A central storage system for backing up a specific file on a target computer comprising:

a backup storage system; and

a backup and restore subsystem, wherein said subsystem is configured to:

compute a specific hashing key from the content of said specific file;

verify if said specific hashing key is already present in a local database, wherein, for each computer file on said target computer which has been previously backed up, said local database comprises a record including a local file path in said target computer where said computer file should be restored, said file path being associated with said file hashing key;

back up said specific file if a file whose name comprises said specific hashing key has not already been backed up to the central storage system, said backing up comprising the steps of:

create a backup file which is a duplicate of said specific file;

rename said backup file to said specific hashing key;

store said renamed backup file in said central storage system; and

store an indication that a file whose name comprises the specific hashing key has been backed up to the central storage system;

wherein, if a file whose name comprises said specific hashing key has already been backed up to the central storage system, not backing up said specific file in said central storage system.

11. The central storage system according to claim 10 being a central storage system, and further comprising means for verifying if a file whose name comprises said specific hashing key has already been backed up to said central storage system, wherein said means for backing up is performed only if said specific hashing key has not already been backed up to said central storage system.

12. The system according to claim 11 , wherein said target computer is connected to a LAN and further wherein said central storage system is connected to said LAN by a WAN.

13. The central storage system according to claim 10 , wherein a plurality of target computers are connected with said central storage system, and further wherein said specific file is not backed up if it is already present in said central storage system as the result of a backup from any target computer.

14. The central storage system according to claim 13 , wherein the location of said renamed backup file in said central storage system depends on said specific hashing key.

15. The central storage system according to claim 10 , further comprising:

means for restoring said specific file from said central storage system to said target computer, comprising:

means for requesting said specific hashing key corresponding to said specific file;

means for using said specific hashing key to retrieve said backup file from said system; and

means for saving said backup file on said target computer.

16. The central storage system of claim 15 , wherein, during said backing up, if a file whose name comprises said specific hashing key has not already been backed up to the central storage system, said backup file is renamed to said specific hashing key before storing said backup file in said central storage system, and further wherein, during said restoring, said backup file is renamed to the name of said specific file before saving said backup file to said target computer.

17. A computer-readable medium storing computer-executable instructions for causing said computer to decide whether a specific file on a target computer should be backed up to a central storage system, wherein the instructions are further executable to cause the computer to:

compute a specific hashing key from the content of said specific file;

verify if said specific hashing key is already present in a local database, wherein, for each computer file on said target computer which has been previously backed up, said local database comprises a record including a local file path in said target computer where said computer file should be restored, said file path being associated with said file hashing key;

if a file whose name comprises the specific hashing key has not already been backed up to the central storage system, back up said specific file by performing the steps of:

creating a backup file which is a duplicate of said specific file;

renaming said backup file to said specific hashing key;

storing said renamed backup file in said central storage system; and

storing an indication that a file whose name comprises the specific hashing key has been backed up to the central storage system; and

if a file whose name comprises the specific hashing key has already been backed up to the central storage system, not back up said specific file in said central storage system.

18. The computer-readable medium as recited in claim 17 , wherein the instructions are further executable to cause the computer to:

verify if a file whose name comprises said specific hashing key has already been backed up to said central storage system; and

back up said specific file if and only if said specific hashing key has not already been backed up to said central storage system.

19. A computer program product storing computer-executable instructions for performing a method for restoring a specific file to a target computer, said method comprising:

requesting a specific hashing key corresponding to said specific file from a local database storing a previously computed hashing key for each backed up computer file;

using said specific hashing key to retrieve a backup file from a central storage server, said backup file being a duplicate of said specific file, wherein a name under which said backup file has been stored in said central storage server depends on said hashing key; and

access a local database that comprises a record including a local file path in said target computer where said specific file should be restored, said file path being associated with said file hashing key;

saving said backup file on said target computer.

20. The computer product as recited in claim 19 , wherein the location at which said backup file has been stored in said central storage server depends on said hashing key.

Assignments (10)
RELEASE OF SECURITY INTEREST Recorded Dec 16, 2024
From: ACQUIOM AGENCY SERVICES LLC, AS COLLATERAL AGENT
To: VERITAS TECHNOLOGIES LLC (F/K/A VERITAS US IP HOLDINGS LLC)
Reel/Frame 069712/0090 →
RELEASE OF SECURITY INTEREST Recorded Dec 13, 2024
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: VERITAS TECHNOLOGIES LLC
Reel/Frame 069634/0584 →
ASSIGNMENT OF SECURITY INTEREST IN PATENT COLLATERAL Recorded Nov 25, 2024
From: BANK OF AMERICA, N.A., AS ASSIGNOR
To: ACQUIOM AGENCY SERVICES LLC, AS ASSIGNEE
Reel/Frame 069440/0084 →
TERMINATION AND RELEASE OF SECURITY IN PATENTS AT R/F 037891/0726 Recorded Nov 30, 2020
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
To: VERITAS US IP HOLDINGS, LLC
Reel/Frame 054535/0814 →
SECURITY INTEREST Recorded Aug 20, 2020
From: VERITAS TECHNOLOGIES LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
Reel/Frame 054370/0134 →
MERGER AND CHANGE OF NAME Recorded Apr 18, 2016
From: VERITAS US IP HOLDINGS LLC; VERITAS TECHNOLOGIES LLC
To: VERITAS TECHNOLOGIES LLC
Reel/Frame 038455/0752 →
SECURITY INTEREST Recorded Feb 23, 2016
From: VERITAS US IP HOLDINGS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 037891/0726 →
SECURITY INTEREST Recorded Feb 23, 2016
From: VERITAS US IP HOLDINGS LLC
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 037891/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 4, 2016
From: SYMANTEC CORPORATION
To: VERITAS US IP HOLDINGS LLC
Reel/Frame 037697/0412 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 14, 2011
From: DATACENTERTECHNOLOGIES N.V.
To: SYMANTEC CORPORATION
Reel/Frame 026589/0412 →
Priority Claims (1)
EP 01120041 · Aug 20, 2001 · regional
Continuity (3)
Continuation 1078068300 · Feb 19, 2004
Continuation PCTEP020258800 · Mar 8, 2002
Related Publication 20080034021A1 · Feb 7, 2008