JP6278938B2 - Storage management device, storage management method, and program - Google Patents

Description

  The present invention relates to a storage management device, a storage management method, and a program.

  In recent years, there has been known a server virtualization technology that virtually creates a computing environment as if there are a plurality of server machines in one physical server. Each of the virtually created computing environments is called a “virtual server” or “virtual machine”. A virtual server and a virtual machine are realized by reading what is stored in a storage as a virtualization software for constructing them into a computer such as a physical server.

  With regard to virtualization technology, for example, in Patent Document 1, the arrangement of virtual machines is calculated so that the resource consumption of a physical machine is equal to or less than a resource threshold, and a plurality of virtual machines are provided to realize the calculated arrangement of virtual machines. A technique for reducing the movement cost by moving between physical machines is disclosed.

  For example, Patent Document 2 discloses a technique for scheduling the movement of a virtual machine so that the load is not biased in the network in order to distribute the load of the entire system and efficiently and safely arrange virtual machines. ing.

  As described above, a technique for leveling data bias between nodes such as physical machine resources and storage has been conventionally known.

International Publication No. 2014/192132 JP 2010-117760 A

  By the way, for example, when the virtual server is migrated from the migration source storage to the migration destination storage when the storage is leveled, the virtual server may be temporarily stopped. For this reason, when leveling, it is necessary to have a person in charge managing the virtual server to be migrated stand by in preparation for the stop of the virtual server.

  On the other hand, the administrator for storage leveling must select a virtual server to be migrated from the migration source storage, schedule a leveling schedule, and manage each virtual server to be migrated before leveling. The person in charge must be contacted. For this reason, man-hours and time are required for leveling.

  The present invention has been made in view of such circumstances, and an object of the present invention is to provide a storage management apparatus that can reduce the man-hours and time required for leveling storage.

  In order to solve the above problems, the storage management apparatus of the present invention is used by a virtual server management apparatus that manages a plurality of virtual servers that are read from storage and executed on a physical server, and a person in charge of the virtual server. A storage management apparatus connected to the person-in-charge terminal and the network, the storage means for storing the contact information of the person in charge in charge of the virtual server, and the free space of the first storage reaches a predetermined threshold; The identification information for identifying each virtual server stored in the storage and the storage size of each virtual server are acquired from the virtual server management device, and the migration target virtual server to be migrated to the second storage is extracted based on at least the storage size Set the migration start date and time for the migration target virtual server, and contact the person in charge of the migration target virtual server A virtual server that transmits a migration notification inquiring whether or not to migrate the server to the second storage at the migration start date and time, and that migrates according to the response received from the person-in-charge terminal used by the person in charge who has transmitted the migration notification A schedule management unit that creates a schedule for migrating to the second storage at the migration start date and time, and a migration instruction unit that issues a migration instruction based on the schedule to the virtual server management apparatus.

  According to the present invention, it is possible to reduce man-hours and time associated with leveling storage.

1 is a schematic configuration diagram of a storage management system in an embodiment of the present invention. It is a functional block diagram concerning the basic composition of the storage management device in the embodiment of the present invention. It is a schematic diagram which shows an example of the data memorize | stored in the memory | storage part shown in FIG. It is a schematic diagram which shows the virtual server list table memorize | stored in the memory | storage part in this embodiment. It is a schematic diagram which shows the transfer list memorize | stored in the memory | storage part in this embodiment. It is a schematic diagram which shows the abolition list memorize | stored in the memory | storage part in this embodiment. It is a schematic diagram which shows the schedule memorize | stored in the memory | storage part in this embodiment. It is a functional block diagram concerning the additional composition of the storage management device in the embodiment of the present invention. It is a schematic diagram which shows an example of the reply request | requirement GUI provided from the storage management apparatus in this embodiment to a person in charge terminal. It is a schematic diagram which shows an example of the abolition request | requirement GUI provided from the storage management apparatus in this embodiment to a person in charge terminal. It is a sequence diagram which shows the whole process sequence in this embodiment. It is a sequence diagram which shows the whole process sequence in this embodiment. It is a flowchart which shows the process sequence of the scheduling in this embodiment. It is a flowchart which shows the process sequence of the scheduling in this embodiment. It is a flowchart which shows the process sequence of the scheduling in this embodiment. In this embodiment, it is a schematic diagram which shows the virtual server list sorted based on the storage size of each virtual server, a person in charge, and the number of virtual servers. In this embodiment, it is a schematic diagram which shows the virtual server list sorted based on the storage size of each virtual server, a person in charge, and the total size. It is a schematic block diagram concerning the modification of the storage management system in the embodiment of this invention.

  A storage management device and a storage management system including the storage management device according to an embodiment of the present invention will be described below with reference to the drawings. In addition, in each figure, the same code | symbol is attached | subjected to the part which is the same or it corresponds, The duplication description is simplified thru | or abbreviate | omitted suitably.

  Note that “storage” used in the following description in the present embodiment includes a magnetic disk such as a hard disk, an optical disk such as a DVD disk, and a flash memory such as a USB memory. Further, the “storage” in the present embodiment may be connected to a physical server on which a virtual server is executed via a network, or may be built in the physical server.

  In addition, for example, “storage management” in “storage management device” is used for leveling storage in this embodiment, such as storage status management and storage migration, in addition to the usual meaning of keeping the storage in good condition. All accompanying control processing shall be included.

