US20060271819A1 - Recovering a system that has experienced a fault - Google Patents
Recovering a system that has experienced a fault Download PDFInfo
- Publication number
- US20060271819A1 US20060271819A1 US11/497,698 US49769806A US2006271819A1 US 20060271819 A1 US20060271819 A1 US 20060271819A1 US 49769806 A US49769806 A US 49769806A US 2006271819 A1 US2006271819 A1 US 2006271819A1
- Authority
- US
- United States
- Prior art keywords
- network
- software
- fault
- backup
- disk drive
- 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.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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 operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1417—Boot up procedures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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 operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1456—Hardware arrangements for backup
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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 operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1469—Backup restoration techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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 operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1464—Management of the backup or restore process for networked environments
Definitions
- the invention relates to recovery of systems that have experienced faults.
- Improvements in technology have provided users with a wide variety of devices to perform various tasks. Examples of such devices include desktop computer systems, portable computer systems, personal digital assistants (PDAs), mobile telephones, and so forth.
- the devices are relatively sophisticated devices that include processing elements (e.g., microprocessors or microcontrollers) and storage devices (e.g., hard disk drives, dynamic random access memorys or DRAMs, and so forth).
- processing elements e.g., microprocessors or microcontrollers
- storage devices e.g., hard disk drives, dynamic random access memorys or DRAMs, and so forth.
- a typical device includes an operating system (e.g., a WINDOWS® operating system, a UNIX operating system, a LINUX operating system, etc.) that is loaded when the device is started.
- Application software is also loaded into the device to provide useful functions for users.
- Example applications include word processing applications, electronic mail applications, web browsing applications, calendar and address book applications, and so forth.
- a component of a device such as a hard disk drive
- fails the user may be left with an inoperational device.
- One option for the user is to take the device to a repair shop where an attempt may be made to recover the failed component, such as the failed hard disk drive.
- data on the hard disk drives may be recovered so that loss of data is minimized.
- the data stored on the hard disk drive is lost, unless the user has diligently backed up the data.
- a system comprises an interface to a network and a first operational element to perform one or more tasks in the system.
- a storage element contains a flag to indicate if a fault has occurred with the first operational element.
- a backup device enables access to the network through the interface in response to the flag indicating failure of the first operational element.
- a system comprises a main storage device, a backup storage device, and a routine executable to boot from the backup storage device in case of a system fault.
- the backup storage device enables access over a network to retrieve data from a network node to recover the system.
- FIG. 1 is an embodiment of a network system including a network, various nodes coupled to the network, and a backup storage system.
- FIG. 2 is a block diagram of components of a node of FIG. 1 , in accordance with an embodiment.
- FIG. 3 is a flow diagram of tasks performed for a failure recovery in the node of FIG. 2 , in accordance with an embodiment.
- a network system 10 includes a network 12 that is coupled to network nodes 14 , 16 , and 18 .
- the nodes 14 , 16 , and 18 include desktop computer systems, portable computer systems, and other types of systems having access to the network 12 (over either wired or wireless connections).
- Examples of the network 12 include local area networks (LANs), wide area networks (WANs), the Internet, and so forth.
- a backup storage system 20 accessible over the network 12 stores data to be used to recover nodes 14 , 16 , and 18 in case of a fault (such as a component experiencing an error or failure) occurring in the nodes.
- the data stored in the backup storage system 20 includes user data, such as user-created documents or files, electronic mail messages, calendar and address book files, and so forth.
- the data stored in the backup storage system also includes software, such as operating system and application software that are stored and executed in each of the nodes.
- the user data and software are stored as image data 30 , 32 , and 34 that correspond to nodes 14 , 16 , and 18 , respectively.
- the image data 30 is retrieved from the backup storage system 20 and communicated to the node 14 , with the image data used to recover the node 14 .
- image data 32 and 34 are used to recover nodes 16 and 18 , respectively.
- the node 18 includes a main hard disk drive 24 , a backup storage device 22 , and a backup routine 26 executable in the node 18 .
- the backup routine 26 is initially stored on the backup storage device 22 and is executable to enable the node 18 to access the backup storage system 20 over the network 12 in case one of several predetermined faults occurs in the node 18 . Examples of such predetermined faults include failure of the hard disk drive, an unrecoverable error occurring on the hard disk drive, corrupted software and files associated with the software (e.g., library files, etc.), and so forth.
- the node 18 includes a central processing unit (CPU) 100 that forms the processing core of the node 18 .
- CPU central processing unit
- a host bridge 102 is connected over a host bus to the CPU 100 .
- the host bridge 102 is also connected to a system bus 104 , such as a Peripheral Component Interconnect (PCI) bus.
- PCI Peripheral Component Interconnect
- the host bridge 102 contains control elements to interface a main memory 103 and a video controller 116 that controls presentation of images on a display 114 .
- the system bus 104 is connected to a network interface 112 that manages communications to the network 12 through a port 110 .
Abstract
A method and system of recovering a system that has experienced a fault includes a backup device to enable access of a network through the interface in response to the fault. The system includes a main operational portion that controls operation of the system under normal conditions. However, if a fault occurs, then the backup device can be selected to take over control of the system so that data can be retrieved from a backup storage to recover the system. The backup device includes software and/or hardware components to enable the system to access a network even though the main operational portion may not be functioning properly.
Description
- This is a continuation of U.S. patent application Ser. No. 09/706,960, entitled “Recovering a System that has Experienced a Fault,” filed Nov. 6, 2000, now U.S. Pat. No. 7,089,449, which is hereby incorporated by reference.
- The invention relates to recovery of systems that have experienced faults.
- Improvements in technology have provided users with a wide variety of devices to perform various tasks. Examples of such devices include desktop computer systems, portable computer systems, personal digital assistants (PDAs), mobile telephones, and so forth. The devices are relatively sophisticated devices that include processing elements (e.g., microprocessors or microcontrollers) and storage devices (e.g., hard disk drives, dynamic random access memorys or DRAMs, and so forth).
- A typical device includes an operating system (e.g., a WINDOWS® operating system, a UNIX operating system, a LINUX operating system, etc.) that is loaded when the device is started. Application software is also loaded into the device to provide useful functions for users. Example applications include word processing applications, electronic mail applications, web browsing applications, calendar and address book applications, and so forth.
- Despite improvements in technology, failures in various components of a device remains a persistent problem. When a component of a device, such as a hard disk drive, fails, the user may be left with an inoperational device. One option for the user is to take the device to a repair shop where an attempt may be made to recover the failed component, such as the failed hard disk drive. In some cases, data on the hard disk drives may be recovered so that loss of data is minimized. However, in many other cases, the data stored on the hard disk drive is lost, unless the user has diligently backed up the data.
- Conventionally, recovery of the failed component such as the hard disk drive is an arduous process that often is frustrating for the user. A need thus exists for an improved method and apparatus for recovering a device to an operational state after a failure has occurred.
- In general, according to one embodiment, a system comprises an interface to a network and a first operational element to perform one or more tasks in the system. A storage element contains a flag to indicate if a fault has occurred with the first operational element. A backup device enables access to the network through the interface in response to the flag indicating failure of the first operational element.
- In general, according to another embodiment, a system comprises a main storage device, a backup storage device, and a routine executable to boot from the backup storage device in case of a system fault. The backup storage device enables access over a network to retrieve data from a network node to recover the system.
- Other features and embodiments will become apparent from the following description, from the claims, and from the drawings.
-
FIG. 1 is an embodiment of a network system including a network, various nodes coupled to the network, and a backup storage system. -
FIG. 2 is a block diagram of components of a node ofFIG. 1 , in accordance with an embodiment. -
FIG. 3 is a flow diagram of tasks performed for a failure recovery in the node ofFIG. 2 , in accordance with an embodiment. - In the following description, numerous details are set forth to provide an understanding of the present invention. However, it will be understood by those skilled in the art that the present invention may be practiced without these details and that numerous variations or modifications from the described embodiments may be possible.
- Referring to
FIG. 1 , anetwork system 10 includes anetwork 12 that is coupled tonetwork nodes nodes network 12 include local area networks (LANs), wide area networks (WANs), the Internet, and so forth. - A
backup storage system 20 accessible over thenetwork 12 stores data to be used to recovernodes backup storage system 20 includes user data, such as user-created documents or files, electronic mail messages, calendar and address book files, and so forth. The data stored in the backup storage system also includes software, such as operating system and application software that are stored and executed in each of the nodes. In one embodiment, the user data and software are stored asimage data nodes node 14, theimage data 30 is retrieved from thebackup storage system 20 and communicated to thenode 14, with the image data used to recover thenode 14. Similarly,image data nodes - As illustrated, the
node 18 includes a mainhard disk drive 24, abackup storage device 22, and abackup routine 26 executable in thenode 18. Thebackup routine 26 is initially stored on thebackup storage device 22 and is executable to enable thenode 18 to access thebackup storage system 20 over thenetwork 12 in case one of several predetermined faults occurs in thenode 18. Examples of such predetermined faults include failure of the hard disk drive, an unrecoverable error occurring on the hard disk drive, corrupted software and files associated with the software (e.g., library files, etc.), and so forth. Thebackup routine 26 and thebackup storage device 22 may be collectively be referred to as the “backup device 25.” In the illustrated embodiment, thebackup routine 26 is a software routine loaded from thebackup storage device 22 for execution on a processing element in thenode 18. Alternatively, the backup device is a hardware component that performs backup tasks in response to detection of certain types of faults. - More generally, the
node 18 includes a main operational portion, which in one embodiment contains the main hard disk drive 24 (or some other type of storage element). The main operational portion controls operation when thenode 18 functions normally. The mainhard disk drive 24 stores the operating system and application software, which are loaded into thenode 18 to perform useful tasks. In case of some predetermined faults, thebackup device 25 is used to enable access over thenetwork 12 to thebackup storage system 20 to retrieve data to recover the main operational portion of thenode 18. - The
backup storage device 22 can be implemented in a number of different ways. For example, thebackup storage device 22 can be a bootable mini-drive that is mounted inside the chassis of or on a motherboard in the node. The mini-drive can be a hard disk drive having a relatively small storage capacity for reduced cost. Alternatively, the mini-drive can be other types of non-volatile memory, such as flash memory, electrically erasable and programmable read-only memory (EEPROM) devices, and so forth. Instead of a separate component in the chassis of each node, the mini-drive can also be integrated onto the motherboard of the node if its size permits. Alternatively, thebackup storage device 22 can be a full form factor drive. - The
backup storage device 22 can also include a compact disk (CD) or digital video disk or digital versatile disk (DVD) drive in which a CD or DVD is loaded. The CD or DVD contains the necessary software to enable thenode 18 to access thenetwork 12. Alternatively, thebackup storage device 22 includes a partition on the mainhard disk drive 24. It is likely that only one part of thehard disk drive 24 is corrupted while another portion is not corrupted. Thebackup storage device 22 can also include other bootable cartridges or drives. - An example of the
backup routine 26 is a browser that is capable of executing on a processor in each node to gain access to thenetwork 12. To avoid having to load a large operating system such as the WINDOWS® operating system, the browser can be a reduced version browser that does not need standard full-scale computer operating systems to run. Examples of such “mini-browsers” include browsers that run in PDAs and other handheld devices. Alternatively, mini-browsers can be designed to operate in a DOS operating system, a WINDOWS® CE operating system, or other “lite” operating systems. - Referring to
FIG. 2 , an example of the node 18 (which has a similar arrangement asnodes 14 and 16) is illustrated. Thenode 18 includes a central processing unit (CPU) 100 that forms the processing core of thenode 18. Ahost bridge 102 is connected over a host bus to theCPU 100. Thehost bridge 102 is also connected to a system bus 104, such as a Peripheral Component Interconnect (PCI) bus. Additionally, thehost bridge 102 contains control elements to interface amain memory 103 and avideo controller 116 that controls presentation of images on adisplay 114. The system bus 104 is connected to anetwork interface 112 that manages communications to thenetwork 12 through aport 110. - Other components of the
node 18 include asouth bridge 123 coupled to the system bus 104. Thesouth bridge 123 is in turn coupled to adisk controller 124 that is connected to themain disk drive 24. Thedisk controller 124 can also manage communications with a CD and/orDVD drive 126. An input/output (I/O)controller 118, which is connected to afloppy disk drive 120 and to a mini-drive 122, is also coupled to thesouth bridge 123. - When the
node 18 first starts up, a basic input/output system (BIOS) routine 108 is loaded to perform boot and initialization tasks. TheBIOS routine 108 is stored in anon-volatile memory 106, which can be a flash memory, EEPROM, and other like memory devices. Access to thenon-volatile memory 106 is provided through thesouth bridge 123. - The
backup storage device 22 ofFIG. 1 can be one or more of the following elements in the node 18: the mini-drive 122, the CD orDVD drive 126, thefloppy drive 120, thebackup partition 130 in the mainhard disk drive 24, or an additional drive like themain drive 24. - Although not shown, the node also includes various layers and stacks to enable communications over the
network 12. For example, a network stack can include a TCP/IP (Transmission Control Protocol/Internet Protocol) or a UDP/IP (User Datagram Protocol/Internet Protocol) stack. TCP is described in RFC 793, entitled “Transmission Control Protocol,” dated September 1981; and UDP is described in RFC 768, entitled “User Datagram Protocol,” dated August 1980. One version of IP is described in Request for Comments (RFC) 791, entitled “Internet Protocol,” dated September 1981; and another version of IP is described in RFC 2460, entitled “Internet Protocol, Version 6 (IPv6) Specification,” dated December 1998. TCP and UDP are transport layers for managing connections over an IP network. - Also, various services enable the communication of requests over the
network 12, such as requests between a node and thebackup storage system 20. One such service is the Hypertext Transport Protocol (HTTP) service, which enables requests sent from one network element to another and responses from the destination network element to the requesting network element. - Referring to
FIG. 3 , the failure recovery process performed in one of thenodes operating system 134 determines (at 202) if the node has experienced a fault. If so, theoperating system 134 sets (at 204) a fail flag 132 (in the main hard disk drive 24) to an active state. Alternatively, the fail flag can be stored in thenon-volatile memory 106, the mini-drive 122, or another memory storage element in the node. - Next, either in response to a user request to restart or automatically upon detection of the fault, the node is rebooted (at 206). When the node starts up, the
BIOS routine 108 is loaded to perform boot tasks. One of the tasks performed by theBIOS routine 108 is to determine if thefail flag 132 has been set (at 208). If not, a normal boot process is performed (at 210) by theBIOS routine 108. If thefail flag 132 is set, then theBIOS routine 108 accesses (at 212) thebackup storage device 22. Alternatively, instead of automatically checking for thefail flag 132, the boot from thebackup storage device 22 can be performed manually by a user through the BIOS (such as by selecting the boot drive). Software on thestorage device 22, including thebackup routine 26, is loaded (at 214) into the node for execution on theCPU 100. As noted above, thebackup routine 26 can be a mini-browser that enables communications over thenetwork 12. - The backup routine 26 presents an indication of the fault (at 216), such as displaying a warning on the
display 114. The backup routine 26 then waits (at 218) for a user request to recover. If a request to recover the node is received, then the backup routine 26 accesses (at 220) theremote backup system 20 over thenetwork 12. Image data (30, 32, or 34) is retrieved from thebackup storage system 20 and downloaded (at 222) into the node, where the image data is used to recover the node. A scan disk operation may be performed to determine portions of the hard disk drive that are defective. The image data can then be copied to the remaining portions of thehard disk drive 24 to enable normal operation of the node. - The various software routines or modules described herein may be executable on various processing elements. Such processing elements include microprocessors, microcontrollers, processor cards (including one or more microprocessors or microcontrollers), or other control or computing devices. As used here, a “controller” can refer to either hardware or software or a combination of the two.
- The storage units include one or more machine-readable storage media for storing data and instructions. The storage media include different forms of memory including semiconductor memory devices such as dynamic or static random access memories (DRAMs or SRAMs), erasable and programmable read-only memories (EPROMs), electrically erasable and programmable read-only memories (EEPROMs), and flash memories; magnetic disks such as fixed, floppy and removable disks; other magnetic media including tape; or optical media such as CDs or DVDs. Instructions that make up the various software routines or modules when executed by a respective processing element cause the corresponding node to perform programmed acts.
- The instructions of the software routines or programs are loaded or transported into the node in one of many different ways. For example, code segments including instructions stored on floppy disks, CD or DVD media, a hard disk, or transported through a network interface card, modem, or other interface device are loaded into the system and executed as corresponding software routines or modules. In the loading or transport process, data signals that are embodied in carrier waves (transmitted over telephone lines, network lines, wireless links, cables, and the like) communicate the code segments, including instructions, to the node. Such carrier waves may be in the form of electrical, optical, acoustical, electromagnetic, or other types of signals.
- While the invention has been disclosed with respect to a limited number of embodiments, those skilled in the art will appreciate numerous modifications and variations therefrom. It is intended that the appended claims cover all such modifications and variations as fall within the true spirit and scope of the invention.
Claims (8)
1. A system comprising:
a processor;
an interface to a network;
a BIOS routine executable on the processor;
a storage element containing a flag to indicate if a fault has occurred in the system; and
a backup device to enable access of the network through the interface,
wherein the BIOS routine loads software from the backup device for execution on the processor in response to the flag indicating failure in the system,
wherein the software is executable to access a remote backup storage over the network.
2. The system of claim 1 , wherein the software is executable to retrieve image data from the backup storage, and wherein the image data is used to recover the system.
3. The system of claim 2 , wherein the flag indicates if a fault has occurred with a disk drive, and wherein the software is executable to scan the disk drive to identify a first portion of the disk drive that is defective, and a second portion of the disk drive that is not defective, the software to store the image data to the second portion of the disk drive.
4. The system of claim 1 , wherein the interface comprises a network stack having an Internet Protocol (IP) layer, wherein the backup device comprises a backup storage element containing the software adapted to perform communications through the network stack including the IP layer to the network.
5. The system of claim 4 , wherein the software comprises a browser.
6. A method of performing error recovery in a system, comprising:
detecting if an operating portion of the system has experienced a fault;
setting a flag to indicate that the operating portion of the system has experienced a fault;
during a boot process, a BIOS routine determining whether the flag is set;
in response to determining the flag is set, accessing a backup device in the system to load software for execution;
the software communicating through a network stack over a network to retrieve an image containing user data and an operating system.
7. The method of claim 6 , further comprising recovering the system using the image.
8. The method of claim 6 , wherein the software comprises a browser, and wherein the software communicating through the network stack over a network to retrieve the image is in response to a recover command received by the browser.
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/497,698 US20060271819A1 (en) | 2000-11-06 | 2006-08-02 | Recovering a system that has experienced a fault |
US13/294,077 US20120060048A1 (en) | 2000-11-06 | 2011-11-10 | Recovering a system that has experienced a fault |
US13/612,096 US20130067276A1 (en) | 2000-11-06 | 2012-09-12 | Software and methods for recovering a network node that has experienced a fault |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/706,960 US7089449B1 (en) | 2000-11-06 | 2000-11-06 | Recovering a system that has experienced a fault |
US11/497,698 US20060271819A1 (en) | 2000-11-06 | 2006-08-02 | Recovering a system that has experienced a fault |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/706,960 Continuation US7089449B1 (en) | 2000-11-06 | 2000-11-06 | Recovering a system that has experienced a fault |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/294,077 Continuation US20120060048A1 (en) | 2000-11-06 | 2011-11-10 | Recovering a system that has experienced a fault |
Publications (1)
Publication Number | Publication Date |
---|---|
US20060271819A1 true US20060271819A1 (en) | 2006-11-30 |
Family
ID=36942149
Family Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/706,960 Expired - Lifetime US7089449B1 (en) | 2000-11-06 | 2000-11-06 | Recovering a system that has experienced a fault |
US11/497,698 Abandoned US20060271819A1 (en) | 2000-11-06 | 2006-08-02 | Recovering a system that has experienced a fault |
US13/294,077 Abandoned US20120060048A1 (en) | 2000-11-06 | 2011-11-10 | Recovering a system that has experienced a fault |
US13/612,096 Abandoned US20130067276A1 (en) | 2000-11-06 | 2012-09-12 | Software and methods for recovering a network node that has experienced a fault |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/706,960 Expired - Lifetime US7089449B1 (en) | 2000-11-06 | 2000-11-06 | Recovering a system that has experienced a fault |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/294,077 Abandoned US20120060048A1 (en) | 2000-11-06 | 2011-11-10 | Recovering a system that has experienced a fault |
US13/612,096 Abandoned US20130067276A1 (en) | 2000-11-06 | 2012-09-12 | Software and methods for recovering a network node that has experienced a fault |
Country Status (1)
Country | Link |
---|---|
US (4) | US7089449B1 (en) |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7979690B1 (en) * | 2008-05-06 | 2011-07-12 | Acronis Inc. | System and method for booting a computer from backup |
US8145940B1 (en) | 2002-10-09 | 2012-03-27 | Rpx Corporation | Method and system for updating a software image |
US8336044B2 (en) | 2002-10-09 | 2012-12-18 | Rpx Corporation | Method and system for deploying a software image |
US9207871B2 (en) | 2013-02-11 | 2015-12-08 | Hewlett-Packard Development Company, L.P. | Internal notebook microSD reader with read-only switch |
US9542259B1 (en) * | 2013-12-23 | 2017-01-10 | Jpmorgan Chase Bank, N.A. | Automated incident resolution system and method |
CN106412200A (en) * | 2016-10-08 | 2017-02-15 | 四川秘无痕信息安全技术有限责任公司 | Method for extracting contact data of WP system |
CN106453780A (en) * | 2016-10-08 | 2017-02-22 | 四川秘无痕信息安全技术有限责任公司 | Method of extracting contact person data of Saipan system |
CN109240869A (en) * | 2018-09-21 | 2019-01-18 | 郑州云海信息技术有限公司 | A kind of method and apparatus of determining target hard disk backboard |
Families Citing this family (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7593972B2 (en) * | 2001-04-13 | 2009-09-22 | Ge Medical Systems Information Technologies, Inc. | Application service provider based redundant archive services for medical archives and/or imaging systems |
JP2004361994A (en) * | 2003-05-30 | 2004-12-24 | Toshiba Corp | Data management device, data management method and program |
US20060023627A1 (en) * | 2004-08-02 | 2006-02-02 | Anil Villait | Computing system redundancy and fault tolerance |
US7370234B2 (en) | 2004-10-14 | 2008-05-06 | International Business Machines Corporation | Method for system recovery |
US7930589B2 (en) * | 2005-06-17 | 2011-04-19 | Analog Devices, Inc. | Interrupt-responsive non-volatile memory system and method |
GB2431748B (en) * | 2005-10-31 | 2010-12-22 | Hewlett Packard Development Co | Data back-up and recovery |
TW200721008A (en) * | 2005-11-23 | 2007-06-01 | Inventec Corp | Method and system for switching between embedded operating systems of computer platform |
US7565524B2 (en) * | 2006-07-03 | 2009-07-21 | Itzhak Levy | Computer backup system at BIOS level |
GB2443008A (en) | 2006-10-20 | 2008-04-23 | Vodafone Plc | Group management in a Session Initiation Protocol network. |
GB0620928D0 (en) * | 2006-10-20 | 2006-11-29 | Vodafone Plc | Boot process |
US7676503B2 (en) * | 2006-11-27 | 2010-03-09 | Microsoft Corporation | Hybrid computer restore using network service |
US8028158B1 (en) * | 2008-07-10 | 2011-09-27 | Cms Products, Inc. | Method and apparatus for creating a self booting operating system image backup on an external USB hard disk drive that is capable of performing a complete restore to an internal system disk |
JP5941273B2 (en) * | 2011-12-02 | 2016-06-29 | キヤノン株式会社 | Information processing apparatus and control method thereof |
CN106462478B (en) * | 2015-04-29 | 2019-06-11 | 华为技术有限公司 | Data reconstruction method, device and terminal |
US10592329B2 (en) | 2017-03-02 | 2020-03-17 | Acer Incorporated | Method and electronic device for continuing executing procedure being aborted from physical address where error occurs |
US10795769B2 (en) * | 2019-02-04 | 2020-10-06 | Dell Products L.P. | Facilitating the identification of a service operating system when a main operating system fails |
Citations (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4972316A (en) * | 1987-03-30 | 1990-11-20 | International Business Machines Corporation | Method of handling disk sector errors in DASD cache |
US5142680A (en) * | 1989-04-26 | 1992-08-25 | Sun Microsystems, Inc. | Method for loading an operating system through a network |
US5455933A (en) * | 1993-07-14 | 1995-10-03 | Dell Usa, L.P. | Circuit and method for remote diagnosis of personal computers |
US5469573A (en) * | 1993-02-26 | 1995-11-21 | Sytron Corporation | Disk operating system backup and recovery system |
US5513314A (en) * | 1995-01-27 | 1996-04-30 | Auspex Systems, Inc. | Fault tolerant NFS server system and mirroring protocol |
US5615330A (en) * | 1994-11-12 | 1997-03-25 | International Computers Limited | Recovery method for a high availability data processing system |
US5627964A (en) * | 1994-12-13 | 1997-05-06 | Microsoft Corporation | Reduce or fail-safe bootstrapping of a system having a graphical user interface |
US5713024A (en) * | 1994-06-10 | 1998-01-27 | Exabyte Corporation | Cold boot data backup system |
US5765151A (en) * | 1995-08-17 | 1998-06-09 | Sun Microsystems, Inc. | System and method for file system fix-on-panic for a computer operating system |
US5805882A (en) * | 1996-07-19 | 1998-09-08 | Compaq Computer Corporation | Computer system and method for replacing obsolete or corrupt boot code contained within reprogrammable memory with new boot code supplied from an external source through a data port |
US5905888A (en) * | 1997-02-19 | 1999-05-18 | On Spec Electronic, Inc. | Bootable redundant hard disk attached to a PC's parallel port with rom-address auto-detect and configure during BIOS scan |
US5974503A (en) * | 1997-04-25 | 1999-10-26 | Emc Corporation | Storage and access of continuous media files indexed as lists of raid stripe sets associated with file names |
US6016553A (en) * | 1997-09-05 | 2000-01-18 | Wild File, Inc. | Method, software and apparatus for saving, using and recovering data |
US6145088A (en) * | 1996-06-18 | 2000-11-07 | Ontrack Data International, Inc. | Apparatus and method for remote data recovery |
US6173417B1 (en) * | 1998-04-30 | 2001-01-09 | Intel Corporation | Initializing and restarting operating systems |
US6195695B1 (en) * | 1998-10-27 | 2001-02-27 | International Business Machines Corporation | Data processing system and method for recovering from system crashes |
US6314532B1 (en) * | 1998-12-04 | 2001-11-06 | Lucent Technologies Inc. | Method and system for recovering from a software failure |
US6324654B1 (en) * | 1998-03-30 | 2001-11-27 | Legato Systems, Inc. | Computer network remote data mirroring system |
US20020042892A1 (en) * | 2000-10-06 | 2002-04-11 | Stephen Gold | Performing operating system recovery from external back-up media in a headless computer entity |
US6374366B1 (en) * | 1998-02-24 | 2002-04-16 | Adaptec, Inc. | Automated drive repair systems and methods |
US6378086B1 (en) * | 1997-02-24 | 2002-04-23 | International Business Machines Corporation | Method and system for recovering a computer system from a loadsource located at a remote location |
US6381694B1 (en) * | 1994-02-18 | 2002-04-30 | Apple Computer, Inc. | System for automatic recovery from software problems that cause computer failure |
US6393585B1 (en) * | 1998-12-23 | 2002-05-21 | Scientific-Atlanta, Inc. | Method and apparatus for restoring operating systems in a set-top box environment |
US20020091710A1 (en) * | 1999-11-10 | 2002-07-11 | Scott Dunham | Method for backup and restore of a multi-lingual network file server |
US6446175B1 (en) * | 1999-07-28 | 2002-09-03 | Storage Technology Corporation | Storing and retrieving data on tape backup system located at remote storage system site |
US6535998B1 (en) * | 1999-07-26 | 2003-03-18 | Microsoft Corporation | System recovery by restoring hardware state on non-identical systems |
US6578160B1 (en) * | 2000-05-26 | 2003-06-10 | Emc Corp Hopkinton | Fault tolerant, low latency system resource with high level logging of system resource transactions and cross-server mirrored high level logging of system resource transactions |
US6625625B1 (en) * | 1999-04-09 | 2003-09-23 | Hitachi, Ltd. | System and method for backup and restoring by utilizing common and unique portions of data |
US6701450B1 (en) * | 1998-08-07 | 2004-03-02 | Stephen Gold | System backup and recovery |
US6799224B1 (en) * | 1998-03-10 | 2004-09-28 | Quad Research | High speed fault tolerant mass storage network information server |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4910658A (en) * | 1985-09-04 | 1990-03-20 | Eaton Leonard Technologies, Inc. | Real time process controller with serial I/O bus |
US5390324A (en) * | 1992-10-02 | 1995-02-14 | Compaq Computer Corporation | Computer failure recovery and alert system |
US20020083361A1 (en) * | 1996-01-04 | 2002-06-27 | Compaq Information Technologies Group, L.P. | Home base user interface |
US6901493B1 (en) * | 1998-02-24 | 2005-05-31 | Adaptec, Inc. | Method for protecting data of a computer system |
US6065073A (en) * | 1998-08-17 | 2000-05-16 | Jato Technologies, Inc. | Auto-polling unit for interrupt generation in a network interface device |
US6948099B1 (en) * | 1999-07-30 | 2005-09-20 | Intel Corporation | Re-loading operating systems |
US6606716B1 (en) * | 1999-10-06 | 2003-08-12 | Dell Usa, L.P. | Method and system for automated technical support for computers |
US6738928B1 (en) * | 2000-06-19 | 2004-05-18 | Hewlett-Packard Development Company, L.P. | Method and expert system for analysis of crash dumps |
-
2000
- 2000-11-06 US US09/706,960 patent/US7089449B1/en not_active Expired - Lifetime
-
2006
- 2006-08-02 US US11/497,698 patent/US20060271819A1/en not_active Abandoned
-
2011
- 2011-11-10 US US13/294,077 patent/US20120060048A1/en not_active Abandoned
-
2012
- 2012-09-12 US US13/612,096 patent/US20130067276A1/en not_active Abandoned
Patent Citations (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4972316A (en) * | 1987-03-30 | 1990-11-20 | International Business Machines Corporation | Method of handling disk sector errors in DASD cache |
US5142680A (en) * | 1989-04-26 | 1992-08-25 | Sun Microsystems, Inc. | Method for loading an operating system through a network |
US5469573A (en) * | 1993-02-26 | 1995-11-21 | Sytron Corporation | Disk operating system backup and recovery system |
US5455933A (en) * | 1993-07-14 | 1995-10-03 | Dell Usa, L.P. | Circuit and method for remote diagnosis of personal computers |
US6381694B1 (en) * | 1994-02-18 | 2002-04-30 | Apple Computer, Inc. | System for automatic recovery from software problems that cause computer failure |
US5713024A (en) * | 1994-06-10 | 1998-01-27 | Exabyte Corporation | Cold boot data backup system |
US5615330A (en) * | 1994-11-12 | 1997-03-25 | International Computers Limited | Recovery method for a high availability data processing system |
US5627964A (en) * | 1994-12-13 | 1997-05-06 | Microsoft Corporation | Reduce or fail-safe bootstrapping of a system having a graphical user interface |
US5513314A (en) * | 1995-01-27 | 1996-04-30 | Auspex Systems, Inc. | Fault tolerant NFS server system and mirroring protocol |
US5765151A (en) * | 1995-08-17 | 1998-06-09 | Sun Microsystems, Inc. | System and method for file system fix-on-panic for a computer operating system |
US6145088A (en) * | 1996-06-18 | 2000-11-07 | Ontrack Data International, Inc. | Apparatus and method for remote data recovery |
US5805882A (en) * | 1996-07-19 | 1998-09-08 | Compaq Computer Corporation | Computer system and method for replacing obsolete or corrupt boot code contained within reprogrammable memory with new boot code supplied from an external source through a data port |
US5905888A (en) * | 1997-02-19 | 1999-05-18 | On Spec Electronic, Inc. | Bootable redundant hard disk attached to a PC's parallel port with rom-address auto-detect and configure during BIOS scan |
US6378086B1 (en) * | 1997-02-24 | 2002-04-23 | International Business Machines Corporation | Method and system for recovering a computer system from a loadsource located at a remote location |
US5974503A (en) * | 1997-04-25 | 1999-10-26 | Emc Corporation | Storage and access of continuous media files indexed as lists of raid stripe sets associated with file names |
US6016553A (en) * | 1997-09-05 | 2000-01-18 | Wild File, Inc. | Method, software and apparatus for saving, using and recovering data |
US6374366B1 (en) * | 1998-02-24 | 2002-04-16 | Adaptec, Inc. | Automated drive repair systems and methods |
US6799224B1 (en) * | 1998-03-10 | 2004-09-28 | Quad Research | High speed fault tolerant mass storage network information server |
US6324654B1 (en) * | 1998-03-30 | 2001-11-27 | Legato Systems, Inc. | Computer network remote data mirroring system |
US6173417B1 (en) * | 1998-04-30 | 2001-01-09 | Intel Corporation | Initializing and restarting operating systems |
US6701450B1 (en) * | 1998-08-07 | 2004-03-02 | Stephen Gold | System backup and recovery |
US6195695B1 (en) * | 1998-10-27 | 2001-02-27 | International Business Machines Corporation | Data processing system and method for recovering from system crashes |
US6314532B1 (en) * | 1998-12-04 | 2001-11-06 | Lucent Technologies Inc. | Method and system for recovering from a software failure |
US6393585B1 (en) * | 1998-12-23 | 2002-05-21 | Scientific-Atlanta, Inc. | Method and apparatus for restoring operating systems in a set-top box environment |
US6625625B1 (en) * | 1999-04-09 | 2003-09-23 | Hitachi, Ltd. | System and method for backup and restoring by utilizing common and unique portions of data |
US6535998B1 (en) * | 1999-07-26 | 2003-03-18 | Microsoft Corporation | System recovery by restoring hardware state on non-identical systems |
US6446175B1 (en) * | 1999-07-28 | 2002-09-03 | Storage Technology Corporation | Storing and retrieving data on tape backup system located at remote storage system site |
US20020091710A1 (en) * | 1999-11-10 | 2002-07-11 | Scott Dunham | Method for backup and restore of a multi-lingual network file server |
US6578160B1 (en) * | 2000-05-26 | 2003-06-10 | Emc Corp Hopkinton | Fault tolerant, low latency system resource with high level logging of system resource transactions and cross-server mirrored high level logging of system resource transactions |
US20020042892A1 (en) * | 2000-10-06 | 2002-04-11 | Stephen Gold | Performing operating system recovery from external back-up media in a headless computer entity |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8145940B1 (en) | 2002-10-09 | 2012-03-27 | Rpx Corporation | Method and system for updating a software image |
US8336044B2 (en) | 2002-10-09 | 2012-12-18 | Rpx Corporation | Method and system for deploying a software image |
US7979690B1 (en) * | 2008-05-06 | 2011-07-12 | Acronis Inc. | System and method for booting a computer from backup |
US8312259B1 (en) | 2008-05-06 | 2012-11-13 | Acronis International Gmbh | System and method for booting a computer from backup |
US9207871B2 (en) | 2013-02-11 | 2015-12-08 | Hewlett-Packard Development Company, L.P. | Internal notebook microSD reader with read-only switch |
US9542259B1 (en) * | 2013-12-23 | 2017-01-10 | Jpmorgan Chase Bank, N.A. | Automated incident resolution system and method |
CN106412200A (en) * | 2016-10-08 | 2017-02-15 | 四川秘无痕信息安全技术有限责任公司 | Method for extracting contact data of WP system |
CN106453780A (en) * | 2016-10-08 | 2017-02-22 | 四川秘无痕信息安全技术有限责任公司 | Method of extracting contact person data of Saipan system |
CN109240869A (en) * | 2018-09-21 | 2019-01-18 | 郑州云海信息技术有限公司 | A kind of method and apparatus of determining target hard disk backboard |
Also Published As
Publication number | Publication date |
---|---|
US7089449B1 (en) | 2006-08-08 |
US20120060048A1 (en) | 2012-03-08 |
US20130067276A1 (en) | 2013-03-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20060271819A1 (en) | Recovering a system that has experienced a fault | |
US8200955B2 (en) | Apparatus and method for booting a system | |
US6665813B1 (en) | Method and apparatus for updateable flash memory design and recovery with minimal redundancy | |
US7895428B2 (en) | Applying firmware updates to servers in a data center | |
US6976058B1 (en) | Computer card for storing bootable images and providing remote management functions | |
US20040255106A1 (en) | Recovery of operating system configuration data by firmware of computer system | |
US7840846B2 (en) | Point of sale system boot failure detection | |
US7512777B2 (en) | Method and system for maintaining system management BIOS | |
US20070294560A1 (en) | Support self-heal tool | |
CN101896889B (en) | Radio terminal, radio terminal nonvolatile memory, and diagnosis information fail-safe storage method | |
US7058563B1 (en) | Device driver auto-load | |
US5987625A (en) | Method and apparatus for testing network bootable devices | |
JP5684962B2 (en) | Method and system for transferring application programs from system firmware to a storage device | |
US20150248247A1 (en) | Multi-mode hybrid storage drive | |
US20160321132A1 (en) | Receiving an update code prior to completion of a boot procedure | |
US8949588B1 (en) | Mobile telephone as bootstrap device | |
US8504869B2 (en) | Kernel swapping systems and methods for recovering a network device | |
CN113032183A (en) | System management method, device, computer equipment and storage medium | |
US11740969B2 (en) | Detecting and recovering a corrupted non-volatile random-access memory | |
US10572166B1 (en) | Firmware download for a solid state storage card | |
US10853085B2 (en) | Adjustable performance boot system | |
Cisco | Channel Interface Processor Microcode Release Note and Microcode Upgrade Requirements | |
Cisco | Channel Interface Processor Microcode Release Note and Microcode Upgrade Requirements | |
Cisco | Channel Interface Processor Microcode Release Note and Microcode Upgrade Requirements | |
US20070061227A1 (en) | Determining a computer system inventory |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: MEI CALIFORNIA, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICRON ELECTRONICS, INC.;REEL/FRAME:029427/0284 Effective date: 20010322 |