JP2008140413A - Storage device system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To reduce management operation cost by a storage device including both functions of NAS and SAN, and having flexibility in a system constitution. <P>SOLUTION: The storage device is equipped with a plurality of interface slots capable of loading a plurality of interface control parts, a block I/O interface control part having the function of SAN loadable on the slot, a file I/O interface control part having the function of NAS, a storage capacity pool constituted of a plurality of disk devices accessible from an optional interface control part, and a storage capacity pool control part for controlling the storage capacity pool. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a storage device system used in a computer system.

  There are roughly two types of interfaces for connecting the storage system and the computer. The first is a “block I / O interface” in which input / output (hereinafter “I / O”) is performed between a storage device system and a computer in units of blocks, which are data management units in the storage device system. . There are various types of block I / O interfaces, such as Fiber Channel and SCSI (Small Computer Systems Interface).

  A network in which a plurality of storage device systems having a block I / O interface and a plurality of computers are connected to each other is referred to as a storage area network (SAN). SANs are often built using Fiber Channel. An example of a storage system connected to a SAN using a fiber channel is disclosed in Japanese Patent Laid-Open No. 10-333839.

  The second is a “file I / O interface” in which I / O is performed between the storage system and the computer in units of files recognized by an application program executed on the computer. The file I / O interface often uses a network file system protocol used in a conventional file server. In particular, among the functions of the file server, a device that combines a storage device system and a function specialized for the storage device system is called network attached storage (NAS). The NAS is directly connected to a local area network (LAN) or the like.

  In the SAN, a computer and a storage device system are connected by a high-speed network dedicated to a storage device system provided separately from a network for exchanging messages between computers. Therefore, in SAN, data can be exchanged at a higher speed than NAS connected to a computer via LAN. Further, since the block I / O interface is adopted in the SAN, the overhead of the protocol processing is small compared with the NAS, and a high-speed response can be obtained.

  On the other hand, since the SAN requires a network dedicated to the storage device system, the cost for introducing the SAN is high for the user. Therefore, the SAN is mainly used in a company's backbone system and is often used for the purpose of constructing a database.

  On the other hand, since NAS can use an existing LAN as it is, the cost at the time of introduction is small and the introduction is easy. Also, since NAS uses a standardized network file system, NAS users can manage data in units of general files. Therefore, data management is easy, and files can be easily shared by a plurality of computers.

  On the other hand, the NAS exchanges data with a computer via a LAN that is also used for communication between computers. Therefore, the load on the LAN may increase. In addition, the overhead of processing a protocol used in the network file system is large, and the response performance is slower than that of the SAN. For this reason, NAS is mainly used in corporate file management systems, and is often used for applications such as Web content management and CAD data file management.

  As described above, NAS and SAN are complementary to each other, and applied fields are also different. Therefore, in general, both are properly used in place.

  Also, in order for each computer to use the storage capacity of the storage system as much as necessary, it is necessary to set resources (hereinafter “devices”) in the storage system and assign devices to each computer. There is a technique called a storage pool as a technique that can be easily performed. An example of a storage pool is disclosed in Japanese Patent Laid-Open No. 2001-142648.

  When an attempt is made to construct a system including a SAN and a NAS in the prior art, both a storage device system having a SAN function and a NAS are required. In this case, the user of the constructed system needs to separately manage different types of storage device systems, which increases the cost for managing and operating the system.

  Further, in a storage device system having a SAN function and a system having each of NAS, the system user needs to manage the storage capacity for each storage device system. Specifically, the user must manage different environment settings and storage capacities. Therefore, there is a problem that the management of the storage device system becomes complicated and difficult for the user of the system.

  Further, in a system including SAN and NAS, when the storage capacity of the storage device system used for the SAN is insufficient, the management system of each storage device system is different even if the storage capacity of the NAS is sufficient. Since they are different, the user cannot freely use the storage capacity existing in the NAS. That is, there is a problem that the user cannot effectively use the storage capacity of the entire system.

  An object of the present invention is to provide a storage device system that can reduce the management operation cost for a plurality of types of storage device systems.

  A further object of the present invention is to provide a storage device system that facilitates management of the storage capacity of the entire system and realizes efficient use of the storage capacity.

  In order to achieve the above object, a storage device system according to the present invention allocates a plurality of slots into which a plurality of types of interface control devices are loaded, a plurality of disk devices, and a storage area of the plurality of disk devices to the slots. Means.

  In addition, the plurality of types of interface control devices may include a block I / O interface control device having a SAN function and a file I / O interface control device having a NAS function.

  Furthermore, as a preferred embodiment of the present invention, a configuration in which each interface control device has the same shape can be considered.

  Further, as a preferred embodiment of the present invention, a configuration in which the storage device system has means for allocating a storage area allocated to a certain interface control device to another type of interface control device can be considered.

  FIG. 1 is a diagram showing an embodiment of a storage system to which the present invention is applied. The storage system 1 is connected to the NAS client 400 via the LANs 20 and 21. In the present embodiment, the LANs 20 and 21 are IP networks (hereinafter simply referred to as “networks”). The storage system 1 is connected to the SAN client 500 via the SAN 30. In the present embodiment, the SAN 30 is assumed to be a fiber channel.

  The storage device system 1 is connected to a management terminal 18. The management terminal 18 includes a display for presenting various types of information to the user, and an input / output device such as a keyboard and a mouse for receiving input of information from the user. The management terminal 18 can communicate with the storage device system 1 via the communication network 19, and is used by the user to make various settings of the storage device system 1.

  As described above, the storage system 1 includes both a SAN configured with a fiber channel and using a block I / O interface, and an interface adapted to a NAS configured with an IP network and using a file I / O interface. A storage device system having an interface. Note that the interface of the storage system 1 can be any combination of SAN support and NAS support. In particular, it is possible to configure a system having an interface corresponding to only a SAN or only a NAS.

  The storage device system 1 includes a disk controller (hereinafter referred to as “DKC”) 11 and a storage device (hereinafter referred to as “disk”) 1700. DKC11 is a network channel adapter (CHN) 1100, fiber channel adapter (CHF) 1110, disk adapter 1200 (DKA), shared memory 13 (SM), cache memory 14 (CM), and disk pool management Part 15 (hereinafter referred to as DPM).

  The CHN 1100 is an interface control unit connected to the NAS client 400 via a file I / O interface. The CHF 1110 is an interface control unit connected to the SAN client 500 via a block I / O interface. Hereinafter, CHN and CHF are collectively referred to as a channel adapter (hereinafter referred to as CH).

  The DKA1200 is connected to the disk 1700. The DKA 1200 controls data transfer between the connected disk 1700 and the client. The SM 13 stores configuration management information for managing the configuration of the storage device system 1, control information for the CM 14, and the like. Data stored in the SM 13 is shared by all CHs and all DKAs. The CM 14 temporarily stores the data on the disk 1700 (hereinafter referred to as “cache”). CM14 data is also shared by all CHs and all DKA1200s. In the storage system 1, all the CHs can access the CM 14 and all the disks 1700. Such a configuration can be realized by a crossbar switch or the like, and the disk pool management unit 15 (hereinafter referred to as DPM) manages all the disks 1700 collectively. Specifically, the DPM 15 stores information for handling all of the storage capacity of the disk 1700 as a single disk pool. The CH, DKA, and DPM 15 are connected by the management network 16 respectively. The DPM 15 is connected to the management terminal 18 via the communication network 19.

  FIG. 2 is a diagram illustrating an external appearance of the storage device system 1. The DKC casing 115 stores CHN 1100, CHF 1110, DKA1200, SM13, and CM14. A disk unit housing (hereinafter referred to as “DKU”) 180 stores a disk 1700. The SM 13 is actually composed of a plurality of controller boards 1300. The CM 14 is also composed of a plurality of cache boards 1400. A user of the storage system 1 increases or decreases the number of boards and disks to obtain a desired storage capacity.

  The DKC housing 115 has a plurality of interface adapter slots 190. Each interface adapter slot 190 stores an adapter board on which CHN 1100 and the like are mounted. In the present embodiment, the shape of the interface adapter slot 190, the size of the adapter board, and the shape of the connector are the same regardless of the type of interface, and the compatibility of adapters of various interfaces is maintained. Therefore, any adapter board can be loaded into the interface adapter slot 190 of the DKC housing 115 regardless of the type of interface.

  Further, the user of the storage device system 1 can load the interface adapter slot 190 of the storage device system 1 by freely combining the number of adapter boards of CHN 1100 and CHF 1110. Thereby, the user of the storage device system 1 can freely configure the interface of the storage device system 1.

  FIG. 3 is a diagram showing a configuration of an adapter board in which the CHN 1100 is built. The connector 11007 is connected to a connector included in the DKC housing 115. In the present embodiment, as described above, CHN 1100 and CHF 1110 have connectors of the same shape. The interface connector 2001 supports LAN. When the adapter board is CHF1110, the interface connector 2001 corresponds to the fiber channel.

  FIG. 4 is a diagram illustrating an internal configuration of the CHN 1100. The CHN 1100 includes a processor 11001, a LAN controller 11002, a management network controller 11003, a memory 11004, an SMI / F control unit 11005, and a CMI / F control unit 11006.

  The processor 11001 controls the entire CHN 1100. The LAN controller 11002 controls communication between the CHN 1100 and the LAN. The management network controller 11003 controls communication between the CHN 1100 and the management network 16. A memory 11004 connected to the processor 11001 stores programs executed by the processor 11001 and control data.

  SMI / F control section 11005 controls data transfer between CHN 1100 and SM13. The CMI / F control unit 11006 controls data transfer between the CHN 1100 and the CM 14.

  The memory 11004 includes an operating system program 110040, a LAN controller driver program 110041, a TCP / IP program 110042, a file system program 110043, a network file system program 110044, a disk volume control program 110045, a cache control program 110046, and a disk pool information acquisition program 110048. And a disk pool information management table 110049 are stored. The memory 11004 has a data buffer 110047.

    The operating system program 110040 is used for management and input / output control of the entire program stored in the memory 11004. The LAN controller driver program 110041 is used to control the LAN controller 11002. The TCP / IP program 110042 is used to control TCP / IP, which is a communication protocol on the LAN. The file system program 110043 is used for managing files stored in the disk 1700.

  The network file system program 110044 is used for protocol control of the network file system for providing the NAS client 400 with files stored on the disk 1700. The disk volume control program 110045 is used to control access to the disk volume set in the disk 1700. The cache control program 110046 is used for management of data stored in the CM 14, control for determining hit / miss of data in the CM 14, and the like.

  The disk pool information acquisition program 110048 is executed when the CHN 1100 acquires disk pool information stored in the SM 13. The obtained disk pool information is stored in the disk pool information management table 110049. The data buffer 110047 is used to adjust the data transfer rate between the NAS client 400 and the CM 14, and to cache file data.

  The processor 11001 may be configured as a single processor or a collection of a plurality of processors. For example, a configuration of a symmetric multiprocessor that horizontally distributes processing associated with control may be used. Also, an asymmetric multiprocessor configuration in which one of the plurality of processors performs network file system protocol processing of the file I / O interface and the other processor controls the disk volume may be employed. Moreover, it is good also as a structure of those combination.

  FIG. 5 is a diagram showing the internal structure of CHF1110. The CHF 1110 includes a processor 11101, a fiber channel controller 11102, a management network controller 11103, a memory 11104, an SM control unit 11005, a CM control unit 11006, and a data buffer 11107.

  The processor 11101 controls the entire CHF 1110. The fiber channel controller 11102 controls communication between the CHF 1110 and the SAN. The management network controller 11103 performs communication control between the CHF 1110 and the management network 16. The memory 11104 connected to the processor 11101 stores programs executed by the processor 11101 and control data.

  The SM control unit 11005 controls data transfer between the CHN 1100 and SM13. The CM control unit 11006 controls data transfer between the CHN 1100 and the CM 14. The data buffer 11107 serves as a buffer memory for eliminating a difference in data transfer speed between the SAN client 500 and the CM 14.

  The memory 11104 stores a fiber channel controller driver program 111041, an operating system program 111040, a disk volume control program 111045, a cache control program 110046, a disk pool information acquisition program 111048, and a disk pool information management table 111049.

  The fiber channel controller driver program 111041 is used to control the fiber channel controller 11002. The other programs have the same functions as the programs stored in the memory of CHN 1100 in FIG.

  The processor 11101 may have a multiprocessor configuration instead of a single processor, like the processor 11001 of the CHN 1100.

  FIG. 6 shows the contents of SM13. The SM 13 has a configuration management information storage area 131. In the configuration management information storage area 131, a channel adapter centralized management table 1310 and a disk pool information centralized management table 1311 are stored. The SM 13 stores all other configuration information that the storage device system 1 has, but a description thereof is omitted in this embodiment.

  The channel adapter centralized management table 1310 stores management information for all the CHs that the storage system 1 has. Details of the channel adapter centralized management table 1310 will be described later. The disk pool information centralized management table 1311 stores management information of the disk pool 6, which is one virtual storage area composed of all the disks 1700 of the storage system 1.

  FIG. 7 is a diagram showing the internal structure of DPM15. The DPM 15 includes a processor 151, a memory 152, a management network controller 153, and a communication controller 155.

  The processor 151 performs overall control of the DPM 15. The memory 152 stores a control program executed by the processor 151 and data used for control. The management network controller 153 controls data transfer between the DPM 15 and another device included in the DKC 11. The communication controller 19 controls data transfer between the management terminal 18 and the DPM 15.

  The memory 152 stores a disk pool management program 1521, a disk pool information centralized management table 1522, a channel adapter recognition / authentication management program 1523, and a channel adapter centralized management table 1524. The disk pool management program 1521 is executed when the storage system 1 constructs and manages the disk pool 6 using the disk 1700. The channel adapter recognition / authentication management program 1523 is executed when the storage system 1 detects the loading status of the CHN 1100 and CHF 1110 and confirms that they operate.

  The disk pool information central management table 1522 manages information for managing the disk pool 6 constructed by the disk pool management program 1521 and how the storage areas of the disk pool 6 are allocated to each CH. Information for storing is stored. The contents of the disk pool information central management table 1522 are basically the same as the disk pool information central management table 1311 stored in the SM 13.

  The channel adapter centralized management table 1524 stores information on all CHs detected and authenticated by the channel adapter recognition / authentication management program 1523. The contents of the channel adapter centralized management table 1524 are basically the same as the channel adapter centralized management table 1310 stored in the SM13.

  FIG. 8 is a diagram showing the configuration of the disk pool 6. The disk pool 6 is a collection of storage capacities of a plurality of disks 1700 defined as one virtual storage area. A plurality of disk pools 6 can be set in the storage device system 1. Specifically, for example, disk devices that have the same characteristics based on differences in disk device properties, such as disk device performance characteristics (such as 7200 rpm and 15000 rpm) and disk group redundancy (such as RAID 1 and RAID 5). It is conceivable to set a disk pool for each group, or to provide a separate disk pool for each group of users who use the storage system (hereinafter referred to as “user group”).

  The number of disks 1700 that make up the disk pool 6 is arbitrary, and can be increased or decreased as necessary. As a result, the capacity of the disk pool 6 can be changed.

  FIG. 8 is a diagram showing a specific example of a correspondence relationship between one disk pool 6 and a plurality of disks 1700, specifically, a RAID group 17000 (hereinafter referred to as RG). The RG 17000 is a RAID (Redundant Array of Inexpensive Disks) composed of a plurality of disks 1700.

  A storage area allocated to one disk pool 6 is divided into a plurality of logical devices LDEV 170 (hereinafter referred to as LDEV). Further, a definition of a plurality of LDEVs 170 as a logical volume is referred to as a logical volume 1750 (hereinafter referred to as LV).

  In FIG. 8, RG17000 (RG0) composed of four disks 1700 is assigned to one disk pool 6. The storage capacity of RG0 is divided into LDEV0 to LDEVk whose storage capacity is L. Furthermore, LLV0 to LDEV2 constitute one LV0. Similarly, one LV1 (1751) is configured by LDEV3 and LDEV4. In the following, several LVs are similarly constructed. In this figure, LV0 is assigned to CHN0 and LV1 is assigned to CHN2. An LDEV may correspond to one stripe size in RAID.

  FIG. 9 is a diagram showing the configuration of the disk pool information central management table 1311 stored in the SM 13. The disk pool information central management table 1522 stored in the DPM 15 has the same configuration as the disk pool information central management table 1311. Hereinafter, the disk pool information central management table 1311 will be described.

  In the disk pool information centralized management table 1311, an entry 13110 in which the number of the disk pool 6 is registered, an entry 1311 in which the number of RG17000 is registered, an entry 1312 in which the number of LDEV170 is registered, and information on the capacity of the LDEV170 are registered. Entry 1313, entry 1314 in which the LV number is registered, CN entry 1315 in which the concatenation number of the LDEV 170 constituting the LV is registered, entry 1316 in which the CH number to which the corresponding LV is assigned is registered, disk pool 6, entry 1317 in which SN shared information indicating whether sharing between SAN (CHF) and NAS (CHN) is registered as shared information between CHs of RG and LV, SS indicating whether sharing between SAN (CHF) is possible It has an entry 1318 in which shared information is registered, an entry 1319 in which NN shared information indicating whether sharing between NAS (CHN) is registered, and an entry 1320 in which user class shared information is registered. Inter-CH shared information and the like will be described later. The CN number is a number indicating the order of combination when a plurality of LDEVs 170 are combined to generate an LV. The storage system 1 is based on information registered in the disk pool information central management table 1311. As a result, the RG 17000 and the LDEV 170 configuring the disk pool 6 are confirmed. In addition, the storage device system 1 determines which CH the LDEV 170 belonging to the disk pool 6 is assigned to based on the information registered in the disk pool information central management table 1311 and how much unused storage is in the disk pool 6. Check if capacity remains.

  FIG. 10 is a diagram showing the configuration of the channel adapter centralized management table 1310 stored in the CM 13. The channel adapter central management table 1524 of the DPM 15 has the same configuration as the channel adapter central management table 1310. The channel adapter centralized management table 1310 registers an entry 13100 in which an address in the management network 16 of the CH loaded in the storage system 1 is registered, an entry 13101 in which an identification number of CH is registered, and information on the type of CH And an entry 13103 in which information related to the operating state of the CH is registered.

