US20040215879A1 - Method of creating a storage area and storage device - Google Patents
Method of creating a storage area and storage device Download PDFInfo
- Publication number
- US20040215879A1 US20040215879A1 US10/848,431 US84843104A US2004215879A1 US 20040215879 A1 US20040215879 A1 US 20040215879A1 US 84843104 A US84843104 A US 84843104A US 2004215879 A1 US2004215879 A1 US 2004215879A1
- Authority
- US
- United States
- Prior art keywords
- storage
- pool
- code
- setting conditions
- storage area
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0604—Improving or facilitating administration, e.g. storage management
- G06F3/0605—Improving or facilitating administration, e.g. storage management by facilitating the interaction with a user or administrator
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0629—Configuration or reconfiguration of storage systems
- G06F3/0631—Configuration or reconfiguration of storage systems by allocating resources to storage systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0894—Policy-based network configuration management
Definitions
- FIG. 1 is a diagram showing the configuration of a system of the first embodiment.
- 20 x represents a server as a host computer
- 30 x represents a management console
- 501 represents a SAN.
- 31 x represents a pool manager x
- 32 x represents a storage x setting utility.
- 21 x represents an OS x
- 22 x represents a pool management agent x.
- 11 x and 12 x represent LUN
- 13 x represents a pool area managed by the pool manager x.
- WWN stands for a world wide name which is information for identifying the fiber channel controller which is a connection interface to SAN 501 .
- WWNx of the computer 20 x is notified to the storage 1 .
- Access permission/inhibition is judged only from the relation between LUN and WWN set in the LUN management table 1525 .
- the internal LUN 11 can be accessed only by the server 101 having WWN 1
- the internal LUN 12 can be accessed only by the server 102 having WWN 2
- other servers cannot access these LUNs.
- Such an exclusive access control is executed by the LUN security control program 1522 .
- the administrator executes the pool area management program 1524 by operating upon the utilities 321 and 322 to set the pool area.
- the pool area management program 1524 sets 20 GB of the RAID group 2 and 80 GB of the RAID group 3 as the pool area 1 .
- the pool area definition work for the pool manager 1 is therefore completed for the storage 1 .
- the pool area definition work for the pool manager 1 is performed for the storage 2 .
- the definition work for the pool manager 2 is performed for both the storages 1 and 2 . With these operations, the preparatory work is completed. At this time it is unnecessary to define LUN.
- FIG. 8 is a diagram showing the structure of the pool manager 311 .
- the pool manager 311 has: a policy management table 3115 for setting policies to be described later; a policy definition program 3111 for supporting policy definition; a policy display program 3112 for displaying the contents of the policy management table 3115 ; a LUN forming program 3113 for supporting user formation of LUN; and a utility coordinated program 3114 for setting LUN in the LUN management table 1525 in coordination with the LUN definition program 1521 for the storage 1 ( 101 ) via the storage 1 setting utility 321 .
- Policy is predetermined rules described in easy-to-understand words and expressions so that a user can use or manage pool areas easily.
- the user can select only by using the policy, by using the attributes written in easy words, or by considering also the supplemental information.
- the policies are displayed by the policy display program 31 x 2 of the pool manager 31 x and a desired policy is selected.
- an “execute” button is depressed. Upon depression of this button, the utility coordinated program 3114 of the pool manager 1 ( 311 ) starts operating. The utility coordinated program 3114 calls the storage 1 setting utility 321 and passes arguments to it, the arguments including the pool manager number, storage number, WWN, RAID group number, host LUN number and LUN capacity. Upon reception of these arguments, the storage 1 setting utility 321 communicates with the storage 1 and passes the arguments to it.
- the LUN definition program 1521 for the storage 1 forms LU of LOGB in the RAID group 2. More specifically, the port number, target ID, host LUN, internal LUN and WWN are set in the LUN management table 1525 .
- the storage 1 After the LUN forming work is completed, the storage 1 returns a completion notice to the storage 1 setting utility 321 . Upon reception of the completion notice, the storage 1 setting utility 321 passes it to the pool manager 1 ( 311 ). The LUN forming program 3113 of the pool manager 1 ( 311 ) displays a notice that LUN formation succeeded, on the LUN forming screen. With the above operations, LUN formation is terminated.
- a plurality of pool managers exist, for example, when pool management policies are different, when a different pool management is performed depending upon an application field, when areas are intentionally divided, when types of usable storages are different, and in other cases. These cases generally occur if the environment scale becomes somewhat large. Such an environment can be dealt with the present invention, which is an advantageous feature of the invention.
- the pool area management program 1524 of the storage x limits the pool area to be managed by the pool manager 31 x , by using the pool area x management table 1527 x .
- the non-pool area is not used.
- the pool area management program 1524 makes public only the area set in the non-pool area management table 1528 , i.e., an area other than the pool area. Therefore, LUN will not be formed in the pool area.
- Storage pool management is not performed by using partitions dependent upon OSes as in conventional techniques, but storage pool management is performed by using LUN which is a general management system independent from OSes. It is therefore possible to realize storage pool management compatible with a hetero server environment having a plurality of different types of OSes.
- management area exclusive control can be realized so that a proper pool manager can be selected. It is possible to avoid critical problems such as interference between management areas by a plurality of pool managers and erroneous deletion of user data.
Abstract
An administrator is required to prepare in advance LU as a pool area when a user storage area is set to a storage. LU configuration is generally cumbersome and it is not easy for a general user to configure it. A pool manager 1 and a storage 1 setting utility in a management console 1 communicate with a program in a storage 1. The storage 1 sets a pool area having a designated capacity. In response to a volume forming request from the management console 1, the storage 1 sets a designated volume by setting the designated volume as a used capacity of the set pool area. When a volume is formed, a policy is designated to select a storage area having a corresponding attribute from the pool area.
Description
- The present invention relates to a management method for storage areas of a storage device, and more particularly to a method of exclusively managing each of a plurality of already set storage areas.
- The capacity of a storage device (hereinafter simply called a “storage”) is increasing more and more, such as a disk array device having a number of disks. For this reason, one server does not occupy one storage, but a plurality of servers share one storage by using a network dedicated for the storage, called a storage area network (SAN). SAN has the advantage that desired connections can be established between a plurality of servers and storages to share data. On the other hand, SAN has the disadvantage that the network configuration becomes complicated and operation management is difficult.
- A method called a “storage pool management” has been devised as a method of facilitating management of storage areas of a large capacity storage connected to a complicated network. With this “storage pool management”, the storage area of a storage is called a “storage pool”, and the “storage pool” is collectively managed as a general area to allocate a necessary capacity of the storage requested from a user.
- FIG. 12 is a diagram showing the structure of a conventional system for performing storage pool management.
Reference numerals reference numerals 201 to 205 representservers 1 to 5,reference numeral 301 represents a management console, andreference numeral 501 represents a SAN. - In the
management console 301,reference numeral 311 represents a pool manager which is software for executing storage pool management. - In the server20 x (x=1-5, x is used hereinafter as a representative number),
reference numeral 211 represents an OS. Reference numeral 29 x represents pool access software for making a storage pool area accessible. - In a storage1 (101),
reference numerals reference numeral 121 representsLUN 1.Reference numeral 130 represents a pool area which is collectively managed by thepool manager 311. - The
pool area 130 is realized by forming beforehand a LUN for the pool area and then assigning this LUN to the pool area. Forming an LU and assigning LU to LUN is called forming LUN. The unit of a storage area called LU is also called a volume. When the pool area is to be expanded, LUN is newly formed which is registered to thepool area 130 by thepool manager 311. - The
pool manager 311 generates a partition (191, . . . ) dedicated to each server x in thepool area 130. Thepool manager 311 notifies partition setting information to the pool access software 29 x of each server x so that partitions other than the partition dedicated to each server x cannot be recognized. - According to conventional techniques, it is necessary for a user to prepare beforehand LUN for the pool area. Generally, it is necessary for a user to configure LUN corresponding to a desired pool size by using storage configuration setting utility software (hereinafter called a utility) presented by a storage maker. In order for a user to configure LUN for a disk array storage, a number of works are required. Such works include a work of loading disk drives necessary for the disk array, a setting work for a RAID (Redundant Arrays of Inexpensive Disks) level, a formatting work for generating guarantee codes called parities for disk drive failures, a LUN setting work, a work of selecting a storage controller for controlling LUN, a work of establishing an access bus from a host to LUN, and other works. As above, a LUN configuration method is generally cumbersome. Furthermore, the LUN configuration method is different at each company or at each product type. Therefore, in the environment having a plurality of different storages, it is difficult for a user to configure LUN unless the user is an expert of configuration works, and the operation facilitation which is essential for a storage pool cannot be achieved satisfactorily.
- Even if a user is an expert of configuration works, it is difficult, from a viewpoint different from configuration works, to select an optimum storage from a plurality of storages while the cost, performance and reliability are taken into consideration, and to configure LUN having a proper capacity to be determined from a past use state and a future use state.
- Conventional techniques do not consider a hetero environment in which servers operate on different OSes. According to conventional techniques, an area used by each server is constituted of a partition whose format is dependent upon OS. Therefore, although a plurality of partitions can be set and managed in the same LU in the single OS environment, it is difficult in a hetero environment for each OS to set and manage a partition in the same LU. In order to set a plurality of partitions in the same LU and allow a plurality of servers to use corresponding partitions, access exclusive management for each partition is necessary. However, such management is not known to date.
- Still further, conventional techniques cannot deal the environment with a plurality of different pool managers.
- It is an object of the present invention to provide a method of realizing storage pool management easily without forming beforehand LUN for a storage pool area.
- It is another object of the invention to provide a method of supplying each host with a proper storage area in accordance with a metaphysical user request called a predetermined policy.
- It is another object of the invention to provide a method of increasing a disk capacity at any time or on-demand when a disk capacity becomes insufficient, without sufficient consideration of the past and future use states.
- It is still another object of the invention to provide a storage pool management method compatible with a hetero server environment.
- It is still another object of the present invention to provide a storage pool management method compatible with a plurality type of storages.
- It is still another object of the present-invention to provide a storage pool management method compatible with both an environment with a plurality of pool managers and a conventional environment without pool management.
- According to one aspect of the present invention, there is provided a method of setting a logical storage area to a storage connected to a management terminal via a network, comprising the steps of: transferring information on the logical storage area input to the management terminal to the storage via the network; and setting the logical storage area to the storage in accordance with information on the storage stored in the storage and the information on the logical storage area transferred via the network.
- According to the present invention, in the method of setting a storage area to a storage, a pool area having a capacity designated by the management console is set to the storage in the form of a pool area management table, in response to a volume forming request, a designated volume is set as a used capacity of the pool area, and the designated volume is set in the storage.
- According to the invention, in the method of setting a storage area to a storage, a plurality of policies are set in accordance with different attributes of storage areas in the storage, and in response to designation of a policy through user-friendly operation, a volume is set.
- According to the invention, the method of setting a storage area to a storage can expand the capacity of a volume on-demand when an insufficient volume capacity is detected.
- FIG. 1 is a diagram showing the configuration of a system according to a first embodiment according to the invention.
- FIG. 2 is a diagram showing the structure of a storage of the embodiment.
- FIG. 3 is a diagram showing the structure of a LUN management table of the embodiment.
- FIG. 4 is a diagram showing the structure of a management table for a
pool area 1 of the embodiment. - FIG. 5 is a diagram showing the structure of a management table for a
pool area 2 of the embodiment. - FIG. 6 is a diagram showing the structure of a management table for a non-pool area of the embodiment.
- FIG. 7 is a diagram showing the structure of a registration table for pool managers of the embodiment.
- FIG. 8 is a diagram showing a policy management table of the embodiment.
- FIG. 9 is a diagram showing the structure of a pool manager of the embodiment.
- FIG. 10 is a diagram showing a LUN setting screen of the embodiment.
- FIG. 11 is a diagram illustrating the configuration of a system according to a second embodiment of the invention.
- FIG. 12 is a diagram showing the configuration of a conventional system.
- FIG. 13 is a diagram showing a RAID group management table according to the invention.
- FIG. 1 is a diagram showing the configuration of a system of the first embodiment. In FIG. 1, 10x represents a storage x (x=1, 2, . . . , x is used hereinafter as a representative number), 20 x represents a server as a host computer, 30 x represents a management console, and 501 represents a SAN. In the management console 30 x, 31 x represents a pool manager x, and 32 x represents a storage x setting utility. In the server x, 21 x represents an OS x, and 22 x represents a pool management agent x. In the
storage 10 x, 11 xand 12 x represent LUN, and 13 x represents a pool area managed by the pool manager x. The pool area 13 x is configured overriding both thestorages pool managers - FIG. 2 is a diagram showing the structure of the
storage 1.Reference numeral 150 represents a fiber channel controller for the connection to and control ofSAN 501,reference numeral 151 represents a central control unit for controlling the whole storage,reference numeral 152 represents a memory for storing programs and data used for the internal control of thestorage 1 by thecentral control unit 151,reference numeral 153 represents a communication control unit for controlling communications with the management console x, 154 x represents a RAID group x, 11 x represents LUN1 x, and 13 x represents a pool area x. - In the
memory 152, the programs and tables described below are stored. - A
LUN definition program 1521 is used for defining and forming a plurality of LUNs. A LUNsecurity control program 1522 is used for controlling a “LUN security function” with which thecentral control unit 151 decides an access permission/inhibition for each LUN in order to make each server 20 x can exclusively use LUN. A LUN management table 1525 stores LUN security information of access inhibition/permission for each LUN of each server, attribute information of each LUN, and correspondence information between a host LUN to be recognized by the server 20 x and an internal LUN for managing the storage. A RAIDgroup definition program 1528 defines, configures and manages a RAID group constituted of a plurality of disk drives. A RAID group management table 1526 stores definition information of each RAID group. A poolarea management program 1524 is used for managing pool areas in order to manage storage pools defined in thestorage 1. A pool area x management table 1527 x stores definition information of pool areas x managed by the pool manager x. A non-pool area management table 1528 stores definition information of a non-pool area which is used by a user by directly controlling thestorage 1setting utility 321 without involving the pool manager. A pool manager registration table 1529 stores registration information of pool managers. - A disk group made of a plurality of disk drives constituting a RAID type disk array and generating redundant data called parities for disk drive failures is called a RAID group. A
RAID group 1 shown in FIG. 2 is a RAID group at alevel 5 made of five disk drives. 4D1P means a structure of data disks corresponding to four disk drives and parity disks corresponding to one disk drive. Assuming that the capacity of one disk drive is 40 GB, the total usable capacity of thisRAID group 1 is 4 drives×40 GB=160 GB. ARAID group 2 has aRAID level 1 and two disk drives having a total usable capacity of 40 GB. Other RAID groups are structured in the same way described above. - FIG. 13 shows the structure of the RAID group management table1526. The RAID group management table 1526 stores information on a RAID group number, a RAID level, a RAID structure, the number of used disk drives, the number of each used disk drive, a used disk speed, a used capacity, a remaining capacity, and a total capacity. The RAID group number is an identification number of the RAID group. The RAID level shows a RAID level of the RAID group. The RAID structure shows a RAID structure of the RAID group. The number of used disk drives shows the number of disk drives constituting the RAID group. The used disk drive number is the number of each disk drive constituting the RAID group. The used disk speed shows the speed of the disk drives constituting the RAID group, and in this embodiment, three speeds “Fast”, “Mid” and “Slow” are defined. The used capacity shows the used capacity in the total capacity of the RAID group. The remaining capacity shows the capacity still not used in the total capacity of the RAID group. The total capacity shows the total capacity of the RAID group. The RAID
group definition program 1523 sets the definition information of the RAID group management table 1526. - FIG. 3 shows the structure of the LUN management table1525. The LUN management table 1525 stores information on a port number, a target ID, a host LUN, an internal LUN, a WWN, an S_ID, an LU size, a RAID group, and a pool number.
- The port number is the number of a connection port of the fiber
channel constituting SAN 501. In this embodiment, it is assumed that the number of ports is one and “0” is stored for all ports. - The target ID is an identification ID assigned to the storage10 x having a connection interface with the server 20 x. In this embodiment, the connection interface between the computer 20 x and storage 10 x is a fiber channel, and a unique destination IF (D_ID) and an arbitrated loop physical address (AL_PA) are provided for each port. However, since the port number is stored in the LUN management table 1525, the target ID may not be stored, or D_ID and AL_PA determined when the fiber channel is initialized may be stored. If the connection interface is SCSI, a plurality of IDs can be set to the same port so that the target ID to which each LUN belongs is stored. In this embodiment, since the fiber channel is used, the column of the target ID is not used and “0” is stored for all target IDs.
- The host LUN and internal LUN show a correspondence between the internal LUN of the storage identified by a LUN management number and the host LUN recognizable by the server20 x.
- The storage10 x can define a plurality of internal LUNs. The internal LUN is a unique number for distinguishing between a plurality of LUNs. The server 20 x cannot discriminate between LUNs in some case unless they have sequential numbers starting from 0. It is therefore necessary that the storage remaps LUNs to have sequential numbers starting from 0 for each server. LUN after this conversion is called the host LUN. In FIG. 3, the
internal LUN 11 is defined as ahost LUN 0 and theinternal LUN 12 is also defined as thehost LUN 0. Although both LUNs are defined as thehost LUN 0, they are used by different computers 20 x so that only the server having WWNx shown in FIG. 3 to be described below can access. - WWN stands for a world wide name which is information for identifying the fiber channel controller which is a connection interface to
SAN 501. During a port login process for establishing a connection between ports of the fiber channel, WWNx of the computer 20 x is notified to thestorage 1. Access permission/inhibition is judged only from the relation between LUN and WWN set in the LUN management table 1525. For example, theinternal LUN 11 can be accessed only by theserver 101 havingWWN 1, theinternal LUN 12 can be accessed only by theserver 102 havingWWN 2, and other servers cannot access these LUNs. Such an exclusive access control is executed by the LUNsecurity control program 1522. - S_ID is ID information stored in the frame header of the fiber channel and identifies a source (initiator) which formed the frame. S_ID is dynamically assigned when the fiber channel is initialized. WWN is a value uniquely set by a fiber channel port exchanged during initialization. It is, however, not contained in each frame header. Therefore, by setting a relation between WWN and S_ID, the computer20 x can be identified by checking only S_ID without checking WWN for each frame.
- The LU size shows a capacity of LUN. The RAID group shows the number of the RAID group with LUN. The pool number shows the number of a pool area to which LUN belongs. A “non-pool” means a pool area not managed as a pool area. “1” and “2” show the
pool areas - FIGS. 4 and 5 show the structure of the pool area management table1527 x. FIG. 4 is a table for managing the
pool area 1, and FIG. 5 is a table for managing thepool area 2. A pool number is an identification number for distinguishing between a plurality of pool areas x. A RAID group is the number of the RAID group constituting the pool area. A RAID level is a RAID level of the RAID group. A RAID structure shows the structure of data disks and parity disks. A disk speed shows a speed of a disk drive constituting the RAID group. The number of defined LUNs shows the number of LUNs already defined in the pool area. A used capacity, a remaining capacity and a total capacity show the total used capacity, total remaining capacity and total capacity of all LUNs already defined in the RAID group having the corresponding pool number. - In FIG. 4, the pool area having the
pool number 1 is defined as having two areas including theRAID groups RAID group 2 has a disk array structure ofRAID level 1 and 1D1P. The disk drive used for theRAID group 2 has a high speed (Fast). In theRAID group 2, only one LUN having a capacity of 10 GB has already been defined, and has an unused pool area having the remaining capacity of 10 GB. TheRAID group 3 has a disk array structure ofRAID level 5 and 4D1P. The disk drive used for theRAID group 3 has a middle speed (Mid). In theRAID group 3, LUN is still not defined and has an unused pool area having the remaining capacity of 80 GB. The above-description is applied in a similar way to thepool area 2 management table shown in FIG. 5. - One storage x can have a plurality of pool area management tables1527 x so that a plurality of pool managers each can independently have the pool area management table.
- FIG. 6 is a diagram showing the structure of the non-pool area management table1528. This embodiment uses both automatic LUN definition under the storage pool management and conventional manual LUN definition using non-pool areas. The invention is applicable to the case having no non-pool areas.
- The structure of the non-pool area management table1528 is the same as that of the pool area x management tables shown in FIGS. 4 and 5. An area belonging to neither the
pool area 1 nor thepool area 2 is the non-pool area used for conventional manual setting. In the example shown in FIG. 4, the non-pool area in theRAID group 2 is an area other than thepool area 1 shown in FIG. 1 so that the total capacity is 20 GB and the remaining capacity is 20 GB because there is no defined LUN. - FIG. 7 is a diagram showing the structure of the pool manager registration table1529. In this embodiment, since there are a plurality of pool managers, it is necessary to determine in advance which pool manager deals with which pool area. A pool manager number is an identification number of each pool manager and takes an optional number which is to be guaranteed unique. A pool area number is the number of each pool area which can be managed by the pool manager.
- The operation of this system will be described. First, a pool area defining work will be described which work should be executed before storage pool management. In the following, the operation of defining the
pool area 1 under the management of thepool manager 1 will be described. - An administrator at the management console1 (301) controls the storage 1 (101) and storage 2 (102) by using the
storage 1setting utility 321 andstorage 2setting utility 322. - First, a RAID group is defined. As shown in FIG. 2, it is assumed that five RAID groups are defined for the
storage 1. Similarly, RAID groups are defined for the storage 2 (this definition is not shown). As the administrator operates upon theutilities group definition program 1523 for thestorage 1 is executed. Definition information generated upon execution of the RAIDgroup definition program 1523 is stored in the RAID group management table 1526. - Next, the administrator registers the
pool manager 1 by operating upon theutilities area management program 1524 for thestorage 101 via theutilities area management program 1524 registers the pool manager number in the pool manager registration table 1529. In this embodiment, as shown in FIG. 7, thepool manager 1 is assigned to thepool area 1. - Next, the administrator executes the pool
area management program 1524 by operating upon theutilities area management program 1524 sets 20 GB of theRAID group 2 and 80 GB of theRAID group 3 as thepool area 1. The pool area definition work for thepool manager 1 is therefore completed for thestorage 1. With similar operations, the pool area definition work for thepool manager 1 is performed for thestorage 2. Further, the definition work for thepool manager 2 is performed for both thestorages - FIG. 8 is a diagram showing the structure of the
pool manager 311. Thepool manager 311 has: a policy management table 3115 for setting policies to be described later; apolicy definition program 3111 for supporting policy definition; apolicy display program 3112 for displaying the contents of the policy management table 3115; aLUN forming program 3113 for supporting user formation of LUN; and a utility coordinatedprogram 3114 for setting LUN in the LUN management table 1525 in coordination with theLUN definition program 1521 for the storage 1 (101) via thestorage 1setting utility 321. - Policy definition by the pool manager will be described.
- Policy is predetermined rules described in easy-to-understand words and expressions so that a user can use or manage pool areas easily.
- FIG. 9 is a diagram showing the structure of the policy management table3115 managed by the
pool manager 1. In this example, three policies can be selectively used. Apolicy # 1 is “for critical job”. The attributes of the policy “for critical job” include a high performance (AA), a high reliability (A), a high cost, and a usable capacity of 10 GB. All of a specific storage name, a RAID group number, a RAID level, a disk configuration and the like are stored in a “details” column. - A
policy # 2 is “for normal job”. The attributes of the policy “for normal job” include a middle performance (B), a middle reliability (B), a middle cost, and a usable capacity of 280 GB. Supplemental information on the usable capacity of 80 GB in thestorage 1 and 200 GB in thestorage 2 is stored in the “details” column. - A
policy # 3 is “for economy job”. The attributes of the policy “for economy job” include a low performance (C), a low reliability (C), a low cost, and a usable capacity of 160 GB. Supplemental information that the usable capacity is stored in thestorage 2 having a slow disk drive is stored in the “details” column. - In accordance with the knowledge level of a user, the user can select only by using the policy, by using the attributes written in easy words, or by considering also the supplemental information. The policies are displayed by the policy display program31 x 2 of the pool manager 31 x and a desired policy is selected.
- Each policy is required to be defined before the user forms LUN. The administrator activates the storage x utility32 x and operates thereupon to acquire pool area information. The storage x setting utility 32 x sends an information acquire command together with the identification number of the pool manager to the storage x. The pool
area management program 1524 returns the information of the pool area x corresponding to the command and stored in the pool area x management table 1527 x, back to the storage x setting utility 32 x. The administrator acquired the information stored in the pool area x management table 1527 x activates the policy definition program 31 x 1 of the pool manager x to define the policy management table 31 x 5 such as shown in FIG. 9. The administrator can set arbitrarily a policy name and a grade division of performance, reliability or cost. The usable capacity and details are based upon the information in the pool area x management table 1527 x. With the above operations, a preparatory work is completed. - A work of forming LUN by a user using storage pool areas will be described. In this embodiment, a user accesses to and operates upon the
management console 301 to form LUN for theserver 202. - FIG. 10 shows an example of a screen layout formed by the
LUN forming program 3113 of themanagement console 301. A user enters an object host name, e.g., “Server 2” for which LUN is formed, into a predetermined field. The pool manager 1 (311) communicates with the pool management agent 1 (221) of the server 2 (202). The pool management agent 1 (221) searches an HBA (host bus adapter) of the server 2 (202) to find a fiber channel board. If the fiber channel board is found, its WWN is acquired and transmitted to the pool manager 1 (311). Upon reception of this, the pool manager 1 (311) displays the acquired HBA name and WWN in the HBA and WWN fields, by using theLUN forming program 3113. The user refers to the policy management table 3115 displayed on the screen, and enters a desired policy, a host LUN to be set to the server, and a desired capacity (LU size). It is herein assumed that the selected policy is “for critical job”, the designated host LUN is “0” and a designated capacity is “10 GB”. - In forming LUN in a pool area having a high cost such as “for critical job”, it can be set in such a manner that a user is required to enter a password so that only a proper person can form LUN.
- After the user completes the setting, an “execute” button is depressed. Upon depression of this button, the utility coordinated
program 3114 of the pool manager 1 (311) starts operating. The utility coordinatedprogram 3114 calls thestorage 1setting utility 321 and passes arguments to it, the arguments including the pool manager number, storage number, WWN, RAID group number, host LUN number and LUN capacity. Upon reception of these arguments, thestorage 1setting utility 321 communicates with thestorage 1 and passes the arguments to it. - The pool
area management program 1524 for thestorage 1 received the arguments confirms whether the remaining capacity written in thepool area 1 management table 15271 satisfies the designated capacity. If it is satisfied, the used capacity and remaining capacity are updated to the values after LUN formation. - In accordance with the arguments, the
LUN definition program 1521 for thestorage 1 forms LU of LOGB in theRAID group 2. More specifically, the port number, target ID, host LUN, internal LUN and WWN are set in the LUN management table 1525. - After the LUN forming work is completed, the
storage 1 returns a completion notice to thestorage 1setting utility 321. Upon reception of the completion notice, thestorage 1setting utility 321 passes it to the pool manager 1 (311). TheLUN forming program 3113 of the pool manager 1 (311) displays a notice that LUN formation succeeded, on the LUN forming screen. With the above operations, LUN formation is terminated. - If a user does not use a policy, the number of a storage and a RAID group are selected instead of selecting a policy.
- Although the LUN forming procedure by the
pool manager 1 has been described above, LUN can also be formed by thepool manager 2 in the same manner. The storage x (10 x) has a pool area x management table 1527 x dedicated to the pool manager x (31 x) to manage each area. It is therefore possible to prevent generation of access conflict by a plurality of hosts, and failures such as losing user data to be caused by erroneous setting and erroneous deletion. The poolarea management program 1524 makes public the contents of the pool area x management table 1527 x only to the pool manager x (31 x). - A plurality of pool managers exist, for example, when pool management policies are different, when a different pool management is performed depending upon an application field, when areas are intentionally divided, when types of usable storages are different, and in other cases. These cases generally occur if the environment scale becomes somewhat large. Such an environment can be dealt with the present invention, which is an advantageous feature of the invention.
- LUN is required to be formed in some cases by considering the physical structure of disk drives in order to improve the performance, such as by forming a table area of a database. In such a case, optimization may be performed through manual LUN setting by a user rather than through automatic LUN setting in a storage pool. Even if LUN setting becomes possible by storage pool management, it becomes necessary in some cases to use conventional LUN setting.
- In this embodiment, a conventional method of setting LUN by a user directly using the
storage 1setting utility 321 is also realized in the following manner. - The pool
area management program 1524 of the storage x limits the pool area to be managed by the pool manager 31 x, by using the pool area x management table 1527 x. When LUN is acquired, the non-pool area is not used. When theutility 321 forms LUN, the poolarea management program 1524 makes public only the area set in the non-pool area management table 1528, i.e., an area other than the pool area. Therefore, LUN will not be formed in the pool area. - As described above, since both the conventional LUN setting and the on-demand LUN setting by storage pool management can exist, a LUN setting method suitable for each application field can be selected.
- According to this embodiment, it is not necessary to form beforehand LUN as the storage pool area, but LUN having a desired capacity can be formed at any time when necessary.
- A user can easily form LUN only by designating a policy, without considering the physical structure of a storage.
- Storage pool management is not performed by using partitions dependent upon OSes as in conventional techniques, but storage pool management is performed by using LUN which is a general management system independent from OSes. It is therefore possible to realize storage pool management compatible with a hetero server environment having a plurality of different types of OSes.
- In this embodiment, pool management by using LUN is realized. Therefore, LUN formed for storage pool can be made secure by using the LUN security function of the storage which provides a LUN access exclusive control for servers. Pool management is therefore possible in the environment wherein a plurality of servers share a storage and LUN access exclusive control is necessary.
- Even in the environment that a plurality type of pool managers having different applications and policies exist at the same time, management area exclusive control can be realized so that a proper pool manager can be selected. It is possible to avoid critical problems such as interference between management areas by a plurality of pool managers and erroneous deletion of user data.
- Both the conventional LUN setting through direct operation of the storage setting utility by a user and LUN setting through storage pool management can be used. Therefore, a proper LUN setting method can be selected when necessary and at the same time a critical problem such as deletion of user data can be avoided.
- A modification of the embodiment will be described. In this modification, a disk capacity can be increased on-demand when the disk capacity becomes insufficient, even if the past storage capacity use history and. future use prediction cannot be obtained prior to forming LUN.
- FIG. 11 is a diagram showing the configuration of a system according to a modification of the embodiment. In FIG. 11, the server2 (202), management console 1 (301), storage 1 (101) and storage 2 (102) are derived from FIG. 1.
- Different points from the embodiment reside in that the
server 2 has afile system 242 for file storage position management, a logical volume manager (LVM) 252 for logical volume management of volumes constituted of LUN to facilitate the use of volumes, and avolume forming program 262 for forming new volumes. - A method of forming a new volume will be described. This method corresponds to a line (1) in FIG. 11. A user instructs the
volume forming program 262 to form a new volume having a proper size. At this time, the user designates only the necessary capacity without considering a future use prediction. Similar to the LUN forming program of the embodiment, setting policies are supplied to the user. The pool management agent 1 (221) transmits a server name, an HBA name of the server, WWN, setting policy and volume capacity to the pool manager 1 (311) of the management console 1 (301). The pool manager 1 (311) activates theLUN forming program 3113 to form LUN in thepool area 1 of the storage x similar to the first embodiment. With the above operations, LUN can be formed. This LUN is called a LUNa. LUNa is used as a volume by the server 2 (202). - It is then assumed that the capacity of LUNa becomes insufficient. This correspond to a line (2) shown in FIG. 11. When the
file system 242 for volume use capacity management detects that the user capacity exceeds a preset threshold value, it issues a volume expansion command toLVM 252.LVM 252 instructs the pool management agent 1 (221) to form a new LUN having a preset capacity or a capacity estimated as a proper capacity from the past volume use state. The pool management agent 1 (221) transmits the server name, HBA name of the server, WWN, setting policy used for forming the first volume, and capacity of the new LUN to the pool manager 1 (311) of the management console 1 (301). The pool manager 1 (311) activates theLUN forming program 3113 to form LUN (called a LUNb) in the pool area of the storage x similar to the first embodiment. - Upon reception of a completion notice of forming LUNb from the pool manager1 (311), the pool management agent 1 (221) notifies LVM of a completion notice of forming the new LUNb. Upon reception of this completion notice,
LVM 252 combines LUNa used as the volume and LUNb to form one logical volume and notifies this effect to thefile system 242. Thefile system 242 generates file management information of the expanded area so that the whole logical volume can be used as one continuous file system area. - With the above operations, application can run continuously without knowing the expansion of the volume size. A user is not necessary at all to perform a cumbersome volume expanding work.
- As described above, according to the modification, the volume capacity can be increased on-demand when it becomes insufficient, without involving any user work and confirmation by the application.
- According to the present invention, LUN having a necessary capacity can be formed when necessary without deciding beforehand a necessary LUN capacity. A proper LUN can be formed for each host in accordance with a user metaphysical request called a policy which is preset. Since storage pool management is performed by using LUN, storage pool management independent from the types of OSes and servers can be realized matching a hetero server environment. Since LUN security can be set for each LUN, storage pool management can be realized even for a multi-platform environment in which a plurality of servers share one storage and LUN dedicated to each server can be formed. The environment with a plurality of storage pool managers can be configured, the pool managers having different use applications, different policies, different available types of storages. Both the conventional manual LUN setting without pool management and LUN setting through storage pool management can be used so that an optimum LUN setting method can be selectively used in accordance with user needs and use applications. A disk capacity can be increased on-demand when the disk capacity becomes insufficient, even if the past storage capacity use history and future use prediction cannot be obtained.
Claims (22)
1-15. (canceled)
16. A computer program stored on a computer readable medium for setting a logical storage area in a storage system comprising:
code for receiving setting conditions from a management consol coupled to said storage system;
code for checking whether or not a storage area meeting the received setting conditions exists in said storage system;
code for defining a logical storage area that meets the received setting conditions if a storage area meeting the received setting conditions exists in said storage system; and
code for sending a completion notification from said storage system to said management consol, the completion notification indicating that the definition of the logical storage area has been completed.
17. A computer program according to claim 16
wherein said storage system comprises a storage pool comprising plural storage areas, and said computer program comprises:
code for checking whether or not a storage area meeting the received setting conditions exists in the storage pool; and
code for setting a logical storage area to the storage pool if the storage area meeting the received setting conditions exists in the storage pool.
18. A computer program according to claim 17 , wherein said setting conditions includes capacity of the logical storage area.
19. A computer program according to claim 17 , wherein said setting conditions includes a RAID group.
20. A computer program according to claim 17 , wherein said storage system comprises a pool management information for maintaining attribute of each of said plural storage areas included in said storage pool, and
said computer program comprises:
code for checking whether or not a storage area meeting the received setting conditions exists in the storage pool by referring to said pool management information.
21. A computer program according to claim 20 , further comprising:
code for updating said pool management information after setting a logical storage area to the storage pool.
22. A computer program according to claim 20 , further comprising:
code for sending attribute of each of said plural storage areas included in said storage poll from said storage system to said management consol;
code for setting a policy name to each of said plural storage areas included in said storage pool according to the received attribute;
code for receiving a policy name;
code for sending setting conditions corresponding to the received policy name to said storage system.
23. A computer program according to claim 16 , wherein said storage system comprises plural storage pools each of which comprises plural storage areas, and said setting conditions includes information for designating one of said plural storage polls, and
said computer program further comprises
code for checking whether or not a storage area meeting the received setting conditions exists in a storage pool designated by said information for designating one of said plural storage pools; and
code for setting a logical storage area to the storage pool designated by said information for designating one of said plural storage pools, if the storage area meeting the received setting conditions exists in the storage pool.
24. A computer program according to claim 23 ,
wherein said information for designating one of said plural storage pools is an identifier of a pool manager included in a management consol, said storage system receives setting conditions from said pool manager,
wherein each of said plural storage pools corresponds to one of pool managers included in at least one management consol,
and said computer program further comprises:
code for selecting one of said plural storage pools for setting a logical storage area according to the identifier of a pool manager.
25. A computer program according to claim 24 ,
wherein said storage system includes pool management tables each of which includes attribute of plural storage areas in a corresponding storage pool, and said computer program comprises:
code for checking whether or not a storage area meeting the received setting conditions exists in a storage pool corresponding to a pool manager designated by the received identifier of a pool manager by referring a pool management table of a storage pool corresponding to a pool manager designated by the received identifier of a pool manager.
26. A computer program according to claim 16 ,
wherein said storage system includes plural storage areas included in a storage pool and plural storage areas not included in a storage pool, and said computer program comprises:
code for checking whether or not a storage area meeting the received setting conditions exists in said storage poll; and code for setting a logical storage area to the storage pool if the storage area meeting the received setting conditions exists in the storage pool.
27. A storage system, comprising;
a plurality of disk drives to store data;
a network interface coupling the storage system to a network;
a computer readable medium including a computer program for setting a logical storage area in said storage system, the computer program comprising:
code for receiving setting conditions from a management consol coupled to said storage system;
code for checking whether or not a storage area meeting the received setting conditions exists in said storage system;
code for defining a logical storage area that meets the received setting conditions if a storage area meeting the received setting conditions exists in said storage system; and
code for sending a completion notification from said storage system to said management consol, the completion notification indicating that the definition of the logical storage area has been completed.
28. A storage system according to claim 27 , wherein said storage system comprises a storage pool comprising plural storage areas, and said computer program comprises:
code for checking whether or not a storage area meeting the received setting conditions exists in the storage pool; and
code for setting a logical storage area to the storage pool if the storage area meeting the received setting conditions exists in the storage pool.
29. A storage system according to claim 28 , wherein said setting conditions includes capacity of the logical storage area.
30. A storage system according to claim 28 , wherein said setting conditions includes a RAID group.
31. A storage system according to claim 28 , wherein said storage system comprises a pool management information for maintaining attribute of each of said plural storage areas included in said storage pool, and said computer program comprises:
code for checking whether or not a storage area meeting the received setting conditions exists in the storage pool by referring to said pool management information.
32. A storage system according to claim 31 , the program further comprising:
code for updating said pool management information after setting a logical storage area to the storage pool.
33 A storage system according to claim 27 , wherein said storage system comprises plural storage pools each of which comprises plural storage areas, and said setting conditions includes information for designating one of said plural storage polls, and said computer program further comprises
code for checking whether or not a storage area meeting the received setting conditions exists in a storage pool designated by said information for designating one of said plural storage pools; and
code for setting a logical storage area to the storage pool designated by said information for designating one of said plural storage pools, if the storage area meeting the received setting conditions exists in the storage pool.
34 A storage system according to claim 33 wherein said information for designating one of said plural storage pools is an identifier of a pool manager included in a management consol, said storage system receives setting conditions from said pool manager, wherein each of said plural storage pools corresponds to one of pool managers included in at least one management consol, and said computer program further comprises:
code for selecting one of said plural storage pools for setting a logical storage area according to the identifier of a pool manager.
35 A storage system according to claim 34
wherein said storage system includes pool management tables each of which includes attribute of plural storage areas in a corresponding storage pool, and said computer program comprises:
code for checking whether or not a storage area meeting the received setting conditions exists in a storage pool corresponding to a pool manager designated by the received identifier of a pool manager by referring a pool management table of a storage pool corresponding to a pool manager designated by the received identifier of a pool manager.
36 A storage system according to claim 27 , wherein said storage system includes plural storage areas included in a storage pool and plural storage areas not included in a storage pool, and said computer program comprises:
code for checking whether or not a storage area meeting the received setting conditions exists in said storage poll; and
code for setting a logical storage area to the storage pool if the storage area meeting the received setting conditions exists in the storage pool.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/848,431 US20040215879A1 (en) | 2001-01-25 | 2004-05-17 | Method of creating a storage area and storage device |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2001016468A JP2002222061A (en) | 2001-01-25 | 2001-01-25 | Method for setting storage area, storage device, and program storage medium |
JP2001-016468 | 2001-01-25 | ||
US09/797,261 US6912627B2 (en) | 2001-01-25 | 2001-02-28 | Method of creating a storage area & storage device |
US10/848,431 US20040215879A1 (en) | 2001-01-25 | 2004-05-17 | Method of creating a storage area and storage device |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/797,261 Continuation US6912627B2 (en) | 2001-01-25 | 2001-02-28 | Method of creating a storage area & storage device |
Publications (1)
Publication Number | Publication Date |
---|---|
US20040215879A1 true US20040215879A1 (en) | 2004-10-28 |
Family
ID=18882836
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/797,261 Expired - Fee Related US6912627B2 (en) | 2001-01-25 | 2001-02-28 | Method of creating a storage area & storage device |
US10/848,431 Abandoned US20040215879A1 (en) | 2001-01-25 | 2004-05-17 | Method of creating a storage area and storage device |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/797,261 Expired - Fee Related US6912627B2 (en) | 2001-01-25 | 2001-02-28 | Method of creating a storage area & storage device |
Country Status (3)
Country | Link |
---|---|
US (2) | US6912627B2 (en) |
EP (1) | EP1227402A3 (en) |
JP (1) | JP2002222061A (en) |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040225662A1 (en) * | 2003-05-08 | 2004-11-11 | Hiroshi Nojima | Storage operation management system |
US20060101203A1 (en) * | 2004-11-09 | 2006-05-11 | Fujitsu Computer Technologies Limited | Storage virtualization apparatus |
US20060117215A1 (en) * | 2004-11-09 | 2006-06-01 | Fujitsu Limited | Storage virtualization apparatus and computer system using the same |
US20060139411A1 (en) * | 2004-12-29 | 2006-06-29 | Lexmark International, Inc. | Device and structure arrangements for integrated circuits and methods for analyzing the same |
US20060282636A1 (en) * | 2005-06-08 | 2006-12-14 | Masayuki Yamamoto | Configuration management method for computer system including storage systems |
US20070055713A1 (en) * | 2005-09-02 | 2007-03-08 | Hitachi, Ltd. | Computer system, storage system and method for extending volume capacity |
US20070192560A1 (en) * | 2006-02-10 | 2007-08-16 | Hitachi, Ltd. | Storage controller |
US20080065853A1 (en) * | 2004-02-18 | 2008-03-13 | Kenji Yamagami | Storage control system and control method for the same |
US20080271034A1 (en) * | 2007-04-26 | 2008-10-30 | Nec Corporation | Resource allocation system, resource allocation method, and resource allocation program |
US20090119529A1 (en) * | 2007-11-02 | 2009-05-07 | Hitachi Ltd. | Configuration optimization method for a storage system |
US20100082900A1 (en) * | 2008-10-01 | 2010-04-01 | Hitachi, Ltd. | Management device for storage device |
US20110185130A1 (en) * | 2010-01-25 | 2011-07-28 | Hitachi, Ltd. | Computer system and storage consolidation management method |
US20120226857A1 (en) * | 2009-03-12 | 2012-09-06 | Hitachi, Ltd. | Computer and method for managing storage apparatus |
US20130067188A1 (en) * | 2011-09-12 | 2013-03-14 | Microsoft Corporation | Storage device drivers and cluster participation |
Families Citing this family (124)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6658436B2 (en) | 2000-01-31 | 2003-12-02 | Commvault Systems, Inc. | Logical view and access to data managed by a modular data and storage management system |
WO2002065329A1 (en) * | 2001-02-14 | 2002-08-22 | The Escher Group, Ltd. | Peer-to peer enterprise storage |
US8392586B2 (en) * | 2001-05-15 | 2013-03-05 | Hewlett-Packard Development Company, L.P. | Method and apparatus to manage transactions at a network storage device |
WO2003005209A2 (en) * | 2001-06-14 | 2003-01-16 | Cable & Wireless Internet Services, Inc. | Secured shared storage architecture |
US7685261B1 (en) | 2001-06-29 | 2010-03-23 | Symantec Operating Corporation | Extensible architecture for the centralized discovery and management of heterogeneous SAN components |
US7734781B2 (en) * | 2001-07-09 | 2010-06-08 | Savvis Communications Corporation | Methods and systems for shared storage virtualization |
JP2003029932A (en) * | 2001-07-18 | 2003-01-31 | Hitachi Ltd | Disk controller |
US7864758B1 (en) | 2001-09-28 | 2011-01-04 | Emc Corporation | Virtualization in a storage system |
US7404000B2 (en) * | 2001-09-28 | 2008-07-22 | Emc Corporation | Protocol translation in a storage system |
US7558264B1 (en) | 2001-09-28 | 2009-07-07 | Emc Corporation | Packet classification in a storage system |
JP2005505045A (en) | 2001-09-28 | 2005-02-17 | コムヴォールト・システムズ・インコーポレーテッド | Method and apparatus for creating and managing a quick recovery volume |
US7707304B1 (en) | 2001-09-28 | 2010-04-27 | Emc Corporation | Storage switch for storage area network |
US7185062B2 (en) * | 2001-09-28 | 2007-02-27 | Emc Corporation | Switch-based storage services |
US7421509B2 (en) * | 2001-09-28 | 2008-09-02 | Emc Corporation | Enforcing quality of service in a storage network |
US6976134B1 (en) | 2001-09-28 | 2005-12-13 | Emc Corporation | Pooling and provisioning storage resources in a storage network |
US20030154271A1 (en) * | 2001-10-05 | 2003-08-14 | Baldwin Duane Mark | Storage area network methods and apparatus with centralized management |
US6895467B2 (en) * | 2001-10-22 | 2005-05-17 | Hewlett-Packard Development Company, L.P. | System and method for atomizing storage |
US7159080B1 (en) * | 2001-12-20 | 2007-01-02 | Network Appliance, Inc. | System and method for storing storage operating system data in switch ports |
US7650412B2 (en) | 2001-12-21 | 2010-01-19 | Netapp, Inc. | Systems and method of implementing disk ownership in networked storage |
US7296068B1 (en) * | 2001-12-21 | 2007-11-13 | Network Appliance, Inc. | System and method for transfering volume ownership in net-worked storage |
JP2003345518A (en) * | 2002-05-29 | 2003-12-05 | Hitachi Ltd | Method for setting disk array device, program, information processor, disk array device |
US7219189B1 (en) * | 2002-05-31 | 2007-05-15 | Veritas Operating Corporation | Automatic operating system handle creation in response to access control changes |
US7194538B1 (en) | 2002-06-04 | 2007-03-20 | Veritas Operating Corporation | Storage area network (SAN) management system for discovering SAN components using a SAN management server |
US7886031B1 (en) | 2002-06-04 | 2011-02-08 | Symantec Operating Corporation | SAN configuration utility |
US6889285B2 (en) * | 2002-08-29 | 2005-05-03 | International Business Machines Corporation | Apparatus and method to maintain information using a plurality of storage attributes |
US6954768B2 (en) * | 2002-08-29 | 2005-10-11 | International Business Machines Corporation | Method, system, and article of manufacture for managing storage pools |
US7260628B2 (en) | 2002-09-06 | 2007-08-21 | Hitachi, Ltd. | Event notification in storage networks |
US8019849B1 (en) | 2002-09-13 | 2011-09-13 | Symantec Operating Corporation | Server-side storage area network management interface |
US7401338B1 (en) | 2002-09-27 | 2008-07-15 | Symantec Operating Corporation | System and method for an access layer application programming interface for managing heterogeneous components of a storage area network |
CA2508089A1 (en) | 2002-10-07 | 2004-04-22 | Commvault Systems, Inc. | System and method for managing stored data |
JP4175083B2 (en) * | 2002-10-29 | 2008-11-05 | 株式会社日立製作所 | Storage device management computer and program |
US7305379B2 (en) * | 2002-12-19 | 2007-12-04 | International Business Machines Corporation | System for automated storage management for databases |
JP4345313B2 (en) * | 2003-01-24 | 2009-10-14 | 株式会社日立製作所 | Operation management method of storage system based on policy |
JP4283004B2 (en) * | 2003-02-04 | 2009-06-24 | 株式会社日立製作所 | Disk control device and control method of disk control device |
JP4651913B2 (en) * | 2003-02-17 | 2011-03-16 | 株式会社日立製作所 | Storage system |
US20040181707A1 (en) * | 2003-03-11 | 2004-09-16 | Hitachi, Ltd. | Method and apparatus for seamless management for disaster recovery |
WO2004090740A1 (en) | 2003-04-03 | 2004-10-21 | Commvault Systems, Inc. | System and method for dynamically sharing media in a computer network |
JP2004334574A (en) | 2003-05-08 | 2004-11-25 | Hitachi Ltd | Operation managing program and method of storage, and managing computer |
US7885256B1 (en) | 2003-05-30 | 2011-02-08 | Symantec Operating Corporation | SAN fabric discovery |
US7454569B2 (en) * | 2003-06-25 | 2008-11-18 | Commvault Systems, Inc. | Hierarchical system and method for performing storage operations in a computer network |
JP4266725B2 (en) | 2003-06-27 | 2009-05-20 | 株式会社日立製作所 | Storage system |
JP2005038071A (en) | 2003-07-17 | 2005-02-10 | Hitachi Ltd | Management method for optimizing storage capacity |
JP4437650B2 (en) | 2003-08-25 | 2010-03-24 | 株式会社日立製作所 | Storage system |
JP2005074578A (en) * | 2003-09-01 | 2005-03-24 | Sony Corp | Particle array, its manufacturing method, and magnetic recording medium |
CN100350371C (en) * | 2003-10-07 | 2007-11-21 | 普安科技股份有限公司 | Consistency initializing method of on-line magnetic disc array |
JP4492084B2 (en) * | 2003-10-07 | 2010-06-30 | 株式会社日立製作所 | Storage path control method |
JP4257783B2 (en) * | 2003-10-23 | 2009-04-22 | 株式会社日立製作所 | Logically partitionable storage device and storage device system |
JP4863605B2 (en) | 2004-04-09 | 2012-01-25 | 株式会社日立製作所 | Storage control system and method |
WO2005050385A2 (en) * | 2003-11-13 | 2005-06-02 | Commvault Systems, Inc. | System and method for performing integrated storage operations |
US7500000B2 (en) * | 2003-12-17 | 2009-03-03 | International Business Machines Corporation | Method and system for assigning or creating a resource |
US7340639B1 (en) | 2004-01-08 | 2008-03-04 | Network Appliance, Inc. | System and method for proxying data access commands in a clustered storage system |
JP2005228278A (en) | 2004-01-14 | 2005-08-25 | Hitachi Ltd | Management method, management device and management program of storage area |
JP4227035B2 (en) * | 2004-02-03 | 2009-02-18 | 株式会社日立製作所 | Computer system, management device, storage device, and computer device |
JP2005267008A (en) | 2004-03-17 | 2005-09-29 | Hitachi Ltd | Method and system for storage management |
JP4485230B2 (en) | 2004-03-23 | 2010-06-16 | 株式会社日立製作所 | Migration execution method |
JP4681247B2 (en) | 2004-04-08 | 2011-05-11 | 株式会社日立製作所 | Disk array device and disk array device control method |
JP4878433B2 (en) * | 2004-05-11 | 2012-02-15 | 株式会社日立製作所 | Storage device configuration management system and configuration management method |
JP4455153B2 (en) | 2004-05-14 | 2010-04-21 | 株式会社日立製作所 | Storage device management method and system |
US20050268036A1 (en) * | 2004-05-27 | 2005-12-01 | Hewlett-Packard Development Company, L.P. | Storage configuration |
JP2006048313A (en) * | 2004-08-04 | 2006-02-16 | Hitachi Ltd | Method for managing storage system managed by a plurality of administrators |
US7350102B2 (en) | 2004-08-26 | 2008-03-25 | International Business Machine Corporation | Cost reduction schema for advanced raid algorithms |
JP4842909B2 (en) * | 2004-08-30 | 2011-12-21 | 株式会社日立製作所 | Storage system and data relocation control device |
US7395396B2 (en) | 2004-08-30 | 2008-07-01 | Hitachi, Ltd. | Storage system and data relocation control device |
JP2006092154A (en) * | 2004-09-22 | 2006-04-06 | Hitachi Ltd | Storage system and storage control method |
US7062628B2 (en) * | 2004-09-28 | 2006-06-13 | Hitachi, Ltd. | Method and apparatus for storage pooling and provisioning for journal based storage and recovery |
US7062624B2 (en) * | 2004-09-29 | 2006-06-13 | Hitachi, Ltd. | Method for managing volume groups considering storage tiers |
EP1811392A4 (en) * | 2004-10-06 | 2008-05-14 | Fujitsu Ltd | System environment setting supporting program, system environment setting supporting method, and system environment setting supporting device |
US7827260B2 (en) * | 2004-10-12 | 2010-11-02 | International Business Machines Corporation | Apparatus, system, and method for configuring zone control of a network feature in a heterogeneous network |
JP4532237B2 (en) * | 2004-10-29 | 2010-08-25 | 株式会社日立製作所 | Computer and access control method in computer |
WO2006053084A2 (en) | 2004-11-05 | 2006-05-18 | Commvault Systems, Inc. | Method and system of pooling storage devices |
US7769975B2 (en) * | 2004-11-15 | 2010-08-03 | International Business Machines Corporation | Method for configuring volumes in a storage system |
US8959299B2 (en) | 2004-11-15 | 2015-02-17 | Commvault Systems, Inc. | Using a snapshot as a data source |
JPWO2006054334A1 (en) * | 2004-11-16 | 2008-05-29 | 富士通株式会社 | Storage area allocation device, storage area allocation method, and storage area allocation program |
US8019842B1 (en) | 2005-01-27 | 2011-09-13 | Netapp, Inc. | System and method for distributing enclosure services data to coordinate shared storage |
US8180855B2 (en) | 2005-01-27 | 2012-05-15 | Netapp, Inc. | Coordinated shared storage architecture |
US7928591B2 (en) * | 2005-02-11 | 2011-04-19 | Wintec Industries, Inc. | Apparatus and method for predetermined component placement to a target platform |
JP4690765B2 (en) * | 2005-04-26 | 2011-06-01 | 株式会社日立製作所 | Storage management system, storage management server, data relocation control method, and data relocation control program |
US8073899B2 (en) * | 2005-04-29 | 2011-12-06 | Netapp, Inc. | System and method for proxying data access commands in a storage system cluster |
US7523273B2 (en) * | 2005-05-05 | 2009-04-21 | International Business Machines Corporation | Autonomic storage provisioning to enhance storage virtualization infrastructure availability |
JP2007004297A (en) * | 2005-06-21 | 2007-01-11 | Fujitsu Ltd | Storage unit management system |
US7457910B2 (en) * | 2005-06-29 | 2008-11-25 | Sandisk Corproation | Method and system for managing partitions in a storage device |
US20070022314A1 (en) * | 2005-07-22 | 2007-01-25 | Pranoop Erasani | Architecture and method for configuring a simplified cluster over a network with fencing and quorum |
JP4322240B2 (en) * | 2005-09-15 | 2009-08-26 | 株式会社日立製作所 | Reboot method, system and program |
US20070088917A1 (en) * | 2005-10-14 | 2007-04-19 | Ranaweera Samantha L | System and method for creating and maintaining a logical serial attached SCSI communication channel among a plurality of storage systems |
US8484365B1 (en) | 2005-10-20 | 2013-07-09 | Netapp, Inc. | System and method for providing a unified iSCSI target with a plurality of loosely coupled iSCSI front ends |
US20070101058A1 (en) * | 2005-10-27 | 2007-05-03 | Kinnan Keith R | Storage unit configuration |
JP4896500B2 (en) * | 2005-11-14 | 2012-03-14 | 株式会社日立製作所 | Virtual volume control method with device stop |
JP4684864B2 (en) * | 2005-11-16 | 2011-05-18 | 株式会社日立製作所 | Storage device system and storage control method |
US7797570B2 (en) | 2005-11-29 | 2010-09-14 | Netapp, Inc. | System and method for failover of iSCSI target portal groups in a cluster environment |
US7707463B2 (en) * | 2005-11-30 | 2010-04-27 | International Business Machines Corporation | Implementing directory organization to selectively optimize performance or reliability |
JP4890033B2 (en) * | 2006-01-19 | 2012-03-07 | 株式会社日立製作所 | Storage device system and storage control method |
JP4856467B2 (en) * | 2006-05-01 | 2012-01-18 | 株式会社日立製作所 | Storage resource management system, storage resource management method, and management computer |
US7428614B2 (en) * | 2006-07-27 | 2008-09-23 | Hitachi, Ltd. | Management system for a virtualized storage environment |
JP4846486B2 (en) | 2006-08-18 | 2011-12-28 | 富士通株式会社 | Information processing apparatus and control method thereof |
JP4939154B2 (en) * | 2006-09-14 | 2012-05-23 | 株式会社日立製作所 | Storage apparatus and configuration setting method |
JP2008117094A (en) * | 2006-11-02 | 2008-05-22 | Hitachi Ltd | Storage system, storage device, and storage management method |
US7925758B1 (en) | 2006-11-09 | 2011-04-12 | Symantec Operating Corporation | Fibre accelerated pipe data transport |
US7613947B1 (en) | 2006-11-30 | 2009-11-03 | Netapp, Inc. | System and method for storage takeover |
JP5069011B2 (en) * | 2007-01-29 | 2012-11-07 | 株式会社日立製作所 | Storage module and capacity pool free space adjustment method |
JP4871758B2 (en) * | 2007-02-26 | 2012-02-08 | 株式会社日立製作所 | Volume allocation method |
US7941598B2 (en) * | 2007-08-08 | 2011-05-10 | Hitachi, Ltd. | Method and apparatus for capacity on demand dynamic chunk allocation |
US20090049236A1 (en) * | 2007-08-15 | 2009-02-19 | Hitachi, Ltd. | System and method for data protection management for network storage |
US8418072B1 (en) * | 2007-12-24 | 2013-04-09 | Emc Corporation | UI data model abstraction |
US7904652B1 (en) * | 2007-12-28 | 2011-03-08 | Emc Corporation | Application aware use of added devices |
US8082330B1 (en) * | 2007-12-28 | 2011-12-20 | Emc Corporation | Application aware automated storage pool provisioning |
US8015343B2 (en) * | 2008-08-08 | 2011-09-06 | Amazon Technologies, Inc. | Providing executing programs with reliable access to non-local block data storage |
JP4685911B2 (en) * | 2008-10-01 | 2011-05-18 | 株式会社日立製作所 | Storage system with LU setting function |
US9092500B2 (en) | 2009-09-03 | 2015-07-28 | Commvault Systems, Inc. | Utilizing snapshots for access to databases and other applications |
US8719767B2 (en) | 2011-03-31 | 2014-05-06 | Commvault Systems, Inc. | Utilizing snapshots to provide builds to developer computing devices |
US8595191B2 (en) | 2009-12-31 | 2013-11-26 | Commvault Systems, Inc. | Systems and methods for performing data management operations using snapshots |
US8433682B2 (en) | 2009-12-31 | 2013-04-30 | Commvault Systems, Inc. | Systems and methods for analyzing snapshots |
US8464003B2 (en) * | 2010-02-17 | 2013-06-11 | Hitachi, Ltd. | Method and apparatus to manage object based tier |
US8711864B1 (en) | 2010-03-30 | 2014-04-29 | Chengdu Huawei Symantec Technologies Co., Ltd. | System and method for supporting fibre channel over ethernet communication |
US20120124183A1 (en) * | 2010-03-31 | 2012-05-17 | James Louis Long | Clients and servers for allocating and managing exclusive access to a portion of remote storage space |
JP5148664B2 (en) * | 2010-08-11 | 2013-02-20 | 富士通株式会社 | Setting program and setting device |
US8356147B2 (en) | 2010-08-20 | 2013-01-15 | Hitachi, Ltd. | Tiered storage pool management and control for loosely coupled multiple storage environment |
US9021198B1 (en) | 2011-01-20 | 2015-04-28 | Commvault Systems, Inc. | System and method for sharing SAN storage |
CN102761579B (en) * | 2011-04-29 | 2015-12-09 | 国际商业机器公司 | Storage are network is utilized to transmit the method and system of data |
US9158828B1 (en) * | 2011-12-19 | 2015-10-13 | Emc Corporation | Techniques using associated object properties |
US9628350B2 (en) * | 2014-11-05 | 2017-04-18 | Amazon Technologies, Inc. | Dynamic scaling of storage volumes for storage client file systems |
US10311150B2 (en) | 2015-04-10 | 2019-06-04 | Commvault Systems, Inc. | Using a Unix-based file system to manage and serve clones to windows-based computing clients |
US10430270B2 (en) | 2017-12-04 | 2019-10-01 | Bank Of America Corporation | System for migrating data using dynamic feedback |
US11138123B2 (en) * | 2019-10-01 | 2021-10-05 | EMC IP Holding Company LLC | Local cache size control in a storage array |
US11593223B1 (en) | 2021-09-02 | 2023-02-28 | Commvault Systems, Inc. | Using resource pool administrative entities in a data storage management system to provide shared infrastructure to tenants |
Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5897661A (en) * | 1997-02-25 | 1999-04-27 | International Business Machines Corporation | Logical volume manager and method having enhanced update capability with dynamic allocation of storage and minimal storage of metadata information |
US6330621B1 (en) * | 1999-01-15 | 2001-12-11 | Storage Technology Corporation | Intelligent data storage manager |
US20020019908A1 (en) * | 2000-06-02 | 2002-02-14 | Reuter James M. | System and method for managing virtual storage |
US6389432B1 (en) * | 1999-04-05 | 2002-05-14 | Auspex Systems, Inc. | Intelligent virtual volume access |
US20020087787A1 (en) * | 2000-06-19 | 2002-07-04 | Storage Technology Corporation | System to support dynamically flexible data definitions and storage requirements |
US20020133669A1 (en) * | 1999-06-11 | 2002-09-19 | Narayan Devireddy | Policy based storage configuration |
US6854034B1 (en) * | 1999-08-27 | 2005-02-08 | Hitachi, Ltd. | Computer system and a method of assigning a storage device to a computer |
US7082462B1 (en) * | 1999-03-12 | 2006-07-25 | Hitachi, Ltd. | Method and system of managing an access to a private logical unit of a storage system |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3837953B2 (en) * | 1999-03-12 | 2006-10-25 | 株式会社日立製作所 | Computer system |
-
2001
- 2001-01-25 JP JP2001016468A patent/JP2002222061A/en active Pending
- 2001-02-22 EP EP01104302A patent/EP1227402A3/en not_active Withdrawn
- 2001-02-28 US US09/797,261 patent/US6912627B2/en not_active Expired - Fee Related
-
2004
- 2004-05-17 US US10/848,431 patent/US20040215879A1/en not_active Abandoned
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5897661A (en) * | 1997-02-25 | 1999-04-27 | International Business Machines Corporation | Logical volume manager and method having enhanced update capability with dynamic allocation of storage and minimal storage of metadata information |
US6330621B1 (en) * | 1999-01-15 | 2001-12-11 | Storage Technology Corporation | Intelligent data storage manager |
US20020032816A1 (en) * | 1999-01-15 | 2002-03-14 | Storage Technology Corporation | Intelligent data storage manager |
US7082462B1 (en) * | 1999-03-12 | 2006-07-25 | Hitachi, Ltd. | Method and system of managing an access to a private logical unit of a storage system |
US6389432B1 (en) * | 1999-04-05 | 2002-05-14 | Auspex Systems, Inc. | Intelligent virtual volume access |
US20020133669A1 (en) * | 1999-06-11 | 2002-09-19 | Narayan Devireddy | Policy based storage configuration |
US6854034B1 (en) * | 1999-08-27 | 2005-02-08 | Hitachi, Ltd. | Computer system and a method of assigning a storage device to a computer |
US20020019908A1 (en) * | 2000-06-02 | 2002-02-14 | Reuter James M. | System and method for managing virtual storage |
US20020087787A1 (en) * | 2000-06-19 | 2002-07-04 | Storage Technology Corporation | System to support dynamically flexible data definitions and storage requirements |
Cited By (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040225662A1 (en) * | 2003-05-08 | 2004-11-11 | Hiroshi Nojima | Storage operation management system |
US7467143B2 (en) | 2003-05-08 | 2008-12-16 | Hitachi, Ltd. | Storage operation management system |
US7555601B2 (en) | 2004-02-18 | 2009-06-30 | Hitachi, Ltd. | Storage control system including virtualization and control method for same |
US8838917B2 (en) | 2004-02-18 | 2014-09-16 | Hitachi, Ltd. | Storage control system and control method for the same |
US8595431B2 (en) | 2004-02-18 | 2013-11-26 | Hitachi, Ltd. | Storage control system including virtualization and control method for same |
US8131956B2 (en) | 2004-02-18 | 2012-03-06 | Hitachi, Ltd. | Virtual storage system and method for allocating storage areas and releasing storage areas from allocation based on certain commands |
US20080065853A1 (en) * | 2004-02-18 | 2008-03-13 | Kenji Yamagami | Storage control system and control method for the same |
US20060101203A1 (en) * | 2004-11-09 | 2006-05-11 | Fujitsu Computer Technologies Limited | Storage virtualization apparatus |
US20060117215A1 (en) * | 2004-11-09 | 2006-06-01 | Fujitsu Limited | Storage virtualization apparatus and computer system using the same |
US20060139411A1 (en) * | 2004-12-29 | 2006-06-29 | Lexmark International, Inc. | Device and structure arrangements for integrated circuits and methods for analyzing the same |
US20100274883A1 (en) * | 2005-06-08 | 2010-10-28 | Masayuki Yamamoto | Configuration management method for computer system including storage systems |
US20060282636A1 (en) * | 2005-06-08 | 2006-12-14 | Masayuki Yamamoto | Configuration management method for computer system including storage systems |
US20090300285A1 (en) * | 2005-09-02 | 2009-12-03 | Hitachi, Ltd. | Computer system, storage system and method for extending volume capacity |
US20070055713A1 (en) * | 2005-09-02 | 2007-03-08 | Hitachi, Ltd. | Computer system, storage system and method for extending volume capacity |
US8082394B2 (en) | 2005-09-02 | 2011-12-20 | Hitachi, Ltd. | Computer system, storage system and method for extending volume capacity |
US20070192560A1 (en) * | 2006-02-10 | 2007-08-16 | Hitachi, Ltd. | Storage controller |
US8352678B2 (en) | 2006-02-10 | 2013-01-08 | Hitachi, Ltd. | Storage controller |
US8037239B2 (en) * | 2006-02-10 | 2011-10-11 | Hitachi, Ltd. | Storage controller |
US20080271034A1 (en) * | 2007-04-26 | 2008-10-30 | Nec Corporation | Resource allocation system, resource allocation method, and resource allocation program |
US8161489B2 (en) | 2007-04-26 | 2012-04-17 | Nec Corporation | Resource sharing and allocation between a plurality of different raid policies on groups of disks |
US8281068B2 (en) | 2007-11-02 | 2012-10-02 | Hitachi, Ltd. | Configuration optimization method for a storage system |
US20090119529A1 (en) * | 2007-11-02 | 2009-05-07 | Hitachi Ltd. | Configuration optimization method for a storage system |
US20100082900A1 (en) * | 2008-10-01 | 2010-04-01 | Hitachi, Ltd. | Management device for storage device |
US20120226857A1 (en) * | 2009-03-12 | 2012-09-06 | Hitachi, Ltd. | Computer and method for managing storage apparatus |
US8527700B2 (en) * | 2009-03-12 | 2013-09-03 | Hitachi, Ltd. | Computer and method for managing storage apparatus |
US20110185130A1 (en) * | 2010-01-25 | 2011-07-28 | Hitachi, Ltd. | Computer system and storage consolidation management method |
US8707004B2 (en) | 2010-01-25 | 2014-04-22 | Hitachi, Ltd. | Computer system and storage consolidation management method |
US20130067188A1 (en) * | 2011-09-12 | 2013-03-14 | Microsoft Corporation | Storage device drivers and cluster participation |
US8886910B2 (en) * | 2011-09-12 | 2014-11-11 | Microsoft Corporation | Storage device drivers and cluster participation |
Also Published As
Publication number | Publication date |
---|---|
EP1227402A2 (en) | 2002-07-31 |
JP2002222061A (en) | 2002-08-09 |
US20020099914A1 (en) | 2002-07-25 |
US6912627B2 (en) | 2005-06-28 |
EP1227402A3 (en) | 2006-11-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6912627B2 (en) | Method of creating a storage area & storage device | |
US10140045B2 (en) | Control device for storage system capable of acting as a constituent element of virtualization storage system | |
US8001229B2 (en) | Operation management system, management apparatus, management method and management program | |
US6640278B1 (en) | Method for configuration and management of storage resources in a storage network | |
US6538669B1 (en) | Graphical user interface for configuration of a storage system | |
US7802251B2 (en) | System for resource allocation to an active virtual machine using switch and controller to associate resource groups | |
US7020734B2 (en) | Connecting device of storage device and computer system including the same connecting device | |
JP5341184B2 (en) | Storage system and storage system operation method | |
US7117336B2 (en) | Computer system for managing storage areas in a plurality of storage devices | |
US8683157B2 (en) | Storage system and virtualization method | |
US6601128B1 (en) | Method, system, program, and data structure for selecting a preferred path to a storage device | |
US6779064B2 (en) | System, method, and computer program product for on-line replacement of a host bus adapter | |
US6654830B1 (en) | Method and system for managing data migration for a storage system | |
US9619171B2 (en) | Storage system and virtualization method | |
EP1798658A2 (en) | Storage apparatus and control method for the same, and computer program product | |
US7424529B2 (en) | System using host bus adapter connection tables and server tables to generate connection topology of servers and controllers | |
US20040230787A1 (en) | Method and apparatus for dynamically modifying a computer system configuration | |
US20060074957A1 (en) | Method of configuration management of a computer system | |
US20110066801A1 (en) | Storage system and method for controlling the same | |
IE20000203A1 (en) | Storage domain management system | |
JP2003030053A (en) | Storage subsystem having security function for each logical unit | |
JP2003091449A (en) | Storage system and method for managing the same system | |
US20100082934A1 (en) | Computer system and storage system | |
JP2005202893A (en) | Storage device controller, storage system, recording medium recording program, information processor, and method for controlling storage system | |
JP4861273B2 (en) | Computer system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |