JP2007183747A - Method and system for system movement between physical servers - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To facilitate system movement between different physical servers. <P>SOLUTION: A management server 102 communicates with an OS information acquisition agent 111 of a moving originating server 110 to acquire system configuration information of the moving source server 110 and stores the information in a table. The server further acquires device information of a moving destination server 112 regardless of presence/absence of OS by transferring a network agent to the moving destination server 112 by network boot, and stores it in a table. The server successively compares both the servers and outputs difference information to a console 101 to ask for determination of a manager. After confirmation by the manager, application of driver or takeover of setting information is performed according to the differencial information for a disk image copied to the moving destination server 112. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a method for supporting application of a driver that is newly required in a movement destination server and taking over of setting information when moving a system between different physical servers.

  If you want to run a server running an application or OS (Operating System) on a higher-performance server, or if you want to run a server hardware failure and other servers, Need to move (migrate) to another different server. In such cases, there are two main ways to move the server environment.

  One is a method of moving only an application to another server. The system can be restarted by installing an OS as an application execution base in advance on the destination server and moving only the application to the destination server. However, when the migration destination OS is different from the migration source, it is necessary to manually correct the interface difference with the OS used by the application. As a prior art for automating this, Patent Document 1 provides a migration processing system between heterogeneous systems by using a restoration processing function for application resources to be migrated, and reduces the burden on the administrator. A possible method is described. Here, the server environment or system mainly refers to an application, an OS, setting information, and the like.

As a second movement method, there is movement using server virtualization. Server virtualization is a technology for building a plurality of virtual servers by dividing resources such as processors and memories of a physical server. In general, a virtual server can generate a specific hardware environment by an emulation mechanism included in server virtualization. That is, even if the hardware environment of the physical server is different, the hardware of the virtual server generated by the emulation mechanism of server virtualization can maintain uniformity. By using this characteristic, virtual servers can be operated on different physical servers, and the environment of the virtual server can be moved without depending on the hardware configuration of the physical server (see Patent Document 2). With this method, not only the application but also the entire system environment can be moved.
JP-A-8-272600 JP 2005-173751 A

The above prior art is a technique for moving application resources in a system to a heterogeneous system, but is a movement technique limited to applications, and does not consider the movement of the entire system environment used on the movement source server. . In addition, an environment where an application can be executed needs to be constructed in advance on the destination server, and environment setting work occurs.
Moreover, there is a virtual server function as an existing technology that provides a function of moving the entire system environment to another server. Since the virtual server has a uniform hardware configuration of the destination server, the migration process is easy. However, the virtual server function provides a movement function from a physical server to a virtual server, and does not target system movement between different physical servers. When moving a system between different physical servers, it is necessary to grasp the hardware configuration of the destination server in advance, and it becomes difficult to move the system compared to the virtual server function.
An object of the present invention is to provide means capable of easily moving a system between different physical servers.

  The present invention was devised to solve the above-mentioned problem, and the present invention is based on the first server and the second server by the management server connected to the second server. The management server stores management information of the first server including hardware information of the first server, driver information corresponding to the hardware, and driver setting information. A storage unit and a processing unit, wherein the processing unit transfers an agent to the second server via a network, and the agent includes a second piece of hardware information included in the second server. Server management information is acquired, the management information of the first server is compared with the management information of the second server, and the system moving procedure is determined.

  According to such a configuration, the processing unit of the management server transfers the agent to the second server, and acquires the management information of the second server including the hardware information of the second server by the agent, Since the management information of the first server and the management information of the second server can be compared to determine the system migration procedure, the system can be easily migrated from the first server to the second server. Can be done.

Further, the present invention is a system migration method to the migration destination server by a management server connected to the migration destination server, wherein the management server corresponds to hardware information of the migration source server and the hardware. System disk system storing management information of the migration source server including driver information and driver setting information, management information of the migration destination server including hardware information of the migration destination server, and the OS of the migration source server A storage unit for storing the disk image, and a processing unit. When the processing unit moves the system disk image to the migration destination server, the management information of the migration source server and the management of the migration destination server Based on the information, a hardware difference is detected, and it is determined whether or not the system disk image needs to be changed. It was.

  According to such a configuration, the processing unit of the management server detects a hardware difference based on the management information of the migration source server and the management information of the migration destination server, and determines whether the system disk image needs to be changed. Since the determination can be made, the system can be easily moved from the source server to the destination server.

  According to the present invention, it is possible to easily move a system between different physical servers and without knowing in advance the hardware configuration of the destination server.

Embodiments of the present invention will be described below in detail with reference to the drawings.
FIG. 1 shows an overall view of a system configuration in the present invention. The system migration system includes a management server 102, a migration source server 110, and a migration destination server 112. The center of control in the present invention is the management server 102. The management server 102 includes a configuration information acquisition mechanism 103, a configuration information check mechanism 104, a configuration change mechanism 105, a migration source server management table 106, a migration destination server management table 107, and a driver storage disk 108. The management targets of the management server 102 are the network switch 109, the migration source server 110, the OS information acquisition agent 111, and the migration destination server 112. The migration source server 110 and the migration destination server 112 exist separately as physical devices. In this embodiment, the system running on the server 110 is moved to the server 112, and the driver settings required for the moved server and the inheritance of configuration information such as an IP (Internet Protocol) address are taken over. Provide the administrator with a function to support

  The management server 102 includes, for example, a storage unit (not shown) and a processing unit (not shown). When the processing unit executes a program of the management server 102 stored in the storage unit, the management server 102 Each function can be realized.

  FIG. 2 shows a configuration of a server that is a management target in the present invention. The source server 110 (destination server 112) includes a memory 202, an application 203, a driver 204, a driver 206, driver setting information 205, driver setting information 207, a processor 208, an HBA (Host Bus Adapter) 209, an NIC (Network Interface Card). ) 210 and the OS / application storage disk 302 (303). The source server 110 (destination server 112) is connected to the network 212. In the present embodiment, processing is performed on the driver 204 and driver 206, the driver setting information 205, and the driver setting information 207, which are components of the server 110 (112). The HBA 209 is not limited to this, and an FCA (Fibre Channel Adapter) or the like may be used instead.

  FIG. 3 shows the flow of processing in the present invention. The management server 102 acquires configuration information from the migration source server 110 and the migration destination server 112 via the configuration information acquisition mechanism 103. When the acquisition of the configuration information is completed, the configuration information check mechanism 104 compares the configuration information of the migration source server 110 and the migration destination server 112 and extracts the difference. When the extraction of the difference is completed, the configuration change mechanism 105 copies the disk image including the driver storage unit 108a from the OS / application storage disk 302 of the migration source server 110 and stores it in the OS / application storage disk 301 after the configuration change. . Here, the disk image is used to handle an actual disk state as one file. Subsequently, the configuration change mechanism 105 allows the driver of the OS / application storage disk 301 after the configuration change so that the acquired disk image can be moved to the migration destination server 112 based on the difference in the configuration information extracted by the configuration information check mechanism 104. The storage unit 108b is changed. When adding or changing a driver, a necessary driver is acquired from the driver storage disk 108 (see FIG. 1) and applied to the driver storage unit 108b of the OS / application storage disk 301 after the configuration change. When deleting a driver, an unnecessary driver is deleted from the driver storage unit 108b of the OS / application storage disk 301 after the configuration change. The configuration change mechanism 105 copies the disk image stored in the OS / application storage disk 301 after the configuration change to the OS / application storage disk 303 of the migration destination server 112. By this processing, the system movement from the movement source server 110 to the movement destination server 112 is completed.

  FIG. 4 shows an example of the source server management table 106 (see FIG. 1) that stores the configuration information acquired from the source server 110 (see FIG. 3) by the configuration information acquisition mechanism 103 (see FIG. 3). . The migration source server management table 106 includes columns of a server identifier 401, an OS 402, a device 403, device information 404, driver information 405, setting information 406, and a device role 407. The server identifier 401 stores a name for identifying the source server 110 (see FIG. 3) that acquired the configuration information. The OS 402 stores the name of the OS running on the migration source server 110 (see FIG. 3). The device 403 stores names (device types) of various devices used in the migration source server 110 (see FIG. 3). In the device information 404, information corresponding to the device 403 is stored. The hardware information includes a device 403 and device information 404. For example, when the device is a NIC, a MAC (Media Access Control) address and a revision number are stored. When the device is an HBA, a WWN (World Wide Name) and a revision number are stored. The MAC address and WWN are identifiers possessed by the NIC and HBA. In this way, by holding detailed hardware information such as the device revision number, it becomes possible to know in detail the differences during movement. The driver information 405 stores the name of the driver corresponding to the device 403. The setting information 406 stores setting information corresponding to the device 403. For example, when the device is a NIC, the IP address set in the NIC is stored. The device role 407 stores the name of the role in the source server 110 (see FIG. 3) corresponding to the device 403. For example, when the device is a NIC and is used as a management network, the name “management network” is stored as a device role. The management network is a network that is used for server power control and hardware event information transfer, etc., and is separated from the business network used by business applications to ensure network security and avoid network traffic congestion. Built as a purpose. In general, a server has a management network NIC and a business network NIC, and is constructed by a network segment. Normally, the management server 102 is constructed so as to belong to the same network segment as the management network. When the server has a plurality of NICs, this table has information indicating which NIC is the management server. This information is used to automatically set the role of the NIC that the destination server described later has.

  FIG. 5 shows an example of the migration destination server management table 107 (see FIG. 1) that stores the configuration information acquired from the migration destination server 112 by the configuration information acquisition mechanism 103. The destination server management table 107 includes columns of a server identifier 501, a device 502, device information 503, and a device role 504. The server identifier 501 stores a name for identifying the destination server that acquired the configuration information. The device 502 stores names of various devices used in the destination server 112 (see FIG. 3). In the device information 503, information corresponding to the device 502 is stored. For example, the MAC address and revision number are stored when the device is a NIC, and the WWN and revision number are stored when the device is an HBA. The device role 504 stores the name of the role in the destination server corresponding to the device 502. For example, when the device is a NIC and is used as a management network, the name “management network” is stored as a device role.

  FIG. 6 shows the configuration content of the configuration information acquisition mechanism 103 that performs processing when acquiring configuration information from the migration source server 110 and the migration destination server 112. The configuration information acquisition mechanism 103 includes a migration source server configuration information acquisition unit 601, a migration destination server configuration information acquisition unit 602, a network agent management unit 603, and a work area 604. The configuration information acquisition mechanism 103 communicates with the OS information acquisition agent 111 of the source server 110 via the source server configuration information acquisition unit 601 when acquiring the configuration information from the source server 110. Here, the source server configuration information acquisition unit 601 acquires configuration information from the source server 110 and stores it in the source server management table 106 (see FIG. 1). The NIC used for communication with the OS information acquisition agent 111 is regarded as a management network, and the configuration information acquisition mechanism 103 adds the information (OS information acquisition agent) to the source server management table 106 (see FIG. 1) as additional information. 111) (information that the NIC used for communication with 111 is a management network) is stored. When the configuration information acquisition mechanism 103 acquires configuration information from the destination server 112, the destination server configuration information acquisition unit 602 cooperates with the network agent management unit 603 to transfer the network agent to the destination server 112. At this time, by transferring the network agent to the migration destination server 112 by network boot, the configuration information can be acquired even when the OS is not installed in the migration destination server 112. The network boot is a function of the NIC, and indicates a function of transferring a program necessary for booting from the NIC from the network agent management unit 603 and executing it when the destination server 112 is powered on. Since the network boot can operate using only the memory of the destination server 112, information can be collected without changing the configuration of the destination server 112. After the transfer of the network agent is completed, the destination server configuration information acquisition unit 602 communicates with the network agent, acquires device information from the destination server 112, and stores it in the destination server management table 107 (see FIG. 1). To do. Note that the NIC used for communication with the network agent is regarded as a management network, and the configuration information acquisition mechanism 103 stores the information as additional information in the destination server management table 107 (see FIG. 1). Further, the network agent transferred to the destination server 112 stays at the destination server 112 in preparation for processing when the system is moved. The work area 604 is used in the processing of the migration source server configuration information acquisition unit 601 and the processing of the migration destination server configuration information acquisition unit 602. These processes will be described with reference to FIGS. 7 and 8, respectively.

  FIG. 7 shows a flow when the source server configuration information acquisition unit 601 (see FIG. 6) performs processing. Here, description will be made with reference to FIGS. 1 and 6 as appropriate. The source server configuration information acquisition unit 601 receives an acquisition request from the configuration information acquisition mechanism 103 in step S701. In step S702, communication is performed with the OS information acquisition agent 111 of the migration source server. In step S703, the MAC address of the NIC used for communication with the migration source server 110 (OS information acquisition agent 111) is stored in the work area 604 as a management network. In step S704, device information of the migration source server 110 is acquired via the OS information acquisition agent 111. In step S705, the setting information of the migration source server 110 is acquired via the OS information acquisition agent 111. In step S706, the acquired server configuration information is stored in the source server management table 106. If the information stored in the source server management table 106 is information about the NIC and the MAC address of the NIC matches the MAC address stored in step S703, the source server configuration information acquisition unit 601 Enter “management network” in the “device role” field of the management table 106 (set a flag). In step S707, it is determined whether or not all configuration information has been acquired from the migration source server 110. If there is information that has not yet been acquired (NO in step S707), the process returns to step S704. If all the configuration information has been acquired (YES in step S707), the process ends.

  FIG. 8 shows a flow when the migration destination server configuration information acquisition unit 602 (see FIG. 6) performs processing. Here, description will be made with reference to FIGS. 1 and 6 as appropriate. The migration destination server configuration information acquisition unit 602 receives an acquisition request from the configuration information acquisition mechanism 103 in step S801. In step S802, in cooperation with the network agent management unit 603, the network agent is transferred to the migration destination server 112 by network boot. In step S803, communication is performed with the transferred network agent. In step S804, the MAC address of the NIC used for communication with the network agent is stored in the work area 604 as a management network. In step S805, device information is acquired from the destination server 112. In step S806, the acquired device information is stored in the destination server management table 107. If the information stored in the destination server management table 107 is information about the NIC and the MAC address of the NIC matches the MAC address stored in step S804, the destination server configuration information acquisition unit 602 Enter “management network” in the “device role” field of the management table 107. In step S807, it is determined whether or not all device information has been acquired from the destination server 112. If there is information that has not yet been acquired (NO in step S807), the process returns to step S805. If all the configuration information has been acquired (YES in step S807), the process ends.

  FIG. 9 shows a flow when the configuration information check mechanism 104 (see FIG. 3) performs processing. Here, description will be made with reference to FIGS. 1 and 6 as appropriate. The configuration information check mechanism 104 receives a check request from the configuration information acquisition mechanism 103 in step S901. In step S902, the source server management table 106 and the destination server management table 107 are compared. In step S903, as a result of comparing the migration source server management table 106 and the migration destination server management table 107, it is determined whether there is information that matches the contents. If there is information whose contents match (YES in step S903), the process proceeds to step S904. If there is no information whose contents match (NO in step S903), the process proceeds to step S905. In step S904, information whose contents match is stored in a temporary table (not shown), and “no change” is entered in the “change contents” column. In step S905, as a result of comparing the migration source server management table 106 and the migration destination server management table 107, it is determined whether there is information with the same device type entered in the “device” column. If information of the same device type exists (YES in step S905), the process proceeds to step S906. If no information with the same device type exists (NO in step S905), the process advances to step S907. In step S906, information that matches the device type is stored in the temporary table, and “driver change” is entered in the “change contents” field. As a result of comparing the source server management table 106 and the destination server management table 107 in step S907, it is determined whether or not there is information on a device that exists in the source server 110 but not in the destination server 112. . If there is information on a device that does not exist in the destination server 112 (YES in step S907), the process proceeds to step S908. If there is no device information that does not exist in the destination server 112 (NO in step S907), the process advances to step S909. In step S908, information on devices that do not exist in the migration destination server 112 is stored in the temporary table, and “driver deletion” is entered in the “change contents” column. In addition, enter “device check required” in the “notification to administrator” field. In step S909, information that does not apply to any of the determinations in step S903, step S905, and step S907 is stored in the temporary table, and “driver added” is entered in the “change contents” column. In step S910, it is determined whether all of the migration source server management table 106 and the migration destination server management table 107 have been checked. If not all are checked (NO in step S910), the process returns to step S902. If all have been checked (YES in step S910), the process proceeds to step S911. In step S911, the information stored in the temporary table is displayed on the console 101.

  FIG. 10 shows an output example when the device difference between the migration source server 110 (see FIG. 1) and the migration destination server 112 (see FIG. 1) is displayed on the console 101 (see FIG. 1). Here, description will be given with reference to FIG. The table displayed on the console 101 includes columns of a device 1001, device information 1002, driver information 1003, setting information 1004, device role 1005, change content 1006, and notification 1007 to the administrator. The device 1001 stores the names of various devices used by the migration source server 110 or the migration destination server 112. In the device information 1002, information corresponding to the device 1001 is stored. For example, the MAC address and revision number are stored when the device is a NIC, and the WWN and revision number are stored when the device is an HBA. The driver information 1003 stores the name of the driver corresponding to the device 1001. Setting information corresponding to the device 1001 is stored in the setting information 1004. For example, when the device is a NIC, the IP address set in the NIC is stored. The device role 1005 stores the name of the role in the destination server 112 corresponding to the device 1001. For example, when the device is a NIC and is used as a management network, the name “management network” is stored as the device role 1005. The change content 1006 stores the change content to be executed when the disk image of the source server 110 is moved to the destination server 112. As an example, when the NIC used as the management network is different between the migration source server 110 and the migration destination server 112, the character string “driver change” is stored. The notification 1007 to the administrator stores notification items to the administrator who moves the system of the server. As an example, if the migration source server 110 uses a NIC and the migration destination server 112 does not have a NIC, the NIC driver used in the migration source server 110 is not required in the migration destination server 112, so Is stored with a character string “delete driver”. However, if the NIC is necessary for system operation in the movement source server 110, the character string “device check required” is stored in the notification 1007 to the administrator because there is a possibility that it cannot be used correctly even if the system is moved. . The administrator confirms that there is no problem in the system movement process based on the display content of the console 101, and then starts the movement process.

  FIG. 11 shows a flow when the configuration changing mechanism 105 (see FIG. 1) performs processing. Here, description will be given with reference to FIG. The configuration change mechanism 105 receives a change request from the configuration information acquisition mechanism 103 in step S1101. In step S1102, a disk image is acquired from the migration source server 110. In step S1103, the network agent (of the migration destination server 112) is requested to copy the disk image acquired in step S1002 to the migration destination server 112. In step S 1104, the driver and setting information necessary for the destination server 112 are acquired in cooperation with the configuration information check mechanism 104. In step S1105, the network agent is requested to change the system configuration of the destination server 112. In step S1106, it is determined whether all the system configuration changes of the destination server 112 have been completed. If all system configuration changes have been completed (YES in step S1106), the process proceeds to step S1107. If all system configuration changes have not been completed (NO in step S1106), the process returns to step S1105. In step S1107, the network agent is requested to restart the destination server 112. When the system is moved, it is possible to prioritize the association of the devices with the matching flags using the flags set in the movement source server management table 106 and the movement destination management server table 107. For example, the management server 102 confirms that the “management network” flag is set for the device whose device 403 (see FIG. 4) is “NIC1” and the device 502 (see FIG. 5) is “NIC2”. It is possible to prioritize detection and movement of this device.

  FIG. 12 shows a flow when the network agent performs processing. Here, description will be given with reference to FIG. In step S1201, the network agent receives a request from the configuration information acquisition mechanism 103 or the configuration information check mechanism 104. In step S1202, it is determined whether the received request is a configuration information acquisition request. If it is a configuration information acquisition request (YES in step S1202), the process advances to step S1203. If it is not a configuration information acquisition request (NO in step S1202), the process proceeds to step S1204. In step S1203, configuration information (setting information) is acquired from the destination server 112. In step S1204, it is determined whether the received request is a disk image copy request. Here, the copy of the disk image means copying from the OS / application storage disk 302 (see FIG. 3) to the OS / application storage disk 303 (see FIG. 3). If it is a disk image copy request (YES in step S1204), the process advances to step S1205. If it is not a disk image copy request (NO in step S1204), the process advances to step S1206. In step S1205, the disk image is copied. Here, the execution of copying of the disk image refers to the OS / application storage disk 302 (see FIG. 3) to the OS / application storage disk 301 (see FIG. 3), and the OS / application storage disk 301 (see FIG. 3) to the OS. / It means copying sequentially to the application storage disk 303 (see FIG. 3). In step S1206, it is determined whether the received request is a disk image configuration change request. If the request is a configuration change request (YES in step S1206), the process advances to step S1207. If it is not a configuration change request (NO in step S1206), the process advances to step S1208. In step S1207, the configuration information for the destination server 112 is changed. When the setting information of the movement source server 110 is taken over, the setting information 1004 (see FIG. 10) is referred to, and the setting information such as the IP address of the movement destination server 112 is the same as that of the movement source server 110 according to the referred result. Change to content. In step S1208, it is determined whether the accepted request is a restart request. If it is a restart request (YES in step S1208), the process advances to step S1209. If it is not a restart request (NO in step S1208), the process returns to step S1201. In step S1209, the destination server 112 is restarted.

  FIG. 13 shows an overall view when components necessary for the OS migration function are added to the system configuration of the present invention shown in FIG. The center of control is the management server 102. The management server 102 includes a configuration information acquisition mechanism 103, a configuration information check mechanism 104, a configuration change mechanism 105, a migration source server management table 106, a migration destination server management table 107, an OS migration information management table 1301, and a driver storage disk 108. The The management targets of the management server 102 are the network switch 109, the migration source server 110, the OS information acquisition agent 111, and the migration destination server 112. The system shown in FIG. 13 performs an operation of moving a system operating on the migration source server 110 to the migration destination server 112, and also includes configuration information such as driver settings and IP addresses necessary for the moved server. Is provided to the administrator with the function of supporting the takeover of the OS and the version upgrade of the OS.

  FIG. 14 shows an example of the OS migration management table 1301 (see FIG. 13). Here, description will be made with reference to FIG. 13 as appropriate. The OS migration management table 1301 includes columns of a migration source OS 1401, a migration destination OS 1402, and a kernel / driver storage destination 1403. The migration source OS 1401 stores information on the OS used by the migration source server 110. The migration destination OS 1402 stores a post-migration OS list in the case where migration to another OS is possible by changing the OS kernel information and driver stored in the migration source OS 1401. The kernel / driver storage location 1403 stores storage locations of kernel files and drivers that need to be changed in order to move the OS. Note that the contents of the OS migration information management table 1301 are fixed and are already owned by the management server 102. For example, in the process of the configuration information check mechanism 104 shown in FIG. 9, the function that supports the OS version upgrade outputs the contents of the OS migration information management table 1301 to the console 101 after the process of step S <b> 901. If there is a version upgrade instruction from, it can be realized by changing the OS kernel information and driver stored in the migration source OS 1401 to make it possible to migrate to another OS.

  As described in the present embodiment, the management server 102 stores management information of the migration source server 110 including hardware information of the migration source server 110, driver information corresponding to the hardware, and driver setting information. A storage unit and a processing unit, and the processing unit transfers the OS information acquisition agent 111 to the migration destination server 112 via the network, and the agent includes a migration destination including hardware information of the migration destination server 112 The management information of the server 112 is acquired, the management information of the migration source server 110 and the management information of the migration destination server 112 are compared, and the system migration procedure is determined.

  According to such a configuration, the processing unit of the management server 102 transfers the agent to the migration destination server 112, and the management information of the migration destination server 112 including the hardware information of the migration destination server 112 is transmitted by the agent. Since it is possible to acquire and compare the management information of the migration source server 110 and the management information of the migration destination server 112 to determine the system migration procedure, the migration of the system from the migration source server 110 to the migration destination server 112 is easy. Can be performed. By comparing the management information of the migration source server 110 and the management information of the migration destination server 112, it is possible to determine and apply the driver to be applied at the migration destination and the setting information to be taken over. Furthermore, since the OS is not installed on the migration destination server, device information can be acquired regardless of the presence or absence of the OS by transferring the network agent to the migration destination server using the network boot function. .

  The management server 102 also includes management information of the migration source server 110 including hardware information of the migration source server 110, driver information and driver setting information corresponding to the hardware, and hardware of the migration destination server 112. A storage unit that stores management information of the migration destination server 112 including information, a system disk image of a system disk in which the OS of the migration source server 110 is stored, and a processing unit, and the processing unit stores the system disk image When moving to the migration destination server 112, a hardware difference is detected based on the management information of the migration source server 110 and the management information of the migration destination server 112, and it is determined whether or not the system disk image needs to be changed. It is the structure to do.

  According to such a configuration, the processing unit of the management server 102 detects a hardware difference based on the management information of the migration source server and the management information of the migration destination server, and whether the system disk image needs to be changed. Therefore, it is possible to easily move the system from the movement source server to the movement destination server.

  The present embodiment can also be applied to a case where the source server 110 and the destination server 112 are the same server. For example, the management server 102 backs up a system disk image, changes the hardware state of the server, and then backs up the system disk in case a hardware failure of the server to be managed occurs. This can be applied to returning an image to the server, and the system can be easily returned.

