JP5659894B2 - Software update device, software update method, and software update program - Google Patents

Description

  The present invention relates to a software update apparatus, a software update method, and a software update program for updating software.

  When software for controlling a module that provides a service is updated for some reason such as problem correction, the module usually needs to stop providing the service. However, when continuity is required for service provision 24 hours a day, 365 days, service provision should not be interrupted even when software is updated. Software updates need to be performed safely and reliably while continuing to provide services. As an example of such software, for example, there is control software for a controller of a disk array device represented by RAID (Redundant Arrays of Independent Disks). The disk array device includes, for example, a disk pool configured from a set of magnetic disks such as hard disks. The disk array device uses a logical disk obtained by logically dividing an area on a disk pool, for example, for a business host connected by a network (SAN, Storage Area Network). When the business host operates continuously for 24 hours 365 days, the disk array device needs to provide a logical disk so that the business host can use it continuously for 24 hours 365 days.

  Patent Document 1 discloses an information processing system that automatically and seamlessly replaces a microprogram of an input / output port corresponding to each connection path of a storage apparatus connected to a host computer via two connection paths. Have been described. Each hard disk drive included in the storage device of Patent Document 1 is connected to a plurality of input / output ports.

  The storage device described in Patent Document 1 first notifies the host computer of the start of microprogram replacement via the connection path, and pauses the connection path corresponding to the input / output port that is blocked for microprogram replacement. , Switch to another connection path. When the connection path switching is completed, the storage apparatus exchanges microprograms. The storage apparatus sequentially exchanges the microprograms for the input / output ports that are subject to microprogram exchange.

  Patent Document 2 describes a disk array device that can apply a control firmware of a storage device that constitutes the disk array device even during operation. The disk array device of Patent Document 2 includes a monitoring unit that monitors the access status to each storage device included in the disk array device.

  The disk array device of Patent Document 2 executes application of a control firmware to a designated storage device when the result of monitoring by the monitoring unit satisfies a predetermined condition. The predetermined condition is, for example, the case where there is no access to the storage device for a predetermined period of time, or the case where the access frequency within a predetermined period is equal to or less than a predetermined value.

  Patent Document 3 discloses a storage device that includes a basic housing including a disk device and two controller units (or two enclosures), and updates an expander control program (firmware) included in each controller unit or enclosure. Have been described. The storage device of Patent Document 3 also includes one or more additional enclosures each having a disk device and two enclosures. The expander is an interface between a basic chassis or additional chassis included in the storage apparatus and a disk device or other additional chassis.

  The storage device of Patent Literature 3 updates the firmware of the expander included in the designated controller unit or enclosure based on the instruction of the download method from the management terminal that designates either the controller unit or the enclosure. For example, when the instruction from the management terminal is “execute download when power is turned off by the power saving function”, the storage apparatus updates the firmware when shifting to the power saving mode. When the instruction from the management terminal is “execute download immediately”, the storage apparatus immediately updates the firmware.

  When the instruction from the management terminal is “perform download in consideration of the influence on performance”, the firmware of the expander is updated based on the instruction of the firmware update timing from the management terminal. When the instruction from the management terminal is “execute download at a specified time”, the storage apparatus updates the firmware at the specified time. When the instruction from the management terminal is “execute download immediately”, the storage apparatus immediately updates the firmware. When the instruction from the management terminal is “perform download when I / O (Input / Output) is low”, for example, update the firmware when the IOPS (Input Output Per Second) value is smaller than a predetermined value. Do.