[Schematic configuration of storage management system in this embodiment]
A schematic configuration of the storage management system 1 in this embodiment will be described with reference to FIG. In the storage management system 1 in this embodiment, the storage management device 10, the virtual server management device 20, and the person-in-charge terminals 30a to 30c (hereinafter collectively referred to as “person-in-charge terminal 30”) are, for example, LANs. Are connected to the physical server 40 via an operation management network 90. Further, the physical server 40, the migration source storage 60, and the migration destination storage 70 are connected via a predetermined storage network 80 for storage different from the operation management network 90. Furthermore, the physical server 40 is connected to a network 50 such as the Internet in order to communicate with the outside. In the present invention, the storage that is the migration source is the first storage and the storage that is the migration destination is the second storage. However, for convenience, the storage that is the migration source and the migration destination It does not have any special meaning other than partitioning storage.

  The network 50, the storage network 80, and the operation management network 90 may be wired or wireless. In addition, the storage network 80 for transmitting and receiving the virtual server program and the operation management network for maintaining and monitoring the physical server 40 and the like may be configured on the same network. However, in order to prevent data congestion, the present embodiment is implemented. In the embodiment, the storage network 80 and the operation management network 90 are configured as separate networks.

  FIG. 1 shows one physical server, two virtual servers, two storages, and one virtual server management apparatus as components of the storage management system 1, but for convenience of illustration and explanation. Therefore, the configuration may be simplified and may be a system including two or more physical servers, three or more virtual servers, three or more storages, and two or more virtual server management devices. Needless to say.

  The storage management device 10 is a device that controls each process in the present embodiment, and is a computer such as a server or a personal computer (hereinafter referred to as “PC”) that performs various controls associated with storage leveling. The detailed operation of the storage management apparatus 10 will be described later.

  The virtual server management device 20 is a computer such as a server or a PC that manages a virtual server that is read from the storage and executed in the physical server 40. The virtual server management device 20 manages the migration between storages of the virtual server 41 operating on the physical server 40. Note that “management” in “virtual server management” here includes the generic meaning of management such as migration of the virtual server described above, management of the storage capacity of the storage for storing the virtual server program, Management of storage information consisting of virtual server identifiers as identification information for identifying virtual servers and the storage size of each virtual server, and between the storage management device 10 and the hypervisor 42 executed in the physical server 40, Processing associated with virtual server management such as storage capacity of storage and transmission / reception control of storage information is included.

  The person-in-charge terminal 30 is an information processing terminal such as a PC used by a person in charge such as a system engineer who is in charge of each virtual server. In FIG. 1, the storage management system 1 includes three person-in-charge terminals 30a, 30b, and 30c. However, the storage management system 1 is an example, and includes two or less person-in-charge terminals. There may be.

  The physical server 40 is a computer such as a server for deploying and executing the virtual server 41 on the memory. The physical server 40 includes a virtual server 41 a and a virtual server 41 b (hereinafter collectively referred to as “virtual server 41”), and various types of necessary components such as a hypervisor 42 that is a control program for controlling the virtual server 41. Program is running.

  The migration source storage 60 and the migration destination storage 70 are storage devices connected to the physical server 40 via the storage network 80. The storage network 80 may be, for example, a LAN or a SAN (Storage Area Network). Further, the storage device may be a storage device directly connected to the physical server 40 by IDE, SCSI, FC, or the like, regardless of the storage network 80. The migration source storage 60 and the migration destination storage 70 are realized by, for example, hard disks. Note that virtual storage may be used instead of physical storage. The migration destination storage 70 is preferably prepared in advance by the administrator of the storage control device 10.

  Although not shown in FIG. 1, it goes without saying that the storage management system 1 may include an administrator terminal that manages the entire system.

  Further, for example, a PC as the storage management device 10, virtual server management device 20, and physical server 40 has, for example, a CPU, RAM, ROM, HDD, various input / output units, a network interface (hereinafter referred to as "NW I / O") as its hardware configuration. Needless to say, it is equipped with a minimum unit for realizing an information processing function such as “F”. An information processing apparatus such as a PC that functions as these apparatuses implements the functions by reading a predetermined program stored in, for example, a ROM or HDD into the RAM and executing it by the CPU.

