GB2559967A - Method for a computer system and computer system - Google Patents
Method for a computer system and computer system Download PDFInfo
- Publication number
- GB2559967A GB2559967A GB1702813.5A GB201702813A GB2559967A GB 2559967 A GB2559967 A GB 2559967A GB 201702813 A GB201702813 A GB 201702813A GB 2559967 A GB2559967 A GB 2559967A
- Authority
- GB
- United Kingdom
- Prior art keywords
- firmware
- components
- redundant
- computer system
- system components
- 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.)
- Withdrawn
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
- G06F8/654—Updates using techniques specially adapted for alterable solid state memories, e.g. for EEPROM or flash memories
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
- G06F8/66—Updates of program code stored in read-only memory [ROM]
-
- 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/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
-
- 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/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0751—Error or fault detection not based on redundancy
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Quality & Reliability (AREA)
- Hardware Redundancy (AREA)
- Stored Programmes (AREA)
Abstract
Method 200 involving detecting 202 redundant components of computer system; verifying 205 whether firmware of components is up-to-date; if firmware is outdated, selecting 207 one of the detected components and updating 208 its firmware; and repeating the selecting and updating steps for further components. Detecting may comprise detecting all redundant components of one or more predetermined types. Prior to the updating step, error detection 204 may be performed and the method cancelled 210 if critical system errors are detected. The error detection may be performed in each repetition. After the updating stem, a final verification 209 of the update may be executed comprising the component generating an update confirmation and/or restarting the component or system. Detecting 202 may comprise generating a list of components or reading a list of components from a storage module, and selecting 207 may comprise selecting a component from the list. The list may be generated based on a capacity utilisation 203 of the detected redundant components. A computer system with redundant components and control unit e.g. baseboard management controller (BMG) to execute the method is also disclosed. The system is capable of continuing the ongoing operation although a component is being updated.
Description
(71) Applicant(s):
Fujitsu Limited (Incorporated in Japan)
1-1 Kamikodanaka 4-chome, Nakahara-ku, Kawasakishi, Kanagawa 211-8588, Japan
1702813.5 (51) (NT CL:
G06F 9/44 (2018.01)
21.02.2017
G06F9/46 (2006.01) (56) Documents Cited:
JP 2008217201 A US 20140281804 A1 US 20050155029 A1
US 8726261 B2 US 20070261052 A1 US 20030037282 A1 (58) Field of Search:
INT CL G06F Other: WPI, EPODOC (72) Inventor(s):
Marco Paulsen (74) Agent and/or Address for Service:
Hoffmann Eitle
Harmsworth House, 3rd Floor, 13-15 Bouverie Street, LONDON, EC4Y 8DP, United Kingdom
Title of the Invention: Method for a computer system and computer system Abstract Title: Updating firmware of redundant components of computer system
Method 200 involving detecting 202 redundant components of computer system; verifying 205 whether firmware of components is up-to-date; if firmware is outdated, selecting 207 one of the detected components and updating 208 its firmware; and repeating the selecting and updating steps for further components. Detecting may comprise detecting all redundant components of one or more predetermined types. Prior to the updating step, error detection 204 may be performed and the method cancelled 210 if critical system errors are detected. The error detection may be performed in each repetition. After the updating stem, a final verification 209 of the update may be executed comprising the component generating an update confirmation and/or restarting the component or system. Detecting 202 may comprise generating a list of components or reading a list of components from a storage module, and selecting 207 may comprise selecting a component from the list. The list may be generated based on a capacity utilisation 203 of the detected redundant components. A computer system with redundant components and control unit e.g. baseboard management controller (BMG) to execute the method is also disclosed. The system is capable of continuing the ongoing operation although a component is being updated.
1/2
u
Η- ;ΐ..ο
Method for a computer system and computer system
The invention relates to a method for a computer system with redundant system components and to a computer system with redundant system components.
Computer systems such as servers or other computer systems that are to be particularly fail-safe often comprise important system components multiple times. System components, which are available multiple times, are referred to as redundant. For example, if a computer system comprises two power supply units, and if one of the power supply units fails, the second power supply unit is operable and assumes the power supply of the computer system.
For operating system components, these system components usually have a firmware. A firmware is often developed further by a manufacturer when computer systems with system components having this firmware have been delivered already. In this process, errors in the firmware are corrected or the firmware is adapted to new components. The firmware of the system components can be updated in order to be able to perform troubleshooting in computer systems that have already been put into operation.
A firmware update in computer systems that have already been put into operation is problematic. Potential errors may result in the loss of data. To prevent this, a technician can monitor the computer system or the system components to be updated or shut them down for the time that the update is carried out. However, this is disadvantageous, since either a monitoring is to be done by the technician or the computer system is unavailable for the duration of the firmware update. This can be problematic, in particular in computer centers.
The object of the invention is to provide a method for a computer system and a computer system, by means of which a firmware update of the system components is improved.
According to a first aspect, this object is achieved by a method for a computer system having redundant system components and a control unit. Redundant system components are detected. After that, verification is carried out as to whether a firmware of the detected redundant system components is up-to-date or not. Furthermore, a system component from the detected redundant system components is selected by the control unit for updating the firmware of the system component, when the verification step for the selected system component showed an outdated firmware for the system component. The firmware of the system component is updated.
The steps of selecting and updating are repeated for further ones of the detected redundant system components.
The control unit assumes functions when updating the firmware of the system components. The control unit can be a component for monitoring or controlling system components of the computer system, in particular a so-called baseboard management controller, BMC for short. As a result, there is no need for a technician to be on site. For example, the detection of the redundant system components can be carried out by the control unit, but can also be initialized by a user. The selection of the system component is done during operation of the computer system. Here, the redundancy of the system components is used, whereby the computer system is capable of continuing the ongoing operation although a system component is being updated.
The simultaneous update of all redundant components of the same type is avoided, reducing the risk of a failure of the overall system. When an error occurs during the update of the selected component, the not-affected parallel redundant component of the same type can ensure further operation of the computer system.
The selection of the system component comprises the determination of a system component, for which an update is to be performed, but also the preparation of the system component for the firmware update. This may include a shut-down of the system component. This may likewise include the activation of another redundant system component as an active system component, so that the system component, the firmware of which is to be updated, no longer is the active system component.
Multiple, in particular all redundant system components of the computer system are updated automatically by repeating the steps of selecting and updating for further ones of the detected redundant system components. In addition to the repeating of the steps of selecting and updating, the step of verifying and/or the step of detecting can be repeated.
According to an advantageous embodiment, the step of detecting includes a detection of all redundant system components of a predefined type. Here, the predefined type relates to the type of the system component. For example, one type is a mains adaptor such as a power supply unit, PSU for short. Other types may include hard drive disks, other types of storage drives, fans and other components, which are installed multiple times in the computer system. Here, the detection relates to the detection of all power supply units in the computer system, for example.
According to an alternative embodiment, the step of detecting comprises a detection of all redundant system components of multiple predefined types. Here, by starting the method, more than one type of system components can be detected. For example, all power supply units, all storage drives and all fans are included in the described detection step.
According to an advantageous embodiment, the following step is carried out before the step of updating the firmware:
performing an error detection of errors of the computer system and cancelling the method if critical errors are detected.
A verification and detection of errors of the computer system before the update of the firmware of a detected redundant system component increases security, in particular the failsafe-security of the method. In this way, the computer system can be protected from a data loss caused by a crash, for example .
According to another advantageous embodiment, the step of repeating comprises repetition of the step of performing an error detection. If multiple redundant system components are updated by repeatedly carrying out steps of the method, performing the error detection before each update of a redundant system component provides the above-described security for all repetitions. In particular, it can be detected whether a previously performed update was error-free or not.
According to another advantageous embodiment, the following step is carried out after the step of updating:
carrying out a final verification of the firmware update, comprising generating of a confirmation of the update by the system components and/or a restart of the redundant system component or of the computer system.
Depending on the type of firmware update, a restart of the updated system component or of the computer system may be required. In other cases, setting a confirmation flag in a storage or the control unit may be sufficient, whereby an update confirmation is produced. Advantageously, a restart of the computer system can be delayed even across multiple cycles of the update of redundant system components.
According to another advantageous embodiment, the step of detecting comprises a generating of a list of redundant system components or a reading of a list of redundant system components from a storage module. Here, the selecting of the system component includes a selecting of a system component from this list.
A list can be stored in a storage module so that subsequently the control unit can process individual contents of the list.
The list can include control data and/or device data of the redundant system components, which are required to address a system component. The list can be stored during running operation of the computer system.
According to another advantageous embodiment, the generating of the list comprises a generating of an order of the redundant system component, which is based on a capacity utilization of the detected redundant system components. If two power supply units (PSU) are operated simultaneously, for example, and one power supply unit has a higher capacity utilization than the other one, the one with the lower capacity utilization can be selected for the firmware update. The power supply unit having the higher capacity utilization can continue operation.
According to a second aspect of the invention, the object is achieved by a computer system with redundant system components and a control unit. The computer system is configured to perform a method according to the type explained above.
All measures, aspects and advantages of the above described method can be expressed by structural features, aspects and advantages of the computer system described herein and vice versa .
According to an advantageous embodiment, the computer system comprises a storage module and a data network port. The control unit is configured to download firmware data for the firmware update into the storage via the data network port.
The invention will hereinafter be explained in greater detail by means of exemplary embodiments and the figures. The Figures show in:
Figure 1
Figure 2 a computer system according to one embodiment of the invention, and a flow chart for a method according to embodiments of the invention.
Figure 1 shows a computer system 100. In the exemplary embodiment, the computer system 100 is a server, e.g. a plugin server. Such computer systems are to have a high fail-safesecurity. To that end, system components are installed multiple times, i.e. redundantly, in the computer system 100. For example, two mains adaptors, i.e. power supply units, socalled PSUs, are installed in computer system 100, as redundant system components 101. The power supply units provide mutual security. In the exemplary embodiment, four hard disk drives are installed as redundant system components 102 as well. The redundant system components 102 are connected as a RAID (a RAID is a redundant array of independent hard disk drives). Here, data is assigned to different hard disk drives. If now one redundant system component 101, 102 fails, another redundant system component 101, 102 can completely assume the functions of the failing redundant system component
101, 102.
The redundant system components 101, 102 are operated with a firmware. To that end, a first firmware 106 is stored in the system components 101. A second firmware 107 is stored in the
- 8 system components 102. In operation of the redundant system components 101, 102, the respective firmware 106, 107 is executed by the redundant system components 101, 102. Just as well, the firmware may be stored in one or multiple storage modules, which are not arranged in the system components 101, 102 and operate the system components 101, 102 via a data line such as a bus line.
The computer system 100 comprises a control unit 103. In the exemplary embodiment, the control unit 103 is a management controller, in particular a so-called baseboard management controller, BMC for short, e.g. an integrated remote management controller, iRMC for short. The control unit 103 is connected to the system components 101, 102 by means of bus lines 104. The control unit 103 can communicate with the system components 101, 102 via the bus lines 104. The control unit 103 can detect and control individual system components 101, 102, for example.
The computer system 100 comprises a storage module 105. The storage module 105 is connected to the control unit 103. The control unit 103 can write data into the storage module 105 and read it from the storage module 105. The first firmware 106 and the second firmware 107 are stored in the storage module 105. The stored firmwares 106, 107 serve as a back-up and reference in a firmware update of the redundant system components 101, 102. In an alternative embodiment, merely information about the first firmware 106 and the second firmware 107 is stored in the storage module 105 instead of the first firmware 106 and the second firmware 107. Here, this information includes data that suggests the up-to-dateness of the respective firmware. For example, a creation date of the firmware is stored. In this embodiment, additionally, the first firmware 106 and the second firmware 107 is stored in a separate storage module (not illustrated) in each case in the system components 101 and in the system components 102 and determine the operation thereof.
The computer system 100 comprises a data network interface 108. The computer system 100 can establish a connection to a data network via the data network interface 108. In this way, the computer system 100 can communicate with another server or a personal computer via the internet, for example. The control unit 103 is connected to the data network interface 108. In this way, the control unit 103 can communicate via the data network, e.g. in order to download an updated firmware or to receive update instructions.
Figure 2 shows a flow chart 200 for a method for the abovedescribed computer system 100.
In a first step 201, an update request is received by the control unit 103. The update request is received via the data network interface 108. In another embodiment, the update request is received locally by a user input or a timecontrolled event.
In step 202, the control unit 103 detects redundant system components 101, 102 of the computer system 100. In the exemplary embodiment, the control unit 103 detects the system components 101, 102 via the bus lines 104. The detected system components 101, 102 are stored in a list by the control unit
103. For example, the list is stored in the storage module 105. Alternatively, the list may also be stored in another storage module. In an alternative embodiment, the control unit 103 detects the system components 101, 102 by reading out a list from a storage module. The storage module can be the storage module 105, but it can just as well be another storage module, e.g. a BIOS storage module. The list read out by the control unit 103 can be a user-generated list or a list that was created by a BIOS or another computer program. In yet another alternative embodiment, the control unit 103 receives a list of the redundant system components 101, 102 via the data network interface 108.
In yet another embodiment, the control unit 103 detects all system components of the computer system 100, i.e. also nonredundant ones. By comparing device data of each individual system component, the control unit 103 identifies the redundant system components.
After step components components the control
202, the detection of the redundant system 101, 102, there is a list of redundant system 101, 102, which can be read out and processed by unit 103.
In a step 203, a state of the system components 101, 102 is checked. Here, it is verified whether the respective system component 101, 102 is active or on a sleep mode or switchedoff. Verification can also be made as to whether the capacity of the system component 101, 102 is utilized and if so, how high capacity utilization is. Capacity utilization relates to a characteristic feature of the respective system component
101, 102. A power supply unit, such as a PSU, is checked in terms of a power output, for example. A hard disk drive is checked in terms of reading and/or writing access, for example. In a fan, the number of revolutions per minute is checked, for example.
In an alternative embodiment, the capacity utilization of each component 101, 102 is checked in step 202 when detecting the system components 101, 102. The creation of the list can then be based upon the capacity utilization of the system components 101, 102. For example, system components 101, 102 having a lower capacity utilization are listed above system components 101, 102 having a higher capacity utilization, leading to a prioritized processing of the system components 101, 102 that have a lower capacity utilization. Here, an order of the type of the system components 101, 102 can be maintained as well. For example, the power supply units are sorted amongst one another and hard disk drives are separately sorted amongst one another.
In step 204, the computer system 100 is checked for existing errors. Here, this check includes software errors, e.g. nonreacting programs, such as a non-reacting operating system, or not addressable system components 101, 102, for example. If an error is detected, the method is stopped in step 210 and an error message is output. The error message can be output with a monitor connected to the computer system 100 and also via the data network interface 108. If no errors are detected in the computer system 100 that would oppose a firmware update of the detected redundant system components 101, 102, the method continues with step 205.
In step 205, it is checked whether a firmware of the detected redundant system components 101, 102 is up-to-date or not. To that end, the version number of the firmware of the system components 101, 102 is compared to a version number of a new firmware. The new firmware is either checked on an external server and downloaded only if an update is required, or downloaded first and checked afterwards. In the described exemplary embodiment, in each case one firmware of one type of system component 101, 102 is compared to a new firmware. For example, a stored firmware of hard disk drives is compared to a new firmware for hard disk drives. In an alternative embodiment, in each case the firmware of an individual system component 101, 102 is compared to a new firmware. For example, a comparison is done for a first hard disk drive, and subsequently a comparison is done for a second hard disk drive, etc. If it is found in step 205 that an update of a firmware is not required, the method ends in step 201. A notification can be generated here. The notification can be transmitted via the data network interface 108. Just as well, the notification can be displayed on a monitor or be written to a BIOS.
If the verification performed in step 205 shows that a firmware update is required, it will be verified subsequently in step 206 whether a firmware update for the redundant system component 101, 102 or the type of system component 101, 102 is possible. This verification includes, for example, a capacity utilization of the system component 101, 102 to be updated. It can also be checked whether the system component 101, 102 to be updated is to be switched off or become inactive. If the verification is negative, i.e. if an update of the firmware of the corresponding system component 101, 102 would result in an error in the computer system 100 or a failure of the computer system 100, the method is stopped in step 210. Optionally, a notification can be generated, like in step 205. In an alternative embodiment, where the redundant system components 101, 102 are grouped by type, instead of stopping the method in step 210, the next type of system component 101, 102 is selected and the method continues.
If the verification performed in step 206 showed that a firmware update of the corresponding system components 101,
102 is possible, one system component 101, 102 is selected for a firmware update in step 207. In other words, a firmware of a system component 101, 102 is selected to be updated. Here, selection is effected based on the generated list of the detected redundant system components 101, 102, as described above. Thus, selection is based on the basis of one or more previously set criteria, e.g., the capacity utilization or physical order of the redundant system components 101, 102 in the computer system 100. Selection is performed by the control unit 103. In the selection of the system component 101, 102 to be updated, the control unit 103 takes all steps required to perform a firmware update for this system component 101, 102. For example, a function of the system component 101, 102 to be updated is previously assigned to the redundant system component 101, 102, which is not to be updated.
Thus, the computer system 100 can continue operation without limitation. Due to the redundancy of the system components 101, 102, none of the functions required for operating the computer system 100 fails during the firmware update of the respective system component 101, 102.
In step 208, the firmware of the system component 101, 102 selected in step 207 is updated. The update is initialized here by the control unit 103. The realization of the firmware update is executed by the control unit 103 via an interface of the selected redundant system component 101, 102, in particular the component interface thereof. In an alternative embodiment, after an initialization of the update by the control unit 103, the firmware update is performed by the system component 101, 102 per se.
In step 209, a final verification of the firmware update is performed. Here, the final verification includes the required steps to make the system component 101, 102 that has been updated fully operational again. In the exemplary embodiment, a confirmation is created for the final verification, which is stored in a BIOS. In further embodiments, the update confirmation can be additionally or alternatively be sent via the data network interface 108. In further embodiments, the final verification additionally or alternatively includes a restart of the updated selected redundant system component 101, 102 or of the entire computer system 100.
The method is repeated until all redundant system components 101, 102, for which an updated firmware is available, have been updated, unless the method was not previously stopped or aborted (e.g. in the steps 204, 205 or 206).
In order to repeat the method, at least steps 207, 208 and 209 are executed repeatedly. In alternative embodiments, furthers steps are repeated additionally. A repetition can be started after each of steps 201 to 206. Due to the automatic execution of the method steps by the control unit 103, the method can be operated fully-automatically. Once an update request has been received in step 201, a start of a repetition of the method is conceivable with any following step 202 to 207. For example, a repetition of an error detection in step 204 further increases the fail-safe security of the computer system 100.
In another embodiment, step 207 is performed before step 205. Here, first a system component 101, 102 which can be updated is selected. After that, it is verified whether an updated firmware is available for this system component 101, 102. The firmwares are compared by means of a firmware version as described above, for example. If an update is not required for the selected system component 101, 102, the method continues and is repeated with the next system component 101, 102, as described above. The order of the steps is maintained in the repetitions according to this embodiment, so that the selection is performed prior to verification.
List of reference numerals
| 100 | computer system | |
| 101, 102 | system component | |
| 5 | 103 | control unit |
| 104 | bus line | |
| 105 | storage module | |
| 106 | first firmware | |
| 107 | second firmware | |
| 10 | 108 | data network interface |
| 200 | flow chart | |
| 201 to 210 | method steps |
Claims (10)
1. Method for a computer system with redundant system components and a control unit, wherein the following steps are executed:
- detecting redundant system components;
- verifying whether a firmware of the detected redundant system components is up-to-date;
- selecting, by the control unit, a system component from the detected redundant system components for updating the firmware of the system component, if the step of verifying the selected system component resulted in an outdated firmware of the system component;
- updating the firmware of the system component;
- repeating the steps of selecting and updating for further of the detected redundant system components.
2. Method according to claim 1, wherein the step of detecting comprises detecting all redundant system components of a predetermined type.
3. Method according to claim 1, wherein the step of detecting comprises a detection of all redundant system components of multiple predetermined types.
4. Method according to one of claims 1 to 3, wherein, prior to the step of updating the firmware, the following step is performed:
- performing an error detection of errors of the computer system and cancelling the method, if critical errors are detected.
5. Method according to claim 4, wherein the step of repeating comprises a repetition of the step of performing the error detection.
6. Method according to one of claims 1 to 5, wherein, after the step of updating, the following step is performed:
- executing a final verification of the firmware update, comprising generating a confirmation of the update by the system component and/or restarting the system component or the computer system.
7. Method according to one of claims 1 to 6, wherein the step of detecting comprises generating a list of system components or reading a list of system components from a storage module, and wherein selecting the system component comprises selecting a system component from said list.
8. Method according to claim 7, wherein generating the list comprises generating a sequence based upon a capacity utilization of the detected redundant system components.
9. Computer system with redundant system components and a control unit, wherein the computer system is configured to execute a method according to any of claims 1 to 8.
10. Computer system according to claim 9, wherein the computer system comprises a storage module and a data network port, and wherein the control unit is configured to download firmware data for updating the firmware into the storage module via the data network port.
Intellectual
Property
Office
Application No: GB1702813.5 Examiner: Mr Thomas Davies
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| DE102016103451.7A DE102016103451A1 (en) | 2016-02-26 | 2016-02-26 | Method for a computer system and computer system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| GB201702813D0 GB201702813D0 (en) | 2017-04-05 |
| GB2559967A true GB2559967A (en) | 2018-08-29 |
Family
ID=58486843
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| GB1702813.5A Withdrawn GB2559967A (en) | 2016-02-26 | 2017-02-21 | Method for a computer system and computer system |
Country Status (2)
| Country | Link |
|---|---|
| DE (1) | DE102016103451A1 (en) |
| GB (1) | GB2559967A (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP4198712A1 (en) * | 2022-12-16 | 2023-06-21 | Pfeiffer Vacuum Technology AG | Vacuum system and method for operating same |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030037282A1 (en) * | 2001-08-15 | 2003-02-20 | Jerry Berg | Method and system for version control in a fault tolerant system |
| US20050155029A1 (en) * | 2004-01-09 | 2005-07-14 | Dell Products L.P. | System and method for updating firmware of a storage drive in a storage network |
| US20070261052A1 (en) * | 2006-05-05 | 2007-11-08 | Honeywell International Inc. | Apparatus and method for allowing a fail-back to a prior software release in a process control system |
| JP2008217201A (en) * | 2007-03-01 | 2008-09-18 | Nec Corp | Automatic update method |
| US8726261B2 (en) * | 2011-04-06 | 2014-05-13 | Hewlett-Packard Development Company, L.P. | Zero downtime hard disk firmware update |
| US20140281804A1 (en) * | 2009-10-30 | 2014-09-18 | Cleversafe, Inc. | Distributed storage network for modification of a data object |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8856776B2 (en) * | 2009-02-05 | 2014-10-07 | International Business Machines Corporation | Updating firmware without disrupting service |
| US9286056B2 (en) * | 2014-05-19 | 2016-03-15 | International Business Machines Corporation | Reducing storage facility code load suspend rate by redundancy check |
-
2016
- 2016-02-26 DE DE102016103451.7A patent/DE102016103451A1/en not_active Ceased
-
2017
- 2017-02-21 GB GB1702813.5A patent/GB2559967A/en not_active Withdrawn
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030037282A1 (en) * | 2001-08-15 | 2003-02-20 | Jerry Berg | Method and system for version control in a fault tolerant system |
| US20050155029A1 (en) * | 2004-01-09 | 2005-07-14 | Dell Products L.P. | System and method for updating firmware of a storage drive in a storage network |
| US20070261052A1 (en) * | 2006-05-05 | 2007-11-08 | Honeywell International Inc. | Apparatus and method for allowing a fail-back to a prior software release in a process control system |
| JP2008217201A (en) * | 2007-03-01 | 2008-09-18 | Nec Corp | Automatic update method |
| US20140281804A1 (en) * | 2009-10-30 | 2014-09-18 | Cleversafe, Inc. | Distributed storage network for modification of a data object |
| US8726261B2 (en) * | 2011-04-06 | 2014-05-13 | Hewlett-Packard Development Company, L.P. | Zero downtime hard disk firmware update |
Also Published As
| Publication number | Publication date |
|---|---|
| GB201702813D0 (en) | 2017-04-05 |
| DE102016103451A1 (en) | 2017-09-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP5851503B2 (en) | Providing high availability for applications in highly available virtual machine environments | |
| US7340638B2 (en) | Operating system update and boot failure recovery | |
| US20170046152A1 (en) | Firmware update | |
| US20060259815A1 (en) | Systems and methods for ensuring high availability | |
| TW201715395A (en) | Method for recovering a baseboard management controller and baseboard management controller | |
| US8219851B2 (en) | System RAS protection for UMA style memory | |
| WO2013094048A1 (en) | Testing server, information processing system, testing program, and testing method | |
| JP2016164785A (en) | Secure recovery apparatus and method | |
| US8806265B2 (en) | LPAR creation and repair for automated error recovery | |
| JP5183542B2 (en) | Computer system and setting management method | |
| US20130138934A1 (en) | Loading configuration information | |
| US10275330B2 (en) | Computer readable non-transitory recording medium storing pseudo failure generation program, generation method, and generation apparatus | |
| CN110865907B (en) | Method and system for providing service redundancy between master server and slave server | |
| US11321454B2 (en) | Notice of intrusion into firmware | |
| US9471256B2 (en) | Systems and methods for restoring data in a degraded computer system | |
| US10824517B2 (en) | Backup and recovery of configuration files in management device | |
| TWI764454B (en) | Firmware corruption recovery | |
| US8448014B2 (en) | Self-healing failover using a repository and dependency management system | |
| GB2559967A (en) | Method for a computer system and computer system | |
| JP5909948B2 (en) | Information processing apparatus and information processing apparatus testing method | |
| US7533297B2 (en) | Fault isolation in a microcontroller based computer | |
| US9195529B2 (en) | Information processing apparatus and activation method | |
| JP4715552B2 (en) | Fault detection method | |
| JP6911591B2 (en) | Information processing device, control device and control method of information processing device | |
| TWI777664B (en) | Booting method of embedded system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| WAP | Application withdrawn, taken to be withdrawn or refused ** after publication under section 16(1) |