JP 2005-242574 A JP 2009-282834 A JP 2010-061288 A

  In the storage device described in Patent Document 1, the connection path corresponding to the input / output port that is the target of the microprogram replacement is independent of the magnitude of the I / O load on each input / output port when the microprogram is replaced. To pause. In this case, the other input / output ports share the I / O load borne by the input / output ports to be exchanged with the microprogram. However, if the sum of the I / O loads of each input / output port exceeds the sum of the processing capacities of the input / output ports other than the input / output ports to be exchanged with the microprogram, the storage device has a performance degradation such as a delay. May occur or performance degradation may be magnified.

  As a result of monitoring by the monitoring unit, the disk array device of Patent Document 2 is directed to a designated storage device when there is no access to the storage device for a predetermined period of time or when the access frequency within a predetermined period is equal to or less than a predetermined value. Apply the application control farm. However, even if there is no access or the access frequency is less than or equal to a predetermined value within a predetermined time before the application of the control farm, after the application of the control farm is started, there is no access or the access frequency is less than or equal to the predetermined value. Not that. When the access frequency increases after the application of the control firmware starts, performance degradation such as delay may occur in the disk array device, or performance degradation may increase.

  The storage device of Patent Document 3 updates the firmware at the designated time (including immediately) or when the I / O is low when “downloading is performed in consideration of the influence on performance”. However, I / O is not always small at the specified time. Further, even if the number of I / Os is measured, even if the number of I / Os is small, the number of I / Os is not always continued after the start of firmware update. If the I / O increases after the firmware update starts and the processing capacity of the controller or enclosure that has not been updated is exceeded, performance degradation such as delay may occur in the storage device, or the performance degradation will increase. Sometimes.

  An object of the present invention is to provide a software updating apparatus that solves the above problems.

  The software updating apparatus according to the present invention includes a load storage unit that stores load transition data in which a predicted value of a module load is associated with time, update data for software that controls the module, and application of the update data to the software The time required to do this is stored in association with the patch storage means, and the time period in which the total value of the loads falls below the threshold is continued from the load transition data continuously for the required time read from the patch storage means. An update estimation means for extracting and assigning the execution schedule of the software update in the extracted time zone, and based on the execution schedule, stopping the provision of services to the module that is the target of the software update, Update execution means for executing the update.

  In the software update method of the present invention, load transition data in which a predicted value of a module load is associated with time is stored in a load storage unit, the update data for the software that controls the module, and the update data is applied to the software The time required to do is stored in the patch storage means in association with each other, and the time period in which the total value of the loads falls below the threshold is continued from the load transition data continuously from the patch storage means. Extracting and assigning the execution schedule of the software update to the extracted time zone, and based on the execution schedule, stopping the provision of services to the module that is the target of the software update, and executing the software update .

  The software update program according to the present invention includes a load storage unit that stores load transition data in which a predicted value of a module load is associated with a time, update data for software that controls the module, and the software A patch storage unit that stores a required time for applying data in association with each other, and a time zone in which the total value of the loads is less than a threshold continuously for the required time read from the patch storage unit, Update estimate means that extracts from the transition data and allocates the execution schedule of the software update in the extracted time zone, and based on the execution schedule, stops providing the service to the module that is the target of the software update, As an update execution means for executing the update of the software To work.

  The present invention has an effect of reducing the influence of the software update of the module on the service provided by the module.