1 shows the overall configuration of a system according to the present invention. 1 shows the overall configuration of a server to be managed in the present invention. The flow of the system movement process in this invention is shown. 6 shows a table for storing system configuration information acquired from a source server by a configuration information acquisition mechanism. The structure information acquisition mechanism shows the table which stores the device information acquired from the movement destination server. The relationship between the configuration content of the configuration information acquisition mechanism and the server to be managed is shown. The flowchart at the time of a movement origin server structure information acquisition part performing a process is shown. The flowchart at the time of a movement destination server structure information acquisition part performing a process is shown. The flowchart at the time of a structure information check mechanism performing a process is shown. The following is an output example when device differences between servers are output to the console. The flowchart at the time of a structure change mechanism performing a process is shown. The flowchart at the time of a network agent performing a process is shown. The entire system configuration when an OS migration information management table is added is shown. An OS movement information management table is shown.

Explanation of symbols

DESCRIPTION OF SYMBOLS 101 Console 102 Management server 103 Configuration information acquisition mechanism 104 Configuration information check mechanism 105 Configuration change mechanism 106 Migration source server management table 107 Migration destination server management table 108 Driver storage disk 109 Network switch 110 Migration source server 111 OS information acquisition agent 112 Migration destination Server 1301 OS migration information management table

