Source: http://www.google.com/patents/US20090271654?dq=5,915,131
Timestamp: 2017-04-24 12:43:38
Document Index: 709688306

Matched Legal Cases: ['Application No. 2008', 'art 320', 'art 320', 'art 320', 'art 324', 'art 320', 'art 324', 'art 324', 'art 324', 'art 324', 'art 325', 'art 325', 'art 325', 'art 325']

Patent US20090271654 - Control method for information processing system, information processing ... - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsAn object of the present invention is to ensure, in an information processing system including a plurality of server apparatuses coupled to one another, reliability and availability thereof when failover is executed. In an information processing system, which includes a plurality of server apparatuses...http://www.google.com/patents/US20090271654?utm_source=gb-gplus-sharePatent US20090271654 - Control method for information processing system, information processing system, and programAdvanced Patent SearchTry the new Google Patents, with machine-classified Google Scholar results, and Japanese and South Korean patents.Publication numberUS20090271654 A1Publication typeApplicationApplication numberUS 12/392,094Publication dateOct 29, 2009Filing dateFeb 24, 2009Priority dateApr 23, 2008Also published asUS8074098, US8423162, US20120047395Publication number12392094, 392094, US 2009/0271654 A1, US 2009/271654 A1, US 20090271654 A1, US 20090271654A1, US 2009271654 A1, US 2009271654A1, US-A1-20090271654, US-A1-2009271654, US2009/0271654A1, US2009/271654A1, US20090271654 A1, US20090271654A1, US2009271654 A1, US2009271654A1InventorsMasayuki Fukuyama, Jun Nakayama, Kouji MasudaOriginal AssigneeHitachi, Ltd.Export CitationBiBTeX, EndNote, RefManPatent Citations (39), Referenced by (7), Classifications (9), Legal Events (3) External Links: USPTO, USPTO Assignment, EspacenetControl method for information processing system, information processing system, and program
US 20090271654 A1Abstract
the management server turning on the power supply to the standby server apparatus, and acquiring information on the standby server apparatus; turning off the power supply to the standby server apparatus after acquiring the information; and judging, based on the acquired information, whether or not failover to the standby server apparatus is possible. 2. The management method of an information processing system according to claim 1, wherein
as a method for acquiring the information from the standby server apparatus there can be selected a first information acquisition method in which the information is acquired from information outputted by a BIOS of the standby server apparatus, and a second information acquisition method in which the information is acquired from a check program which is executed in the standby server apparatus, and while the management server is acquiring the information on the standby server apparatus, the management server
prior to acquisition of the information by using the second information acquisition method, the management server stores the check program in the standby server apparatus. 4. The management method of an information processing system according to claim 1, wherein
the management server stores therein specifications required for the standby server apparatus that is set on standby to replace the active server apparatus and, the management server judges that failover to the standby server is impossible in the step of judging whether or not failover to the standby server apparatus is possible, in a case where the specifications of the standby apparatus which are specified by the information acquired from the standby server apparatus do not satisfy the specifications required for the active server apparatus which the standby apparatus is on standby to replace. 5. The management method of an information processing system according to claim 1, wherein
the management server stores therein time when the power supply to the standby server apparatus is turned off, and the management server executes the step of acquiring the information, and the step of judging whether or not the failover is possible in a case where a predetermined time period has passed since the stored time. 6. The management method of an information processing system according to claim 1, wherein
the management server executes the step of acquiring the information and the step of judging whether or not the failover is possible, when detecting a configuration change in the standby server apparatus. 7. The management method of an information processing system according to claim 6, wherein
the management server executes the step of acquiring the information and the step of judging whether or not the failover is possible, on the active server apparatus to which the standby server apparatus configuration of which is changed is set on standby to replace, and on a different standby server apparatus that is set on standby to replace the active server apparatus. 8. The management method of an information processing system according to claim 1, wherein;
the management server judges whether or not a different standby server apparatus is further set on standby to replace the active server apparatus, and with a result of the judgment, executes the step of acquiring the information and the step of judging whether or not the failover is possible, if the judgment indicates that the different standby server apparatus is set on standby. 9. An information processing system comprising:
a standby server apparatus coupled to an active server apparatus; and a management server coupled to the active server apparatus and to the standby server apparatus, the management server after turning on a power supply to the standby server apparatus, performing a failover from the active server apparatus to the standby server apparatus when detecting an occurrence of a failure in the active server apparatus, wherein the management server includes an information acquisition part operable to start operation, of the standby server apparatus, whose operation is at a stop, and then acquire information on the standby server apparatus; a server control part operable to turn off the power supply of the standby server apparatus after acquiring the information; and a status judgment part operable to judge, based on the acquired information, whether or not failover to the standby server apparatus is possible. 10. A program executed by a management server in an information processing system including an active server apparatus and a standby server apparatus coupled to one another, and a management server coupled to the active server apparatus and to the standby server apparatus, which after turning on a power supply to the standby server apparatus, performs a failover from the active server apparatus to the standby server apparatus when detecting an occurrence of a failure in the active server apparatus, the program being operable to implement:
a function of turning on the power supply, of the standby server apparatus, whose operation is at a stop, and then acquiring information on the standby server apparatus; a function of turning off the power supply of the standby server apparatus after acquiring the information; and a function of judging, based on the acquired information, whether or not failover to the standby server apparatus is possible. Description
[0001] The present application claims a priority from Japanese Patent Application No. 2008-113042 filed on Apr. 23, 2008, the content of which herein incorporated by reference.
[0045] In the Permissible Function 404, permissible types to be described later are set, the permissible types being pieces of information indicating specifications (functions and capabilities) required for each of the standby server apparatuses 20 which is set on standby to replace any one of the active server apparatuses 20. In the Allocated Area 405, identifiers of logical units (LUs) allocated to the respective server apparatuses 20 are set. In the Standby Server Flag 406, “1” is set to the server apparatuses 20 that are standby server apparatuses 20, and “0” is set to the others that are not standby server apparatuses 20. In the Check Requirement Flag 407, “1” is set to the server apparatuses 20 that require to be checked, and “0” is set to the others that do not require to be checked. In the Server Status 408, “normal” is set to the server apparatuses 20 that are operating normally, and “abnormal” is set to the others that are not operating normally. In the Server Last Power-off Time-and-Date 409, the last power-off time and date of the respective server apparatuses 20 is set.
[0050] Next, specific operations of the information processing system 1 will be described in connection with a flowchart. Note that, in the following description, the character “S” prefixed to reference numerals indicates “step.”
[0083] In S615, the management server 10 notifies the manager that there is a problem, and about the kind of problem. Note that this notification is made, for example, through an output to a display or a printer, or through an e-mail. In S616, the server management part 320 reflects contents of the configuration comparison table 340 in the configuration management table 330. In S617, the server management part 320 sets “0” in Check Requirement Flag 407 for the check target apparatus in the configuration management table 330. In S618, with reference to Standby Server Flag 406 in the configuration management table 330, the server management part 320 judges whether or not the check target apparatus is the standby server apparatus 20. If the check target apparatus is the standby server apparatus 20 (YES in S618), the processing proceeds to S619, whereas, if the check target apparatus is not the standby server apparatus 20 (NO in S618), the processing is ended. In S619, in Server Last Power-off Time-and-Date 409 in the configuration management table 330, for the standby server apparatus 20 which is the check target apparatus, the management server 10 sets the time and date (for example, present time and date) of when the standby server apparatus 20 is turned off. The check processing is implemented as described hereinabove.
[0085] In the time activation processing, the time activation judgment part 324 of the server management part 320 firstly acquires contents (last power-off time and date) in the Server Last Power-off Time-and-Date 409 of the standby server apparatuses 20 (for which “1” has been set in Standby Server Flag 406) from the configuration management table 330 (S711).
[0086] Subsequently, by comparing the last power-off time and date acquired in S711 with the present time and date, the time activation judgment part 324 sets “1” in Check Requirement Flag 407 for those of the standby server apparatuses 20 that have the last power-off times and dates exceeding a predetermined time period (for example, one hour, one day, or the like) (S712).
[0087] In S713 that follows, the time activation judgment part 324 judges whether or not there is any one of the server apparatuses 20 that has “1” set in the Check Requirement Flag 407 in the configuration management table 330. If there is any one of the server apparatuses 20 that has “1” set in the Check Requirement Flag 407 (YES in S713), the processing proceeds to S713, whereas, if there is no server apparatus 20 that has “1,” set in the Check Requirement Flag 407 (NO in S713), the processing is ended.
[0088] In S713, from the configuration management table 330, the time activation judgment part 324 selects one of not-yet selected server apparatuses 20 (server apparatuses having not been subjected yet to arbitration processing (S714) to be described later) that have “1” set in the Check Requirement Flag 407.
[0090] In S715, the time activation judgment part 324 judges whether or not there is any not-yet-selected one of the server apparatuses 20 that has been found in S713 to have “1” set in the Check Requirement Flag 407 (S715). If there is any not-yet-selected one (YES in S715), the processing proceeds to S713, whereas, if there is no not-yet-selected one (NO in S715), the processing is ended.
[0098] After receiving the configuration change notification (S812), the configuration change activation judgment part 325 of the management server 10 judges whether or not the server apparatus 20 specified by the configuration change notification is the active server apparatus 20 (S813). Based on a result of the judgment, if the specified server apparatus 20 is the active server apparatus 20 (“active” in S813), the processing proceeds to S814, whereas, if it is not the active server apparatus 20 (“not active” in S813), the processing proceeds to S815.
[0099] In S814, the configuration change activation judgment part 325 sets “1” in Check Requirement Flag 407, for the active server apparatus 20, in the configuration management table 330. Additionally, the configuration change activation judgment part 325 sets “1” in Check Requirement Flag 407 also for those of the server apparatuses 20 that have been set on standby to replace the active server apparatus 20. Note that, when the specified server apparatus 20 is the active server apparatus 20, those of the server apparatuses 20 that have been set on standby to replace the active server apparatus is also required to be checked for the following reason. If a configuration is changed for the active server apparatus 20, it necessitates another judgment on whether or not each of those server apparatuses 20 having been set on standby to replace the active server apparatus satisfies specifications required for the active server apparatus 20.
[0100] In S815, the configuration change activation judgment part 325 sets “1” in Check Requirement Flag 407 for the specified server apparatus 20. Processing in S816 to S819 is the same as the processing in S713 to S715 in FIG. 7A. The configuration change activation processing is implemented as described above.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS4377000 *Jun 18, 1980Mar 15, 1983Westinghouse Electric Corp.Automatic fault detection and recovery system which provides stability and continuity of operation in an industrial multiprocessor controlUS4958270 *Jan 23, 1989Sep 18, 1990Honeywell Inc.Method for control data base updating of a redundant processor in a process control systemUS5136498 *Sep 26, 1990Aug 4, 1992Honeywell Inc.Method for enacting failover of a 1:1 redundant pair of slave processorsUS6275953 *Sep 26, 1997Aug 14, 2001Emc CorporationRecovery from failure of a data processor in a network serverUS6625750 *Nov 16, 1999Sep 23, 2003Emc CorporationHardware and software failover services for a file serverUS6820098 *Mar 15, 2002Nov 16, 2004Hewlett-Packard Development Company, L.P.System and method for efficient and trackable asynchronous file replicationUS6823477 *Jan 23, 2001Nov 23, 2004Adaptec, Inc.Method and apparatus for a segregated interface for parameter configuration in a multi-path failover systemUS6832298 *Aug 28, 2002Dec 14, 2004Hitachi, Ltd.Server system operation control methodUS7076691 *Sep 12, 2002Jul 11, 2006Emc CorporationRobust indication processing failure mode handlingUS7159234 *Jun 27, 2003Jan 2, 2007Craig MurphySystem and method for streaming media server single frame failoverUS7287187 *Oct 15, 2001Oct 23, 2007Sun Microsystems, Inc.Method and apparatus for supplying redundant powerUS7293194 *Mar 11, 2005Nov 6, 2007Hitachi, Ltd.Method and device for switching database access part from for-standby to currently in useUS7313722 *Apr 18, 2006Dec 25, 2007Hitachi, Ltd.System and method for failoverUS7318107 *Jun 30, 2000Jan 8, 2008Intel CorporationSystem and method for automatic stream fail-overUS7320083 *Apr 23, 2004Jan 15, 2008Dot Hill Systems CorporationApparatus and method for storage controller to deterministically kill one of redundant servers integrated within the storage controller chassisUS7478263 *Jun 1, 2004Jan 13, 2009Network Appliance, Inc.System and method for establishing bi-directional failover in a two node clusterUS7516353 *May 16, 2008Apr 7, 2009Hitachi, Ltd.Fall over method through disk take over and computer system having failover functionUS7536576 *Jun 22, 2006May 19, 2009Hitachi, Ltd.Storage apparatus and power supply control method thereofUS7562247 *May 16, 2006Jul 14, 2009International Business Machines CorporationProviding independent clock failover for scalable blade serversUS7603423 *Jul 29, 2005Oct 13, 2009Ntt Docomo, Inc.Communication system with primary device and standby device to prevent suspension of service of the systemUS7711979 *Feb 16, 2007May 4, 2010Symantec CorporationMethod and apparatus for flexible access to storage facilitiesUS7802127 *Jun 20, 2007Sep 21, 2010Hitachi, Ltd.Method and computer system for failoverUS20030079093 *Aug 28, 2002Apr 24, 2003Hiroaki FujiiServer system operation control methodUS20030149750 *Feb 7, 2002Aug 7, 2003Franzenburg Alan M.Distributed storage arrayUS20040015668 *Jul 18, 2002Jan 22, 2004International Business Machines CorporationLimited concurrent host access in a logical volume management data storage environmentUS20050097394 *Dec 2, 2004May 5, 2005Yao WangMethod and apparatus for providing host resources for an electronic commerce siteUS20050143498 *Apr 16, 2004Jun 30, 2005Rudiger MuschAqueous adhesive dispersionsUS20050204183 *Jun 23, 2004Sep 15, 2005Hitachi, Ltd.System and method for failoverUS20060025871 *Sep 23, 2004Feb 2, 2006Mks Instruments, Inc.Failsafe switching of intelligent controller method and deviceUS20060129772 *Mar 11, 2005Jun 15, 2006Nobuo KawamuraData processing method and systemUS20060136686 *Dec 22, 2004Jun 22, 2006International Business Machines CorporationLog shipping data replication with parallel log writing and log shipping at the primary siteUS20060190760 *Apr 18, 2006Aug 24, 2006Hitachi, Ltd.System and method for failoverUS20060253725 *May 4, 2005Nov 9, 2006International Business Machines CorporationMethod and apparatus for expressing high availability cluster demand based on probability of breachUS20070143374 *Aug 7, 2006Jun 21, 2007D Souza Roy PEnterprise service availability through identity preservationUS20070150526 *Aug 7, 2006Jun 28, 2007D Souza Roy PEnterprise server version migration through identity preservationUS20070168058 *Jan 13, 2006Jul 19, 2007Emerson Process Management Power & Water Solutions , Inc.Method for redundant controller synchronization for bump-less failover during normal and program mismatch conditionsUS20070244937 *Apr 12, 2006Oct 18, 2007Flynn John T JrSystem and method for application fault tolerance and recovery using topologically remotely located computing devicesUS20080005614 *Jun 30, 2006Jan 3, 2008Seagate Technology LlcFailover and failback of write cache data in dual active controllersUS20090158081 *Dec 13, 2007Jun 18, 2009International Business Machines CorporationFailover Of Blade Servers In A Data Center* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS8423162Oct 31, 2011Apr 16, 2013Hitachi, Ltd.Control method for information processing system, information processing system, and programUS8726049Dec 2, 2011May 13, 2014Hitachi, Ltd.Computer system with a plurality of computer modules and baseboard management controllers, including a state machine that dynamically conducts a switching operationUS9461883 *Dec 12, 2014Oct 4, 2016Airbus Operations GmbhCoupling device for a data transmission network and data transmission networkUS20100289921 *May 14, 2009Nov 18, 2010Napoli Thomas ADigital camera having last image capture as default timeUS20130268801 *Sep 9, 2011Oct 10, 2013Nec CorporationServer management apparatus, server management method, and programUS20150172116 *Dec 12, 2014Jun 18, 2015Airbus Operations GmbhCoupling device for a data transmission network and data transmission networkEP2463778A1 *Dec 2, 2011Jun 13, 2012Hitachi, Ltd.Computer system* Cited by examinerClassifications U.S. Classification714/4.1, 714/E11.071International ClassificationG06F11/20Cooperative ClassificationG06F11/2033, G06F11/2025, G06F11/2028, G06F11/2046European ClassificationG06F11/20P2E, G06F11/20P2CLegal EventsDateCodeEventDescriptionMay 7, 2009ASAssignmentOwner name: HITACHI, LTD., JAPANFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:FUKUYAMA, MASAYUKI;NAKAYAMA, JUN;MASUDA, KOUJI;REEL/FRAME:022653/0773Effective date: 20090305May 15, 2012CCCertificate of correctionMay 20, 2015FPAYFee paymentYear of fee payment: 4RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services