[Basic function blocks of the storage management apparatus 10]
Next, basic functional blocks of the storage management apparatus 10 shown in FIG. 1 will be described with reference to FIG. The storage management device 10 includes a storage unit 11, a schedule management unit 12, a communication unit 13, and a migration instruction unit 14 as basic function blocks.

  The storage unit 11 is storage means for storing person-in-charge information including the contact information of the person in charge of the virtual server 41. For example, the storage unit 11 is stored in a storage device such as a ROM or HDD built in the PC as the storage management apparatus 10. Function is realized. The storage device is not limited to a built-in storage device, and may be realized by an external storage medium such as a USB memory. The information stored in the storage unit 11 is not limited to the person-in-charge information described above.

  Here, an example of data stored in the storage unit 11 illustrated in FIG. 2 will be described with reference to FIG. The storage unit 11 stores a person-in-charge information list 110, a virtual server list 111, an abolition list 112, a schedule 113, and a migration list 114. These indicate data necessary for performing the processing in the present embodiment, and the storage unit 11 may store all data used in the processing of the storage management apparatus 10. Also, the migration target virtual server list to be inquired of the person in charge will be referred to as the “migration list”, and the list of the migration target virtual servers after obtaining the consent of the migration from the person in charge will be described as a “schedule” as a separate list. One list may be used. In such a case, an item such as “approved / not approved” that indicates whether or not the person in charge of the virtual server migration has approved is prepared.

  An example of the virtual server list 111 illustrated in FIG. 3 will be described with reference to FIG. 4A. Here, the table data includes “identifier”, “storage size”, “contact person address”, “status” and item names in order from the left. As a specific example of each item, identifier “VM-C04”, storage size “10”. The person in charge address “ccc@mail.***.jp” status “Abolition” is listed. The unit of the storage size “10” is, for example, gigabyte (GB). Further, the person-in-charge address “ccc@mail.***.jp” is an e-mail address that is the contact information of the person in charge. However, “***” is an abbreviation used so as not to be a specific mail address in the explanation, and the same applies to the following explanation. When the abolition list is used, the “status” item may or may not be provided.

  An example of the migration list 114 shown in FIG. 3 will be described with reference to FIG. 4B. Here, table data is arranged in the order of “identifier”, “migration start date / time”, and “migration end date / time” from the left. As a specific example of each item, the identifier “VM-C05”, the migration start date “○ month × "9 o'clock" and the transition end date and time "○ month x 17:00" are listed.

  An example of the abolition list 112 shown in FIG. 3 will be described with reference to FIG. 4C. Here, table data is arranged in the order of “identifier”, “stop date / time”, and “delete date / time” from the left. As a specific example of each item, identifier “VM-C06”, stop date “Δ month □ day 15:00” ", The date and time of deletion" ◎ month ◇ day 12:00 "are listed.

  An example of the schedule 113 shown in FIG. 3 will be described with reference to FIG. 4D. Here, “identifier”, “migration start date / time” and item names are arranged in order from the left, and as a specific example of each item, the migration start date / time corresponding to the identifier “VM-C04” “○ month × day 9 o'clock”. ", The transition start date and time" ○ month ◇ day 9:00 "corresponding to the identifier" VM-C05 ", and the transition start date and time" ○ month □ day 9:00 "corresponding to the identifier" VM-C06 "are listed. .

  The schedule management unit 12 is a schedule management unit that creates a schedule for migrating the migration target virtual server 41 to the migration destination storage 70 at the migration start date and time. Specifically, identification information (for example, “server name”) for identifying each virtual server 41 from the virtual server management device 20 when the free capacity of the migration source storage 60 in which the virtual server 41 is stored reaches a predetermined threshold value. (Also called “virtual server identifier”) and the storage size of each virtual server is acquired, and the virtual server 41 to be migrated is extracted based on the acquired identification information of each virtual server and the storage size of each virtual server. Then, set the migration start date and time and create a migration list. After that, the reply that approves the migration based on the migration notification is received from the person-in-charge terminal 30 used by the person in charge of the virtual server 41 that has received the migration notification, and the migration target virtual server 41 is transferred to the migration destination storage at the migration start date and time. Create a schedule to migrate to 70.

  In addition, the schedule management unit 12 receives a response from the person-in-charge terminal 30 used by the person in charge of the virtual server 41 that has received the migration notification, or the person in charge of the virtual server 41 that has received the migration notice. If there is a reply from the person-in-charge terminal 30 that does not approve the migration, the virtual server is stored in the migration source storage 60 registered as a backup in the migration list and is in charge of another virtual server different from the virtual server to be migrated The migration notification is transmitted to the contact person of the person in charge via the communication unit 13. Thus, even when there is no response from the person in charge who has received the migration notification, the storage can be leveled.

  As described above, since it is possible to automatically confirm the person in charge of the virtual server in accordance with the migration of the storage, it becomes possible to reduce the man-hours and time required for the leveling of the storage.

  Further, the schedule management unit 12 associates the identification information and storage size of each virtual server acquired from the virtual server management device 20 with the person in charge information of the person in charge of each virtual server stored in the storage unit 11. The virtual server list is created, and the created virtual server list is stored in the storage unit 11.

  Then, the schedule management unit 12 may create a migration list using the virtual servers listed in the abolition list as migration target virtual servers. Since the virtual server listed in the abolition list is not already used, it can be migrated without confirming with the person in charge as a virtual server to be migrated.

  Further, the schedule management unit 12 calculates the storage size of the migration target virtual server registered in the migration list based on the virtual server list, and calculates the migration target calculated in the free capacity of the migration source storage 60 that has reached the threshold. It is determined whether or not the free capacity of the migration source storage 60 obtained by adding the storage sizes of the virtual servers 41 exceeds the threshold value, and when it is determined that the free capacity of the migration source storage 60 exceeds the threshold value, Record the identification information of the registered migration target virtual server in the schedule. If the free capacity obtained by adding the storage size of the virtual server 41 to be migrated registered in the migration list to the free capacity of the migration source storage 60 exceeds the threshold, the free capacity of the migration source storage 60 is more than that, This will contribute to storage leveling.

  Furthermore, when the schedule management unit 12 determines that the free capacity of the migration source storage 60 is less than the threshold (that is, there is not enough free space), the schedule management unit 12 moves in the sort order sorted based on the storage size of each virtual server in the virtual server list. The virtual server 41 is extracted as a target virtual server and registered in the migration list, and the storage size of the registered migration target virtual server 41 is calculated based on the virtual server list. It is determined whether or not the free capacity of the migration source storage 60 obtained by adding the storage size of the migration target virtual server in the calculated migration list exceeds a threshold, and if the free capacity of the migration source storage 60 exceeds the threshold When the determination is made, the migration start date and time of the virtual server extracted as the migration target virtual server is set under a predetermined condition, and the migration It is recorded in the door. The virtual server list may be sorted together with the storage size of the virtual server or instead based on the person-in-charge information of each virtual server. A specific example of sorting the virtual server list will be described later.

  If the schedule management unit 12 adds the storage size of the virtual server listed in the migration list based on the abolition list to the free capacity of the migration source storage 60 and falls below the threshold, the free capacity of the migration source storage 60 is Because there is not enough and it is tight, effective storage leveling does not progress with the migration of virtual servers that have been discontinued. Therefore, the schedule management unit 12 needs to list a virtual server in operation as a migration target in addition to a virtual server that has been abolished or instead of a virtual server that has been abolished. Therefore, in this case, the virtual server in operation having a storage size that allows the free capacity of the migration source storage 60 to exceed the threshold is listed with reference to the virtual server list.

  This function of the schedule management unit 12 described above is realized by, for example, a program related to this function stored in the ROM or HDD of the PC as the schedule management unit 12 being expanded in the RAM and executed by the CPU.

  The migration instruction unit 14 is a migration instruction unit that transmits a virtual server migration instruction corresponding to the migration start date and time to the virtual server management device 20 based on the schedule migration start date and time stored in the storage unit 11.

  This function of the migration instruction unit 14 described above is realized by, for example, a program related to this function stored in the ROM or HDD of the PC as the schedule management unit 12 being expanded in the RAM and executed by the CPU.

  The communication unit 13 is a communication unit that connects the storage management apparatus 10 to a network and communicates with other apparatuses. Specifically, the communication unit 13 transmits a migration notification including an inquiry to migrate the virtual server 41 registered in the migration list created by the schedule management unit 12 to the migration start date and time to the contact person in charge. To do.

  The communication unit 13 transmits the migration instruction to the virtual server management apparatus 20 when the migration instruction unit 14 issues a migration instruction based on the schedule.

  This function of the communication unit 13 described above is realized by an NW I / F built in a PC as the storage management device 10, for example.