It is a block diagram showing the structure of 1st Embodiment. It is a block diagram showing the example of a structure of the disk array apparatus containing the controller part which is an example of the module of 1st Embodiment. It is a flowchart showing operation | movement of 1st Embodiment. It is a figure showing the example of the required time of the update which the patch memory | storage part 12 memorize | stores. It is a figure showing the example of the load transition data which the load memory | storage part 11 memorize | stores. It is a block diagram showing the structure of 2nd Embodiment. It is a block diagram showing the example of a structure of the controller part of 2nd Embodiment. It is a flowchart showing the operation | movement at the time of the update execution schedule allocation of 2nd Embodiment. It is a figure showing the 2nd example of the required time of the update which the patch memory | storage part 12 memorize | stores. It is a figure showing the 2nd example of the load transition data which the load memory | storage part 11 memorize | stores. It is a figure showing the example of the result of the allocation of the execution schedule by an update estimation part. It is a flowchart showing the operation | movement at the time of the update execution of 2nd Embodiment.

  Next, embodiments of the present invention will be described in detail with reference to the drawings.

  Each embodiment of the present invention described below can be realized by hardware, a program for controlling the computer and the computer, or a combination of hardware and a program for controlling the computer and the computer.

  FIG. 1 is a block diagram showing the configuration of the first exemplary embodiment of the present invention.

  Referring to FIG. 1, the software update device 1 </ b> A according to the present embodiment includes a load storage unit 11, a patch storage unit 12, an update estimation unit 13, and an update execution unit 14. A module 21A and a module 22A are connected to the update execution unit 14. Note that the number of modules connected to the update execution unit 14 is two in the example illustrated in FIG. 1, but is not limited to two.

  The load storage unit 11 stores load transition data in which a predicted value of the total load of each module by providing a service is associated with a time. The predicted value of the total load may be an average value or an intermediate value at the same time of the total load value calculated from the time series data of the load of each module measured in the past, for example. The load transition data may be data in which an average value or an intermediate value at the same time of the total load value is associated with the time.

  The patch storage unit 12 stores the update data for the software that controls each module and the time required to apply the update data to the software that controls each module in association with each other. In the following description, applying update data to software is expressed as executing update.

  The update estimation unit 13 reads the required time from the patch storage unit 12. The update estimation unit 13 extracts, from the load transition data stored in the load storage unit 11, a time period in which the total predicted load value is lower than a predetermined threshold continuously for the read required time. The update estimation unit 13 assigns a software update execution schedule corresponding to the read required time to the extracted time zone.

  The update execution unit 14 stops providing the service by the module that is the target of the software update when the software update execution start time assigned by the update estimation unit 13 is reached. The update execution means 14 updates the software of the module after stopping the module from providing the service.

  Each module provides some service to, for example, a computing device or a terminal device connected to each module. Each module is controlled by software. Each module is, for example, a controller unit controlled by software in a disk array device represented by RAID. Each module may be a computer in a computer cluster or a controller of a computer network interface. In each embodiment of the present invention, a description will be given of a case where a module is a controller unit that controls I / O of a disk array device.

  FIG. 2 is a block diagram showing a configuration of the disk array device 2A when each module is a controller unit of the disk array device.

  The disk array device 2A includes a controller unit 21 and a controller unit 22 which are the aforementioned modules, and a disk array 23. The disk array 23 includes a disk 231, a disk 232,..., A disk 23N.

  The controller unit 21 and the controller unit 22 are connected to both the business host 3A and the business host 3B, respectively. The controller unit 21 and the controller unit 22 provide a service for reading and writing data recorded in the disk array device to the business host 3A and the business host 3B. In the example of FIG. 2, the controller unit 21 and the controller unit 22 have a redundant configuration, and even if one of them stops, the other operates to continue providing services to the business host 3A and the business host 3B. can do.

  Next, the operation of the present embodiment will be described in detail with reference to the drawings.

  FIG. 3 is a flowchart showing the operation of the software updating apparatus 1A of this embodiment.

  For example, the software update device 1A checks the presence / absence of update data to be applied to the module software every predetermined time, and if there is update data to be applied, the operation of FIG. 3 may be started. The software updating apparatus 1A may start the operation of FIG. 3 according to an instruction from a management host (not shown), for example. In either case, for example, a management host (not shown) may store update data to be applied to the patch storage unit 12 and transmit information specifying the update data to be applied to the software update device 1A.

  Referring to FIG. 3, first, the update estimation unit 13 reads from the patch storage unit 12 the time required to execute the software update associated with the software update data of the module (step S11).

  The patch storage unit 12 may store the required time in the form of a table, for example.

  FIG. 4 is an example of the required time stored in the patch storage unit 12. In the example of FIG. 4, the update data name is associated with the required time.

  The update data and the required time may be stored in advance in the patch storage unit 12 by a management host (not shown), for example. The update data may be a patch set in which a plurality of update data are combined into one. When the update data is a patch set, the required time is the time required to apply all the update data included in the patch set to the software. The patch storage unit 12 may store the required time corresponding to the patch set. Further, the update estimation unit 13 reads out the required time corresponding to each update data included in the patch set from the patch storage unit 12, for example, the longest required time among the required times is set as the required time of the patch set, etc. The time required for the patch set may be calculated by an existing method.

  Next, the update estimation unit 13 extracts a time period in which the total load is below the threshold value from the load transition data stored in the load storage unit 11 for more than the time required for software update (step S12).

  The load storage unit 11 may store the load transition data in the form of a table, for example.

  FIG. 5 is a diagram illustrating an example of load transition data. In the example of FIG. 5, the load transition data is a total value of loads at intervals of 10 seconds.

  The load transition data is a total value of loads of each module, for example, expressed in IOPS, for example, at a predetermined time interval associated with the time. The value indicating the magnitude of the load may be an existing arbitrary value. IOPS is the number of I / Os per second.

  The time interval of the load transition data is arbitrary, and may be 1 second, 10 seconds, 1 minute, or any other time. Also, the amount of load transition data stored in the load storage unit 11 is arbitrary, whether it is for one day, one month, one year, or any other amount. Also good. The total load value included in the load transition data may be a statistic such as an average or median value of the total load of each module measured at the same time.

  The threshold value for the total load value should be the appropriate total load value that will not adversely affect the provided services even if all the loads other than the modules that are subject to software updates are burdened. Any selected value may be used. The threshold value may be a value obtained by subtracting a margin for safety from a total load value that does not affect the service to be provided in calculation.

  Next, the update estimation unit 13 assigns the execution schedule of the software update in which the update data corresponding to the read required time is applied to the software to the extracted time zone (step S13).

  In addition, when applying the same update with respect to the software of several modules, what is necessary is just to repeat the process of step S12 and step S13 until there is no module which has not applied the update. If there are a plurality of update data to be applied, the processes in steps S12 and S13 may be repeated until there is no update data to which no update execution schedule is assigned.

  The update execution unit 14 does nothing until the update start time in the update schedule assigned by the update estimation unit 13 is reached (step S14, N).

  When the update start time assigned in the update schedule assigned by the update estimation unit 13 is reached (Y in step S14), the update execution unit 14 causes the module to be updated of software to stop providing the service (step S15). .

  Note that the update execution unit 14 may check whether there is a module that is operating normally in addition to the module that is the target of the software update before the module that is the target of the software update stops providing the service. Good. If there is no module that is operating normally other than the module that is the target of the software update, the update execution unit 14 may continue to provide the service to the module that is the target of the software update. In this case, the software update device 1A may stop updating the software. In addition, when there is a module that is operating normally in addition to the module that is the target of the software update, the update execution unit 14 may stop providing the service to the module that is the target of the software update.

  When each module is a controller unit of the disk array device, the update execution unit 14 performs processing necessary to change the data transfer path so that the data transfer does not pass through the controller unit that is the target of software update. May be appropriately performed. Each path is a connection for data transfer between each controller unit and each business host.

  Next, the update execution unit 14 reads the update data from the patch storage unit 12, and updates the software by applying the read update data to the software of the module to be updated (step S16). .

  After completing the software update, the update execution unit 14 causes the module that was the target of the software update to resume providing the service (step S17).

  When each module is the controller unit of the disk array device, the update execution unit 14 changes the data transfer path so that the data transfer is appropriately performed via the controller unit that is the target of the software update. The processing necessary for the above may be performed as appropriate.

  Next, the effect of this embodiment will be described.

  The present embodiment has an effect of reducing the influence of updating the software of the module on the service provided by the module.

  The reason is that a time zone in which the total load continues below the threshold for software update is extracted from the load transition data stored in the load storage unit 11, and an execution schedule for software update is assigned. is there. The threshold for the total load is a value that is selected so that even if all the loads other than the module that is the target of software update bear the load, the service provided by each module is not affected by delay or the like. Therefore, the software update device 1A of the present embodiment can reduce the influence of delays on services provided by each module while the update execution unit 14 is updating software.

  In the above description, it is assumed that a plurality of modules exist in a redundant configuration. However, the module may not have a redundant configuration and may not have a plurality. In that case, the load storage unit 11 may store the load for each module in association with the time. Further, the update estimation unit 13 extracts a time zone whose length is equal to or longer than the time required for software update and in which the load of the module to be updated is lower than a predetermined threshold. Further, the module stops providing the service while the update execution unit 14 updates the software. However, since the update estimation unit 13 extracts a time zone in which the load of the module to be updated is below a predetermined threshold, the influence of the module software update on the service provided by the module is reduced. can do.

  Next, a second embodiment of the present invention will be described in detail with reference to the drawings.

  FIG. 6 is a block diagram showing the configuration of the present embodiment.

  Referring to FIG. 6, the present embodiment includes a software update device 1, a disk array device 2, a business host 3 </ b> A and a business host 3 </ b> B, and a management host 4. In FIG. 6, the software update device 1 and the disk array device 2 are separate devices, but the disk array device 2 may include the software update device 1.

  The software update device 1 includes a threshold storage unit 15 in addition to the configuration of the software update device 1A shown in FIG. Further, the software update device 1 may include a load monitoring unit 16. In this embodiment, the module that is the target of software update is each controller unit of the disk array device 2.

  The update execution unit 14 outputs an instruction to switch the data transfer path so that the software update execution start time assigned by the update estimation unit 13 does not pass through the controller unit to be updated. . The output destination of this instruction is a path switching unit 25 of the disk array device 2 described later. The update execution unit 14 outputs an instruction to switch the path and then updates the software of the controller unit.

  The threshold storage unit 15 stores a threshold for the total load value in association with the time. The threshold value stored in the threshold value storage unit 15 may be a different value depending on the time. For example, the management host 4 may store the threshold associated with the time in the threshold storage unit 15 in advance.

  The load monitoring unit 16 measures the load of each controller, for example, every predetermined time. The load monitoring unit 16 may calculate, for example, a statistical value such as an average from a load measurement value at the same time in a predetermined period in the past, and calculate a predicted value of the total load for each time. The load monitoring unit 16 may store the calculated predicted value in the load storage unit 11 as needed. The load monitoring unit 16 determines whether or not the controller unit can be disabled without causing a delay in the response from the disk array device 2 based on the measured value of the load at the same time in the past predetermined period. A threshold value may be calculated. The calculation method in this case may be any existing method. The load monitoring unit 16 may store the calculated threshold in the threshold calculation unit 12 as needed.

  The other components of the software update device 1 of the present embodiment are the same as the components having the same symbols in the first embodiment, and a description thereof will be omitted.

  The disk array device 2 includes a controller unit 21 and a controller unit 22, a disk array 23, a path state registration unit 24, and a path switching unit 25.

  The controller unit 21 and the controller unit 22 of the disk array device 2 are connected to respective business hosts. Each controller can communicate with each business host. Each controller and each business host are connected via, for example, a SAN (Storage Area Network) network.

  The controller unit 21 and the controller unit 22 control reading / writing and transfer of data with respect to the disk array 23. The controller unit 21 and the controller unit 22 have a redundant configuration. Further, there may be three or more controller units. Each controller unit is controlled by software.

  FIG. 7 is a diagram illustrating an example of the configuration of software that controls the controller unit 21. The configuration of the other controller units is the same as that of FIG. The configuration of the controller unit is not limited to the configuration of FIG.

  Referring to FIG. 7, the controller unit 21 is controlled by software operating in the execution environment 211. In the example of FIG. 7, there are three types of software in the execution environment 211: management SW (Software), RAID control (RAID control driver), and OS (Operation System). The backup environment 212 is a copy of the execution environment 211.

  The disk array 23 stores data that each business host reads and writes via each controller unit.

  The path status registration unit 24 stores a path status indicating whether or not a path between each controller and each business host is valid. Further, the path status registration unit 24 receives the path status from the path management unit 31 of each business host, which will be described later, and changes the stored path status.

  Based on an instruction from the update execution unit 14, the path switching unit 25 changes each controller unit to a state where it cannot be used from each business host. Further, the path switching unit 25 changes each controller unit to a state where it can be used from each business host based on an instruction from the update execution unit 14.

  FIG. 6 shows two business hosts, the business host 3A and the business host 3B, but the number of business hosts is not limited to two. Each business host includes a path management unit 31. Each business host is simultaneously connected to each controller, and reads and writes data stored in the disk array 23 via each controller unit.

  The path management unit 31 monitors whether or not a path between each controller unit is available. For example, the path management unit 31 may perform monitoring by periodically checking whether or not an I / O error has occurred in each controller unit. If there is a controller unit that cannot be used, the path management unit 31 prohibits the use of the path between the business host and the controller unit. Further, the path management unit 31 permits the use of the path between the business host and the controller unit when the unusable controller unit becomes available.

  For example, as shown in FIG. 6, when the disk array device 2 and the business host 3A are connected and each controller is operating normally, the controller unit 22 and the business host 3A, and the controller unit 22 and the business host 3A are connected. Two paths between are available. From this state, for example, when the path switching unit 25 disables the controller unit 21, the path management unit 31 detects the occurrence of an I / O error for the controller unit 21 and uses the path to the controller unit 21. Disable. In this way, so-called misalignment is performed in which the path state is switched from a state where two paths are available to a state where only one path is possible.

  Further, when each device has a configuration as shown in FIG. 6 and the path switching unit 25 switches the controller unit 21 from an unusable state to an available state, the path management unit 31 makes an I / O to the controller unit 21. Detect that no O error occurs. The path management unit 31 that has detected that no I / O error occurs makes the path to the controller unit 21 available.

  The path management unit 31 causes the path status registration unit 24 of the storage apparatus 2 to store the status of each path obtained as a result of monitoring via any path between the business host and the storage apparatus 2.

  Note that the path switching described above is merely an example. The disk array device 2 and each business host can perform path switching by an existing arbitrary method.

  The management host 4 includes an update instruction unit 41.

  The update instruction unit 41 stores the update data and the required time in the patch storage unit 12. The update instruction unit 41 may transmit an instruction to assign an execution schedule for software update to the update estimation unit 13.

  Next, the operation of the software update device 1 of the present embodiment will be described in detail with reference to the drawings.

  FIG. 8 is a flowchart showing the operation of assigning the execution schedule of the update in the software update device 1 of this embodiment. For example, the software update device 1 receives information specifying update data to be applied from the update instruction unit 41 and starts the following operation.

  Referring to FIG. 8, first, the update estimation unit 13 reads the required update time associated with the update data applied to the software of each controller unit from the patch storage unit 12 (step S21).

  The patch storage unit 12 can also store the required time in association with information about the corresponding update data, for example, in the form of a table.

  FIG. 9 is an example of a table that includes information related to required time and corresponding update data stored in the patch storage unit 12. The table of FIG. 9 shows the type of software to be updated, the module name to be updated, the restart type including the necessity of restart after update, the required time, and the path switching at the time of update. Includes necessity.

  The type represents the type of control software to which the patch is applied. The types include, for example, the management software, the RAID control driver, and the OS described above. The software module name is a name for identifying a software module constituting the software. The restart type indicates whether restart is not necessary after execution of update, or if restart is necessary, whether fast restart is possible after restart. The fast restart is a restart that does not execute, for example, POST (Power On Self Test). When the restart type is “none”, restart after execution of update is not necessary. When the restart type is "Fast", restart is required after applying the patch, but fast restart is possible. When the restart type is “normal”, a normal restart is required after applying the patch.

  The required time is the time required from the start of the update until the controller unit becomes operational again. The required time may be an approximate estimate of the required time estimated appropriately. In the example of FIG. 9, when the restart type is “none”, the required time is 0 seconds. When the restart type is “high speed”, the required time is 10 seconds. When the restart type is “normal”, the required time is 600 seconds to 700 seconds.

  The necessity of switching indicates whether or not path switching is required when executing update. The necessity of switching may be determined in advance depending on, for example, whether the required time is greater than or equal to a predetermined threshold or less. If the controller part that can be used from each business host becomes unusable continuously, this threshold is set in advance to the time that is considered to affect the processing that is being performed on each business host after it becomes unavailable. Just set it up. The necessity of switching in FIG. 7 is an example when the threshold is 10 or more and less than 600.

  Note that the patch storage unit 12 need not store the necessity of switching corresponding to each update data. When the patch storage unit 12 does not store the necessity of switching, the update estimation unit 13 may determine whether or not the path needs to be switched by comparing the required time with a threshold value in step S22 described later. In step S32 described later, the patch execution unit 14 may use the determination result as it is as to whether or not the update estimation unit 13 needs to switch the path. Alternatively, the patch execution unit 14 may determine whether it is necessary to switch paths by comparing the required time with a threshold value.

  The patch storage unit 12 stores not only the time required for individual update data and information related to the update data, but also information such as the time required for a patch set in which a plurality of update data is collected in association with the patch set. Good.

  Next, the update estimation unit 13 determines whether or not it is necessary to switch paths when applying update data (step S22).

  When applying the single update data, the update estimation unit 13 may determine whether or not to switch the path based on the data indicating whether or not to switch the update data to be applied, read from the patch storage unit 12. When a patch set is applied to software, if the patch storage unit 12 stores data on whether or not the patch set needs to be switched, the update estimation unit 13 determines whether or not the path needs to be switched based on the data. do it. When the patch storage unit 12 does not store the data indicating whether the patch set needs to be switched or not, the update estimation unit 13 needs to switch the path if the patch set includes update data that needs to be switched. Can be determined.

  When the path switching is not necessary (step S23, N), the update execution unit 14 may execute the update immediately (step S27). The execution of the update will be described later.

  When path switching is required (step S23, Y), the update estimation unit 13 continues the load required time for the update, and the load transition unit in which the load storage unit 11 stores a time zone in which the total load value is below the threshold value. Extract from the data (step S24).

  The update estimation unit 13 may read the update required time from the patch storage unit 12.

  FIG. 10 is a diagram illustrating an example of load transition data stored in the load storage unit 11. The load transition data may include at least the transition of the total load value. The load value stored in the load storage unit 11 is, for example, IOPS.

  Further, the update estimation unit 13 may read the threshold value for the total load value from the threshold storage unit 15. As described above, the threshold value stored in the threshold value storage unit 15 may vary with time. In this case, for example, an administrator of the disk array device 2 may store a threshold value appropriately determined according to time in the threshold value storage unit 15 in advance. The threshold value stored in the threshold value storage unit 15 may be a value corresponding to the magnitude of the variation in the load value observed, for example, by the load monitoring unit 16 at the same time in the past. The threshold value stored in the threshold value storage unit 15 is, for example, a value corresponding to the magnitude of the variation in the observed load value at each time from the total load value that does not affect the service provided in the calculation. It may be a subtracted value. In this case, the threshold value at the time when the variation in the observed value of the load is large is small, and the threshold value at the time of the small variation in the observed value of the load is large.

  FIG. 11 is a diagram illustrating the time period extracted by the update estimation unit 13. The update estimation unit 13 can generate a table as shown in FIG. 11 and extract a time zone. “Load threshold” in FIG. 11 is a threshold stored in the threshold storage unit 15. The “predicted load value” is a total load value stored in the load storage unit 11. The update estimation unit 13 extracts a time period in which the “predicted load value” is smaller than the “load threshold” and the “difference” is positive. The time zone extracted by the update estimation unit 13 in FIG. 11 is a time zone in which the execution availability is “OK”.

  When there is no time zone that meets the conditions (N in step S25), the software update device 1 ends the process without performing update or assigning an update execution schedule. In this case, for example, the administrator of the disk array device 2 may perform the update manually.

  If there is a time zone that meets the conditions (step S25, Y), the update execution unit 14 performs the update if the current time zone is present and an immediate update can be performed (step S26, Y). (Step S27).

  When the time zone suitable for the condition is not present and the immediate update cannot be executed (step S26, N), the update estimation unit 13 assigns an update execution schedule (step S28). In this case, the update execution unit 14 may execute the update as described below at the scheduled update execution time.

  Next, the operation of this embodiment at the time of update execution will be described.

  FIG. 12 is a flowchart showing the operation of this embodiment at the time of execution of update. Note that the software update device 1 may stop executing the update if the total load value at the scheduled update execution time measured by the load monitoring unit 16 is greater than the threshold at the same time stored in the threshold storage unit 15. Good. In that case, the software update apparatus 1 may perform the above-described update execution schedule assignment again.

  Referring to FIG. 12, the update execution unit 14 reads patch information including information corresponding to the update data, such as update data and required time, from the patch storage unit 12 (step S31).

  Next, the update execution unit 14 determines, for example, from the read patch information whether or not it is necessary to switch the path when the update is executed (step S32). The update execution unit 14 may receive from the update estimation unit 13 whether or not it is necessary to switch paths when executing the update.

  When path switching is not necessary (step S33, N), the update execution unit 14 performs update (step S38).

  When it is necessary to switch the path (step S33, Y), the update execution unit 14 checks whether the path between the disk array device 2 and all the business hosts is normal (step S34). In step S <b> 34, the update execution unit 14 may confirm whether or not there is a normal path with all the business hosts when the controller unit to be updated with software is stopped. The update execution unit 14 may confirm whether all the paths between each controller unit and each business host are normal.

  The update execution unit 14 may perform the confirmation in step S34 by receiving the status of each path from the path status registration unit 24 of the storage device 2, for example.

  If there is a business host whose path is not normal (step S34, N), the software updating apparatus 1 ends the process.

  When there is no business host whose path is not normal (step S34, Y), the update execution unit 14 transmits an instruction to the path switching unit 25 to switch the path (step S35). The path switching unit 25 that has received the path switching instruction from the update execution unit 14 may make all the paths between the controller unit that is the target of the software update and each business host unavailable.

  The update execution unit 14 performs the update after switching the path (step S36).

  After executing the update, the update execution unit 14 transmits an instruction to the path switching unit 25 to recover the path (step S37). The path switching unit 25 that has received the path restoration instruction from the update execution unit 14 may make all paths between the controller unit that updated the software and each business host available again.

  In the present embodiment described above, in addition to the effects of the first embodiment, the software of the controller unit can be used for the service provided by the controller unit even when the load at the same time varies. This has the effect of reducing the impact of updates.

  The reason is that, when assigning an update execution schedule, the update estimation unit 13 compares the threshold value whose value fluctuates with time and the total load value. For example, by reducing the threshold value at the time when the load variation is large and increasing the threshold value at the time when the load variation is small, the time when the predicted load value is small but a large load fluctuation can occur You can avoid performing band updates. Thus, for example, it is possible to reduce the occurrence of an influence due to the software update of the controller unit, such as a delay caused by a sudden increase in load during the execution of the update.

  The present invention has been described above with reference to the embodiments, but the present invention is not limited to the above embodiments. Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

