JP2009524122A - Emergency data storage service - Google Patents

Abstract

A method and system for initiating a data backup process on a computer system is described. One method requires that the data to be backed up is specified. The computer system is monitored for the occurrence of a backup trigger event. When the trigger occurs, the data backup process is started.
[Selection] Figure 1

Description

Field

  [0001] Embodiments described herein generally relate to the storage of digital information, and more specifically to automatic backup of digital information in the event of an impending or emergency.

Related technology

  [0002] One convenient aspect of digital data is the ease with which it can be manipulated. Files in a computer system can be edited, moved, duplicated, and deleted quickly and easily. Unfortunately, digital data is equally prone to loss. A single command mistake, a virus-infected file, or a hard drive failure is enough to erase thousands of files each of which may be valuable.

  [0003] At least three factors affect the value of electronically stored data. If it takes a lot of time for the data to be entered into the computer, the loss of the data means that more time must be spent to recreate the data. For example, companies may have a database in which all of their company information is stored. If the hard drive that contains the database crashes, even if it can be recreated, such a recreation takes a lot of time.

  [0004] Some files have an associated monetary cost. Some small software companies allow users to purchase software for download over the Internet. If those files are destroyed by a virus and must be repurchased, the loss of those files represents the loss of money used to purchase those files.

  [0005] There are really only one file, and the loss of those files can be most damaging. Digital images of historical events, or email records of years of business interaction cannot be recreated and cannot be repurchased. Once only one piece of data is lost, no matter how much time or money you spend, you can't restore the missing data.

  [0006] One solution to the problem of storing digital information is a process that is often described as storing the information elsewhere, ie, "backuping" the data or creating a backup. . However, the backup process is generally inconvenient. In some cases, the backup is created by a time consuming process of manually replicating files to another location, such as a large number of floppy disks or a second hard drive. In other cases, automatic backup software is used to create the backup. Such software can at best only be set to start at a specific time, and starting at a specific time is inconvenient for those who want to use the computer at that given time. there is a possibility. In addition, these automatic backup processes are slow to operate. In many cases, several minutes pass while the software examines the computer system before any data is backed up.

  [0007] All prior art backup systems are proactive and in order to make any sense, they must be utilized before any actual crisis situation occurs. Such a system cannot cope with the situation by backing up important data immediately. Existing systems also cannot determine whether critical data needs to be backed up.

Overview

  [0008] Methods and indications for performing an emergency data storage service are described. In one embodiment, backup event triggers are defined and the computer is monitored to detect the occurrence of these triggers. If a trigger is detected, an equivalence heuristic is applied to determine whether the backup process should be initiated. In this embodiment, the automatic initialization of the backup process is not limited to a simple temporal trigger as is known in the prior art. System monitoring software may be applied to monitoring system events that may predict system failure, such as predicting a hard drive failure, for example, and detecting whether the system is approaching a temperature limit and / or system The monitoring software determines when a manual backup is performed. In addition, applying a weight test reduces the inconvenience to the user trying to use the computer because the backup process is less likely to start while the computer is in use.

[0009] In another embodiment, data to be backed up is identified before the backup process is initiated. The computer is monitored for backup event triggers and the backup process is initiated when detected. By locating data to be stored before the backup process begins, the prior art problem of a slow backup process is greatly reduced.
In general, this specification discloses a method and system for initiating a data backup process on a computer system.
One method requires that the data to be backed up is specified. The computer system is monitored for the occurrence of a backup trigger event. When the trigger occurs, the data backup process is started.

  [0011] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments of the invention and together with the description, serve to explain the principles of the invention.

Detailed description

  [0019] A method and system for providing an emergency data storage service is described. Reference will now be made in detail to some embodiments of the invention. While the invention will be described in conjunction with the alternative embodiment (s), it will be understood that those alternative embodiments are not intended to limit the invention to these embodiments. I will. On the contrary, the invention is intended to cover alternatives, modifications, and equivalents, which may be included within the spirit and scope of the invention as defined by the appended claims.

Notation and terminology
[0020] Furthermore, in the following detailed description of the present invention, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be recognized by one skilled in the art that the present invention may be practiced without these specific details or with their equivalents. In other instances, well-known methods, procedures, components, and circuits have not been described in detail as not to unnecessarily obscure aspects of the present invention.

  [0021] The portions of the detailed description that follow are presented and discussed in terms of methods. Although the steps and ordering of those steps are disclosed in the figures herein (eg, FIGS. 3, 5, and 6) that illustrate the operation of this method, such steps and ordering are typical. Embodiments of the present invention perform various other steps, or variations of the steps described in the flowcharts of the figures herein, and in an order different from the order described and described herein. Well suited to perform.

  [0022] Some of the detailed description that follows is presented in terms of procedures, steps, logical blocks, processing, and other symbolic representations of operations on data bits that can be performed on computer memory. These descriptions and representations are the means used by those familiar with data processing techniques to most effectively convey the content of their work to others skilled in the art. Procedures, computer-executed steps, logical blocks, processes, etc., are generally considered herein as a self-consistent sequence of steps or instructions that yields the desired result. A step is a step that requires physical manipulation of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated in a computer system. It has been found that calling these signals bits, values, elements, symbols, characters, words, numbers, etc. may be convenient primarily for common use.

  [0023] It should be noted, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. As will be clear from the discussion below, throughout the present invention, unless otherwise specifically indicated, “access”, “write”, “include”, “test”, “use”, “examine” Considerations using terms such as “,” “associate,” “identify”, etc., manipulate data represented as physical (electronic) quantities in the computer system registers and memory, and the computer system memory, or registers, Or other such information storage, transmission, or reference to operations and processes of a computer system or similar electronic computing device that translates into other data that is also represented as a physical quantity within the display device. Is done.

