JP5232515B2 - Storage system, management method thereof, and storage control device - Google Patents

Description

  The present invention relates to an interface technology for performing a setting operation in a storage system, a management method thereof, and a storage control device.

  In recent years, many network connection functions have been realized in storage devices. With this network connection function, the storage apparatus can send and receive data and commands to and from the computer via a fiber channel or IP (Internet Protocol) network. As a protocol for transmitting / receiving SCSI (Small Computer System Interface) commands by TCP / IP (Transmission Control Protocol / Internet Protocol), iSCSI (Internet Small Computer System Interface) is standardized, and a storage apparatus in which this iSCSI is implemented. Are increasingly being used.

  2. Description of the Related Art Conventionally, in order to connect a computer and a storage device equipped with iSCSI newly and allow the computer to access a storage area in the storage device equipped with iSCSI as a SCSI device, a storage device equipped with iSCSI For this, information such as an initiator name and a target name is set, and this information is notified to the computer user. The user has to go through a procedure of setting these pieces of information for the computer.

  Normally, this procedure is required for each user, and since the RAID (Redundant Array of Inexpensive Disks) level and capacity of LUs (Logical Units) to be set differ depending on the user, the number of users who use storage devices equipped with iSCSI increases. As a result, there is a problem that the load on the administrator increases.

  As a method for solving this problem, a technique is conceivable in which setting authority for a storage apparatus equipped with iSCSI is delegated to the user, and a part of the setting work is performed by the user.

  In addition, a technique corresponding to a change in the internal state of a storage apparatus related to data movement or data copy within the storage apparatus mounted with iSCSI is disclosed (see Patent Document 1).

JP 2004-192305 A

  However, when delegating the setting authority for a storage device equipped with iSCSI to a user, there is a new problem that the free space on the disk of the storage device equipped with iSCSI is depleted when the user allocates an unlimited amount of disk space. To do.

  Conventionally, an administrator uses software unique to a storage apparatus equipped with iSCSI in order to perform a setting operation on a management terminal. For this reason, in order to transfer the setting authority to the user, there arises a problem that it is necessary to install software unique to the storage apparatus equipped with iSCSI in each computer.

  Therefore, the present invention is a storage that implements iSCSI that allows each user to perform necessary settings within the range of authority given to each computer without installing software unique to the storage device that implements iSCSI. It is an object of the present invention to provide a storage system capable of realizing the device, a management method thereof, and a storage control device.

  In order to achieve the above object, in the present invention, one or a plurality of host computers, and a storage control device that provides a plurality of logical volumes that are storage areas for reading and writing data to each of the host computers, are provided. In the storage system, the storage control device, based on a command from the host computer, an identification unit for identifying functional information of the logical volume included in the information of the logical volume allocated or unallocated to the host computer; An execution unit that executes processing on the logical volume according to the identification result of the identification unit.

  As a result, processing corresponding to the function information of the logical volume can be performed in the storage apparatus.

  In the present invention, a storage system management method comprising one or a plurality of host computers and a storage control device that provides a plurality of logical volumes each having a storage area for reading and writing data to and from each of the host computers. The storage control device is configured to identify, based on a command from the host computer, function information of a logical volume included in information on the logical volume allocated or unassigned to the host computer, and the identification step And executing a process for the logical volume according to the identification result.

  As a result, processing corresponding to the function information of the logical volume can be performed in the storage apparatus.

  Furthermore, in the present invention, in a storage control device that provides a plurality of logical volumes that are storage areas for reading and writing data to one or a plurality of host computers, the host is based on a command from the host computer. An identification unit that identifies function information of a logical volume included in information on the logical volume that is allocated or unallocated to a computer, and an execution unit that executes processing on the logical volume according to the identification result of the identification unit. It is characterized by that.

  As a result, processing corresponding to the function information of the logical volume can be performed in the storage apparatus.

  According to the present invention, the setting work for the storage apparatus can be performed within the range of the given authority without the user using the software specific to the storage apparatus, so that the burden of the setting work of the administrator is reduced. be able to.

(1) First Embodiment In the first embodiment, the operation when a storage apparatus newly creates an LU will be described as an example.

  FIG. 1 is a schematic diagram of a storage system according to the first embodiment. As shown in FIG. 1, the storage system 1 includes a storage device 100, a plurality of host computers 110, and a management terminal 150 connected to the storage device 100, which are connected to each other via a network 120 such as the Internet or an intranet. Configured.

  The host computer 110 is an information processing apparatus that executes an application that involves data input / output, and includes an initiator program 111 for accessing the storage apparatus 100 and a host side CPU (Central Processing Unit) 112 for executing the initiator program 111. have.

  The storage apparatus 100 includes a storage-side CPU 101 (control unit), a memory (control unit) 102, a cache 103 for speeding up access, a disk controller 104, one or more disks 105, and ports 106a and 106b. (Hereinafter collectively referred to as a port 106), a semiconductor memory 107 formed of a flash memory or the like, a management port 108, and a bus 109 for connecting these devices.

  The storage-side CPU 101 executes various processes described later by executing the target program 201 stored in the memory 102.

  The memory 102 is a device for storing a target program 201 and data to be described later.