Hereinafter, the operation of the storage device system 1 according to the present embodiment will be described. There are two main operations of the storage system 1 as follows.
(A) Volume allocation processing (B) Volume recognition processing (A) Volume allocation processing is processing in which the storage system 1 allocates the storage capacity included in the disk pool 6 to CH as LV.
(B) The volume recognition process is a process for the CH of the storage device system 1 to recognize the LV assigned to the CH.

  FIG. 11 is a flowchart showing the procedure of volume allocation processing. When assigning a new LV to a certain CH (hereinafter referred to as CHNi), the administrator of the storage system 1 activates the management software of the management terminal 18 (step 6100).

  The administrator inputs information indicating CHNi and information regarding the LV to be assigned to CHNi to the management terminal 18. Specifically, the administrator 1 uses the mouse or the like to display an icon indicating the LDEV 170 displayed in the unused area displayed on the display of the management terminal 18 by executing the management software on the screen. Drag to move to the area showing CHNi. At this time, the administrator can simultaneously move a plurality of LDEVs corresponding to the necessary storage capacity on the screen. In this embodiment, it is assumed that the LDEV is set in the storage device system 1 in advance at the time of product shipment (step 6101).

  Information on CHNi selected by the administrator 1 and LDEV 170 assigned to it is transmitted from the management terminal 18 to the DPM 15. The DPM 15 receives the transmitted information (step 6150).

  Upon receiving information from the management terminal 18, the DPM 15 executes the disk pool management program 1521. The DPM 15 identifies the pool number to which the specified LDEV 170 belongs and operates the disk pool information central management table 1522 to change the contents of the allocation destination CH information entry 1312 of the specified LDEV 170 from “unassigned” to “CHNi”. (Step 6151).

  Next, the DPM 15 assigns a new logical volume number LVj to the specified LDEV 170, and registers information related to the assigned LV in the LV number entry 1314 and the CN number entry 1315 of the disk pool information central management table 1522. (Step 6152).

  Thereafter, the DPM 15 notifies the CHNi that the LDEV 170 has been added and the added LDEV 170 has been defined as the logical volume LVj via the management network 16 (step 6153).

  Upon receiving this notification (step 6160), CHNi executes the disk pool information acquisition program 110048 and performs the following processing. CHNi changes the information registered in the disk pool information management table 110049 of CHNi itself according to the contents notified from DPM 15 (step 616). Further, CHNi controls SM13 to change the corresponding part of the disk pool information central management table 1311 stored in SM13 (step 6162).

  Next, CHNi executes the disk volume control program 110045 to provide information for configuring the assigned LDEV group as a logical volume LVj and information for using the assigned LDEV group as LVj (LV number, etc.) Then, it is registered in the disk pool information management table 110049 (step 6163).

  Thereafter, CHNi transmits an end report to DPM 15 (step 6164). The DPM 15 that has received the end report transmits the end report to the management terminal 18 (step 6155). This completes the volume assignment process.

  Although the processing operation for new volume allocation has been described above, processing for adding storage capacity to an existing logical volume LVp can also be realized by the same processing as described above. When adding storage capacity to an existing logical volume LVp, the user instructs the LVp to add a new LDEV 170 on the screen of the management terminal 18, and the DPM 15 receives an instruction to add the LDEV 170 to the LVp. The disk pool information central management table 1522 is changed to add the LDEV 170, the information about the change is transmitted to the CHNi, and the CHNi that receives the information about the change adds the LDEV 170 to the LVp. Changing the disk pool information central management table of 110049 and SM13 is different from the above processing. The above processing can be similarly applied to the addition of LV to CHF 1110.

  FIG. 12 is a flowchart showing the procedure of volume recognition processing by CH, which is performed when the storage device system 1 is started or when CH is added. When power is turned on to the storage device system 1 or when a CH is added to the storage device system (step 6200), each CH performs initial setting of the CH itself (step 6201).

  After completing the initial setting, each CH starts to execute the disk pool information acquisition program 110048 (step 6202). After that, each CH refers to the disk pool information centralized management table 1311 of the SM 13 and acquires information about the LV used by itself (step 6203).

  The CH that has acquired information about the LV to be used registers that information in its own disk pool information management table 110049 (step 6204). Through the above processing, each CH can recognize the LV assigned to the CH (step 6205).

  By such control, each CH has an LV that the storage device system 1 has, based on information registered in the disk pool information centralized management table 1311 in which information related to the LV of the entire storage device system 1 is registered in a lump. Can be used. In particular, in this embodiment, LVs are exclusively assigned in the disk pool information central management table 1311 so that they do not overlap with each CH, so that each CH can exclusively use the LV. Note that the above recognition process is the same regardless of the CH type such as CHN1100 and CHF1110.

  Further, in the above embodiment, the example in which the disk 1700 is subdivided into the form of the logical device LDEV170 and the logical volume LV is defined as the combination thereof has been described. However, an embodiment in which the disk 1700 is not divided into LDEVs 170 is also conceivable. In this case, a process is performed in which a disk pool 6 is generated with the entire storage capacity of one or a plurality of RGs 17000, and a predetermined storage capacity is assigned to the CH as an LV from the disk pool 6.

  According to the above-described embodiment, a storage device system having any combination of a plurality of Fiber Channel adapters with SAN or block I / O interfaces and a plurality of network channel adapters with NAS or file I / O interfaces is realized. This makes it possible to construct a storage device system that is excellent in scalability and configuration flexibility.

  In addition, since the setting and management operation of the storage area of the storage device system are performed collectively from a single management terminal, the ease of management operation can be improved and the management cost can be reduced.

  Furthermore, since the storage capacity of a storage device system in which SAN and NAS are mixed can be used safely while performing exclusive control, an environment that can be easily used is provided by centralized management of storage capacity, and storage Optimal capacity distribution can be realized and management and operation costs can be reduced.

  Next, a second embodiment of the present invention will be described. In the above-described embodiment, the method of assigning different LVs to one CHF 1110 or one CHN 1100 has been described. However, in this embodiment, a disk pool management method when assigning the same LV to a plurality of CHs , And how to share LV.

  In this embodiment, the inter-CH shared information 1317 to 1319 disclosed in FIG. 9 is used. In the present embodiment, inter-CH shared information 1317 to 1319 is set corresponding to each of the disk pool 6, RG 17000, and LV.