[Additional Function Block of Storage Management Device 10]
Next, an additional function block of the storage management apparatus 10 will be described with reference to FIG. 5 is an additional configuration of the basic function block shown in FIG. 2, and since the basic function block shown in FIG. 2 is naturally provided, the illustration is omitted. That is, the storage management apparatus 10 includes a U / I unit 15 and an abolition instruction unit 16 as additional configurations.

  The U / I unit 15 uses a homepage or the like for obtaining from the person-in-charge terminal 30 an answer to the person-in-charge terminal 30 that acknowledges that the virtual server 41 is to be migrated to the migration start date and time, for example, as described above. A graphical user interface (hereinafter referred to as “answer request GUI”) is provided. Thereby, the person in charge of the person-in-charge terminal 30 can easily input an answer to the migration of the virtual server in charge. The person in charge terminal 30 used by the person in charge is not limited to the reply from the person in charge terminal 30 used by the person in charge via the U / I unit 15, but is used, for example, by sending an e-mail or the like to the mail address of the person in charge. It is good also as receiving the reply of the reply mail from.

  Here, an example of an answer request GUI provided to the person-in-charge terminal 30 for obtaining an answer from the person in charge to migrate the virtual server 41 to the migration start date and time will be described with reference to FIG. 6A. The response request GUI is a screen such as a homepage provided by the U / I unit 15 shown in FIG. 5 to the person-in-charge terminal 30, and when provided to the person-in-charge terminal 30 by the U / I unit 15, for example, It is transmitted in the form of a URL or the like, and is guided to the connection to the home page. The person in charge of the person-in-charge terminal 30 uses this screen to inform the storage management apparatus 10 of whether or not the virtual server in charge can be migrated. The response request GUI may be provided with a different URL for each virtual server to be migrated, or a column for inputting or selecting a virtual server in charge from the person-in-charge terminal 30 is provided to determine which virtual server the response is to be made. The virtual server identifier may be transmitted to the storage management device 10 so that it can be performed.

  A “Migration OK?” Column 300 for requesting confirmation of migration from the top of this screen to the person in charge of the person-in-charge terminal 30 is displayed, and a “YES” icon 301 for accepting migration and the migration are not accepted on the right side. A “NO” icon 302 is displayed. Instead of “YES” and “NO”, the intention of transition may be reflected by simply pressing the “OK” icon or the like.

  Next, in the middle column of this screen, when the person in charge selects the “NO” icon 302 in the upper column, the “When is NO, what is the specified date and time?” Column 310 that prompts the user to input the specified date and time for migration. Is displayed, and a date and time input field is displayed below it. This field may be displayed at all times or displayed when the person in charge selects the “NO” icon 302 in the upper field. In addition, when this column is “NO”, it may be omitted if the person in charge cannot specify the date and time.

  In the lower column, a “send” icon 320 for sending an answer including the contents selected by the person in charge described above and the date and time inputted when necessary to the storage management device 10, and “cancel” canceling the selection or input are displayed. Icon 330 is displayed.

  Further, the U / I unit 15 provides a GUI for a homepage or the like (hereinafter referred to as “decommission request GUI”) for accepting a virtual server decommissioning request to the person-in-charge terminal 30.

  Here, an example of the abolition request GUI provided to the person-in-charge terminal 30 for obtaining a request to abolish the virtual server 41 from the person in charge will be described with reference to FIG. 6B. The abolition request GUI is also a screen such as a home page provided to the person-in-charge terminal 30 by the U / I unit 15 shown in FIG. 5, and is provided to the person-in-charge terminal 30 by the U / I unit 15 in the same manner as the response request GUI. When it is done, it is transmitted in the form of, for example, a URL or the like, and is guided to connection to the home page. A person in charge of the person-in-charge terminal 30 uses this screen to inform the storage management apparatus 10 of a request for abolishing the virtual server in charge.

  The “Do you want to abolish the virtual server?” Column 400 is displayed to ask the person in charge of the person in charge terminal 30 to confirm the abolition from the top of this screen, and “YES” is reflected on the right side to reflect the intention to abolish it. An icon 401 is displayed. In addition, even if it is not “YES”, the intention of abolition may be reflected by simply pressing the “OK” icon or the like.

  Subsequently, in the middle column of this screen, a “target virtual server identifier” column 410 for allowing the person in charge to input an identifier for identifying the virtual server to be abolished is displayed, and an identifier input column 411 is displayed on the right side thereof. Yes. These fields may be displayed when the “YES” icon 401 is selected.

  Under the “target virtual server identifier” column 410, a “desired desired date / time” column 420 for allowing the person in charge to input the date / time desired to be abolished is displayed, and a date / time input column 421 is displayed on the right side thereof. . The display form is not limited to the one for inputting the identifier, and a display form may be used in which a plurality of dates and times are displayed, and the person in charge selects the date and time desired to be abolished from the displayed plurality of dates and times. When selecting from a plurality of dates and times, a pull-down icon may be provided, and when this is selected, a plurality of dates and times may be displayed so as to be selectable at intervals of 30 minutes, for example. This field may also be displayed when the “YES” icon 401 is selected as in the “target virtual server identifier” field 410 and the like.

  In the lower column, a “send” icon 420 for sending a revocation request including the content selected by the person in charge described above, the input identifier, and the input date and time to the storage management apparatus 10, A “cancel” icon 430 for canceling input to the “target virtual server identifier” column 410 or the “desired desired date and time” column 420 is displayed.

  The abolition instructing unit 16 receives the abolition request for abolishing the virtual server from the person-in-charge terminal 30 in charge of the virtual server via the communication unit 13, and the identification information for identifying the virtual server related to the received abolition request, An abolition instruction that creates an abolition list that corresponds to the stop date and time for stopping the virtual server related to the abolition request and determines whether or not to instruct the virtual server management apparatus 20 to perform the abolition instruction based on the created abolition list Means. This function of the abolition instruction unit 16 is also realized by, for example, a program related to this function stored in the ROM or HDD of the PC as the schedule management unit 12 being expanded in the RAM and executed by the CPU.

[Overall Processing Procedure in this Embodiment]
Next, the overall processing procedure of this embodiment will be described with reference to FIGS. 7A and 7B. Hereinafter, each configuration illustrated in FIG. 1 will be described as an example. First, when the virtual server management apparatus 20 detects a storage whose free capacity has reached the threshold based on the free capacity of the storage acquired from the hypervisor 42 on the physical server 40 to be managed, the virtual server management apparatus 20 schedules storage threshold arrival notification. It transmits to the part 12 (step S101). Whether or not the threshold has been reached may be determined based on whether the free space has fallen below the threshold or the access load has exceeded the threshold. Instead of the free space, a measured value such as a ratio of the free space to the storage capacity of the entire storage, an access load to the storage, or the like may be used. One measurement value or a plurality of measurement values may be used. 7A and 7B, the communication unit 13 is omitted for convenience of illustration.

  When the schedule management unit 12 receives the storage threshold arrival notification from the virtual server management device 20 via the communication unit 13 (step S101), the schedule management unit 12 identifies a virtual server identifier that identifies a virtual server stored in the detected storage, A storage information acquisition request for requesting the storage size of the virtual server is transmitted to the virtual server management apparatus 20 via the communication unit 13 (step S102).

  When receiving the storage information acquisition request, the virtual server management device 20 transmits storage information including the virtual server identifier stored in the detected storage and the storage size of the virtual server, and the communication unit that has transmitted the storage information acquisition request 13 to the schedule management unit 12. (Step S103). Note that the storage information may include status information indicating the state of the virtual server, for example, indicating the presence or absence of the above-mentioned “decommission”.

  When the schedule management unit 12 receives the storage information via the communication unit 13, the schedule management unit 12 stores in the storage unit 11 a virtual server list that is a list of correspondence between the virtual server identifier included in the storage information and the storage size of the virtual server. (Step S104). At this time, based on the virtual server identifier included in the virtual server list, the schedule management unit 12 requests the storage unit 11 for person-in-charge information including contact information such as an e-mail address of the person in charge of each virtual server. . Here, a mail address will be described as an example of the person-in-charge information. The person-in-charge information may include a person-in-charge name described in the mail.

  When the person-in-charge information is returned from the storage unit 11 (step S105), the schedule management unit 12 stores the returned person-in-charge information in association with the virtual server identifier in the virtual server list stored in the storage unit 11. To do. The schedule management unit 12 also schedules migration of virtual servers. Details of scheduling will be described later.

  When the scheduling is completed, the schedule management unit 12 extracts the mail address corresponding to the migration target virtual server identifier registered in the migration list stored in the storage unit 11 based on the virtual server list, and is registered in the migration list. Inquiries about whether or not to migrate the virtual server stored corresponding to the migration start date and time, and a migration contact email including the URL of the answer request GUI to be answered for each virtual server identifier or the email of the person in charge It creates for every address, and transmits the transfer notification mail to the person in charge terminal 30 via the communication part 13 (step S106).

  The person-in-charge terminal 30 that has received the migration notification mail is connected to the response request GUI illustrated in FIG. 5A provided by the URL included in the mail, by an operation from the person in charge to the input unit. When the person in charge inputs whether or not the virtual server can be migrated via the answer request GUI displayed on the display unit and selects the transmission icon 320, the contents of the reply are managed by the schedule from the person in charge terminal 30 via the communication unit 13 It is transmitted to the unit 12 (step S107). Note that when connecting to the response request GUI from the person-in-charge terminal 30, an authentication process for authenticating the person in charge may be performed. In addition, the response content may include a virtual server identifier for identifying the virtual server, an approval for the migration start date and time determined by scheduling, an alternative date and time when the migration is not approved, and the like.

  When the schedule management unit 12 receives the answer, the schedule management unit 12 stores the schedule in which the virtual server identifier and the migration start date and time are registered in the storage unit 11 based on the content of the answer (step S108). Here, the schedule management unit 12 compares the virtual server identifier registered in the migration list stored in the storage unit 11 with the virtual server identifier registered in the schedule, and all the virtual servers registered in the migration list. When the identifier is not registered in the schedule by the deadline, or when there is a reply that does not approve the migration from the person-in-charge terminal 30 used by the person in charge of the virtual server 41 that has received the migration notification mail, A migration notification mail is transmitted via the communication unit 13 to a person in charge of another virtual server registered as a backup in the migration list.

  When the migration start date and time registered in the schedule stored in the storage unit 11 is reached, the migration instruction unit 14 migrates the virtual server corresponding to the virtual server identifier corresponding to the migration start date and time registered in the schedule to the migration destination storage The migration instruction to be transmitted is transmitted to the virtual server management apparatus 20 via the communication unit 13 (step S110).

  When the virtual server management apparatus 20 receives the migration instruction from the migration instruction unit 14, the virtual server corresponding to the virtual server identifier included in the received migration instruction receives the migration destination storage 70 included in the migration instruction received from the migration source storage 60. A transition instruction to shift to is transmitted to the hypervisor 42 (step S111).

  When the hypervisor 42 receives the migration command, the hypervisor 42 reads the storage image of the virtual server corresponding to the virtual server identifier from the migration source storage 60 (step S112) and writes it to the migration destination storage 70 (step S113). When the migration process of the virtual server is completed, the hypervisor 42 transmits a migration completion result indicating that the migration of the virtual server corresponding to the virtual server identifier is completed to the virtual server management apparatus 20 (step S114).

  When receiving the migration completion result, the virtual server management apparatus 20 transmits a migration completion notification indicating that the migration of the virtual server corresponding to the virtual server identifier is completed to the migration instruction unit 14 (step S115). The migration instructing unit 14 transmits a completion email describing that the migration of the virtual server corresponding to the virtual server identifier is completed to the person-in-charge terminal 30 of the email address corresponding to the virtual server identifier via the communication unit 13. (Step S116).