Typical computer system and network
[0024] Referring now to FIG. 1, a block diagram of a typical computer system 112 is shown. It will be appreciated that the computer system 112 described herein represents an exemplary configuration of an operating platform in which embodiments of the present invention may be implemented. However, other computer systems having different configurations may be used in place of computer system 112 within the scope of the present invention. That is, the computer system 112 can include elements other than those described in connection with FIG. For example, in some embodiments, a media server or personal video recorder (PVR) is utilized in place of system 112. In another embodiment, the system 112 is connected to network attached storage (NAT). Further, the present invention may be implemented not only on a computer system such as computer system 112, but also on any system that can be configured to allow the present invention to be implemented.

  [0025] The computer system 112 is for an address / data bus 100 for communicating information, a central processing unit 101 coupled to the bus 100 for processing information and instructions, and for the central processing unit 101. Volatile memory unit 102 (eg, random access memory [RAM], static RAM, dynamic RAM, etc.) coupled to bus 100 and static information for processing unit 101 for storing information and instructions And a non-volatile memory unit 103 (eg, read only memory [ROM], programmable ROM, flash memory, etc.) coupled to the bus 100 for storing instructions. Computer system 112 may also include an optional display device 105 coupled to bus 100 for displaying information to a computer user. Computer system 112 further includes a data storage device 104 (eg, a disk drive) for storing information and instructions.

  [0026] Further included in the computer system 112 is an optional alphanumeric input device 106. Device 106 can communicate information and instruction selections to central processing unit 101. The computer system 112 also includes an optional cursor control or pointing device 107 coupled to the bus 100 for communicating user input information and command selections to the central processing unit 101. The computer system 112 also includes a signal communication interface (input / output device) 108 that is coupled to the bus 100 and may be a serial port. The communication interface 108 may also include a wireless communication mechanism. Using communication interface 108, computer system 112 may be communicatively coupled to other computer systems via a communication network, such as the Internet or an intranet (eg, a local area network).

  [0027] It is understood that embodiments of the present invention may be implemented on many different types of computer systems 112. Examples are desktop computers, workstations, servers, media servers, laptops, game consoles, and personal digital assistants (PDAs), as well as wireless telephones, media center computers, digital video recorders, digital cameras, and digital audio playback or recording devices. Including, but not limited to, other electronic devices with computing capabilities and data storage capabilities.

  [0028] Referring now to FIG. 2, a block diagram of an exemplary computer network in which embodiments of the present invention may be implemented is shown. Computer system 112 is shown communicating with server 212 via network connection 202. Network connection 202 may be any means that enables data transfer between system 112 and server 212. In one embodiment, network connection 202 is a local area network (LAN). In such embodiments, system 112 and server 212 may be located close to each other, such as in the same office. In another embodiment, the network connection 202 is the Internet and the server 212 need not be physically close to the system 112. In another embodiment, the network connection 202 is a wireless connection. In another embodiment, the network connection 202 is a direct connection, such as a universal serial bus (USB) connection. In other embodiments, other communication methods may be used between the system 112 and the server 212. Other embodiments may be indirect communications, for example, system 112 is behind a firewall. In some embodiments, multiple systems 112 may connect to a single server 212. In some embodiments, a single system 112 can connect to multiple servers 212. In a further series of embodiments, a single computer system may serve as both system 112 and server 212, for example, by utilizing separate hard drives to back up data.

  [0029] In FIG. 2, computer system 112 is shown executing system monitoring software 250. In one embodiment, the system monitoring software 250 has three roles: preparing the data stored on the computer system 112 for backup, monitoring the computer system 112 for backup event triggers, and data Can be backed up to data stored on the computer 112 by sending to the server 212 via the network connection 202. These three roles are described in more detail below in connection with further exemplary embodiments of the present invention.

  [0030] In some embodiments, the computer system 112 is coupled to an optional environmental monitor 251. In such an embodiment, environmental monitor 251 is a detector or a series of detectors that provide information to system 112 about the environmental conditions surrounding system 112. In one embodiment, the environmental monitor 251 is a security system that monitors unauthorized intrusion around the system 112, such as a residential intrusion monitoring system. In another embodiment, environmental monitor 251 detects a fire and is, for example, a smoke detector.

  [0031] In some embodiments, the computer system 112 is coupled to an optional uninterruptible power supply (UPS) 252. In such an embodiment, the system 112 may have a UPS 252 for a limited period of time, even if normal power is turned off, for example, even after the power supply to the office where the system 112 resides is cut. Receive power from. In one embodiment, UPS 252 is an external unit. In another embodiment, UPS 252 is integrated into system 112. In one embodiment, the system 112 detects when normal power has stopped and the UPS 252 is supplying power.

  [0032] In some embodiments, the computer system 112 incorporates an optional hardware monitoring sensor 260 that is used to detect events that can predict hardware failure. In some such embodiments, the hardware monitoring sensor 260 is located near the data storage device 104. In one embodiment, hardware monitoring sensor 260 includes a voice sensing component, such as a microphone. In another embodiment, hardware monitoring sensor 260 includes a temperature sensing component, such as a thermocouple or a temperature sensor. In one embodiment, hardware monitoring sensor 260 is coupled to system 112 and the detected reading is available to system monitoring software 250, which generates a backup event trigger based on a signal from sensor 260. be able to.

  In FIG. 2, server 212 is shown to execute backup management software 290. In one embodiment, the backup management software 290 has four roles: monitoring the computer system 112, initiating a backup of the computer system 112 under certain circumstances, and data transmitted from the computer system 112. For retrievable storage and restoring information to the computer system 112 as needed. These four roles are described in more detail below in connection with further exemplary embodiments of the present invention. In some embodiments, backup management software 290 performs these roles remotely, for example, by collecting and transferring information via network connection 202. In other embodiments, the backup management software 290 is partially executed on the system 112 and performs these roles locally. In other embodiments, a combination of these two approaches is utilized.

Client operation-system monitoring software
[0034] Referring now to FIG. 3, a flowchart 300 of the operation of the system monitoring software 250 according to one embodiment of the present invention is shown. In step 310, the system monitoring software 250 executes a data storage preparation task. In step 320, the system monitoring software 250 monitors the client system, i.e., system 112, for a backup event trigger. If a backup event trigger is detected, at step 330, the system monitoring software 250 initiates the backup process.

Preparing for data storage
[0035] According to one embodiment of the present invention, several pre-backup operations are performed on the data in step 310 in order for the backup of data from the system 112 to the server 212 to proceed quickly and efficiently. Is done. In the illustrated embodiment, these data storage preparation tasks are continuously performed on the system 112. In this embodiment, when new data is created or stored on the system 112, the system monitoring software 250 may use the backup process to expedite the backup process when the next backup event trigger is detected. Work to prepare this data. In other embodiments, the data storage preparation task is performed at a specified time or under specified conditions, such as when the system 112 enters an idle state. In other embodiments, the data storage preparation task is performed only immediately prior to sending data over the network connection 202. In some embodiments, a combination of these approaches is utilized. For example, in one embodiment, high priority data must be prepared for data protection immediately after the data is stored in the system 112 while less important data has been idle for a certain period of time. Prepared only after.

  [0036] Several operations fall within the scope of data storage preparation. In one embodiment, one such operation is data compression. In another embodiment, the data is encrypted. In another embodiment, the data is assigned a priority level. In another embodiment, the data is sorted on the hard disk and arranged to speed up access time during backup. In another embodiment, the data is replicated to a separate area of the hard drive or another hard drive to speed up access times during backup. In other embodiments, other data storage preparation tasks or operations are performed. The main factor that affects which tasks are executed and when tasks should be executed is to reduce the time required between the backup event trigger and the transmission of data from the system 112 to the server 212 It is a desire to do. If critical tasks such as data transmission instructions, data compression, and data stream encryption are processed before the backup event trigger is detected, the delay between such detection and the start of data transmission Is required to be very small.

