JP3861920B2 - Computer system and program installation method - Google Patents

Description

  The present invention relates to a computer system and a program installation method in the computer system, and more particularly to a method for installing a program for a plurality of computers.

  For installation of a program on a computer, a portable record such as a CD-ROM storing an installer which is a program for executing a series of installation procedures, a main body of the program to be installed, and other necessary installation files. Media is used. Conventionally, in general, an installation operation has been performed by an operator loading a recording medium in a storage device such as a CD-ROM device provided in a computer and executing an installer on the computer.

  As another method for installing the program in the computer, there is a method of installing the program from a file server connected to the computer via a network. In this method, a file group for installation is stored in a storage device that can be mounted as a so-called network disk from another computer. The operator activates the computer to install the program and mounts the storage device of the file server as a network disk. After that, the worker executes the installer stored in the storage device of the file server on the computer, reads the program main body file and other necessary files from the storage device of the file server to the computer, and the computer The data is stored in an appropriate location of a storage device such as a disk device provided.

  When installing a program on a plurality of computers on the network, the worker performs the above-described operation for each computer. Since the disk device of the file server can be used in common by all the computers, the operator can also start the installer on a plurality of computers substantially simultaneously.

  In general, a portable recording medium has a slow file transfer speed, and therefore requires a long time for installation. When performing installation for a plurality of computers, it is necessary to perform the installation work for the number of units, and the processing time becomes longer in proportion to the number of computers. By using a plurality of recording media, installation work for a plurality of computers can be executed in parallel. However, even in this case, the number of recording media that can be prepared is limited, and if the number of computers is large, the repetitive processing cannot be avoided. Even when parallel processing is executed in this way, loading of recording media, starting of an installer, various setting processes, and the like need to be performed for each computer, so that a plurality of workers are required.

  On the other hand, when installation is performed via a network, there is a possibility that file transfer can be performed faster than using a portable recording medium. However, if installation is performed on multiple computers in parallel, the file transfer speed between the file server and the network becomes a bottleneck. Consequently, the required transfer speed cannot be obtained, and the work must be repeated multiple times. . In general, the program is constantly upgraded due to improvement of the function of the program, correction of a defect, and the like, and program installation work also occurs regularly. For this reason, expenses such as labor costs in the installation work are factors that increase the operation cost for maintaining and managing the computer system.

  As another problem, if the worker who performs the installation work does not belong to the organization that owns the computer, it is preferable for such a worker to enter the place where the computer is installed because of confidentiality issues. Absent. Also, the method of installation varies depending on the program, and a great amount of training time is required for all workers to master the installation method of all programs. If the operator is not sufficiently familiar with the installation method, secondary problems such as re-installation due to failure or destruction of files inside the disk device may occur.

  SUMMARY OF THE INVENTION An object of the present invention is to provide a program installation method capable of reducing the operation cost required for the maintenance and management of a computer system by making the processing when installing the program in the computer efficient in the computer system. There is.

  In order to achieve the above object, according to one aspect of the present invention, there are provided a plurality of computers, a management console in which an operator installs a program to the plurality of computers, and a storage connected to the computer and the management console. A computer system having a method for installing a program on a computer is provided. In this method, the installation agent process is started on the computer under the control of the management console. When the installation agent starts the process, the installer program stored in the first storage device in the storage is loaded on the computer and activated. When the installer program is activated, it transfers a file related to the program to be installed stored in the first storage device to the second storage device used by the computer, and executes the program installation.

  According to another aspect of the present invention, there is provided a computer system having a plurality of computers, a management console in which an operator installs a program to the plurality of computers, and a computer and a storage connected to the management console. The storage includes a first storage device shared by the plurality of computers and a plurality of second storage devices that are used exclusively for the plurality of computers. The first storage device stores a file related to a program installed in the computer and an installer program for executing the program installation. The second storage device stores an install agent executed on each computer and a control file referred to by the install agent. The management console has an install manager for starting execution of the install agent on each computer. In a preferred aspect of the present invention, each computer includes a power control circuit that turns on the power in response to an instruction from the installation manager. The installation manager starts processing by the installation agent on each computer by turning on the power of each computer. When the installation agent starts processing, it starts the installer program on the computer according to the contents of the control file. The installer program reads a related file from the first storage device, transfers the file to the second storage device dedicated to the computer, and installs the program.

  According to the present invention, in the computer system, it is possible to reduce the operation cost required for the maintenance management of the computer system by making the processing when installing the program in the computer efficient.

  Embodiments of the present invention will be described below.

  FIG. 1 is a simplified block diagram showing the configuration of a computer system according to an embodiment of the present invention. The computer system according to the present embodiment includes a plurality of computers 2a, 2b,..., 2n (hereinafter, when description is made without distinguishing between individual computers, 2 is used as a reference number). A shared storage 1, a management console 4 for managing the computer system, and a plurality of computers 2, a management console 4, and a fiber channel connection device 3 to which the storage 1 is connected are provided. The computer 2, the management console 3, and the storage 1 and the fiber channel connection device 3 are connected by a fiber channel 5. Each computer 2 and the management console 4 are connected to each other via a local area network (LAN) 6 so that they can communicate with each other. The management console 4 and the storage 1 are connected by a communication path 7.

  In the present embodiment, description will be made assuming that a PC (Personal Computer) is used as the computer 2. Of course, a computer such as a server or a workstation can be used as the computer 2. As an interface (hereinafter abbreviated as I / F) for connecting the computer 2 and storage, a fiber channel suitable for the connection distance and speed is used, but SCSI (Small Computer System Interface), An interface such as USB (Universal Serial Bus), IEEE 1394 bus, or the like may be used.

  FIG. 2 is a simplified block diagram showing the configuration of the computer 2. 21 is an input / output device for accepting or outputting information, 22 is a central processing unit (CPU) that controls the entire computer 2, and 25 is installed for performing fiber channel connection and control. A fiber channel board 24, a LAN board for performing communication via the LAN 6, and a memory 23 for storing programs and data necessary for the CPU 22 to execute various controls. The memory 23 stores a plurality of programs.

  The Fiber Channel board 25 stores a Fiber Channel controller 250 that controls the Fiber Channel, programs and data necessary for the Fiber Channel controller to control, and programs and data necessary for the CPU 22 to control the Fiber Channel controller 250. A stored memory 251 is included. The programs stored in the memory 251 include a boot-up control program that is executed by the CPU 22 to control the fiber channel controller 250 to load and start the OS from the storage 1. The memory 251 holds a WWN (World Wide Name) 2512 that is name information provided to uniquely identify the Fiber Channel controller 250. In this embodiment, the fiber channel controller 25 and the memory 251 are provided on a board mounted on the computer 2, but these may be directly mounted on, for example, a board on which the CPU 22 or the like is mounted. .

  The LAN board 24 is provided with a remote power-on circuit 241 for controlling the main power switch 26 of the computer 2 from the outside of the computer 2 to turn on / off the power of the computer 2.

  FIG. 3 is a simplified block diagram showing the configuration of the storage 1. The storage 1 is connected to the control unit 11 that controls the entire storage 1, the fiber channel 5, the fiber channel controller 15 that performs the control, and the program and data that the control unit 11 executes to control the storage 1. , 13n, and 14 and a communication interface 16 that controls communication with the management console 4 and a plurality of logical units (LU) 13a, 13b,. Note that the communication LU 17 shown in the drawing is not particularly required in the present embodiment, and this will be described in the second embodiment.

  The logical unit is a virtual volume (storage device) recognized by the computer 2, and the computer 2 recognizes one LU as one logical disk device. The logical unit is a name defined in the specification of SCSI (Small Computer System Interface), which is one of the interfaces connecting the computer and the storage. In SCSI, in order to identify individual logical units, a logical unit number (LUN) is assigned to each logical unit as an identifier. Hereinafter, in this specification, a logical unit is simply expressed as LU, and a logical unit number is expressed as LUN. The storage 1 can be constructed by defining a plurality of LUs inside. An LU defined inside the storage 1 is called an internal LU. Each internal LU is given an integer serial number starting from 0 in order to manage them inside the storage 1. This number is called an internal LUN.

  Each computer 2 has a dedicated LU 13 (hereinafter referred to as “13” as a reference number when it is not necessary to individually distinguish logical units 13a, 13b,..., 13n from a plurality of defined LUs. To be used). In this specification, the LU 13 assigned exclusively to one of the computers is also called a local LU. On the other hand, the LU 14 is an LU that is shared by all the computers 2 and the management console 4 and can be accessed from any of them. In this specification, an LU shared by a plurality of computers is also called a shared LU. The computer 2 searches the connected storages at the time of booting up the OS and detects their LUNs. In general, for detection of LUNs by a computer such as a PC, (a) LUNs are searched in order from 0. (b) It is assumed that LUNs exist in consecutive numbers. There is a restriction that it is not performed. When there is such a restriction, if the internal LUN is used as it is as the LUN detected by each computer 2, each computer 2 is made to recognize only the internal LUN of the LU that can be accessed from each computer 2. I can't do that. In the present embodiment, each computer is caused to recognize a virtual LUN so that the computer 2 can recognize only LUNs of available LUs as sequential numbers starting from 0. Hereinafter, a virtual LUN recognized by the computer 2 is referred to as a virtual LUN. The correspondence relationship between the internal LUN and the virtual LUN is managed by a LUN management table described later.

  The memory 12 includes an LU definition program 121 executed by the control unit 11 to define and create LUs, and access control executed by the control unit 11 to control access from each computer 2 to each LU. A LUN management table 122 that stores management information referred to by the control unit 11 when controlling access to the LU from the computer 123 and each computer 2 is stored.

  FIG. 4 is a table configuration diagram illustrating an example of the LUN management table. The LUN management table 122 has a plurality of entries corresponding to a set of an internal LU and a computer that can use the internal LU. In each entry, a port number 1221, Target ID 1222, virtual LUN 1223, internal LUN 1224, WWN 1225, S_ID 1226, and attribute 1227 are set. These pieces of information are set via the management console 4 by the system administrator when creating and defining an LU, for example.

  The port number 1221 is a number assigned to the connection port of the fiber channel included in the storage 1. In the present embodiment, it is assumed that the storage 1 has one connection port, and the port number 1221 is assumed to store 0 uniformly.

  The Target ID 1222 is an identifier assigned to the storage 1 at the interface with the computer 2. When a fiber channel is used for an interface connecting the computer 2 and the storage 1 as in the present embodiment, D_ID (Destination ID) assigned at the time of initialization to each port can be used as the Target ID 1221. . When SCSI is used as an interface, a plurality of IDs can be assigned to the same port. In such a case, the Target ID to which each LUN at that time belongs is set in this field. When the interface is a fiber channel, the connection port number and D_ID can be made to correspond one-to-one, and therefore either the port number 1221 or the target ID 1222 may be omitted. In this embodiment, since the fiber channel is used for the interface, the Target ID 1221 is not used and 0 is set uniformly.

  The virtual LUN 1223 and the internal LUN 1224 hold the relationship between the virtual LUN recognized by the computer 2 identified by the information set in the WWN 1225 and the internal LUN corresponding to the virtual LUN.

  In the WWN 1225, the WWN 2512 set in the fiber channel controller 250 of the computer 2 is set. The WWN is information notified from each computer 2 at the time of port login processing for establishing a connection relationship between the ports of the fiber channel.

  S_ID 1226 is ID information set in the frame header of the fiber channel, and is an ID for identifying the source (initiator) that created the frame. The S_ID is dynamically assigned when the Fiber Channel is initialized. By associating the WWN and the S_ID, the computer 2 can be identified by checking the S_ID without checking the WWN for each frame.

  An attribute 1227 indicates the ownership attribute of each LU. “Dedicated” indicates that the LU is exclusively allocated to one computer 2. “Shared” indicates that the LU is shared by a plurality of computers 2.

  Here, WWN of the computer 2a is “WWNa”, S_ID is “S_IDa”, WWN of the computer 2b is “WWNb”, S_ID is “S_IDb”, WWN of the computer 2n is “WWNn”, S_ID is “S_IDn”, management console 4 is assumed to be “WWNz” and S_ID is “S_IDz”. From the LUN management table 122 shown in FIG. 4, for example, the computer 2a is assigned an LU with an internal LUN of 0 as a dedicated local LU 13a, and is recognized by the computer 2a as an LU of LUN “0”. Understood. Similarly, it is understood that an LU having an internal LUN of 1 is allocated to the computer 2b as a dedicated local LU, and is recognized as an LU of LUN “0” from the computer 2b. The LU of the internal LUN “k” is an LU shared by a plurality of computers, and is recognized as the LU of LUN “1” from the computers 2a, 2b, and 2n, and the LUN “1” is recognized from the management console 4. It is understood that it is recognized as a 0 ″ LU.

  FIG. 5 is an explanatory diagram of programs and the like stored in the local LU 13. The local LU 13 includes an operating system (OS) 131, an install agent program (hereinafter referred to as an install agent) 132, a communication program 134, and a shutdown program 135 as programs used by the computer 2 to which the LU is assigned. Stored. These programs are loaded into the memory 23 of the computer 2 and executed by the CPU 22.

  The OS 131 is a program for executing various programs on the computer 2, controlling hardware, and the like. The OS 131 has its own setting information and configuration information, information about the program executed on the computer 2, and the computer 2 It has a registry 1311 that holds and manages information about users to be used. The installation agent 132 is a program that starts an installer program for installing a program and performs a part or all of the processing of an installation operation that has been performed by a conventional worker. The communication program 134 is a program that controls communication with the management console 4 and reports the progress of installation work and the occurrence of errors. The shutdown program 135 is a program for shutting down the computer 2.

  In addition to the above-described program, the local LU 13 includes an install agent control file 133 that holds information for controlling the install agent 132, progress information on the installation work of the program executed in the computer 2, various kinds of work success / failure, and the like. A computer status table file 136 that stores status information and the like is stored.

  FIG. 6 is an explanatory diagram of programs and the like stored in the shared LU 14. The shared LU 14 stores an installer program 141 and an installation file group 142. The installation file group 142 includes files necessary for installation such as a main body file of the program installed by the installer program 141 and various setting files. The installer program 141 and the installation file group 142 are copied from a portable medium such as a CD-ROM to the shared LU 14 by an operator prior to the installation work.

  The installer program 141 is loaded into the memory 23 of the computer 2 by the installation agent 132 and executed. The installation file group is referred to by the installer program 141 or copied to the local LU 13 of the computer 2 on which the installer program 141 is executed.

  FIG. 7 is a simplified block diagram showing the configuration of the management console 4. The management console 4 includes an input / output device 41 for an administrator to operate the management console 4, a CPU 42 that controls the entire management console 4, a memory 43 for storing programs and data executed by the CPU 41, and a fiber channel 5. A fiber channel board 45 for connection and control, a LAN board 44 for communication via the LAN 6, a disk device 46 for storing the OS and program of the management console 4, and a communication interface 47 for communication with the storage 1. Have

  The programs stored in the memory 43 include an install manager program 431 (hereinafter referred to as an install manager) that controls the overall installation work. The install manager 431 includes a plurality of subprograms described below.

  FIG. 8 is a conceptual diagram showing the configuration of the install manager 431. The install manager 431 includes a remote power control program 4311, an install agent control file delivery program 4312, an install agent delivery program 4313, a registry change program 4314, a shutdown program delivery program 4315, a progress status display program 4316, a communication program 4317, and a communication program. A distribution program 4318 is included.

  The remote power control program 4311 is a program for controlling on / off and reboot of the computer 2 from a physically remote location. The install agent control file delivery program 4312 is a program for delivering the install agent control file 133 to each computer 2. The install agent delivery program 4313 is a program for delivering the install agent 132 to each computer 2. The registry change program 4314 is a program for changing the registry 1311 of the computer 2 from a physically remote location. The shutdown program distribution program 4315 is a program for distributing the shutdown program 135 to each computer 2. The progress status display program 4316 is a program for displaying the progress status of installation work and error occurrence status in each computer 2. The communication program 4317 is a program for communicating with each computer 2 and acquiring the progress of installation work and the occurrence of errors. The communication program distribution program 4318 is a program for distributing the communication program 134 to each computer 2.

  FIG. 9 is a flowchart of processing performed as preparation work for installation.

  The operator first turns on the power of the computer 2 to be installed. Specifically, the installation manager 431 of the management console 4 is activated, a remote power-on packet is created by the remote power control program 4311, and is transmitted to the computer 2 that performs the installation. The remote power-on packet has a header 901 and a data part 902 as shown in FIG. The data unit 902 includes a synchronization unit 9021 and one or more MAC addresses 9022 of the computer 2 to be turned on. When the remote power-on control unit 241 on the LAN board 24 of the computer 2 receives the remote power-on packet 900, it checks the MAC address 9021 set in the data part 902. The remote power-on control means 241 compares the MAC address 9021 set in the data part 902 and the MAC address of the LAN board 24, and if a match is found, controls the main power switch 26 to 2 is turned on (step 701).

  When the power source of the computer 2 to be installed is turned on, the installation manager 431 executes the installation agent program distribution program 4313 and distributes the installation agent 132 to each computer 2 via the LAN 6. When each computer receives the install agent 132, each computer stores it in the dedicated local LU 13. The program distributed to the computer 2 in this step and the subsequent steps mounts the local LU 13 of each computer 2 as a network disk on the management console 4 and stores it directly in the local LU 13 of each computer 2 from the management console 4. It does not matter (step 702).

  Subsequently, the install manager 431 distributes the communication program 134 to the computers 2 using the communication program distribution program 4318 and the shutdown program 135 using the shutdown program distribution program 4315. These programs are stored in the local LU 13 similarly to the install agent 132 (steps 703 and 704).

  Next, the install manager 431 creates an install agent control file 133. FIG. 11 shows the configuration of the installation agent control file 133. The installation agent control file 133 includes a selected installer 1331, an agent on / off identifier 1332, an installer activation time 1333, and installation key information 1334 as information. The selection installer 1331 represents the storage location and name of the installer program 141 to be started by the computer 2. This information makes it possible to control which computer 2 starts which installer program 141 when there are a plurality of installer programs. The agent on / off identifier 1332 is an identifier used for determining whether or not the installation agent 132 of the computer 2 performs the installation process. The agent on / off identifier 1332 describes either an on attribute or an off attribute. The installer activation time 1333 is information for instructing the installation agent 132 when to activate the installer program 141. The installation key information 1334 is information prepared for preventing unauthorized installation. The installation agent 132 performs installation only when appropriate key information is stored. This information may be used as necessary and is not essential information. The contents of the install key information 1334 will be described later (step 705).

  The install manager 431 uses the install agent control file delivery program 4312 to deliver the created install agent control file 133 to each computer 2. When this file is distributed to each computer, it is stored in the local LU 13 of each computer 2 (step 706).

  When the distribution of each program and the installation agent control file is completed, the installation manager 431 uses the registry change program 4314 to change the registry 1311 of the computer 2 so that the computer 2 automatically logs on and starts executing the installation agent 132. (Step 707). Subsequently, the install manager 431 activates the shutdown program 135 of the computer 2 by the remote power control program 4311 and shuts down the computer 2 (step 708).

  After the shutdown of the computer 2 to be installed, the installation manager 431 stores the installer program 141 and the installation file group 142 in the shared LU 14 (Step 709 and Step 710).

  This completes the preparation for installation.

  FIG. 12 is a flowchart showing a flow of installation execution work.

  The operator operates the management console 4 and activates the installation manager 431 similarly to step 701, and turns on the power of the computer 2 performing the installation work by the remote power control program 4311 (step 801).

  In each computer 2, when the power is turned on, the OS 131 is started and logon is automatically performed. When the computer 2 starts up, the computer 2 starts executing the installation agent 132. In the present embodiment, when the OS 131 is activated, the installation agent 132 is automatically activated and the operation is started. However, the installation agent 132 can be realized as a program resident in the computer 2. In this case, the install manager 431 may give a start instruction to the install agent 132 by inter-program communication (step 802).

  When the installation agent 132 of the computer 2 starts its operation, it refers to the installation agent control file 133 in the computer local LU 13 (step 803).

  The install agent 132 checks the agent on / off identifier 1332 of the install agent control file 133. If the agent on / off identifier 1332 indicates an on attribute, then the installation key information 1334 is confirmed. As the install key information 1334, for example, license key information issued by the developer of the program to be installed, license key information issued by the developers of the install manager and the install agent, or the like can be used. By using these pieces of information, it is possible to confirm whether or not the program to be installed is properly licensed. Further, as the installation key information 1334, identification information such as the WWN or MAC address of the computer 2 permitted to be installed may be used. The installation agent 132 can compare such information with the identification information on the computer to confirm whether or not the own computer is a computer permitted to be installed. As the install key information 1334, such computer identification information and the license key information described above may be used in combination. If the agent on / off identifier 1332 is an off attribute or the installation key information 1334 is not valid, the installation agent ends the process without installing the program (step 804).

  If the agent on / off identifier 1332 has the on attribute and the install key information 1334 is valid, the install agent 132 loads the installer program 141 stored in the shared LU into the memory 23 and starts it. . In step 804, if the installer program activation time is specified in the installer activation time 1333 of the installation agent control file 133, the installation agent 133 suspends the activation of the installer program until that time.

  When the installer program 141 is activated, it installs the program. At this time, the installer program 141 reads the installation file group 142 from the shared LU 14 to the memory 23 of the computer 2 via the fiber channel in order to reflect the installation information in the registry 1311 of the computer 2, and subsequently to the local LU 13 for the computer. Those files are transferred (step 806).

  When the installation process by the installer program 141 is completed, the installation agent 132 rewrites the agent on / off identifier 1332 of the installation agent control file 133 to the off attribute so that the installation process is not performed when the computer 2 is activated next time. At this time, the install key information 1334 is invalidated as necessary (step 807).

  Subsequently, the installation agent 132 activates the shutdown program 135 in the computer local LU 13 (step 808). When started, the shutdown program 135 shuts down the computer 2 (step 809).

  This completes the installation work. Thereafter, when the user of the computer 2 starts the computer 2, the installed program can be used. When installing a program for a plurality of computers 2, the above-described preparation process is performed for a plurality of computers, and if the plurality of computers 2 are turned on in step 801, The installation process is performed in parallel.

  In the program installation work, it is desirable that the operator can confirm the progress of the installation process and whether the work has been completed without causing an error. In this embodiment, the progress status of the installation work and the error occurrence status are recorded in the computer status table file 136, and the worker can refer to the progress status and the error occurrence status by referring to this file from the management console 4. You can check it.

  FIG. 13 is a table configuration diagram showing an example of the computer status table file 136. As shown in the figure, the computer status table file 136 includes information indicating the power status, the OS startup status, the installation agent operating status, the installation processing status, and the shutdown processing status as information indicating the work status in the computer 2. Is recorded. The computer status table file 136 records the progress status and error occurrence status for each work step in the middle of the installation work. Specifically, the remote power control program 4311 records the power supply status and the OS startup status, the installation agent 132 records the installation agent status and the installation status, and the shutdown program 135 records the shutdown status. The value set as the status 1362 is defined as shown in FIG. According to the definition of FIG. 14, from the computer status table file 136 shown in FIG. 13, this computer 2 is powered on, the OS is completely started, the installation agent is on, the installation is in progress, and the shutdown process starts. It can be grasped that it is not in the state.

  The management console 4 mounts the local LU 13 as a network disk, reads the computer status table file 136 stored in each local LU 13 by the progress status display program 4316, and progresses the work progress or error occurrence status in the install target computer 2. Is displayed on the input / output device 41. In this embodiment, the computer status table file stored in the local LU 13 is directly referenced from the management console 4, but the communication program 134 of each computer 2 and the communication program 4317 of the management console 4 are used. This information may be transferred by communication. When an error occurs during installation, the operator can recognize this on the management console 4 and can take necessary measures such as retry processing.

  According to this embodiment, it is possible to install a program using a fiber channel that is a high-speed interface and without interposing a control device such as a file server located between the computer and the storage. As a result, the transfer speed of the file transfer executed in the installation process can be increased. In addition, a single worker can install a plurality of computers intensively and simultaneously from the management console. As a result, the installation time can be shortened and the number of necessary workers can be reduced, and the operation cost for maintaining and managing the computer system can be reduced. In addition, since the management console is installed at a location physically separated from the location where the computer is installed and installation can be performed remotely, there is no need for an operator to enter the environment where the computer is installed, and security is improved. Can be increased. Furthermore, by using the installation key information, it is possible to prevent unauthorized installation or erroneous installation on a computer that has not received a license. Furthermore, according to the present embodiment, the installation work can be executed in the same procedure regardless of the type of program to be installed, so that the installation work is simplified, and specialized knowledge and proficiency are insufficient. You can also perform the installation work.

  In this embodiment, the installation agent control file prevents unauthorized installation or erroneous installation. However, using the function of the LUN management table 122 of the storage 1, a computer to be installed prior to execution of installation is used. The local LU of other computers may be hidden, or the shared LU may be hidden from computers other than the installation target computer so that the installation cannot be executed. Further, after the installation is completed, it is possible to prevent unauthorized installation or erroneous installation by deleting the installer program and the installation file group from the shared LU.

  In the first embodiment, power-on control of each computer is performed via the LAN, but the same processing can be performed without using the LAN. Hereinafter, as a second embodiment, a case where installation work is performed without using a LAN will be described.

  The computer system according to the second embodiment is basically configured in the same manner as the computer system according to the first embodiment except that the LAN 6 is not necessary. Therefore, description will be given here with reference to the drawings used in the first embodiment.

  In the present embodiment, the storage 1 is provided with a communication LU 17. The communication LU 17 holds a total status table list indicating the state of each computer 2.

  FIG. 15 is a configuration diagram of the computer status table list 137. The computer status table list 137 is an aggregation of the contents of the computer status table file 136 of each computer 2. The contents of the computer status table file 136 are the same as those shown in FIG. The computer status table list 137 is used to notify the management console 4 of the progress status of installation work and the occurrence status of errors in each computer 2.

  The computer status table list 137 is created by the communication program 134 included in the computer 2. In the table 1371 for each computer 2, the address in the communication LU 17 is uniquely determined in advance. The communication program 134 of the computer 2 accesses the communication LU 17 using a RAW I / O command that directly reads / writes a logical block of the LU, not a file read / write using a file system. Thereby, each computer 2 can write status information in the computer status table list 137 at an arbitrary timing. The communication program 4317, which is a subprogram of the installation manager 431 of the management console 4, can sequentially know the status of each computer 2 by reading the computer status table list 137 at an appropriate timing using the RAW I / O command. it can. The communication program 4317 of the management console 4 cannot write data to the computer status table list 137 unless it is clear that a certain computer 2 has not been installed or has been installed. If the file system is configured so that file sharing is possible, the computer status table 136 may be constructed as a file and accessed without using RAW I / O.

  In the present embodiment, distribution of various programs and files performed in the installation preparation process is performed as follows.

  In this embodiment, the management console 4 communicates with the storage 1 to change the WWN of the LUN management table 122 of the storage 1 and installs a program in the management console 4 in the same manner as LU creation and definition. Mount the local LU 13 of the computer 2. In this state, the management console 4 stores various programs and files in the local LU 13 of each computer 2. After the programs and files are stored, the management console 4 restores the information in the LUN management table 122 so that the files can be used when the computer 2 is started next time.

  In the present embodiment, power-on control of the computer 2 is performed via a fiber channel. Therefore, each computer 2 includes a remote power-on control unit 2501 and a standby power supply 2502 in the fiber channel board 25 as shown in FIG. Since the LAN is not used in this embodiment, the LAN board is not shown in FIG. 16, but a LAN board may be provided for other purposes.

  The remote power-on control means 2501 is provided inside the fiber channel controller 250. The standby power supply 2502 is maintained on even while the main power supply of the computer 2 is off, and supplies power to the fiber channel board 25. Therefore, the fiber channel controller 250 can operate regardless of the state of the main power supply of the computer 2 and can receive a frame (packet) sent via the fiber channel 5.

  FIG. 17 is a format diagram showing an example of a remote power-on frame used for power-on of the computer 2. The Fiber Channel frame includes an SOF (Start of Frame) 9501 indicating the beginning of the frame, a frame header 9502 having information such as information on the transmission node of the frame and the type of the frame, and a payload that holds the substance of data transferred by the frame. 9503, a CRC (Cyclic Redundancy Code) 9504, which is a data guarantee code for detecting a bit error of the frame, and an EOF (End Of Frame) 9505 indicating the end of the frame. In the remote power-on frame 950, the frame header 9502 includes a broadcast identifier 9502a. Broadcast identifier 9502a Indicates that this frame is issued simultaneously to all nodes connected to the fiber channel. As a result, the remote power-on frame 950 is transferred toward all devices on the fiber channel. In the payload 9503, the WWN assigned to the Fiber Channel controller 250 of the computer 2 to be turned on is set.

  The installation manager 431 of the management console 4 creates the above-described remote power-on frame 950 by the remote power control program 4311 in order to turn on the computer 2 that installs the program in step 801 of the installation process. The WWN of at least one computer 2 to be installed is set in the payload 9503 of the generated remote power-on frame 950. The generated remote power on frame 950 is broadcast on the fiber channel.

  The broadcast remote power-on frame 950 is received by the fiber channel controller 250 of each computer 2. When the Fiber Channel controller 250 receives the remote power-on frame 950, the Fiber Channel controller 250 inspects the frame header 2502. If the frame header 2502 includes the broadcast identifier 9502a, the payload 9503 is further inspected to determine whether a WWN that matches its own WWN is set. If a WWN that matches its own WWN is set in the payload 9503, the fiber channel controller 250 controls the main power switch 26 by the remote power-on control means 2501 to turn on the computer 2.

  In the present embodiment, the installation process is basically performed in the same manner as in the first embodiment except that the above-described program and file distribution and the remote power-on method of the computer 2 are different.

  According to the present embodiment, since power-on control of the computer is performed via the fiber channel and communication between the computer and the management console is performed via the communication LU 17, installation work by remote control is performed even in an environment without a LAN. Can be implemented. In this embodiment, power-on control is performed using a Fiber Channel broadcast frame. However, if the Fiber Channel controller is compatible with the IP protocol, the same remote control as that in the first embodiment is used via the Fiber Channel. Remote power-on can also be realized by transferring a power-on packet.

  In the first and second embodiments, when the program is installed, the computer 2 reads the installation file group from the shared LU 14 and transfers it to its own local LU 13. Hereinafter, “direct installation” in which an installation file group is transferred without using the computer 2 and installation is performed will be described.

  FIG. 18 is a simplified block diagram showing the configuration of the computer system of this embodiment. In the figure, the same reference numerals as those in FIG. 1 are assigned to the same parts as those in the first embodiment. Hereinafter, the present embodiment will be described mainly with respect to differences from the first embodiment.

  The computer 2 has functions of a direct copy director 138 that gives an instruction to copy data to the storage 1 and a direct copy API 137 that is an application program interface (API) for giving an instruction related to copying from the program to the direct copy director 138. These functions are realized by a program stored in the local LU 13 dedicated to each computer 2 and loaded onto the memory 23 at the time of execution and executed by the CPU 22.

  The storage 1 has a direct copy engine 124 that copies data from a copy source LU in the storage 1 to a copy destination LU in accordance with an instruction from the direct copy director 138. The direct copy engine 124 is realized as a program stored in the memory 12 of the storage 1 and executed by the control unit 11.

  FIG. 19 is a flowchart showing the flow of processing executed by the installer program 141 in this embodiment. When the process is started, the installer program 141 initializes the installation screen such as displaying a title on the input / output device 21 (step 851). Next, the installer program 141 displays a screen for prompting input of user information and license information of the program on the input / output device 21 and waits for input of such information. Normally, the license information and the like are input by the worker, but in this embodiment, as in the first embodiment, the installation agent 132 executes this processing on behalf of the worker (step 852). Subsequently, the installer program 141 receives an input for selecting an installation method. The installation method specified here includes, for example, a standard installation in which installation is performed with a predetermined file configuration and settings, and a custom installation in which programs to be installed, file types, and configurations can be arbitrarily set (steps). 853). The installer program 141 and the designation of the installation directory for storing the program to be installed are received (step 854). The input processing performed in these steps 852, 853, and 854 is also performed by the install agent 132 on behalf of the worker. The install agent 132 inputs the various types of information described above into the installer program 141 according to the information set in the install agent control file.

  Based on the information set in the above steps, the installer program 141 specifies a file to be copied and an installation destination directory, and executes a file copy process. File copy processing is performed by calling the direct copy API 137 from the installer program 141. The direct copy API 137 is given as a function described as “direct_file_copy (transfer source, transfer destination);” on the source code of the installer program 141, for example. For example, when copying the file “file1” in the directory “dir_a” of the shared LU (d-drive) to the directory “dir_b” of the dedicated LU (c-drive), “direct_file_copy (d: dir_a \ file1, c: dir_b); ”. The direct copy API 137 instructs the storage 1 to copy a file via the direct copy director 138 according to the given parameters. Transfer of the specified file is executed in the storage 1 in accordance with this instruction. (Step 855).

  When copying of all necessary files is completed, the installer program 141 executes registration processing of the registry 1311 of the OS 131 (step 856). This completes the installation process. Thereafter, the installer program 141 reboots the computer as necessary. Similarly to the first embodiment, the installation agent 132 executes processing such as setting change of the installation agent control file 133 as necessary, and ends the installation processing (step 857).

  Next, details of the direct copy performed in step 906 will be described. When the direct copy API 137 is called by the installer program 141, it passes the process to the direct copy director 138. The direct copy API 137 transfers processing between the direct copy director 138 and an application program such as the installer program 141 without performing specific processing. When the direct copy director 138 receives a direct copy request from the direct copy API 137, the direct copy director 138 identifies the LU from the drive letter passed as a parameter, refers to the OS 131 file table information generally called a file system, and copies the copy source and copy. Based on the destination directory and file name, copy information is created in which the logical address and transfer length of the copy source and copy destination are paired. The copy information can be configured so that a plurality of file transfers can be requested at once as a list. The direct copy director 138 issues a copy information list to the direct copy engine 124 of the storage 1. When the direct copy engine 124 receives the copy information list from the direct copy director 138 of the computer 2, the direct copy engine 124 refers to the LUN management table 122 and obtains an internal LUN from the virtual LUNs of the copy source and the copy destination. Next, the direct copy engine 124 refers to the copy information list, and generates a read command from the copy source logical address and transfer length, and a write command from the copy destination logical address and transfer length. The direct copy engine 124 uses the access control program to execute these read commands and write commands in order in the storage. Data read by the read command is temporarily held in a buffer (or cache) (not shown) in the storage 1. The data held in the buffer is written to the copy destination LU by a write command. The direct copy engine 124 executes the above processing for all copy information according to the order of the copy information list. When the copy process based on all copy information is completed, the direct copy engine 124 reports the process end to the direct copy director 138 of the computer 2.

  According to the present embodiment, the file copy process executed at the time of installation can be executed inside the storage 1. For this reason, the computer processing accompanying the copy processing and the data transfer by the fiber channel do not occur, and the processing load of the computer and the fiber channel accompanying the installation processing can be reduced. In addition, since data is copied in the storage 1, a faster copy process can be realized, and the time required for the installation process can be shortened.

  In the third embodiment, the direct copy engine 124 is provided inside the storage 1, but the direct copy engine 124 may be arranged inside the Fiber Channel connection device 3. In this case, the Fiber Channel connection device 3 generates a read command and a write command for copying and issues them to the storage 1. Further, since the Fiber Channel connection device 3 needs to hold data once, it is necessary to provide a buffer for this purpose. In such a configuration, although data flows in the fiber channel, the load on the computer can be reduced as in the third embodiment. Further, it is not necessary to provide a special function for the storage 1, and a system can be configured using a conventional storage. Furthermore, direct installation can be executed even when the copy source LU and the copy destination LU are in physically different storages.

  In the third embodiment, one-to-one direct copy from one copy source to one copy destination is used for the copy processing at the time of installation. In this embodiment, a plurality of copies from one copy source is used. The previous copying is performed without using the computer 2. Such direct copy from one copy source to a plurality of copy destinations is referred to as “one-to-n direct copy”.

  In this embodiment, a direct copy destination LU link generation program 125 is provided in the storage 1 as shown in FIG. The direct copy destination LU link generation program 125 associates (links) a plurality of LUs as copy destinations. When a link is generated by the direct copy destination LU link generation program 125, the direct copy engine 124 performs a one-to-n copy in response to one copy request from the computer 2. With this function, when the computer 2 installs one LU, the same program can be installed in a plurality of LUs for which links have been generated as internal processing of the storage 1.

  The operator or the administrator designates an LU group to be linked to the storage 1 (for example, assuming that a link is generated for LU-a, LU-b, and LU-c) by the installation manager 431 of the management console 4. . At this time, one LU is set as the representative LU. Here, LU-a is a representative LU. The direct copy destination LU link generation program 125 of the storage 1 generates links in the internal LU-a, LU-b, and LU-c.

  When executing the direct copy, the direct copy director 138 of the computer 2 creates a copy information list and transmits it to the storage 1. When receiving the copy information list, the direct copy engine 124 of the storage 1 refers to the LUN management table 122 and obtains an internal LUN from the virtual LUNs of the copy source and the copy destination. In the copy information list, only the representative LU is designated as the copy destination. The direct copy engine 124 refers to the copy information list, sends a read command from the logical address and transfer length of the copy source, and all LUs (LU-) for which a link is generated from the logical address and transfer length for the copy destination representative LU. a, write command with the same contents for a, LU-b, and LU-c). Next, the direct copy engine 124 executes a read command using the access control program, and once reads data into a buffer in the storage 1. Thereafter, the data read into the buffer is written into a plurality of LUs linked by the write command.

  With the above processing, it is possible to install a program to a plurality of LUs at a time. Also in this embodiment, as in the third embodiment, the direct copy engine 124 and the direct copy destination LU link generation program 125 are arranged in the Fiber Channel connection device 3, and these processes are performed as functions of the Fiber Channel. It can also be realized.

  In this embodiment, a plurality of copy destination LUs are designated in advance by the direct copy destination LU link generation program 125. However, the API for extending the direct copy API function and realizing the above-described one-to-n direct copy is described above. May be used. Such an API can be described by a function such as “direct_file_copy_n (number of copy destination LUs, transfer source, transfer destination 1, transfer destination 2,... Transfer destination n);” on the source code. In this case, the direct copy director 138 transmits information of a plurality of linked LUs as a part of the copy information list to the direct copy engine 124. As a result, 1-to-n direct copy can be realized without specifying a link in advance.

  In the first to fourth embodiments described above, the storage 1 is connected to the management console 4 via the fiber channel 5. Therefore, the management console 4 and the storage 1 cannot be arranged beyond the fiber channel connectable distance. At present, the connection distance of the fiber channel is 10 km, and in each of the above-described embodiments, the program cannot be installed from a remote place exceeding this distance. Hereinafter, a method for realizing program installation from a remote location will be described as a fifth embodiment.

  FIG. 20 is a simplified block diagram illustrating a configuration of a computer system according to the fifth embodiment. In the figure, a user site 1000 provided with a computer system having a computer 2 on which a program is installed and a management site 2000 for an administrator to perform an installation operation are arranged at physically separated locations.

  The user site 1000 is basically provided with a computer system similar to that of the first embodiment. The computer system provided in the user site 1000 is different from the computer system in the first embodiment in that a management server 4 a is provided instead of the management console 4 and an Internet server 8 is connected to the LAN 6. The management site 2000 is provided with a management console 4b and the Internet server 10 connected to the management console 4b. The Internet server 8 and the Internet server 10 are communicably connected to each other via the Internet 9 which is a wide area network.

  The management server 4 a provided in the user site 1000 is basically the same as the management console 4 in the first embodiment, but is operated from the management site 2000 via the Internet 9. An install manager server program (hereinafter referred to as an install manager server) 431a is obtained by adding a server function for the management console 4b of the management site 2000 in addition to the functions of the install manager 431 in the first embodiment. The management console 4b communicates with the management server 4a via the Internet 9, displays various operation screens, or a browser program (hereinafter simply referred to as a browser) 432b for accepting various operations by the administrator. A terminal device such as a PC that operates.

  The other components in the present embodiment are basically the same as those in the first embodiment, and a description thereof is omitted here.

  Next, the installation process in the present embodiment will be described focusing on differences from the first embodiment. Here, it is assumed that the various LU settings have already been completed, and the install manager server 431a is already operating on the management server 4a.

  Prior to program installation, necessary files are transferred from the management site 2000 to the management server 4a in advance. The necessary file group includes an install agent 132, an install agent control file 133, a communication program 134, a shutdown program 135, an installer program 141, and an install file group 142. A transfer protocol such as a file transfer protocol (ftp) is used for transferring these files. These files are temporarily stored in the local disk device of the management server 4a. In the installation agent control file 133, the administrator makes various settings for each computer in advance using the management console 4b.

  The program installation operation is performed by starting the browser 432b on the management console 4b and accessing the installation manager server 431a via the Internet 9. The specific processing contents executed for the installation are the first processing shown in FIGS. 9 and 12 except that the operation of the installation manager server on the management server 4a is performed via the Internet. Processing similar to the processing in the embodiment is performed.

  While the program is being installed, the management server 4a refers to the computer status table file 136 of each computer 2, and the work progress status and error in each computer 2 being installed by the progress status display program 4316. The occurrence status is transmitted to the management console 4b via the Internet 9. On the management console 4b, the progress status of the sent work and the error occurrence status are displayed on the display device by the browser 432b.

  According to the present embodiment, there is no restriction on the distance between the management console searched by the administrator and the place where the computer on which the program is installed is disposed, and installation by centralized control from a remote location can be realized. In this embodiment, the configuration of the user site 1000 and the installation process are the same as those in the first embodiment. However, the configuration of the user site 1000 and the installation process are the same as those in the second to fourth embodiments. It is also possible to conform to that.

  In the fifth embodiment, the method of performing the management such as the start control of the installation work and the progress monitoring has been described. In the following, a case where file transfer itself performed at the time of installation is performed intensively from a remote place will be described as a sixth embodiment.

  FIG. 21 is a simplified block diagram illustrating a configuration of a computer system according to the sixth embodiment. The user site 1001 and the management site 2001 are arranged at physically separated locations. The user site 1001 is provided with a computer system having a computer on which a program is installed. The computer system of the user site 1001 has the same configuration as that of the first embodiment. However, the storage 1a included in the user site 1001 has a remote copy function 126 described later in addition to the functions included in the storage 1 in the first embodiment. The management site 2001 includes a proxy computer 132x, a storage 1b, and a management console 4c. The proxy computer 132x, the storage 1b, and the management console 4c are connected to each other via the fiber channel connection device 3. The storage 1b provided in the management site 2001 has the same configuration as the storage 1a. The storage 1a and the storage 1b are connected via a wide-area communication path 9a realized by a network such as the Internet, a public line network, an ATM network, or a fiber channel. In the figure, the storage 1a and the storage 1b are directly connected, but they may be connected via a connection device such as a gateway or a router.

  The remote copy function 126 is a function for transferring data to other storages via the wide area communication path 9a. For example, when data is written from the management console 4 c to the storage 1 b of the management site 2001, the storage 1 b stores the write data in a disk device (LU) in the storage 1 b and also performs wide-area communication by the remote copy function 126. The same write data is transferred to the storage 1a of the user site 1001 via the path 9a. The storage 1a receives this write data by the remote copy function 126, writes the write data to the corresponding disk unit (LU) in the storage 1a, and transmits an end report to the storage 1b. The storage 1b has a management console at the time when the write processing in the storage 1b is completed (in the case of synchronous remote copy) or when the write processing in both the storage 1a and storage 1b is completed (in the case of asynchronous remote copy). An end report is returned to 4c. Prior to the execution of remote copy, it is necessary to create a pair by associating LUs that are targets of remote copy of the storage 1a, 1b. Further, prior to the execution of the write process, it is necessary to execute an initial copy that completely copies the data of one LU to the other LU and to keep the data consistent. All of these controls and data transfers are executed by the remote copy function 126.

  The installation process using the remote copy function will be described below. Here, in order to simplify the description, a case where a program is installed in one computer 2 will be described as an example. In the following description, it is assumed that the LU configurations of the storage at the user site 1001 and the management site 2001 are the same, and a pair is configured with each corresponding LU.

  In the preparatory work for installation in the present embodiment, first, the contents of the local LU 13 for the computer 2 to be installed are copied to the corresponding LU 13 in the storage 1b (hereinafter referred to as a mirror LU). Match the contents of. The mirror LU whose contents match is mounted as a local LU on the proxy computer 2x. The install manager 431 of the management console 4c distributes various file groups to the shared LU 14 of the storage 1b of the management site 2001 and the local LU (mirror LU) of the computer 2x, as in the fourteenth embodiment. In file group distribution, write access to the shared LU and mirror LU in the storage 1b occurs. At this time, the remote copy function 126 of the storage 1b executes data transfer to the corresponding LU in the storage 1a of the user site 1001. As a result, the result of file distribution at the management site 2001 is also reflected in the storage 1a of the user site 1001.

  In the installation execution work, the management site 2001 executes the installation in the local LU 13 (mirror LU) using the proxy computer 2x as in the first embodiment. As in the case of the previous preparation work, the data written to the mirror LU by the installation process is also written to the local LU 13 of the user site 1001, and as a result, the program is installed on the computer 2 of the user site 1001. It will be. Since the data copy between the storage 1a and the storage 1b is guaranteed by the remote copy function 126, if the installation at the management site 2001 is successful, the installation at the user site 1001 is also successful.

  Thus, according to the present embodiment, installation can be executed including not only various settings but also file transfer from a remote location. If settings for each computer are separately required on the user site side, the necessary settings may be made by using the same method as in the fifth embodiment. In addition, a plurality of proxy computers corresponding to a plurality of computers that are used to install the program at the user site are prepared on the management site side, and the installation process is performed using the plurality of proxy computers, thereby installing on the plurality of computers. It is also possible to perform processing in parallel.

  Furthermore, if the one-to-n direct installation described in the fourth embodiment is applied, a plurality of installations can be executed by one proxy computer. Similarly, if remote copy is performed between storage at a management site and storage at a plurality of user sites, installation can be performed simultaneously on a plurality of user sites by installation at one management site. . However, with these methods, initial copying cannot be performed for all LUs, so it is effective when it is desired to match the contents of all LUs, such as system installation that includes a new OS.

  Furthermore, in this embodiment, the installation process is performed using the remote copy function, but after the contents of the LU of the user site and the LU of the management site are matched, the installation work is performed in the management site. Installation can also be realized by copying the contents of the LU of the management site to the LU of the user site by initial copy again. In order to simplify the management site, the management site may be configured with a proxy computer and storage connected thereto. In this case, the program can be installed on the computer on the user site side by the remote copy function by installing the program on the proxy computer on the management site side by the same method as before.