The cache 103 is a device for temporarily storing write data.
The disk controller 104 is a device that controls input / output of data to / from the disk 105. The disk controller 104 may perform processing corresponding to RAID (Redundant Array of Independent Disks).

  The disk 105 is a device that stores data read and written by the host computer 110.

  The port 106 is a device such as a network card for connecting a LAN (Local Area Network) cable to the storage device 100, and performs data transmission / reception processing. In this embodiment, the storage apparatus 100 has two ports 106a and 106b, but it may have three or more ports 106.

  The semiconductor memory 107 is a device that stores a program and data read to the memory 102 when the storage device 100 is activated.

  The management port 108 is a device for connecting the storage apparatus 100 to the management terminal 150.

  The management terminal 150 is a computer for performing setting operations for the storage apparatus 100, such as setting of the maximum disk usage of the LU for each initiator, which will be described later, through the management port 108 of the storage apparatus 100.

  FIG. 2 shows programs and data stored in the memory 102 of the storage apparatus 100 (see FIG. 1 as appropriate). The memory 102 stores a target program 201, a target table 202, and an initiator management table 203.

  The target program 201 is a program for transmitting and receiving iSCSI PDU (Protocol Data Unit) according to the iSCSI standard with the initiator program 111 operating on the host computer 110. The target program 201 creates, adds, or deletes an LU or a target in response to reception of an iSCSI Login PDU based on the processing of the initiator program 111 of the host side CPU 112. Details of the operation at this time are shown in FIG. This will be described later with reference to FIGS.

  The target table 202 is a table showing the correspondence between initiators, targets, ports, and LUs, and the capacity of the corresponding LUs. Details will be described later with reference to FIG. The initiator management table 203 is a table showing the upper limit of the used capacity of the LU allocated for each initiator, and details will be described later with reference to FIG.

  FIG. 3 is a diagram illustrating an example of the target table 202. In FIG. 3, the target table 202 is a table including information of an “initiator name” field 301, a “target name” field 302, an “assigned port” field 303, a “LUN” field 304, and a “disk usage” field 305. .

  The “initiator name” field 301 stores a name for identifying the iSCSI initiator. The “target name” field 302 stores a name for identifying the iSCSI target. The target name is configured as volume information of the logical volume, and information such as “iqn.init000-20gb-jbod-lu0” is stored in the “target name” as the function information of the logical volume.

  The “assigned port” field 303 stores information indicating whether the port 106 allows the initiator to access the target.

  For example, assume that a value of “1” is taken when access is permitted, and a value of “0” is taken when access is not permitted. In the example of the present embodiment, the case where the storage 100 has two ports 106a and 106b is described as an example, and these ports are identified by IP addresses “192.168.0.1” and “192.168.0.2”, respectively. It is supposed to be done. In the example shown in FIG. 3, an initiator identified by the initiator name “initiator0” has an IP address “192.168.0.1” with respect to a target identified by the target name “iqn.init000-20gb-jbod-lu0”. This means that it can be accessed through the identified port, but cannot be accessed through the port identified by the IP address “192.168.0.2”.

  The “LUN” field 304 stores a number for identifying the LU assigned to each host computer 110. “-” In the “LUN” field 304 indicates an LU not assigned to each host computer 110.

  The “disk usage” field 305 represents the capacity of the corresponding LU. In this embodiment, it is assumed that the disk usage amount 305 is expressed in units of gigabytes. In the example shown in FIG. 3, the LUN number “0” that can be used by the initiator identified by the initiator name “initiator0” accessing the target identified by the target name “iqn.init000-20gb-jbod-lu0”. This means that the capacity of the LU is 20 gigabytes.

  FIG. 4 is a diagram illustrating an example of the initiator management table 203. The initiator management table 203 is a table including information of an “initiator number” field 401, an “initiator name” field 402, and a “maximum disk usage” field 403.

  The “initiator number” field 401 stores a number that is given only to identify the initiator by the storage apparatus 100 and is valid only within the storage apparatus 100. As described above, the “initiator name” field 402 stores a name for identifying the initiator.

  The “maximum disk usage” field 403 indicates the upper limit of the capacity allocated to each initiator. In the present embodiment, it is assumed that the administrator uses the management terminal 150 to set the maximum disk usage for each initiator. In the example shown in FIG. 4, the initiator number assigned to the initiator name “initiator0” by the storage apparatus 100 is “000”, and the upper limit of the maximum disk usage allocated to this initiator is 80 gigabytes. Means.

  FIG. 5 is a diagram illustrating the exchange of messages and data between the host CPU 112 and the storage CPU 101 when the host CPU 112 transmits an iSCSI Login Request PDU to the storage CPU 101 using the initiator program 111. The storage-side CPU 101 performs processing using the target program 201.

  First, the host CPU 112 issues a discovery session. By this issuance, information such as a target name can be obtained. Then, the host side CPU 112 transmits an iSCSI Login Request PDU to the storage apparatus 100 side in order to request a discovery session start and a login request (SP501).

  When the storage-side CPU 101 receives the iSCSI Login Request PDU for the discovery session, the storage-side CPU 101 performs processing A (SP502), and then transmits an iSCSI Login Request PDU to the host computer 110 as a response to the iSCSI Login Request PDU (SP503). Thereby, the login of the host computer 110 is permitted. At this time, the storage-side CPU 101 sets the return value of the immediately preceding process A (SP502) as the value of the Status field in the iSCSI Login Request PDU. Details of the processing A will be described later with reference to FIG.

  The host-side CPU 112 that has established the discovery session transmits a Text Request PDU requesting notification of information such as a target name to the storage apparatus 100 side (SP504).

  When the storage-side CPU 101 receives the Text Request PDU transmitted by the host-side CPU 112, the storage-side CPU 101 refers to the target table 202. The storage-side CPU 101 sends all the target names corresponding to the initiator name in the “initiator name” field 301 to the host computer 110 by including them in the Text Response PDU (SP505). Accordingly, since a plurality of target names can be displayed on the host computer 110 side, the user can determine which target name to log in to.

  The host-side CPU 112 that has been notified of the target name by the discovery session transmits to the storage apparatus 100 an iSCSI Login PDU requesting to perform the normal session (normal mode login) (SP506).

  When the storage-side CPU 101 receives the iSCSI Login Request PDU requesting to log in in the normal mode, after performing the process A (SP507), the storage-side CPU 101 sets the value of the Status A field to the value of the Status A immediately before as a response to the iSCSI Login Request PDU. A return value is set, and an iSCSI Login Response PDU is transmitted to the host computer 110 (SP508). That is, the storage-side CPU 101 transmits to the host computer 110 that the specified target login is permitted or not permitted. Details of the processing A will be described later with reference to FIG.

  FIG. 6 is a flowchart in which the storage-side CPU 101 executes the process A by executing the target program 201. First, when the storage-side CPU 101 receives an iSCSI Login PDU from the host computer 110 (SP501), the storage-side CPU 101 reads a value from the “Session Type” field included in the command of the iSCSI Login PDU.

  Then, the storage-side CPU 101 determines whether or not the “Session Type” of the iSCSI Login PDU is “Discovery” (SP601). If the storage-side CPU 101 determines that “Session Type” is “Discovery” (SP601: YES), the storage-side CPU 101 continues to check whether an “Initiator Name” field is present from the iSCSI Login PDU command. Judgment is made (SP603).

  When the storage-side CPU 101 determines that the “Initiator Name” field exists in the command (SP603: YES), the storage-side CPU 101 executes processing B described later with the value of the “Initiator Name” field as an argument (SP605), and the login is successful. (S606), the process A is finished.

  On the other hand, if the storage-side CPU 101 determines in step SP603 that the “Initiator Name” field does not exist (SP603: NO), the storage-side CPU 101 sets “Initiator Error” as the return value of the login failure (SP607). Finish.

  In step SP601, when the storage-side CPU 101 determines that the value of the “Session Type” field is not “Discovery” (SP601: NO), the storage-side CPU 101 determines that the processing is step SP507. It is determined whether or not the value of the “Session Type” field is “Normal” (SP602).

  If the storage-side CPU 101 determines that the value of the “Session Type” field is “Normal” (SP602: YES), then the “Initiator Name” field and “ It is determined whether the “Target Name” field exists (SP604).

  When the storage-side CPU 101 determines that both of these fields exist (SP604: YES), the storage-side CPU 101 executes processing C described later with the values of the “Initiator Name” field and the “Target Name” field as arguments (SP608). . Then, the storage-side CPU 101 ends the process A with the return value of the process C that determines whether the login is successful or failed as the return value of the process A (SP609).

  When the storage-side CPU 101 determines that at least one of the “Initiator Name” field and the “Target Name” field does not exist (SP604: NO), the return value of process A is set to “Initiator Error” as a login failure ( SP610) and the process A ends.

  If the storage-side CPU 101 determines that the value of the “Session Type” field is not “Discovery” (SP601: NO) and is not “Normal” (SP602: NO), the storage-side CPU 101 determines that the login has failed. The return value is set to “Initiator Error” (SP610), and the process A ends.

  FIG. 7 is a flowchart in which the storage-side CPU 101 executes the process B by executing the target program 201. In FIG. 7, specifically, the storage-side CPU 101 first determines whether or not the initiator name passed as an argument is registered in the initiator management table 203 (SP701).

  When the storage-side CPU 101 determines that the initiator name is registered in the initiator management table 203 (SP701: YES), the storage-side CPU 101 refers to the initiator management table 203 and the target table 202. The storage-side CPU 101 newly assigns a value obtained by subtracting the disk usage in the “disk usage” field 305 already allocated from the maximum disk usage in the “maximum disk usage” field 403 corresponding to the initiator name. Use as much disk usage as possible.

  Then, based on the disk usage amount that can be newly allocated, the storage-side CPU 101 obtains a pair of RAID level and capacity of one or more newly assignable LUs (SP702). For example, when two LUs are allocated to the initiator with the initiator name “initiator0” and the respective disk usage is 20 gigabytes, it is assumed that an iSCSI Login Request PDU from the same initiator is received from the host computer 110. The storage-side CPU 101 can provide a LU of 40 GB at maximum in the JBOD configuration, which is a normal configuration, and 20 GB in the RAID level 1 configuration, instead of the configuration at the RAID level.

  Next, the storage-side CPU 101 generates a target name for each combination of LU RAID level and capacity obtained in the previous step SP702, and adds the generated target name to the target table 202 (SP703). In the present embodiment, as shown in FIG. 3, a character string “iqn.init”, an initiator number, a character “−”, an LU capacity, a character string “gb−”, a RAID level, a character string “−LU”, and a LUN. A target name is created by concatenating the character strings in order from the left to create the target itself. The storage-side CPU 101 adds each target created in this way to the target table 202.

  In this embodiment, the “allocated port” fields 303 of the targets created as described above are all “1”, and the “LUN” field 304 and the “disk usage” field 305 are blank.

  Subsequently, the storage-side CPU 101 sequentially adds the character string “iqn.init”, the initiator number, the character string “−delete”, the character string “−lu”, and the LUN from the left to the LU already assigned “LUN”. A target whose target name is the concatenation (hereinafter referred to as a deletion target) is added to the target table 202 (SP704). Also for these targets, in the present embodiment, all the “allocated port” fields 303 of the targets created as described above are set to “1”, and the “LUN” field 304 and the “disk usage” field 305 are blank.

  On the other hand, if the storage-side CPU 101 determines in step SP701 that the initiator name passed as an argument is not registered in the initiator management table 203 (SP701: NO), first, an initiator number is assigned and used as an argument. The passed initiator name, initiator number, and maximum disk usage set in advance by the administrator are added to the initiator management table 203 (SP705).

  Next, the storage-side CPU 101 refers to the initiator management table 203 and sets the maximum disk usage in the “maximum disk usage” field 403 corresponding to the newly assigned initiator number as one newly assignable disk usage. The combination of the RAID level and capacity of the LU that can be newly allocated is calculated (SP706). For example, if there is no data of the initiator name “initiator1” in the initiator management table 203 and an iSCSI Login PDU having an initiator name “initiator1” is received from the host computer 110, the storage-side CPU 101 has the maximum JBOD configuration. An LU of up to 40 GB can be provided in a configuration of 80 GB and RAID level 1.

  Next, the storage-side CPU 101 generates a target name for the combination of the RAID level and capacity of the LU obtained in the previous step SP706, and adds the generated target name to the target table 202 (SP707). Note that the target name generation method is the same as that described in step SP703, and thus the description thereof is omitted.

  FIG. 8 is a flowchart in which the storage-side CPU 101 executes the target program 201 and performs process C. In FIG. 8, specifically, the storage-side CPU 101 first determines whether or not a pair of initiator name and target name passed as an argument is registered in the target table 202 (SP801).

  If the storage-side CPU 101 determines that the combination of the initiator name and the target name passed as an argument is registered in the target table 202 (SP801: YES), next, “delete” is set in the target name. It is determined whether it is included (SP802).

  As a result of the determination, if the storage-side CPU 101 determines that “delete” is included in the target name (SP802: YES), the storage-side CPU 101 reads the target name, refers to the target table 202, and sets the target to be deleted. The LU number of the LU to be identified is identified. When the storage-side CPU 101 detects a number corresponding to the identified LU number from the “LUN” field 304, the storage-side CPU 101 deletes the corresponding row from the target table 202 and deletes the LU (SP803).

  For example, when the LU number recognized by the storage-side CPU 101 is “0”, if it is confirmed in the “LUN” field 304 that LU0 is assigned to the host computer 110, “0” is stored in the “LUN” field 304. Are deleted from the target table 202, and LU0 is deleted.

  Next, the storage-side CPU 101 sets the return value indicating that the row corresponding to the identified LU has been deleted as “Target Removed” (SP804), and ends the process C.

  On the other hand, in step SP802, if the storage-side CPU 101 determines that “delete” is not included in the target name (SP802: NO), the initiator number and character in the character string of the target name Read from LU capacity information after “-”. Then, the storage-side CPU 101 recognizes the RAID level and capacity of the corresponding LU, refers to the target table 202, and adds the corresponding LUN and disk usage (SP805). Further, the storage-side CPU 101 creates an LU with the RAID level and capacity added in the previous step SP805 (SP806).

  Next, the storage-side CPU 101 refers to the target table 202 and deletes the target whose “LUN” field 304 is blank “-” (SP807), and sets “Success” as the return value of successful login ( SP808) Processing C ends.

  If the storage-side CPU 101 determines that the combination of the initiator name and the target name passed as an argument is not registered in the target table 202 (SP801: NO), “Initiator Error” which is the return value of the login failure. (SP809) The process C ends.

  In this way, when the storage apparatus receives an iSCSI login command from the host computer 110 to the storage apparatus 100, the storage apparatus 100 performs a login permission response (SP503) and processing that the user can perform on the storage apparatus 100. A response (SP505) having a character string to be represented can be made.

  Further, when the storage apparatus 100 receives a message from the host computer 110 that is predicted to start using a specific target on the storage apparatus 100 (SP506), processing corresponding to the name of the target (SP507) may be performed. it can.

  Furthermore, the storage apparatus 100 can generate an LU according to the target name and provide it to the host computer 110.