Data compression
[0037] In some embodiments, data compression is part of step 310. Data compression speeds up the backup process by reducing the number of bytes that must be transferred over the network connection 202. Also, in embodiments where data replication is utilized, as discussed below, data compression reduces the amount of storage space used by the system monitoring software 250 to store the replicated data. Depending on the type of compression routine selected and the size and type of data being compressed, data compression (and decompression) can require a significant amount of time and processor cycles. In embodiments where data compression is performed before a backup event trigger is detected, the amount of time between the detection of the backup event trigger and the transmission of data from the system 112 to the server 212 is such that the data is already compressed. Since it is prepared for transfer, it is greatly reduced.

  [0038] In some embodiments, the type of data compression utilized is selected from a group of so-called "lossless" compression routines that allow data compression and subsequent decompression without any loss of initial quality. . Many such compression routines are known in the art, such as, for example, run length encoding. In other embodiments, a “lossy” compression routine is used to allow more data compression than is possible with lossless compression. Some embodiments utilize a combination of lossy and lossless compression routines. In one such embodiment, the user can select what type of data should be stored without loss and which can be backed up with some loss of initial quality. In such embodiments, important or indispensable data, e.g. data that cannot be modified, can be stored using lossless compression techniques, while less important data uses irreversible techniques. Compressed.

  [0039] In some embodiments, data compression occurs when data is input to the system. One such embodiment is combined with data replication as described below. This combination also allows the system monitoring software 250 to have a complete compressed copy of the data ready for backup, without requiring the user to decompress the data each time it is accessed. Allows unlimited access to the user's data stored on the system 112. In other embodiments, data compression occurs at a predetermined time, such as every night at midnight, or after the system has been idle for 15 minutes, or after a predetermined trigger has occurred. In other embodiments, only selected data is compressed when the data is input to the system 112, while other data is left uncompressed to facilitate local access to the data. . In one such embodiment, the text document can be immediately decompressed as needed, so the text document is immediately compressed, but it takes a significantly longer time to become accessible when needed. Required multimedia files are not compressed.

  [0040] In other embodiments, data is compressed only after a backup event trigger is detected. In another embodiment, whether compression is utilized depends on the type of backup event trigger detected. In one embodiment, data compression is not performed.

Data encryption
[0041] In some embodiments, data encryption is part of step 310. Data encryption makes the backup process more secure for the user by making it much more difficult for the data being transferred to be accessed by unauthorized persons. In some embodiments where server 212 and system 112 are owned and operated by different entities, including data encryption is stored on server 212 even if the data owner does not manage server 212. It can be ensured that the generated data remains secure.

  [0042] Many types of data encryption are known in the art and can be implemented in connection with embodiments of the present invention. Some embodiments combine data compression and data encryption such that the system monitoring software 250 performs both data compression and encryption simultaneously. In some embodiments, data encryption occurs when data is input to the system 112. In one such embodiment, combined with the data replication discussed below, in this embodiment, duplicate copies of the data are encrypted when the duplicate copy is created or immediately after it is created. . In other embodiments, data encryption occurs at a specified time or after a specified event, for example, new data every day at midnight or after the system 112 has been idle for 15 minutes. Encrypted. In other embodiments, only selected data is encrypted when the data is entered into the system 112, while other data is left unencrypted to facilitate user access.

  [0043] In other embodiments, the data is encrypted after a backup event trigger is detected. In other embodiments, whether the data is encrypted and what type of encryption is used depends on the type of backup event trigger detected. For example, if the detected backup event trigger is an impending hard drive failure, the user spends time encrypting the data and in some cases it is important that it is not encrypted rather than losing all of that data. You may want to back up your data. In other embodiments, data encryption is not included as part of the preparation for data storage.

priority
[0044] In some embodiments, data stored in system 112 is assigned a priority level as part of step 310. Not all data stored in the system 112 is of the same value. Most users want to save certain types of data, even at the expense of other files. By assigning different levels of importance to different data using the system monitoring software 250, the user can determine which files are given priority in the backup process.

  [0045] In some embodiments, the user assigns a priority level to the file. In one embodiment, this assignment is made on a file-by-file basis so that the user selects a priority level for each file. In another embodiment, the user determines priority levels for different types of files, and in such embodiments, the user may choose to prioritize digital photos over, for example, digital copies of movies. There is. In another embodiment, the user specifies the priority by location within the file system of system 112, in which the user can place the operating system files in a directory where all of their email messages are stored. May choose to have a higher priority. In another embodiment, the user can set rules regarding which priorities are assigned to files, and the system monitoring software 250 can set priority levels based on those rules. In this embodiment, the user does not need to assign a priority to every file, for example, when the system monitoring software 250 is installed when the system monitoring software 250 is installed. doc and. Any file that ends in jpg may be configured to have a higher priority than all other files. In other embodiments, users may assign priorities in different ways.

  [0046] In other embodiments, the system monitoring software 250 assigns priorities to the data. In one such embodiment, priority is assigned based on the frequency of access such that more frequently accessed user created files get a higher level of priority. In another embodiment, system monitoring software 250 identifies user-created content, such as word processing documents and digital photos, and assigns such files higher priority than operating system files. Composed. In another embodiment, a higher priority is automatically assigned to smaller files that can be backed up faster. In other embodiments, other approaches to assigning levels of importance to different files, file types, or locations within the file system are implemented.

  [0047] In some embodiments, both the user and the system monitoring software 250 assign priority levels to data on the system 112. In one such embodiment, the system monitoring software 250 assigns a default priority level to a given file based on preset rules, such as those described above, and the user assigns a different priority level. Can be selected.

  [0048] In some embodiments, multiple priority levels are assigned to the same data. In one such embodiment, users can assign priorities based on how they want their data to be saved when various backup event triggers are detected. For example, a user may assign a higher priority to a digital movie file for regular backups, but assign a significantly lower priority level to the same file if an emergency backup is initiated due to an impending hardware failure There is. In this way, the user has a high degree of flexibility in protecting his data.

  [0049] In different embodiments of the present invention, the rules under which the priority system operates can vary greatly. For example, in some embodiments, the user can specify priority rules to take into account the relative changes in the file and how important the file is, for example, High-priority files that have changed only slightly since the last time the file was backed up, with the idea that the fix is easy to recreate using an earlier backup than an entirely new file, It may be less important to the user than lower priority files that have never been backed up before. Similarly, a user can assign a priority level to a file when a full backup is to be performed, and a different priority level when an incremental backup is performed. Embodiments of the present invention allow many different priority rules to be applied to the data to account for many different situations.

  [0050] Priorities and the effect that various priority levels have on the backup process are discussed in more detail below with reference to further embodiments.