It is a simple block diagram which shows the structure of the computer system in one Embodiment of this invention. 3 is a simplified block diagram showing a configuration of a computer 2. FIG. 2 is a simplified block diagram showing a configuration of a storage 1. FIG. It is a table block diagram which shows an example of a LUN management table. It is explanatory drawing of the program and file which are stored in local LU. It is explanatory drawing of the program etc. which are stored in shared LU14. 3 is a simplified block diagram showing a configuration of a management console 4. FIG. 3 is a conceptual diagram showing a configuration of an installation manager 431. FIG. It is a flowchart of the process performed as installation preparation work. It is a conceptual diagram which shows an example of a format of a remote power-on packet. It is a file block diagram which shows the structure of an installation agent control file. It is a flowchart which shows the flow of the execution work of installation. It is a table block diagram which shows an example of a computer status table file. It is explanatory drawing about the definition of the status set to a computer status table file. It is a block diagram of a computer status table list. It is a simple block diagram which shows the structure of the computer in 2nd Embodiment. It is a format figure which shows an example of a remote power on frame. It is a simple block diagram which shows the structure of the computer system in 3rd Embodiment. It is a flowchart which shows the flow of the process implemented by the installer program of 3rd Embodiment. It is a simple block diagram which shows the structure of the computer system in 5th Embodiment. It is a simple block diagram which shows the structure of the computer system in 6th Embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... Storage 2a, 2b, 2n ... Computer 3 ... Fiber channel connection apparatus 4 ... Management console 13a, 13b, 13n ... Local LU
14 ... Shared LU
132: Installation agent program 133 ... Installation agent control file 136 ... Computer status table file 141 ... Installation program 142 ... Installation file group 431 ... Installation manager program

