This invention pertains generally to enabling dynamic computer data protection by linking backup with an external state.
Currently, computer data (for example, data stored on disk volumes) are backed up either on pre-set schedules, or in the event of a known impending disaster (for example, a loss of power, an imminent flood, etc.). This leaves any new or modified data fully vulnerable between backups, because it is not possible to recover data more recent than the last executed backup.
On the other hand, each executed backup uses both computing cycles and storage resources. Therefore, although backing up frequently is safer in terms of data integrity, it can become very resource expensive. Traditionally, a compromise has been reached for each protected system by balancing the time between backups (the window of vulnerability) and the resources needed or available to perform or hold the backup data.
In contemporary computing environments, information from external sources concerning the stability of the system is often available. For example, a malicious code threat assessment system can provide information regarding a current threat level. However, today's backup systems do not leverage external states to enhance data backup management.
What is needed are methods, systems and computer readable media to improve backup management, by automatically adjusting the frequency and/or data granularity of backups responsive to states external to the backup system.
The present invention comprises methods, systems and computer readable media for linking data backup robustness to an external state. In some embodiments, a data backup manager monitors an external state (such as a security threat assessment or other distress level). Responsive to the external state, the data backup manager adjusts parameters controlling data backup. The parameters to modify can include backup frequency, backup content, and backup retention time. The data backup manager can increase these parameters responsive to an increase in an external distress state level, and decrease them in response to a decrease in the external distress state level. Thus, the data backup manager ties the allocation of resources devoted to data backup to anticipated need.
The features and advantages described in this disclosure and in the following detailed description are not all-inclusive, and particularly, many additional features and advantages will be apparent to one of ordinary skill in the relevant art in view of the drawings, specification, and claims hereof. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes, and may not have been selected to delineate or circumscribe the inventive subject matter, resort to the claims being necessary to determine such inventive subject matter.
The Figures depict embodiments of the present invention for purposes of illustration only. One skilled in the art will readily recognize from the following discussion that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles of the invention described herein.
The data backup manager 101 monitors a state external to the backup system, such as an external distress state level state (for example, an external security threat assessment, an external computing resource overload assessment, an external software stability assessment, etc.). In some embodiments of the present invention, the data backup manager 101 monitors an external state by receiving e-mails 107 (or other forms of electronic notification, for example, control signals) from an external source 109 (for example, a threat assessment system) regarding the external state. In other embodiments, the data backup manager 101 reads data (for example, a global variable, a buffer, a port) external to the data backup manager 101 concerning the external state. Typically, such data is provided by an external source 109. It is to be understood that although the external source 109 in
As illustrated in
Increasing 203 the frequency of data backups 121 reduces the window of vulnerability for stored data 117 during times of high threat. Also in the event of a successful attack or system compromise, increasing 203, 205, 207 backup frequency, depth and/or retention periods increases the possibility of recovering unmodified or undamaged versions of the data 117 as they existed before the failure.
As will be understood by those familiar with the art, the invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. Likewise, the particular naming and division of the modules, managers, features, attributes, methodologies and other aspects are not mandatory or significant, and the mechanisms that implement the invention or its features may have different names, divisions and/or formats. Furthermore, as will be apparent to one of ordinary skill in the relevant art, the modules, managers, features, attributes, methodologies and other aspects of the invention can be implemented as software, hardware, firmware or any combination of the three. Of course, wherever a component of the present invention is implemented as software, the component can be implemented as a script, as a standalone program, as part of a larger program, as a plurality of separate scripts and/or programs, as a statically or dynamically linked library, as a kernel loadable module, as a device driver, and/or in every and any other way known now or in the future to those of skill in the art of computer programming. Additionally, the present invention is in no way limited to implementation in any specific programming language, or for any specific operating system or environment. Accordingly, the disclosure of the present invention is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5649196 | Woodhill et al. | Jul 1997 | A |
| 5778395 | Whiting et al. | Jul 1998 | A |
| 5835953 | Ohran | Nov 1998 | A |
| 6023507 | Wookey | Feb 2000 | A |
| 6085244 | Wookey | Jul 2000 | A |
| 6088803 | Tso et al. | Jul 2000 | A |
| 6550057 | Bowman-Amuah | Apr 2003 | B1 |
| 7330997 | Odom | Feb 2008 | B1 |
| 7363359 | Tripathy et al. | Apr 2008 | B1 |
| 7472349 | Srivastava et al. | Dec 2008 | B1 |
| 7584208 | Spivack et al. | Sep 2009 | B2 |
| 7640267 | Spivack et al. | Dec 2009 | B2 |
| 8161066 | Spivack et al. | Apr 2012 | B2 |
| 8190684 | Spivack et al. | May 2012 | B2 |
| 20020120685 | Srivastava et al. | Aug 2002 | A1 |
| 20070180490 | Renzi et al. | Aug 2007 | A1 |
| 20080177994 | Mayer | Jul 2008 | A1 |
| 20130036088 | Orenstein et al. | Feb 2013 | A1 |
| Entry |
|---|
| Van der Walt, Charl; “Assessing Internet Security Risk, Part 1: What is Risk Assessment”, Jun. 11, 2002, Security Focus, pp. 1-5. |
| Kaczmarski, M., et al., “Beyond backup toward storage management,” 2003, IBM Systems Journal, vol. 42, Issue 2, pp. 322-337 (16 total pages). |
| Parkhouse, Jayne, “Pelican SafeTNet 2.0”, [online] Jun. 2000, SC Magazine Product Review, [retrieved Dec. 1, 2003] Retrieved from the Internet: <URL: http://www.scmagazine.com/standalone/pelican/sc—pelican.html>. |