File relocation
[0051] In some embodiments, system monitoring software 250 rearranges data on data storage device 104 of system 112 as part of step 310. During the backup process, any file that is to be stored on the server 212 must be located on the data storage device 104. In embodiments where the data storage device 104 is a mechanical storage system, such as a hard disk drive (HDD), the files to be backed up are often scattered at various locations across multiple platters. Therefore, it takes time to move between files. One approach to reducing the time consumed by seeking data is file relocation where the system monitoring software 250 rearranges the data stored on the data storage device 104 before a backup event trigger is detected. It is. An embodiment incorporating this approach is described with reference to FIGS. 4a and 4b.

  [0052] Referring now to FIG. 4a, a top view representation of the data storage device 104, the hard disk drive, is shown. It is understood that embodiments of the present invention can be implemented in connection with many different types of data storage devices 104, not just hard disk drives of the type shown herein. The HDD 104 is shown as having a rotating platter 401, a moving arm 403, and a read head 405. The plurality of files to be backed up are shown on the platter 401 as files 411, 412, 413, 414, 415, 416 and 417. In order to back up these files, the arm 403 needs to move the read head 405 in turn to each of those files, a process known as seeking. The arm 403 must seek each file in turn and will move at least seven times to reach each file. Seeking adds extra time to the backup process and, if the hard drive is about to fail, places an additional burden on the component that can cause the hard drive to fail completely before all files are backed up.

  [0053] Referring now to FIG. 4b, a top view representation of the data storage device 104 is again shown in accordance with one embodiment of the present invention. In this embodiment, the system monitoring software 250 arranges the files to be backed up on the HDD 104 so that the files 411, 412, 413, 414, 415, 417 and 417 are located close to each other on the platter 401. Therefore, the file rearrangement is executed in step 310. If a backup event trigger is detected and these files need to be backed up, the arm 403 does not have to travel so many times or too far to reach all of the files to be backed up. This both saves time and reduces the burden on HDD 104 components.

  [0054] In some embodiments incorporating both a priority system and file relocation, file relocation takes into account the relative priority of the data. For example, referring to FIG. 4b, files 411, 412, and 417 are all shown as being high priority files, files 413 and 415 are medium priority, and files 414 and 416 are low priority. In the case of the degree, the embodiment using both the priority and the file relocation is a higher priority data such as a file 411, 412, 417, 413, 425, 414, 416, for example. Arrange the files so that they are placed before.

  [0055] Other embodiments of the present invention do not incorporate file relocation.

Data replication
[0056] Some embodiments incorporate a data replication scheme as part of step 310 to expedite the backup process. As mentioned above, data compression and encryption techniques are incorporated into embodiments of the present invention to provide a faster and more secure backup process. However, both file compression and encryption reduce the speed at which the system 112 accesses the data. For example, in order for a user to open a digital movie file that has been compressed and encrypted by the system monitoring software 250, the file must first be decrypted and decompressed. For large files, this process can take several minutes. In embodiments that incorporate data replication, the files to be backed up are replicated either to another location on the data storage device 104 or to another data storage device available to the system 112. Thus, the file that the user wishes to access remains readily available without compromising the benefits gained by the data storage preparation process of step 310.

  [0057] In one such embodiment, the data is replicated as soon as the data is entered into the system 112 or modified. In other embodiments, the data is replicated at a specified time, such as at midnight every day, or after the system 112 has been idle for 15 minutes, or after a specified trigger has occurred. In other embodiments, certain specified types of data are replicated immediately, while other types are replicated at a specified time or after a specified trigger occurs. In other embodiments, data replication is combined with file relocation to better align the replicated files to be backed up on the hard disk drive.

  [0058] In some embodiments where both priority and data replication are performed, data replication and subsequent storage takes into account the relative priority of the data. For example, as shown in FIG. 4b, files 411, 412, and 417 are all shown as being high priority files, files 413 and 415 are medium priority, and files 414 and 416 are low priority. In an embodiment that utilizes both priority and data replication, higher priority data is lower priority, such as replica files 411, 412, 417, 413, 425, 414, 416, for example. The duplicate files are arranged so that they are placed before the data.

  [0059] In other embodiments, only designated files are data replicated. In yet another embodiment, data replication is not utilized.

Backup event trigger monitoring
[0060] In some embodiments of the present invention, system monitoring software 250 performs step 320 of monitoring client system 112 for backup event triggers. In one embodiment, a backup event trigger is defined in the system monitoring software 250 as a condition that initiates the backup process defined below if conditions are met. The conditions under which a backup event trigger can be configured vary in different embodiments. One consideration in enumerating the set of backup event triggers for a particular embodiment is that under what conditions it would be beneficial for the user to automatically back up the data stored in the system 112. What do you think? A typical list of backup event triggers is shown in Table 1 below. This list is not exhaustive and it is understood that other embodiments incorporate other backup event triggers.

Time reservation backup
[0061] In some embodiments, the system monitoring software 250 is configured to execute a time reservation backup scheme. In one embodiment, the time reservation backup scheme causes the system monitoring software 250 to generate a backup event trigger at a preset time. In some embodiments, this time is set by the user, for example, the user may set the system monitoring software 250 to start at midnight every Monday night. In another embodiment, system monitoring software 250 selects a time to start a backup. In one such embodiment, the system monitoring software 250 is configured to select times when the user is unlikely to use the system 112 based on detected past usage. In other embodiments, the time-scheduled backup trigger occurs after a predetermined period from the last successful backup, for example, the system monitoring software 250 schedules the backup to occur 72 hours after the last successful backup operation. To do. One consideration when implementing a time-reserved backup scheme is that data on the system 112 is regularly and regularly protected.

System idle state backup
[0062] In some embodiments, the system monitoring software 250 is configured to execute a system idle state backup scheme. In such an embodiment, system monitoring software 250 generates a system idle state backup trigger after a predetermined period of time has passed since the last operation of system 112. In one such embodiment, it is determined whether the system 112 is not operating the HDD. In another embodiment, the operation of the system is determined based on the presence of input from a keyboard, mouse, or other input device. One consideration when implementing the system idle state backup scheme is that the backup operation of the system monitoring software 250 prevents user access to the system 112 while providing normal protection for data on the system 112. It is not. In this case, the backup process may be suppressed during the period when user activity is detected.

  [0063] In one embodiment, the system monitoring software 250 is configured to execute a system idle state backup scheme and an incremental backup scheme, as described below. In this embodiment, for example, when the system 112 enters an idle state, the system monitoring software 250 generates a system idle state backup trigger and the backup process is initiated. The backup process is suspended when the system 112 is no longer idle, for example, when a user accesses the system 112. When the second backup process is started, data already transmitted during the first interrupted backup process is not retransmitted.

User-initiated backup
[0064] In some embodiments, the system monitoring software 250 is configured to execute a user-initiated backup scheme. In such an embodiment, system monitoring software 250 allows a user to generate a user-initiated backup trigger, thereby initiating the backup process. One consideration when implementing a user-initiated backup scheme is that the user is often more familiar with when data that is truly important than the system monitoring software 250 has been entered into the system 112. Being able to act to protect data by initiating a backup process. A further consideration is that the user is more aware of whether the system 112 should be powered down or disconnected from the network connection 202 than the system monitoring software 250 and the backup process before this is done. Is that you can start.

