JP2007233940A - Patch application control method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a patch application control method for shortening a disabled period of a computer to which a patch is applied. <P>SOLUTION: The patch application control method by which a first computer applies a patch to a program stored in a recording medium related to a second computer comprises: a first copying procedure in which the first computer copies record contents of the recording medium related to the second computer to a recording medium related to a third computer different from the second computer; a patch application procedure in which the third computer applies a patch to record contents copied to the recording medium related to the third computer; a determination procedure in which the third computer determines the success of failure of patch application; and a second copying procedure in which the first computer copies the record contents of the recording medium related to the third computer to the recording medium related to the second computer when the patch application is successful. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a patch application control method, and more particularly to a patch application control method in which a first computer applies a patch to a program stored in a recording medium related to a second computer.

  When a problem is found in the computer system, the program module that causes the problem is corrected, and the corrected program module is released again. Here, the corrected program module is generally referred to as a patch, and applying the program module to the computer system is referred to as “applying a patch”.

  Programs in recent computer systems have been modularized, and it is possible to solve the problem by replacing only a part (patch application) without replacing the entire system.

Since the problem can be solved by the patch, the efficiency of the maintenance work can be improved, such as the need to test the entire system again.
JP 2003-15894 A

  However, in order to apply a patch, it is necessary to temporarily disconnect the computer from the network, and it is still necessary to confirm the operation of the function related to the patch after applying the patch. Conventionally, a task for applying a patch has been performed manually by a system administrator or the like. Under such circumstances, in order to apply a patch, a business server in a company cannot be used for a long time, which sometimes hinders business.

  The present invention has been made in view of the above points, and an object of the present invention is to provide a patch application control method capable of shortening the unusable period of a computer to which a patch is applied.

  In order to solve the above problems, the present invention provides a patch application control method in which a first computer applies a patch to a program stored in a recording medium related to a second computer, the first computer However, the first copy procedure for copying the recording contents of the recording medium related to the second computer to a recording medium related to a third computer different from the second computer, and the third computer A patch application procedure for applying the patch to the recorded content copied to a previous recording medium according to a third computer, a determination procedure for determining whether the application of the patch is successful, or the third computer; When the patch application is successful, the first computer reads the recorded content of the recording medium related to the third computer. And having a second copy procedure for copying the recording medium according to the second computer.

  With such a patch application control method, it is possible to shorten the unusable period of the computer to which the patch is applied.

  ADVANTAGE OF THE INVENTION According to this invention, the patch application control method which can shorten the unusable period of the computer to which a patch is applied can be provided.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram illustrating a configuration example of a patch application system according to an embodiment of the present invention. 1, the patch application system 1 includes a management server 10, a business server 20, a patch application server 30, a RAID (Redundant Array of Independent Disks) device 40, and the like.

  The management server 10 is a computer that controls patch application work to the business server 20 and includes a patch application manager 11. The patch application manager 11 is a program that controls patch application processing.

  The business server 20 is a server computer in various business systems in a company, and is a patch application target in the present embodiment. The business server 20 has an agent 21. The agent 21 is a program for executing power ON / OFF of the business server 20 based on an instruction from the patch application manager 11. In FIG. 1, only one business server 20 is displayed, but a plurality of business servers 20 may exist.

  The patch application server 30 is a computer used for a patch application test, and includes a patch application agent 31. The patch application agent 31 is a program for executing processing for applying a patch to the patch application server 30 based on an instruction from the patch application manager 11.

  That is, in the present embodiment, it is confirmed that the patch application server 30 does not apply a patch suddenly, but the patch application server 30 first applies the patch normally. The patch application server 30 is prepared for each hardware and software architecture of the business server 20 (model of the patch application server 30, type of OS (Operating System) installed in the patch application server 30, etc.). There is a need.

  The RAID device 40 is a so-called RAID device and serves as a storage (recording medium) for various business servers 20. The RAID device 40 includes storage areas such as a system volume (system volume) 42 of the business server 20, a patch test volume 43 (for example, a system volume of the patch application server 30), a backup volume 44, and the like. Is secured. The sysbol 42 stores the OS and boot program of the business server 20. In this embodiment, a case where a patch is applied to the OS in the sysbol 42 of the business server 20 is taken as an example. However, an application volume of the business server 20 (a storage area in which application programs and the like are stored) may be secured in the RAID device 40, and the application volume may be a patch application target. The access path between the disk of the RAID device 40 and the business server 20 and the patch application server 30 is defined in advance.

  The RAID device 40 is also provided with a RAID device management unit 41. The RAID device management unit 41 is a program for managing disks in the RAID device 40.

  By the way, each server in the patch application system 1 is connected by any one of three LANs (whether wired or wireless) such as a business LAN (Local Area Network) 51, a management LAN 52, and a test LAN 53. Has been.

  The business LAN 51 is a LAN used for using the business server 20 in normal business. Therefore, only the business server 20 is connected among the three servers. The management LAN 52 is a LAN used for communication for performing patch application processing. Therefore, the management server 10, the business server 20, and the patch application server 30 are connected. The test LAN 53 is a LAN used for performing a confirmation test when a patch is applied to the patch application server 30. Therefore, only the patch application server 30 is connected.

  Since the management LAN 52 is provided separately from the business LAN 51, it is possible to prevent the load due to the patch application work from reaching the business LAN 51, and security in the business LAN 51 is ensured. In addition, since the test LAN 52 is provided separately from the business LAN 51 and the management LAN 52, the patch application server 30 can be operated on the test LAN 52 with the same IP address as the business LAN 51. That is, the patch application server 30 can be operated under exactly the same conditions as the business server 20.

  FIG. 2 is a diagram illustrating a hardware configuration example of the management server in the embodiment of the present invention. The management server 10 in FIG. 2 includes a drive device 100, an auxiliary storage device 102, a memory device 103, an arithmetic processing device 104, an interface device 105, a display device 106, which are connected to each other via a bus B. And an input device 107.

  A program such as a patch application manager 11 that implements processing in the management server 10 is provided by a recording medium 101 such as a CD-ROM. When the recording medium 101 on which the program is recorded is set in the drive device 100, the program is installed from the recording medium 101 to the auxiliary storage device 102 via the drive device 100. The auxiliary storage device 102 stores the installed program and also stores necessary files and data. However, the program need not be installed from the recording medium 101 and may be downloaded from another computer via a network.

  The memory device 103 reads the program from the auxiliary storage device 102 and stores it when there is an instruction to start the program. The arithmetic processing unit 104 realizes functions related to the management server 10 in accordance with a program stored in the memory device 103. The interface device 105 is used as an interface for connecting to a network. The display device 106 displays a GUI (Graphical User Interface) or the like by a program. The input device 107 includes a keyboard and a mouse, and is used for inputting various operation instructions.

  The business server 20 and the patch application server 30 also have a hardware configuration as shown in FIG. However, the display device 106 and the input device 107 are not necessarily required for the business server 20 and the patch application server 30.

  Hereinafter, the processing procedure of the patch application system 1 of FIG. 1 will be described.

  FIG. 3 is a flowchart for explaining the processing procedure of the patch application system according to the first embodiment.

  In step S101, a user such as a system administrator registers a patch, a shell script for confirming the operation of the patch, patch application schedule information, and the like in the patch application manager 11 of the management server 10. The registration of the schedule information is performed, for example, via a screen as shown in FIG. 4 that is displayed on the display device 106 by the patch application manager 11.

  FIG. 4 is a diagram showing an example of a screen for registering schedule information. In the schedule information registration screen 600 of FIG. 4, for each business server 20 (Server1, Server2, Server3, Server4, etc.), the recorded contents of the sysbol 42 of the business server 20 are stored in the patch test volume 43 and the backup volume of the patch application server 30. It is possible to set a time for duplicating the copy to both volumes 44 (hereinafter referred to as “copy execution time”) and a time for applying a patch to the sysbol 42 (hereinafter referred to as “patch application time”). . For example, in FIG. 4, for “Server 1”, the copy execution time is set to 10:00 and the patch application time is set to 13:00.

  As will be described later, at the copy execution time and the patch application time, the business server is turned off or on. Therefore, the user may select a time zone having a small influence on the business and set the copy execution time and the patch application time.

  For the patch application time, information for identifying the patch to be applied (hereinafter referred to as “patch ID”) is also set as attribute information. In FIG. 4, “R101111” corresponds to the patch ID.

  When the registration work by the user is completed, the patch application manager 11 waits until the copy execution time registered as schedule information. When the arrival of the copy execution time is detected, the patch application manager 11 turns off the power of the business server 20 (S102). More specifically, the patch application manager 11 transmits a power OFF command to the agent 21 of the business server 20 via the management LAN 52. The agent 21 that has received the power OFF command turns off the power of the business server 20. Therefore, at this time, the business server 20 is stopped and becomes unusable.

  Subsequently, the patch application manager 11 duplicates the recorded contents of the sysbol 42 of the business server 20 to both the patch test volume 43 and the backup volume 44 of the patch application server 30 (S103). This process will be described in detail with reference to FIG.

  FIG. 5 is a diagram for explaining the processing procedure of the double copy of the system volume of the business server.

  First, the patch application manager 11 designates identifiers of the copy source sysvol 42 and the copy destination patch test volume 43 and backup volume 44 and instructs the RAID device management unit 41 to make a double copy of the sysbol 42. (S1031). The RAID device management unit 41 identifies the copy source or destination sysvol 42, patch test volume 43, and backup volume 44 based on the specified identifier, and executes double copy (S1032, S1033). Therefore, in the management server 10, for each business server 20, the identifier of the system volume and the identifiers of the patch test volume 43 and the backup volume 44 of the patch application server 30 corresponding to the architecture are registered in advance. There is a need. In FIG. 5, the schedule information 12, the patch 13, and the shell script 14 registered in step S101 are displayed in the management server 10.

  Incidentally, the double copy in steps S1032 and S1033 is performed at a high speed because it is executed in a snapshot manner in the RAID device 40. Further, since the business server 20 is powered off, copying is performed in a state where the system volume 42 is clean, that is, a state where no update of a file or the like occurs. Accordingly, the same contents as the contents of the sysbol 42 are created in the patch test volume 43 and the backup volume 44.

  Subsequently, the patch application manager 11 activates the business server 20 (S104). More specifically, the patch application manager 11 transmits a power ON command to the agent 21 of the business server 20 via the management LAN 52. The agent 21 that has received the power ON command turns on the power of the business server 20. Therefore, at this time, the stopped state of the business server 20 is released, and the business server 20 can be used.

  Subsequently, the patch application manager 11 activates the patch application server 30 (S105). More specifically, the patch application manager 11 transmits a power ON command to the patch application agent 31 of the patch application server 30 via the management LAN 52. The patch application agent 31 that has received the power ON command turns on the power of the patch application server 30.

  Subsequently, the patch application manager 11 applies the patch 13 to the patch test volume 43 of the patch application server 30 (S106). This process will be described in detail with reference to FIG.

  FIG. 6 is a diagram for explaining a patch application processing procedure for the patch application server.

  First, the patch application manager 11 transfers the registered patch 13 and shell script 14 to the patch application agent 31 of the patch application server 30 via the management LAN 52 (S1061). The patch application agent 31 applies the received patch 13 to the patch test volume 43 (S1062), and automatically executes the shell script 14 to confirm the success or failure of the patch application (S1063). The success or failure of patch application is performed, for example, by confirming version information of a program to which the patch is applied. That is, if the version information is updated, it is determined that the patch application is successful. Further, it is also possible to confirm the operation of the function related to the patch and determine the success or failure of the patch application based on the operation result. Thereafter, the patch application agent 31 transmits result information indicating the success or failure of the patch application to the patch application manager 11 via the management LAN 52 (S1064).

  Returning to FIG. Subsequently, the patch application manager 11 turns off the power of the patch application server 30 (S107). More specifically, the patch application manager 11 transmits a power OFF command to the patch application agent 31 of the patch application server 30 via the management LAN 52. The patch application agent 31 that has received the power OFF command turns off the power of the patch application server 30.

  Subsequently, when the result information returned from the patch application agent 31 indicates that the application of the patch to the patch application server 30 has failed (No in S108), the patch application manager 11 performs the process of FIG. Terminate. That is, in this case, the patch is not applied to the business server 20.

  On the other hand, when the result information indicates that the patch application to the patch application server 30 is successful (Yes in S108), the patch application manager 11 waits until the patch application time registered as the schedule information (S109). ). When the arrival of the copy execution time is detected, the patch application manager 11 turns off the power of the business server 20 in the same manner as in step S102 (S110).

  Subsequently, the patch application manager 11 copies the recorded contents of the patch test volume 43 to the sysbol 42 (S111). This process will be described in detail with reference to FIG.

  FIG. 7 is a diagram for explaining a processing procedure for patch application to a business server.

  First, the patch application manager 11 specifies the identifiers of the copy-source patch test volume 43 and the copy-destination sysbol 42, and copies the patch test volume 43 to the sysbol 42 to the RAID device management unit 41. Instruction is given (S1111). The RAID device management unit 41 identifies the patch test volume 43 and the sysbol 42 that are the copy source or the destination based on the specified identifier, and executes the copy (S1112). Note that the copy in step S1112 is performed at high speed because it is executed in a snapshot manner in the RAID device 40.

  Subsequently, the patch application manager 11 starts up the business server 20 (turns on the power) in the same manner as in step S104. If the activation fails, the patch application manager 11 copies the contents of the backup volume 44 to the system volume 42 to restore the contents of the system volume 42 to the state before the patch application (S104, S1041 in FIG. 7). As a result, the occurrence of a fatal failure in the business server 20 can be avoided.

  On the other hand, if the activation is successful, and if the schedule for patch application for the other business server 20 is registered in the schedule information 12, the processing from step S102 onward for the other business server 20 is repeated (S115).

  Note that the patch application manager 11 may cause the display device 106 to display a result of success or failure of patch application to the patch application server 30 or the business server 20. FIG. 8 is a diagram illustrating a display example of the patch application result.

  In the display example of FIG. 8, for “Server1”, the patch application to the patch application server 30 (patch_server) was successful (701), and the patch application to the business server 20 (“Server1”) was also successful. (702). On the other hand, for “Server2”, it is indicated that the patch application to the patch application server 30 (patch_server) has failed (703).

  As described above, according to the patch application system 1 in the first embodiment, the user can automatically apply the patch to the business server 20 only by registering the schedule information. In addition, since patch application is executed in a test using the patch application server 30, the period during which the business server 20 is stopped is shortened between steps S102 to S104 and between steps S110 to S112. In addition, the necessity of disconnecting the business server 20 from the business LAN 51 can be reduced.

  By the way, the reason why the business server 20 is stopped during steps S102 to S104 is to keep the sysbol 42 of the business server 20 not updated during the double copy. However, even if the sysbol 42 is copied while the business server 20 is running, the file check function provided by the OS of the patch application server 30 maintains the consistency of the file being updated during the copy execution. It can be drunk. Therefore, it is not always necessary to stop the business server 20 in steps S102 to S104.

  FIG. 9 is a flowchart for explaining the processing procedure of the patch application system when the business server is not stopped in the case of double copying. 9, the same steps as those in FIG. 3 are denoted by the same step numbers, and the description thereof is omitted.

  In FIG. 9, the steps indicated by broken lines are not necessary. Therefore, it is possible to further reduce the stop period of the business server 20 and to reduce the time required for the entire patch application process.

  By the way, in a place where a large number of business servers are managed, such as a data center, each business server 20 is generally composed of the same OS. When applying an OS patch in such a case, it is efficient if the patch test volume 43 after patch application can be copied to all servers after performing the application test only once on the patch application server 30.

  However, in addition to the OS, the sysbol 42 stores information unique to each business server 20 such as an IP address (unique information). Therefore, the patch test volume 43 created based on the replication of one business server 20 cannot be copied and used as it is to the business server 20 different from the business server 20.

  Therefore, an example in which such a problem is solved will be described as a second embodiment. FIG. 10 is a diagram for explaining the principle of the second embodiment.

  10A shows the state of the conventional sysbol 42 and the application volume (application volume) 45. FIG. In (A), the unique information 421 of the business server 20 is directly stored in the sysbol 42. On the other hand, (B) shows the state of the sysbol 42 and the application volume 45 in the second embodiment. In (B), the unique information 421 of the business server 20 is stored in the application volume 45, and the link information 422 (for example, Windows (registered) as reference information for identifying the position of the unique information 421 is stored in the system volume 42. Trademark)), a shortcut) is stored. By doing so, the contents of the Sysbol 42 can be made common among the business servers 20. However, in each business server 20, the link destination of the unique information 421 needs to have the same value (path) in each application volume 45.

  A processing procedure of the patch application system 1 when the unique information of the business server 20 is managed in this way will be described. FIG. 11 is a flowchart for explaining the processing procedure of the patch application system according to the second embodiment. In FIG. 11, the same steps as those in FIG. 3 are denoted by the same step numbers, and description thereof is omitted.

  The contents of each step in FIG. 11 are the same as those in FIG. However, the steps included in the loop executed for each business server 20 are different. That is, in FIG. 3, steps S101 to S113 need to be repeated for each business server 20, but in FIG. 11, the contents of one patch test volume 43 after applying the patch are stored in a plurality of business servers 20. Since it can be copied to each sysbol 42, only steps S109 to S113 need be repeated for each business server 20.

  In order to realize the processing of FIG. 11, the management server 10 manages information related to each business server 20 or each patch application server 30 using tables as shown in FIGS. 12 and 13.

  FIG. 12 is a diagram illustrating a configuration example of a business server management table. In FIG. 12, the business management table 15 includes a host name, an IP address in the business LAN 51, an IP address in the management LAN 52, an OS type and version information for each business server 20 (Server1, Server2,...). Various hardware information, applied patch information, and the like are registered.

  FIG. 13 is a diagram illustrating a configuration example of the patch application server management table. 13, the patch application server management table 16 includes a host name, an IP address in the management LAN 51, an OS type and version information, for each patch application server 30 (patch server 1, patch server 2,...). In addition, various hardware information and the like are registered.

  That is, in the second embodiment, the patch application manager 11 of the management server 10 stores the OS type and version information, and hardware information of the patch application server 10 to which the patch 13 is applied in steps S101 to S107, as the patch application server. Recognize based on the management table 16. Further, the OS type and version information of the business server 20 registered as a patch application target in the schedule information 12 and the hardware information are recognized based on the business server management table 15. In the loop processing from step S109 to S113, the business server 20 whose OS type, version information, and hardware information match that of the patch application server 30 is processed. In this way, patches can be collectively applied to a plurality of business servers 20 having the same OS type, version information, hardware information, and the like, based on one patch test volume 43. Note that if the patch has already been applied based on the applied patch information in the business management table 15, the business server 20 may be excluded from the patch application targets.

  As described above, according to the patch application system 1 in the second embodiment, the processing efficiency when applying the same patch to a plurality of business servers 20 can be improved.

  As mentioned above, although the Example of this invention was explained in full detail, this invention is not limited to the specific embodiment which concerns, In the range of the summary of this invention described in the claim, various deformation | transformation * It can be changed.

