Method and apparatus for managing backup data

• US 8,244,678 B1
• Filed: 03/20/2009
• Issued: 08/14/2012
• Est. Priority Date: 08/27/2008
• Status: Active Grant

• Current Assignee: Spearstone Management LLC
• Original Assignee: Spearstone Management LLC
• Inventors: Hartland, Hayden Thomas, Goddard, Dale Woodroffe, Jensen, David Loy
• Primary Examiner(s): Truong, Dennis
• Application Number:
  US12/408,617
• Time in Patent Office: 1,243 Days
• Field of Search: 707/610, 707/640, 707/661, 707/688, 707/694, 707/821, 707/999.2, 711/162, 711/170, 726/26
• US Class Current: 707/640
• CPC Class Codes: G06F 11/1448 Management of the data involved in backup or backup restore
• CPC Class Codes: G06F 11/1458 Management of the backup or restore process
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

A method of easily-accessible, versioned, secure, redundant backup of digital information involves establishing a back-end data store connected to a world-wide telecommunications network. Users communicate with the data store using a variety of user a computing devices, each of which has installed thereon client software capable various operations, including communicating with the data store, monitoring a second data store, detecting and replicating changes in the second data store, and selecting data to be transmitted over the telecommunications network to and from the back-end data store. Users may establish policies for data backup and transmission, may monitor the status of data backup, may browsing the back-end data store, may review prior versions of data stored on the back-end data store. The data store is configured for remote management by a user, including deletion of data in the second data store if the computing device is lost or stolen.

Claims

1. A method of easily-accessible, versioned, secure, redundant backup of digital information, comprising the steps of:

establishing a first readily expandable redundant back-end data store having a fault tolerant connection to a communications network, the first data store being configured for remote management by a user;

enabling bi-directional communication over the communications network between the first data store and a computing device;

provisioning the computing device with a client application capable of executing an algorithm on the computing device, the client application having the capabilities of;

communicating with the first data store;

monitoring a second data store that is accessible by the computing device;

detecting and replicating changes in the second data store including detection of differences in versions of data in the second data store and detection of deletions of versions of data;

selecting a first set of predetermined data in the second data store to be monitored by the client application and selecting at least a portion of the first set of predetermined data to be transmitted over the communications network to the first data store;

selecting predetermined data in the first data store to be transmitted over the communications network to the second data store, including pushing data from the first data store to the second data store using a remote access protocol;

establishing policies for the data backup and transmission, including requirements for data to be transmitted to and from the first data store, data not to be transmitted to or from the first data store, requirements for data to be deleted from, or retained on, the first or second data store, and allocation of network bandwidth and CPU cycles;

monitoring the status of data backup and providing a risk assessment of the data backup based on predetermined criteria;

browsing the first data store;

restoring data from the first data store to the second data store;

reviewing prior versions of data stored on the first data store based on a predetermined criteria;

managing access to the computing device upon occurrence of a triggering event;

being remotely updated;

causing data on the second data store to be deleted when the operating system is started unless a user properly authenticates to the client application;

setting backup criteria, including location, naming conventions, file types, frequently changing files backup criteria, size limits, bandwidth requirements and limitations, and identification of file groups, members of which require synchronous backup;

enabling the capturing, sending, and remote storage of device coordinates and proximity alerts when within user defined boundaries or conditions;

setting restoration criteria;

handling alerts regarding the backup of data to the first data store; and

staging changes to data in the second data store during offline use for backup to the first data store upon connection to the communications network;

causing the client application to generate and send a file hash to the first data store,

searching the first data store for a matching file hash for files already stored in the first data store; and

if a match is found, saving a file pointer reference for any data store that subsequently attempts to save a file from which an identical file hash is obtained; and

enabling web access to the first data store.

2. The method of claim 1 further comprising the step of providing a web client that can configure aspects of the first data store and manage rights and access to the first data store and the second data store.

3. The method of claim 1 further comprising the step of providing an engine that rebrands the client application to allow third party value added resellers to distribute the client application under a brand controlled by the third party.

4. The method of claim 1 wherein the triggering event includes notification from a user or an administrator, repeated unsuccessful access attempts, or a predetermined length of time passing between uses of the client application.

5. The method of claim 1 further comprising the step of enabling capture of electronic messages and attachments for transmission to and storage in the first data store.

6. The method of claim 1 further comprising the step of enabling the capturing, searching, and indexing of SMS, MMS, and other handheld communication protocols for review by an authorized user.

7. The method of claim 1 further comprising the step of identifying a set of privilege levels for users.

8. The method of claim 1 further comprising the step of safeguarding digital information by triggering a deletion of said data, or deleting the second data store upon occurrence of a triggering event.

9. The method of claim 1 wherein the data being transmitted between the first and second data store is encrypted and compressed prior to transmission.

10. A system for backup of digital information, comprising the steps of:

establishing a first data store having a connection to a communications network;

enabling communication over the communications network between the first data store and a computing device;

provisioning the computing device with a client application having the capabilities of;

communicating with the first data store;

monitoring a second data store;

detecting and replicating differences in versions of data in the second data store and detection of deletions of versions of data;

selecting a first set of predetermined data in the second data store to be monitored by the client application;

causing data on the second data store to be deleted when the operating system is started unless a user properly authenticates to the client application;

establishing policies for the data backup and transmission;

enabling the capturing, sending, and remote storage of device coordinates and proximity alerts when within user defined boundaries or conditions;