New data storage backup
[0065] In some embodiments, the system monitoring software 250 is configured to implement a new data retention backup scheme. In such an embodiment, the system monitoring software 250 generates a new data retention backup trigger after a predetermined amount of new data has been stored on the system 112 since the last successful backup process. In one such embodiment, it is determined in step 310, ie how much new data has been entered into the system 112 in preparation for data protection. In one embodiment, the amount of new data is measured in bytes. In another embodiment, the amount of new data is measured by the number of individual files. In another embodiment, the amount of new data is measured relative to the type of file stored, for example, a text document requires significantly less bytes than a digital movie file, but with equal importance. Can be given. In some embodiments, the user configures system monitoring software 250 to set a threshold level for the new data retention backup trigger. In other embodiments, the system monitoring software 250 determines an appropriate threshold. In one such embodiment, the threshold is determined by tracking the successful generation of new data during a set period of time, for example, system monitoring software 250 generates 150 new files in system 112 every day. If it is recognized, the appropriate threshold value may be 300 new files, which are the generation amount for about two days.

  [0066] In some embodiments, the new data retention backup scheme is implemented in conjunction with a priority system. In such embodiments, higher priority data is treated as more important than the same amount of lower priority data. For example, the system monitoring software 250 generates a backup trigger after 10 megabytes of low-priority data has been accumulated since the last successful backup of the system 112, and only 1 megabyte of high-priority data is accumulated. After that, a backup trigger may be generated.

Power failure backup
[0067] In some embodiments, the system monitoring software 250 is configured to execute a power failure backup scheme. In such an embodiment, system 112 is configured to detect an impending power failure. In one embodiment, the system 112 is connected to an uninterruptible power supply (UPS) 252 and the UPS 252 and the system 112 are configured to allow the system 112 to determine when normal power has stopped and generate a power outage backup trigger. Is done. In another embodiment, the system 112 is powered by a depleted power source and is configured to detect when the power source is about to be exhausted. For example, laptop computers operate on battery power. One consideration is that data is protected when power to the system 112 is stopped due to the detection of an imminent power failure.

Hard disk failure
[0068] In some embodiments, the system monitoring software 250 is configured to execute a hard disk failure backup scheme. In such an embodiment, the system monitoring software 250 is configured to generate a hard disk failure backup trigger. In some embodiments, the system monitoring software 250 tracks factors that affect HDD performance and expected life and can predict system failure. In such an embodiment, when the HDD is exposed to more factors than expected to shorten its operating life, the system monitoring software 250 may reduce the frequency of backup triggers to reduce the risk of losing data due to a hard disk failure. Increase.

  [0069] One factor that affects the expected life of the HDD is the life of the HDD. In one embodiment, the system monitoring software 250 determines the approximate lifetime of the HDD. A typical method for determining the lifetime of an HDD is to check the system registry of the operating system of the system 112 to determine when the HDD is installed in the system 112, or to know the HDD model number or serial number. A comparative reference to the list of production periods is included. In another embodiment, the system monitoring software 250 considers the number of write / read cycles performed by the hard drive that affects the useful life of the hard drive. In another embodiment, the system monitoring software 250 considers the number of on / off cycles experienced by the hard drive that affects the useful life of the hard drive. In further embodiments, some or all of these approaches are combined in considering how often to generate backup triggers.

  [0070] Another factor that affects the life of the HDD is environmental factors such as temperature. HDDs that operate continuously at extreme temperatures have a shorter operating life than HDDs that operate only in a controlled environment. Similarly, an HDD that is operated in a system that does not have a cooling fan or in a system in which the cooling fan has failed has a shorter operating life than an HDD that operates in a cooled system. In one embodiment, the system 112 incorporates a hardware monitor sensor 260 that is a system temperature monitor. The system monitoring software 250 is configured to record the system temperature and compare the average operating temperature to the accumulated statistics of the average system temperature and expected HDD life.

  [0071] A related factor that affects the life of the HDD is the temperature difference to which the HDD is exposed. Rather than operating at extreme temperatures, subjecting the HDD to large sudden temperature changes can greatly reduce the expected HDD life. In one embodiment, the system 112 incorporates a hardware monitor sensor 260 that is a system temperature monitor. The system monitoring software 250 is configured to record the system temperature, determine the temperature difference, and compare it with accumulated statistics of the temperature difference and expected HDD life.

  [0072] Other factors that affect the expected life of the HDD are known in the art. In other embodiments, system monitoring software 250 and system 112 are configured to allow system monitoring software 250 to recognize these factors and adjust the frequency of backup triggers accordingly.

  [0073] In some embodiments, the system monitoring software 250 and the system 112 are configured to allow detection of factors that can predict an impending HDD failure. In some such embodiments, the combination of hardware incorporated in the system 112 and instructions incorporated in the system monitoring software 250 allows for recognition of an indication of HDD failure.

  [0074] One such symptom is a change in sound produced by the operation of the HDD. For example, some HDDs may be loud and may sound crisp immediately before a serious HDD failure. In some embodiments, a microphone located near the HDD 104 is incorporated into the system 112 to measure sound emitted during operation of the HDD, for example, to measure sound pitch and amplitude. In other embodiments, a sound detection sensor is incorporated in the HDD 104 itself to achieve a similar purpose. By comparing the emitted sound with the expected acoustic profile, the system monitoring software 250 can predict a failure of the HDD that is likely to fail and generate a backup trigger. In some embodiments, the system monitoring software 250 compares the current sound with an acoustic profile generated from past performance of this same HDD 104. In other embodiments, the system monitoring software 250 is configured to use a predetermined acoustic profile stored by a particular HDD manufacturer.

  [0075] Another indication of an HDD failure that is likely to occur is a sudden increase in the operating temperature of the HDD. In some embodiments, a temperature sensor located near the HDD 104 is incorporated into the system 12 to measure the operating temperature. In other embodiments, a temperature sensor is incorporated into the HDD 104 itself to achieve a similar purpose. By detecting a sudden increase in operating temperature, the system monitoring software 250 can predict an imminent HDD failure or failure and generate a backup trigger.

Environmental factor backup trigger
[0076] In some embodiments, the system monitoring software 250 is configured to execute an environmental factor backup scheme. In such an embodiment, the system monitoring software 250 is configured to generate an environmental factor backup trigger when a predetermined environmental condition occurs. In some embodiments, the system 112 is coupled to an environment monitor 251 that provides information about the environment in which the system 112 is present. In one embodiment, system 112 is an office workstation and environmental monitor 251 is a security system that monitors for unauthorized entry into the office. If a trespass occurs, the environmental monitor 251 detects the trespass, the system 112 is informed of it, and the system monitoring software 250 generates a backup trigger to cause the system 112 to be stolen or destroyed, Alternatively, the backup process is initiated so that the data is backed up before being disconnected from the server 212 otherwise. In another embodiment, environmental monitor 251 is a fire detection system that allows system monitoring software 250 to initiate a backup process when a fire is detected, and event system 112 is damaged or destroyed. Save data in case. In other embodiments, other environmental monitors 251 are used to detect other conditions limited to the system 112 that should trigger a backup trigger. In some embodiments implementing both environmental factor backup triggers and weighted backup triggers, some or all environmental factor backup triggers are weighted to facilitate a rapid backup process.