(2) Second Embodiment Next, in the second embodiment, an operation when the storage apparatus 100A newly creates an LU formatted with a specific file system will be described.

  The configuration of the storage system 1A in the present embodiment is the same as the configuration of the storage system 1 in the first embodiment except for the memory 102A. Also, among the operations of the storage apparatus 100A in the present embodiment, the sequence diagram shown in FIG. 5 and the flowchart of the process A shown in FIG. In the present embodiment, portions that are different from the first embodiment will be described.

  FIG. 9 shows the target table 202A in the present embodiment. In the target table 202A of FIG. 9, a character string for the storage apparatus 100A to newly create an LU formatted with a specific file system is added.

  Regarding the process B of the present embodiment, the storage-side CPU 101 performs a process based on the target program 201A. The process B described in the present embodiment is the same as the process B in the first embodiment described in FIG. 7 except for step SP703.

  In the present embodiment, in a step (not shown) corresponding to step SP703 in FIG. 7, in addition to the target name described in the first embodiment, a character string “iqn.init”, an initiator number, and a character “ -", LU capacity, character string" gb- ", RAID level, character"-", file system name, character string" -LU ", concatenated LUNs in order from the left are generated as target names, and the generated target The name is added to the target table 202A. Here, a typical file system such as “ntfs (NT File System)” or “ext3” is set as the file system name.

  The process C described in the present embodiment is the same as the process C in the first embodiment described in FIG. 8 except for step SP806. In the present embodiment, if a file system name is included between the RAID level and LUN in the character string of the target name in a step (not shown) corresponding to step SP806 in FIG. Write the corresponding file system to the LU.

  In this way, the host computer 110 can use an LU formatted with a specific file system in the storage 100 as a peripheral device.