Regarding the above description, the following items are further disclosed.
(Supplementary Note 1) A patch application control method in which a first computer applies a patch to a program stored in a recording medium related to a second computer,
A first copy procedure for causing the first computer to copy the recorded content of the recording medium according to the second computer to a recording medium according to a third computer different from the second computer;
A patch application procedure in which the third computer applies the patch to the recorded content copied to a previous recording medium according to the third computer;
A determination procedure in which the third computer determines success or failure of application of the patch;
A second copy procedure for causing the first computer to copy the recorded content of the recording medium related to the third computer to the recording medium related to the second computer when the application of the patch is successful; A patch application control method characterized by comprising:
(Supplementary Note 2) A first setting procedure for causing the first computer to set a first timing for executing the first copy procedure;
A first detection procedure in which the first computer detects the arrival of the first timing;
The patch application control method according to claim 1, wherein the first computer executes the first copy procedure in response to detection of arrival of the first timing.
(Supplementary Note 3) A second setting procedure for causing the first computer to set a second timing for executing the second copy procedure;
A second detection procedure in which the first computer detects the arrival of the second timing;
The patch application control method according to appendix 1 or 2, wherein the first computer executes the second copy procedure in response to detection of arrival of the second timing.
(Supplementary Note 4) The first copy procedure may cause the recording contents of the recording medium related to the second computer to be duplicated to the recording medium related to the third computer,
The patch application procedure applies the patch to one of the recorded contents duplicated,
If the second computer does not operate normally after the second copying procedure, the recorded contents to which the patch is not applied among the recorded contents copied twice are transferred to the second computer. The patch application control method according to any one of appendices 1 to 3, wherein the patch is copied to the recording medium.
(Supplementary Note 5) In the recording content of the recording medium related to the second computer copied in the first copying procedure, the unique information of the second computer is used as reference information for identifying the position of the unique information. Recorded,
The second copy procedure includes causing the recording contents of the recording medium related to the third computer to be copied to recording media related to a plurality of computers including the second computer. 5. The patch application control method according to claim 1.
(Supplementary note 6) A patch application control apparatus for applying a patch to a program stored in a recording medium according to a second computer,
First copy means for copying the recording content of the recording medium related to the second computer to a recording medium related to a third computer different from the second computer;
Patch application instruction means for causing the third computer to apply the patch to the recorded contents copied to the previous recording medium of the third computer;
Result acquisition means for acquiring information indicating success or failure of application of the patch from the third computer;
And a second copy means for copying the recorded content of the recording medium related to the third computer to the recording medium related to the second computer when the application of the patch is successful. Patch application control device.
(Supplementary note 7) A patch application device as a third computer according to supplementary note 6,
Patch application means for applying the patch to the recorded content copied to the previous recording medium according to the patch test apparatus in response to a request from the patch application instruction means of the patch application control apparatus;
Determining means for determining success or failure of application of the patch;
A patch application apparatus comprising: a determination result providing means for providing a determination result by the determination means to the patch application control apparatus.
(Supplementary Note 8) A computer that applies a patch to a program stored in a recording medium related to a second computer,
First copy means for copying the recorded content of the recording medium related to the second computer to a recording medium related to a third computer different from the second computer;
Patch application instruction means for causing the third computer to apply the patch to the recorded content copied to the previous recording medium of the third computer;
Result acquisition means for acquiring information indicating success or failure of application of the patch from the third computer;
Patch application for functioning as second copy means for copying the recorded content of the recording medium of the third computer to the recording medium of the second computer when the application of the patch is successful Control program.
(Appendix 9) The third computer described in Appendix 6 is
Patch application means for applying the patch to the recording content copied to the previous recording medium according to the patch test apparatus in response to a request from the patch application instruction means of the patch application control apparatus;
Determining means for determining success or failure of application of the patch;
A patch application program for causing a determination result provided by the determination unit to function as a determination result providing unit that provides the patch application control device.