Weighted backup trigger
[0077] In some embodiments, backup event triggers are given various weights or levels of importance. In such embodiments, a backup urgency scheme is often implemented, as discussed in more detail below. In such an embodiment, a backup event trigger, such as a time-scheduled backup, receives less weight than an impending hardware failure. In other embodiments, these weightings may change over time. In one such embodiment, for example, as time-scheduled backups receive progressively higher levels of importance, the backups have been postponed longer.

Backup process
[0078] In some embodiments, the system monitoring software 250 is configured to perform the backup process step 330 after a backup event trigger is detected. In other embodiments, the system monitoring software 250 allows a separate backup process to be performed. In some embodiments, the backup process 330 involves sending data stored on the system 112 to the server 212 via the network connection 202. Some embodiments include a backup urgency test as part of step 330. Some embodiments utilize a priority scheme to determine which data to send first. Some embodiments utilize an incremental backup scheme for data transmission.

Backup urgency test
[0079] In some embodiments, a backup urgency test is performed after a backup event trigger is detected. In such an embodiment, the need for immediate backup is assessed against other pertinent matters, and if the need for backup is greater, the backup begins immediately, otherwise the backup process is postponed. Typical factors that affect each aspect of this quantitative heuristic are described below, and in other embodiments of the system monitoring software 250, other factors are incorporated into the backup urgency test.

  [0080] In some embodiments, the need for backup is affected by the type of backup event trigger detected. In one embodiment, if an impending hard drive failure or failure that may occur is detected, the need for backup is the highest level of urgency. In another embodiment, time-reserved backups are given a much lower level of urgency. One consideration when setting the level of urgency for various backup event triggers is how prone to data loss on the system 112 if the backup process does not begin immediately.

  [0081] In some embodiments, the need for backup is affected by the length of time since the last successful backup. In one such embodiment where a time-reserved backup has been postponed multiple times, each successive backup urgency test gives a higher urgency to the need for backup until the backup is performed.

  [0082] In some embodiments where a priority system for data is implemented, the need for backup is affected by the priority of the data accumulated on the system 112 since the last successful backup. . For example, in one such embodiment, a higher backup need is required when 10 megabytes of high priority data is accumulated than when 10 megabytes of low priority data is accumulated, for example. Are assigned by the system monitoring software 250.

  [0083] In some embodiments, the need for backup is compared to the current level of operation in the system 112. In some such embodiments, how the user is accessing the system 112 is considered, and the system monitoring software 250 balances the need for backup with the user's desire to access the system 112. take. One consideration is that the backup process often requires intensive access to system resources such as HDD and network connection access. Initiating a backup while the user is performing some task with long HDD or network access is inconvenient for the user and not an efficient use of the system 112.

  [0084] In one embodiment, the operation of HDDs on the system 112 is monitored to determine the operational level of the system 112. In another embodiment, the operation of the network connection is monitored to determine when the network connection 202 can send data to the server 212. In another embodiment, the use of input devices such as a mouse and keyboard is monitored to determine when the system 112 is idle. In another embodiment, the system monitoring software 250 and the screen saver program running on the system 112 are associated so that the backup process does not begin unless the system is idle long enough for the screen saver program to run. It is done. In other embodiments, other methods for determining the operating level of the system or network are incorporated.

  [0085] In other embodiments where a backup urgency test is not performed, the system monitoring software 250 monitors the operation of the system 112 and prevents the backup process from being performed whenever the system 112 is in use.

Data integrity
[0086] In some embodiments, various methods are incorporated to allow checking the integrity of the data after it is received. Many methods known in the art are appropriate to ensure the accuracy of the data, which is to generate a checksum and transmit the checksum information before transferring the data to the server 212. , Including but not limited to having the server 212 verify the integrity of the transmitted data. Other embodiments incorporate other systems that check data integrity.

Data encryption
[0087] In some embodiments, a secure encrypted connection must be established between the system 112 and the server 212 before data is transferred over the network connection 202. Many forms of encrypted connections are known in the art, including but not limited to secure socket layer (SSL) or secure shell (SSH), and are suitable for implementing embodiments of the present invention. . In other embodiments, a secure connection is not required before sending data. In one such embodiment, data encryption is incorporated during step 310 to reduce the risk that the data will be accessed by unauthorized personnel.

data transfer
[0088] Various embodiments of the present invention utilize various data transfer methods. Any method of reliably sending data from the system 112 to the server 212 via the network connection 202 can be used to implement embodiments of the present invention. In one embodiment, the Internet is used as a transfer medium and data is formatted according to the Internet protocol (IP). In other embodiments, different types of network connections 202 are utilized and data is encoded according to other data transfer protocols.

  [0089] In some embodiments, the system monitoring software 250 performs incremental storage of data. In such an embodiment, the system monitoring software 250 will only transfer data that has been added since the system 112 was last backed up. In one embodiment, identification of new data is performed as part of step 310. In another embodiment, new data is identified immediately prior to transmission as part of step 330. One consideration when deciding whether to perform an incremental backup is that the speed at which the full backup is completed is more important than having a complete separate backup record of the data on the system 112. It is whether there is. In other embodiments, incremental storage is omitted and instead all data to be backed up is sent each time the backup process is performed. This type of full backup is useful for systems that have rapidly changing data for archival purposes and systems that may be susceptible to attack by malicious programs or viruses. In some embodiments, a combination of these two approaches is incorporated. In one such embodiment, for example, a full backup is performed once a month and an incremental backup is performed weekly.

  [0090] In some embodiments, the backup process is performed until it is complete. In such embodiments, once data transfer begins, the data transfer continues until all data from system 112 has been transferred to server 212. In other embodiments, the backup process is paused each time a user accesses the system 112 for another purpose. In such embodiments, the use of the user's system 112 is not significantly harmed by performing the backup process. In other embodiments, whether the backup process can be suspended follows the same criteria as the backup urgency test described above. In one such embodiment, the backup process may change the result of the urgency test if, for example, high priority data is accumulated that forces the backup process to be performed at an inconvenient time. Is not paused until enough high-priority data is transferred. In another set of embodiments, the backup process can continue while the user accesses the system 112 but at a reduced rate. For example, the transfer of data over the network connection 202 can be used while the user is accessing the system 112 to allow the user to use the system 112 while not completely pausing the backup process. Network bandwidth, processing device bandwidth, and / or drive bandwidth.