[Scheduling procedure in this embodiment]
Next, the scheduling procedure in the present embodiment will be described with reference to FIGS. 8A to 8C. Here, the description will be made on the assumption that the virtual server list is stored in the storage unit 11. First, the schedule management unit 12 extracts the virtual servers one by one from the virtual server list stored in the storage unit 11, and determines whether the status of the virtual server has been abolished or not. (Step S201). Note that status information included in the storage information received from the virtual server management apparatus 20 may be taken into the virtual server list and the abolition may be determined based on the status information, regardless of the abolition list.

  If the status of the extracted virtual server has been abolished (step S201, YES), the schedule management unit 12 adds the virtual server identifier of the virtual server as a migration target virtual server to the migration list (step S202). On the other hand, if the status of the extracted virtual server has not been abolished (step S201, NO), the schedule management unit 12 proceeds to step S203.

  The schedule management unit 12 repeats the process of “Step S201” for determining whether or not all virtual servers listed in the virtual server list have been abolished (Step S203).

  The schedule management unit 12 calculates the storage size of the migration target virtual server by summing the storage sizes corresponding to the virtual server identifier registered in the migration list with reference to the virtual server list (step S204).

  Next, the schedule management unit 12 adds the storage size of the migration target virtual server from the storage free capacity that has reached the threshold, and determines whether or not the added free capacity exceeds the threshold (step). S205). If the schedule management unit 12 determines that the added free space exceeds the threshold (step S205, YES), the storage unit 11 uses the virtual server identifier in the migration list as the migration target virtual server identifier along with the default migration start date and time. Is registered in the schedule stored in (step S206). Note that the schedule management unit 12 registers a default date and time such as a predetermined date and time of light load or a date and time to be executed immediately in association with the schedule as the default start date and time of transition.

  On the other hand, if the schedule management unit 12 determines that the free space after the addition does not exceed the threshold (NO in step S205), the schedule management unit 12 sorts the virtual server list using, for example, the storage size of each virtual server as at least one key. (Step S207). Sorting in this case includes [1] sorting in ascending order of storage size, [2] sorting in order of increasing storage size, and [3] sorting in such a way that the VMs to be moved become the same person in charge as much as possible. . Note that the reason for adopting the method of sorting for each person in charge in [3] is that the person who has fewer persons in charge of the virtual server to be moved can enjoy the advantage of having fewer persons to wait. is there. A specific example of the virtual server list after sorting for each person in charge will be described later.

  In the sorting of [3], after extracting the virtual server whose storage size is equal to or smaller than the predetermined size in the [3-1] virtual server list, the virtual servers corresponding to the mail addresses of the same person in charge are collected and summarized. The method in which the group to which the virtual server of the person in charge with a large number of virtual servers belongs is sorted as an upper group, and the virtual servers in each group are sorted in ascending order of storage size, and [3-2] virtual server list is the same. The virtual servers corresponding to the email address of the person in charge are collected, and the groups are sorted in descending order from the largest to the smallest, using the total storage size of the virtual servers in the group of virtual servers as a key, and the virtual servers in each group Although a method of sorting in order of increasing or decreasing storage size is illustrated, it is a matter of course that other methods may be used.

  Here, an example of the virtual server list after sorting based on the storage size of the virtual server, the person in charge address, and the number of virtual servers will be described with reference to FIG. 9A. First, a virtual server having a storage size equal to or smaller than a predetermined size is extracted as a virtual server to be migrated. In the example of this figure, the default size of the storage size of the virtual server to be migrated is set to 70 GB or less, and those exceeding 70 GB are registered as non-migration targets.

  Next, the virtual servers are grouped into virtual server groups corresponding to the mail addresses of the same person in charge, and the collected virtual server groups are sorted in descending order of the number of virtual servers. In the example of this figure, the group with the person in charge address “aaa@mail.***.jp” has two virtual servers, and the group with “bbb@mail.***.jp” has the number of virtual servers. Since the number of virtual servers in the group “ccc@mail.***.jp” is three (excludes virtual servers not included in the number), the address of the person in charge is “ccc@mail.**” “* .Jp” group, “aaa@mail.***.jp” group, “bbb@mail.***.jp” group. The virtual servers in the upper group having the person-in-charge addresses “ccc@mail.***.jp” in the ranks 1 to 3 are arranged in ascending order of storage size (here, 5 GB, 10 GB, and 15 GB). ), Virtual servers having virtual server identifiers “VM-C04”, “VM-C03”, and “VM-C02” are sorted. On the other hand, even if the person-in-charge address is “ccc@mail.***.jp”, the virtual server identified by “VM-C01” whose storage size exceeds 110 GB and the default size 70 GB is excluded from the migration target.

  Also, in the ranks 4 to 5, the virtual servers in the middle group whose person-in-charge address is “aaa@mail.***.jp” are in ascending order of storage size (in this case, 10 GB and 70 GB in this order). The virtual servers with the virtual server identifiers “VM-A03” and “VM-A02” are sorted. On the other hand, even if the person-in-charge address is “aaa@mail.***.jp”, the virtual server identified by “VM-A01” whose storage size exceeds 100 GB and the default size 70 GB is excluded from the migration target.

  Furthermore, in rank 6, the virtual server identifiers in the order of the smaller storage size (in this case, only 70 GB) of the virtual servers in the lower group whose person-in-charge address is “bbb@mail.***.jp” are “VM”. -B02 "are sorted. On the other hand, even if the person-in-charge address is “bbb@mail.***.jp”, the virtual server identified by “VM-B01” whose storage size exceeds 80 GB and the default size 70 GB is excluded from the migration target.

  As described above, in this example, the virtual server group of the person in charge with a large number of virtual servers is ranked higher, and the virtual servers in the group are sorted in ascending order of storage size.

  Next, an example of the sorted virtual server list based on the total of the storage size of the virtual server, the person in charge address, and the storage size will be described with reference to FIG. 9B. First, virtual servers are grouped with the same person-in-charge address, and a group of virtual servers having a large total storage size of the combined virtual servers is sorted as an upper virtual server. In the example of this figure, the total storage size of the virtual server of the group whose person-in-charge address is “aaa@mail.***.jp” is 180 GB, and the group of “bbb@mail.***.jp” The total size of the virtual server storage size is 150 GB and the total size of the virtual server storage size of the group “ccc@mail.***.jp” is 140 GB, so the person in charge address is “aaa @ mail” . ***. Jp ”,“ bbb@mail.***.jp ”, and“ ccc@mail.***.jp ”.

  Then, the virtual servers in the upper group having the person-in-charge address “aaa@mail.***.jp” from the ranks 1 to 3 are identified by the virtual server identifier “VM-A01” having the storage size of 100 GB. Like a virtual server identified by a virtual server identifier “VM-A02” having a storage size of 70 GB, a virtual server identified by a virtual server identifier “VM-A03” having a storage size of 10 GB, They are sorted in descending order of size.

  Also, in the ranks 4 to 5, the virtual server in the middle group whose person-in-charge address is “bbb@mail.***.jp” is the virtual server identifier “VM-B01” whose storage size is 80 GB. Like the virtual server identified by the virtual server identified by the virtual server identifier “VM-B02” having a storage size of 70 GB, the storage size is sorted in descending order.

  Further, in the ranks 6 to 9, the virtual servers in the lower group whose person-in-charge address is “ccc@mail.***.jp” are identified by the virtual server identifier “VM-C01” whose storage size is 110 GB. Virtual server identified by a virtual server identifier “VM-C02” having a storage size of 15 GB, a virtual server identified by a virtual server identifier “VM-C03” having a storage size of 10 GB, and a storage size of Like the virtual server identified by the virtual server identifier “VM-C04” which is 5 GB, they are sorted in descending order of storage size.

  As described above, in this example, the virtual server group of the person in charge with the large total storage size is ranked higher, and the virtual servers in the group are sorted in descending order of the storage size.

  Subsequently, the schedule management unit 12 initializes the count number N of the virtual server to be determined with 1 (step S208). Here, the virtual server added to the migration list in step S202 is deleted. However, it may be registered in the migration list as it is without being deleted.

  The schedule management unit 12 confirms the status of the Nth virtual server in the sorted virtual server list (step S209), and when confirming that the status is not abolished (step S209, NO), the schedule server 12 Add to the migration list (step S210). On the other hand, when it is confirmed that the schedule management unit 12 has been abolished (step S209, YES), the schedule management unit 12 proceeds to step S213.

  In step S210, after adding the Nth virtual server to the migration list, the schedule management unit 12 sums the storage size corresponding to the virtual server identifier registered in the migration list with reference to the virtual server list, and migrates The storage size of the target virtual server is calculated (step S211).

  The schedule management unit 12 adds the storage size of the migration target virtual server to the free space of the storage that has reached the threshold, and determines whether or not the free space after the addition exceeds the threshold (step S212). Here, thresholds are provided in two stages, such as a first threshold value and a second threshold value that is larger than the first threshold value, including the storage size of the virtual server to be migrated as a spare. However, a reserve migration target virtual server may also be registered in the migration list in preparation for a case where no approval is received from the person in charge. If the schedule management unit 12 determines that the added free space does not exceed the threshold (NO in step S212), the schedule management unit 12 adds 1 to N (step S213), and the determination process of “step S209” for the next virtual server repeat.

  On the other hand, when it is determined that the free space after the addition exceeds the threshold (YES in step S212), the schedule management unit 12 initializes M indicating the transfer order with 1 (step S213) and registers the Mth registered in the transfer list. The virtual server migration start date and time is set to the default date and time of the next migratable date (step S214). Here, the following description will be given on the assumption that, for example, 9 am on the next weekday is set as the “predetermined date and time for the next transferable day”.

  Next, the schedule management unit 12 calculates the estimated migration time, which is the time required for migration of the Mth virtual server registered in the migration list, based on a predetermined calculation formula using the storage size of the virtual server ( Step S215). As a predetermined calculation formula, for example, a calculation formula such as multiplying a measured value of a certain transition time as a reference and a predetermined coefficient based on the storage model or network type can be used.

  Thereafter, the schedule management unit 12 adds the predicted migration time to the migration start date and time of the Mth virtual server, and calculates the migration end date and time of the Mth virtual server (step S216).

  When the schedule management unit 12 determines that the migration end date / time of the Mth virtual server exceeds the second predetermined date / time (step S217, NO), the schedule management unit 12 further sets the migration start date / time of the Mth virtual server to the next migration. Change to the default date and time of the possible date, and add the estimated migration time to the new migration start date and time as the migration end date and store this in the migration list of the storage unit 11 in association with the Mth virtual server identifier (Step S218). Note that, as a specific example of the second predetermined date and time, for example, a work end time such as 17:00 can be set. In addition, the “next migration possible date” of the “predetermined date and time for the next possible migration date” is the day following the “next possible migration date”, and the “default date and time” is the “predetermined date and time”. For example, it is possible to set 9:00 on the next weekday. However, the migration end date may not be stored in the migration list.

  On the other hand, if the schedule management unit 12 determines that the migration end date / time of the Mth virtual server does not exceed the second predetermined date / time (YES in step S217), the schedule start date / time of the set Mth virtual server The migration end date and time of the Mth virtual server is stored in the migration list of the storage unit 11 in association with the Mth virtual server identifier (step S219).

  The schedule management unit 12 determines whether the determination has been completed for all virtual servers (step S220). If the schedule management unit 12 determines that there is still a virtual server registered in the migration list that has not yet been set with the migration start date and time (step S220, NO), the migration start of the M + 1th virtual server is started. Set the date and time to the migration end date and time of the Mth virtual server (step S221), add 1 to M, and until the migration start date and time is set for all virtual servers registered in the migration list, step S215 and subsequent steps Repeat the process. On the other hand, if the schedule management unit 12 determines that there are no virtual servers that are registered in the migration list and for which the migration start date / time is not set (step S220, YES), the scheduling process ends.