Claims (2)

A first computer; a second computer; a management computer operated by an operator to install a program; and a storage device connected to the first computer, the second computer, and the management computer A system program installation method having a system,
  The storage system includes a shared logical unit accessed from each of the first computer, the second computer, and the management computer, a first logical unit accessed from the first computer, and the second logical unit. A second logical unit accessed from a computer of
  The storage system receives a link setting request from the management computer and sets a link used when the program is installed between the first logical unit and the second logical unit. When,
  The storage device system receiving a command from outside the storage device system and reading an installer program stored in the shared logical unit;
  The storage system executes the installer program, reads the program stored in the shared unit, and stores the read program in the first logical unit;
  A program installation method comprising the step of the storage device system storing the read program in the second logical unit according to the link. A first system program installation method comprising: a first computer; a second computer; and a first storage device system connected to the first computer and the second computer,
  The first storage device system includes a first logical unit accessed from the first computer, and a second logical unit accessed from the second computer,
  Here, a second computer having a third computer, a second storage system connected to the third computer, and a management computer connected to the third computer and the second storage system. A data transfer unit for copying data between a logical unit of the first storage device system and a logical unit of the second storage device system, the system being provided apart from the first system; , Provided in the first storage device system and the second storage device system,
  In the second storage device system, the second storage device system includes a first shared logical unit, a third logical unit corresponding to the first logical unit, and the second logical unit. Providing a corresponding fourth logical unit;
  The second storage system receives a link setting request from the management computer and sets a link used when installing a program between the third logical unit and the fourth logical unit; ,
  The second storage system receiving a command from outside the second storage system and reading an installer program stored in the first shared logical unit;
  The second storage system executing the read installer program, reading the program stored in the first shared unit, and storing the read program in the third logical unit;
  The second storage device system storing the read program in the fourth logical unit according to the link;
  Copying the contents of the third logical unit to the first logical unit by the data transfer unit; and
  And copying the contents of the fourth logical unit to the second logical unit by the data transfer unit.

Images