Server operation-backup management software
[0091] Referring now to FIG. 5, a flowchart 500 of the operation of the backup management software 290 according to one embodiment of the present invention is shown. In step 510, the backup management software 290 remotely monitors the operation of the client system 112. In step 520, the backup management software 290 remotely initiates the backup process on the client system 112. In step 530, if the backup management software 290 initiates the backup process remotely, or if the system monitoring software 250 initiates the backup process, the backup management software 290 stores the data received from the client system 112 so that it can be retrieved. To do. In step 540, the backup management software 290 serves to restore the stored data to the client.

Remote monitoring
[0092] In some embodiments, the backup management software 290 is configured to perform remote monitoring of the system 112. In some embodiments, remote monitoring enables server 212 to act as a multiple security feature for system monitoring software 250 by remotely providing some multiplicity of essential tasks. In some embodiments, the backup management software 290 also monitors the system 112 for problems that are more difficult to detect on the client side.

Client backup event trigger
[0093] In some embodiments, the backup management software 290 multiplexes the monitoring of backup event triggers that occur in the system monitoring software 250 described above. In some such embodiments, the monitoring information available to the system monitoring software 250 is sent to the backup management software 290 via the network connection 202 and the same assessment of the current state is performed on the system 112 and the server 212. Done.

  [0094] In other embodiments, only selected information is transferred to the server 212, and the backup management software 290 monitors the system 112 for selected backup event triggers. For example, in one such embodiment in which the system monitoring software 250 incorporates hard drive failure detection, a current hard drive sound sample is transferred to the server 212 and the backup management software 290 sounds for an indication of an impending failure. To monitor. One consideration in determining which monitoring tasks to multiplex in backup management software 290 is that backup management software 290 can perform its monitoring role better than system monitoring software 250. That's right. For example, in the embodiment described above, off-site server 212 maintained by a company providing backup services to multiple clients may include the latest version of backup management software 290 that includes all available HDD acoustic profiles. High nature.

  [0095] In other embodiments of the backup management software 290, none of the monitoring tasks of the system monitoring software 250 are multiplexed.

Other monitoring tasks
[0096] In some embodiments, the backup management software 290 monitors the system 112 and the system monitoring software 250 for other issues or problems that should cause the backup process. In one embodiment, the backup management software 290 monitors the system 112 for data corruption or software degradation. Such irregular system performance can be caused by viruses, malware, or file system corruption. For example, if the backup management software 290 contacts the system monitoring software 250 using a status update request and receives a meaningless or unexpected response, the system 112 may endanger data stored in the system 112. Should be backed up immediately.

  [0097] In another embodiment, the backup management software 290 is configured to determine how much time has elapsed since the last successful backup process. In one embodiment, the backup management software 290 is configured to initiate the backup process after a predetermined amount of time has elapsed. In another embodiment, the backup management software 290 may be configured to contact personnel in the system 112, for example by email message, to inform those personnel that the system 112 has not been recently backed up.

  [0098] In another embodiment, the backup management software 290 is configured to initiate a remote backup when the system 112 is known to be in a compromised location. In one embodiment, for example, the server 212 is connected to multiple systems 112 within a city and the city is known to be in a major fire, earthquake, tornado, typhoon, or other similar crisis. The backup management software 290 can initiate a remote backup process on all systems 112 at the compromised location.

  [0099] In another embodiment, the backup management software 290 is configured to initiate a remote backup when the presence of a virus or system security threat is detected. In some embodiments, backup management software 290 is informed of a new virus that spreads through the Internet, such as a self-replicating email worm, and minimizes damage caused when one or more systems 112 are infected. Therefore, a remote backup of all systems 112 monitored by the backup management software 290 is initiated.

  [00100] Other embodiments incorporate other remote monitoring tasks.

Remote backup process
[0100] In some embodiments, the backup management software 290 is configured to initiate a remote backup process. In these embodiments, the backup management software 290 initiates a remote backup process in response to a backup event trigger, such as those described above, or in response to one of the other monitoring tasks described above.

  [0101] In some such embodiments, the backup management software 290 can signal the system monitoring software 250 to initiate the backup process. In one embodiment, the remote backup trigger undergoes the emergency balance test described above. In another embodiment, the remote backup trigger occurs immediately.

Storage of data in a removable form
[0102] In some embodiments, the backup management software 290 is responsible for retrievably storing data received from the system 112. In other embodiments, the backup management software 290 calls other programs that store the data in a retrievable manner. In many embodiments, special protection features are in place to ensure the safety of data stored on the server 212. In some embodiments, for example, a redundant array of independent disks (RAID) configuration is utilized to make data protection on the server 212 more reliable. In other embodiments, other data storage methods known in the art for securely storing data are used.

  [0103] In some embodiments, the backup management software 290 encrypts data to be stored. As already discussed, many types of encryption can be used with embodiments of the present invention.

  [0104] In some embodiments, the backup management software 290 allows external access to data stored on the server 212. One such embodiment allows users to access their data stored on the server 212 over the Internet. In this embodiment, users can access and display their data without having to expose the system 112 to external access, which allows for greater security of the system 112.

  [0105] In some embodiments, the backup management software 290 overwrites old data from the system 112 each time a backup process is performed. In such embodiments, the amount of storage space required to store data from system 112 can be more easily controlled. In other embodiments, the backup management software 290 stores data received from the system 112 in a new location each time the backup process is performed. Although consuming more space, these embodiments allow for better data archiving and, in the unlikely event, the system 112 is infected with malware or viruses, allowing better data recovery. . In such cases, the most recent backup of system 112 may also be infected, while older versions of the data from system 112 may not be infected. In some embodiments, these two approaches are mixed so that several backup sessions from the system 112 can coexist on the server 212 simultaneously. This strikes a balance between storage requirements and the use of archiving or restoration.

Data recovery
[0106] In some embodiments, the backup management software 290 allows data to be restored to the system 112. In some such embodiments, the backup management software 290 returns the data stored on the server 212 back to the system 112 via the network connection 202. In some embodiments, the owner or operator of server 212 may charge a fee for data restoration. Transferring data and restoring the data to system 112 is performed in many different ways in different embodiments. Any known approach for transferring and restoring data over a network connection is sufficient to implement embodiments of the present invention.