(3) Third Embodiment In the third embodiment, an operation when the storage apparatus 100B creates a backup of an existing LU will be described.

  The configuration of the storage system 1B according to the present embodiment is the same as the configuration of the storage system 1 according to the first embodiment except for the memory 102B. Further, among the operations of the storage apparatus 100B in the present embodiment, the sequence diagram shown in FIG. 5 and the flowchart of the process A shown in FIG. In the present embodiment, portions that are different from the first embodiment will be described.

  FIG. 10 shows the target table 202B in the present embodiment. A character string for the storage apparatus 100B to create a backup of the existing LU is added to the target table 202B in FIG.

  Regarding the process B of the present embodiment, the storage-side CPU 101 performs a process based on the target program 201B. The process B described in the present embodiment is the same as the process B in the first embodiment described in FIG. 7 except for step SP703.

  In the present embodiment, in a step corresponding to step 703 in FIG. 7, in addition to the target name described in the first embodiment, a character string “iqn.init”, an initiator number, a character “−”, a character string A concatenation of “backup”, character string “-LU”, and LUN in order from the left is generated as a target name, and the generated target name is added to the target table 202B.

  The process C described in the present embodiment will be described below. Also for the process C, the storage-side CPU 101 performs a process based on the target program 201B. Specifically, first, as shown in FIG. 11, the storage-side CPU 101 determines whether or not a pair of initiator name and target name passed as an argument is registered in the target table 202B (SP901).

  If the storage-side CPU 101 determines that the combination of the initiator name and the target name passed as an argument is registered in the target table 202B (SP901: YES), next, “backup” is set as the target name. It is determined whether it is included (SP902). If the storage-side CPU 101 determines that “backup” is included in the target name, it reads the target name, identifies the LUN number corresponding to the LU from the target table 202B, and copies the read LU. Is created (SP903). Therefore, the replicated LU has the same RAID level, capacity and data as the read LU.

  Next, the storage-side CPU 101 adds the LUN and disk usage of the copied LU to the target table 202B (SP904). Then, the storage-side CPU 101 sets “Target Moved Temporarily”, which is a return value indicating that the target LU has moved (SP905), and ends the process C. The return value may be a return value that allows the host computer 110 to identify that it is not a normal login, and is not limited to “Target Moved Temporarily”.

  Note that the processing from step SP906 to step SP910 is the same as the processing from step SP805 to SP809 in FIG.

  In this way, the host computer 110 can create an LU backup as necessary.