causing the client application to generate and send a file hash to the first data store;

searching the first data store for a matching file hash for files already stored in the first data store; and

if a match is found, saving a file pointer reference for any data store that subsequently attempts to save a file from which an identical file hash is obtained;

monitoring the status of data backup;

restoring data from the first data store to the second data store; and

managing access to the computing device upon occurrence of a triggering event; and

enabling web access to the first data store.

11. The system of claim 10 further comprising the step of providing a web client that can configure aspects of the first data store and manage rights and access to the first data store and the second data store.

12. The system of claim 10 further comprising the step of providing an engine that rebrands the client application to allow third party value added resellers to distribute the client application under a brand controlled by the third party.

13. The system of claim 10 further comprising the step of enabling capture of electronic messages and attachments for transmission to and storage in the first data store.

14. The system of claim 10 further comprising the step of enabling the capturing, searching, and indexing of SMS, MMS, and other handheld communication protocols for review by an authorized user.

15. The system of claim 10 further comprising the step of identifying a set of privilege levels for users.

16. The system of claim 10 further comprising the step of safeguarding digital information by triggering a deletion of said data, or deleting the second data store upon occurrence of a triggering event.

17. The system of claim 10 wherein the data being transmitted between the first and second data store is encrypted and compressed prior to transmission.

18. The system of claim 10 wherein the first data store is configured for remote management by a user.

19. The system of claim 10 further comprising the step of selecting at least a portion of the first set of predetermined data to be transmitted over the communications network to the first data store.

20. The system of claim 10 further comprising the step of selecting predetermined data in the first data store to be transmitted over the communications network to the second data store.

21. The system of claim 10 further comprising the step of providing a risk assessment of the data backup based on predetermined criteria.

22. The system of claim 10 further comprising the step of browsing the first data store.

23. The system of claim 10 further comprising the step of reviewing prior versions of data stored on the first data store based on a predetermined criteria.

24. The system of claim 10 further comprising the step of setting restoration criteria.

25. The system of claim 10 further comprising the step of handling alerts regarding the backup of data to the first data store.

26. The system of claim 10 further comprising the step of staging changes to data in the second data store during offline use for backup to the first data store upon connection to the communications network.

27. The system of claim 10 wherein the triggering event includes notification from a user or an administrator, repeated unsuccessful access attempts, or a predetermined length of time passing between uses of the client application.

28. A non-transitory computer-readable media for storing and executing instructions to backup digital information, comprising the step of enabling a first data store to communicate with a computing device, the computing device being capable of detecting and replicating differences in versions of data in the first data store and a second data store and of restoring predetermined data from the first data store to the second data store, and further comprising the steps of:

communicating with the first data store;

monitoring the second data store;

detecting and replicating differences in versions of data in the second data store and detection of deletions of versions of data;

selecting a first set of predetermined data in the second data store to be monitored by the client application;

causing data on the second data store to be deleted when the computing device is started unless a user properly authenticates to the computing device;

establishing policies for the data backup and transmission;

enabling the capturing, sending, and remote storage of device coordinates and proximity alerts when within user defined boundaries or conditions;

causing the computing device to generate and send a file hash to the first data store;

searching the first data store for a matching file hash for files already stored in the first data store; and

if a match is found, saving a file pointer reference for any data store that subsequently attempts to save a file from which an identical file hash is obtained;

monitoring the status of data backup;

restoring data from the first data store to the second data store;

managing access to the computing device upon occurrence of a triggering event; and

enabling web access to the first data store.

29. The non-transitory computer-readable media of claim 28 further comprising the step of enabling web access to the first data store.

30. The non-transitory computer-readable media of claim 28 wherein the first data store and the computing device communicate over a communications network.

31. The non-transitory computer-readable media of claim 28 further comprising the step of establishing policies for the data backup and transmission.

32. The non-transitory computer-readable media of claim 28 further comprising the step of managing access to the computing device upon occurrence of a triggering event.

33. The non-transitory computer-readable media of claim 28 further comprising the step of providing a web client that can configure aspects of the first data store and manage rights and access to the first data store and the second data store.

34. The non-transitory computer-readable media of claim 28 further comprising the step of providing an engine that rebrands the method to allow third party value added resellers to distribute the method under a brand controlled by the third party.

35. The non-transitory computer-readable media of claim 28 further comprising the step of enabling capture of electronic messages and attachments for transmission to and storage in the first data store.

36. The non-transitory computer-readable media of claim 28 further comprising the step of enabling the capturing, searching, and indexing of SMS, MMS, and other handheld communication protocols for review by an authorized user.

37. The non-transitory computer-readable media of claim 28 further comprising the step of identifying a set of privilege levels for users.

38. The non-transitory computer-readable media of claim 28 further comprising the step of safeguarding digital information by triggering a deletion of said data, or deleting the second data store upon occurrence of a triggering event.

39. The non-transitory computer-readable media of claim 28 wherein the first data store being configured for remote management by a user.

40. The non-transitory computer-readable media of claim 28 further comprising the step of setting restoration criteria.

41. The non-transitory computer-readable media of claim 28 further comprising the step of staging changes to data in the second data store during offline use for backup to the first data store upon establishing a connection between the first data store and the computing device.

42. The non-transitory computer-readable media of claim 32 wherein the triggering event includes notification from a user or an administrator, repeated unsuccessful access attempts, or a predetermined length of time passing between uses of the client application.