It is a figure which shows the structural example of the patch application system in embodiment of this invention. It is a figure which shows the hardware structural example of the management server in embodiment of this invention. It is a flowchart for demonstrating the process sequence of the patch application system in 1st embodiment. It is a figure which shows the example of a screen for registering schedule information. It is a figure for demonstrating the processing procedure of the double copy of the system volume of a business server. It is a figure for demonstrating the process sequence of the patch application with respect to a patch application server. It is a figure for demonstrating the process sequence of the patch application to a business server. It is a figure which shows the example of a display of a patch application result. It is a flowchart for demonstrating the process sequence of the patch application system when not stopping a business server in the case of double copy. It is a figure for demonstrating the principle of 2nd embodiment. It is a flowchart for demonstrating the process sequence of the patch application system in 2nd embodiment. It is a figure which shows the structural example of a business server management table. It is a figure which shows the structural example of a patch application server management table.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Patch application system 10 Management server 11 Patch application manager 12 Schedule information 13 Patch 14 Shell script 20 Business server 21 Agent 30 Patch application server 31 Patch application agent 40 RAID apparatus 41 RAID apparatus management part 42 Sysbol 43 Patch test volume 44 For backup Volume 45 Application volume 51 LAN for business use
52 Management LAN
53 LAN for testing
DESCRIPTION OF SYMBOLS 100 Drive apparatus 101 Recording medium 102 Auxiliary storage apparatus 103 Memory apparatus 104 Arithmetic processing apparatus 105 Interface apparatus 106 Display apparatus 107 Input apparatus B Bus