[About the abolition processing procedure in this embodiment]
Next, the abolition processing procedure in this embodiment will be described. The stop date and time may be calculated based on a predetermined calculation formula such as 3 months after receiving the abolition request, that is, the reception date + 3 months. The reason for setting the period of three months here is, for example, from the viewpoint of operation such as preparing for a user who requests to use the virtual server related to the decommissioning object for some reason after the decommissioning immediately. Of course, it may be set to a predetermined date and time.

  When the stop date and time stored in the revocation list is reached, the revocation instruction unit 16 of the storage management device 10 stops the deployment and execution of the virtual server corresponding to the virtual server identifier that is desired to be revoked on the physical server 40, and only the storage image The virtual server stop instruction to be transmitted is transmitted to the virtual server management apparatus 20.

  In addition, when receiving a stop instruction from the storage management apparatus 10, the virtual server management apparatus 20 transmits a stop command for stopping execution of the virtual server corresponding to the virtual server identifier included in the received stop instruction to the hypervisor 42. When receiving the stop command, the hypervisor 42 stops the execution of the virtual server corresponding to the virtual server identifier included in the stop command. When the virtual server is in this state, the status becomes “decommissioned” on the hypervisor 42 or the decommissioning list.

  Further, when the deletion date and time stored in the abolition list is reached, the abolition instruction unit 16 transmits to the virtual server management device 20 a deletion instruction for deleting the storage image of the virtual server identifier corresponding to the deletion date and time from the storage.

  When receiving the deletion instruction from the storage management apparatus 10, the virtual server management apparatus 20 transmits to the hypervisor 42 a deletion instruction for deleting the storage image of the virtual server corresponding to the virtual server identifier included in the received deletion instruction from the storage. . When receiving the delete instruction, the hypervisor 42 deletes the storage image of the virtual server corresponding to the virtual server identifier included in the delete instruction from the storage. When a virtual server is deleted, the virtual server is not described in the virtual server list, or when it is described, the status of the virtual server list becomes “deleted”.