The inter-CH shared information mainly includes information on the following three attributes.
(1) Read / write shared attribute (hereinafter “R / W”)
(2) Read-only shared attribute (hereinafter “R”)
(3) Share prohibition attribute (hereinafter “P”)
These attributes are ranked in the order of P>R> R / W. And once these attributes are set to LV, they can only be changed to attributes of higher rank than the rank of the set attributes. In other words, an LV once set with an R attribute can be changed to a P attribute, but cannot be changed to an R / W attribute. This is because once an LV that has been prohibited from being shared can be shared, the attribute of the LV is changed to R, etc. This is because data that is not desired to be disclosed may be disclosed, or the data may be altered, resulting in a logical contradiction.

  Also, if you want to set the lower attribute to the LV for which the higher attribute is set, the user once deletes the LV and returns the storage area such as LDEV assigned to the LV to the disk pool 6, A new LV needs to be reconfigured. It is also possible to provide attributes other than these three.

  In addition, the inter-CH shared information is inherited in the order of disk pool 6> RG17000> LV or LDEV170. That is, the upper shared information (the disk pool is the highest) has priority over the shared information held by the lower RG 17000 and LDEV 170. Further, the shared information of RG17000 has priority over the shared information held by LDEV170.

  For example, if the shared attribute of the disk pool 6 is P, all the attributes such as RG 17000 below it are also P. Therefore, the storage area of the disk pool 6 in the storage device system 1 cannot be shared at all. Also, since the rank of the P attribute is set high, it is not possible to individually assign or change an attribute having a lower rank than P to the lower RG 17000 or the like. If the shared attribute of the disk pool 6 is R / W, all the attributes such as RG17000 below it are also R / W. Therefore, all the storage areas of the storage device system 1 can be shared. In this case, arbitrary attributes R and P can be individually assigned to the lower RG 17000 and the like.

  In this way, by setting whether or not sharing is possible at each logical level of the storage area of the storage system 1 such as the disk pool 6 or RG17000, the storage area of the storage system 1 can be assigned at the time of LV allocation. It is possible not to allow any sharing, or to allow any storage area of the storage system 1 to be freely shared, and to control the ease of volume allocation and the strength of security. .

  The setting of the shared volume between CHs will be described below in several cases. Here, the case where a single logical volume is shared between CHF 1110 and CHN 1100, that is, SAN and NAS, will be described in the following two forms.

  The first example is a form called NAS over SAN. This is because a computer outside the storage system 1 sends a file access request to the CHN 1100 via the LAN 20 for the file system created on the LV assigned to the CHN 1100. Data is transmitted and received via the network.

  The second example is a form called backup via SAN. This is to back up the data stored in the LV in which the file system assigned to the CHN 1100 is constructed via the SAN connected to the CHF 1110.

  Since the above example relates to sharing of logical volumes between computers between SAN and NAS, S-N shared information 1317 is used among the above-mentioned shared information between CHs.

  In FIG. 9, LV8 constructed with disk pool 6 (number 1), RG17000 (number 2), and LDEV170 (numbers 6-8) is defined as an LV shared between SAN-compatible computers and NAS-compatible computers. ing. This is apparent from the fact that a plurality of types of CH are registered in the CH number entry 1316.

  In the S-N shared information entry 1317 corresponding to LV8, information indicating that the disk pool 1 is R / W, RG2 is R / W, and LV8 is R / W is registered. All LVs in the same disk pool other than LV8 in the same RG17000 have been changed to the P attribute, and sharing is prohibited. Furthermore, the R / W attribute is set for all unused LDEVs 170.

  Such setting of the shared attribute is performed for the disk pool 6 when defining the disk pool, for RG17000, when registering the RG17000 in the disk pool 6, and for LV and LDEV, during the volume allocation processing operation. A specific setting information instruction is given by the user via the management terminal 18. SAN-SAN shared information (S-S shared information) and NAS-NAS shared information (N-N shared information) are also set in the entries 1318 and 1319 in the same manner as described above.

  In the second embodiment described above, an example in which multiple levels of attributes are set for LV sharing has been described. In the next third embodiment, an example will be described in which, in addition to these attributes, multiple levels of attributes are set for users who use LVs, and different levels of access are restricted for users at each level. In the present embodiment, sharing between NAS and NAS will be described.