(4) Fourth Embodiment In the fourth embodiment, an operation when the storage apparatus 100C provides the setting information of an existing initiator will be described.

  The storage system 1C configuration of the present embodiment is the same as the storage system 1 configuration of the first embodiment except for the memory 102C. Of the operations of the storage apparatus 100C in the present embodiment, the sequence diagram shown in FIG. 5 and the flowchart of the process A shown in FIG. In the present embodiment, portions that are different from the first embodiment will be described.

  FIG. 12 shows a target table 202C in the present embodiment. In the target table 202C of FIG. 12, a character string for the storage apparatus 100C to provide the setting information of the existing initiator is added. Regarding the process B of the present embodiment, the storage-side CPU 101 performs a process based on the target program 201C. The process B described in the present embodiment is the same as the process B in the first embodiment described in FIG. 7 except for step SP703.

  In the present embodiment, in the step corresponding to step 703 in FIG. 7, in addition to the target name described in the first embodiment, the target name includes a character string “iqn.init”, an initiator number, a character “−”, A character string “showconfig”, a character “−”, and a file system name concatenated in order from the left are generated as a target name, and the generated target name is added to the target table 202C.

  The process C described in the present embodiment will be described below. Also for the processing C of the present embodiment, the storage-side CPU 101 performs processing based on the target program 201C.

  Specifically, first, as shown in FIG. 13, the storage-side CPU 101 determines whether or not the combination of initiator name and target name passed as an argument is registered in the target table 202C (SP1001).

  If the storage-side CPU 101 determines that the combination of the initiator name and the target name passed as an argument is registered in the target table 202C (SP1001: YES), then “showconfig” is set as the target name. It is determined whether it is included (SP1002).

  When the storage-side CPU 101 determines that “showconfig” is included in the target name (SP1002: YES), the storage-side CPU 101 reads the target name and reads the LUN and disk usage corresponding to the LU from the target table 202C. Add to 202C (SP1003) and create a new LU (SP1004). At this time, the LU allocated to the host computer 110 may be an unallocated LU. The disk usage may be any capacity that can record an execution program to be described later.

  Then, the storage-side CPU 101 identifies the file system name when reading the target name, writes the corresponding file system in the LU, and a typical OS such as Windows (registered trademark) or Linux on this LU. An execution program that can be executed above is written (SP1005). When this execution program is executed on the host computer 110, it displays on the output device such as the display of the host computer 110 the set of the target name, assigned port, LUN, and disk usage of the target assigned to the relevant initiator. It shall be. Then, the storage-side CPU 101 sets the return value to “Target Moved Temporarily” (SP1006) and ends the process C.

  Note that the processing from step SP1007 to step SP1011 is the same as the processing from step SP805 to SP809 in FIG.

  In this way, when the user operates the host computer 110, the information set in the storage apparatus 100C can be confirmed as necessary.

(5) Fifth Embodiment In the fifth embodiment, an operation when the storage apparatus 100D changes the password of a specific initiator will be described.

  The storage system 1D configuration of the present embodiment is the same as the storage system 1 configuration of the first embodiment except for the memory 102D. Also, among the operations of the storage apparatus 100D in the present embodiment, the sequence diagram shown in FIG. 5 and the flowchart of the process A shown in FIG. In the present embodiment, portions that are different from the first embodiment will be described.

  FIG. 14 shows a target table 202D in the present embodiment. A character string for the storage apparatus 100D to change the password of a specific initiator is added to the target table 202D in FIG.

  FIG. 15 shows an initiator management table 203D in the present embodiment. The initiator management table 203D of FIG. 15 includes a “password” field 404 in addition to the “initiator number” field 401, the “initiator name” field 402, and the “maximum disk usage” field 403 described in FIG.

  The “password” field 404 stores a password set by the user for the initiator.

  Regarding the process B of the present embodiment, the storage-side CPU 101 performs a process based on the target program 201D. The process B described in the present embodiment is the same as the process B in the first embodiment described in FIG. 7 except for step SP703.

  In the present embodiment, in the step corresponding to step 703 in FIG. 7, in addition to the target name described in the first embodiment, the target name includes a character string “iqn.init”, an initiator number, a character “−”, A character string “changepassword”, a character “−”, and a file system name concatenated in order from the left are generated as a target name, and the generated target name is added to the target table 202D.

  The process C described in the present embodiment will be described below. Also for the processing C of the present embodiment, the storage-side CPU 101 performs processing based on the target program 201D.

  Specifically, first, as shown in FIG. 16, the storage-side CPU 101 determines whether or not the combination of initiator name and target name passed as an argument is registered in the target table 202D (SP1101).

  If the storage-side CPU 101 determines that the combination of the initiator name and the target name passed as an argument is registered in the target table 202D (SP1101: YES), next, “changepassword” is added to the target name. It is determined whether it is included (SP1102).

  If the storage-side CPU 101 determines that “changepassword” is included in the target name (SP1102: YES), it writes the corresponding file system from the read target name to the LU and then Windows (registered trademark). An execution program that can be executed on a typical OS such as Linux is written (SP1103).

  Next, the storage-side CPU 101 sets one of the UDP port numbers for which execution program designation is unused in the storage apparatus 100D to be in a standby state (SP1104).

  By executing the execution program, the host computer 110 allows the user to input a new password. When the user inputs a new password, the host computer 110 transmits the password to the storage apparatus 100D.

  Then, the storage-side CPU 101 determines whether or not a new password has been received (SP1105). If the storage-side CPU 101 determines that a new password has been received (SP1105: YES), it updates the initiator management table 203D (SP1106) and cancels the standby state for the UDP port number (SP1108).

  On the other hand, if the storage-side CPU 101 determines that a new password has not been received (SP1105: NO), the storage-side CPU 101 determines whether a predetermined time has elapsed since the start of standby (SP1107). When the storage-side CPU 101 determines that a certain time has not elapsed since the start of standby (SP1107: NO), the storage-side CPU 101 returns to step SP1105.

  If the storage-side CPU 101 determines that a certain time has elapsed since the start of standby (SP1107: NO), the storage-side CPU 101 cancels the standby state of the UDP port number (SP1108). Then, the storage-side CPU 101 sets the return value to “Success” (SP1109) and ends the process C.

  Note that the processing from step SP1110 to step SP1114 is the same as the processing from step SP805 to SP809 in FIG.

  In this way, the user can change the password set in the storage apparatus 100D as needed.