1, 1A Software update device 2, 2A Disk array device 3A, 3B Business host 4 Management host 11 Load storage unit 12 Patch storage unit 13 Update estimation unit 14 Update execution unit 15 Threshold storage unit 16 Load monitoring unit 21, 22 Controller unit 21A 22A module 23 disk array 24 path state registration unit 25 path switching unit 31 path management unit 41 update instruction unit 211 execution environment 212 backup environment

Claims (7)

Load storage means for storing load transition data in which a predicted value of the total load of each of a plurality of modules having a redundant configuration is associated with time;
Patch storage means for storing, in association with each other, update data for the software that controls the module, and a time required for applying the update data to the software, provided in each of the modules ;
The time period in which the total predicted value of the load is lower than a threshold value is continuously extracted from the load transition data continuously for the required time read from the patch storage unit, and at least one module in normal operation is excluded. a plurality of modules, select the module, the extracted the time zone, and updates estimates means for assigning the execution schedule of updates of the software to the selected modules,
A software update device comprising: an update execution unit configured to stop the provision of a service to the module to be updated of the software based on the execution schedule and to update the software. Load threshold storage means for storing the threshold corresponding to the time in association with the time,
The update estimation unit compares the total predicted value of the load corresponding to the same time with the threshold value read from the load threshold storage unit, and the time period when the total predicted value of the load is lower than the threshold value Extract
The software updating apparatus according to claim 1 . An information processing system including the module and the software updating apparatus according to claim 1 . Storing load transition data in which the predicted value of the total load of each of a plurality of modules having a redundant configuration is associated with time in the load storage means;
Each of the modules, the update data for the software that controls the module and the time required to apply the update data to the software are stored in the patch storage unit in association with each other,
The time period in which the total predicted value of the load is lower than a threshold value is continuously extracted from the load transition data continuously for the required time read from the patch storage unit, and at least one module in normal operation is excluded. a plurality of modules, select the module, the extracted said time period, allocates a scheduled execution of the update of the software to the selected modules,
A software update method for executing an update of the software by stopping the provision of a service to the module to be updated of the software based on the execution schedule. Storing the threshold according to time in the load threshold storage means in association with the time;
The total predicted value of the load corresponding to the same time is compared with the threshold value read from the load threshold storage unit, and a time zone in which the total predicted value of the load is lower than the threshold value is extracted.
The software update method according to claim 4 . Computer
Load storage means for storing load transition data in which a predicted value of the total load of each of a plurality of modules having a redundant configuration is associated with time;
Patch storage means for storing, in association with each other, update data for the software that controls the module, and a time required for applying the update data to the software, provided in each of the modules ;
The time period in which the total predicted value of the load is lower than a threshold value is continuously extracted from the load transition data continuously for the required time read from the patch storage unit, and at least one module in normal operation is excluded. a plurality of modules, select the module, the extracted the time zone, and updates estimates means for assigning the execution schedule of updates of the software to the selected modules,
A software update program that operates as an update execution unit that stops the provision of a service to the module that is a target of the software update and executes the software update based on the execution schedule. Computer
Load threshold storage means for storing the threshold according to time in association with the time;
The update estimate that compares the total predicted value of the load corresponding to the same time with the threshold value read from the load threshold storage unit, and extracts a time zone in which the total predicted value of the load is less than the threshold value The software update program according to claim 6, which is operated as a means.

Images