WO2007067699A2 - Services de conservation de donnees de secours - Google Patents

Services de conservation de donnees de secours Download PDF

Info

Publication number
WO2007067699A2
WO2007067699A2 PCT/US2006/046730 US2006046730W WO2007067699A2 WO 2007067699 A2 WO2007067699 A2 WO 2007067699A2 US 2006046730 W US2006046730 W US 2006046730W WO 2007067699 A2 WO2007067699 A2 WO 2007067699A2
Authority
WO
WIPO (PCT)
Prior art keywords
backup
data
monitoring
computer
monitoring software
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/US2006/046730
Other languages
English (en)
Other versions
WO2007067699A3 (fr
Inventor
William Samuel Herz
Andrew C. Fear
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nvidia Corp
Original Assignee
Nvidia Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US11/298,173 external-priority patent/US8402322B2/en
Priority claimed from US11/297,985 external-priority patent/US9122643B2/en
Application filed by Nvidia Corp filed Critical Nvidia Corp
Priority to CN2006800459961A priority Critical patent/CN101326498B/zh
Priority to JP2008544511A priority patent/JP4904365B2/ja
Publication of WO2007067699A2 publication Critical patent/WO2007067699A2/fr
Publication of WO2007067699A3 publication Critical patent/WO2007067699A3/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operations
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1458—Management of the backup or restore process
    • G06F11/1461—Backup scheduling policy
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/86—Event-based monitoring

Definitions

  • Embodiments here described relate to the preservation of digital information generally, and more specifically to automated backup of digital information in urgent or emergency situations.
  • Prior art backup systems are all preventative; in order to have any value at all, they must be utilized before any actual crisis situation occurs. Such systems cannot react to a situation by immediately backing up crucial data. Nor can existing systems determine whether there is a need to backup crucial data.
  • backup event triggers are defined, and a computer is monitored to detect occurrences of these triggers. If a trigger is detected, a balancing heuristic is applied to determine if a backup process should be initiated or not.
  • automated initialization of the backup process is not limited to a simple time trigger, as is known in the prior art.
  • system monitoring software can be applied to monitor system events that potentially predict system failure, e.g., predict that a hard drive is failing, that detect if the system is approaching a thermal limit, and/or determine when a manual backup is done. Further, by applying a balancing test, the inconvenience for a user trying to use the computer is reduced, as a backup process is less likely to begin while the computer is in use.
  • data to be backed up is identified before the backup process is initiated.
  • the computer is monitored for a backup event trigger, and upon detection, the backup process is initiated.
  • One method calls for the data to be backed up to be identified.
  • the computer system is monitored for the occurrence of a backup trigger event. If the trigger occurs, a data backup process is initiated.
  • Figure 1 is a block diagram of an exemplary computer system upon which embodiments of the present invention may be implemented.
  • Figure 2 is a block diagram of an exemplary computer network upon which embodiments of the present invention may be implemented.
  • FIG. 3 is a flowchart of the operation of system monitoring software, in accordance with one embodiment of the present invention.
  • Figure 4a is a representation of a hard disk drive, upon which
  • Figure 4b is a representation of a hard disk drive, upon which
  • Figure 5 is a flowchart of the operation of backup management software, in accordance with one embodiment of the present invention.
  • Figure 6 is a flowchart of a backup process, in accordance with one embodiment of the present invention.
  • traversing refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
  • FIG. 1 a block diagram of an exemplary computer system 112 is shown. It is appreciated that computer system 112 described herein illustrates an exemplary configuration of an operational platform upon which
  • computer system 1 12 can include elements other than those described in conjunction with Figure 1.
  • system 112 is connected to a network attached storage device (NAT).
  • NAT network attached storage device
  • Computer system 112 includes an address/data bus 100 for
  • a central processor 101 coupled with bus 100 for processing information and instructions; a volatile memory unit 102 (e.g., random access memory [RAM], static RAM, dynamic RAM, etc.) coupled with bus 100 for storing information and instructions for central processor 101; and a non-volatile memory unit 103 (e.g., read only memory [ROM], programmable ROM, flash memory, etc.) coupled with bus 100 for storing static information and instructions for processor 101.
  • Computer system 112 may also contain an optional display device 105 coupled to bus 100 for displaying information to the computer user.
  • computer system 112 also includes a data storage device 104 (e.g., disk drive) for storing information and instructions.
  • Computer system 112 Also included in computer system 112 is an optional alphanumeric input device 106. Device 106 can communicate information and command selections to central processor 101. Computer system 112 also includes an optional cursor control or directing device 107 coupled to bus 100 for communicating user input information and command selections to central processor 101. Computer system 112 also includes signal communication interface (input/output device) 108, which is also coupled to bus 100, and can be a serial port. Communication interface 108 may also include wireless
  • computer system 112 can be communicatively coupled to other computer systems over a communication network such as the Internet or an intranet (e.g., a local area network).
  • a communication network such as the Internet or an intranet (e.g., a local area network).
  • embodiments of the present invention can be practiced on many different types of computer system 112. Examples include, but are not limited to, desktop computers, workstations, servers, media servers, laptops, gaming consoles, and personal digital assistants (PDAs), as well as other electronic devices with computing and data storage capabilities, such as wireless telephones, media center computer, digital video recorders, digital cameras, and digital audio playback or recording devices.
  • PDAs personal digital assistants
  • Network connection 202 can be any means of allowing data transfer between system 112 and server 212.
  • network connection 202 is a local area network (LAN).
  • system 112 and server 212 can be located near to each other, such as within the same office.
  • LAN local area network
  • network connection 202 is the Internet, and server 212 need not be located physically near to system 1 12.
  • network connection 202 is a wireless connection.
  • network connection 202 is a direct connection, e.g., a universal serial bus (USB) connection.
  • USB universal serial bus
  • system 112 is behind a firewall.
  • multiple systems 1 12 may connect to a single server 212.
  • a single system 112 can connect to multiple servers 212.
  • a single computer system can serve the role of both system 1 12 and server 212, e.g., by utilizing a separate hard drive for backing up data.
  • Computer system 112 is depicted in Figure 2 as executing system monitoring software 250.
  • system monitoring software 250 may perform three roles: to prepare data stored on computer system 112 for backup; to monitor computer system 112 for backup event triggers; and to backup the data stored on computer system 112 by sending it over network connection 202 to server 212. These three roles are described in further detail below, in conjunction with further exemplary embodiments of the present invention.
  • environmental monitor 251 is a detector, or series of detectors, that provide information to system 112 about the status of the environment around system 112.
  • environmental monitor 251 is a security system that monitors for unauthorized entry into the vicinity of system 112; e.g., a home break-in monitoring system.
  • environmental monitor 251 detects fire; e.g., a smoke alarm.
  • computer system 112 is coupled to optional uninterruptible power supply (UPS) 252.
  • UPS uninterruptible power supply
  • system 112 receives power from UPS 252 for a limited time, even after normal power is lost; e.g., the electrical line powering the office in which system 112 resides is cut.
  • UPS uninterruptible power supply
  • UPS 252 is an external unit. In another embodiment, UPS 252 is incorporated into system 112. In one embodiment, system 112 is configured to detect when normal power is lost and UPS 252 is providing power. [0032] In some embodiments, computer system 1 12 incorporates optional hardware monitor sensor 260 that may be used to detect events that potentially predict hardware failure. In several such embodiments, hardware monitor sensor 260 is positioned near data storage device 104. In one embodiment, hardware monitor sensor 260 includes a sound-sensitive component; e.g., a microphone. In another embodiment, hardware monitor sensor 260 includes a temperature-sensitive component; e.g., a thermocouple or thermal sensor. In one embodiment, hardware monitor sensor 260 is coupled to system 112, and the readings detected are available to system monitoring software 250, which may generate a backup event trigger based on the signals from sensor 260.
  • hardware monitor sensor 260 is coupled to system 112, and the readings detected are available to system monitoring software 250, which may generate a backup event trigger based on the signals from sensor 260.
  • Server 212 is depicted in Figure 2 as executing backup management software 290.
  • backup management software 290 has four roles: to monitor computer system 1 12; to trigger a backup of computer system 1 12 under certain circumstances; to retrievably store data transmitted from computer system 112; and to restore information to computer system 112 as needed. These roles are described in further detail below, in conjunction with further exemplary embodiments of the present invention.
  • backup management software 290 performs these roles remotely, e.g., by collecting and transferring information over network connection 202.
  • backup . management software 290 executes, in part, on system 112, and performs these roles locally. In other embodiments, a combination of these two approaches is utilized.
  • step 310 system monitoring software 250 performs data preservation preparations tasks.
  • step 320 system monitoring software 250 monitors the client system, system 112, for a backup event trigger. If a backup event trigger is detected, in step 330 system monitoring software 250 initiates the backup process.
  • some prc-backup operations can be performed on the data in step 310.
  • these data preservation preparation tasks are performed continually on system 112.
  • system monitoring software 250 acts to prepare this data for backup, in order to expedite the backup process when the next backup event trigger is detected.
  • data preservation preparations tasks occur at a specified time, or under specified conditions, such as when system 1 12 has entered an idle state. In other embodiments, the data preservation preparations tasks are performed only immediately prior to transmitting the data over network connection 202. In several embodiments, a combination of these approaches is utilized. For example, in one embodiment high- priority data is subject to data preservation preparation immediately after it is stored on system 112, while less important data is prepared only after the system has been idle for a specified length of time.
  • a number of operations fall within the scope of data preservation preparation.
  • one such operation is compression of data.
  • data is encrypted.
  • data is assigned a priority level.
  • data is sorted on the hard disk, and arranged to speed access times during backup.
  • data is duplicated in a separate area of the hard drive, or onto another hard drive, to speed access times during backup.
  • Other embodiments perform other data preservation preparation tasks or operations.
  • a major consideration that influences what tasks are performed, and when the tasks should be performed, is the desire to reduce the time needed between a backup event trigger and transmission of data from system 112 to server 212. If essential tasks, such as the transmission order for the data, the compression of the data, and the encryption of the data stream are handled before a backup event trigger is detected, much less delay is required between such a detection and the start of data transmission.
  • data compression is part of step 310.
  • Data compression speeds the backup process by reducing the number of bytes that must be transferred over network connection 202.
  • data compression reduces the amount of storage space used by system monitoring software 250 to stored the duplicated data.
  • data compression can require significant amounts of time and processor cycles.
  • the amount of time between the detection of a backup event trigger and transmission of data from system 112 to server 212 is greatly reduced, as the data is already compressed and ready to be transferred.
  • the type of data compression utilized is selected from the group of so-called "lossless" compression routines, which allow for data compression, and later decompression, without any loss of initial quality.
  • Many such compression routines are known in the art, e.g., run-length encoding.
  • "lossy" compression routines are used, to allow for greater data compression than is possible with loss-less compression.
  • Some embodiments utilize a combination of lossy and lossless compression routines.
  • One such embodiment allows the user to select which types of data should be preserved without loss, and which can be backed up with some degradation in initial quality.
  • crucial or • mission critical data e.g., data that cannot be modified, could be preserved using lossless compression techniques, while less important data is compressed using lossy techniques.
  • compression of data occurs when data is entered into the system.
  • One such embodiment is paired with data duplication, discussed below. This combination allows the user to have full access to his data stored on system 112, without having to decompress data every time it is accessed, while still allowing system monitoring software 250 to maintain a complete, compressed copy of the data ready for backup.
  • compression of data occurs at a preset time, or after a preset trigger occurs, e.g., at midnight every night, or after the system has been idle for 15 minutes.
  • only selected data is compressed when it enters system 112, while other data is left uncompressed to facilitate local access to it.
  • One such embodiment compresses text documents immediately, as they can be decompressed quickly if needed, while not compressing multimedia files, which would take much longer to become accessible if needed.
  • data is only compressed after a backup event trigger is detected. In another embodiment, whether compression is utilized or not is dependent upon the type of backup event trigger detected. In one embodiment, no data compression is performed.
  • data encryption is part of step 310.
  • Data encryption makes the backup process more secure for users, by making the data being transferred much more difficult for unauthorized parties to access.
  • server 212 and system 112 are owned and operated by different entities, including data encryption can ensure that data stored on server 212 remains secure, even though the owner of the data is not in control of server 212.
  • Many types of data encryption are known in the art, and can be practiced in conjunction with embodiments of the present invention. Several embodiments combine data compression and data encryption, such that system monitoring software 250 will both compress and encrypt the data at the same time. In some embodiments, data encryption occurs when the data enters system 112.
  • One such embodiment is paired with data duplication, discussed below; in this embodiment, the duplicate copy of the data is encrypted when it is created, or shortly thereafter.
  • data encryption occurs at a specified time, or after a specified event; e.g., new data is encrypted at midnight every day, or after system 112 has been idle for fifteen minutes.
  • only selected data is encrypted when it enters system 112, while other data is left unencrypted to facilitate user access.
  • data is encrypted after a backup event trigger is detected.
  • whether data is encrypted, and which type of encryption to use is dependent upon the type of backup event trigger detected. For example, if the backup event trigger detected is imminent hard drive failure, a user might prefer to backup crucial data unencrypted, instead of spending time encrypting data and perhaps losing all of it.
  • Other embodiments do not include data encryption as part of data preservation preparation.
  • data stored in system 112 is assigned a priority level as part of step 310. Not all data stored in system 112 is of equal value. Most users would prefer to preserve certain types of data, even at the expense of other files. By using system monitoring software 250 to assign different levels of importance to different data, the user can determine which files are given preference in the backup process.
  • a user assigns priority levels to files. In one embodiment, this assignment is conducted on a per-file basis, with the user selecting a priority level for each file. In another embodiment, the user determines a priority level for different types of files; in such an embodiment, a user could choose, for example, to give digital photographs priority over digital copies of movies. In another embodiment, the user specifies priority by location within system 112's file system; in this
  • the user could choose to have the directory where all of his email messages are stored to have a higher priority than the operating system's files.
  • the user can set rules for what priority is assigned to files, and system monitoring software 250 could establish priority levels based on those rules.
  • the user need not assign a priority to every file, but could, for example, configure system monitoring software 250 when it was installed to give priority to any file ending in .doc and .jpg over all other files.
  • a user may assign priority in different ways.
  • system monitoring software 250 assigns priority to data. In one such embodiment, priority is assigned based on frequency of access, with user-generated files that are accessed more often getting higher levels of priority. In another embodiment, system monitoring software 250 is configured to identify user- generated content, such as word processing documents and digital photographs, and assign such files higher priority than operating system files. In another embodiment, higher priority is automatically assigned to smaller files, which can be backed up faster. In other embodiments, other approaches to assigning levels of importance to different files, types of files, or locations within the file system are implemented.
  • both the user and system monitoring software 250 assign priority levels to data on system 112.
  • system monitoring software 250 assigns a default level of priority to a given file, based on preconfigured rules such as those described above, and the user can choose to assign a different level of priority.
  • multiple levels of priority are assigned to the same data.
  • a user can assign priority based on how he wants his data preserved in situations where different backup event triggers are detected. For example, a user might assign a high priority to digital movie files for routine backups, but assign much lower priority levels to the same files in the event of an emergency backup triggered by imminent hardware failure. In this way, the user has greater flexibility in protecting his data.
  • the rules under which a priority system operates can vary significantly.
  • a user may specify priority rules to take into account the relative change in a file, as well as how crucial the file is; e.g., a high-priority file that has changed only slightly since the last time it was backed up could be less important to the user than a lower-priority file that has never been backed up before, under the theory that slight revisions to an existing file would be easier to recreate, using the previous backup, than an entirely new file.
  • a user may assign one level of priority to a file in situations where a full backup is to be performed, and a different level of priority when an incremental backup will be performed.
  • Embodiments of the present invention allow for many different priority rules to apply to data, to account for many different circumstances.
  • system monitoring software 250 rearranges the data on data storage device 104 of system 1 12 as part of step 310.
  • every file to be stored on server 212 must be located on data storage device 104.
  • data storage device 104 is a mechanical storage system, e.g., a hard disk drive (HDD)
  • HDD hard disk drive
  • the files to be backed up will often be spread across multiple platters in different locations. Transitioning between each file therefore takes time.
  • One approach to reducing the time consumed by seeking for data is file relocation, wherein system monitoring software 250 rearranges data stored on data storage device 104 before a backup event trigger is detected. Embodiments incorporating this approach are explained with reference to Figures 4a and 4b.
  • HDD 104 is shown as having a rotating platter 401, a moving arm 403, and a read head 405. Multiple files to be backed up are depicted on platter 401 as files 411, 412, 413, 414, 415, 416, and 417. In order to backup these files, arm 403 must move read head 405 to each of them in turn, a process known as seeking.
  • Arm 403 must seek each file in turn, and will move at least seven times in order to reach each file. Seeking adds extra time to the backup process, and if the hard drive is failing, adds additional stress on the components that can result in the hard drive failing fully before all files are backed up.
  • system monitoring software 250 has implemented file relocation during step 310 to arrange the files to be backed up on HDD 104, such that files 411, 412, 413, 414, 415, 416, and 417 are located near to each other on platter 401. If a backup event trigger is detected, and these files need to be backed up, arm 403 does not have to move as often or as far in order to reach all of the files to be backed up. This results both in a savings of time and a reduction of stress on the components of HDD 104.
  • the relocation of files takes into account the relative priority of data. For example, with reference to Figure 4b, if files 411, 412, and 417 are all marked as being high priority files, while files 413 and 415 are medium priority, and files 414 and 416 are low priority, an embodiment utilizing both priority and file relocation would order the files to place higher priority data before lower priority data, e.g., files 411, 412, 417, 413, 425, 414, 416.
  • Some embodiments incorporate a data duplication scheme as part of step 310, in order to expedite the backup process.
  • data compression and encryption techniques are incorporated into embodiments of the present invention in order to provide a faster and more secure backup process.
  • both compression and encryption of files will slow the speed at which system 1 12 may access that data.
  • the files to be backed up are duplicated, either in another location on data storage device 104 or on another data storage device available to system 1 12. As such, the files the user wants to access remain readily available, without compromising the advantages gained by the data preservation preparation process of step 310.
  • data is duplicated as soon as it enters system 1 12, or is modified.
  • data is duplicated at a specified time or after a specified trigger has occurred, such as at midnight every day or after system 112 has been idle for fifteen minutes.
  • certain specified types of data are duplicated immediately, while other types are duplicated at a specified time or after a specified trigger has occurred.
  • data duplication is paired with file relocation, to better order the duplicate files to be backed up on a hard disk drive.
  • data duplication and subsequent storage takes into account the relative priority of data. For example, with reference to Figure 4b, if files 411, 412, and 417 are all marked as being high priority files, while files 413 and 415 are medium priority, and files 414 and 416 are low priority, an embodiment utilizing both priority and data duplication would order the copied files to place higher priority data before lower priority data, e.g., copied files 411, 412, 417, 413, 425, 414, 416.
  • system monitoring software 250 performs step 320, monitoring client system 112 for backup event triggers.
  • backup event triggers are defined in system monitoring software 250 as conditions that, if met, trigger the backup process, defined below.
  • the conditions that can constitute a backup event trigger vary in different embodiments.
  • One consideration in enumerating the set of backup event triggers for a particular embodiment is under what conditions a user will find it valuable to have the data stored on system 112 automatically backed up.
  • An exemplary list of backup event triggers appears below in Table 1. It is understood that this list is non-exhaustive; other embodiments incorporate other backup event triggers.
  • system monitoring software 250 is configured to implement a time-scheduled backup scheme.
  • a time-scheduled backup scheme causes system monitoring software 250 to produce a backup event trigger at a preset time. In some embodiments, this time is user-configured; e.g., a user could set system monitoring software 250 to trigger at midnight every Monday night.
  • system monitoring software 250 selects a time to trigger a backup. In one such embodiment, system monitoring software 250 is configured to select a time when a user is unlikely to be using system 112, based on detected past usage.
  • a time-scheduled backup trigger occurs after a predetermined length of time since the last successful backup; e.g., system monitoring software 250 will schedule a backup to occur 72 hours after the last successful backup operation.
  • a time-scheduled backup scheme One consideration in implementing a time-scheduled backup scheme is that the data on system 112 be routinely and regularly protected.
  • system monitoring software 250 is configured to implement a system idle backup scheme.
  • system monitoring software 250 will produce a system idle backup trigger after a predetermined length of time has passed since the last activity in system 1 12.
  • One such embodiment determines if system 112 is idle from HDD activity.
  • Another embodiment determines system activity based on the presence of input from a keyboard, mouse, or other input device.
  • One consideration in implementing a system idle backup scheme is that the backup activity of system monitoring software 250 not interfere with a user's access to system 112, while still providing regular protection for the data on system 112. In this case, backup processes may be inhibited during periods of detected user activity.
  • system monitoring software 250 is configured to implement a system idle backup scheme and an incremental backup scheme, as described below.
  • system monitoring software 250 when system 112 enters an idle state, system monitoring software 250 produces a system idle backup trigger, and a backup process is initiated. When system 112 is no longer idle, e.g., a user accesses system 112, this backup process is suspended. When a second backup process is initiated, data already transmitted during the first, interrupted, backup process is not transmitted again.
  • system monitoring software 250 is configured to implement a user-initiated backup scheme.
  • system monitoring software 250 allows a user to produce a user-initiated backup trigger, thereby starting the backup process.
  • One consideration in implementing a user-initiated backup scheme is that the user will often know better than system monitoring software 250 when truly crucial data has been entered into system 112, and can therefore act to protect the data by starting a backup process.
  • a further consideration is that the user will know better than system monitoring software 250 if system 112 is to be powered down or disconnected from network connection 202, and can start a backup process before this occurs.
  • system monitoring software 250 is configured to implement a new data preservation backup scheme.
  • system monitoring software 250 produces a new data preservation backup trigger after a predetermined amount of new data has been stored on system 112 since the last successful backup process.
  • One embodiment of this type determines how much new data has been entered into system 112 during step 310 3 data preservation preparation.
  • the amount of new data is measured in terms of bytes.
  • the amount of new data is measured in terms of numbers of discrete files.
  • the amount of new data is measured with reference to the type of files that have been stored; e.g., a text document requires far fewer bytes than a digital movie file, but can be accorded equal importance.
  • system monitoring software 250 configures system monitoring software 250 to set a threshold level for a new data preservation backup trigger.
  • system monitoring software 250 determines an appropriate threshold.
  • One such embodiment determines a threshold value by tracking the normal generation of new data for a set time period; e.g., if system monitoring software 250 notes 150 new files being generated in system 112 every day, a reasonable threshold may be 300 new files, approximately two days productivity.
  • the new data preservation backup scheme is implemented in conjunction with a priority system.
  • higher priority data is treated as more important than equal amounts of lower priority data.
  • system monitoring software 250 might produce a backup trigger after 10 megabytes of low-priority data have accumulated since the last successful backup of system 112, but might produce a backup trigger after only one megabyte of high-priority data has accumulated. Power Failure Backup
  • system monitoring software 250 is configured to implement a power failure backup scheme.
  • system 112 is configured to detect an imminent power failure.
  • system 112 is connected to uninterruptible power supply (UPS) 252, and UPS 252 and system 1 12 are configured such that system 112 can determine when normal power is lost, and generate a power failure backup trigger.
  • UPS 252 and system 1 12 are configured such that system 112 can determine when normal power is lost, and generate a power failure backup trigger.
  • system 112 is powered by an expendable energy source, and configured to detect when that energy source is running out; e.g., a laptop computer running on battery power.
  • UPS uninterruptible power supply
  • system 112 is powered by an expendable energy source, and configured to detect when that energy source is running out; e.g., a laptop computer running on battery power.
  • One consideration is that data be protected in the event of a loss of power to system 112, through detection of imminent power failure.
  • system monitoring software 250 is configured to implement a hard disk failure backup scheme. In such embodiments, system monitoring software 250 is configured to produce hard disk failure backup triggers. In some embodiments, system monitoring software 250 tracks factors that affect HDD
  • system monitoring software 250 increases the frequency of backup triggers, so as to reduce the risk of loss of data from hard disk failure.
  • One factor affecting the expected life of the HDD is the age of the HDD- Systern monitoring software 250, in one embodiment, determines the approximate age of the HDD. Exemplary methods of determining the age of a HDD include checking the system registry in the operating system of system 112 to determine when the HDD was installed in system 112, or referencing the HDD's model number or serial number against a list of known manufacturing periods.
  • system monitoring software 250 considers the number of read/write cycles the hard drive has performed, which effects the life expectancy of a hard drive. In another embodiment, system monitoring software 250 considers the number of on/off cycles the hard drive has undergone, which effects the life expectancy of a hard drive. Further embodiments combine some or all of these approaches, in considering how frequently to generate backup triggers.
  • system 112 incorporates hardware monitor sensor 260, a system temperature monitor.
  • System monitoring software 250 is configured to record system temperatures, and compare average operating temperatures against compiled statistics of average system temperature and expected HDD life.
  • a related factor affecting HDD life is the temperature gradient to which the HDD is exposed. Even more than operating at extreme temperatures, exposure of a HDD to large, sudden changes in temperature can significantly reduce expected HDD life.
  • system 112 incorporates hardware monitor sensor 260, a system temperature monitor. System monitoring software 250 is configured to record system temperatures, determine temperature gradients, and compare against compiled statistics of temperature gradients and expected HDD life.
  • system monitoring software 250 and system 112 are configured to allow system monitoring software 250 to be aware of these factors, and adjust the frequency of backup triggers accordingly.
  • system monitoring software 250 and system 112 are configured to allow for detection of factors that may potentially predict imminent HDD failure.
  • a combination of hardware incorporated in system 112 and instructions incorporated in system monitoring software 250 allow for recognition of HDD failure symptoms.
  • One such symptom is a change in the sounds produced by operation of the HDD. For example, some HDDs become louder and can produce a clicking sound immediately before catastrophic HDD failure.
  • a microphone into system 112, positioned near to HDD 104, to measure the sounds produced during HDD operation, e.g., the pitch and amplitude of the sounds.
  • Other embodiments incorporate a sound detecting sensor into HDD 104 itself, to accomplish a similar purpose.
  • system monitoring software 250 can predict imminent HDD malfunction of failure, and produce a backup trigger.
  • system monitoring software 250 compares the current sounds against an acoustic profile generated from past performance of this same HDD 104.
  • system monitoring software 250 is configured to use a pre-established acoustic profile compiled by a manufacturer of a particular HDD.
  • Another symptom of imminent HDD failure is a sudden increase in operating temperature of the HDD.
  • Some embodiments incorporate a temperature sensor into system 12, positioned near to HDD 104, to measure the operating temperature.
  • Other embodiments incorporate a temperature sensor into HDD 104 itself, to accomplish a similar purpose. By detecting a sudden increase in operating temperature, system monitoring software 250 can potentially predict imminent HDD malfunction or failure, and produce a backup trigger.
  • system monitoring software 250 is configured to implement an environmental backup scheme. In such embodiments, system monitoring software 250 is configured to produce an environmental backup trigger if a prescribed environmental condition occurs.
  • system 112 is coupled to environmental monitor 251, which provides information about the environment system 1 12 resides in.
  • system 1 12 is an office workstation, and
  • environmental monitor 251 is a security system monitoring the office for break-ins. If a break-in occurs, environmental monitor 251 detects it, system 1 12 is informed, and system monitoring software 250 can produce a backup trigger to begin a backup process, which may allow data to be backed up before system 112 is stolen, vandalized, or otherwise disconnected from server 212.
  • environmental monitor 251 is a fire detection system, allowing system monitoring software 250 to initiate a backup process when a fire is detected, and preserving data in the event system 112 is damaged or destroyed.
  • other environmental monitors 251 are used to detect other conditions local to system 1 12 that should prompt a backup trigger. In some embodiments which implement both environmental backup triggers and weighted backup triggers, some or all environmental backup triggers are weighted so as to prompt an immediate backup process.
  • backup event triggers are given different weighting, or levels of importance. Such embodiments often implement a backup urgency scheme, discussed in greater detail below.
  • a backup event trigger such as a time-scheduled backup would receive less weight than would an imminent hardware failure.
  • Other embodiments allow for these weightings to change over time. In one such an embodiment, for example, a time-scheduled backup would receive progressively greater levels of importance, the longer it has been delayed.
  • system monitoring software 250 is configured to perform step 330, a backup process, after a backup event trigger has been detected. In other embodiments, system monitoring software 250 causes a separate backup process to execute. In some embodiments, backup process 330 involves transmitting data stored on system 112 over network connection 202 to server 212. 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 in sending data.
  • a backup urgency test is performed.
  • the need for an immediate backup is weighed against other concerns; if the need for a backup is greater, backup begins immediately, and if it is not, the backup process is delayed. Exemplary factors influencing each side of this balancing heuristic are described below; other embodiments of system monitoring software 250 incorporate other factors into the backup urgency test.
  • the need for a backup is affected by the type of backup event trigger detected. In one embodiment, if potential imminent hard drive malfunction or failure is detected, the need for a backup is given the highest level of urgency. In another embodiment, a time-scheduled backup is given a much lower level of urgency. One consideration in establishing levels of urgency for different backup event triggers is how likely the data on system 1 12 is to be lost, if a backup process is not initiated immediately.
  • the need for a backup is affected by the length of the time since the last successful backup.
  • each successive backup urgency test will give greater urgency to the need for a backup, until a backup is accomplished.
  • the need for a backup is affected by the priority of data that has accumulated on system 1 12 since the last successful backup.
  • greater need for backup is assigned by system monitoring software 250 when, for instance, 10 megabytes of high-priority data has accumulated than when 10 megabytes of low-priority data has accumulated.
  • the need for a backup is measured against the current level of activity in system 112.
  • consideration is given to how the user is accessing system 112, and system monitoring software 250 balances the need for a backup against the user's desire to access system 112.
  • One consideration is that a backup process often requires intensive access to system resources, such as HDD and network connection access; initiating a backup while a user is performing some task that involves extensive HDD or network access is inconvenient for the user, and not an efficient use of system 112.
  • One embodiment monitors HDD activity on system 1 12 to determine system 112's activity level. Another embodiment monitors network connection activity, to determine when network connection 202 is available to transmit data to server 212. Another embodiment monitors use of input devices, e.g., mouse and keyboard, to determine when system 112 is in an idle state. Another embodiment links system monitoring software 250 to a screensaver program executing on system 112, such that a backup process would not start unless the system were idle long enough for the screensaver program to execute. Other embodiments incorporate other methods for determining system or network activity levels.
  • system monitoring software 250 monitors system 112 activity, and avoids executing a backup process whenever system 112 is being used.
  • Some embodiments incorporate various methods to allow for checking the integrity of the data after it is received. Many methods known in. the art are appropriate for ensuring data accuracy, including, but not limited to, generating a checksum prior to transferring the data to server 212, transmitting the checksum information, and having server 212 verify the integrity of the data sent. Other embodiments incorporate other systems of checking data integrity.
  • a secure, encrypted connection before data is transferred over network connection 202, a secure, encrypted connection must be established between system 1 12 and server 212.
  • SSL secure socket layer
  • SSH secure shell
  • a secure connection is not required before transmitting data.
  • One such embodiment incorporates encryption of data during step 310, which would reduce the risk of data being accessed by unauthorized personnel.
  • Different embodiments of the present invention utilize different methods of data transferal. Any method of reliably transmitting data from system 112 to server 212 over network connection 202 is acceptable in practicing embodiments of the present invention.
  • One embodiment utilizes the Internet as a transfer medium, and formats the data in accordance with the Internet protocol (IP).
  • IP Internet protocol
  • Other embodiments utilize different types of network connection 202, and encode the data in accordance with other data transfer protocols.
  • system monitoring software 250 implements incremental storage of data. In such an embodiment, system monitoring software 250 only transfers data that was added since the last time system 1 12 was backed up.
  • Identification of new data is accomplished as part of step 310.
  • new data is identified immediately before transmittal, as part of step 330.
  • One consideration in deciding whether to implement incremental backup is whether the speed at which a full backup is completed is more important than maintaining complete, separate backed up records of the data on system 112.
  • Other embodiments omit incremental storage, instead transmitting all data to be backed up every time a backup process is executed.
  • a full backup of this sort is useful for systems with rapidly changing data, for archival purposes, and for systems that may be subject to attack by malicious programs or viruses.
  • Some embodiments incorporate a combination of these two approaches. In one such embodiment, for example, a full backup is performed once every month, with incremental backups performed weekly.
  • a backup process executes until it is complete. In such embodiments, once data transfer has begun, it continues until all data from system 112 is transmitted to server 212. In other embodiments, the backup process is suspended whenever the user accesses system 112 for another purpose. In such an embodiment, the user's use of system 112 is not significantly impaired by the execution of the backup process. In other embodiments, whether the backup process can be suspended is subject to the same criteria as the backup urgency test, described above. In one such
  • the backup process for example, if enough high-priority data had accumulated to force a backup to occur at an inconvenient time, the backup process will not be suspended until enough high-priority data is transferred to alter the outcome of the urgency test.
  • the backup process may continue while a user accesses system 112, but at a reduced rate.
  • the transfer of data over network connection 202 may be limited to a fixed percentage of available network bandwidth, processor bandwidth, and/or drive bandwidth, while the user is accessing system 112, to allow the user some use of system 1 12 while not fully suspending the backup process.
  • backup management software 290 remotely monitors the operation of client system 112.
  • backup management software 290 remotely triggers a backup process on client system 112.
  • backup management software 290 retrieveably stores the data received from client system 112.
  • backup management software 290 acts to restore the stored data to the client.
  • backup management software 290 is configured to perform remote monitoring of system 112.
  • remote monitoring allows server 212 to act as a failsafe for system monitoring software 250 by providing some duplication of essential tasks remotely.
  • backup management software 290 also monitors system 1 12 for problems that would be more difficult to detect client-side.
  • backup management software 290 duplicates the monitoring for backup event triggers that occurs in system monitoring software 250, described above.
  • the monitoring information available to system monitoring software 250 is transmitted over network connection 202 to backup management software 290, and the same evaluation of present conditions occurs on system 1 12 and server 212.
  • backup management software 290 monitors system 112 for select backup event triggers.
  • system monitoring software 250 incorporates hard drive failure detection
  • samples of present hard drive sounds are transferred to server 212, and backup management software 290 monitors the sounds for evidence of impending failure.
  • backup management software 290 monitors the sounds for evidence of impending failure.
  • One consideration in determining which monitoring tasks to duplicate in backup management software 290 is whether backup management software 290 could perform the monitoring role better than system monitoring software 250 will.
  • an off-site server 212 maintained by a company providing backup services to multiple clients, is more likely to include up-to-date versions of backup management software 290, including acoustic profiles of all available HDDs.
  • backup management software 290 do not duplicate any of the monitoring tasks of system monitoring software 250.
  • backup management software 290 monitors system 112 and system monitoring software 250 for other problems or issues that should result in a backup process.
  • backup management software 290 monitors system 112 for corruption or software degradation. Such irregular system performance can be caused by viruses, malicious programs, or file system corruption. For example, if backup management software 290 contacts system monitoring software 250 with a request for a status update and receives a nonsensical or unexpected response, system 112 may have problems that threaten the data stored thereon, and should be backed up immediately.
  • backup management software 290 is configured to determine how much time has elapsed since the last successful backup process.
  • One embodiment allows backup management software 290 to be configured to initiate a backup process after a predetermined length of time has elapsed.
  • Another embodiment allows backup management software 290 to be configured to attempt to contact an individual responsible for system 112, e.g., via an electronic mail message, and notify them that system 112 has not been backed up recently.
  • backup management software 290 is configured to initiate a remote backup if system 112 is known to be in a threatened location.
  • server 212 is connected to multiple systems 1 12 in a single city; if that city is known to be at risk from a major fire, an earthquake, a tornado, a hurricane, or other similar disaster, backup management software 290 can initiate a remote backup process on all systems 112 in the threatened location.
  • backup management software 290 is configured to initiate a remote backup when a substantial virus or system security threat is detected.
  • backup management software 290 is notified of a new virus spreading through the Internet, e.g., a self-replicating email worm, and initiates a remote backup of all systems 112 monitored by backup management software 290, in order to minimize damage caused if one or more systems 112 becomes infected.
  • backup management software 290 is configured to initiate a remote backup process.
  • Backup management software 290 in these embodiments, initiates a remote backup process in response to a backup event trigger, such as those detailed above, or in response to one of the other monitoring tasks, described above.
  • backup management software 290 can signal system monitoring software 250 to initiate a backup process.
  • a remote backup trigger is subject to the urgency balance test detailed above.
  • a remote backup trigger is acted on immediately.
  • backup management software 290 is responsible for retrievably storing the data received from system 1 12. In other embodiments, backup management software 290 calls other programs which retrievably store data. In many embodiments, extra safeguards are in place to ensure the safety of the data stored on server 212. In several embodiments, for example, a redundant array of independent disks (RAID) configuration is utilized, to better ensure data preservation on server 212. Other embodiments use other methods of data storage known in the art for securely storing data.
  • RAID redundant array of independent disks
  • backup management software 290 encrypts the data to be stored. As discussed previously, many types of encryption are available for use with embodiments of the present invention.
  • backup management software 290 allows outside access to the data stored on server 212.
  • One such embodiment allows a user to access his data stored on server 212 over the Internet.
  • a user has the ability to access and display his data without needing to expose system 112 to outside access, which allows for better security on system 112.
  • backup management software 290 overwrites old data from system 1 12 whenever a backup process is implemented. In such an embodiment, the amount of storage space required to store data from system 112 can be more readily controlled. In other embodiments, backup management software 290 stores data received from system 1 12 in a new location each time a backup process is implemented. While consuming much greater space, these embodiments allow for better archival of data, as well as better restoration of data, should system 112 be infected by malicious programs or viruses. In such a case, the most recent backup of system 1 12 may be infected as well, while an earlier version of the data from system 112 may be clean. Some embodiments mix these two approaches, allowing for several backup sessions from system 112 to coexist on server 212 at one time. This allows for a balance between storage requirements and archival or restoration uses. Restore Data
  • backup management software 290 allows for the restoration of data to system 1 12.
  • backup management software 290 transfers the data stored on server 212 over network connection 202, back to system 112.
  • the owner or operator of server 212 may charge a fee for the restoration of data. Transferring data and restoring it to system 112 is accomplished in many different ways in different embodiments. Any approach known for transferring and restoring data across a network connection will suffice to practice embodiments of the present invention.
  • FIG. 6 a computer controlled flowchart depicting a backup process is shown, in accordance with one embodiment of the present invention. With reference to Figures 2 and 6, embodiments configured to provide data backup services in emergency situations will be detailed.
  • system monitoring software 250 monitors system 1 12 for new or altered data. Upon initial execution of system monitoring software 250, all data in system 1 12 would register as new. After the first successful backup process, only data that was subsequently added to system 112, or data that was changed since the last successful backup process, would be identified as new. In some embodiments, system monitoring software 250 can be configured to ignore certain files, types of files, or locations within the file structure of system 1 12. In these embodiments, the user can elect not to backup certain less important files, e.g., operating system files, temporary storage files, or easily reinstalled programs, in favor of preserving more important data.
  • system monitoring software 250 can be configured to ignore certain files, types of files, or locations within the file structure of system 1 12. In these embodiments, the user can elect not to backup certain less important files, e.g., operating system files, temporary storage files, or easily reinstalled programs, in favor of preserving more important data.
  • only new data of a certain type, or in a defined location within the file structure of system 1 12, will be registered as new.
  • the degree of change in an existing file is also identified, which can allow a user to specify differing levels of importance for slightly altered files, heavily altered files, and completely new data. These embodiments allow the user further control over what data is preserved, by excluding data by default and allowing the user to select which types of files, or which directories, to backup.
  • system monitoring software 250 prepares the new data for preservation.
  • the data be identified to system monitoring software 250 in such a way that, in the case of an emergency backup event trigger, no searching is required to locate the data before transmission.
  • system monitoring software 250 creating or updating a list that identifies the location of all new data in system 1 12, e.g., a database that stores the addresses of all new data files.
  • a file relocation scheme such as that detailed above with reference to Figure 2
  • a data duplication scheme such as that detailed above with reference to Figure 2 is utilized.
  • system monitoring software 250 has identified the location of all new data in system 112 before an emergency situation occurs, and no time is lost by needing to search for the new data.
  • step 610 also encompasses data
  • a consideration in these embodiments is speed of transmission, as less time is required to transmit compressed data over network connection 202 to server 212. In an emergency situation, faster transmission of data can mean that more data is backed up before transmission is terminated.
  • step 610 also encompasses data encryption.
  • a consideration in these embodiments is whether security, both during
  • step 610 also encompasses data priority flagging.
  • the relative importance of data can be established. In an emergency situation, higher priority data can be transmitted before lower priority data, better ensuring the preservation of high priority data even if the transmission is terminated before the backup process is completed.
  • system monitoring software 250 monitors system 112 for emergency situations.
  • system monitoring software 250 monitors the environment of system 112 for emergency situations.
  • Other embodiments combine these features, while others also configure system monitoring software 250 for monitoring system 112 for other backup event triggers as well.
  • One consideration in selecting what events to monitor for is whether a particular situation has the potential to interrupt the backup process. A number of such situations are detailed above, including power interruption, hard drive failure, and environmental situations, such as fire or security system alerts.
  • backup management software 290 monitors system 112 for emergency situations.
  • backup management software 290 monitors the environment of system 1 12 for emergency situations.
  • Other embodiments combine these features, while other also configure backup management software 290 to monitor system 112 for other backup event triggers as well.
  • one consideration in selecting events to monitor for is how likely a particular event is to prevent a successful backup process. A number of such situations are described above, including those detailed for step 620, as well as monitoring for other environmental factors, such as a fire or natural disaster occurring near system 112.
  • step 630 an emergency backup event trigger is detected.
  • system monitoring software 250 starts a backup process.
  • backup management software 290 initiates a backup process, by sending a command or series of commands to system 112 over network connection 202.
  • network connection 202 must be established before data
  • network connection 202 is already established. Data begins transmitting from system 1 12 to server 212 over network connection 202. In embodiments, where a priority data system has been implemented, higher priority data is transmitted before lower priority data. In other embodiments, smaller files are transmitted before larger files.
  • One consideration that applies to all embodiments is that data transmission begin as soon as possible, so as to allow the largest amount of data possible to be transmitted to server 212 before transmission is terminated.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Software Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Hardware Redundancy (AREA)
  • Debugging And Monitoring (AREA)

Abstract

La présente invention se rapporte à des procédés et à des systèmes permettant de lancer un processus de sauvegarde de données dans un système informatique. Un procédé selon l'invention consiste : à identifier les données devant être sauvegardées ; à contrôler le système informatique pour détecter un événement de déclenchement de sauvegarde ; et à lancer un processus de sauvegarde de données si un tel événement de déclenchement est détecté.
PCT/US2006/046730 2005-12-08 2006-12-06 Services de conservation de donnees de secours Ceased WO2007067699A2 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN2006800459961A CN101326498B (zh) 2005-12-08 2006-12-06 紧急数据保存服务
JP2008544511A JP4904365B2 (ja) 2005-12-08 2006-12-06 緊急データ保存サービス

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US11/298,173 US8402322B2 (en) 2005-12-08 2005-12-08 Emergency data preservation services
US11/297,985 US9122643B2 (en) 2005-12-08 2005-12-08 Event trigger based data backup services
US11/298,173 2005-12-08
US11/297,985 2005-12-08

Publications (2)

Publication Number Publication Date
WO2007067699A2 true WO2007067699A2 (fr) 2007-06-14
WO2007067699A3 WO2007067699A3 (fr) 2008-06-05

Family

ID=38123496

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2006/046730 Ceased WO2007067699A2 (fr) 2005-12-08 2006-12-06 Services de conservation de donnees de secours

Country Status (4)

Country Link
JP (1) JP4904365B2 (fr)
KR (1) KR100990004B1 (fr)
TW (1) TWI432956B (fr)
WO (1) WO2007067699A2 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2690556A3 (fr) * 2012-06-15 2014-05-07 LG Electronics, Inc. Terminal mobile et procédé de contrôle du terminal mobile
WO2018137540A1 (fr) * 2017-01-24 2018-08-02 中兴通讯股份有限公司 Procédé et dispositif de sauvegarde de données
WO2025087516A1 (fr) * 2023-10-25 2025-05-01 Huawei Technologies Co., Ltd. Procédé de génération d'un accord de niveau de service de sauvegarde sur la base d'une analyse de contenu profond

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI493375B (zh) * 2009-07-01 2015-07-21 Fineart Technology Co Ltd 應用於電腦及電腦系統架構之資訊安全管理方法
JP2011237950A (ja) * 2010-05-07 2011-11-24 Fujitsu Ltd 情報処理装置、バックアップサーバ、バックアッププログラム、バックアップ方法及びバックアップシステム
JP5816424B2 (ja) * 2010-10-05 2015-11-18 富士通株式会社 情報処理装置、テープ装置、およびプログラム
KR102671482B1 (ko) * 2016-12-22 2024-06-03 주식회사 케이티 오브젝트에 대한 동기화 관리 장치 및 방법
JP6891603B2 (ja) * 2017-03-31 2021-06-18 日本電気株式会社 バックアップシステム、ストレージ装置、データ転送方法及びプログラム

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5560023A (en) * 1994-09-07 1996-09-24 International Business Machines Corporation Automatic backup system for advanced power management
JPH08106419A (ja) * 1994-10-06 1996-04-23 Hitachi Ltd バックアップ装置
JP4034405B2 (ja) * 1998-02-25 2008-01-16 東芝テック株式会社 情報処理装置
JP2001092688A (ja) * 1999-09-24 2001-04-06 Toshiba Corp 故障管理装置
US6574754B1 (en) * 2000-02-14 2003-06-03 International Business Machines Corporation Self-monitoring storage device using neural networks
JP4041656B2 (ja) * 2001-03-02 2008-01-30 株式会社日立製作所 ストレージシステム及びストレージシステムにおけるデータ送受信方法
JP4057818B2 (ja) * 2002-02-15 2008-03-05 株式会社ブロードリーフ データバックアップ方法
JP2003345627A (ja) * 2002-05-27 2003-12-05 Sony Corp 障害発生予防装置および方法、並びにプログラム
US7328366B2 (en) * 2003-06-06 2008-02-05 Cascade Basic Research Corp. Method and system for reciprocal data backup
US7109861B2 (en) * 2003-11-26 2006-09-19 International Business Machines Corporation System and method for alarm generation based on the detection of the presence of a person
US7340646B2 (en) 2004-05-03 2008-03-04 International Business Machines Corporation Apparatus, system, and method for resource group backup
JP2005346218A (ja) * 2004-06-01 2005-12-15 Dainippon Printing Co Ltd データバックアップ装置
US7512825B2 (en) 2004-09-27 2009-03-31 Hewlett-Packard Development Company, L.P. Responding to DC power degradation

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2690556A3 (fr) * 2012-06-15 2014-05-07 LG Electronics, Inc. Terminal mobile et procédé de contrôle du terminal mobile
WO2018137540A1 (fr) * 2017-01-24 2018-08-02 中兴通讯股份有限公司 Procédé et dispositif de sauvegarde de données
WO2025087516A1 (fr) * 2023-10-25 2025-05-01 Huawei Technologies Co., Ltd. Procédé de génération d'un accord de niveau de service de sauvegarde sur la base d'une analyse de contenu profond

Also Published As

Publication number Publication date
WO2007067699A3 (fr) 2008-06-05
KR100990004B1 (ko) 2010-10-26
JP2009524122A (ja) 2009-06-25
TWI432956B (zh) 2014-04-01
KR20080072904A (ko) 2008-08-07
JP4904365B2 (ja) 2012-03-28
TW200745840A (en) 2007-12-16

Similar Documents

Publication Publication Date Title
US9122643B2 (en) Event trigger based data backup services
US8402322B2 (en) Emergency data preservation services
US9654417B2 (en) Methods and systems for managing bandwidth usage among a plurality of client devices
US6611850B1 (en) Method and control apparatus for file backup and restoration
US6950836B2 (en) Method, system, and program for a transparent file restore
JP6521462B2 (ja) バックアップシステムの性能の改善
US8938643B1 (en) Cloning using streaming restore
US10127119B1 (en) Systems and methods for modifying track logs during restore processes
US20060095470A1 (en) Managing a file in a network environment
US8352430B1 (en) File storage system to support high data rates
AU2015362561B2 (en) Techniques for data backup and restoration
US20080189785A1 (en) Method and system for storage-based instrusion detection and recovery
US11113152B1 (en) Systems and methods for managing file backup
US12124595B2 (en) Detecting unauthorized encryptions in data storage systems
US12332839B2 (en) Immutable object locking for snapshot management
US8655841B1 (en) Selection of one of several available incremental modification detection techniques for use in incremental backups
US10466924B1 (en) Systems and methods for generating memory images of computing devices
KR100990004B1 (ko) 긴급 데이터 보존 서비스
US9465710B1 (en) Systems and methods for predictively preparing restore packages
CN104869361B (zh) 一种视频监控系统中的视频监控终端设备
US9064132B1 (en) Method for writing hardware encrypted backups on a per set basis
Beech The evolving role of disk and tape in the data center
EP1932073B1 (fr) Appareil et procede pour le stockage de donnees

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200680045996.1

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 2008544511

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 1020087013835

Country of ref document: KR

NENP Non-entry into the national phase

Ref country code: DE

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
122 Ep: pct application non-entry in european phase

Ref document number: 06847517

Country of ref document: EP

Kind code of ref document: A2

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)