(6) Sixth Embodiment In the sixth embodiment, the storage apparatus 100E creates a pair of LUs, resynchronizes or restores data between the paired LUs, or makes a pair. The operation when changing the status of the LU being changed will be described. In this embodiment, it is assumed that two LUs can make a pair, and the LU pair consists of a primary volume and a secondary volume.

  The storage system 1E configuration of the present embodiment is the same as the storage system 1 configuration of the first embodiment except for the memory 102E. Further, among the operations of the storage apparatus 100E in the present embodiment, the sequence diagram shown in FIG. 5 and the flowchart of the processing A shown in FIG. In the present embodiment, portions that are different from the first embodiment will be described.

  FIG. 17 shows the memory 102E in the present embodiment. The memory 102E stores a target program 201E, a target table 202E, an initiator management table 203E, and an LU (management) table 204E.

  The target program 201E is a program for transmitting and receiving iSCSI PDU (Protocol Data Unit) according to the iSCSI standard with the initiator program 111 operating on the host computer 110. Also, the target program 201 generates an LU pair and resynchronizes or restores data between the paired LUs when receiving an iSCSI Login PDU based on the processing of the initiator program 111 of the host side CPU 112. The state of the paired LU is changed, and details of the operation at this time will be described later with reference to FIGS.

  When the target program 201 receives a write request to the primary volume in the “PAIR” state, which will be described later, from the host computer 110, the target program 201 writes the same data to the corresponding secondary volume simultaneously with the data write to the primary volume. Further, when the target program 201 receives a write request to the secondary volume in the “PAIR” state or “COPY” state described later from the host computer 110, the target program 201 does not write to the secondary volume and gives an error to the host computer 110. respond. The target table 202E and the initiator management table 203E are the same as those in the first embodiment.

  As shown in FIG. 18, the LU table 204E includes an “initiator name” field 1801, a “LUN” field 1802, a “P / S” field 1803, a “status” field 1804, an “elapsed time” field 1805, and a “progress rate” field. 1806, a “throughput” field 1807, a “remaining time” field 1808, and a “vs. LU” field 1809.

  The “initiator name” field 1801 stores a name for identifying the iSCSI initiator. The “LUN” field 1802 stores a number for identifying the LU. In the “P / S” field 1803, for a pair of LUs, a letter “P” meaning primary volume or a letter “S” meaning secondary volume is stored. The “status” field 1804 stores information related to the LU status.

  “SMPL” means a state where there is no other LU as a pair. “PAIR” means a state in which data is synchronized with a paired volume and the same data is written. “SUS” means a state in which data synchronization is stopped between the paired volumes, and writing is performed only to the primary volume. “COPY” means that data is being copied between primary and secondary volumes.

  The “elapsed time” field 1805 stores the elapsed time of the inter-LU data copy of the LU in the “COPY” state. The “progress rate” field 1806 stores the progress rate of the inter-LU data copy of the LU in the “COPY” state. The “throughput” field 1807 stores the throughput of the inter-LU data copy of the LU in the “COPY” state. In the “remaining time” field, 1808, the remaining time of the inter-LU data copy of the LU in the “COPY” state is stored. The “paired LU” field 1809 stores a number for identifying the partner LU of the pair.

  As shown in FIG. 19, the command table 205E includes a “status” field 1901, a “paircreate” field 1902, a “split” field 1903, a “suspend” field 1904, a “resync” field 1905, a “restore” field 1906, and “abort”. It is a table consisting of information in field 1907.

  “Paircreate” is a command for newly creating an LU serving as a secondary volume using an LU in the “SMPL” state as a primary volume. “Split” is a command for canceling an LU pair. “Suspend” is a command that changes the state of the LU pair in the “PAIR” state to “SUS” and stops writing to the secondary volume.