[Modification of this embodiment]
Next, a modification of the storage management system in this embodiment will be described with reference to FIG. In the above-described storage management system 1 illustrated in FIG. 1 in the present embodiment, a virtual server program that realizes a virtual server in a migration destination storage is migrated from a migration source storage connected to a physical server via a network. However, as in the storage management system 100 of this variation, the virtual server migrates the virtual server program via the shared storage 700 connected by the migration source physical server 500, the migration destination physical server 600, and the storage network 80. The present invention can also be applied to a system configuration in which the storage image is stored in the local disk of each physical server. A description of the same configuration as that of the storage management system 1 described above is omitted.

  In the storage management system 100 according to this modification, the migration source physical server 500 and the migration destination physical server 600 are connected to the storage management device 10 and the like via the operation management network 90. The migration source physical server 500 and the migration destination physical server 600 are connected to the shared storage 700 via a storage network 80 such as a LAN. The migration source physical server 500 includes a local disk 501 and a hypervisor 502, and the migration destination physical server 600 includes a local disk 601 and a hypervisor 602. In addition, the virtual server 503a and the virtual server 503b are expanded on the local disk 501, and the virtual server 603a and the virtual server 603b are expanded on the local disk 601, but here, which virtual server is to be migrated or not is determined. Shall not be mentioned.

  In this case, at the time of the migration instruction from the migration instruction unit 14 to the virtual server management device 20 shown in step S110 of FIG. 7B, the storage management device 10 stores the storage image of the virtual server in the local disk 501 of the migration source physical server 500. In order to migrate, an instruction to copy to the shared storage 700 is given. Then, the storage management apparatus 10 instructs to copy the storage image of the virtual server from the shared storage 700 to the local disk 601 of the migration destination physical server 600 again. Then, the virtual server management device 20 issues a migration command to the corresponding hypervisor so as to perform processing according to the migration instruction.

  Each of the above-described embodiments is a preferred embodiment of the present invention, and various modifications can be made without departing from the scope of the present invention. For example, each process in the present embodiment described above can be executed using hardware, software, or a combined configuration of both.

  In the case of executing processing using software, it is possible to install and execute a program in which a processing sequence is recorded in a memory in a computer incorporated in dedicated hardware. Alternatively, the program can be installed and executed on a general-purpose computer capable of executing various processes.

DESCRIPTION OF SYMBOLS 1,100 Storage management system 10 Storage management apparatus 11 Storage part 12 Schedule management part 13 Communication part 14 Migration instruction part 15 U / I part 16 Decommissioning instruction part 20 Virtual server management apparatus 30 Person in charge terminal 40 Physical server 41 Virtual server 42, 502, 602 Hypervisor 50, 80 Network 60 Migration source storage 70 Migration destination storage 90 Operation management network 110 Personnel information list 111 Virtual server list 112 Abolition list 113 Schedule 114 Migration list 500 Migration source physical server 501, 601 Local disk 600 Migration Destination physical server 700 Shared storage

Claims (8)