Claims (20)

A system migration method from the first server to the second server by a management server connected to the first server and the second server,
The management server processes information, and a storage unit that stores management information of the first server including hardware information of the first server, driver information corresponding to the hardware, and driver setting information A processing unit,
The processor is
Transferring an agent to the second server via a network;
Via the agent, obtaining management information of the second server including hardware information of the second server;
A system migration method between physical servers, comprising comparing the management information of the first server and the management information of the second server and determining a system migration procedure. The processor is
When determining the procedure for moving the system, the management information of the first server is compared with the management information of the second server, a hardware difference is detected, and the management information of the first server is The system movement method between physical servers according to claim 1, wherein the driver information newly determined for the second server is determined with reference to the system. The processor is
Based on the determined system migration procedure, a system disk image is extracted from the system disk storing the OS of the first server, and the system disk is based on the newly determined driver information. The system migration method between physical servers according to claim 2, wherein a driver is added to the image, and the system disk image is copied to the system disk of the second server. The processor is
When copying the system disk image to the system disk of the second server, the driver in which the setting information of the added driver is described is searched from the management information of the first server, and the first corresponding to the driver is searched. The system migration method between physical servers according to claim 3, wherein the setting information of the driver of the second server is changed. The agent executed on the second server is:
The identifier of the network interface device of the second server used by the agent is acquired, information about the network interface device is searched from the hardware information in the management information of the second server, and the identifier corresponds to the identifier The method for moving a system between physical servers according to any one of claims 1 to 4, wherein a flag for specifying a use of the network interface is set in the information related to the network interface device. The management information of the first server has a flag that identifies the use of the network interface,
The processor is
6. The system is moved from the first server to the second server with priority given to association of devices having the same flag based on the determined system movement procedure. A method for moving a system between physical servers as described in 1. The processor is
The method of moving a system between physical servers according to any one of claims 2 to 4, wherein the determined driver information is displayed on a console. The management information of the first server is
Further includes information on an OS running on the first server;
The storage unit
OS migration information management information including the type of the OS of the migration source and the type of OS that can be changed is further included.
The processor is
When changing the type of OS running on the first server and moving to the second server,
Obtaining OS information running on the first server, searching for a changeable OS type from the OS migration information management information based on the OS information, and determining a changeable OS candidate. The method of moving a system between physical servers according to any one of claims 1 to 7. A system migration method to a migration destination server by a management server connected to a migration destination server as a migration destination of the system,
The management server
Management information of the source server including hardware information of the source server, driver information corresponding to the hardware, and driver setting information;
Management information of the destination server including hardware information of the destination server;
A storage unit that stores a system disk image of a system disk in which the OS of the migration source server is stored, and a processing unit that processes information,
The processor is
A physical difference is detected based on the management information of the migration source server and the management information of the migration destination server, and it is determined whether the system disk image needs to be changed. System movement method. The processor is
When it is determined that the system disk image needs to be changed, the driver information newly determined for the destination server is determined with reference to the management information of the source server. Item 10. A method for moving a system between physical servers according to Item 9. The processor is
When moving the system to the destination server,
The system migration method between physical servers according to claim 10, further comprising: adding a driver to the system disk image based on the determined newly necessary driver information. The processor is
When moving the system to the destination server,
12. The driver setting information of the added driver is searched from the management information of the source server, and the driver setting information of the destination server corresponding to the driver is changed. A method of moving a system between the described physical servers. The system disk image stored in the storage unit is
The system migration method between physical servers according to any one of claims 9 to 12, wherein the processing unit is backed up from the migration source server. The management information of the destination server including the hardware information of the destination server is
The processing unit is
Transfer the agent to the destination server via a network;
The system migration method between physical servers according to any one of claims 9 to 13, wherein the system migration method is obtained via the agent. The agent executed on the destination server is:
The network interface device corresponding to the identifier is obtained by acquiring an identifier of the network interface device of the destination server used by the agent, searching for information on the network interface device from the hardware information in the management information of the destination server The system migration method between physical servers according to claim 14, wherein a flag that identifies a use of the network interface is set in the information related to the device. The management information of the source server has a flag that identifies the use of the network interface,
The processor is
The system migration method between physical servers according to claim 15, wherein the system is migrated to the migration destination server with priority given to the association of the devices having the same flag. The processor is
The method of moving a system between physical servers according to any one of claims 10 to 12, wherein the determined driver information is displayed on a console. The management information of the source server is
It further has information on the OS running on the source server,
The storage unit
OS migration information management information that includes the type of OS that can be migrated and the type of OS that can be changed,
The processor is
When moving to the destination server by changing the type of OS running on the source server,
Acquiring OS information running on the migration source server, searching for a changeable OS type from the OS migration information management information based on the OS information, and determining a changeable OS candidate. The method of moving a system between physical servers according to any one of claims 9 to 17. A system movement system including a first server, a second server, and a management server connected to the first server and the second server,
The management server processes information, and a storage unit that stores management information of the first server including hardware information of the first server, driver information corresponding to the hardware, and driver setting information A processing unit,
The processor is
Transferring an agent to the second server via a network;
Via the agent, obtaining management information of the second server including hardware information of the second server;
A system migration system between physical servers, wherein the management information of the first server and the management information of the second server are compared to determine a system migration procedure. The processor is
When determining the procedure for moving the system, the management information of the first server is compared with the management information of the second server, a hardware difference is detected, and the management information of the first server is Referring to and determining newly required driver information for the second server,
Based on the determined system migration procedure, a system disk image is extracted from the system disk storing the OS of the first server, and the system disk is based on the newly determined driver information. The system migration system between physical servers according to claim 19, wherein a driver is added to the image and the system disk image is copied to the system disk of the second server.

Images