In FIG. 9, the user class shared information entry 1320 of the disk pool information central management table 1311 (1522) has a subentry for each attribute (user class) related to the user. The user class has the following five attributes.
(1) Everyone: All users (“E”)
(2) Company: Users within the same company (hereinafter “C”)
(3) Domain: Users within the same domain (hereinafter “E”)
(4) WorkGroup: Users within the same workgroup (hereinafter “W”)
(5) UserGroup: Users in the same user group (hereinafter “U”)
In general, the number of target users decreases in the order of (1) to (5).

  Each user class is further given the same attributes as the inter-CH volume sharing attributes described in the second embodiment, that is, three types of attributes R / W, R, and P. The concept of the meaning, order, inheritance, changeability, etc. of these attributes is the same as in the second embodiment, and a description thereof will be omitted.

  An example of LV0 shown in FIG. 9 will be described. In each subentry of the user class shared information entry 1320, information of E = P, C = R, D = R, W = R / W, and U = R / W is registered. That is, LV0 is an LV that allows users in the same user group and the same work group to read / write, but users in the same domain and the same company that do not belong to these cannot change the contents of this LV.

  Such user class shared attribute settings are made when defining a disk pool for disk pool 6, when RG17000 is registered in disk pool 6 for RG17000, and during volume allocation processing for LV and LDEV. . This setting instruction is given by the user via the management terminal 16.

  The storage system 1 stores a user class definition information table in which information such as what name group the user classes 1 to 5 belong to is stored in order to manage users. It is necessary to have. In the user class definition information table, user information is registered for each LV.

  Specifically, since the NAS has a mechanism for managing users for each file system, the user needs to set user management information in the CHN 1100. What is necessary is just to create a user class definition information table together when setting the user information.

  According to the present embodiment, the administrator selects an appropriate user class when setting the LV in the storage device system 1. In this way, security according to the user class can be set at the LV level. With this function, even if a user of an unauthorized user class tries to access this LV, the user is authenticated for each LV, so that the access of the user without the access right is suppressed.

  With such a security function, a single large-scale storage device system 1 is installed in the data center, and a plurality of companies can maintain access security while sharing a single disk pool.

  Since the NAS originally has a user management function, it is easy to apply this embodiment to the NAS. On the other hand, by implementing the user management function in the SAN as well, disk pool management and volume allocation that realizes access security between user classes can be realized in exactly the same way.

  Further, in the present embodiment, the realization of access security between user classes within a single CH has been described, but the configuration of volume sharing between CHs of the second embodiment and the configuration of access security between user classes of the third embodiment Embodiments summarizing these are also possible. That is, the storage device system 1 can provide the user with a usage such as permitting access only to users of an appropriate user class while sharing the volume between the CHs.