“Resync” is a command for resynchronizing the data of the primary volume with the secondary volume. “Restore” is a command for restoring the secondary volume data to the primary volume. “Abort” is a command for canceling data resynchronization or data restoration being executed.

  A value “1” in each field indicates that the command can be executed in the corresponding state, and a value “0” in each field indicates that the command cannot be executed in the corresponding state. For example, FIG. 19 indicates that the only command that can be executed on an LU in the “SMPL” state is “paircreate”.

  The process B described in the present embodiment is the same as the process B in the first embodiment described in FIG. 7 except for step SP703. The target table 202E of the present embodiment has the same configuration as the target table 202D in FIG.

  FIG. 20 shows processing B performed by the target program 201E when receiving a login of a discovery session. The process B described in this embodiment is the same as the process B in the first embodiment described in FIG. 7 except for step SP2002 (steps SP2003 to SP2005 are the same as SP703 to SP707). is there.

  In step SP2002, by referring to the LU table 204E and the command table 205E, a command executable for each LU is determined, and a target name is generated based on the command. For example, since the only command that can be executed for the LU of the LUN “0” having the initiator name “initiator0” is paircreate, the target having the target name “iqn.init000-lu0-paircreate” is added to the target table 202E. In addition to this, the target program 201E updates the target table 202E so that the state, elapsed time, progress rate, throughput, and remaining time of each LU at that time are included in the target name.

  For example, the target program 201E adds “paircreate”, which is processing information executable according to the state of the LU, to “iqn.init000-lu0-”, which is LU function information, and the target name (volume information). And the target name (volume information) to which the internal status information indicating the real-time LU internal status, including “the status of each LU, elapsed time, progress rate, throughput, remaining time” and the like, is added to the host computer 110. It is generated as response information, and the target table 202E is updated with the generated target name.

  FIG. 21 shows an example of the target table 202E in the present embodiment. For the target name "iqn.init000-lu5: p-copy-00: 01: 42-38.2percent-233mbps-00: 02: 45", the LUN of LUN "5" is a primary volume and the status is "COPY" Yes, the copy elapsed time is 1 minute 42 seconds, the progress rate is 38.2%, the throughput is 233 megabytes per second, and the remaining time is 2 minutes 45 seconds. The initiator program 111 on the host computer 110 receives these target names as a discovery session login response (SP505).

  Hereinafter, in step SP506 in FIG. 5, the target program when the end of the target name destined for the iSCSI Login (Normal Session) received by the storage-side CPU 101 from the host-side CPU 112 is a character string representing a command in the command table 205E. The operation of 201E will be described.

  FIG. 22 shows the operation of the target program 201E when the end of the login destination target name is “paircreate”. If the initiator name / target name pair included in the iSCSI login request is registered in the target table 202E (SP2201: Yes), the target program 201E creates a new LU having the same capacity as the corresponding LU ( SP2202), the initial copy is started (SP2203), the LU table 204E and the target table 202E are updated so that the former LU is the primary volume and the latter LU is the secondary volume and the status is “COPY” (SP2204). When the initial copy is completed (SP2205: Yes), the LU table 204E and the target table 202E are updated so that the state of these LUs is “PAIR” (SP2206).

  FIG. 23 shows the operation of the target program 201E when the end of the login destination target name is “split”. If the initiator name / target name pair included in the iSCSI login request is registered in the target table 202E (SP2301: Yes), the target program 201E cancels the corresponding LU pair and changes the status of both LUs to “ The LU table 204E and the target table 202E are updated to “SMPL” (SP2302).

  FIG. 24 shows the operation of the target program 201E when the login destination target name ends with “suspend”. If the initiator name / target name pair included in the iSCSI login request is registered in the target table 202E (SP2401: Yes), the target program 201E sets the corresponding LU pair status to “SUS”. The LU table 204E and the target table 202E are updated (SP2402).

  FIG. 25 shows the operation of the target program 201E when the login destination target name ends with “resync”. If the initiator name / target name pair included in the iSCSI login request is registered in the target table 202E (SP2501: Yes), the target program 201E starts data resynchronization from the corresponding primary volume to the secondary volume. (SP2502) The LU table 204E and the target table 202E are updated so that the state of both LUs is “COPY” (SP2503). When resynchronization is completed (SP2504: Yes), the LU table 204E and the target table 202E are updated so that the state of these LUs is “SUS” (SP2505).

  FIG. 26 shows the operation of the target program 201E when the login destination target name ends with “restore”. If the initiator name / target name pair included in the iSCSI login request is registered in the target table 202E (SP2601: Yes), the target program 201E starts data restoration from the corresponding secondary volume to the primary volume ( SP2602), the LU table 204E and the target table 202E are updated so that the state of both LUs is “COPY” (SP2603). When the data restoration is completed (SP2604: Yes), the LU table 202E and the target table 202E are updated so that the state of these LUs is “SUS” (SP2605).

  FIG. 27 shows the operation of the target program 201E when the end of the login destination target name is a character string following “abort”. If the initiator name / target name pair included in the iSCSI login request is registered in the target table 202E (SP2701: Yes), the target program 201E stops data resynchronization or data restoration between the corresponding LUs ( SP2702), the LU table 204E and the target table 202E are updated so that the state of both LUs is “SUS” (SP2703).

  The character string following “abort” at the end of the target name indicates the elapsed time, progress rate, throughput, and remaining time of data resynchronization or data restoration of the corresponding volume. The user confirms this information. In addition, it is possible to determine whether or not to stop data resynchronization or data restoration.

  In the embodiments described above, the target name of a single iSCSI target represents a command operation or status for a single LU, but the target name of a single iSCSI target is a command operation for multiple LUs. Or you may take embodiment which represents a state. In this case, for example, the target named “iqn.init000-lu1-lu3-split” means a target for performing pair resolution for an LU with a LUN of 1 and an LU with a LUN of 3. Can be implemented.

  In this way, users can perform backup and restore in units of LUs using only standard iSCSI initiators without using the storage software's unique management software, or the internal status of LUs such as their progress and throughput. It is possible to monitor the status and grasp possible operations for each LU.

(7) Other Embodiments In the above-described embodiment, the management unit that manages the information of the logical volume allocated or unallocated to the host computer 110 as volume information (target name) is the memory 102 and the target table. 202, and an identification unit for identifying the necessary volume information based on a command from the host computer 110 is configured by the CPU 101 and the target program 201, and volume information based on the necessary volume information identified by the identification unit. Although the execution unit that executes predetermined processing according to the function information of the logical volume included in the logical volume is configured by the CPU 101 and the target program 201, the present invention is not limited to this, and the management unit, Each identification unit and execution unit A hardware configuration may be used.

  The present invention can be widely applied to a storage system having one or a plurality of storage devices and other forms of storage systems.

1 is a schematic diagram of a storage system according to a first embodiment. 2 is a block diagram in a memory according to the first embodiment. FIG. It is a chart which shows the target table in a 1st embodiment. 4 is a chart showing an initiator management table in the first embodiment. It is a figure which shows the sequence at the time of iSCSI login in 1st Embodiment. It is a flowchart which shows the process A of the target program in 1st Embodiment. It is a flowchart which shows the process B of the target program in 1st Embodiment. It is a flowchart which shows the process C of the target program in 1st Embodiment. It is a chart which shows the target table in a 2nd embodiment. It is a chart which shows the target table in a 3rd embodiment. It is a flowchart which shows the process C of the target program in 3rd Embodiment. It is a chart which shows the target table in a 4th embodiment. It is a flowchart which shows the process C of the target program in 4th Embodiment. It is a chart which shows the target table in a 5th embodiment. It is a chart which shows the initiator management table | surface in 5th Embodiment. It is a flowchart which shows the process C of the target program in 5th Embodiment. It is a block diagram in a memory in a 6th embodiment. It is a chart which shows the LU table in 6th Embodiment. It is a figure which shows the command table in 6th Embodiment. It is a flowchart which shows the process B of the target program in 6th Embodiment. It is a chart which shows the target table in a 6th embodiment. It is a flowchart which shows the process at the time of pair receive reception in 6th Embodiment. It is a flowchart which shows the process at the time of split reception in 6th Embodiment. It is a flowchart which shows the process at the time of the suspension reception in 6th Embodiment. It is a flowchart which shows the process at the time of resync reception in 6th Embodiment. It is a flowchart which shows the process at the time of restore reception in 6th Embodiment. It is a flowchart which shows the process at the time of abort reception in 6th Embodiment.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 1 ... Storage system, 110 ... Host computer, 100 ... Storage apparatus, 102 ... Memory, 201 ... Target program, 202 ... Target table 202 ... Initiator management table