Claims (5)

A patch application control method in which a first computer applies a patch to a program stored in a recording medium related to a second computer,
A first copy procedure for causing the first computer to copy the recorded content of the recording medium according to the second computer to a recording medium according to a third computer different from the second computer;
A patch application procedure in which the third computer applies the patch to the recorded content copied to a previous recording medium according to the third computer;
A determination procedure in which the third computer determines success or failure of application of the patch;
A second copy procedure for causing the first computer to copy the recorded content of the recording medium related to the third computer to the recording medium related to the second computer when the application of the patch is successful; A patch application control method characterized by comprising: A first setting procedure for causing the first computer to set a first timing for executing the first copy procedure;
A first detection procedure in which the first computer detects the arrival of the first timing;
2. The patch application control method according to claim 1, wherein the first computer executes the first copy procedure in response to detection of arrival of the first timing. A second setting procedure for causing the first computer to set a second timing for executing the second copy procedure;
A second detection procedure in which the first computer detects the arrival of the second timing;
3. The patch application control method according to claim 1, wherein the first computer executes the second copy procedure in response to detection of arrival of the second timing. In the first copy procedure, the recording content of the recording medium related to the second computer is duplicated to the recording medium related to the third computer,
The patch application procedure applies the patch to one of the recorded contents duplicated,
If the second computer does not operate normally after the second copying procedure, the recorded contents to which the patch is not applied among the recorded contents copied twice are transferred to the second computer. 4. The patch application control method according to claim 1, wherein copying is performed on the recording medium. In the recording contents of the recording medium related to the second computer copied in the first copying procedure, the unique information of the second computer is recorded as reference information for identifying the position of the unique information. ,
2. The second copy procedure, wherein the recording content of the recording medium according to the third computer is copied to a recording medium according to a plurality of computers including the second computer. The patch application control method according to any one of claims 1 to 4.

Images