WO2015189925A1 - ストレージシステム、ストレージ装置及びデータ移行方法 - Google Patents
ストレージシステム、ストレージ装置及びデータ移行方法 Download PDFInfo
- Publication number
- WO2015189925A1 WO2015189925A1 PCT/JP2014/065425 JP2014065425W WO2015189925A1 WO 2015189925 A1 WO2015189925 A1 WO 2015189925A1 JP 2014065425 W JP2014065425 W JP 2014065425W WO 2015189925 A1 WO2015189925 A1 WO 2015189925A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- vol
- volume
- copy
- storage
- mppk
- Prior art date
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/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
- G06F3/0647—Migration mechanisms
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
-
- 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
-
- 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/061—Improving I/O performance
-
- 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/0614—Improving the reliability of storage systems
- G06F3/0619—Improving the reliability of storage systems in relation to data integrity, e.g. data losses, bit errors
-
- 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/0638—Organizing or formatting or addressing of data
- G06F3/0644—Management of space entities, e.g. partitions, extents, pools
-
- 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/0662—Virtualisation aspects
- G06F3/0665—Virtualisation aspects at area level, e.g. provisioning of virtual or logical volumes
-
- 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]
-
- 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/0671—In-line storage system
- G06F3/0673—Single storage device
Definitions
- the present invention relates to a storage system, a storage apparatus, and a data migration method.
- the storage system includes at least one storage device that uses, for example, an HDD (Hard Disk Drive) or an SSD (Solid State Drive) as a storage device.
- a storage system including the storage device is accessed from a plurality of higher-level devices (for example, host computers) via a storage area network (Storage Area Network (SAN)) or a local network (Local Area Network (LAN)).
- SAN Storage Area Network
- LAN Local Area Network
- RAID Redundant Array of Independent (or Inexpensive) Disks
- Patent Document 1 describes that the efficiency of copy control is improved corresponding to the offload data transfer function, that is, the data copy function performed on the host computer side is offloaded to the storage device.
- Patent Document 2 discloses an information system that can improve availability, and the first volume of the first storage and the second volume of the second storage are set as the same volume. It is described that it provides. From the host computer, the first volume and the second volume are recognized as the same volume with different paths.
- the storage apparatus provides a virtual volume to the host computer as in Patent Document 2, when the host computer instructs the offload data copy described in Patent Document 1, it is recognized from the host computer side.
- a virtual volume is specified as the copy source.
- the HA pair in which the first volume of the first storage device and the second volume of the second storage device respond to the host with the same virtual ID, respectively.
- the first volume depends on the storage device in which the copy destination volume exists.
- either of the second volumes is selected as a copy source volume, and data is copied from the selected copy source volume to the copy destination volume.
- the storage system of the present invention achieves high performance such as a reduction in data processing time and a load on the host computer while realizing high reliability by an HA pair configuration that allows the system to operate even if the entire storage device is down.
- offload data copying that achieves resource efficiency is enabled.
- FIG. 1 is a diagram showing the concept of the HA pair configuration.
- FIG. 2 is an overall configuration diagram of the storage system.
- FIG. 3 is a diagram illustrating a configuration example of a VOL management table.
- FIG. 4 is a diagram illustrating a configuration example of a VOL management table.
- FIG. 5 is a diagram illustrating a first offload data copy operation.
- FIG. 6 is a diagram showing a second offload data copy operation.
- FIG. 7 is a diagram showing a third offload data copy operation.
- FIG. 8 is a diagram showing a fourth offload data copy operation.
- FIG. 9 is a flowchart showing a main process in the first to fourth offload data copy operations.
- FIG. 9 is a flowchart showing a main process in the first to fourth offload data copy operations.
- FIG. 10 is a flowchart showing offload data copy processing on the volume side that has received the transferred offload data copy command (SCOPY command).
- FIG. 11 is a flowchart showing the volume search process.
- FIG. 12 is a flowchart showing data read processing from the volume.
- FIG. 13 is a flowchart showing data write processing to the volume.
- FIG. 14 is a diagram illustrating a fifth offload data copy operation.
- FIG. 15 is a diagram illustrating a sixth offload data copy operation.
- FIG. 16 is a diagram illustrating a seventh offload data copy operation.
- FIG. 17 is a diagram illustrating an eighth offload data copy operation.
- FIG. 18 is a flowchart showing main processing in the fifth to eighth offload data copy operations.
- FIG. 11 is a flowchart showing the volume search process.
- FIG. 12 is a flowchart showing data read processing from the volume.
- FIG. 13 is a flowchart showing data write processing to the volume.
- FIG. 14
- FIG. 19 is a flowchart showing offload data copy processing on the volume side that has received the transferred offload data copy command (TCCOPY command).
- FIG. 20 is a flowchart showing processing for a token on the volume side that has received a token acquisition command.
- FIG. 21 is a diagram showing a ninth offload data copy operation (the copy source volume and the copy destination volume exist in different storage devices).
- management table various types of information may be described using an expression such as “management table”, but the various types of information may be expressed using a data structure other than a table. Further, the “management table” can be referred to as “management information” to indicate that it does not depend on the data structure.
- the program is executed by a processor such as an MP (Micro Processor) or a CPU (Central Processing Unit), and performs a predetermined process. Since the processor performs processing while appropriately using storage resources (for example, a memory) and a communication interface device (for example, a communication port), the subject of the processing may be a processor.
- the processor may have dedicated hardware in addition to the CPU.
- the computer program may be installed on each computer from a program source.
- the program source may be provided by, for example, a program distribution server or a storage medium.
- each element for example, the controller can be identified by a number or the like, but other types of identification information such as a name may be used as long as the information can identify each element.
- identification information such as a name may be used as long as the information can identify each element.
- the same reference numerals are given to the same parts.
- the present invention is not limited to the present embodiment, and any application examples that meet the idea of the present invention can be applied. Included in the scope. Further, unless specifically limited, each component may be plural or singular.
- FIG. 1 is a diagram showing the concept of the HA pair configuration.
- the storage system includes a storage device 1 11 accessed by the host computer 16, a storage device 2 12, and a management computer (not shown) that manages the storage device 1 11 and the storage device 2 12.
- Each storage device configures one or more physical volumes in the device, and hosts A1-VOL (PVOL (Primary Volume): 1171) and A2-VOL (SVOL (Secondary Volume)) 1272 Provided to the computer 16 as a virtual VOL-A.
- PVOL Primary Volume
- SVOL Secondary Volume
- HA1 Data is replicated synchronously with two physical volumes (VOL-A1 (PVOL) 1171 and VOL-A2 (SVOL) 1272).
- HA2 VOL-A1
- SVOL VOL-A2
- HA3 In response to an inquiry command from the host computer 16, the VOL-A1 (PVOL) 1171 and the VOL-A2 (SVOL) 1272 both uniquely identify the same virtual device serial number (manufacturing number) or device.
- VOL-A virtual VOL-A
- VOL-ID also referred to as a virtual ID
- the host computer 16 designates the virtual device serial number and virtual VOL name ("virtual VOL-A" in FIG. 1) assigned to the VOL of the one HA pair configuration, so that the VOL of the storage device 111 is stored.
- -Access to both VOLs of the HA pair configuration of the A1 1272 and the VOL-A2 of the storage system 2 12 is possible.
- HA4 From the host computer 16 side, both VOL-A1 (PVOL) 1171 and VOL-A2 (SVOL) 1272 access with the same VOL name A. When writing, data is first written to VOL-A1 (PVOL) 1171 and then data is written to VOL-A2 (SVOL) 1272.
- the I / O from the host computer 16 is processed.
- FIG. 2 is an overall configuration diagram of the storage system.
- the storage system includes a host computer 16, a plurality of storage devices 11 to 15, and a management computer 17 that manages the storage devices 11 to 15.
- the host computer 16 includes a CPU 161 that controls the entire apparatus, a memory that stores apparatus control information and a control program, and an FE (Front End) -PORT 163 that performs I / F with the storage apparatus.
- the management computer 17 has the same configuration as the host computer 16.
- the storage devices 11 to 15 control the FE-PORT 111 that performs I / F with the host computer 16, the network I / F 112 that performs communication with the management computer 17, the PORT 113 that performs communication between the storage devices, and the entire device. Controls data transmission / reception with a plurality of MPPKs (Micro Processor Package) 114, CMPK (Cache Memory Package) 115 that temporarily stores data to / from host computer 16 and data to / from HDD 117, and HDD 117 It includes a BE (Back End) -PORT 116 component, and further includes an internal network 119 that connects each component.
- the MPPK 114 includes a plurality of processor cores 1141 and a local memory 1142 that stores a control program and control data used in each processor core.
- the storage apparatuses 11 to 15 configure a logical volume using a plurality of HDDs 117, and the configured logical volume is transferred to a logical volume of another storage apparatus by a PORT 113 and a connection line 1131 (Fibre Channel protocol, LAN, etc.). Offload data copy using.
- the offload data copy process is performed by the MPPK 114 or the processor core 1141 in the MPPK 114 having the ownership right to access each logical volume.
- the offload data copy is a function for executing replication (copying) and migration function (copying and deletion), which are processing originally performed by the host computer 16, between the storage apparatuses instead of the host computer 16.
- replication copying
- migration function copying and deletion
- the host computer 16 can execute copy processing without inputting / outputting copy target data.
- the offload data copy there are mainly the following two methods (1) and (2).
- SCOPY instruction Single instruction (single) offload data copy
- the SCOCY command includes a copy source virtual volume name (hereinafter referred to as copy source volume), a copy destination virtual volume name (hereinafter referred to as copy destination volume), a copy data storage source in the copy source volume, and a copy data storage destination in the copy destination volume. Consists of information.
- a storage start LBA Logical Block Address
- an address range represented by the number of storage blocks are stored.
- copy source virtual volume ID (copy source VOL-ID) or a copy destination virtual volume ID (copy destination VOL-) that uniquely identifies the virtual volume is used instead of the copy source virtual volume name or copy destination virtual volume name by the SCOPY command. ID) can also be used.
- the host computer 16 issues an offload copy command (SCOPY command) from the copy source volume (VOL-A) to the copy destination volume (VOL-B) to the storage device 111, and the issued command is issued to the storage device 111.
- SOPY command an offload copy command
- MPPK-A also referred to as owner MPPK
- MPPK-B which is in charge of I / O processing to the copy destination volume (VOL-B)
- the SCOPY instruction can be received by any volume as long as the copy source volume and the copy destination volume are volumes in the same storage device.
- the copy destination volume (VOL-B) can receive the SCOPY command and perform offload data copy with the copy source volume (VOL-A).
- the third VOL-C that is neither the copy source volume (VOL-A) nor the copy destination volume (VOL-B) can receive the SCOPY command and control offload data copy.
- the MPPK-C (VOL-C) that has received the SCOPY instruction issues a read instruction to the MPPK-A (VOL-A) and a write instruction to the MPPK-B (VOL-B) to perform data copy.
- the read is executed on the copy source volume (VOL-A), and the read data is written on the copy destination volume (VOL-B).
- the copy source volume (VOL-A) receives the SCOPY instruction will be mainly described.
- the host computer 16 issues a token acquisition command including a copy source virtual volume name and copy data storage source information in the copy source virtual volume to the storage apparatus 111 (for example, VOL-A).
- the storage apparatus 111 receives the token acquisition command, the storage apparatus 111 generates a token by adding a token ID that uniquely indicates the token to the copy source virtual volume name and the copy data storage source information in the copy source virtual volume, and creates a host computer 16.
- the host computer 16 sends a COPY command composed of the copy destination virtual volume name, the copy data storage destination in the copy source virtual volume, and the received token to the copy destination volume of the storage device 111.
- the storage apparatus 1 11 that has received the COPY command performs offload data copy from VOL-A to VOL-B.
- the host computer that sends the token may be the host computer that issued the token acquisition command, or another host computer that received a copy of the token from the host computer that executed the token acquisition command.
- the COPY command also uses a copy source virtual volume ID (copy source VOL-ID) or copy destination virtual volume ID that uniquely identifies the virtual volume instead of the copy source virtual volume name or copy destination virtual volume name. (Copy destination VOL-ID) can also be used.
- the copy destination (VOL-B) of the offload data copy designated by the host computer 16 is a virtual volume of HA configuration composed of the real volumes VOL-B1 (PVOL) and VOL-B2 (SVOL).
- Case 1 (C01): VOL-A1 and VOL-B1 are in the same device (SCOPY instruction)
- Case 3 (C03): VOL-A2 and VOL-B1 are in the same device (SCOPY instruction)
- Case 5 (C05): VOL-A1 and VOL-B1 are in the same device (TCOPY command)
- Case 7 (C07): VOL-A2 and VOL-B1 are in the same device (TCOPY command)
- Case 11 (C11) VOL-A
- VOL-A1 PVOL
- VOL-A2 VOL-B1
- VOL-B2 VOL-B2
- the copy source VOL, VOL-B1 (PVOL) and VOL-B2 (SVOL), which have an HA pair configuration, are copy destination VOLs which have an HA pair configuration.
- VOL-A is a virtual VOL name indicating VOL-A1 and VOL-A2
- VOL-B is a virtual VOL name indicating VOL-B1 and VOL-B2.
- the copy source VOL or the copy destination VOL need not have the HA pair configuration, and either one may have the HA pair configuration.
- the VOL management table 1 is a volume management table in (C01), (C05), (C02), and (C06).
- the storage device 1 11 (storage 1) table is the VOL management table 31
- the storage device 2 12 (storage 2) table is the VOL management table 32
- the storage device 3 13 (storage 3) table is the VOL management table 33.
- the VOL management table 1 includes a real VOL name 311, a virtual VOL name 312, a VOL type 313, and an HA pair VOL storage destination 314.
- the VOL management table 31 / VOL management table 32 / VOL management table 33 is stored in each of the local memories 1142 of the storage 1 11 / storage 2 12 / storage 3 13, but all three VOL management tables are stored in each storage device. It can also be stored in the local memory 1142.
- VOL management table 31 and the VOL management table 33 the actual VOL name 311 and the HA pair VOL storage destination 314 are shown in parentheses (C02) and (C06). Otherwise, the four cases are the same. is there.
- the actual VOL name 311 in the VOL management table 31 is “B1 (B2)” because the case of (C01) and (C05) is “B1”, and the case of (C02) and (C06) is “B2”.
- the HA pair VOL storage destination 314 is “B2 of storage 3 (B1)” in the case of (C01) and (C05) is “B2 of storage 3”, and is in the case of (C02) and (C06). Is “B1 of storage 3”.
- the virtual VOL name 312 is “B”
- the VOL type 313 is “HA-PVOL”.
- the actual VOL name 311 in the VOL management table 33 is “B2 (B1)” because the cases (C01) and (C05) are “B2” and the cases (C02) and (C06) are “B1”.
- the HA pair VOL storage destination 314 is “B1 of storage 1 (B2)” in the case of (C01) and (C05) is “B1 of storage 1”, and is in the case of (C02) and (C06). Is “B2 of storage 1”.
- the virtual VOL name 312 is “B”
- the VOL type 313 is “HA-SVOL”.
- the VOL management table 1 manages the volumes of each storage device in this way, and the MPPK 114 searches the VOL management table 1 to find out which storage device has the necessary volume, and in the VOL management table 1. Thus, it can be seen which volume is a single (Simplex) or HA pair configuration.
- the VOL management table 2 is a volume management table in (C04), (C08), (C03), (C07).
- the storage 11 table is the VOL management table 41
- the storage device 2 12 (storage 2) table is the VOL management table 42
- the storage device 3 13 (storage 3) table is the VOL management table 43.
- the VOL management table 2 includes a real VOL name 311, a virtual VOL name 312, a VOL type 313, and an HA pair VOL storage destination 314.
- the VOL management table 1 and the VOL management table 2 may be collectively referred to as a VOL management table.
- VOL management table 42 and the VOL management table 43 the actual VOL name 311 and the HA pair VOL storage destination 314 are shown in parentheses (C03) and (C07). Otherwise, the four cases are the same. is there.
- the actual VOL name 311 in the VOL management table 42 is “B2 (B1)” because the cases (C04) and (C08) are “B2”, and the cases (C03) and (C07) are “B1”.
- the HA pair VOL storage destination 314 is “B1 of storage 3 (B2)” in the case of (C04) and (C08) is “B1 of storage 3”, and is in the case of (C03) and (C07). Is “B2 of storage 3”.
- the virtual VOL name 312 is “B”
- the VOL type 313 is “HA-SVOL”.
- the actual VOL name 311 in the VOL management table 43 is “B1 (B2)” because the cases (C04) and (C08) are “B1” and the cases (C03) and (C07) are “B2”. ".
- the HA pair VOL storage destination 314 is “B2 (B1) of storage 2” when (C04) and (C08) are “B2 of storage 2”, and (C03) and (C07). Is “B1 of storage 2”.
- the virtual VOL name 312 is “B”
- the VOL type 313 is “HA-PVOL”.
- the MPPK 114 searches the VOL management table 2 to identify the volume configuration in the storage apparatus.
- FIG. 5 is a diagram illustrating a first offload data copy operation. In this case, it is assumed that VOL-A1 (PVOL) 1171 and VOL-B1 (PVOL) 1181 are in the same apparatus as the storage 111.
- the host computer 16 sends an offload copy command (SCOPY command) from the copy source VOL-A to the copy destination VOL-B to the VOL-A 1 (PVOL) 1171 responsible MPPK 114 in the storage 1.
- the MPPK 114 in charge of the VOL-A1 (PVOL) 1171 of the storage 1 11 receives the SCOPY instruction to the VOL-A1 (PVOL) 1171.
- the VOL-A1 (PVOL) 1171 responsible MPPK 114 searches the VOL management table 31 for a volume in the same storage (storage 1 11) where the VOL-A1 (PVOL) 1171 exists.
- the MPPK 114 in charge of VOL-A1 (PVOL) 1171 finds VOL-A (VOL-A1 (PVOL) 1171) and VOL-B (VOL-B1 (PVOL) 1181) in the storage 1 11. Also, the MPPK 114 in charge of VOL-A1 (PVOL) 1171 has an HA pair configuration of VOL-A1 (PVOL) 1171 and VOL-A2 (SVOL) 1272 of storage 2 12 from the HA pair VOL storage destination 314 in the VOL management table 31.
- the VOL-B1 (PVOL) 1181 and the VOL-B2 (SVOL) 1382 of the storage 3 13 are determined to have an HA pair configuration.
- the MPPK 114 in charge of the VOL-A1 (PVOL) 1171 reads the copy target data designated by the copy data storage source information from the VOL-A1 (PVOL) 1171, and writes the read data to the cache memory of the CMPK 115.
- the VOL-B1 (PVOL) 1181 responsible MPPK 114 writes the copy target data read from the cache memory to the copy data storage destination in the VOL-B1 (PVOL) 1181.
- the MPPK 114 in charge of the VOL-B1 (PVOL) 1181 determines from the search result of the VOL management table 31 that the VOL-B2 (SVOL) 1382 and the VOL-B1 (PVOL) 1181 constitute a HA pair, and the VOL-B2 (SVOL)
- the write command of the data to be copied to 1382 is transferred to the MPPK 114 of the storage 3 13.
- the VOL-B2 (SVOL) 1382 MPPK 114 in the storage 3 13 receives the write command.
- the VOL-B2 (SVOL) 1382 responsible MPPK 114 writes the copy target data to the VOL-B2 (SVOL) 1382.
- VOL-A1 (PVOL) 1171 is a single volume (Simplex) that is not an HA pair configuration and a volume (HA-PVOL) that is an HA pair configuration.
- VOL-B1 (PVOL) 1181 also has a single volume that is not in the HA pair configuration and two cases that are volumes in the HA pair configuration.
- the copy target data is written in the order of the VOL-B1 (PVOL) 1181 and the VOL-B2 (SVOL) 1382.
- the volume that receives the SCOPY command may be a volume in the same device as the VOL-A1 (PVOL) 1171.
- the SCOPY instruction received by the MPPK 114 in charge of I / O processing of a volume other than the VOL-A1 (PVOL) 1171 is transferred to the VOL-A1 (PVOL) 1171 MPPK 114. Therefore, the processing after the transfer of the SCOPY instruction is the same as the processing from S011 to S018. Further, even when VOL-A1 is SVOL and VOL-A2 is PVOL, the processing contents are the same.
- the processing when the VOL-A2 (SVOL) receives the SCOPY instruction is the same as the processing when the VOL-A PVOL and the SVOL are exchanged in (C03) described later.
- VOL-A1 (PVOL) 1171 that has received the offload data copy instruction (SCOPY instruction) is copied to the VOL-B2 (SVOL) 1382 that constitutes the HA pair with the VOL-B1 (PVOL) 1181.
- the target data can be written. For this reason, data copying between volumes in the HA pair configuration, which has conventionally been performed by the host computer 16, can be performed only between storage devices, so that high performance such as reduction of data processing time and load of the host computer 16 can be achieved. In addition, resource efficiency can be improved.
- FIG. 6 is a diagram showing a second offload data copy operation.
- VOL-A1 (PVOL) 1171 and VOL-B2 (SVOL) 1182 are in the same apparatus as storage 111.
- the host computer 16 transmits a SCOPY instruction from the copy source VOL-A to the copy destination VOL-B to the VOL-A1 (PVOL) 1171 responsible MPPK 114 of the storage 1.11.
- the VOL-A1 (PVOL) 1171 responsible MPPK 114 of the storage 1 11 receives the SCOPY instruction.
- the VOL-A1 (PVOL) 1171 responsible MPPK 114 searches the VOL management table 31 for a volume in the same storage apparatus (storage 1 11) where the VOL-A1 (PVOL) 1171 exists.
- the MPPK 114 in charge of VOL-A1 (PVOL) 1171 discovers VOL-A (VOL-A1 (PVOL) 1171) and VOL-B (VOL-B2 (SVOL) 1182).
- the MPPK 114 in charge of the VOL-A1 (PVOL) 1171 has the VOL-A1 (PVOL) 1171 and the VOL-A2 (SVOL) 1272 of the storage device 2 12 from the HA pair VOL storage destination 314 in the VOL management table 31 as an HA pair. It is determined that the configuration, VOL-B2 (SVOL) 1182 and VOL-B1 (PVOL) 1381 of the storage 3 13 are HA pair configurations.
- the MPPK 114 in charge of the VOL-A1 (PVOL) 1171 reads the copy target data from the VOL-A1 (PVOL) 1171 and writes the read data to the cache memory of the CMPK 115.
- the MPPK 114 in charge of the VOL-A1 (PVOL) 1171 determines from the search result of the VOL management table 31 that the VOL-B2 (SVOL) 1182 and the VOL-B1 (PVOL) 1381 constitute a HA pair, and the copy target data Is transferred to the MPPK 114 in charge of the VOL-B1 (PVOL) 1381 in the storage 3 13.
- the MPPK 114 in charge of VOL-B1 (PVOL) 1381 receives a write command for the copy target data.
- the MPPK 114 in charge of the VOL-B1 (PVOL) 1381 writes the copy target data to the VOL-B1 (PVOL) 1381.
- the VOL-B1 (PVOL) 1381 MPPK 114 sends a write completion report to the VOL-B2 (SVOL) 1182 MPPK 114.
- the MPPK 114 in charge of the VOL-B2 (SVOL) 1182 of the storage 1 11 writes the copy target data to the VOL-B2 (SVOL) 1182 after receiving the write completion report.
- the host computer 16 can execute offload data copy only between storages by simply issuing a SCOPY instruction to the storage apparatus.
- VOL-A1 is SVOL and VOL-A2 is PVOL
- the processing contents are the same.
- the processing when the VOL-A2 (SVOL) receives the SCOPY instruction is the same as the processing when the VOL-A PVOL and SVOL are exchanged in (C04) described later.
- the data to be read can be read from either PVOL or SVOL.
- data must be written to PVOL and then written to SVOL to synchronize the data between the volumes in the HA pair configuration.
- FIG. 7 is a diagram showing a third offload data copy operation.
- VOL-A2 (SVOL) 1272 and VOL-B1 (PVOL) 1281 are in the same apparatus as storage 212.
- the host computer 16 transmits a SCOPY instruction from the copy source VOL-A to the copy destination VOL-B to the VOL-A1 (PVOL) 1171 responsible MPPK 114 of the storage 1.11.
- the VOL-A1 (PVOL) 1171 responsible MPPK 114 receives the SCOPY instruction.
- the MPPK 114 searches the VOL management table 41 for a volume in the same storage 111 where the VOL-A1 (PVOL) 1171 exists. As a result of the search, MPPK 114 finds VOL-A (VOL-A1 (PVOL) 1171), but cannot find VOL-B (undiscovered). Further, the MPPK 114 finds in the storage 2 12 a VOL-A2 (SVOL) 1272 that constitutes an HA pair with the VOL-A1 (PVOL) 1171.
- the MPPK 114 in charge of the VOL-A1 (PVOL) 1171 transfers the SCOPY instruction to the storage 2.12.
- the MPPK 114 in charge of the VOL-A2 (SVOL) 1272 receives the SCOPY instruction and searches the VOL management table 42.
- VOL-A2 (SVOL) 1272 and VOL-B1 (PVOL) 1281 are found in the storage 2 12.
- the MPPK 114 recognizes from the VOL management table 42 that the VOL-B 1 (PVOL) 1281 and the VOL-B 2 (SVOL) 1382 constituting the HA pair exist in the storage 3 13.
- the MPPK 114 in charge of the VOL-A2 (SVOL) 1272 reads the copy target data from the VOL-A2 (SVOL) 1272, and writes the read data to the cache memory of the CMPK 115.
- the MPPK 114 in charge of the VOL-B1 (PVOL) 1281 writes the copy target data read from the cache memory to the VOL-B1 (PVOL) 1281.
- the MPPK 114 in charge of the VOL-B1 (PVOL) 1281 and the VOL-B1 (PVOL) 1281 and the VOL-B2 (SVOL) 1382 constituting the HA pair are instructed to write the copy target data write command to the VOL-B2 of the storage 3 (SVOL) 1382 Transfer to MPPK 114 in charge.
- the VOL-B2 (SVOL) 1382 MPPK 114 receives the write command.
- the MPPK 114 in charge of the VOL-B2 (SVOL) 1382 writes the copy target data to the VOL-B2 (SVOL) 1382.
- the host computer 16 can execute offload data copy only between storages by simply issuing a SCOPY instruction to the storage apparatus.
- VOL-B1 (PVOL) 1281 is a single volume that does not have an HA pair configuration and another volume that has an HA pair configuration. Further, even when VOL-A1 is SVOL and VOL-A2 is PVOL, the processing contents are the same. Note that the processing when the VOL-A2 (SVOL) receives the SCOPY instruction is the same as the processing when the VOL-A PVOL and the SVOL are replaced in (C01) described above.
- FIG. 8 is a diagram showing a fourth offload data copy operation. In this case, it is assumed that VOL-A2 (SVOL) 1272 and VOL-B2 (SVOL) 1282 are in the same apparatus as storage 212.
- the host computer 16 transmits a SCOPY instruction from the copy source VOL-A to the copy destination VOL-B to the VOL-A1 (PVOL) 1171 responsible MPPK 114 of the storage 1.11.
- the VOL-A1 (PVOL) 1171 responsible MPPK 114 receives the SCOPY instruction.
- the MPPK 114 in charge of the VOL-A1 (PVOL) 1171 searches the VOL management table 41 for a volume in the same storage 111 where the VOL-A1 (PVOL) 1171 exists.
- VOL-A1 (PVOL) 1171 discovers VOL-A (VOL-A1 (PVOL) 1171), but cannot find VOL-B (undiscovered). Also, the VOL-A1 (PVOL) 1171 responsible MPPK 114 finds the VOL-A1 (PVOL) 1171 and the VOL-A2 (SVOL) 1272 in the storage 2 12 as an HA pair.
- the MPPK 114 in charge of the VOL-A1 (PVOL) 1171 transfers the offload data copy command (SCOPY command) to the MPPK 114 in charge of the VOL-A2 (SVOL) 1272 in the storage 2 12.
- the MPPK 114 in charge of the VOL-A2 (SVOL) 1272 that has received the SCOPY instruction searches the VOL management table 42. As a result, VOL-A2 (SVOL) 1272 and VOL-B2 (SVOL) 1282 are found in the storage 2 12. Further, the MPPK 114 recognizes from the VOL management table 42 that the VOL-B2 (SVOL) 1282 and the VOL-B1 (PVOL) 1381 constituting the HA pair exist in the storage 3 13.
- the MPPK 114 in charge of the VOL-A2 (SVOL) 1272 reads the copy target data from the VOL-A2 (SVOL) 1272, and writes the read data to the cache memory of the CMPK 115. Then, the VOL-A2 (SVOL) 1272 responsible MPPK 114 transmits a write command to the VOL-B2 (SVOL) 1282 responsible MPPK 114. In S047, the VOL-B2 (SVOL) 1282 responsible MPPK 114 transfers a copy target data write command to the VOL-B1 (PVOL) 1381 responsible MPPK 114 constituting the HA pair recognized from the search result of the VOL management table 31.
- VOL-B2 (SVOL) 1282 responsible MPPK 114 transfers a copy target data write command to the VOL-B1 (PVOL) 1381 responsible MPPK 114 constituting the HA pair recognized from the search result of the VOL management table 31.
- the MPPK 114 in charge of the VOL-B1 (PVOL) 1381 of the storage 3 13 receives the write command.
- the MPPK 114 in charge of the VOL-B1 (PVOL) 1381 writes the copy target data to the VOL-B1 (PVOL) 1381.
- the MPPK 114 in charge of the VOL-B1 (PVOL) 1381 transmits a write completion report in the VOL-B1 (PVOL) 1381 to the MPPK1 in charge of the VOL-B2 (SVOL) 1282.
- the MPPK 114 in charge of the VOL-B2 (SVOL) 1282 writes the copy target data to the VOL-B2 (SVOL) 1282.
- the host computer 16 can execute offload data copy only between storages by simply issuing a SCOPY instruction to the storage apparatus.
- VOL-A1 is SVOL and VOL-A2 is PVOL
- the processing contents are the same. Note that the processing when the VOL-A2 (SVOL) receives the SCOPY instruction is the same as the processing when the VOL-A PVOL and the SVOL are replaced in (C02) described above.
- FIG. 9 is a flowchart showing a main process in the first to fourth offload data copy operations.
- the main subject of the processing is simply MPPK114.
- the MPPK 114 receives a SCOPY instruction (copy source VOL name, copy destination VOL name, copy data storage source, copy data storage destination) from the host computer 16.
- a SCOPY instruction copy source VOL name, copy destination VOL name, copy data storage source, copy data storage destination
- the MPPK 114 searches the VOL management table 31/41 to find the copy source VOL name.
- the MPPK 114 determines whether a copy source VOL has been found. When the copy source VOL is found (Yes), the MPPK 114 executes S902. If not found (No), the MPPK 114 executes S903 and transmits an error report that the copy source VOL does not exist to the host computer 16. Note that the processing of S901 and S902 may be executed for all storage apparatuses connected to the storage apparatus that has received the SCOPY instruction to search for a copy source VOL.
- the MPPK 114 searches the VOL management table 31/41 to find the copy destination VOL name. In step S905, the MPPK 114 determines whether a copy destination VOL has been found. When the copy destination VOL is found (Yes), the MPPK 114 determines that offload data copy is possible within the own apparatus, and executes S906. This case is (C01) and (C02) described above. If it has not been found (No), the MPPK 114 determines that offload data copy is not possible within itself and executes S908.
- the MPPK 114 reads the copy target data designated by the copy data storage source from the copy source VOL, and writes the read copy target data in the cache memory of the CMPK 115.
- the MPPK 114 reads the copy target data stored in the cache memory of the CMPK 115, and writes the read copy target data to the copy data storage destination in the copy destination VOL. Then, the MPPK 114 copies all the copy target data, ends the main process of the SCOPY instruction, and transmits a copy completion report to the host computer 16.
- the MPPK 114 determines whether the copy source VOL type is HA-PVOL or HA-SVOL based on the VOL type 313 of the VOL management table 31/41. If it is the HA pair configuration (Yes), the MPPK 114 executes S910. If it is not the HA pair configuration (No), the MPPK 114 executes S909 and transmits an error report that the copy destination VOL does not exist to the host computer 16.
- the MPPK 114 transfers the SCOPY instruction to the storage apparatus in which the HA pair VOL of the copy source VOL exists.
- the processing in the storage apparatus to which the SCOPY instruction has been transferred will be described with reference to FIG.
- the MPPK 114 ends the execution of the SCOPY instruction. Note that during the period from the start of reading the copy target data to the end of writing (S906, S907, and S910), the copy target data is write-locked so that it is not changed by other processing.
- FIG. 10 is a flowchart showing offload data copy processing on the storage device side that has received the transferred offload data copy command (SCOPI command). This process is started when the storage apparatus receives the transfer SCOPY instruction in (C03) and (C04).
- the MPPK 114 receives the SCOPY instruction transferred from the other storage apparatus.
- the MPPK 114 searches the VOL management table 31/41 to find the copy source VOL name designated by the SCOPY instruction.
- the MPPK 114 determines whether a copy source VOL has been found. When the copy source VOL is found (Yes), the MPPK 114 executes S1004. If not found (No), the MPPK 114 executes S1003 and transmits an error report that the copy source VOL does not exist to the host computer 16. It should be noted that the processing of S1001 and S1002 may be executed on all storage devices connected to the storage device that has received the transferred SCOPY instruction to find the copy source VOL.
- the MPPK 114 searches the VOL management table 31/41 to find the copy destination virtual VOL name (copy destination VOL) designated by the SCOPY instruction.
- the MPPK 114 determines whether a copy destination VOL has been found. When the copy destination VOL is found (Yes), the MPPK 114 executes S1007. If not found (No), the MPPK 114 executes S1006 and transmits an error report that the copy destination VOL does not exist to the host computer 16. Note that the processing of S1004 and S1005 may be executed for all the storage apparatuses connected to the storage apparatus that has received the transferred SCOPY instruction to search for a copy destination VOL.
- the MPPK 114 reads the copy target data from the copy data storage source designated by the SCOPY instruction in the copy source VOL, and writes the read copy target data in the cache memory of the CMPK 115.
- the MPPK 114 reads the copy target data stored in the cache memory of the MPK 115, and writes the read copy target data to the copy data storage destination specified by the SCOPY instruction in the copy destination VOL.
- the process returns to S910 of FIG.
- the VOL search process in S901, S904, S1001, and S1004 described above will be described with reference to FIG.
- FIG. 11 is a flowchart showing the volume search process.
- the MPPK 114 starts a VOL search process (VOL name search).
- the MPPK 114 searches for a virtual VOL name corresponding to an argument (copy source VOL name or copy destination VOL name) from the virtual VOL name 312 of the VOL management table of the storage apparatus having the self VOL.
- the MPPK 114 acquires the real VOL name corresponding to the found virtual VOL name from the real VOL name 311 in the VOL management table.
- the MPPK 114 passes the acquired real VOL name to the call routine of this process, and ends the process. If there is no corresponding real VOL, information such as an error report or NULL (blank) is passed to the call routine.
- FIG. 12 is a flowchart showing data read processing from the volume.
- the MPPK 114 starts a process of reading the copy target data from the volume corresponding to the VOL name (copy source VOL name) specified by the argument.
- the MPPK 114 reads from the copy source volume and writes the read copy target data to the cache memory of the CMPK 115.
- the read process is a process of simply reading the copy target data from the volume regardless of whether the volume is a single VOL (VOL type 313 is “Simplex”) / PVOL / SVOL.
- FIG. 13 is a flowchart showing data write processing to the volume.
- the MPPK 114 starts a process of writing the copy target data to the volume corresponding to the VOL name (copy destination VOL name) specified by the argument.
- the MPPK 114 determines whether the copy destination VOL is an HA pair configuration. When the HA pair configuration is not used (No), the MPPK 114 executes S1302 in order to write the copy target data to the single VOL when the copy destination VOL is a single VOL. In the case of the HA pair configuration (Yes), the MPPK 114 executes S1303. In step S1302, the MPPK 114 reads the copy target data stored in the cache memory of the CMPK 115 by the read process of FIG. 12, and writes the read copy target data to the copy destination VOL.
- the MPPK 114 determines whether the copy destination VOL is a PVOL. If it is a PVOL (Yes), the MPPK 114 executes the processing from S1304 onward in order to write the copy target data to the copy destination PVOL. Note that there are four cases (C01), (C03), (C05), and (C07) of writing to the copy destination PVOL. When the copy destination VOL is not PVOL but SVOL (No), the MPPK 114 executes the processing from S1307 onward in order to write the copy target data to the copy destination SVOL. Note that there are four cases (C02), (C04), (C06), and (C08) of writing to the copy destination SVOL.
- the MPPK 114 reads the copy target data stored in the cache memory of the CMPK 115, and writes the read copy target data to the copy destination VOL (PVOL).
- the MPPK 114 transfers the write instruction for the copy target data to the SVOL responsible MPPK 114 having the HA pair configuration.
- the MPPK 114 writes the copy target data to the SVOL. Then, the process is returned to the PVOL responsible MPPK, and the VOL write process is terminated.
- step S1307 the MPPK 114 transfers the copy target data write command to the PVOL responsible MPPK 114.
- the data is first written to the PVOL and then written to the SVOL.
- the PVOL responsible MPPK 114 writes the copy target data to the PVOL, and returns the process to the SVOL responsible MPPK 114.
- the SVOL MPPK 114 writes the copy target data read from the cache memory of the CMPK 115 to the copy destination VOL (SVOL).
- FIG. 14 is a diagram illustrating a fifth offload data copy operation.
- the copy source volume name is “VOL-A”
- the copy destination volume name is “VOL-B”
- the copy data storage source and the copy data storage destination store address information.
- VOL-A1 (PVOL) 1171 and VOL-B1 (PVOL) 1181 are in the same apparatus as the storage 111.
- a token acquisition command is issued from the host computer 16 to the VOL-A1 (PVOL) 1171 in the storage 111, and the VOL-A1 (PVOL) 1171 MPPK 114 in charge receives the token acquisition command.
- the MPPK 114 in charge of the VOL-A1 (PVOL) 1171 transmits the generated token relating to the copy source VOL-A to the host computer 16, and the host computer 16 acquires the token.
- the host computer 16 transmits a COPY command including the token of the copy source VOL-A to the VOL-B1 (PVOL) 1181, and the VOL-B1 (PVOL) 1181 MPPK 114 receives.
- the MPPK 114 in charge of the VOL-B1 (PVOL) 1181 searches the VOL management table 31 for the VOL in the storage 111. As a result of the search, the MPPK 114 finds VOL-A1 (PVOL) 1171 and VOL-B1 (PVOL) 1181. In S054, the VOL-A1 (PVOL) 1171 responsible MPPK 114 reads the copy target data from the VOL-A1 (PVOL) 1171 and writes the read data to the cache memory of the CMPK 115. In S055, the MPPK 114 in charge of the VOL-B1 (PVOL) 1181 writes the copy target data read from the cache memory to the VOL-B1 (PVOL) 1181.
- the MPPK 114 in charge of the VOL-B1 (PVOL) 1181 recognizes the VOL-B2 (SVOL) command for writing the data to be copied to the VOL-B2 (SVOL) 1382 constituting the HA pair recognized from the search result of the VOL management table 31. ) Transfer to MPPK 114 in charge of 1382.
- the MPPK 114 in charge of VOL-B2 (SVOL) 1382 receives the write command.
- the MPPK 114 in charge of the VOL-B2 (SVOL) 1382 writes the copy target data to the VOL-B2 (SVOL) 1382.
- VOL-A1 (PVOL) 1171 is a single volume that is not in an HA pair configuration
- VOL-B1 (PVOL) 1181 also has a single volume that is not in the HA pair configuration and two cases that are volumes in the HA pair configuration.
- the copy target data is written in the order of the VOL-B1 (PVOL) 1181 and the VOL-B2 (SVOL) 1382.
- VOL-A1 is SVOL and VOL-A2 is PVOL
- the processing contents are the same.
- the processing when the VOL-A2 (SVOL) receives the COPY command is the same as the processing when the VOL-A PVOL and the SVOL are exchanged in (C07) described later.
- token duplication processing is performed at the time of token acquisition, even when VOL-A2 receives a token acquisition command, VOL-A1 duplicates and duplicates the token. This token duplication and duplication processing is also executed in (C06), (C07), and (C08).
- VOL-B1 PVOL
- TCCOPY instruction offload data copy instruction
- FIG. 15 is a diagram illustrating a sixth offload data copy operation.
- a token acquisition command is issued from the host computer 16 to the VOL-A1 (PVOL) 1171 of the storage 111, and the VOL-A1 (PVOL) 1171 MPPK 114 in charge receives the token acquisition command.
- the MPPK 114 in charge of the VOL-A1 (PVOL) 1171 transmits the generated token relating to the copy source VOL-A to the host computer 16, and the host computer 16 acquires the token.
- the host computer 16 transmits a COPY instruction including the token of the copy source VOL-A to the VOL-B1 (PVOL) 1381 of the storage 3 13 and received by the MPPK 114 in charge of the VOL-B1 (PVOL) 1381 .
- the MPPK 114 in charge of the VOL-B1 (PVOL) 1381 searches the VOL management table 33 for the VOL in the storage 3 13. As a result of the search, the MPPK 114 in charge of VOL-B1 (PVOL) 1381 finds only VOL-B1 (PVOL) 1381 and cannot find the copy source VOL-A. In this search process, it is recognized that the VOL-B1 (PVOL) 1381 and the VOL-B2 (SVOL) 1182 constituting the HA pair exist in the storage 1.11. In S064, the MPPK 114 in charge of VOL-B1 (PVOL) 1381 transfers a COPY instruction including the token of the copy source VOL-A to VOL-B2 (SVOL) 1182.
- the MPPK 114 in charge of the VOL-B2 (SVOL) 1182 searches the VOL management table for the VOL in the storage 111. As a result of the search, the MPPK 114 in charge of VOL-B2 (SVOL) 1182 discovers VOL-A1 (PVOL) 1171 and VOL-B2 (SVOL) 1182. In S066, the VOL-A1 (PVOL) 1171 responsible MPPK 114 reads the copy target data from the VOL-A1 (PVOL) 1171, and writes the read data to the cache memory of the CMPK 115.
- the VOL-B2 (SVOL) 1182 responsible MPPK 114 transfers the copy target data and the write command read from the cache memory to the VOL-B1 (PVOL) 1381 responsible MPPK 114.
- the MPPK 114 in charge of VOL-B1 (PVOL) 1381 receives the copy target data and the write command.
- the MPPK 114 in charge of the VOL-B1 (PVOL) 1381 writes the copy target data to the VOL-B1 (PVOL) 1381.
- the VOL-B1 (PVOL) 1381 responsible MPPK 114 sends a writing completion report to the VOL-B2 (SVOL) 1182 responsible MPPK 114.
- the MPPK 114 in charge of the VOL-B2 (SVOL) 1182 that has received the write completion report in S06a writes the copy target data to the VOL-B2 (SVOL) 1182.
- VOL-A2 (SVOL) receives a COPY command, it corresponds to the case where the PVOL and SVOL of virtual VOL-A are replaced in (C08).
- FIG. 16 is a diagram illustrating a seventh offload data copy operation.
- a token acquisition command is issued from the host computer 16 to the VOL-A1 (PVOL) 1171 of the storage 111, and the VOL-A1 (PVOL) 1171 MPPK 114 in charge receives the token acquisition command.
- the MPPK 114 in charge of the VOL-A1 (PVOL) 1171 transmits the generated token relating to the copy source VOL-A to the host computer 16, and the host computer 16 acquires the token.
- the host computer 16 transmits a COPY instruction including the token of the copy source VOL-A to the VOL-B1 (PVOL) 1281 of the storage 2 12, and the MPPK 114 in charge of the VOL-B1 (PVOL) 1281 receives it. .
- the MPPK 114 in charge of VOL-B1 (PVOL) 1281 searches the VOL management table 42 for the VOL in the storage 2 12. As a result of the search, the MPPK 114 finds VOL-A2 (SVOL) 1272 and VOL-B1 (PVOL) 1281. This search process recognizes that the VOL-B1 (PVOL) 1281 and the VOL-B2 (SVOL) 1382 constituting the HA pair exist in the storage 3 13.
- the MPPK 114 in charge of the VOL-A2 (SVOL) 1272 reads the copy target data from the VOL-A2 (SVOL) 1272, and writes the read data to the cache memory of the CMPK 115.
- the VOL-A2 (SVOL) 1272 responsible MPPK 114 transfers the copy target data and the write command read from the cache memory to the VOL-B1 (PVOL) 1281 responsible MPPK 114.
- the VOL-B1 (PVOL) 1281 responsible MPPK 114 writes the received copy target data to the VOL-B1 (PVOL) 1281.
- the VOL-B1 (PVOL) 1281 responsible MPPK 114 transfers the COPY instruction including the token of the copy source VOL-A and the copy target data to the VOL-B2 (SVOL) 1382.
- the MPPK 114 in charge of VOL-B2 (SVOL) 1382 receives the COPY command and the copy target data.
- the MPPK 114 in charge of the VOL-B2 (SVOL) 1382 writes the copy target data in the VOL-B2 (SVOL) 1382.
- VOL-A2 (SVOL) receives a COPY command, it corresponds to the case where the PVOL and SVOL of virtual VOL-A are replaced in (C05).
- FIG. 17 is a diagram illustrating an eighth offload data copy operation.
- a token acquisition command is issued from the host computer 16 to the VOL-A1 (PVOL) 1171 of the storage 111, and the VOL-A1 (PVOL) 1171 MPPK 114 in charge receives the token acquisition command.
- the VOL-A (PVOL) responsible MPPK 114 transmits the generated token relating to the copy source VOL-A to the host computer 16, and the host computer 16 acquires the token.
- the host computer 16 sends a COPY instruction including the token of the copy source VOL-A to the VOL-B1 (PVOL) 1381 of the storage 3 13, and the MPPK 114 in charge of the VOL-B1 (PVOL) 1381 receives it. To do.
- the MPPK 114 in charge of the VOL-B1 (PVOL) 1381 searches the VOL management table 43 for a VOL in the storage 3.
- the MPPK 114 in charge of VOL-B1 (PVOL) 1381 finds VOL-B1 (PVOL) 1381 in the storage 3 13, but cannot find VOL-A.
- This search process recognizes that the VOL-B1 (PVOL) 1381 and the VOL-B2 (SVOL) 1282 constituting the HA pair exist in the storage 2 12.
- the VOL-B1 (PVOL) 1381 responsible MPPK 114 is the VOL-B1 (PVOL) 1381 and the VOL-B2 (SVOL) 1282 responsible MPPK 114 of the storage 2 12 constituting the HA pair is the copy source VOL-A. Transfer TCOPY instruction including token.
- the MPPK 114 in charge of VOL-B2 (SVOL) 1282 searches the VOL management table 42 for the VOL in the storage 2 12. As a result of the search, the MPPK 114 finds VOL-A2 (SVOL) 1272 and VOL-B2 (SVOL) 1282.
- the MPPK 114 in charge of the VOL-A2 (SVOL) 1272 reads the copy target data from the VOL-A2 (SVOL) 1272, and writes the read data to the cache memory of the CMPK 115.
- the VOL-B2 (SVOL) 1282 responsible MPPK 114 transfers the read copy target data and write command to the VOL-B1 (PVOL) 1381 responsible MPPK 114.
- the MPPK 114 in charge of VOL-B1 (PVOL) 1381 receives the copy target data and the write command.
- the MPPK 114 in charge of the VOL-B1 (PVOL) 1381 writes the copy target data in the VOL-B1 (PVOL) 1381.
- the VOL-B1 (PVOL) 1381 responsible MPPK 114 sends a writing completion report to the VOL-B2 (SVOL) 1282 responsible MPPK 114.
- the MPPK 114 in charge of the VOL-B2 (SVOL) 1282 writes the copy target data to the VOL-B2 (SVOL) 1282.
- the host computer 16 simply transmits the token acquisition command and the COPY command generated from the acquired token to the storage device, and copies the offload data between the storage devices (from the virtual VOL-A to the virtual VOL-B). Data copy). Since the host computer 16 can eliminate the need for read / write processing for copying data to the storage apparatus, the processing performance can be improved. Further, since the time for occupying the network between the host computer 16 and the storage device can be reduced, the response performance can be improved. In the configuration of FIG. 17, when VOL-A2 (SVOL) receives a COPY instruction, it corresponds to the case where the PVOL and SVOL of virtual VOL-A are replaced in (C06).
- VOL-A2 SVOL
- FIG. 18 is a flowchart showing main processing in the fifth to eighth offload data copy operations. This process starts when the host computer 16 issues a COPY instruction including a token acquired by a token acquisition instruction to the storage apparatus to the storage apparatus having the copy destination VOL.
- the main subject of the processing is simply MPPK114.
- the MPPK 114 receives a COPY instruction (token) and starts offload data copy processing.
- the MPPK 114 searches the VOL management table for a VOL corresponding to the copy destination virtual VOL (hereinafter, copy destination VOL) name of the COPY instruction. In other words, the MPPK 114 checks whether the copy destination VOL name exists in the virtual VOL name 312 of the VOL management table. In step S1802, the MPPK 114 determines whether a copy destination VOL has been found. If found (Yes), the MPPK 114 executes S1804, and if not found (No), executes S1803. In S1803, the MPPK 114 transmits an error report indicating that the copy destination VOL could not be found to the host computer 16, and ends the process.
- copy destination VOL the MPPK 114 searches the VOL management table for a VOL corresponding to the copy destination virtual VOL (hereinafter, copy destination VOL) name of the COPY instruction. In other words, the MPPK 114 checks whether the copy destination VOL name exists in the virtual VOL name 312 of the VOL management table. In step S1802, the MPPK
- step S1804 the MPPK 114 acquires a copy source virtual VOL (hereinafter, copy source VOL) name from the token of the COPY instruction.
- step S1805 the MPPK 114 searches for the acquired copy source VOL name in the virtual VOL name 312 of the VOL management table.
- step S1806 the MPPK 114 determines whether a copy source VOL has been found. If found (Yes), the MPPK 114 performs S1807. This case corresponds to (C05) and (C08), and is a case where offload data copy is possible in one storage device alone (in its own housing). If it cannot be found (No), the MPPK 114 executes S1809. This case corresponds to (C06) and (C07), and it is impossible to copy offload data in one storage device alone (within its own chassis).
- the MPPK 114 reads the copy target data from the copy data storage source of the copy source VOL. In step S1808, the MPPK 114 writes the copy target data to the copy data storage destination of the copy destination VOL. Between the read processing in S1807 and the write processing in S1808, write lock is performed so that other processing (such as destaging processing) does not rewrite the copy target data.
- the MPPK 114 determines whether the copy destination VOL type is HA-PVOL or HA-SVOL in the VOL type 313 of the VOL management table 31/41. If it is an HA pair configuration (Yes), the MPPK 114 executes S1811. If it is not the HA pair configuration (No), the MPPK 114 executes S1810 and sends an error report that the copy source VOL does not exist to the host computer 16.
- the MPPK 114 transfers the COPY instruction to the storage apparatus in which the HA pair VOL of the copy destination VOL exists. Processing in the storage apparatus to which the COPY instruction has been transferred will be described with reference to FIG. Then, the MPPK 114 transmits a COPY instruction completion report to the host computer 16 and ends the process.
- FIG. 19 is a flowchart showing offload data copy processing on the volume side that has received the transferred offload data copy command (TCCOPY). This process is started when the transfer SCOPY instruction in (C06) and (C07) is received.
- the MPPK 114 receives the COPY command transferred from another storage device.
- the MPPK 114 searches the virtual VOL name 312 of the VOL management table for the copy destination VOL name of the COPY instruction, and finds the copy destination VOL name.
- the MPPK 114 determines whether a copy destination VOL has been found. When the copy destination VOL is found (Yes), the MPPK 114 executes S1004. If not found (No), the MPPK 114 executes S1003 and sends an error report that the copy destination VOL does not exist to the host computer 16. Note that the processing of S1901 and S1902 may be executed for all the storage apparatuses connected to the storage apparatus that has received the transferred COPY instruction to find the copy destination VOL.
- step S1904 the MPPK 114 acquires the copy source VOL name from the token in the COPY instruction.
- step S1905 the MPPK 114 searches for the virtual VOL name 312 in the VOL management table and finds a VOL that matches the acquired copy source VOL name.
- step S1906 the MPPK 114 determines whether a copy source VOL has been found. When the copy source VOL is found (Yes), the MPPK 114 executes S1908. If not found (No), the MPPK 114 executes S1907 and transmits an error report that the copy source VOL does not exist to the host computer 16. Note that the processing of S1905 and S1906 may be executed for all the storage apparatuses connected to the storage apparatus that has received the transferred COPY instruction to find the copy source VOL.
- step S1908 the MPPK 114 determines whether the copy source VOL stores the token ID.
- the token ID is held in both VOLs of PVOL and SVOL and duplicated. Since the copy source VOL stores this token ID, the MPPK 114 reads the copy target data by the COPY instruction, the copy source VOL (copy source VOL (PVOL) alone, or the copy source VOL (PVOL) and the copy source VOL (PVOL)). ) And the pair configuration) can be correctly recognized, and the copy target data can be read from either copy source VOL. Detailed processing will be described with reference to FIG.
- the MPPK 114 executes S1910.
- the MPPK 114 transmits an error report that the copy source VOL does not exist to the host computer 16 in S1909.
- the MPPK 114 reads the copy target data from the copy source VOL, and writes the read copy target data in the cache memory of the CMPK 115.
- the MPPK 114 reads the copy target data stored in the cache memory of the MPK 115, and writes the read copy target data to the copy destination VOL.
- the MPPK 114 returns the process to S1811 of FIG.
- the VOL search process is the same as that shown in FIG. 11, the read process of S1807 / S1910 is the same as that shown in FIG. 12, and the write process of S1808 / S1911 is the same as that shown in FIG.
- FIG. 20 is a flowchart showing processing for a token on the volume side that has received a token acquisition command.
- the MPPK 114 receives a token acquisition command (copy source virtual VOL name, copy data storage source) from the host computer 16. Upon receipt of this token acquisition command, processing in the MPPK 114 is started.
- the MPPK 114 searches the virtual VOL name 312 in the VOL management table and finds a VOL that matches the acquired copy source VOL name.
- the MPPK 114 determines whether a copy source VOL has been found. When the copy source VOL is found (Yes), the MPPK 114 executes S2004. If not found (No), the MPPK 114 executes S2003 and transmits an error report that the copy source VOL does not exist to the host computer 16.
- the MPPK 114 In S2004, the MPPK 114 generates a token in which a token ID for uniquely identifying the token is added to the received token acquisition command information (copy source virtual VOL name, copy data storage source). In step S2005, the MPPK 114 stores the token ID of the copy source VOL. It is also possible to store a token in a local memory accessed by the copy source VOL MPPK 114 and use it for token identification or the like.
- the MPPK 114 determines whether the copy source VOL type is HA-PVOL or HA-SVOL based on the VOL type 313 of the VOL management table. If it is the HA pair configuration VOL (Yes), the MPPK 114 executes S2007. In S2007, the MPPK 114 performs a token duplication process.
- the MPPK 114 sends the token ID to the HA pair VOL of the copy source VOL, and the HA pair VOL that has received the token ID stores the token ID in itself. If the VOL has an HA pair configuration (No), the MPPK 114 transmits the generated token to the host computer 16. Note that the generated token may be transmitted to the host computer 16 in S2004. By doing so, the token acquisition command processing on the storage device side and the COPY command generation processing on the host computer 16 side can be executed in parallel, so that the processing performance of the entire storage system can be improved. Further, by duplicating the token, even if the token in one copy source VOL disappears, the offload data copy can be continued in the other copy source VOL. Furthermore, it is possible to acquire the load of the copy source VOL having the same token, read data from the copy source VOL with a light load, and prevent the access performance to the copy source VOL from deteriorating.
- the host computer 16 can perform offload data copy between predetermined volumes only by issuing a token acquisition command and a TCOPY command accompanying it to the storage device. Therefore, as with the SCOPY instruction, processing related to copying on the host computer 16 side can be reduced, so that the processing performance of the host computer 16 and the entire storage system can be improved. Further, the offload data copy can also improve the data transfer speed and transfer efficiency by using a dedicated port and a dedicated line for connecting the storage apparatuses, so that the copy time can be shortened.
- VOL-A1 (PVOL) 1171 is stored in the storage 1
- VOL-A 2 (SVOL) 1272 is stored in the storage 2
- VOL-B 1 (PVOL) 1381 is stored in the storage 3
- VOL-B 2 (SVOL) is stored in the storage 4 14.
- 1482 exists. Also, it is assumed that each storage uses an PORT 113 and can communicate with each other.
- the MPPK 114 in charge of the VOL-A1 (PVOL) 1171 starts offload data copy processing.
- the volume in the own device is searched with the VOL management table 31.
- the MPPK 114 in charge of the VOL-A1 (PVOL) 1171 confirms the existence of only the VOL-A1 (PVOL) 1171 in the storage 1.11.
- the MPPK 114 recognizes that the VOL-A 2 (SVOL) 1272 exists in the storage 2 12 from the information of the HA pair VOL storage destination 314 in the VOL management table 31.
- the MPPK 114 in charge of VOL-A1 (PVOL) 1171 searches the VOL management table 31 of the storage 4 14 via the storage 2 12.
- the search result recognizes that VOL-B2 (SVOL) 1482 exists in the storage 4.
- the MPPK 114 in charge of the VOL-A 1 (PVOL) 1171 recognizes that the VOL-B 1 (PVOL) 1381 exists in the storage 3 13 from the information of the HA pair VOL storage destination 314 in the VOL management table 31.
- the storage device that has received the offload data copy command can specify the storage device in which the copy source VOL or the copy destination VOL exists.
- a cascade configuration is taken as an example, but a VOL search can be performed even in a multi-target configuration.
- VOL search of another device and remote copy between different devices can be performed by communication (port 113 and dedicated line 1131) between different (different) storage devices. That is, VOLs in storage apparatuses that can communicate with each other can be handled as if they were in the same storage apparatus and provided to the host computer 16. As a result, the same processing as the offload data copy processing in the VOL in the same storage apparatus described in this embodiment can be performed in the VOL in another storage that can communicate with each other.
- the HA pair configuration is described as two VOLs (VOL-B1 (PVOL), VOL-B2 (SVOL)), but is not limited to this. Three or more may be sufficient.
- the connection configuration may be a cascade configuration in which VOL-B2 (SVOL1) is connected to VOL-B1 (PVOL) and VOL-B3 (SVOL2) is connected to VOL-B2 (SVOL1).
- VOL-B2 SVOL1
- SVOL2 VOL-B3
- the offload data copy in this embodiment can be executed even in a multi-target configuration in which VOL-B2 (SVOL1) and VOL-B3 (SVOL2) are connected to VOL-B1 (PVOL).
- the data processing time can be reduced while realizing high reliability by the HA pair configuration that allows the system to operate even when the entire storage apparatus is down. -It is possible to enable offload data copying that achieves high performance and resource efficiency such as a reduction in the load on the host computer.
- this invention is not limited to the above-mentioned Example, Various modifications are included.
- the above-described embodiments have been described in detail for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described. Further, a part of the configuration of one embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of one embodiment. Further, it is possible to add, delete, and replace other configurations for a part of the configuration of each embodiment.
- Each of the above-described configurations, functions, processing units, processing means, and the like may be realized by hardware by designing a part or all of them with, for example, an integrated circuit.
- Each of the above-described configurations, functions, and the like may be realized by software by interpreting and executing a program that realizes each function by the processor.
- Information such as programs, tables, and files for realizing each function may be stored in a memory, a hard disk, a recording device such as an SSD (Solid State Drive), or a recording medium such as an IC card, an SD card, or a DVD.
- a recording device such as an SSD (Solid State Drive)
- a recording medium such as an IC card, an SD card, or a DVD.
- control lines and information lines indicate what is considered necessary for the explanation, and not all the control lines and information lines on the product are necessarily shown. Actually, it may be considered that almost all the components are connected to each other.
Abstract
Description
図1は、HAペア構成の概念を示す図である。ストレージシステムは、ホスト計算機16がアクセスするストレージ装置1 11と、ストレージ装置2 12、ストレージ装置1 11とストレージ装置2 12を管理する管理計算機(図示せず)を備える。各ストレージ装置は、1つ以上の物理ボリュームを装置内に構成し、A1-VOL(PVOL(Primary Volume):正ボリューム)1171と、A2-VOL(SVOL(Secondary Volume:副ボリューム))1272をホスト計算機16へ仮想VOL-Aとして提供する。
(HA1)2つの物理ボリューム(VOL-A1(PVOL)1171及びVOL-A2(SVOL)1272)でデータを同期的に複製する。
(HA2)VOL-A1(PVOL)1171とVOL-A2(SVOL)1272との双方にアクセスを可能とすることで、両方のVOLが同時にI/O処理を担当するActive-Active構成を実現する。
(HA3)ホスト計算機16からのInquary コマンドに対して、VOL-A1(PVOL)1171とVOL-A2(SVOL)1272とは、どちらも同じ仮想装置の製番(製造番号)ないし装置を一意に識別する装置ID、と仮想VOL名(図1では“仮想VOL-A”)ないし仮想ボリュームを一意に識別する仮想VOL-ID(仮想IDとも表す)を応答する。そのため、ホスト計算機16は、1組のHAペア構成のVOLに割り当てられた仮想装置製番、仮想VOL名(図1では“仮想VOL-A”)を指定することで、ストレージ装置1 11のVOL-A1 1272とストレージ装置2 12のVOL-A2とのどちらのHAペア構成のVOLにもアクセスできる。
(HA4)ホスト計算機16側からは、VOL-A1(PVOL)1171もVOL-A2(SVOL)1272も、同じAというVOL名でアクセスする。ライトの際は、最初に、VOL-A1(PVOL)1171にデータを書き込み、次に、VOL-A2(SVOL)1272にデータを書き込む。
という構成とし、ホスト計算機16からのI/Oを処理する。
図2は、ストレージシステムの全体構成図である。ストレージシステムは、ホスト計算機16、複数のストレージ装置11から15と、ストレージ装置11から15を管理する管理計算機17を備える。
オフロードデータコピーとは、本来はホスト計算機16が行う処理である複製(コピー)やマイグレーション機能(コピー及び削除)を、ホスト計算機16ではなくストレージ装置間で実行する機能である。このオフロードデータコピー機能によりホスト計算機16は、コピー対象データの入出力をすることなく、コピー処理を実行できる。これにより、ホスト計算機16の使用リソース(CPUやメモリ)削減効果、ホスト計算機16とストレージ装置間の通信量削減による処理時間短縮が見込める。
(1)一命令(Single)オフロードデータコピー(以下、SCOPY命令と称す)
SCOPY命令は、コピー元仮想ボリューム名(以下、コピー元ボリューム)、コピー先仮想ボリューム名(以下、コピー先ボリューム)、コピー元ボリュームでのコピーデータ格納元、コピー先ボリュームでのコピーデータ格納先の情報から構成される。コピーデータ格納元及びコピーデータ格納先には、例えば、格納開始LBA(Logical Block Address)と格納ブロック数で表されたアドレス範囲が格納される。なお、SCOPY命令でコピー元仮想ボリューム名ないしコピー先仮想ボリューム名の代わりに、仮想ボリュームを一意に識別するコピー元仮想ボリュームID(コピー元VOL-ID)ないしコピー先仮想ボリュームID(コピー先VOL-ID)を用いることもできる。
まず、ホスト計算機16は、コピー元仮想ボリューム名、コピー元仮想ボリュームでのコピーデータ格納元の情報で構成されるトークン取得命令を、ストレージ装置1 11(例えば、VOL-A)に発行する。トークン取得命令を受領したストレージ装置1 11は、コピー元仮想ボリューム名およびコピー元仮想ボリュームでのコピーデータ格納元の情報に、トークンを一意に示すトークンIDを付加したトークンを生成し、ホスト計算機16に返信する。
本実施例では、ホスト計算機16から指定されたオフロードデータコピーのコピー元(VOL-A)が実ボリュームVOL-A1(PVOL)とVOL-A2(SVOL)とから構成されるHA構成の仮想ボリュームであり、ホスト計算機16から指定されたオフロードデータコピーのコピー先(VOL-B)が実ボリュームVOL-B1(PVOL)とVOL-B2(SVOL)とから構成されるHA構成の仮想ボリュームである場合を考える。この場合、VOL-A、VOL-Bを構成する実ボリュームのストレージ装置における配置とオフロードデータコピーの方式により、以下のようなケースが存在する。
・ケース1(C01):VOL-A1とVOL-B1が同一装置内(SCOPY命令)
・ケース2(C02):VOL-A1とVOL-B2が同一装置内(SCOPY命令)
・ケース3(C03):VOL-A2とVOL-B1が同一装置内(SCOPY命令)
・ケース4(C04):VOL-A2とVOL-B2が同一装置内(SCOPY命令)
・ケース5(C05):VOL-A1とVOL-B1が同一装置内(TCOPY命令)
・ケース6(C06):VOL-A1とVOL-B2が同一装置内(TCOPY命令)
・ケース7(C07):VOL-A2とVOL-B1が同一装置内(TCOPY命令)
・ケース8(C08):VOL-A2とVOL-B2が同一装置内(TCOPY命令)
・ケース11(C11)VOL-A1とVOL-B1が異なる(別の)装置
・ケース12(C12)VOL-A1とVOL-B2が異なる(別の)装置
・ケース13(C13)VOL-A2とVOL-B1が異なる(別の)装置
・ケース14(C14)VOL-A2とVOL-B2が異なる(別の)装置
なお、ケース11(C11)からケース14(C14)の異なる(別の)装置でのコピー動作については、同一装置内のケースでの“同一装置内コピー(ローカルコピー)”の代わりに、“別装置へのコピー(リモートコピー)”を使用する。また、“同一装置内ボリュームのサーチ”の代わりに“接続装置内ボリュームのサーチ”を実行する。以降の説明では、VOL-A1(PVOL)、VOL-A2(SVOL)、VOL-B1(PVOL)、VOL-B2(SVOL)と表記し、VOL-A1(PVOL)とVOL-A2(SVOL)とはHAペア構成であるコピー元VOL、VOL-B1(PVOL)とVOL-B2(SVOL)ともHAペア構成であるコピー先VOLとする。また、VOL-AとはVOL-A1とVOL-A2を指す仮想VOL名で、VOL-Bは、VOL-B1とVOL-B2を指す仮想VOL名とする。なお、本実施例では、コピー元VOLないしコピー先VOLがHAペア構成でなくてもよく、どちらか一方がHAペア構成としてればよい。
図3及び図4は、VOL管理テーブルの構成例を示す図である。VOL管理テーブル1は、(C01)、(C05)、(C02)、(C06)でのボリューム管理テーブルである。ストレージ装置1 11(ストレージ1)用テーブルがVOL管理テーブル31、ストレージ装置2 12(ストレージ2)用テーブルがVOL管理テーブル32、ストレージ装置3 13(ストレージ3)用テーブルがVOL管理テーブル33である。VOL管理テーブル1は、実VOL名311、仮想VOL名312、VOL種別313、HAペアVOL格納先314を備える。なお、VOL管理テーブル31/VOL管理テーブル32/VOL管理テーブル33は、ストレージ1 11/ストレージ2 12/ストレージ3 13のローカルメモリ1142それぞれに格納されるが、3つのVOL管理テーブル全てを各ストレージ装置のローカルメモリ1142に格納することもできる。
<C01:VOL-A1、VOL-B1が同一装置内(SCOPY)>
SCOPY命令のコピー元ボリューム名に“VOL-A”と、コピー先ボリューム名に“VOL-B”、コピーデータ格納元およびコピーデータ格納先には、それぞれアドレス情報が格納されている。図5は、第1のオフロードデータコピー動作を示す図である。このケースでは、VOL-A1(PVOL)1171、VOL-B1(PVOL)1181がストレージ1 11という同一装置内にあるものとする。
図6は、第2のオフロードデータコピー動作を示す図である。このケースでは、VOL-A1(PVOL)1171、VOL-B2(SVOL)1182がストレージ1 11という同一装置内にあるものとする。
図7は、第3のオフロードデータコピー動作を示す図である。このケースでは、VOL-A2(SVOL)1272、VOL-B1(PVOL)1281がストレージ2 12という同一装置内にあるものとする。
図8は、第4のオフロードデータコピー動作を示す図である。このケースでは、VOL-A2(SVOL)1272、VOL-B2(SVOL)1282がストレージ2 12という同一装置内にあるものとする。
図9は、第1から第4でのオフロードデータコピー動作におけるメイン処理を示すフローチャートである。説明を簡便にするため、処理の主体を単純にMPPK114とする。
図10は、転送されたオフロードデータコピー命令(SCOPY命令)を受領したストレージ装置側でのオフロードデータコピー処理を示すフローチャートである。本処理は、(C03)、(C04)での転送SCOPY命令をストレージ装置が受領したことを契機に開始される。
図11は、ボリュームサーチ処理を示すフローチャートである。S1100で、MPPK114は、VOLサーチ処理(VOL名の検索)を開始する。S1101で、MPPK114は、自VOLがあるストレージ装置のVOL管理テーブルの仮想VOL名312から、引数(コピー元VOL名ないしコピー先VOL名)に該当する仮想VOL名を探す。MPPK114は探し出した仮想VOL名に対応する実VOL名を、VOL管理テーブルの実VOL名311から取得する。MPPK114は、取得した実VOL名を本処理のコールルーチンに渡し、処理を終了する。なお、該当する実VOLが存在しない場合は、エラー報告ないしNULL(空白)などの情報をコールルーチンに渡す。
図12は、ボリュームからのデータ読み出し処理を示すフローチャートである。S1200で、MPPK114は、引数で指定されたVOL名(コピー元VOL名)に該当するボリュームからコピー対象データをリードする処理を開始する。S1201で、MPPK114は、コピー元ボリュームから読み出し、読み出したコピー対象データをCMPK115のキャッシュメモリに書き出す。なお、リード処理は、ボリュームが単体VOL(VOL種別313が“Simplex”)/PVOL/SVOLの何れであるかは関係なく、単純にボリュームからコピー対象データを読み出す処理である。
図13は、ボリュームへのデータ書き込み処理を示すフローチャートである。S1300で、MPPK114は、引数で指定されたVOL名(コピー先VOL名)に該当するボリュームにコピー対象データをライトする処理を開始する。
<HAペア構成でのトークン取り扱い>
HAペア構成の場合、コピー元(トークン発行元)として仮想VOL名を使用する。HAペア構成ではPVOLもPVOLとペア構成するSVOLも仮想VOL名は同じであるから、コピー元としてどちらのVOLも使用することができる。そのため、トークンを発行したボリュームがVOL-A1(PVOL)であっても、トークン発行元のHAペアであるVOL-A2(SVOL)のどちらもコピー元として使用できる。この場合、VOL-A1(PVOL)で発行されたトークンは、VOL-A2(SVOL)でコピーされ二重化される。次に、トークン方式の命令(TCOPY命令)でのオフロードデータコピー動作を説明する。
図14は、第5のオフロードデータコピー動作を示す図である。TCOPY命令のコピー元ボリューム名に“VOL-A”と、コピー先ボリューム名に“VOL-B”、コピーデータ格納元およびコピーデータ格納先には、それぞれアドレス情報が格納されている。このケースでは、VOL-A1(PVOL)1171、VOL-B1(PVOL)1181がストレージ1 11という同一装置内にあるものとする。
図15は、第6のオフロードデータコピー動作を示す図である。
図16は、第7のオフロードデータコピー動作を示す図である。
図17は、第8のオフロードデータコピー動作を示す図である。
図18は、第5から第8でのオフロードデータコピー動作におけるメイン処理を示すフローチャートである。本処理は、ホスト計算機16がストレージ装置へのトークン取得命令で取得したトークンを含むTCOPY命令を、コピー先VOLを有するストレージ装置に発行したことを契機に処理が開始される。なお、説明を簡便にするため、処理の主体を単純にMPPK114とする。S1800で、MPPK114は、TCOPY命令(トークン)を受領し、オフロードデータコピー処理を開始する。
図19は、転送されたオフロードデータコピー命令(TCOPY)を受領したボリューム側でのオフロードデータコピー処理を示すフローチャートである。本処理は、(C06)、(C07)での転送SCOPY命令を受領したことを契機に開始される。
図20は、トークン取得命令を受領したボリューム側でのトークンへの処理を示すフローチャートである。S2000で、MPPK114は、ホスト計算機16からのトークン取得命令(コピー元仮想VOL名、コピーデータ格納元)を受領する。このトークン取得命令の受領により、MPPK114での処理が開始される。
図21で、コピー元VOL-A(VOL-A1(PVOL)、VOL-A2(SVOL))と、コピー先VOL-B(VOL-B1(PVOL)、VOL-B2(SVOL))が全て異なるストレージ装置に存在する場合でのオフロードデータコピー動作について説明する。
Claims (12)
- ホスト計算機に接続するストレージシステムであって、
前記ストレージシステムは、第1ストレージ装置と、第2ストレージ装置とを備え、
前記第1ストレージ装置の第1ボリュームと、前記第1ボリュームのデータが二重化された前記第2ストレージ装置の第2ボリュームとがそれぞれ同じ仮想IDをホストに応答し、HAペアを構成し、
前記第1ストレージ装置または前記第2のストレージ装置が、仮想IDをコピー元として指定したオフロードデータコピーの指示を前記ホスト計算機から受領すると、
コピー先ボリュームが存在するストレージ装置に応じて、前記第1ボリュームまたは前記第2ボリュームのいずれをコピー元ボリュームとして選択し、当該選択したコピー元ボリュームからコピー先ボリュームにデータをコピーする
ことを特徴とするストレージシステム。 - 請求項1記載のストレージシステムであって、前記コピー先ボリュームが第3ボリュームと、前記第3ボリュームのデータが二重化された第4ボリュームとがそれぞれ同じ仮想IDをホストに応答し、HAペアを構成する
ことを特徴とするストレージシステム。 - 請求項1記載のストレージシステムであって、前記コピー元ボリュームから読み出したデータを、前記第3ボリュームに書き込んだ後、前記第4ボリュームに当該データを書き込む
ことを特徴とするストレージシステム。 - 請求項2記載のストレージシステムであって、更に第3ストレージ装置を備え、前記第1ストレージ装置に第3ボリュームを、第3ストレージ装置に前記第4ボリュームを備える
ことを特徴とするストレージシステム。 - 請求項4記載のストレージシステムであって、第1ストレージ装置に前記第4ボリュームを、第3ストレージ装置に前記第3ボリュームを備える
ことを特徴とするストレージシステム。 - 請求項4記載のストレージシステムであって、第3ストレージ装置に前記第4ボリュームを、第2ストレージ装置に前記第3ボリュームを備える
ことを特徴とするストレージシステム。 - 請求項4記載のストレージシステムであって、第2ストレージ装置に前記第4ボリュームを、第3ストレージ装置に前記第3ボリュームを備える
ことを特徴とするストレージシステム。 - 請求項1記載のストレージシステムであって、更に、各ボリュームを制御する制御部を備え、前記ホスト計算機からのデータコピー命令を当該制御部が受信し、前記コピー元ボリュームから前記コピー先ボリュームへのデータコピーを実行する
ことを特徴とするストレージシステム。 - 請求項8記載のストレージシステムであって、
前記ホスト計算機は前記第1ストレージ装置ないし第2ストレージ装置にトークン取得命令を発行し、
前記トークン取得命令を受信したストレージ装置は、当該トークン取得命令にトークンを一意に識別するトークンIDを付加したトークンを生成して、当該生成したトークンを前記ホスト計算機の送信し、
前記トークンIDを前記第1ボリュームと前記第2ボリュームとに格納し、
前記ホスト計算機は受信した前記トークンからデータコピー命令を生成し、当該データコピー命令を前記第1ストレージ装置ないし第2ストレージ装置の制御部に送信して前記コピー元ボリュームから前記コピー先ボリュームへのデータコピーを実行する
ことを特徴とするストレージシステム。 - ホスト計算機に接続するストレージ装置であって、
第1ボリュームと、前記第1ボリュームのデータが二重化された前記第2ボリュームとがそれぞれ同じ仮想IDをホストに応答し、HAペアを構成し、
前記ストレージ装置が、仮想IDをコピー元として指定したオフロードデータコピーの指示を前記ホスト計算機から受領すると、
前記第1ボリュームまたは前記第2ボリュームのいずれをコピー元ボリュームとして選択し、当該選択したコピー元ボリュームからコピー先ボリュームにデータをコピーする
ことを特徴とするストレージ装置。 - 請求項10記載のストレージ装置であって、前記コピー先ボリュームが第3ボリュームと、前記第3ボリュームのデータが二重化された第4ボリュームとがそれぞれ同じ仮想IDをホストに応答し、HAペアを構成する
ことを特徴とするストレージ装置。 - ホスト計算機に接続するストレージシステムのデータ移行方法であって、
前記ストレージシステムは、第1ストレージ装置と、第2ストレージ装置とを備え、
前記第1ストレージ装置の第1ボリュームと、前記第1ボリュームのデータが二重化された前記第2ストレージ装置の第2ボリュームとがそれぞれ同じ仮想IDをホストに応答し、HAペアを構成し、
前記第1ストレージ装置または前記第2のストレージ装置が、仮想IDをコピー元として指定したオフロードデータコピーの指示を前記ホスト計算機から受領するステップと、
コピー先ボリュームが存在するストレージ装置に応じて、前記第1ボリュームまたは前記第2ボリュームのいずれをコピー元ボリュームとして選択するステップと、
前記選択したコピー元ボリュームからコピー先ボリュームにデータをコピーするステップとを有する
ことを特徴とするストレージシステムのデータ移行方法。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2016527539A JP6279731B2 (ja) | 2014-06-11 | 2014-06-11 | ストレージシステム、ストレージ装置及びデータ移行方法 |
US15/121,782 US10191685B2 (en) | 2014-06-11 | 2014-06-11 | Storage system, storage device, and data transfer method |
PCT/JP2014/065425 WO2015189925A1 (ja) | 2014-06-11 | 2014-06-11 | ストレージシステム、ストレージ装置及びデータ移行方法 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2014/065425 WO2015189925A1 (ja) | 2014-06-11 | 2014-06-11 | ストレージシステム、ストレージ装置及びデータ移行方法 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2015189925A1 true WO2015189925A1 (ja) | 2015-12-17 |
Family
ID=54833056
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2014/065425 WO2015189925A1 (ja) | 2014-06-11 | 2014-06-11 | ストレージシステム、ストレージ装置及びデータ移行方法 |
Country Status (3)
Country | Link |
---|---|
US (1) | US10191685B2 (ja) |
JP (1) | JP6279731B2 (ja) |
WO (1) | WO2015189925A1 (ja) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2017208319A1 (ja) * | 2016-05-31 | 2017-12-07 | 株式会社日立製作所 | ストレージシステム及びストレージシステムの管理方法 |
WO2019003416A1 (ja) * | 2017-06-30 | 2019-01-03 | 株式会社日立製作所 | ストレージシステム及び記憶制御方法 |
US10846012B2 (en) | 2018-09-21 | 2020-11-24 | Hitachi, Ltd. | Storage system for minimizing required storage capacity during remote volume replication pair duplication |
US11586516B2 (en) | 2021-02-15 | 2023-02-21 | Hitachi, Ltd. | Storage system, storage device, and storage device management method |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10762021B2 (en) * | 2016-07-11 | 2020-09-01 | Hitachi, Ltd. | Information processing system, and control method of information processing system |
JP6734251B2 (ja) | 2017-11-30 | 2020-08-05 | 株式会社日立製作所 | システム及びその制御方法並びにプログラム |
US10956078B2 (en) | 2018-03-27 | 2021-03-23 | EMC IP Holding Company LLC | Storage system with loopback replication process providing object-dependent slice assignment |
US10866969B2 (en) * | 2018-03-28 | 2020-12-15 | EMC IP Holding Company LLC | Storage system with loopback replication process providing unique identifiers for collision-free object pairing |
JP6751423B2 (ja) * | 2018-07-31 | 2020-09-02 | 株式会社日立製作所 | ストレージ装置及びその制御方法 |
US11775186B1 (en) * | 2021-08-04 | 2023-10-03 | Amazon Technologies, Inc. | Dynamic usage-metric-based configuration of storage volumes |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2007042008A (ja) * | 2005-08-05 | 2007-02-15 | Hitachi Ltd | 記憶制御方法及び記憶制御システム |
JP2008134986A (ja) * | 2006-10-30 | 2008-06-12 | Hitachi Ltd | 情報システム、データ転送方法及びデータ保護方法 |
JP2009093316A (ja) * | 2007-10-05 | 2009-04-30 | Hitachi Ltd | ストレージシステム及び仮想化方法 |
JP2009104421A (ja) * | 2007-10-23 | 2009-05-14 | Hitachi Ltd | ストレージアクセス装置 |
JP2014048787A (ja) * | 2012-08-30 | 2014-03-17 | Fujitsu Ltd | 情報処理装置、コピー制御プログラム、およびコピー制御方法 |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP5057366B2 (ja) * | 2006-10-30 | 2012-10-24 | 株式会社日立製作所 | 情報システム及び情報システムのデータ転送方法 |
JP4902403B2 (ja) | 2006-10-30 | 2012-03-21 | 株式会社日立製作所 | 情報システム及びデータ転送方法 |
JP4990066B2 (ja) * | 2007-08-21 | 2012-08-01 | 株式会社日立製作所 | 論理ボリュームのペアを利用したデータ保存の方式を変更する機能を備えたストレージシステム |
JP5222617B2 (ja) | 2008-04-28 | 2013-06-26 | 株式会社日立製作所 | 情報システム及びi/o処理方法 |
JP5508798B2 (ja) * | 2009-09-29 | 2014-06-04 | 株式会社日立製作所 | クラスタを考慮してレプリケーションを管理する管理方法及びシステム |
WO2011104741A1 (en) * | 2010-02-23 | 2011-09-01 | Hitachi, Ltd. | Management system for storage system and method for managing storage system |
JP2012027829A (ja) * | 2010-07-27 | 2012-02-09 | Hitachi Ltd | スケールアウト型ストレージシステムを含んだストレージシステム群及びその管理方法 |
JP5749803B2 (ja) * | 2011-04-27 | 2015-07-15 | 株式会社日立製作所 | 情報記憶システム及びストレージシステム管理方法 |
JP5942511B2 (ja) * | 2012-03-19 | 2016-06-29 | 富士通株式会社 | バックアップ装置,バックアップ方法,およびバックアッププログラム |
US20150227600A1 (en) * | 2014-02-13 | 2015-08-13 | Actifio, Inc. | Virtual data backup |
-
2014
- 2014-06-11 JP JP2016527539A patent/JP6279731B2/ja active Active
- 2014-06-11 US US15/121,782 patent/US10191685B2/en active Active
- 2014-06-11 WO PCT/JP2014/065425 patent/WO2015189925A1/ja active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2007042008A (ja) * | 2005-08-05 | 2007-02-15 | Hitachi Ltd | 記憶制御方法及び記憶制御システム |
JP2008134986A (ja) * | 2006-10-30 | 2008-06-12 | Hitachi Ltd | 情報システム、データ転送方法及びデータ保護方法 |
JP2009093316A (ja) * | 2007-10-05 | 2009-04-30 | Hitachi Ltd | ストレージシステム及び仮想化方法 |
JP2009104421A (ja) * | 2007-10-23 | 2009-05-14 | Hitachi Ltd | ストレージアクセス装置 |
JP2014048787A (ja) * | 2012-08-30 | 2014-03-17 | Fujitsu Ltd | 情報処理装置、コピー制御プログラム、およびコピー制御方法 |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2017208319A1 (ja) * | 2016-05-31 | 2017-12-07 | 株式会社日立製作所 | ストレージシステム及びストレージシステムの管理方法 |
WO2019003416A1 (ja) * | 2017-06-30 | 2019-01-03 | 株式会社日立製作所 | ストレージシステム及び記憶制御方法 |
JPWO2019003416A1 (ja) * | 2017-06-30 | 2019-11-07 | 株式会社日立製作所 | ストレージシステム及び記憶制御方法 |
US10732901B2 (en) | 2017-06-30 | 2020-08-04 | Hitachi Ltd. | Storage system and storage control method |
US10846012B2 (en) | 2018-09-21 | 2020-11-24 | Hitachi, Ltd. | Storage system for minimizing required storage capacity during remote volume replication pair duplication |
US11586516B2 (en) | 2021-02-15 | 2023-02-21 | Hitachi, Ltd. | Storage system, storage device, and storage device management method |
Also Published As
Publication number | Publication date |
---|---|
US10191685B2 (en) | 2019-01-29 |
JPWO2015189925A1 (ja) | 2017-04-20 |
JP6279731B2 (ja) | 2018-02-14 |
US20170017433A1 (en) | 2017-01-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP6279731B2 (ja) | ストレージシステム、ストレージ装置及びデータ移行方法 | |
US7343467B2 (en) | Method to perform parallel data migration in a clustered storage environment | |
US7478221B1 (en) | System and method for using consistent virtual addresses to communicate in cooperative multi-layer virtualization environments | |
CN102681794B (zh) | 基于双控制器实现磁盘冗余阵列保护的方法及系统 | |
WO2015125221A1 (ja) | ストレージシステム及び移行方法 | |
CN109074297A (zh) | 在同步复制的数据集中启用数据完整性检查和更快的应用恢复 | |
US9514008B2 (en) | System and method for distributed processing of file volume | |
JP4400653B2 (ja) | 情報システム、および、情報システムの情報保存方法 | |
US11144252B2 (en) | Optimizing write IO bandwidth and latency in an active-active clustered system based on a single storage node having ownership of a storage object | |
US7809907B2 (en) | System and method for backup by splitting a copy pair and storing a snapshot | |
JP2005301590A (ja) | ストレージシステム及びデータ複製方法 | |
JP2007279845A (ja) | ストレージシステム | |
JP2013539119A (ja) | オフロード・リードおよびライト | |
US10768851B2 (en) | Instant-ready active-active storage nodes | |
US10031682B1 (en) | Methods for improved data store migrations and devices thereof | |
JP6197816B2 (ja) | ストレージシステム、ストレージの管理方法、及び、コンピュータ・プログラム | |
CN113360082A (zh) | 存储系统及其控制方法 | |
JP2007310448A (ja) | 計算機システム、管理計算機、および、ストレージシステム管理方法 | |
US8799596B2 (en) | Switching visibility between virtual data storage entities | |
WO2015198390A1 (ja) | ストレージシステム | |
US10140307B1 (en) | Efficiently managing reference weights for write splits | |
JP5445504B2 (ja) | データ複製装置、データ複製制御方法、及びデータ複製制御プログラム | |
JP6194784B2 (ja) | ストレージ制御装置、制御方法および制御プログラム | |
CN105912277B (zh) | 在虚拟机镜像中实现文件系统单写日志的方法 | |
US20090271579A1 (en) | Storage subsystem and storage system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 14894546 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2016527539 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15121782 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 14894546 Country of ref document: EP Kind code of ref document: A1 |