Special case-"LOADED GUN" backup process
[0107] As already discussed, one common drawback of conventional backup systems is that they are inherently slow in starting the actual backup process. Such systems are not designed to initiate the backup process in emergency situations where the time available to back up the system is limited and unknown. Some embodiments of the present invention are directed to methods and systems for providing data backup services in an emergency. In some embodiments, the backup process is continuously viable, allowing data transfer to begin immediately after an emergency backup event trigger is detected.

  [0108] Referring now to FIG. 6, a computer controlled flowchart representing a backup process according to one embodiment of the present invention is shown. With reference to FIGS. 2 and 6, an embodiment configured to provide a data backup service in an emergency will be described in detail.

  [0109] Referring now to step 605, in some embodiments, system monitoring software 250 monitors system 112 for new or changed data. When the system monitoring software 250 is executed for the first time, all data in the system 112 is registered as new data. After the first successful backup process, only data that has subsequently been added to the system 112 or only data that has changed since the last successful backup process is considered new. In some embodiments, the system monitoring software 250 can be configured to ignore specific files, file types, or locations within the file structure of the system 112. In these embodiments, the user may prioritize the protection of high-importance data and select certain non-important files, such as operating system files, temporary storage files, or programs that are easy to reinstall. You can choose not to back up. In other embodiments, only new data of a particular type or within a fixed location in the file structure of system 112 is registered as new data. In some embodiments, the degree of modification of an existing file is also identified, which means that the user has different levels of importance for slightly modified files, heavily modified files, and completely new files. You can make it possible to specify. In these embodiments, the user is given more control over which data is saved by excluding data by default and giving the user the choice of which file types or directories to back up. The

  [0110] Referring now to step 610, in some embodiments, the system monitoring software 250 prepares new data for storage. In these embodiments, one consideration is that if an emergency backup event trigger occurs, the data is sent to the system monitoring software 250 in such a way that no search is required to locate the data before transmission. It is to be specified. In one embodiment, this is performed by the system monitoring software 250 creating or updating a list that identifies the location of all new data in the system 112, eg, a database that stores the addresses of all new data files. The In another embodiment, a file relocation scheme as described with reference to FIG. 2 is utilized. In another embodiment, a data replication scheme as described with reference to FIG. 2 is utilized. In all of these exemplary embodiments, the system monitoring software 250 locates all new data in the system 112 before an emergency occurs and requires a search for new data. No time is lost.

  [0111] In some embodiments, step 610 also includes data compression. A consideration in these embodiments is the speed of transmission, because less time is required to send the compressed data to the server 212 via the network connection 202. In an emergency, faster transmission of data can mean that more data is backed up before transmission is terminated.

  [0112] In some embodiments, step 610 also includes data encryption. A consideration in these embodiments is whether security is an issue both during transmission and after the data is stored on the server 212. If server 212 and network connection 202 are both trusted, encryption is less important than if server 212 is remote and network connection 202 is an Internet connection.

  [0113] In some embodiments, step 610 also includes setting a data priority flag. In these embodiments, as described above, the relative importance of the data can be set. In an emergency, higher priority data can be transmitted before lower priority data, and even if transmission ends before the backup process is completed, high priority data can be stored. Make sure.

  [0114] Referring now to step 620, in some embodiments, system monitoring software 250 monitors system 112 for emergencies. In other embodiments, the system monitoring software 250 monitors the environment of the system 112 for emergencies. In other embodiments, these features are combined, and in yet another form, the system monitoring software 250 is configured to monitor the system 112 for other backup event triggers. One consideration when choosing which event to monitor is whether a particular situation can interfere with the backup process. Such situations, including environmental situations such as power outages, hard drive failures, and fire or security system warnings, are as described above.

  [0115] Referring now to step 625, in some embodiments, the backup management software 290 monitors the system 112 for emergencies. In other embodiments, the backup management software 290 monitors the environment of the system 112 for emergencies. In other embodiments, these features are combined and the backup management software 290 is configured to monitor the system 112 for other backup event triggers. Again, one consideration when selecting events to monitor is how much a particular event is likely to hinder the success of the backup process. Scenes including the situation described in detail with respect to step 620 and the situation of monitoring other environmental factors such as fires or natural disasters that occur near the system 112 are as described above.

  [0116] Referring now to step 630, an emergency backup event trigger has been detected.

  [0117] Referring now to step 640, in some embodiments, the system monitoring software 250 initiates a backup process. In other embodiments, the backup management software 290 initiates the backup process by sending a command or series of commands to the system 112 via the network connection 202. In some embodiments, the network connection 202 must be established before data transmission can begin. In another embodiment, the network connection 202 is already established. Data begins to be transmitted from system 112 to server 212 via network connection 202. In embodiments where a priority data system is implemented, higher priority data is transmitted before lower priority data. In other embodiments, smaller files are sent before larger files. One consideration that applies to all embodiments is that the data transmission begins as soon as possible so that the largest amount of data is transmitted to the server 212 before the transmission is completed.

  [0118] An embodiment of the present invention has been described. Although the invention has been described in specific embodiments, it should be understood that the invention should not be construed as limited by such embodiments, but rather construed according to the claims that follow.

FIG. 2 is a block diagram of a typical computer system in which embodiments of the present invention can be implemented. 1 is a block diagram of an exemplary computer network in which embodiments of the present invention may be implemented. 5 is a flowchart of the operation of system monitoring software according to an embodiment of the present invention. 1 is a diagram of a hard disk drive in which embodiments of the present invention can be implemented. It is a figure of the hard disk drive by which embodiment of this invention was mounted. 5 is a flowchart of the operation of backup management software according to an embodiment of the present invention. 4 is a flowchart of a backup process according to an embodiment of the present invention.

Claims (10)

A method for initiating a data backup process on a computer system, comprising:
Identifying data to be stored on the computer system;
Monitoring the computer system for the occurrence of a backup trigger event;
Applying a weighted heuristic to determine whether to initiate a backup process in response to the occurrence of the backup event trigger.   The monitoring step includes monitoring a mechanical data storage device coupled to the computer system, and the backup trigger event includes an indication of an imminent failure that may occur in the mechanical data storage device. The method of claim 1.   The monitoring step includes monitoring the audio signal generated by an audio sensing device located within the computer system and in close proximity to the mechanical data storage device, wherein the mechanical data storage device is 3. The method of claim 2, further comprising determining from the audio signal whether it indicates an indication of a mechanical storage system failure.   The monitoring step includes monitoring the temperature signal generated by a temperature sensing device located within the computer system and located in close proximity to the mechanical data storage device, wherein the mechanical data storage device is The method of claim 2, further comprising determining from the temperature signal whether it indicates an indication of a mechanical storage system failure.   The method of claim 1, wherein the monitoring further comprises detecting a threat to the computer system.   6. The method of claim 5, wherein the monitoring step further comprises monitoring a security system that detects an intrusion of the computer into the environment.   The method of claim 1, further comprising assigning a level of importance to the backup event trigger.   The method of claim 7, wherein the equivalence heuristic includes determining whether a current operation on the computer is more important than the level of importance of the backup event trigger. Detecting whether the computer switches between an active state and an idle state;
Initiating an incremental backup process in response to the computer switching to an idle state;
The method of claim 7, further comprising: pausing the incremental backup process in response to the computer switching to an active state.   The method of claim 1, wherein the monitoring further comprises remotely monitoring the computer system for the occurrence of the backup event trigger.

Images