A storage management device that is connected to a virtual server management device that manages a plurality of virtual servers that are read from storage and executed on a physical server, a person-in-charge terminal used by a person in charge of the virtual server, and a network ,
Storage means for storing contact information of a person in charge of the virtual server;
When the free capacity of the first storage reaches a predetermined threshold, the virtual server management device acquires identification information for identifying each virtual server stored in the storage and the storage size of each virtual server, Based on the storage size, extract the migration target virtual server to be migrated to the second storage, set the migration start date and time of the migration target virtual server, and contact the person in charge of the migration target virtual server According to the response received from the person-in-charge terminal used by the person in charge who sent the migration notification, sending a migration notice inquiring whether or not to migrate the migration target virtual server to the second storage at the migration start date and time, Schedule management means for creating a schedule for migrating the virtual server to be migrated to the second storage at the migration start date and time;
Transition instruction means for performing a transition instruction based on the schedule to the virtual server management device ,
The schedule management means is stored in the first storage when there is no response from the person-in-charge terminal used by the person in charge who has received the schedule and has received the schedule, and is different from the migration target virtual server. A storage management device characterized by transmitting a migration notification to the contact information of the person in charge of the virtual server . A storage management device that is connected to a virtual server management device that manages a plurality of virtual servers that are read from storage and executed on a physical server, a person-in-charge terminal used by a person in charge of the virtual server, and a network ,
Storage means for storing contact information of a person in charge of the virtual server;
When the free capacity of the first storage reaches a predetermined threshold, the virtual server management device acquires identification information for identifying each virtual server stored in the storage and the storage size of each virtual server, Based on the storage size, extract the migration target virtual server to be migrated to the second storage, set the migration start date and time of the migration target virtual server, and contact the person in charge of the migration target virtual server According to the response received from the person-in-charge terminal used by the person in charge who sent the migration notification, sending a migration notice inquiring whether or not to migrate the migration target virtual server to the second storage at the migration start date and time, Schedule management means for creating a schedule for migrating the virtual server to be migrated to the second storage at the migration start date and time;
Transition instruction means for performing a transition instruction based on the schedule to the virtual server management device ,
The storage means stores identification information for identifying a virtual server desired to be abolished and a revocation list registered in association with a stop date and time for stopping the virtual server desired to be abolished.
The schedule management means creates a migration list in which virtual servers registered in the abolition list are registered as the migration target virtual server, calculates a total storage size of migration target virtual servers registered in the migration list, Whether or not the free capacity of the first storage obtained by adding the calculated storage size of the migration target virtual server to the free capacity of the first storage that has reached the threshold exceeds the threshold When the free capacity of the first storage is determined to exceed the threshold value, the identification information of the migration target virtual server registered in the migration list is recorded in the schedule in association with a predetermined date and time. A storage management device.   The schedule management means is a virtual server in which the identification information and storage size of each virtual server acquired from the virtual server management apparatus is associated with the contact information of the person in charge of each virtual server stored in the storage means The storage management apparatus according to claim 1 or 2, wherein a list is created, and the created virtual server list is stored in the storage means.   When receiving the abolition request for abolishing the virtual server from the person-in-charge terminal in charge of the virtual server, the identification information for identifying the virtual server desired to be abolished included in the received abolition request, and the virtual server for which the abolition is desired A decommissioning list registered in correspondence with the stop date and time to stop is created, and based on the created revocation list, the virtual server desiring to be decommissioned is sent to the physical server at the stop date and time. The storage management apparatus according to any one of claims 1 to 3, further comprising abolishing instruction means for issuing a stop instruction for stopping execution on the server. The storage means stores a virtual server list in which identification information and storage size of each virtual server are associated with contact information of a person in charge of each virtual server stored in the storage means ,
When it is determined that the free space of the first storage is less than the threshold, the schedule management unit determines each virtual server in the virtual server list as at least the storage size of each virtual server and the contact information of each virtual server. Based on one, the value obtained by adding the total storage size of the migration target virtual servers registered in the migration list and the free capacity of the first migration source storage that has reached the threshold is the threshold The virtual servers in the virtual server list are extracted as migration target virtual servers in the sort order and registered in the migration list, and the migration start date and time of each of the migration target virtual servers registered in the migration list The storage management apparatus according to claim 2 , wherein the storage management apparatus is set based on a calculation formula and registered in the migration list. Storage management of a virtual server management device that manages multiple virtual servers that are read from storage and executed on a physical server, a person-in-charge terminal that is used by a person in charge of the virtual server, and a storage management device that is connected via a network A method,
Storing the contact information of the person in charge of the virtual server in a storage unit;
When the free space of the first storage reaches a predetermined threshold, Tokusu that step preparative memory size of each virtual server identification information for identifying the respective virtual servers stored from the virtual server management device in the storage When,
Extracting a migration target virtual server to be migrated to the second storage based on at least the storage size;
Setting a migration start date and time of the migration target virtual server;
Transmitting to the contact person in charge of the migration target virtual server a migration notification inquiring whether the migration target virtual server can be migrated to the second storage at the migration start date and time;
A step wherein the transition contact depending on the answers received from the representative terminal which transmits the personnel to use, that forms create a schedule for transition to a second storage as a transfer start time of the virtual servers to the transition,
Look including the steps of: performing a shift instruction based on the scheduled for the virtual server management device,
In the step of creating the schedule, when there is no response from the person-in-charge terminal used by the person in charge who has received the schedule and has received the schedule, it is stored in the first storage, and the migration target virtual server and A storage management method characterized by transmitting a migration notification to a contact person of a person in charge of a different virtual server . Storage management of a virtual server management device that manages multiple virtual servers that are read from storage and executed on a physical server, a person-in-charge terminal that is used by a person in charge of the virtual server, and a storage management device that is connected via a network A method,
Storing the contact information of the person in charge of the virtual server in a storage unit;
When the free space of the first storage reaches a predetermined threshold, Tokusu that step preparative memory size of each virtual server identification information for identifying the respective virtual servers stored from the virtual server management device in the storage When,
Extracting a migration target virtual server to be migrated to the second storage based on at least the storage size;
Setting a migration start date and time of the migration target virtual server;
Transmitting to the contact person in charge of the migration target virtual server a migration notification inquiring whether the migration target virtual server can be migrated to the second storage at the migration start date and time;
A step wherein the transition contact depending on the answers received from the representative terminal which transmits the personnel to use, that forms create a schedule for transition to a second storage as a transfer start time of the virtual servers to the transition,
Look including the steps of: performing a shift instruction based on the scheduled for the virtual server management device,
The creating step includes
Migration in which a virtual server registered in a revocation list registered in association with identification information for identifying a virtual server desired to be retired and a stop date and time for stopping the virtual server desired to be retired is registered as the migration target virtual server Creating a list;
Calculating the total storage size of the migration target virtual servers registered in the migration list;
Whether or not the free capacity of the first storage obtained by adding the calculated storage size of the migration target virtual server to the free capacity of the first storage that has reached the threshold exceeds the threshold Determining
When it is determined that the free capacity of the first storage exceeds the threshold, the identification information of the migration target virtual server registered in the migration list is recorded in the schedule in association with a predetermined date and time. storage management method characterized by. A virtual server management apparatus that manages a plurality of virtual servers that are read from storage and executed on a physical server, a person-in-charge terminal used by a person in charge of the virtual server, and a computer as a storage management apparatus connected by a network A program for causing each step included in the storage management method according to claim 6 to be executed .

Images