Claims (15)

In a storage system having one or a plurality of host computers and a storage control device that provides a plurality of logical volumes that are storage areas for reading and writing data to each of the host computers,
The storage controller is
A generation unit for generating a target name corresponding to each of the logical volumes;
A transmitting unit that transmits one or more target names corresponding to an initiator name identifying each of the host computers to each of the host computers;
An identification unit that receives a command from each of the host computers and identifies the target name included in the command ;
An execution unit that executes processing for the logical volume corresponding to the target name according to the identification result of the identification unit ;
The generation unit generates a target name including a character string representing a process in which each host computer can instruct the storage control device to execute,
The identification unit identifies the character string included in the target name,
Storage system wherein the execution unit, the identification unit is characterized in that that perform the processing represented by the string identified. The generation unit generates the target name in response to a login request from any of the host computers,
The storage system according to claim 1 , wherein the transmission unit transmits one or more target names in response to an information notification request from a host computer that has issued the login request . The generation unit generates the target name in response to a discovery session start request from any of the host computers,
In response to the information notification request from the host computer that has issued the start request, the transmission unit transmits one or more target names corresponding to an initiator name that identifies the host computer,
The identification unit receives a normal mode login request from the host computer, determines whether the character string is included in the target name included in the login request,
The storage system according to claim 1, wherein the execution unit executes the process represented by the character string when the character string is included . The processing includes creation of the logical volume, deletion of the logical volume, and creation of a copy of the logical volume,
The storage system according to claim 1, wherein the generation unit generates the target name including the character string representing any one included in the processing . The processing further includes creation of a secondary logical volume that is a pair of the logical volume, cancellation of a pair between the paired logical volume and the secondary logical volume, and the paired logical volume and the Stop data synchronization with the secondary logical volume, resynchronize data between the paired logical volume and the secondary logical volume, and data from the paired secondary logical volume to the logical volume Including restoration of
The storage system according to claim 4 , wherein the generation unit generates the target name including internal state information indicating a real-time internal state of the logical volume , in addition to the character string representing any of the processes . In a storage system management method comprising one or a plurality of host computers and a storage controller that provides a plurality of logical volumes comprising storage areas for reading and writing data to each of the host computers,
The storage control device generates a target name corresponding to each of the logical volumes;
Transmitting one or more target names corresponding to an initiator name identifying each of the host computers to each of the host computers;
An identification step of receiving a command from each of the host computers and identifying the target name included in the command ;
Executing the process for the logical volume corresponding to the target name according to the identification result of the identification step ;
In the generation step, a target name including a character string representing a process in which each of the host computers can instruct the storage control device to execute is generated.
In the identification step, the character string included in the target name is identified,
In the execution step, a storage system management method for executing the processing represented by the character string identified by the identification unit . In the generation step, the target name is generated in response to a login request from any of the host computers,
The management method according to claim 6, wherein in the transmission step, one or more target names are transmitted in response to an information notification request from a host computer that has issued the login request . In the generation step, the target name is generated in response to a discovery session start request from any of the host computers,
In the transmission step, in response to an information notification request from the host computer that issued the start request, one or more target names corresponding to an initiator name that identifies the host computer are transmitted,
In the identification step, a normal mode login request is received from the host computer, and it is determined whether the character string is included in the target name included in the login request;
The management method according to claim 6, wherein, in the execution step, when the character string is included, the process represented by the character string is executed . The processing includes creation of the logical volume, deletion of the logical volume, and creation of a copy of the logical volume,
The management method according to claim 6, wherein in the generation step, a target name including the character string representing any one included in the processing is generated. The processing further includes creation of a secondary logical volume that is a pair of the logical volume, cancellation of a pair between the paired logical volume and the secondary logical volume, and the paired logical volume and the Stop data synchronization with the secondary logical volume, resynchronize data between the paired logical volume and the secondary logical volume, and data from the paired secondary logical volume to the logical volume Including restoration of
The management method according to claim 9 , wherein in the generation step, the target name including internal state information indicating a real-time internal state of the logical volume is generated in addition to the character string representing any one included in the processing . In a storage control device that provides a plurality of logical volumes that are storage areas for reading and writing data to one or a plurality of host computers,
A generation unit for generating a target name corresponding to each of the logical volumes;
A transmitting unit that transmits one or more target names corresponding to an initiator name identifying each of the host computers to each of the host computers;
An identification unit that receives a command from each of the host computers and identifies the target name included in the command ;
An execution unit that executes processing for the logical volume corresponding to the target name according to the identification result of the identification unit ;
The generation unit generates a target name including a character string representing a process in which each host computer can instruct the storage control device to execute,
The identification unit identifies the character string included in the target name,
The execution control unit is a storage control device that executes the process represented by the character string identified by the identification unit. The generation unit generates the target name in response to a login request from any of the host computers,
The storage control device according to claim 11, wherein the transmission unit transmits one or more target names in response to an information notification request from a host computer that has issued the login request . The generation unit generates the target name in response to a discovery session start request from any of the host computers,
In response to the information notification request from the host computer that has issued the start request, the transmission unit transmits one or more target names corresponding to an initiator name that identifies the host computer,
The identification unit receives a normal mode login request from the host computer, determines whether the character string is included in the target name included in the login request,
The storage control device according to claim 11, wherein the execution unit executes the processing represented by the character string when the character string is included . The processing includes creation of the logical volume, deletion of the logical volume, and creation of a copy of the logical volume,
The storage control device according to claim 11, wherein the generation unit generates the target name including the character string representing any one included in the processing . The processing further includes creation of a secondary logical volume that is a pair of the logical volume, cancellation of a pair between the paired logical volume and the secondary logical volume, and the paired logical volume and the Stop data synchronization with the secondary logical volume, resynchronize data between the paired logical volume and the secondary logical volume, and data from the paired secondary logical volume to the logical volume Including restoration of
The storage control device according to claim 14 , wherein the generation unit generates the target name including internal state information indicating a real-time internal state of the logical volume in addition to the character string representing any one included in the processing. .

Images