[The invention's effect]
According to the present invention, the management operation cost of the storage device system can be reduced. Further, according to the present invention, it is possible to provide a storage device system in which storage capacity can be easily managed.

  Furthermore, according to the present invention, the degree of freedom of operation of the storage device system can be increased.

It is a system configuration figure of an embodiment of the present invention. It is a system outline figure of an embodiment of the present invention. It is a general-view figure of a channel adapter. It is a block diagram of a network channel adapter (CHN). It is a block diagram of a fiber channel adapter board (CHF). It is a block diagram of SM. It is a block diagram of a disk pool management part. It is a block diagram of a disk pool. It is a block diagram of a disk pool information centralized management table. It is a block diagram of a channel adapter centralized management table. It is a volume allocation process flowchart. It is a volume recognition process flowchart.

Explanation of symbols

1 ... Storage system, 11 ... Disk controller, 1700 ... Disk, 1100 ... Network channel adapter (CHN), 400 ... NAS client, 1110 ... Fibre channel adapter (CHF), 500 ... SAN client, 13 ... Shared memory (SM) , 14 ... Cache memory (CM), 15 ... Disk pool management unit (DPM), 16 ... Management network, 18 ... Management terminal.

Claims (10)

  A plurality of slots in which different types of interface devices are loaded; a plurality of disk devices; and a management unit that manages storage areas of the plurality of disk devices, wherein the management unit includes the plurality of disk devices. Information indicating a correspondence relationship between the storage area having the storage area and the interface control device of the different type loaded in the slot, and the interface device of the different type stores the storage area based on the information indicating the correspondence relation. A storage system characterized by being used.   The storage device system according to claim 1, wherein the different types of interface devices include a channel adapter board corresponding to a file I / O interface and a channel adapter board corresponding to a block I / O interface. .   3. The storage device system according to claim 2, wherein the different types of interface control devices have the same shape.   4. The storage device system according to claim 3, wherein the storage areas of the plurality of disk devices are divided into a plurality of groups based on characteristics of the respective disk devices.   The management unit holds information indicating that a storage area associated with the interface control device is also associated with another interface control device, and the other interface control device is configured based on the information. 2. The storage device system according to claim 1, wherein the storage area is accessed.   2. The storage device according to claim 1, wherein a specific attribute is assigned to a storage area of the plurality of disk devices, and an access request received via the interface control device is processed according to the attribute. system.   The storage device system according to claim 6, wherein the specific attribute is an attribute indicating whether or not the interface control device corresponding to the storage area can write data in the storage area.   The storage device system according to claim 7, wherein the specific attribute is an attribute indicating whether or not there are a plurality of the interface control devices corresponding to the storage area.   The data corresponding to the file access request is transmitted via another interface control device different from the interface control device in response to the file access request received by the interface control device. Storage system.   7. The apparatus according to claim 1, further comprising: a shared memory, wherein the shared memory stores information indicating a correspondence relationship between the plurality of interface control devices and the storage area. Storage system.

Images